Split the owners into their system page, references and what's left - Owners explains one thread over one queue, the two built owners and why; Owners base, account and realm carry the facts, checked against bootstrap c3409ba - Owners design keeps only what isn't built: the map owners, the hand-off, the protocols and the realm's modules
Hold today's design pages to the house style - Name the map's messages by opcode beside their names - Keep Map scheduler design's summary to three sentences - Narrow Gateway design's diagram to three nodes
Regenerate the reference with logout read, bootstrap c3409ba - LogoutRequest and LogoutConfirm at Fields, LogoutCountdown at Purpose - Client protocol's Leaving section gains the logout steps, and Owners design the map's side of them - Counts from run 39100555948: 53 read to fields, 1,066 unverified, 742 of 742
Design the map side from the approved Stage 2a plan - Map scheduler design and Timer wheel design, moved out of Server core design with the plan's rulings - Owners design gains the map owners, the hand back and the second login; Gateway design locks tagged routing - Harness design gains stepped maps and the world scenarios - The handling gate by verified members (decided 2026-10-18) on Message audit design, Gateway design and Roadmap
Document step 3's first stage as built, at bootstrap e8da4aa The real client logs in through our own server and creates a character. Host, Gateway, Owners, Persistence, Command layer and Harness each get an explanation page checked against the merged code, and Running a server is the guide to running it. The six design pages say their first stage is built and stay the direction for the rest. Repository layout, Running the tests, Roadmap, Client protocol and Server core design catch up; Home groups pages by area now the wiki is past twenty. Counts from run 39083384598: 718 tests in 13 applications.
Record the user's calls on tiers, starting zones and two protocols Distance tiers set their own offsets, since the client plays each entity's keys at their own timestamps, and a tier change must reset the entity's time. The four classic starting zones stay one shared map each; copies of 20 are rejected. P8 and P9 carry account-wide friends and presence to the realm, and account grants to the map holding the character.
Record the client facts checked again for the map side Server core design marks four client facts as re-checked to two readings, labels the movement correction recipe as inferred, and says the client keeps an interval set in one world until the next world's WorldSettings. Owners design no longer claims seven protocols cover every flow: two rare ones, account to realm and account to map, are open. Roadmap's 0x025E row says its lists can start empty.
Document TaggedMessage and correct which messages travel tagged 0x038C is TaggedMessage, verified to its fields: one message under a tag fixed by its opcode. The client sends tagged messages before the world as well as in it, and sends others on their own, so pregame isn't untagged as the pages said. What each tag stands for is our reading, not yet verified. Counts from run 39006780626: 48 read to fields, 1,071 unverified.
Move step 3's first systems onto design pages of their own Step 3's first stage is approved and being built, so the host, gateway, owners, persistence, command layer and harness get their own design pages, moved off Server core design with their knobs and rejected ideas, and filled in from the stage's plan. The map scheduler and timer wheel stay until the map side is planned. Home, the sidebar and Roadmap's step 3 point at them.