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
@@ -81,3 +81,22 @@ allowed where it resolves a core-system question, without waiting for every leve
|
||||
unavailable; source full integration validated above. Package evidence recorded
|
||||
separately without changing runtime. Continue the remaining source-state and
|
||||
shared-camera/control/collision gates rather than resuming feature expansion.
|
||||
|
||||
- Retained-field continuation2026-10-26: property extraction has no hidden reset
|
||||
callback; generic Init re-applies authored body vectors, final preparation clears
|
||||
velocity/speed, Jimmy jump state resets separately from mode/hold/fire. Bounded
|
||||
route/no-gadget/jetpack PlayerLevelState now carries only those three scalars
|
||||
through ordinary transitions, never TSK loads. Companion/shadow reset fields and
|
||||
same-state AI guard are documented; body registration/new-helper timing remain.
|
||||
- Corrected C7 prefix-only availability: full VR01..08 tails re-enable the practice
|
||||
gadget0..7, so owned VR04 jetpack finishes1. LV1B disables gadgets1/7. Managed
|
||||
state boundaries/unknown values and GPU practice/RETURN guard the correction.
|
||||
Other level-specific selection/availability tails remain an explicit gate.
|
||||
|
||||
- Retained continuation validation:84 Python,22 movement plus remaining managed
|
||||
groups,26 enabled-validation GPU renders, final nondefault tutorial/RETURN
|
||||
boundary replay, four final SDL dummy checks and539 original hashes pass.
|
||||
Original43A750/vector leaf component probe passes in isolated Wine32; this is
|
||||
separate from whole-loader/original-game/native-Windows validation. Next gates:
|
||||
uncontrolled body/controller/fire scheduling, body registration/helper traversal,
|
||||
C4 response/root and shared camera handoff. See progress.md for test-race details.
|
||||
Reference in new issue
Block a user