BCM Conflict Core Native Arland Candidate
Full 12-position native Arland production candidate.
- Scenario ID
- {A4F3500000000000}Missions/Production/TB_CC_Arland.conf
- Game mode
- Sandbox
- Player count
- 16
BCM Conflict Core M4.X Native Prototype
Experimental BCM-owned Arland campaign: one US MOB, two ordinary positions, metadata-only OPFOR origin. No diagnostic actor driver.
- Scenario ID
- {A4F2600000000000}Missions/TB_CC_M4X_NativePrototype.conf
- Game mode
- Sandbox
- Player count
- 16
TB Conflict Core M4.1 Arland Registry Fixture
Non-playable portability and registry validation fixture
- Scenario ID
- {A412000000000000}Missions/TB_CC_M4_1_ArlandFixture.conf
- Game mode
- Sandbox
- Player count
- 1
BCM Conflict Core M4.4 Arland Graph Campaign
Production Arland graph campaign integration
- Scenario ID
- {A442000000000000}Missions/TB_CC_M4_4_ArlandGraphCampaign.conf
- Game mode
- Sandbox
- Player count
- 16
TB PvE M1.4B Dedicated Lifecycle Regression
Disposable deterministic forward-base lifecycle regression
- Scenario ID
- {A14B000000000000}Missions/TB_PVE_M1_4B.conf
- Game mode
- Sandbox
- Player count
- 8
TB PvE M1.5 Human Faction Restriction
Production-style dedicated faction restriction regression
- Scenario ID
- {A150000000000000}Missions/TB_PVE_M1_5.conf
- Game mode
- Sandbox
- Player count
- 8
TB PvE M2.1 Linear Frontier Vertical Slice
MOB to three objectives with reversible server-authoritative frontier policy
- Scenario ID
- {A212000000000000}Missions/TB_PVE_M2_1.conf
- Game mode
- Sandbox
- Player count
- 8
TB PvE M2.4 Production Linear Route
Ten-node authored north-to-south campaign route
- Scenario ID
- {A242000000000000}Missions/TB_PVE_M2_4.conf
- Game mode
- Sandbox
- Player count
- 8
TB PvE M3.7 Human Combat Playtest
Production ten-node PvE route for sustained human combat validation
- Scenario ID
- {A370000000000000}Missions/TB_PVE_M3_7_Playtest.conf
- Game mode
- Sandbox
- Player count
- 8