docs(runicnpc): stage 3's design, D239–D242 #303

wtclaude · 2026-09-30T06:50:03Z

wtclaude commented

2026-09-30 06:50:03 +00:00

What

This records the org lead's four answers for stage 3 (2026-09-30) in runicnpc/PLAN.md:

D239: a roamer may be placed on a player-built floor, because Rust's mesh covers it a moment after it is built (stage 2's finding). The placement's answer warns that if the structure is destroyed, the NPC falls back to the nearest navmesh. Sentry-only stays the rule for spots truly off the mesh. §5, §8, stage 1's Q4 note and stage 10 now follow this, which closes the item stage 2 left open.
D240: routes are recorded point by point: /rnpc path record <name>, point, undo, save [loop|back] and cancel. Nothing is drawn on screen (D216).
D241: a placement made in game is named <profile>-<n> and can be renamed with /rnpc rename.
D242: /rnpc place and /rnpc here take key=value options in any order: count=, respawn=, mode=, move= and radius=.

It also updates §5's command table and stage 3's text and test plan, and the decision range in README.md and PLAN_REDESIGNS.md now reads D214–D242.

Checklist

AI-assisted: written with Claude Code (Claude Opus 5.5); the commit carries the trailer.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What This records the org lead's four answers for stage 3 (2026-09-30) in `runicnpc/PLAN.md`: - **D239:** a roamer may be placed on a player-built floor, because Rust's mesh covers it a moment after it is built (stage 2's finding). The placement's answer warns that if the structure is destroyed, the NPC falls back to the nearest navmesh. Sentry-only stays the rule for spots truly off the mesh. §5, §8, stage 1's Q4 note and stage 10 now follow this, which closes the item stage 2 left open. - **D240:** routes are recorded point by point: `/rnpc path record <name>`, `point`, `undo`, `save [loop|back]` and `cancel`. Nothing is drawn on screen (D216). - **D241:** a placement made in game is named `<profile>-<n>` and can be renamed with `/rnpc rename`. - **D242:** `/rnpc place` and `/rnpc here` take `key=value` options in any order: `count=`, `respawn=`, `mode=`, `move=` and `radius=`. It also updates §5's command table and stage 3's text and test plan, and the decision range in `README.md` and `PLAN_REDESIGNS.md` now reads D214–D242. ## Checklist - [x] AI-assisted: written with Claude Code (Claude Opus 5.5); the commit carries the trailer. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

wtclaude added 1 commit 2026-09-30 06:50:06 +00:00

docs(runicnpc): stage 3's design, D239–D242 791ac75b14

The org lead answered stage 3's four questions on 2026-09-30:

- D239: a roamer may stand on a player-built floor (Rust's mesh covers it
  a moment after it is built, stage 2), with a warning in the answer.
  §5, §8 and stage 10 now follow it; stage 2's open item is closed.
- D240: routes are recorded point by point (record, point, undo,
  save loop|back, cancel), with nothing drawn on screen.
- D241: placements made in game are named <profile>-<n>, renamable.
- D242: /rnpc place and /rnpc here take key=value options in any order.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

whitlocktech merged commit fdfd525bc4 into main

2026-09-30 06:52:57 +00:00

whitlocktech referenced this issue from a commit

2026-09-30 06:52:57 +00:00

Merge pull request 'docs(runicnpc): stage 3's design, D239–D242' (#303) from docs/runicnpc-stage3-decisions into main

whitlocktech deleted branch docs/runicnpc-stage3-decisions

2026-09-30 06:52:58 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#303