Rehost route preference override mutation seam
This commit is contained in:
parent
f7fde709f7
commit
cdab16476e
8 changed files with 361 additions and 16 deletions
|
|
@ -187,9 +187,16 @@ The highest-value next passes are now:
|
|||
- that same seam now also resolves the base world route-preference byte at `[world+0x4c74]`, the
|
||||
effective electric-only override fed by `0x0d17`, and the matching `1.4x` versus `1.8x`
|
||||
route-quality multiplier as a normal runtime reader instead of a pure atlas note
|
||||
- that same seam now also owns the first route-preference mutation path directly: beginning the
|
||||
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
|
||||
- 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
|
||||
instead of guessing another derived leaf field from neighboring raw offsets; the checked-in
|
||||
`docs/rehost-queue.md` file is the control surface for that work loop, and after each commit the
|
||||
next queue item should run unless the queue is empty, a real blocker remains, or approval is
|
||||
needed
|
||||
- a checked-in `EventEffects` export now exists at
|
||||
`artifacts/exports/rt3-1.06/event-effects-table.json`, and a checked-in semantic closure layer
|
||||
now exists at `artifacts/exports/rt3-1.06/event-effects-semantic-catalog.json`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue