Rule out region policy chunk latch candidates
This commit is contained in:
parent
2d2a83957f
commit
90059bb727
2 changed files with 46 additions and 0 deletions
|
|
@ -102,6 +102,10 @@ Working rule:
|
|||
`0x00531150/0x00531030` plus `0x00530720/0x0052e8b0`; they still do not touch
|
||||
`[region+0x276/+0x302/+0x316]`. That means the remaining region restore target is now the later
|
||||
owner that rebuilds those latches or the separate tagged body seam that persists them.
|
||||
- The widened real-save region trace rules out one more false lead too: on grounded saves the
|
||||
`0x55f2` fixed-policy chunk keeps all three reserved dwords at `0x00000000` and the trailing word
|
||||
at invariant `0x0001`, so that fixed chunk is not currently carrying the missing latch or stable
|
||||
region id/class discriminator either.
|
||||
- Reconstruct the save-side placed-structure collection body on top of the newly grounded
|
||||
`0x36b1/0x36b2/0x36b3` header seam so the blocked city-connection / linked-transit branch can
|
||||
stop depending on atlas-only placed-structure and local-runtime refresh notes, especially the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue