Trace post-skip tilt and gate gameplay changes on original lifecycle recovery
This commit is contained in:
1 parent
a2e89c625a
commit
68154dffce
15 files changed
+752
-6
No files matched your search
@@ -0,0 +1,65 @@
|
||||
# Laboratory trigger and skip callback order
|
||||
|
||||
2026-11-05. Static original source/data recovery; gameplay changes are paused.
|
||||
Original EXE identity and retained REA Evidence are recorded in
|
||||
[jimmy-cutscene-return-source.md](jimmy-cutscene-return-source.md).
|
||||
`tools/binary/jimmy_cutscene_chain.py` verifies PE-mapped offsets, calls, virtual
|
||||
bindings and supplied GAM fields; generated output is
|
||||
artifacts/jimmy-cutscene-return/source-contracts/chain.json.
|
||||
|
||||
## Actual lab records
|
||||
|
||||
| Record / file offset | Source chain |
|
||||
|---|---|
|
||||
|3MCA neutron1a, GAM index7, E0B|Five active targets, beginning with JIM1, then Carl, Carl, Jimmy, Carl. PlayerControlledJIM1 is the completion target; DeactivateInv1; TargetDeactAnimSTOP; NextTriggercarlwalk.|
|
||||
|3AIT Carlwalk, index10,1AFD|AITargetC3DCARL, AIState3, no new position/yaw, PlayerControllednone, NextTriggerdefault. This record does not restore an old Jimmy transform.|
|
||||
|3AIT teleportexplanation,index34,6756|Touch activation byjim1, SCENE30 invokes te1; PlayerControllednone; te1→te2→TE3→te4→te5→default. This is a different entry path from Carl's friend talk.|
|
||||
|
||||
GAM hash316fff40db565c2add5b07cbccdef640ddb67c64d6625fea1429ce2a0542a234.
|
||||
All tags are looked up case-insensitively as in the existing bounded parser.
|
||||
|
||||
## Original partial order
|
||||
|
||||
Viewport47E554 calls global physics479BC0 before registry473740 at47E582.
|
||||
Physics invokes dynamic pair processing47A430 at479C83. Its enter callbacks
|
||||
47A555/47A578 dispatch slot40 before the later registry traversal.
|
||||
|
||||
- An AI trigger's interface is complete+C8:48F8C0+40→40C200, then40C21F
|
||||
synchronously dispatches40C300. A trigger can therefore activate a camera
|
||||
during the contact pass, before the game's ordinary input callback.
|
||||
- Carl's interface is complete+C0:495364+40→40A3C0. Its AI contact state may
|
||||
become0. The friend update41B950 first calls408000, then41B972..41B988
|
||||
invokes talk when the resulting state is0. In the fresh registry partial
|
||||
order, Carl follows Jimmy. Contact and actual conversation activation are
|
||||
separate boundaries.
|
||||
- Talk41B7B0 obtains a matching trigger, invokes Carl's progress callback,
|
||||
then41B7D8 dispatches the chosen trigger. Carl413E50 calls41B810 first
|
||||
(+100 score and **Carl's**410 preparation), then advances SCENE50→60.
|
||||
This does not by itself establish a Jimmy movement reset.
|
||||
- MCA update is game interface+C8 table4A8F64+3C4→430DA0. Natural completion
|
||||
and skip have different branches; skip writes Jimmy's action latch and
|
||||
shared skip flag before completing through4A93C8+E4→4311F0.
|
||||
- Source registry473740 dispatches each object's slot10 at473758. Actor
|
||||
insertion order matters for same-frame control changes. Fresh and retained
|
||||
routes must not be collapsed into a single assumed order.
|
||||
|
||||
The port's director.Touch/SceneInteractions calls occur after the combined
|
||||
player update in Program. This is a documented scheduling approximation; it
|
||||
cannot prove the original starts a conversation with identical support/mode/
|
||||
turn state. The original dynamic admission/support and callback positions need
|
||||
comparison before that difference can be called the tilt's source cause.
|
||||
|
||||
## Missing proof and next trace
|
||||
|
||||
The user specifically reports **skipping Carl**, not a measured natural-end
|
||||
comparison. The diagnostic also reproduces natural-end failures in the port,
|
||||
but that is not evidence about original natural completion. Required original
|
||||
trace points are: physical contact, final Jimmy callback before activation,
|
||||
MCA entry, accepted skip, completion/DEFAULT, next game input and next Jimmy
|
||||
update. At each point record raw owner, support, mode, turn, current/target
|
||||
Euler, dirty and input suppression/latches. This will distinguish an entry-state
|
||||
mismatch from a return/scheduling mismatch.
|
||||
|
||||
Current static conclusions and managed traces are useful evidence, but neither
|
||||
supplies a source-justified reset location. No gameplay change is introduced by
|
||||
this report or its read-only guard.
|
||||
Reference in new issue
Block a user