Note stable region row families across saves
This commit is contained in:
parent
1f305222b8
commit
cbbf2388df
2 changed files with 8 additions and 0 deletions
|
|
@ -91,6 +91,10 @@ Working rule:
|
|||
- the save-side fixed-row run candidate family is now also the next save-slice seam to keep
|
||||
first-class once grounded, because it is the closest save-native candidate family to the
|
||||
still-missing cached tri-lane inputs behind `[site+0x310/+0x338/+0x360]`
|
||||
- cross-save fixed-row comparison is tighter now too:
|
||||
`runtime compare-region-fixed-row-runs p.gms q.gms` shows shared shape-family matches even
|
||||
though the best raw `rows_offset` drifts between saves, so the tri-lane-adjacent row family
|
||||
should be treated as a stable shape-family seam rather than a fixed-offset seam
|
||||
- Direct disassembly now narrows that acquisition strip further:
|
||||
- `0x004014b0` scans the live placed-structure collection at `0x0062b26c`
|
||||
- `0x0041f6e0 -> 0x0042b2d0` is the center-cell token gate over the current region
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue