Import locomotive availability descriptors with overlay context
This commit is contained in:
parent
8c7ff335cb
commit
87108f357b
21 changed files with 1154 additions and 27 deletions
|
|
@ -127,10 +127,10 @@ The highest-value next passes are now:
|
|||
descriptors `454..456` (`All Steam/Diesel/Electric Locos Avail.`) now lower through checked-in
|
||||
metadata into keyed `world_flags`, while the wider locomotive availability/cost scalar bands
|
||||
remain recovered-but-parity-only until per-locomotive identity is grounded
|
||||
- the runtime now also carries the save-owned named locomotive availability table directly:
|
||||
checked-in save-slice documents can populate `RuntimeState.named_locomotive_availability`, and
|
||||
imported runtime effects can mutate that map through the ordinary event-service path without
|
||||
needing full live locomotive-pool parity
|
||||
- the runtime now also carries both the save-owned named locomotive availability table and an
|
||||
overlay-backed locomotive catalog context: checked-in save-slice documents can populate
|
||||
`RuntimeState.named_locomotive_availability`, and boolean `0/1` availability descriptors can
|
||||
lower through `RuntimeState.locomotive_catalog` into the same ordinary event-service path
|
||||
- keep in mind that the current local `.gms` corpus still exports with no packed event collection,
|
||||
so real descriptor mapping needs to stay plumbing-first until better captures exist
|
||||
- use `rrt-hook` primarily as optional capture or integration tooling, not as the first execution
|
||||
|
|
|
|||
|
|
@ -86,10 +86,14 @@ Implemented today:
|
|||
save-slice documents can carry the persisted `[world+0x66b6]` name table into
|
||||
`RuntimeState.named_locomotive_availability`, and imported runtime effects can mutate that map
|
||||
through the ordinary event-service path without requiring Trainbuy or live locomotive-pool parity
|
||||
- the boolean `0/1` subset of the recovered locomotives-page availability bands can now import
|
||||
through an overlay-backed `RuntimeState.locomotive_catalog`; non-boolean availability payloads
|
||||
and the adjacent locomotive-cost/cargo-production/access-cost families remain parity-only
|
||||
|
||||
That means the next implementation work is breadth, not bootstrap. The recommended next slice is
|
||||
broader real grouped-descriptor and ordinary condition-id coverage beyond the current access,
|
||||
whole-game toggle, train, player, numeric-threshold, and named locomotive availability batches.
|
||||
whole-game toggle, train, player, numeric-threshold, named locomotive availability, and
|
||||
overlay-resolved locomotive availability batches.
|
||||
Richer runtime ownership should still be added only where a later descriptor or condition family
|
||||
needs more than the current event-owned roster.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue