Ground acquisition create-side constructor family
This commit is contained in:
parent
eadc10b4d6
commit
a120053d2f
2 changed files with 42 additions and 5 deletions
|
|
@ -121,9 +121,14 @@ Working rule:
|
|||
`0x2329/0x0d`, candidate field `[candidate+0x22]`, and the projected-cell validation strip
|
||||
`0x00417840 -> 0x004197e0`, then commits the linked-site mutation through
|
||||
`0x0040d1f0 / 0x00480710 / 0x0045b160 / 0x0045b9b0 / 0x00418be0 / 0x0040cd70`
|
||||
- the create-side family is grounded separately too:
|
||||
city-connection direct placement already reaches
|
||||
`0x00402cb0 -> 0x00403ed5/0x0040446b -> 0x004134d0 -> 0x0040ef10`
|
||||
as the shared constructor/finalize strip for newly created site rows
|
||||
- so the acquisition blocker is no longer “is there any real consumer family above these
|
||||
lanes?”; it is specifically the restore or replay owner that populates those live preconditions
|
||||
for shellless acquisition
|
||||
lanes?” or “how do new placed structures finalize?”; it is specifically the restore or replay
|
||||
owner that populates those live preconditions for already-restored rows before shellless
|
||||
acquisition runs
|
||||
- direct disassembly now shows the generic base constructor `0x0052edf0` clearing base state
|
||||
through `0x0052ecd0` and then writing `[this+0x04]` from caller arg `1`
|
||||
- `0x00455b70` is the concrete placed-structure specialization constructor feeding
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue