docs(runicnpc): plan RunicNPC, our own Rust NPC plugin (D214-D220)
The PLAN_REDESIGNS §6 spike ran on the Oxide rig on 2026-09-30. Route A kept its kit and fought with it but cannot be named; HumanNPC counted its NPCs as players in the killfeed and tallies; NpcSpawn worked but costs a boot hitch, a phone-home and an unbundleable dependency. The org lead chose to write our own API-style plugin in runicnpc-rust. runicnpc/PLAN.md records the spike, the decisions, the features, the API, the chat commands, and stages 0-10 with how each is tested, plus eight questions. PLAN_REDESIGNS §6, §9 and §10 point at it; the index lists it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
11
README.md
11
README.md
@@ -11,6 +11,7 @@ website/ docs from the website core (Node/Express + MariaDB + React/Vite)
|
||||
modules/ docs for installable game modules — one directory per module id
|
||||
link/ docs from the ServUO bridge (C# plugin + Rust sidecar + Node WS)
|
||||
rust-link/ docs from the Rust bridge (Oxide plugin + Rust sidecar)
|
||||
runicnpc/ docs for RunicNPC, the Rust NPC plugin (runicnpc-rust)
|
||||
android/ docs from the native Android client (Kotlin + Jetpack Compose)
|
||||
installer/ docs for the installer that deploys a shard's bridge components
|
||||
ci/ cross-cutting CI/quality notes
|
||||
@@ -89,6 +90,16 @@ share a shape and nothing else, so neither document is a fallback for the other.
|
||||
| [INTEGRATION.md](rust-link/INTEGRATION.md) | Standing the bridge up by hand, and which of the three components is wrong when it does not work |
|
||||
| [PLAYER_WALK.md](rust-link/PLAYER_WALK.md) | The half of the read path a console cannot reach: ten minutes on a rig with a player, step by step, with what each hook should produce |
|
||||
|
||||
### `runicnpc/`
|
||||
|
||||
RunicNPC, Runic Gateway's own NPC plugin for Rust (Oxide and Carbon), in its own repository. Admins place NPCs
|
||||
with it in game, events place them through the bridge, and other plugins drive it through its API. `module-rust`
|
||||
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–D220, the features, the API, the chat commands, and stages 0–10 with how each is tested |
|
||||
|
||||
### `android/`
|
||||
| Doc | What it covers |
|
||||
|---|---|
|
||||
|
||||
Reference in New Issue
Block a user