Recover Rocketship flight components against original-code probes
This commit is contained in:
1 parent
c6eb1861cd
commit
a274670fe8
23 files changed
+2462
-2
No files matched your search
@@ -93,6 +93,19 @@ and activation gating remain unresolved. The no-gadget controller checkpoint now
|
||||
integrates the corrected formulas; see analysis/movement-checkpoint.md rather than
|
||||
the older preliminary movement interpretations.
|
||||
|
||||
## Gadget component continuation — 2026-11-03
|
||||
|
||||
Supplied jn-engine class names/saved decompiler bodies guided independent local
|
||||
REA and guarded-byte recovery. Rocketship owner/control, radius50/factor.6,
|
||||
flight input/apply and VR02 game filter are documented in gameplay/rocketship.md.
|
||||
Two synthetic Wine32 harnesses executed copied input/vertical instruction ranges,
|
||||
yielding28 numeric references for13 managed RocketFlight groups. This does not
|
||||
observe whole-game flight or recover the remaining body/camera/attachment phase.
|
||||
Provenance and next gates: gameplay/rocketship-component.md. Grappler's source
|
||||
ray/material, attach/reel/swing/detach and retained helper state are recorded in
|
||||
gameplay/grappler.md with12 source/projection checks; live integration is gated.
|
||||
Original/friend files remain untouched; no tuned friend C gameplay was imported.
|
||||
|
||||
## Unresolved
|
||||
|
||||
Follow-up evidence: `analysis/runtime-checkpoint.md` identifies TSK StoredVector,
|
||||
|
||||
Reference in new issue
Block a user