Files
Neutron/docs/analysis/gameplay.md
T

3.3 KiB

Gameplay evidence

Verified data reconstruction

tools/levels/gam.py parses all 35 supplied GAM files and accounts for every byte; re-encoding each parsed file reproduces its original bytes. Corpus: 3,299 entities, 93 class FourCCs, 84,044 properties (22,505 string, 26,965 float, 31,275 integer, 3,295 opaque type 2, four opaque type 4). Entity type names are inferred from matching object tags/properties, not universally proven class implementations.

All integer metadata and float32 values in GAM are big endian despite the little endian x86 executable. World positions are large unscaled coordinates; the Y coordinate is consistent with height, pending binary confirmation.

Initial scene

Original/NewGame.tsk begins with LV1B and float32 20.0. This supports LV1B as the new-game scene; it does not prove all save fields. gam/level1b.gam has 129 objects. Its player record at file offset 0x8:

Property Value
kind 3JIM
ObjectTag JIM1
PositionX 5071.93310546875
PositionY 26.661895751953125
PositionZ 824.1039428710938
RotationY 155 degrees
StartPoint STARTEXP

The matching STRT record starts at 0x5b0e. It agrees on player position/yaw; camera position is (4873.83642578125, 235.64761352539062, 373.21588134765625), camera rotations are zero, music is musicsecretlab.omt index 0, and StartTrigger is LABEXP. Camera look-at behavior and the introductory trigger require code analysis; do not treat zero stored rotation as proof of a zero effective rotation.

Small validation scene

gam/VR01.gam: 16 entities, one trophy, four pickups, two phone booths and two LOAD return triggers. Player at 0x8: (-2678.0380859375, 87.33218383789062, -2783.401123046875), yaw 290 degrees. STRT at 0x45c stores camera (-2709.25634765625, 287.3321838378906, -2390.133056640625), music musicvr01.omt index 0 and start trigger bu. Pickups use radius 100.0 and PointValue 5.

Controls documented by original readme

Source: Original/readme.txt, section V.

Input Original action
Up / Down Forward / backup (rearview in scooter mode)
Left / Right Turn left / right
Enter / Ctrl / left mouse Primary fire
Shift / Insert / right mouse Jump or jet-pack burst
M / O / H / I Menu / objectives / help / item inventory
G Call Goddard
Tab / Space Gadget screen
Escape Quit / main menu / skip cutscene
Mouse movement Forward, backward, turn

Data is not an algorithm

LOAD exposes LevelName, StartPoint, RequiredTask, RequiredLevel, ExactLevel, Radius, SoundIndex, FadeType and FadeTime. PIC exposes prerequisite fields, PointValue and pickup index. These are faithfully recoverable inputs; exact trigger conditions, distance metric, timing, task comparison and state updates must be established from executable code or observation before implementation is called faithful. Negative integers commonly act as flags/sentinels; their exact meaning depends on each property.

Save data has a fixed-looking region followed by Pascal task names and big endian values (NewGame.tsk tail includes SCENE = 30). Save writing is not yet recovered. Physics, jumping, collision, AI, RNG, combat, progression and cutscene execution remain under investigation. No original gameplay session has been captured yet.