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

docs(rust): say which half of the step-2 walk rows was walked

Browse Source 
Rows 1-2 of PLAYER_WALK's step-2 section had their game side walked on both
rigs; their site side (the servers-page warning, a grant landing within a
minute) needs a walk core running Module-Rust#22 on website#209, which the
first commit claimed as walked.

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-26 21:48:18 -05:00
parent 1a7f52743f
commit a199823513
2 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
modules/rust/PLAN_FIXES.md
View File

@@ -399,9 +399,9 @@ in Rust-Plugins, Rust-Link and Module-Rust, and the three cut over to `main` tog
installer#35 and website#209 (core's `expired` status, MODULE_API 1.11.0). The spec is installer#35 and website#209 (core's `expired` status, MODULE_API 1.11.0). The spec is
[`PROTOCOL.md`](../../rust-link/PROTOCOL.md) §19.4–19.8. Walked on both rigs without a player: the [`PROTOCOL.md`](../../rust-link/PROTOCOL.md) §19.4–19.8. Walked on both rigs without a player: the
bridge and the ZoneManager helper compile and load, the helper patches ZoneManager 3.1.14, the hello bridge and the ZoneManager helper compile and load, the helper patches ZoneManager 3.1.14, the hello
carries its state, and `plugin.loaded` / `plugin.unloaded` carry the right permissions. The rows that carries its state, and `plugin.loaded` / `plugin.unloaded` carry the right permissions. Still to walk:
need somebody in the game are [`PLAYER_WALK.md`](../../rust-link/PLAYER_WALK.md)'s step-2 section, the site side (a walk core running Module-Rust#22 on website#209), and the rows of
rows 3–9. [`PLAYER_WALK.md`](../../rust-link/PLAYER_WALK.md)'s step-2 section that need somebody in the game (3–9).
3. **The redesigns**, each planned in detail before code and walked on both frameworks: the permission manager 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 (§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). marker types (§4.5), the chat title conditions (§4.6), and the NPC research (§4.7).

6
rust-link/PLAYER_WALK.md
View File

@@ -412,8 +412,10 @@ without a sender, and a popup appears on a real screen.
Added 2026-09-27. What [`PLAN_FIXES.md`](../modules/rust/PLAN_FIXES.md) §8 asks the re-walk to show for Added 2026-09-27. What [`PLAN_FIXES.md`](../modules/rust/PLAN_FIXES.md) §8 asks the re-walk to show for
step 2's fixes, in the order they are quickest to walk. Player A from the walks above; a staff member step 2's fixes, in the order they are quickest to walk. Player A from the walks above; a staff member
at the website. **Run it on Oxide and on Carbon.** Rows marked *no player* were walked on both rigs on at the website. **Run it on Oxide and on Carbon.** Rows marked *no player* need nobody in the game.
2026-09-27 without one; the rest need somebody in the game. Their game side was walked on both rigs on 2026-09-27 (the helper patched, the hello carried its state,
the load frames carried Kits' permissions); their site side waits for a walk core running Module-Rust#22 on
website#209. The rest need somebody in the game.
| # | Do this | You should see | | # | Do this | You should see |
|---|---|---| |---|---|---|