Recover retained route state and complete PostLoad availability tails
This commit is contained in:
1 parent
1dddfefc68
commit
9ad5a8ef6b
36 files changed
+1559
-32
No files matched your search
@@ -138,3 +138,16 @@
|
||||
continue. Debug checkpoint uses the existing TSK/start progression contract,
|
||||
never pretends to save live physics/cutscene state. These are investigation
|
||||
features with port verification, not recovered original behavior.
|
||||
|
||||
29. **Persist bounded retained scalars independently of resets.** Ordinary route
|
||||
loads keep movement mode, jump-hold and owned-fire timer in a separate memory
|
||||
container for proven no-gadget/jetpack states. Reset jump/body/presentation
|
||||
through their own boundaries; do not serialize these fields in TSK or carry
|
||||
them through debug checkpoint load. Unsupported levels/gadget cleanup remain
|
||||
the existing explicit approximation until traced. First destination ticks
|
||||
can change retained values; boundary and post-tick tests are different.
|
||||
30. **Read full PostLoad tails before asserting final availability.** The prior
|
||||
common-prefix interpretation was incomplete. Each VR01..08 re-enables its
|
||||
practice gadget after the shared disable pass; LV1B disables1/7. Correct the
|
||||
implementation and expectations from the later dispatch/call evidence and
|
||||
retain the earlier report as a scoped historical audit with a correction.
|
||||
Reference in new issue
Block a user