Execute aggregate cargo packed event conditions
This commit is contained in:
parent
c17b9f55f7
commit
377de45631
18 changed files with 1036 additions and 176 deletions
|
|
@ -102,12 +102,12 @@ Implemented today:
|
|||
`%1 Production` conditions can expose stable slot metadata without a live cargo simulation layer
|
||||
- world-scalar ordinary-condition coverage now aligns with those runtime surfaces too: checked-in
|
||||
metadata lowers named locomotive availability, named locomotive cost, named cargo-production
|
||||
slot thresholds, aggregate cargo production, limited-track-building-amount, and
|
||||
territory-access-cost rows into explicit runtime condition gates
|
||||
- the remaining world-side condition frontier is now narrower and more honest: unsupported scalar
|
||||
families such as `All Factory Production` stay visible on `blocked_unmapped_world_condition`;
|
||||
the remaining cargo frontier is slot classification rather than missing save/import context
|
||||
instead of falling back to generic placeholder ids
|
||||
slot thresholds, aggregate cargo production, factory/farm-mine/other cargo production,
|
||||
limited-track-building-amount, and territory-access-cost rows into explicit runtime condition
|
||||
gates
|
||||
- cargo slot classification is now checked in across the full 11-slot recipe-book surface, so the
|
||||
remaining world-side frontier is broader descriptor/condition breadth rather than missing cargo
|
||||
classification or save/import context
|
||||
|
||||
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,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue