docs(runicnpc): stage 6 spike questions answered, D283–D284 #315

Merged
whitlocktech merged 1 commits from docs/runicnpc-stage6-spike into main 2026-10-05 15:19:31 +00:00
Member

What

Your answers of 2026-10-05 to the two questions docs#314 raised. docs#314 was merged before this commit reached it.

# Decision
D283 RunicNPC keeps // Requires: Kits. A Kits reload reloads RunicNPC and loses the NPCs it had spawned; placements respawn, an event's NPCs do not. The operator documentation (stage 9) says not to reload Kits while an event runs.
D284 The four example kits are written only on the first install, behind a flag in RunicNPC's data, and are never restored or overwritten afterwards.

Proposed with D284; merging this PR approves them:

  • the kit names rnpc_raider, rnpc_campguard, rnpc_sniper and rnpc_juggernaut;
  • RequiredPermission: runicnpc.examplekits, which nobody is granted, so players can't claim the kits by typing their names;
  • the first-install order: write the kits, set the flag, reload Kits. The reload takes RunicNPC down once (D283), the flag stops a second write, and nothing has spawned yet.

Changed in runicnpc/PLAN.md: the decisions table (§0), the status line, and stage 6's questions block, now marked answered.

Checklist

  • I have read CONTRIBUTING.md.
  • Docs only.
  • AI tools were used. Tool(s): Claude Code (Claude Opus 5.5). The commit carries the Co-Authored-By trailer.
  • I agree that my contribution is licensed under GPL-3.0-or-later.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What Your answers of 2026-10-05 to the two questions docs#314 raised. docs#314 was merged before this commit reached it. | # | Decision | |---|---| | D283 | RunicNPC keeps `// Requires: Kits`. A Kits reload reloads RunicNPC and loses the NPCs it had spawned; placements respawn, an event's NPCs do not. The operator documentation (stage 9) says not to reload Kits while an event runs. | | D284 | The four example kits are written only on the first install, behind a flag in RunicNPC's data, and are never restored or overwritten afterwards. | Proposed with D284; merging this PR approves them: - the kit names `rnpc_raider`, `rnpc_campguard`, `rnpc_sniper` and `rnpc_juggernaut`; - `RequiredPermission: runicnpc.examplekits`, which nobody is granted, so players can't claim the kits by typing their names; - the first-install order: write the kits, set the flag, reload Kits. The reload takes RunicNPC down once (D283), the flag stops a second write, and nothing has spawned yet. Changed in `runicnpc/PLAN.md`: the decisions table (§0), the status line, and stage 6's questions block, now marked answered. ## Checklist - [x] I have read CONTRIBUTING.md. - [x] Docs only. - [x] AI tools were used. Tool(s): `Claude Code (Claude Opus 5.5)`. The commit carries the `Co-Authored-By` trailer. - [x] I agree that my contribution is licensed under GPL-3.0-or-later. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-05 14:28:52 +00:00
D283: RunicNPC keeps "// Requires: Kits"; a Kits reload reloads it and
its spawned NPCs are lost, so operators are told not to reload Kits
during an event. D284: the four example kits are written only on the
first install, behind a flag, and never restored or overwritten.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
whitlocktech merged commit 64f6e019cf into main 2026-10-05 15:19:31 +00:00
whitlocktech deleted branch docs/runicnpc-stage6-spike 2026-10-05 15:19:31 +00:00
Sign in to join this conversation.
No description provided.