Run body and fire phases during scripted control locks
This commit is contained in:
1 parent
5876da112c
commit
c285b57091
35 files changed
+1503
-45
No files matched your search
@@ -190,3 +190,16 @@ all physics/AI/render fields. The detailed contract, phase limits and original
|
||||
component probe are in checkpoint/retained-player-body.md; companion/shadow
|
||||
resets and full availability tails have separate reports. Uncontrolled physics
|
||||
and exact appended-helper traversal remain next scheduler boundaries.
|
||||
|
||||
## Player control versus frame ownership
|
||||
|
||||
PlayerSceneBinding connects authored preparation/transform events to the player
|
||||
adapter. Body integration and owned fire run without player control; only input
|
||||
and movement math are gated. CAM/MCA/AI preparation has distinct order and operates
|
||||
on the prior raw owner, while Force Control affects effective input. Ordinary
|
||||
frame/modal/debug pauses stop all these phases. Scripted AI roots/yaw flow into
|
||||
physics, and physical roots flow back to director/camera targets. Destination yaw
|
||||
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.
|
||||
Reference in new issue
Block a user