Files
BT411/engine/MUNGA
arcattackandClaude Opus 4.8 a8a6da6760 Solo mission clock: end the mission when the game length expires (port shim)
Field 2026-07-23: a 20-minute solo mission was still running at 53
minutes.  In the arcade the OPERATOR CONSOLE owned the game clock and
sent StopMission at zero; the engine only computes the HUD countdown
(secondsRemainingInGame) -- nothing consumes it.  The desktop FE-solo
mode has no console, so timed solo missions ran forever.

Shim at the countdown site (Application::Execute): when no
console/relay owns the session (BT_RELAY unset), post the console's
own StopMissionMessage when the clock runs out -- the normal end flow
(EndingMission -> review -> FE relaunch) takes over.  length=0 (raw
solo) stays endless; console-driven sessions untouched.  One-shot
latch resets outside RunningMission.

Awaiting live verification (a 60s-length solo egg must end itself).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-23 15:00:41 -05:00
..