PROTOCOL.md §20.10: hello's integrations.zLevels, and nothing more
(D374). PLAN_REDESIGNS §14.3.20 records the build, two points settled in
code, the tests and the rig check; pointers from §9's summary and
§14.3.6.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
@@ -930,7 +930,7 @@ pulls) is research, not a walk, so it still comes first:
answered before code: **written on 2026-10-14 as §14.3**, from D361–D369, and answered as D370–D376. Then the
build, in §14.3.11's nine stages (two of them core), §13 first. **Stage 1, §13, was built on 2026-10-15
(§14.3.14)**, with D378 and D379. **Stage 2, core's `retryAfterMs` (MODULE_API 1.15.0), was built on
2026-10-15 (§14.3.15).** **Stage 3, TruePVE in the zone step, was built on 2026-10-15 (§14.3.16)**, and **stage 4, Dynamic PVP, the same day (§14.3.17)**, and **stage 5, Dangerous Treasures, the same day (§14.3.18)**, and **stage 6, Guarded Crate, the same day (§14.3.19).**
2026-10-15 (§14.3.15).** **Stage 3, TruePVE in the zone step, was built on 2026-10-15 (§14.3.16)**, and **stage 4, Dynamic PVP, the same day (§14.3.17)**, and **stage 5, Dangerous Treasures, the same day (§14.3.18)**, and **stage 6, Guarded Crate, the same day (§14.3.19)**, and **stage 7, ZLevels, the same day (§14.3.20).**
**Then one walk, on Oxide and Carbon, of everything still owed (D331):** §2.7; §11's rows; §12.9; §13's and
§14's rows; the in-game rows
@@ -2652,6 +2652,8 @@ dropped. D369 still holds in what remains: nothing is done at a wipe.
**Walk rows.** Lend `vip2` from a run and see the XP rate change at once, and back at the run's end.
> **Built on 2026-10-15** (§14.3.20), specified in PROTOCOL.md §20.10, as planned here.
#### 14.3.7 Server Rewards (D369)
It mirrors §11.2.2 (Economics) wherever Server Rewards allows, and the code shares Economics' path where the two
@@ -3178,6 +3180,35 @@ the sidecar and the site are §14.3.5's walk rows, at the end walk (D331, D359).
placement raising no airdrop line; `gcrate stop all` taking a crate off the map; and a crate's guards killed by
server reports Guarded Crate or a row counts one (`guardedCrate: true` on the answer).
- The map draws a running event on the world layer. Server settings' plugin line names Guarded Crate and
NpcSpawn, the events, and whether a step can place one.
### 20.10 ZLevels Remastered — hello only (§14.3.6, D369, D374)
nivex's **ZLevels Remastered** (3.3.1, uMod), optional like Economics (D199) and not in `overlay.toml`. It
levels six gathering and crafting skills. **The bridge only says whether it is loaded.** No level is read,
nothing goes on the wire for it, and the site stores nothing: the leaderboard is not changed for it (D374),
and nothing is done at a wipe (D369). The design is [`PLAN_REDESIGNS.md`](../modules/rust/PLAN_REDESIGNS.md)
§14.3.6, and the stage-7 record is §14.3.20 there.
**Hello and status.**`integrations` gains `zLevels`:
```json
"zLevels":{"loaded":true,"version":"3.3.1"}
```
Hello is sent again when ZLevels loads or unloads. `rg.world` prints `zLevels=` (its version, or `absent`).
**Its XP boosts need nothing here.** ZLevels' VIP XP multipliers are its own permissions
(`zlevelsremastered.vip1`–`vip3` as it ships, ×2–×4) and it reads them on every gain. So the site's
*Permissions until the event ends* step (`PLAN_REDESIGNS.md` §12.4) lends one, pushed in `perm.sync` like a
kit reward (§20.2), and it takes effect at once.
**The sidecar** forwards hello whole, as before; nothing in it changed.
**The website (Module-Rust).** Server settings' plugin line says whether ZLevels is loaded and, where it is,
that an event may lend its XP boosts as permissions. Nothing else reads the field.
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.