Bound packed-state trigger-kind omission
This commit is contained in:
parent
511c030244
commit
699a2ae7f1
5 changed files with 19 additions and 4 deletions
|
|
@ -149,6 +149,12 @@ The ordinary reload path is narrower in the same negative way now too:
|
|||
- clears collection flag `[this+0x88] = 0` before returning
|
||||
- that reload path does not pass any trigger-kind argument analogous to the later `0x00432f40`
|
||||
service call
|
||||
- and the per-record helper `0x0042db20` is narrower than a full metadata restore:
|
||||
- it conditionally rebuilds the six fixed text bands and the linked `0x1e` / `0x28` row families
|
||||
- it does **not** restore the event metadata band `+0x7ee..+0x80e`, including `[event+0x7ef]`
|
||||
- the save-side companion `0x00430d70` matches that same omission:
|
||||
- it writes the fixed text bands plus the linked condition/effect rows
|
||||
- it does **not** serialize the metadata band `+0x7ee..+0x80e`
|
||||
|
||||
So the remaining periodic-company question stays between reload and service: the checked restore
|
||||
path repopulates the rows, but the later trigger-kind gate lives only in the service strip.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue