Re-date Documentation standards after its client-identifier change
Allow the client's identifiers where it ships them in plain view A table or column name, or a value its tables or public add-on interface name, may be used where a verified declaration needs it. Interface and script text, names found only inside the executable, and whole name tables stay off. The example client fact is now one the audit has verified.
Route the overview diagram by opcode rows The gateway's arrows name the opcode table's rows, not the client's tags, and the account owner's P8 and P5/P9 links to the realm and maps show.
Document PlayerState at purpose, bootstrap 48bb36d 0x025E is PlayerState, verified to its purpose: the player's own values, kept apart from the unit, which the client doesn't need to finish entering the world. Roadmap no longer says it carries items and abilities. Reference pages regenerated; counts unchanged, run 39061867784.
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.
State the rule for the zone change on takeover A mark on the unit the client last moved decides whether a takeover of the player's unit sends a ZoneChange; after a MovementControlEnd is the usual case, not the rule.
Document the movement messages at bootstrap 1b7e100 Taking control, ending it and the zone change are verified to their fields, and the movement messages to their purpose. Client protocol walks the receipt, the zone change and movement after a grant; MovementInterval is the period of the client's movement timer, not how often it sends. 0x0635 is client to server only. Counts from run 39057431917: 51 read to fields, 1,068 unverified.
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.
Name the core's pattern and open three design questions In short now says the owners are hand-built actors around a game loop and entities are composed from components, not an ECS. Open questions gain visibility beyond distance (stealth, phasing), instance lockouts, and world sockets for dynamic events.
Name the forms behind the c136cc7 count line The line pointed at "the last two forms above", and one of them is now part of the same-bits rule.
Compare the same bits on every path, at bootstrap cb7a9f0 The facts check now accepts a run of fields split differently from the client's when the totals meet and nothing depends on the split, and fails a message at fields that splits a value the client reads whole. 1,087 agree and 43 are pinned. Codec design and Message audit design carry the rule and the gate; counts from run 39054474869, 318 tests.
Document UnitCreate's members and PlayerUnit's faction refusal The reference pages are regenerated at bootstrap 7e90db0 with UnitCreate's members, stats and type arms documented. Client protocol and Roadmap say a PlayerUnit refused for a missing base faction still sets the player, so the client refuses every later one. Counts unchanged, run 39049099887.
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.
Document UnitCreate at purpose, bootstrap c136cc7 0x0262 is UnitCreate, verified to its purpose. The facts check treats two more pairs of forms as the same bits, which with three corrected arms settles 48 pins: 1,030 agree and 104 are pinned. The reference pages are regenerated; counts from run 39003475287, 289 tests.
Correct the player's own data and the movement interval 0x025E is never a stub: most of the client's interface waits for it, and it's the only way items, abilities, currencies and experience arrive. The interval in WorldSettings sets how often the client sends its own movement; whether it plays out others at it is now an open question. Roadmap names the audit's path to milestone one and the account messages character select may need.
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.
Document LoginRequest at fields, bootstrap f1e5c15 LoginRequest is verified to its fields, so pregame has 41 of its 42. The reference pages are regenerated, which also corrects how many strings a realm notice carries. Client protocol says what the login request holds and drops its own trust row; counts from run 38973272246: 47 read to fields, 1,072 unverified.
Document world entry at bootstrap 7c68ecc Six world-entry messages verified to their fields: the reference pages regenerated, Client protocol follows the conversation to the end of the loading screen, and Roadmap's milestone one table takes their names and the client's WorldReady. Counts from run 38972717843: 273 tests, 46 read to fields, 1,073 unverified. Repository layout carries the reference tool's two new tests.
Publish the generated message reference at bootstrap 58cb3ba Messages and a page per area, generated by Tools/NexusTomorrow.ProtocolReference at 58cb3ba: 1,119 messages on 40 pages. Home, the sidebar, Client protocol, Codec design and Message audit design link it. Repository layout gains the Tools folder, the generator and its tests; the counts move to 271 tests in six applications. Code pages re-verified against 58cb3ba, run 38964363277.
List a generated set through its own index The message reference will run to an index and one page per area; Home and the sidebar list the index, which lists the rest.
Record the build reorder: step 2 closed, the audit alongside step 3 The codec's third stage closed after its review at c6b56e9, and the core skeleton starts on the messages already verified rather than after the whole audit, so the project can stop depending on the old server; milestone one's messages are checked first and the rest alongside the build. Roadmap marks step 2 done and step 3's pregame stage planned and waiting on review; the audit page records decision 2's change with its reason; Codec-design closes stage 3.
Re-verify against bootstrap c6b56e9, pins that carry their problem Each facts-check pin records the exact problem it covers, and the check fails when that text changes (run 38955532713, 263 of 263; counts unchanged).
Add Client protocol, the pregame conversation as far as it's verified An explanation page for how the 16042 client talks to a server: its three connections, the envelopes and keys, the greeting's build and protocol checks, and the pregame conversation from logging in through character select, realm select and transfers to entering the world, named by the verified declarations. Sign-on is labelled as carried over from the old code. Linked from Home, the sidebar, Roadmap and the audit page.
Record pregame done for milestone one, at bootstrap b9b7eea Character creation reaches Fields: 40 of pregame's 42 messages are verified to their fields (run 38939303230, 263 of 263; 40 read to fields, 1,079 unverified). LoginRequest stays at Purpose and 0x03EF unverified. Roadmap names milestone one's next areas.
Record the character list and world entry at Fields, at bootstrap 585b32a Pregame has 39 messages verified to their fields (run 38935110817, 263 of 263; 39 read to fields, 1,080 unverified); two stay at Purpose. EnterWorld's three floats are a point the world loads around, not the character's position, so milestone one's table says so.
Record pregame's value sets, 36 messages at Fields, at bootstrap 25218fd Checking the values the client's interface names raised twelve pregame messages to Fields; five stay at Purpose until both readings agree on their last fields (run 38925236863, 263 of 263; 36 read to fields, 1,083 unverified). The audit page states the rule for naming a value.
Correct the cross-build agreement after the facts table's fix The two clients' trees agree on 1,145 of 1,154 sides: correcting ten rows exposed a union in 0x098B, where the builds differ in one arm as well as in the two out-of-range selector values.
Publish the first verified area, pregame, at bootstrap cd601a0 41 pregame messages carry the names the client check gave them, 24 verified to their fields; the facts table corrected ten of its own rows, so 1,022 messages agree and 152 disagreements are pinned (run 38915570345, 263 of 263). Roadmap names EnterWorld in milestone one's table, Repository-layout and Codec-design name the shared and envelope messages, and the audit page states the two-reading rule and the progress line.
Re-verify against bootstrap 64dba89 at the close of the audit's full-layout step CI gains a method-words check beside the em dash scan; Code-standard, Repository-layout, Running-the-tests and Branches-and-workflow list it. Message-audit-design marks the full-layout step done after its review (run 38879621476, 263 of 263; 1,015 of 1,119 agree, 157 pinned, none verified yet).
Call another project a game server, not an emulator