Ground event retagger trigger materializations
This commit is contained in:
parent
e2f60bef9a
commit
e62962f337
2 changed files with 17 additions and 0 deletions
|
|
@ -297,6 +297,12 @@ Working rule:
|
|||
remaining trigger-kind frontier is no longer “maybe the name sweep bulk-materializes null
|
||||
kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes
|
||||
`[event+0x7ef]` itself or a still-later owner does.
|
||||
- two explicit trigger-kind materializations are now grounded inside that retagger:
|
||||
the `SP - GOLD` branch at `0x00443526` rewrites `[event+0x7ef]` from `1 -> 5` on live
|
||||
runtime-event id `1` when `[world+0x66de]` is set and the checked root payload is kind `7`
|
||||
with subtype byte `5`, while the `Labor` branch at `0x00443601` rewrites `[event+0x7ef]`
|
||||
from `0 -> 2` on live runtime-event id `0x0d` when the same scenario flag is set and the
|
||||
checked `0x3c -> 0x3d` child payload pair carries the matching negative scalar sentinel.
|
||||
- cross-map probing now gives a better static-analysis lead too:
|
||||
`British Isles.gmp` shows no current `0x00431b20` dispatch-strip rows, `Germany.gmp` stays on
|
||||
`Game Variable 1` plus `Company Variable 3..4`, while `Texas Tea.gmp` adds `Economic Status`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue