Rule out region offset-collision helper classes

This commit is contained in:
Jan Petykiewicz 2026-04-18 17:42:07 -07:00
commit 8889b904f7
2 changed files with 8 additions and 0 deletions

View file

@ -337,6 +337,11 @@ Working rule:
`0x0062bae0` that adjust the same mirrored pair for hardcoded region ids. So the remaining
region restore question is no longer “what does `[region+0x25e]` mean?” but “which load/reseed
seam restores the mirrored severity pair before the producer runs?”
- Two more direct-hit writer bands are now explicitly ruled out too: `0x0043a5a0` is a separate
constructor under vtable root `0x005ca078` that zeroes its own `[this+0x302/+0x316]` fields
during local object setup, and `0x0045c460/0x0045c8xx` is a separate vtable-`0x005cb5e8` helper
family whose `[this+0x316]` is a child-array pointer serialized through `0x61a9/0x61aa/0x61ab`.
So those offset-collision classes should stay out of the remaining region restore search.
- 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]`,