Rule down post-load region placement branches
This commit is contained in:
parent
0b0420c898
commit
a56d360a3e
4 changed files with 44 additions and 0 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue