docs(runicnpc): stage 2 as built, and API.md #302

wtclaude · 2026-09-30T06:32:00Z

wtclaude commented

2026-09-30 06:32:00 +00:00

What

This PR records stage 2 as built (runicnpc-rust#4) on both rigs.

runicnpc/API.md (new): the reference for other plugins at API version 2. It covers owners, every RunicNpc_* call and what it refuses, the four hooks it raises, the profile, placement and route shapes field by field, and the files and config.
runicnpc/PLAN.md §9, stage 2: the results table (every group passed on Oxide and Carbon, and again after a plugin reload and a server restart), and what building it found.
README.md: indexes API.md, and the plan's decision range now reads D214–D238.

Two findings

Outside a monument, Rust's scientists never chase. Rust's chase state errors without an AI zone's move points, just as its roam does (stage 1, Q3). wander and route roamers therefore have our own chase: it stops at the profile's chase range from home, and if the target stays out of reach there for 5 s, the NPC gives up and walks home. This is how the approved "roamers chase and fight" was implemented. It is not a new decision.
Rust's navmesh covers a new player-built floor within 0.1–0.3 s (2–3 frames) on both rigs. Stage 1's Q4 read "not on the mesh" in the same frame the floor spawned. Its table now carries the correction.

Open for the org lead

§5's sentry rule, §8 and stage 10 were written on stage 1's reading, that players' bases are off the mesh. Roamers can in fact stand on a player-built floor a moment after it is placed, so bases may not need a custom navmesh at all. I have not changed those sections; they wait on your call.

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 PR records stage 2 as built (runicnpc-rust#4) on both rigs. - **`runicnpc/API.md` (new):** the reference for other plugins at API version 2. It covers owners, every `RunicNpc_*` call and what it refuses, the four hooks it raises, the profile, placement and route shapes field by field, and the files and config. - **`runicnpc/PLAN.md` §9, stage 2:** the results table (every group passed on Oxide and Carbon, and again after a plugin reload and a server restart), and what building it found. - **`README.md`:** indexes API.md, and the plan's decision range now reads D214–D238. ## Two findings 1. **Outside a monument, Rust's scientists never chase.** Rust's chase state errors without an AI zone's move points, just as its roam does (stage 1, Q3). `wander` and `route` roamers therefore have our own chase: it stops at the profile's chase range from home, and if the target stays out of reach there for 5 s, the NPC gives up and walks home. This is how the approved "roamers chase and fight" was implemented. It is not a new decision. 2. **Rust's navmesh covers a new player-built floor within 0.1–0.3 s** (2–3 frames) on both rigs. Stage 1's Q4 read "not on the mesh" in the same frame the floor spawned. Its table now carries the correction. ## Open for the org lead - **§5's sentry rule, §8 and stage 10 were written on stage 1's reading**, that players' bases are off the mesh. Roamers can in fact stand on a player-built floor a moment after it is placed, so bases may not need a custom navmesh at all. I have not changed those sections; they wait on your call. ## 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:32:02 +00:00

docs(runicnpc): stage 2 as built, and API.md 1e00c5da6e

runicnpc/API.md is the reference for other plugins: owners, every
RunicNpc_* call, the four hooks, and the profile, placement and route
shapes. PLAN.md records stage 2's results on both rigs and what building it
found: Rust's chase needs an AI zone like its roam, and a player-built floor
joins the navmesh 0.1-0.3 s after it spawns, which corrects stage 1's Q4
(left open for the org lead). README indexes API.md.

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

whitlocktech merged commit 3f358bba76 into main

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

whitlocktech deleted branch docs/runicnpc-stage2

2026-09-30 06:40:51 +00:00

whitlocktech referenced this issue from a commit

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

Merge pull request 'docs(runicnpc): stage 2 as built, and API.md' (#302) from docs/runicnpc-stage2 into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#302