Game-mode handler for "2: Long Game" (dispatched from 43135).

The Long Game is the full-length scenario. All 7 crew start alive but ONE of them is selected (via the ROM-traversal script, see AdvanceScriptPtr) to be the CHESTBURSTER HOST — the crew member the alien physically hatches out of. That slot is marked by stamping the HostMarker pattern ($FF on bytes +1 and +7 of its 8-byte record) so per-frame routines like SelectSlotByDrawIdx can skip it with a "CP 255" test on byte +1. The host's name is also baked into the opening status-bar message #33 enqueued at step 7 below.

The script independently chooses the alien's initial stalk target, so each Long Game has both a different host AND a different first victim.

The android-traitor mechanic lives on the OTHER randomised slot picked below: AlienTargetID (LongGameTargetTable values {1, 2, 4, 6} = Dallas / Kane / Ash / Parker). That slot is dormant at game start — it appears as just another crew member.

UpdateAndroid flips it hostile on the FIRST ENCOUNTER with the alien: the first frame AlienActiveFlag is non-zero AND the slot still carries the template's zero values in bytes +0 and +7, UpdateAndroid stamps it into action state 7 (attack) and arms it with sprite-class kin as targets.

From then on the Android wounds nearby crew via CrewAction7_Handler, named in status-bar dialogue (msg #30 "{Android} is attacking {target}"). When other crew fight it in combat state 4, CrewHitsAndroid (msg #32 "{actor} hits the Android") logs the response. The alien itself kills crew that share its room via CrewHitsAlien and the kill primitive at 37733 — independent of this Android subplot.

Steps:

• 1. Point the message queue head (MsgQueueWritePtr) at the queue base MessageQueue and clear the two run-state bytes 33708/33709.
• 2. CALL 45222: reseed the script pointer from the ZX FRAMES system variable and reset the message-dup marker (MsgLastEnqueued) to $FFFF.
• 3. LDIR 64 bytes from LongGameCrewInit into $737E to populate the alien slot and the seven crew slots with the long-game starting state (all crew alive, normal alien position).
• 4. Pull one script nibble, look it up in LongGameHostSlotTable to get the host slot index A_host (one of {1, 2, 5}), then stamp the HostMarker on that record by overwriting bytes +1 and +7 with $FF. The host's vacated room is first copied into Brett's room byte (slot 7 +1, $73B7): Brett, whom LongGameCrewInit leaves in room 0, takes the host's seat so both dinner-scene groups stay at three crew.
• 5. Loop pulling more script nibbles, looking them up in LongGameTargetTable, until the looked-up value A_target differs from A_host — the Android can't be the same slot the alien just hatched out of.
• 6. Store A_target in AlienTargetID — this slot is the per-run ANDROID: a dormant traitor crew member that UpdateAndroid flips hostile once the crew has wounded the alien 6+ times (TriggerAlienEvent).
• 7. Enqueue message #33 ("Alien has hatched from {actor}") via 37176, with the host slot index as the actor parameter — this is the long game's opening narrative beat.
• 8. Store &slot[A_target] in AlienTargetPtr so UpdateAndroid and CrewHitsAndroid can access the Android's crew record directly.
• 9. Fall through into the common init at CommonGameInit.

Used by the dispatcher at 43134 via the table at 43135.