Expose save-side region record triplets
This commit is contained in:
parent
86511f9670
commit
8861074c1b
2 changed files with 222 additions and 4 deletions
|
|
@ -10,10 +10,12 @@ Working rule:
|
|||
## Next
|
||||
|
||||
- Reconstruct the save-side region record body on top of the newly corrected non-direct tagged
|
||||
region seam (`0x5209/0x520a/0x520b`, stride hint `0x06`, `Marker09` record stems), especially
|
||||
the pending bonus lane `[region+0x276]`, completion latch `[region+0x302]`, one-shot notice
|
||||
latch `[region+0x316]`, severity/source lane `[region+0x25e]`, and any stable region-id or
|
||||
class discriminator that can drive shellless city-connection service.
|
||||
region seam (`0x5209/0x520a/0x520b`, stride hint `0x06`, `Marker09` record stems) and its now
|
||||
grounded repeated `0x55f1/0x55f2/0x55f3` record-triplet envelope, especially the fixed `0x55f2`
|
||||
policy row behind `[region+0x272/+0x25a/+0x25e]`, the pending bonus lane `[region+0x276]`,
|
||||
completion latch `[region+0x302]`, one-shot notice latch `[region+0x316]`, severity/source lane
|
||||
`[region+0x25e]`, and any stable region-id or class discriminator that can drive shellless
|
||||
city-connection service.
|
||||
- Reconstruct the save-side placed-structure collection body on top of the newly grounded
|
||||
`0x36b1/0x36b2/0x36b3` header seam so the blocked city-connection / linked-transit branch can
|
||||
stop depending on atlas-only placed-structure and local-runtime refresh notes.
|
||||
|
|
@ -56,6 +58,9 @@ Working rule:
|
|||
at metadata dword `16`, while the actual region family is the larger non-direct `Marker09`
|
||||
collection with live_id/count `0x96/0x91`; the tagged placed-structure header
|
||||
(`0x36b1/0x36b2/0x36b3`) remains grounded alongside them.
|
||||
- That same corrected region seam now also exposes repeated `0x55f1/0x55f2/0x55f3` serialized
|
||||
record triplets with len-prefixed names plus fixed policy/profile chunk lengths, so the next
|
||||
city-connection pass can target the real record envelope instead of another blind scan.
|
||||
- Stepped calendar progression now also refreshes save-world owner time fields, including packed
|
||||
year, packed tuple words, absolute counter, and the derived selected-year gap scalar.
|
||||
- Automatic year-rollover calendar stepping now invokes periodic-boundary service.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue