Recover Rocketship flight components against original-code probes

This commit is contained in:
UnixNight committed 2026-11-03 11:09:16 -05:00
1 parent c6eb1861cd
commit a274670fe8
23 files changed
+2462 -2

No files matched your search

+9
View File
@@ -239,3 +239,12 @@
evidence. Capture tooling/derived scenes are present; raw OMTC, analysed
Ghidra database and proposed gameplay state traces are not. Record offered
permission before source import. Assessment: reviews/jn-engine-survey.md.
42. **Verify vehicle arithmetic before connecting live ownership.** RocketFlight
preserves per-callback input acceleration, support/brake ordering and retained
vertical-command publication, compared with28 isolated copied-original cases.
Radius50 is collision size, not render scale; rates650/−650 are acceleration,
not assigned velocity. Do not substitute Jimmy's body/camera for aircraft
callbacks or claim the scalar component is a live Rocketship. Resolve owned
versus placed properties, passenger/effect lifetime and control/camera phase
before VR02 integration. Grappler's geometry/material/swing contract likewise
forbids nearest-hook/direct-pull replacement. See gameplay/rocketship-component.md.