Game Phases (Screens)

Overview

Each phase corresponds to a WM_PHASE_* Windows message. The active phase determines which background image, buttons, and event handlers are active. A phase switch is triggered by sending WM_PHASE_* to the window, caught by CEvent::ChangePhase().

Complete Phase Table

Typical Phase Flow for One Mission

WM_PHASE_INIT
    → WM_PHASE_INTRO1 / WM_PHASE_INTRO2   (intro animation, first run only)
    → WM_PHASE_SKILL1 / WM_PHASE_SKILL2   (difficulty selection)
    → WM_PHASE_REGION                      (visual theme selection)
    → WM_PHASE_SCHOOL or WM_PHASE_MISSION  (mission selection)
    → WM_PHASE_INFO                        (mission briefing)
    → WM_PHASE_PLAYMOVIE                   (pre-mission cinematic)
    → WM_PHASE_PLAY                        (gameplay!)
        ↓ (during play)
        WM_PHASE_STOP → WM_PHASE_PLAY      (pause and resume)
        WM_PHASE_HELP → WM_PHASE_PLAY      (help overlay)
        ↓ (mission end)
    → WM_PHASE_WIN or WM_PHASE_LOST
    → WM_PHASE_WINMOVIE                    (victory cinematic)
    → WM_PHASE_TERM                        (mission statistics)
    → WM_PHASE_MISSION                     (select next mission)

How Phase Switching Works

// Send message to trigger a phase switch:
PostMessage(g_hWnd, WM_PHASE_PLAY, 0, 0);

// Handled in WindowProc:
case WM_PHASE_PLAY:
    pEvent->ChangePhase(WM_PHASE_PLAY);
    break;

// ChangePhase() in event.cpp:
// 1. Clears current toolbar (buttons, gauges)
// 2. Loads the appropriate background image into CHBACK channel
// 3. Creates phase-specific buttons
// 4. Initialises phase state

Navigation Messages

Background Images per Phase