docs(runicnpc): stage 5 decisions D253–D262 #309

wtclaude · 2026-10-01T04:05:49Z

wtclaude commented

2026-10-01 04:05:49 +00:00

What

These are your answers of 2026-09-30 for RunicNPC stage 5 (behaviour), recorded in runicnpc/PLAN.md §0. §6 and the stage 5 section now follow them.

#	Decision
D253	One stage, walked once end to end. It opens with the D231 spike, and its wire changes join protocol 13 while that is unreleased (as D248)
D254	Named factions (`bandits`, plus the built-in `scientists` and `animals`), and per-profile exceptions that win over the faction's relations
D255	With no faction settings, a profile fights players only. NPC and animal targets are opt-in
D256	Group alert: allies within the alert radius join the fight (40 m by default, 0 turns it off)
D257	An NPC allied to a clan or Rust team never targets its members, and defends them and what they own
D258	An escort's target comes from an event step, the API, or `/rnpc follow <placement> <player>`. Placements never escort on their own
D259	Turrets treat our NPC as they treat Rust's scientists, and it shoots back. Per profile: `default`, `ignore` or `always`
D260	Kit extras (syringes, grenades, melee, rockets, flamethrowers) are opt-in per profile, and items used are consumed
D261	TruePVE and NextGenPVE allow damage both ways for our NPCs, with a per-profile opt-out
D262	A patrol that leaves its route to fight returns to the point it was heading to

The stage 5 section now lists what the spike measures and what each repository gets: RunicNPC API 4, the bridge, Module-Rust.

One thing to check: D253's "joins protocol 13 while it is unreleased" is my reading of D248's rule. Say so if stage 5 should bump to 14 instead.

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 These are your answers of 2026-09-30 for RunicNPC stage 5 (behaviour), recorded in `runicnpc/PLAN.md` §0. §6 and the stage 5 section now follow them. | # | Decision | |---|---| | D253 | One stage, walked once end to end. It opens with the D231 spike, and its wire changes join protocol 13 while that is unreleased (as D248) | | D254 | Named factions (`bandits`, plus the built-in `scientists` and `animals`), and per-profile exceptions that win over the faction's relations | | D255 | With no faction settings, a profile fights players only. NPC and animal targets are opt-in | | D256 | Group alert: allies within the alert radius join the fight (40 m by default, 0 turns it off) | | D257 | An NPC allied to a clan or Rust team never targets its members, and defends them and what they own | | D258 | An escort's target comes from an event step, the API, or `/rnpc follow <placement> <player>`. Placements never escort on their own | | D259 | Turrets treat our NPC as they treat Rust's scientists, and it shoots back. Per profile: `default`, `ignore` or `always` | | D260 | Kit extras (syringes, grenades, melee, rockets, flamethrowers) are opt-in per profile, and items used are consumed | | D261 | TruePVE and NextGenPVE allow damage both ways for our NPCs, with a per-profile opt-out | | D262 | A patrol that leaves its route to fight returns to the point it was heading to | The stage 5 section now lists what the spike measures and what each repository gets: RunicNPC API 4, the bridge, Module-Rust. **One thing to check:** D253's "joins protocol 13 while it is unreleased" is my reading of D248's rule. Say so if stage 5 should bump to 14 instead. ## 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-01 04:05:52 +00:00

docs(runicnpc): stage 5 decisions D253-D262 f899834453

The org lead's answers of 2026-09-30 for stage 5 (behaviour): one stage
walked once, opening with the D231 spike; named factions with per-profile
exceptions; players-only by default; group alert at 40 m; clan and team
allies defended; escort targets from events, the API and /rnpc follow;
turrets as for Rust's scientists; kit extras opt-in; PVE hooks allowed both
ways; a patrol returns to the point it was heading to.

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

whitlocktech merged commit c28a688b03 into main

2026-10-01 04:10:13 +00:00

whitlocktech deleted branch docs/runicnpc-stage5-decisions

2026-10-01 04:10:13 +00:00

whitlocktech referenced this issue from a commit

2026-10-01 04:10:14 +00:00

Merge pull request 'docs(runicnpc): stage 5 decisions D253–D262' (#309) from docs/runicnpc-stage5-decisions into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#309