Restore tutorial return placement and source terrain collision eligibility

This commit is contained in:
UnixNight committed 2026-10-25 01:30:09 -04:00
1 parent ca08c468ba
commit 8d60a68511
36 files changed
+991 -69

No files matched your search

+7 -1
View File
@@ -20,11 +20,17 @@ support these field sizes/order. Reader calls at`0x4605A8–0x460633`,
|18|4200 int32|Global0x4F8438..0x4FC5D8; acquired-item slots referenced by pickup code|
|16818|29 int32|One int at each8-byte record from0x4F7DB8..0x4F7EA0; semantics pending|
|16934|4 Pascal strings|Startpoint, reserved name, return level, return start|
|after strings|3 float32|Stored vector; exact meaning unresolved, not assumed player position|
|after strings|3 float32|Transition departure root at Jimmy complete+9A8; captured on ordinary departure, preserved/restored by RETURN|
|after vector|19 int32|9 group0 and10 group1 inventory states; source getters sign-extend shorts|
|after inventory|int32 count|Task entry count|
|per task|Pascal string +int32|Task name and state, in original order|
The vector identity is established by writer46008B..4600B0 and reader460B9E..460BBA,
which access complete+9A8 (interface+8E8). It is separate from pickup42AF00's
complete+1E38 checkpoint. Pending RETURN flags are not serialized; fresh save
loading still selects its STRT. See analysis/runtime-checkpoint.md for the source
capture, one-time position restoration and start-trigger suppression rules.
No version tag/checksum was found in this supplied format. Unknown tables/fields
and unusual existing inventory values are preserved. Several old saves contain
large or negative inventory states; normalizing them to booleans would break