jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Tighten route-mode ladder docs

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-06 20:36:20 -07:00
commit d783822b1c
2 changed files with 17 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/atlas/multiplayer.md
View file

@ -205,7 +205,14 @@ Highest-value open edge:
wrappers `0x591480` and `0x591510`, but still no dedicated semantic reader has been recovered.
So the main remaining uncertainty is the exact higher-level meaning of header bit
`[descriptor+0x15] & 0x1`, plus whether `[descriptor+0x10]` ever matters outside that
preservation path. The route-event dispatcher side is cleaner too:
preservation path. The route-mode setter is clearer too: `0x595650` now reads as a compact
state machine over the transport-owned route tables, where mode `0` splits the `gsi_am_rating`
branch into direct primary-endpoint handling versus queued insertion, mode `1` adds the ready-bit
gate and the same queued fallback, mode `2` removes pending descriptors from the queued family,
mode `3` forces mode `2` when the primary-endpoint table is empty, mode `4` updates the deferred
route-status state around `[this+0x1ed4]` and `[this+0x1ed8]`, and mode `5` copies the staged
route companion dword at `[this+0x490]` into `[this+0x54]` while mirroring that value into the
local field-cache family. The route-event dispatcher side is cleaner too:
the mode-`5` tails in both callback families do not copy a descriptor-local field. They mirror the
transport-staged companion dword at `[this+0x490]` into `[this+0x54]` and the local field-cache
family instead. The `gsi_am_rating` maintenance lane is tighter now too: it sorts the