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

Rule down post-load region placement branches

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

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

@ -788,6 +788,16 @@ The same brush strip is tighter now too:
way: when startup latch `0x006cd8d8` is clear it stamps `[0x006cec7c+0x79] = 1`, ensures
`[world+0x6a6c] >= 1`, forces chairman-seat byte `[world+0x69db] = 1`, and then re-enters
`0x004377a0` before the later route-entry and placed-structure refresh families. The
region-side setup branches are narrower in the same negative way now too: `0x00421c20` is just
the collection dispatcher, and its worker `0x004235c0` stays inside live region demand and
placement by routing through `0x00422900` cached category accumulation, `0x004234e0` projected
structure-count scalars, `0x00422be0` placed-count subtraction, and `0x00422ee0` placement
attempts over the live placed-structure registry `0x0062b26c`. Likewise the `321` tail
`0x00437b20 -> 0x00423d30` only refreshes cached category slots
`[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
editor-side read path is explicit on the same seam:
`map_editor_economic_cost_panel_refresh_preview_curve_and_numeric_rows` `0x004caaf0` reads the
same six-float band, builds the live preview curve on control `0x5be1`, and republishes the six

10
docs/rehost-queue.md
View file

@ -1565,6 +1565,16 @@ 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 `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,
`0x00422be0` placed-count subtraction, and `0x00422ee0` placement attempts over the live
placed-structure registry `0x0062b26c`. That keeps it on live setup and maintenance work rather
than any restore-time republisher for `[region+0x2a4]` or `[region+0x310/+0x338/+0x360]`.
- The `321` branch is narrower in the same way: `0x00437b20` only stages the fast-forward burst,
then re-enters the live region collection through `0x00423d30`, and that helper only republishes
`[region+0x27a/+0x27e/+0x282/+0x286]` via `0x00422900`. It should stay ruled down as a cached
summary refresh instead of a plausible owner for the missing restore-side body lanes.
- The later restore-side region owners are narrowed further now too: the `0x00421ce0 ->
0x0041fb00 -> 0x00421730` sweep is class-`0` raster/id rebuild, `0x004881b0` is a companion
region-set cell-count rebuild over `[region+0x3d/+0x41]`, `0x00487de0` is a border-segment