Split post-load chairman and subtype latch branches
This commit is contained in:
parent
a56d360a3e
commit
15643a6df6
3 changed files with 13 additions and 0 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue