The org lead answered §13's and §14's questions on 2026-10-14:
D353 public feed with name and grid, staff adds the Steam id; D354 an
event can call a vanilla event, kept at teardown; D355 every world event
is a trigger; D356 Safecracker and Scavenger; D357 protocol 14; D358
BotReSpawn stays out; D359 the end walk waits for RaidableBases (against
the proposal), recorded in §9 too.
D360: Steam sign-in in the same manner as Google and Discord, kept on
the website's plan (D171). New website/STEAM_SIGNIN.md (OpenID 2.0
adapter, the build per repo, security, tests, Q1-Q4), indexed in the
README, linked from PLAN_REDESIGNS §15 and PLAN_FIXES §4.8, and on the
roadmap as the website milestone "Steam sign-in" (website#214).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
PLAN_REDESIGNS gains two sections from the 2026-10-14 plugin survey:
- §13: the patrol helicopter, Bradley, cargo, the Chinook, airdrops and
locked crates reach the feed and the event system in the base module
(D349). What exists today, the proposed events, and Q12-Q16 (feed
audience, a step that calls one, triggers, new counts, protocol).
- §14: TruePVE, Dynamic PVP, Dangerous Treasures, Guarded Crate, ZLevels
and Server Rewards as first-class optional plugins (D350), Duelist left
out. D351: as few helpers as possible, nothing that runs afoul of a
licence. D352: one test phase for all of them on both rigs (§14.2),
then one integration plan (§14.3). The routes read from each plugin's
current source, what is not included and why, and Q17-Q18 (BotReSpawn,
whether the end walk waits for RaidableBases).
The header, the item table, §9's build order and the end walk, and §10's
decisions table follow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
