Ground bridge-only infrastructure prelude class
This commit is contained in:
parent
ab0573458b
commit
fb13cd22d8
3 changed files with 72 additions and 9 deletions
|
|
@ -2998,8 +2998,9 @@ The low helper strip beneath that shared family is tighter now too: `0x0052ecd0`
|
|||
`BridgeSTWood_Section.3dp / Infrastructure` class across `18` rows with dominant prior profile
|
||||
span `0x06` (`10` rows). So the next infrastructure pass should split its owner questions the
|
||||
same way: treat `0x0055 / 0x00` as a `BallastCap`-specific boundary artifact class, and treat
|
||||
`0x0002 / 0xff` as the likely bridge-specific two-child / clone-path class above
|
||||
`0x0048a1e0/0x0048dcf0`.
|
||||
`0x0002 / 0xff` as the grounded save-side bridge-specific two-child candidate class above
|
||||
`0x0048a1e0/0x0048dcf0`, with the remaining unknown narrowed to the upstream chooser that emits
|
||||
that class before the attach/rebuild path runs.
|
||||
The child loader family is explicit now too: local `.rdata` at `0x005cfd00` proves the
|
||||
`Infrastructure` child vtable uses the shared tagged callback strip directly, with
|
||||
`+0x40 = 0x00455fc0`, `+0x48 = 0x00455870`, and `+0x4c = 0x00455930`. So the remaining
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue