Apply recovered player phases, static camera query and level availability

This commit is contained in:
UnixNight committed 2026-10-25 19:56:44 -04:00
1 parent 117db77c7b
commit 09cf1172bf
33 files changed
+1500 -99

No files matched your search

+14 -10
View File
@@ -79,7 +79,7 @@ retention and the current-level global509948 are distinct: GAM loading assigns
Further class-specific lifecycle flags or later predicate changes require their
own evidence; do not generalize the constructor default into a full object map.
**Critical integration consistency gate: old level-game ownership.** The lab game
**Resolved follow-up: old level-game ownership.** The lab game
is initialized for preservation (interface4C386C slots200/204 resolve
4719B0/C0; defaults bridge above reaches44D456's push0/44D472's dispatch204).
Later changes to that predicate remain part of the lifetime audit. GAM loading then
@@ -95,12 +95,16 @@ The lab constructor chain44F300→44F358/44D2B0→44D306/4745A0 was also inspect
destructor/removal was established in this inspected chain. **Overwriting the
current-game pointer does not remove an old game from registry50999C.**
Consequently the remaining contract must include the old level-game registry
membership and callback eligibility: locate its explicit removal/deactivation
or account for its retained28/40C/update callbacks. Do not infer a clean sequence
containing only Jimmy/Goddard plus the new game from selective deletion alone.
Possible later class/OMT ownership effects remain open; this negative bounded
audit does not prove that old games accumulate or remain active at runtime.
The subsequent audit in `level-game-lifetime.md` closes this gap: normal Init28
calls470540, whose4705B3 getter8C reads stored interface+11 through470F30;
4705BC setter204 copies it to live+139. Generic game construction stored+11=1;
the direct defaults204(0) never changed that stored value. Thus initialized level
games qualify for selective teardown. Their destructor reaches470060 and
explicitly removes their registry node at470106→469490. Jimmy/Goddard instead
use470F40(0), setting both stored/live fields, so initialization preserves their
retention. The earlier bounded prefix/constructor search was incomplete; pointer
overwrite is still not deletion, but Init and destructor now establish actual
old-game removal and retained-character/new-game ordering.
## GAM construction/reuse and initialization
@@ -127,7 +131,7 @@ registry in order. It invokes object28, handles attached render-object state,
then object40C, handles attached render state again, then advances registry.
These are per-object boundaries, not “initialize all, then PostLoad all.” Jimmy's
28 is437890; it calls4587F0→470540 and resets movement fieldsinterface+608/+614/
+618 and captures another velocity component+61C. Jimmy40C423610 applies:
+618 and captures logical Euler.Y (yaw) into+61C, not body velocity. Jimmy40C423610 applies:
1. Matching source STRT root42399D and rotation4239E6.
2. Existing companion source root423A36.
@@ -176,8 +180,8 @@ force original editor R semantics into the game's current R reset control.
## Bounded continuation gate
1. Resolve old level-game removal/deactivation and callback eligibility across
destination construction. Then trace a retained Jimmy through one departure,
1. Old level-game removal is now resolved by the Init stored/live flag bridge and
destructor unlink. Trace a retained Jimmy through one departure,
identifying every mutation
from property load, initialization and PostLoad. Constructor evidence closes
byte+9 ownership; it does not substitute for this per-field reset trace.