Correct save train and region collection probes

This commit is contained in:
Jan Petykiewicz 2026-04-18 08:26:58 -07:00
commit 86511f9670
5 changed files with 251 additions and 113 deletions

View file

@ -191,11 +191,12 @@ The highest-value next passes are now:
electric-only periodic-company override rewrites the world route-preference byte to the
effective company preference, ending it restores the base world byte, and runtime service state
now carries both the active and last applied override
- save inspection now also exposes the tagged live region header `0x5209/0x520a/0x520b` plus its
live-entry directory rooted at metadata dword `16`, and the tagged placed-structure header
`0x36b1/0x36b2/0x36b3`, as first-class owner seams, so the remaining city-connection /
linked-transit blocker is record-body reconstruction rather than missing save-side collection
identity
- save inspection now also separates the shared `0x5209/0x520a/0x520b` save family correctly: the
smaller direct `0x1d5` collection is the live train family and now exposes a live-entry
directory rooted at metadata dword `16`, while the actual region collection is the larger
non-direct `Marker09` family; the tagged placed-structure header `0x36b1/0x36b2/0x36b3`
remains grounded alongside them, so the remaining city-connection / linked-transit blocker is
record-body reconstruction rather than missing save-side collection identity
- the project rule on the remaining closure work is now explicit too: when one runtime-facing field
is still ambiguous, prefer rehosting the owning source state or real reader/setter family first
instead of guessing another derived leaf field from neighboring raw offsets; the checked-in