feat(bridge): protocol 7 — a raid frame that names who lives there #7
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/phase-10-engagement"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What & why
Protocol 7 for phase 10's raid alert (
docs/modules/rust/PLAN.md§25,docs/rust-link/PROTOCOL.md§13).entity.destroyednow covers doors, external walls and gates, and the tool cupboard. A door is anAnimatedBuildingBlock, a sibling ofBuildingBlock, so until now a door-only raid reached nobody. The frame gains:structure;buildingId;authorized([{steamId, online}], bounded at 64).Both new fields are absent when there's no cupboard.
recentGroupMembersis deliberately not read: it's upkeep accounting, not authorisation. Thestructurestally still counts building blocks only.attackerIdis derived fromuserID.UserIDStringis unset for a player another plugin spawned, and the website's self-demolish exclusion depends on this field.clan.disbandedcarriesmembers. The board that follows the event can remove the roster before the website reads the disband.overlay.tomlprotocol → 7.How it was tested
node scripts/checkPlugin.js: protocol 7, 29 hooks, all void and listed.OnEntityDeathdispatched to the bridge with no exception. That rig has no sidecar, so the frame wasn't read back.Checklist
AI-assisted contributions (required)
Claude Code (Claude Opus 5.5). AI-authored commits carry aCo-Authored-Bytrailer.License
🤖 Generated with Claude Code
https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY