Box in region class-mix rebuild seam
This commit is contained in:
parent
ea8ee9d753
commit
a105c387c3
2 changed files with 5 additions and 3 deletions
|
|
@ -613,8 +613,10 @@ Working rule:
|
|||
checkpoint above the ruled-down `0x00421510 -> 0x0041f5c0 -> 0x00455fc0` path. It immediately
|
||||
advances into `0x00487c20` territory refresh and `0x0040b5d0` support refresh, then later
|
||||
re-enters the per-region follow-on loop at `0x00444b90 -> 0x00420560`. Current disassembly keeps
|
||||
`0x00420560` on `[region+0x312]` / `[region+0x317/+0x31b]` only, so the next region pass should
|
||||
treat the broader `0x00444887` continuation as the live handoff seam when chasing
|
||||
`0x00420560` on the profile/class-mix scalar side only: it recomputes `[region+0x312]` from the
|
||||
embedded profile collection and linked placed-structure class mix, then seeds the year-driven
|
||||
`[region+0x317/+0x31b]` band through `0x00420350`. So the next region pass should treat the
|
||||
broader `0x00444887` continuation as the live handoff seam when chasing
|
||||
`[region+0x2a4]` and `[region+0x310/+0x338/+0x360]`, not as just another generic restore note.
|
||||
- That same continuation is slightly less symmetric now too: the atlas-backed territory side at
|
||||
`0x00487c20` currently restores only collection metadata/live ids and still uses no-op per-entry
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue