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

docs(rust): plan the six step-3 redesigns in one document

Browse Source 
PLAN_REDESIGNS.md plans PLAN_FIXES §6 step 3 in detail, before any code:
the permission manager, the event step editor and kit weekend, zones and
domes, map marker types, the 23 title conditions, and NPCs. Checked on
both rigs first: the public owner lookup for permissions, the mission
hooks both frameworks already raise, and ZoneDomes' null-player throw.
Eleven questions for the org lead (§10) become D188 onward.

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:45:44 -05:00
parent 180d6a85d9
commit a430666f94
3 changed files with 534 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
modules/rust/PLAN_FIXES.md
View File

@@ -428,6 +428,8 @@ in Rust-Plugins, Rust-Link and Module-Rust, and the three cut over to `main` tog
3. **The redesigns**, each planned in detail before code and walked on both frameworks: the permission manager
(§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.
4. **The cutover**, once the re-walk (§8) passes on Oxide and Carbon.
## 7. Helper plugins (D168)
@@ -464,7 +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:
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.
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).