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

Split post-load chairman and subtype latch branches

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 12:44:39 -07:00
commit 15643a6df6
3 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/control-loop-atlas/post-load-generation-paintterrain-and-save-load-restore.md
View file

@ -797,6 +797,12 @@ The same brush strip is tighter now too:
`[region+0x27a/+0x27e/+0x282/+0x286]` through `0x00422900`. So these post-load branches stay
ruled down as setup and cache-maintenance work rather than the missing restore-time republisher
for `[region+0x2a4]` or `[region+0x310/+0x338/+0x360]`.
The surrounding `319` helpers are narrower in the same negative way now too: `0x00437220` and
`0x004377a0` stay on chairman-slot selector and profile materialization over
`[world+0x69d8/+0x69db]` and scenario selector bytes `[0x006cec7c+0x87]`, while `0x00434d40`
only seeds the subtype-`2` candidate runtime latch `[candidate+0x7b0]` across live placed
structures. That leaves the placed-structure replay strip `0x004133b0` as the only region-
adjacent bridge inside the `319` plateau worth chasing for the missing restore seam.
The
editor-side read path is explicit on the same seam:
`map_editor_economic_cost_panel_refresh_preview_curve_and_numeric_rows` `0x004caaf0` reads the

6
docs/rehost-queue.md
View file

@ -1565,6 +1565,12 @@ Working rule:
`[region+0x27a/+0x27e/+0x282/+0x286]`. So the next non-hook region work should start from the
post-load `319` placed-structure replay seam and only then revisit the narrower region-side
`320/321` branches if the exact field bridge is still missing.
- The `319` plateau is split more cleanly now too: its neighboring world helpers are no longer
plausible region-body owners. `0x00437220` and `0x004377a0` are the chairman-slot selector and
profile materialization family over `[world+0x69d8]`, `[world+0x69db]`, and scenario selector
bytes `[0x006cec7c+0x87]`, while `0x00434d40` is only the subtype-`2` candidate runtime-latch
seeder over live placed structures. That leaves `0x004133b0` as the only region-adjacent `319`
bridge worth chasing for the missing restore seam.
- The `320` branch is narrower than that headline now too: direct worker recovery shows
`0x004235c0` staying inside the live region demand-and-placement family by routing through
`0x00422900` cached category accumulation, `0x004234e0` projected structure-count scalars,