Preserve retained Jimmy update order on initial story entry
This commit is contained in:
1 parent
4cd62d3627
commit
ea04210f52
24 files changed
+1209
-22
No files matched your search
@@ -373,3 +373,14 @@ assets and generated packages stay excluded.
|
||||
registry membership. Its successful Wine32 attach is tool validation, while
|
||||
MAIN-only black frames are not gameplay evidence. Keep runtime/packages fixed
|
||||
until the source/differential gate closes. See gameplay/jimmy-cutscene-lifecycle.md.
|
||||
|
||||
54. **Classify successful TSK story entry as retained-player order.**
|
||||
Source application startup loads backgroundLevel1D/Jimmy; successful TSK
|
||||
destination requests use an existing controlled C3DJIMMY and the ordinary
|
||||
selective teardown/reuse path. The new level game follows that retained node,
|
||||
including first playable New Game. Program's carriedSave-only test was too
|
||||
narrow. Include TSK-backed story entry, keep fresh direct-scene simulations,
|
||||
and preserve rotation/movement algorithms. Baseline first-neutral input
|
||||
republishes−10° bank; corrected startup order stays upright through300 idle
|
||||
ticks. Original runtime/native Windows comparison remains distinct. See
|
||||
gameplay/main-menu-player-lifetime.md.
|
||||
Reference in new issue
Block a user