RunicGateway/docs
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(rust): record the org lead's answers to the step-3 plan (D188-D198)

Browse Source 
Groups are per server unless an admin shares them (D189); an in-game
change affects that server only, as an exception or a split (D190);
ZoneDomes stays, made safe by a domes helper (D194); presets are the
admins' own (D195); zone and reward messages get the popup choice
(D193); the NPC spike tries both routes (D197). The rest confirm the
plan: D188, D191, D192, D196, D198.

Refs RunicGateway/Module-Rust#21

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
claude
2026-09-27 03:56:43 -05:00
parent a430666f94
commit fa53526079
2 changed files with 155 additions and 111 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
modules/rust/PLAN_FIXES.md
View File

@@ -429,7 +429,7 @@ in Rust-Plugins, Rust-Link and Module-Rust, and the three cut over to `main` tog
(§4.1), the event step editor with the kit-weekend template (§4.2, §4.3), zones and domes (§4.4), the map's
marker types (§4.5), the chat title conditions (§4.6), and the NPC research (§4.7).
*Planned 2026-09-27:* all six are in one document, [`PLAN_REDESIGNS.md`](PLAN_REDESIGNS.md), as the org
lead chose. Its eleven questions (§10) are answered before any code.
lead chose. Its eleven questions were answered the same day as D188–D198 (its §10).
4. **The cutover**, once the re-walk (§8) passes on Oxide and Carbon.
## 7. Helper plugins (D168)
@@ -466,9 +466,9 @@ The four questions this plan first asked were answered on 2026-09-26: the gate (
(D171) and the title conditions (D172) — then quests (D173), the title rules (D174) and admin-owned title names
(D175).
Left for the detailed plans of §6 step 3, none of them blocking the fixes. Each is answered, or turned into a
question, in [`PLAN_REDESIGNS.md`](PLAN_REDESIGNS.md): 1 by a framework hook (its §0.4), 2 as Q9, 3 on the rig
(§3.2), and 4 as Q10.
Left for the detailed plans of §6 step 3, none of them blocking the fixes. Each is settled in
[`PLAN_REDESIGNS.md`](PLAN_REDESIGNS.md): 1 by a framework hook (its §0.4), 2 by D196, 3 on the rig during the
build (§3.2), and 4 by a spike of both routes (D197).
1. How a completed mission is detected — the spike in §4.6 (D173).
2. Whether the plugin or the site filters monument types (§4.5).