Campaign: missions, briefings, and the victory and defeat movies

[CubeB]

RWE plays skirmish only. The campaign is the largest piece of the original still missing, and the ending movies wait on it: 3.zrb (victory) and 4.zrb (defeat) have nothing to hang off until missions exist (ROADMAP, "The ending movies and the credits belong to the campaign"; B4 #6).

This is an umbrella. Open one issue per piece as you start it, one PR each.

What is there already

• MovieScene and the Smacker decoder; a missing movie file is already a no-op.
• GameSimulation::processVictoryCondition for skirmish, and the igvictory / igdefeat title art is loaded (LoadingScene.cpp).
• ccdata.ccx carries camps/ with per-language briefing folders (Briefs-German/CoreCampaign5.txt and so on). Find where the base game's Arm and Core campaigns live in the shipped archives; they were not under camps/ in totala1-3.hpi or rev31.gp3 at a first look.

Pieces, roughly in order

1. Decode the campaign definition files and the mission fields the original reads from a mission map's OTA: description, win and lose conditions, starting units, the AI's setup. Read docs/TOTALA-EXE.md first, and decode from TotalA.exe with tools/exe/ where behaviour matters.
2. The campaign menus: side select, mission list, the briefing screen with its voice-over.
3. Loading a mission through LoadingScene with its own units and players instead of a skirmish setup.
4. Mission win and lose conditions in the sim. They are sim state, so the four-place rule in CLAUDE.md applies (save, hash, dump).
5. Victory and defeat: the title art, then 3.zrb / 4.zrb, then back to the campaign menu.

🤖 Generated with Claude Code

https://claude.ai/code/session_018moxVoyHDBoHqkw8uqS3HX

[HectorBailey]

Before opening the first sub-issue, three things I could not settle from the data and would like a steer on:

1. Where the base game's campaigns are. ccdata.ccx/CAMPS/ has Arm Campaign.tdf and Core Campaign.tdf for Core Contingency: a [HEADER] with campaignside, then [MISSIONn] blocks of missionfile=AC01.ota, missionname and four localised names, plus Briefs-<language>/ folders. The mission OTAs are in the ordinary map archives (AC01 loads through --map today). totala1.hpi, totala2.hpi and totala3.hpi have no camps/ and no campaign TDF; the only hits are two newcampaign*.pcx bitmaps. So the original's Arm and Core campaigns look hardcoded in the executable rather than in data. Is decoding that table from TotalA.exe in scope for piece 1, or do we ship the base campaigns as our own TDFs in the same format as Core Contingency's?
2. Which piece first, and the order of the menus vs the sim. The list has menus (2) before loading (3) and win/lose (4). A mission needs 1, 3 and 4 before a menu has anything to launch; 2 is the shell around it. Happy to start at 1 and 3 with a --mission command-line path so a mission can be played and tested before any menu exists, if that order suits you.
3. Scope of the mission OTA fields. Skirmish reads the schema's features, specials and start positions. A mission OTA also carries the starting units, the AI's script/profile, and win/lose conditions in fields RWE's parseOta ignores. Do you want the decode of those fields written into TOTALA-EXE.md as its own section before any of them is ported (the way §97 went), or ported field by field as each piece needs it?

I'll open "Campaign 1: campaign and mission definition files" as the first sub-issue once you've answered, unless you'd rather open it yourself.

[CubeB]

1. The base campaigns are data, not hard-coded. ccdata.ccx/CAMPS/Arm Campaign.tdf is the original Arm campaign, not Core Contingency's: its first entry is missionfile=AC01.ota, missionname=1: A Hero Returns, and it has 25 missions. The GOG and Steam releases carry the original campaign disc in the .ccx files; the mission maps are in ccmiss.ccx (AC12.OTA, CC03.OTA, …). TotalA.exe loads a campaign by file name: it has the strings "Arm Campaign", "Core Campaign", "ArmCamp", "CoreCamp" and "The requested campaign file, %s, does not exist.". So read the TDFs from the data, and decode only how the exe finds and reads them: which names it asks for, the [HEADER] and [MISSIONn] fields, and what it does with the Briefs-<language> folders. Don't ship campaign files of our own.
2. Order: yes. Start with 1 and 3 behind a --mission command-line path, then 4, and the menus last.
3. Decode first. Write the mission OTA's campaign fields up as their own section of TOTALA-EXE.md in a docs-only PR, the way Where the nanoframe's shadow is not decided, with addresses #48 went. Then port them piece by piece. The strings to pivot on are MISSIONUNIT DATA, MISSIONFEATURE DATA, MISSIONRULE DATA, GlobalHeader, MissionCriticalUnit, "No GlobalHeader block in mission file!" and "No suitable schema type in mission file!".

Go ahead and open "Campaign 1" yourself.

🤖 Generated with Claude Code

https://claude.ai/code/session_018moxVoyHDBoHqkw8uqS3HX