Bind world-region restore callback strip

This commit is contained in:
Jan Petykiewicz 2026-04-18 13:18:10 -07:00
commit 2d2a83957f
3 changed files with 21 additions and 11 deletions

View file

@ -3058,8 +3058,11 @@ The low helper strip beneath that shared family is tighter now too: `0x0052ecd0`
`0x0056ae30` dispatches selector `3` over the active registry, `0x0056ae80` marks pending flag
`0x100` by key, `0x0056aeb0` closes the digital driver, and `0x0056aee0/0x0056af20` are the
constructor/destructor pair for that sibling service object. One other sibling table is no longer
anonymous either: local `.rdata` at `0x005c9a60` is the world-region record family, while the
smaller collection table at `0x005c9ae0` is the live region manager stored at `0x0062bae0`.
anonymous either: local `.rdata` at `0x005c9a28` is the actual world-region record-family vtable
root, while the smaller collection table at `0x005c9ae0` is the live region manager stored at
`0x0062bae0`. The same root now also resolves the restore-side virtual strip precisely:
`0x0041f5c0` is slot `+0x40`, `0x0041f650` is slot `+0x44`, `0x00455870` is slot `+0x48`, and
`0x00455930` is slot `+0x4c`.
Constructor-side evidence is the anchor here. `0x00421660` allocates one `0x389`-sized region
row, resolves the new record, and forwards into `0x00421200`, which seeds region id
`[region+0x23a]`, class `[region+0x23e]`, profile collection `[region+0x37f]`, name buffer