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.
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.
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).
Describe the tree check and every message declared, at bootstrap 7072554
The facts check compares each declaration's full tree with the client's, names a disagreement by opcode, side and path, and treats two pairs of indistinguishable forms as equal; 157 disagreements are pinned. Every one of the client's 1,119 messages is declared, 1,015 agreeing with the client (run 38877202011, 263 of 263; it ran the identical tree of 7072554). The layout tree's union example is now a plain test layout, no longer tied to 0x01C3.
Describe the facts table's layout trees, at bootstrap bd2ec2c
The client facts table is schema 2: every side carries the client's full layout tree, its widths come from the tree, and three client envelopes keep widths with no tree. The trees hold for both clients. The facts check still compares empty paths, at 873 agreeing and 55 pinned (run 38876037239, 252 of 252).
Describe the layout tree, at bootstrap 9f13a55
Codec-design gains the layout tree: its one-line text form, the node kinds, worked examples and how a disagreement's path is named, and the generator now emits each declared message's tree (WireLayout.TreeText and Tree, carried in WireLayoutData), held to the empty path the facts check proves. Message-audit-design marks the generator's trees built; Repository-layout and Roadmap take run 38863032351, 251 of 251.
Re-verify against bootstrap cb985d3 with the stricter verification rules
A message at Purpose needs a name of its own in place of its neutral number, and a member keeping its neutral name at Fields begins its summary with 'The client gives this value no meaning.' (run 38857101195, 224 of 224). The blame-ignore list now skips the neutral rename too.
Re-verify against bootstrap 2ee1445 at the close of the audit's first stage
The verification check reads every wire member whatever its accessibility, across all three model projects (run 38855029660, 223 of 223).
Re-verify against bootstrap 9c93c58 with the wire models under the analysers
Network.World and Network.Auth no longer opt out of the analysers, code style or nullable reference types, and nothing suppresses NTC003 or NTC006 (run 38852967763, 221 of 221). Code-standard loses three suppression rows and the nullable exception, Repository-layout its Off column and first known edge, Codec-design its NoWarn sentence; the audit's step 3 is marked done.
Re-badge every code page to bootstrap fadf745
Branches-and-workflow and Running-the-tests describe nothing the CONTRIBUTING.md change touched; the verified dates move to the day of the check.
Re-verify against bootstrap fadf745 with the verification check in
The Verified attribute and the registry verification tests are built: 927 declared messages, none read to fields, all pinned as unverified (run 38852302801, 221 of 221). Code-standard states the documentation rule for wire messages as CONTRIBUTING.md now does, with the CS1591 suppression; Repository-layout, Codec-design, Message-audit-design and Roadmap record what's built.
Name messages by opcode after the neutral rename
No old message name exists in the code since bootstrap 86b7f28, so pages name each message by its opcode and describe it only where what it does is established: milestone one's table, the crowd-control pair, the codec's example and errata, the facts check's table, the irregular shapes. House style states the rule. Re-verified against 86b7f28, run 38851638578, 215 of 215.
Add the message audit's design
A published design page for checking every message against the client before more feature work: the five rungs, the Verified attribute and its shrinking-list test, the use gate at dispatch, neutral names, the full-layout tree check, feature areas, the generated protocol reference, and the order of the work. Linked from Home, the sidebar, Codec-design, Roadmap and the systems table.
Re-verify against bootstrap c5b0774 after the old code's deletion
The converter, the equivalence harness, the frozen copy of the old models and the old packet layer are gone; the facts check is the proof that remains (run 38847142696, 215 of 215; 873 of 927 agree, 55 pinned). Codec-design compresses the conversion and its proof into a past-tense record, gives the facts check and the irregular shapes sections of their own, and lists what was retired. Repository-layout, Code-standard and Roadmap lose the deleted projects, suppressions and counts; Server-core-design stops listing the converter as a tool.
Say which client facts the wiki states, and pause step 2 for the audit
Documentation-standards gains Facts about the client: purpose, field meanings, units, ranges, value sets, table indexes and order are stated as facts; addresses, decompiled code, tool names and output, client strings and method stay off. Roadmap: stage 3 paused for an audit of every message against the client before more feature work, and why it comes before the core skeleton.
Set the documentation format for building out the core
Documentation-standards gains a system's page set (design, explanation hub, references, guides), generated reference for the code's registries, a Where the code lives table on every page with a ref badge and none on index pages, a path-based re-verify check, Home by area past twenty pages, and the three kinds of reader. Server-core-design gains the systems table that points at each system's current page. House style names messages with their opcode beside them. Home drops its ref badge; Running-the-tests, Codec-design and Roadmap gain their code tables.
Bring the core design up to one world, the gateway and public hosting
Server-core-design takes the new names (message queue, gateway, write-behind queue, AOI, conflation, handoff, TCC), one world with no layering, routing by an opcode table with priorities, rate limits and kill switches, the realm as modules, pooled and dedicated map threads, tick and update interval per instance type, sleeping cells, AOI tiers, the gateway's login exchange, the hardened client ports, the two unsent-bytes limits, the write-behind sequencer and load workers, the private pack, the portal's recovery and source link, and a Hosting section. Roadmap drops public hosting from out of scope and states one world and public hosting as goals.
Re-verify the codec pages at bootstrap 07ccf71 after more corrections
- 873 of 927 messages agree with the client facts, 55 pinned.
- Equivalence 1,155 proven, 27 through holders, 99 excluded, each new one a correction to the client.
- The facts table holds for both the 64-bit and 32-bit client of build 16042.