Bound scenario fixup trigger-kind retags
This commit is contained in:
parent
e57b07c9bc
commit
76396ee12e
4 changed files with 30 additions and 1 deletions
|
|
@ -172,6 +172,13 @@ editor strip rather than to ordinary post-load simulation bringup.
|
|||
- `0x0062bae0`
|
||||
- `0x006ada80`
|
||||
- `0x0062b268`
|
||||
- The event-side trigger-kind boundary is narrower now too:
|
||||
- grounded `[event+0x7ef]` writes inside `0x00442c30` are still only:
|
||||
- `0x00443526`: event row `1`, `1 -> 5`
|
||||
- `0x00443601`: event row `0x0d`, `0 -> 2`
|
||||
- the surrounding surfaced event branches only patch modifier bytes `[event+0x7f9/+0x7fa]`
|
||||
or nested payload dwords under already-existing kinds `6`, `5`, `1`, `2`, `3`, or `9`
|
||||
- no grounded branch in `0x00442c30` seeds `[event+0x7ef] = 8`
|
||||
|
||||
## Explicit Trigger-Kind Retags Already Grounded
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue