docs(runicnpc): stage 3's design, D239–D242
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
This commit is contained in:
@@ -98,7 +98,7 @@ requires it once it releases (D220).
|
||||
|
||||
| Doc | What it covers |
|
||||
|---|---|
|
||||
| [PLAN.md](runicnpc/PLAN.md) | **The plan** — what the 2026-09-30 spike found (route A, HumanNPC, NpcSpawn), the org lead's decisions D214–D238, the features, the API, the chat commands, and stages 0–10 with how each is tested and what each found |
|
||||
| [PLAN.md](runicnpc/PLAN.md) | **The plan** — what the 2026-09-30 spike found (route A, HumanNPC, NpcSpawn), the org lead's decisions D214–D242, the features, the API, the chat commands, and stages 0–10 with how each is tested and what each found |
|
||||
| [API.md](runicnpc/API.md) | **The API** other plugins call (version 2): owners, every `RunicNpc_*` call, the hooks it raises, and the profile, placement and route shapes |
|
||||
|
||||
### `android/`
|
||||
|
||||
Reference in New Issue
Block a user