Expose save-side placed-structure triplets
This commit is contained in:
parent
49ee76ef2a
commit
2d6efc7c59
3 changed files with 101 additions and 2 deletions
|
|
@ -151,6 +151,13 @@ Working rule:
|
|||
it iterates the live placed-structure collection `0x0062b26c`, filters rows through
|
||||
`0x0040c990`, optional owner-company match `[site+0x276]`, and row vtable slot `+0x70`,
|
||||
which keeps that branch on the live application side rather than replay
|
||||
- the focused save-side triplet probe is now available directly too:
|
||||
`runtime inspect-save-placed-structure-triplets <save.gms>` dumps the grounded
|
||||
`0x36b1/0x55f1/0x55f2/0x55f3` rows without the wider periodic trace wrapper
|
||||
- real-save output from that focused probe rules the checked-in triplet seam down further:
|
||||
on grounded `p.gms`, all 2026 rows keep policy trailing word `0x0101`, the profile side is
|
||||
dominated by companion byte `0x00` with status `unset` (`1885` rows) plus farm-growth buckets
|
||||
(`138` rows), and the only nonzero companion-byte residue is `3` `TextileMill` rows
|
||||
- the create-side family is grounded separately too:
|
||||
city-connection direct placement already reaches
|
||||
`0x00402cb0 -> 0x00403ed5/0x0040446b -> 0x004134d0 -> 0x0040ef10`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue