feat(rust): Guarded Crate — feed, map, Warden, Place a guarded crate (PLAN_REDESIGNS §14.3.5)
Stage 6 of the §14.3 integration plan, on protocol 14. Spec: docs rust-link/PROTOCOL.md §20.9. - gc.started and gc.ended public, gc.failed staff's; guardedCrate.js reads each row per viewer (the clearer's name for the presence audience, Steam id, position and key for staff, `won` for everyone). - Triggers rust.gc.started and rust.gc.ended (a crate a player cleared only). - The step rust.gc.place: an event from rust.options.gc_events and a world call's location; refused at verify for Guarded Crate absent, NpcSpawn missing (D364), console unavailable, or an unknown event. Kept (D373); the run log's success line says so (D380). Budget rust.gc.crates. - Warden (D375): guarded_won, title category guardedwon, Crates cleared column. - Map marker, server settings line, swagger, engagement manifest, bundle, README. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
@@ -135,6 +135,15 @@ one now, kept when the run ends: an airdrop or a patrol helicopter can be sent t
|
||||
ten minutes after DT loads the step says "Dangerous Treasures is not ready yet" and tries again ten
|
||||
minutes later. Refused where DT is absent, or where the framework cannot run DT's console command
|
||||
(`docs/modules/rust/PLAN_REDESIGNS.md` §14.3.4).
|
||||
- **Guarded Crate** (Bazz3l, 2.0.17), with **NpcSpawn** (Codefling) for its guards. With both: a
|
||||
guarded crate landing and being cleared are public feed lines and triggers (*"Alice cleared the
|
||||
guarded crate · M4"*, the name only for the presence audience), a running crate is on the live map's
|
||||
world layer, the **Crates cleared** leaderboard column and the *Warden* title count the crates a
|
||||
player cleared by killing the last guard, and the step **Place a guarded crate** places one of its
|
||||
events at a monument or a point. The crate is kept when the run ends — Guarded Crate cannot end one
|
||||
alone — and the run log says so. Refused where Guarded Crate or NpcSpawn is absent, where the event
|
||||
is not one the server has, or where the framework cannot run its console command
|
||||
(`docs/modules/rust/PLAN_REDESIGNS.md` §14.3.5).
|
||||
|
||||
News and event lines said in chat can wear one styled group's title and colours — the
|
||||
**announcement voice**, chosen in Admin → Rust servers. The line is said by the bridge plugin with no
|
||||
|
||||
Reference in New Issue
Block a user