State and progression

Primary variables

The persistent script state is an array of 100 signed 16-bit words. New game initialization clears all words before assigning starting values. Scene programs may use unnamed words as temporaries; a compatible engine MUST save all 100, not only the named fields.

The following indexes have cross-scene meanings:

Faith is stored in hundredths of a displayed percentage point. New play starts at 10000. F3 displays it as a percentage, and ordinary rendering clamps values to the 0–10000 range. A negative value after input processing is clamped to zero and requests OVER.

Flag bank

Variables 3 through 10 also form a 128-bit boolean bank. Flag n resides in:

word = 3 + (n >> 4)
mask = 1 << (n & 15)

Flags 00 through 2F include transient movement and action context and are rebuilt by current-cell processing. Higher flags carry durable abilities and progress. The map-derived ranges are:

The world-model chapter gives the exact individual mapping and scan gates. Flags 14, 15, and 22 through 2F are cleared by this operation but not set from map geometry.

Other important identifiers are:

The status bar exposes the five powers as F4 through F8 icons. They are boolean capabilities, not consumable counters, unless a scene explicitly clears them.

Ordinary progression

Each level is an explorable grid containing halls, Cybers, side rooms, Scripture stations, and an exit. The player acquires verses, studies them to answer lies and unlock interactions, rescues the level’s victim, and reaches the exit. Scene programs set the seven rescue flags at the successful conversation points. The engine MUST preserve the live map, variables, flags, text-record states, and scene name across save/restore.

At the gantry, each rescue flag 3A–40 is mirrored to crew flag 42–48. The craft requires all seven crew flags; with fewer, it reports the missing count and does not depart. Departure clears Sword, Shield, No Trap, Candle, and Flight, initializes Unibot node and heading state, and enters the final road network.

Unibot graph

The final network is a 16-node graph embedded in CP2.BIN. Direction slots are north, east, south, west; 100 is blocked. All open edges are reciprocal.

The player can turn right (.r), turn left (.l), or move forward (.u). Turns wrap heading modulo four. Forward follows the adjacency entry for the current heading and is unavailable when it is 100.

On scene entry, endpoint nodes normalize to adjacent roads: 3→2, 5→4, 7→6, 8→15, 10→9, 11→12, 13→12, and 14→1. The engine MUST honor the script’s table reads and this normalization rather than substituting Euclidean movement.

CP2.BIN is 1E55 bytes. Its commands occupy 0000..1D54; the trailer is four consecutive signed-word tables:

The first eligible road event loads ANNOY, clears the player’s acquired verse states, and sets flag 54. Later road visits skip it.

Pylons and ending

Pylon endpoints map to variables 56 through 62 and study selectors 11 through 17. A completed pylon is skipped. Correct study sets its variable to one, destroys it, and recovers the associated crew member. A wrong answer enters OVER.

The Tower at node 14 requires all seven variables to be nonzero; arriving early also enters OVER. With the gate satisfied, FACE and CP3 implement:

There is no additional engine-defined victory condition. Scene programs and these persistent values are the progression authority.