Narrow region latch gap to restore seams

This commit is contained in:
Jan Petykiewicz 2026-04-18 13:06:23 -07:00
commit 12dad6399f
3 changed files with 15 additions and 1 deletions

View file

@ -83,6 +83,13 @@ Working rule:
`0x0047fd50`, and the status branch `0x0047de00 -> 0x0040c990`; `0x00420280` is the same scan
returning the first matching site id. So the remaining unknown is the persisted latch/id seam,
not the live peer/service logic.
- The checked-in constructor owner `0x00421200`
`world_region_construct_entry_with_id_class_and_default_marker09_profile_seed` now also grounds
the initialization side of this family: it clears `[region+0x276]`, `[region+0x302]`,
`[region+0x316]`, and neighboring cached bands at construction time while seeding
`[region+0x25a/+0x25e] = 100.0f` and `[region+0x31b] = 1.0f`. That means the remaining queue item
is specifically post-construction restore or rebuild of the same latches, not their basic field
identity.
- 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