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
@@ -270,3 +270,17 @@ and queued work are not cleared by a transform setter. The original full wrapper
|
||||
registry, body response and morph clock are still not reconstructed by this bridge.
|
||||
See checkpoint/control-phase-implementation.md. REA tooling is separate from
|
||||
runtime architecture; setup/provenance are in rea.md.
|
||||
|
||||
## Isolated vehicle components
|
||||
|
||||
RocketFlight separates ordinary keyboard scalar/bank input from vertical
|
||||
acceleration publication. The source applies retained state before the controlled
|
||||
input/camera callback. It neither integrates a body nor owns a camera/passenger;
|
||||
no live runtime path calls it yet. Twenty-eight isolated copied-original numeric
|
||||
references support its bounded arithmetic. Aircraft callbacks, full Euler/camera,
|
||||
owned-versus-placed property/reset and helper lifetime remain gates before an
|
||||
explicit vehicle owner is added to PlayerSceneBinding/director scheduling.
|
||||
The exact resource exporter is opt-in and assigns no attachment transforms.
|
||||
See gameplay/rocketship-component.md. Grappler's distinct source ownership and
|
||||
geometry/material/swing contract is in gameplay/grappler.md; it is not a simple
|
||||
player movement mode or nearest-tag interaction.
|
||||
Reference in new issue
Block a user