docs: plan Rust's world events, six optional plugins, and Steam sign-in (D349–D360) #345

Merged
whitlocktech merged 2 commits from docs/rust-native-events-optional-plugins into main 2026-10-14 10:10:50 +00:00
Member

Adds the 2026-10-14 plugin survey, the org lead's decisions and answers, and the Steam sign-in plan.

modules/rust/PLAN_REDESIGNS.md

  • §13 Rust's own world events (D349): base module, no plugin. Covers the patrol helicopter, Bradley, cargo, the Chinook, airdrops, locked crates, oil rig scientists, the Travelling Vendor, and anything newer. Hooks are named only after the test phase confirms them.
  • §14 Six optional plugins (D350): TruePVE, Dynamic PVP, Dangerous Treasures, Guarded Crate, ZLevels Remastered and Server Rewards. Duelist is left out entirely.
    • D351: as few helpers as possible (target none), and no licence trouble (never copy, modify, bundle or redistribute).
    • D352: one test phase (§14.2) on both rigs for all six plus §13, then one integration plan (§14.3), before code.
  • Answers, 2026-10-14 (D353–D359):
    • D353: public feed shows the name and grid; the staff feed adds the Steam id.
    • D354: an event can call a vanilla event, and it's 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. This went against the proposal, and §9 now says so.
  • §15 Steam sign-in (D360): a link to the website's plan, not planned here. It covers what the Rust module takes from it.
  • The header, item table, §9 (items 8, 9 and the walk) and §10's tables are updated.

website/STEAM_SIGNIN.md (new): Steam sign-in stays on the website's plan (D171)

  • A built-in provider beside Google and Discord, in the same manner as the others: link-only with opt-in sign-up, the one session service, the TOTP gate, Admin → Auth, account link and unlink, and Android through the M9 bridge.
  • How Steam's OpenID 2.0 differs from OAuth2, and the checks the adapter makes.
  • The build per repo, including MODULE_API 1.15.0, which lets a module read a user's verified Steam ids.
  • Security, tests, and Q1–Q4 for the org lead:
    • Q1: does a Steam sign-in count as a Rust link?
    • Q2: what does unlinking remove?
    • Q3: an optional Steam Web API key for names and avatars.
    • Q4: Steam sign-up with no email.
  • Roadmap: the website milestone Steam sign-in, with issue website#214.
  • Linked from the docs README, PLAN_FIXES §4.8 and PLAN_REDESIGNS §15.

Nothing is built. Next comes the §14.2 test phase, and Steam's Q1–Q4 whenever you take it up.

  • AI-assisted: written with Claude Code (Claude Opus 5.5)

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

Adds the 2026-10-14 plugin survey, the org lead's decisions and answers, and the Steam sign-in plan. ## `modules/rust/PLAN_REDESIGNS.md` - **§13 Rust's own world events (D349):** base module, no plugin. Covers the patrol helicopter, Bradley, cargo, the Chinook, airdrops, locked crates, oil rig scientists, the Travelling Vendor, and anything newer. Hooks are named only after the test phase confirms them. - **§14 Six optional plugins (D350):** TruePVE, Dynamic PVP, Dangerous Treasures, Guarded Crate, ZLevels Remastered and Server Rewards. Duelist is left out entirely. - **D351:** as few helpers as possible (target none), and no licence trouble (never copy, modify, bundle or redistribute). - **D352:** one test phase (§14.2) on both rigs for all six plus §13, then one integration plan (§14.3), before code. - **Answers, 2026-10-14 (D353–D359):** - D353: public feed shows the name and grid; the staff feed adds the Steam id. - D354: an event can call a vanilla event, and it's 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.** This went against the proposal, and §9 now says so. - **§15 Steam sign-in (D360):** a link to the website's plan, not planned here. It covers what the Rust module takes from it. - The header, item table, §9 (items 8, 9 and the walk) and §10's tables are updated. ## `website/STEAM_SIGNIN.md` (new): Steam sign-in stays on the website's plan (D171) - A built-in provider beside Google and Discord, in the same manner as the others: link-only with opt-in sign-up, the one session service, the TOTP gate, Admin → Auth, account link and unlink, and Android through the M9 bridge. - How Steam's OpenID 2.0 differs from OAuth2, and the checks the adapter makes. - The build per repo, including **MODULE_API 1.15.0**, which lets a module read a user's verified Steam ids. - Security, tests, and **Q1–Q4 for the org lead**: - Q1: does a Steam sign-in count as a Rust link? - Q2: what does unlinking remove? - Q3: an optional Steam Web API key for names and avatars. - Q4: Steam sign-up with no email. - **Roadmap:** the `website` milestone *Steam sign-in*, with issue **website#214**. - Linked from the docs README, PLAN_FIXES §4.8 and PLAN_REDESIGNS §15. Nothing is built. Next comes the §14.2 test phase, and Steam's Q1–Q4 whenever you take it up. - [x] AI-assisted: written with Claude Code (Claude Opus 5.5) 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-14 10:02:55 +00:00
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
wtclaude added 1 commit 2026-10-14 10:09:33 +00:00
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
wtclaude changed title from docs(rust): plan Rust's own world events and six more optional plugins (D349–D352) to docs: plan Rust's world events, six optional plugins, and Steam sign-in (D349–D360) 2026-10-14 10:09:43 +00:00
whitlocktech merged commit 95e81ecb54 into main 2026-10-14 10:10:50 +00:00
whitlocktech deleted branch docs/rust-native-events-optional-plugins 2026-10-14 10:10:51 +00:00
Sign in to join this conversation.
No description provided.