Implement world-scalar packed event conditions
This commit is contained in:
parent
b060c42fa2
commit
3f2632e330
12 changed files with 1541 additions and 8 deletions
|
|
@ -58,7 +58,13 @@ rows directly into `RuntimeState.named_locomotive_availability` and
|
|||
`RuntimeState.named_locomotive_cost` without needing overlay snapshots when the save carries enough
|
||||
catalog context. The remaining recovered scalar world families execute too: cargo-production slots
|
||||
`230..240` lower into `cargo_production_overrides`, and descriptor `453` lowers into
|
||||
`world_restore.territory_access_cost`. Explicit unmapped world-condition and world-descriptor
|
||||
`world_restore.territory_access_cost`. Whole-game ordinary-condition breadth now aligns with those
|
||||
same world-scalar runtime surfaces too: named locomotive availability thresholds, named
|
||||
locomotive cost thresholds, aggregate cargo-production thresholds, limited-track-building-amount
|
||||
thresholds, and territory-access-cost thresholds all gate imported runtime records through the
|
||||
same service path. Families the current checked-in metadata still does not ground, such as `All
|
||||
Factory Production`, now remain explicitly visible on `blocked_unmapped_world_condition` rather
|
||||
than collapsing back to generic residue. Explicit unmapped world-condition and world-descriptor
|
||||
frontier buckets still remain where current checked-in metadata stops, and
|
||||
`blocked_missing_locomotive_catalog_context` is now reserved for intentionally incomplete save-side
|
||||
catalog context instead of the normal save-slice path. Shell purchase-flow, Trainbuy refresh,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue