Unterstütze mich durch ein Kauf in meinem Spreadshirtshop

Battletech Alpha Strike campaign overview

Battletech Alpha Strike campaign overview

Sources:

  • “Broken Sword – Campaign booklet, fan product version 1.0” (BT_AS_Broken_sword.pdf)
  • “The Battle for Brixtania – Campaign booklet, fan product version 1.1” (BT_AS_Schlacht_Brixtania.pdf)
  • “Battle for Damian – Campaign booklet, fan product version 1.0” (BT_AS_damian.pdf)
AI virtual podcast with campaign presentation

1. introduction and overview

This document describes three unofficial fan products for Battletech Alpha Strike campaigns created by me (Sören Spieckermann): “Broken Sword”, “The Battle for Brixtania” and “Battle for Damian”. All campaigns are specially designed for beginners, use the BattleTech Alpha Strike rules and offer an ongoing storyline, tactical depth and the opportunity to take on the role of different factions. They are explicitly not designed as tournament campaigns, but are intended to provide players with “interesting rounds of Battletech Alpha Strike”.

2. main themes and commonalities of the campaigns

2.1. Target group and didactic approach

All three campaigns are primarily aimed at newcomers to the Battletech universe who want to make the leap from individual battles to a more comprehensive campaign structure.

  • Battle for Brixtania”: “”Battle for Brixtania” was specifically designed to introduce new players to campaigns in the Battletech universe.” (BT_AS_Schlacht_Brixtania.pdf, p. 5)
  • “Broken Sword“: “This campaign scenario for Battletech Alpha Strike, specially developed for beginners, takes you into the merciless conflicts of the late Succession Wars (Renaissance era)…” (BT_AS_Broken_sword.pdf, p. 5)
  • “Battle for Damian”: “This campaign scenario for Battletech Alpha Strike, specially developed for beginners, takes you into the merciless conflicts of the Clan Invasion…” (BT_AS_damian.pdf, p. 6)

They emphasize the ongoing storyline, where victories and defeats influence the course of the campaign, as well as the simple Alpha Strike rules for fast and dynamic play. Experienced players who want to introduce new players are also named as a target group.

2.2. Temporal classification and conflict contexts

  • “Broken Sword” and “Battle for Brixtania” are set in the late Succession Wars (Renaissance era; 3020 – 3049).
  • “Broken Sword” focuses on a mercenary unit (“Iron Revenants”) that is lured into a trap on the planet Valentina by the Draconis Combine (House Kurita). The core plot is a fight for survival and an attempt to escape from the planet. Command “Death to Mercenaries” (BT_AS_Broken_sword.pdf, p. 5).
  • “Battle for Brixtania” deals with the battle for the resource-rich planet Brixtania between the Capellan Confederacy(Red Lancers) and the local defense forces/mercenaries(Canopian Highlanders). The planet is of strategic importance for “future operations in the Periphery” (BT_AS_Schlacht_Brixtania.pdf, p. 5).
  • “Battle for Damian” takes place in the era of the Clan Invasion (3050 – 3061), more precisely in the year 3052 after the battles for Tukayyid. Here, Clan Ghost Bear and the Free Republic of Rasalhaag fight over the planet Damian, which contains boranite mines that are essential for modern weapons technology (BT_AS_damian.pdf, p. 6). This conflict is described as a “bloody positional war”.

2.3. Political groups and their motivations

  • Broken Sword:Iron Revenants (mercenaries): Were hired by House Kurita, but then betrayed and must now fight to survive and escape.
  • House Kurita: Executes the “Death to Mercenaries” command and attempts to eliminate the mercenaries on Valentina to “make an example” (BT_AS_Broken_sword.pdf, p. 6).
  • Battle for Brixtania: Capellan Confederacy (Red Lancers): An elite unit of House Liao that seeks to conquer Brixtania in order to “strengthen Capellan economic power” and secure “a strategic base position for future operations in the Periphery” (BT_AS_Schlacht_Brixtania.pdf, p. 7).
  • Brixtania Coalition (Canopian Highlanders): Experienced mercenaries commissioned by the Magistracy of Canopus to “protect the home” and defend the planet. They rely on guerrilla tactics (BT_AS_Schlacht_Brixtania.pdf, p. 5, 8).
  • Battle for Damian:Clan Ghost Bear: Attempts to conquer Damian for good in order to use it as a “supply base for future invasions” and restore the clan’s honor after Tukayyid (BT_AS_damian.pdf, p. 6). Led by Star Colonel Torin Tseng.
  • Free Republic of Rasalhaag (3rd Hussar Company): Defends Damian. Known for their will to resist and their ability to defeat even overwhelming opponents. Led by Major Helga Kaarina, who is expecting reinforcements and needs to buy time (BT_AS_damian.pdf, p. 7-8). The Rasalhaagians fight for their survival.

2.4. Campaign mechanics

All campaigns use the Alpha Strike Quick Start rules, supplemented by rules from the Commander’s Edition.

  • Momentum roll: The player who won the previous mission performs a 1D6 roll, which determines further mission characteristics (e.g. initiative bonuses, additional PV). This simulates the advantage of the successful player. (BT_AS_Broken_sword.pdf, p. 11; BT_AS_Schlacht_Brixtania.pdf, p. 9; BT_AS_damian.pdf, p. 14)
  • Tactical victory in the event of a draw: If neither side achieves the victory condition, the player who has destroyed more of the opponent’s PVs wins. (BT_AS_Broken_sword.pdf, p. 11; BT_AS_Schlacht_Brixtania.pdf, p. 10; BT_AS_damian.pdf, p. 14)
  • Unit pool and PV limits: A unit pool of 500 PV per player is recommended. Each mission has a specific PV limit. (BT_AS_Broken_sword.pdf, p. 10; BT_AS_Schlacht_Brixtania.pdf, p. 9; BT_AS_damian.pdf, p. 11)
  • Card size and layout types: Typically 44 x 34 inches. Layout types include city, landscape and urban terrain. (BT_AS_Broken_sword.pdf, pp. 10-11; BT_AS_Battle_Brixtania.pdf, pp. 9-10; BT_AS_damian.pdf, pp. 14-15)
  • Skill value: Skill 4 by default for all units at the start. (BT_AS_Broken_sword.pdf, p. 10; BT_AS_Schlacht_Brixtania.pdf, p. 9; BT_AS_damian.pdf, p. 11)
  • Mission duration: Maximum 8 rounds, unless otherwise stated. (BT_AS_Broken_sword.pdf, p. 11; BT_AS_Schlacht_Brixtania.pdf, p. 10; BT_AS_damian.pdf, p. 15)

3. differences and further developments of the campaigns

Although they follow a similar basic approach, the campaigns show a development in the depth of detail of the campaign elements:

3.1. Dealing with destroyed units and repairs

  • Battle for Brixtania” (simplest approach): “Mech damage etc. is not carried over to the next battle and there is also no “WarChest” that you can earn in the missions in order to repair or improve your units for the next mission.” There is only an optional rule that units destroyed by ammunition or cockpit hits cannot be used for the next mission. (BT_AS_Schlacht_Brixtania.pdf, p. 7, 9)
  • “Broken Sword” (medium complexity): Destroyed units cannot be used for the next mission (“no field repair possible”). After a “mission pause” they are ready for action again. In the case of ammunition or cockpit hits, the “pause” is increased to two missions. The mercenary units are generally not subject to the “Forced Withdrawal” rule, as they are fighting for their survival. (BT_AS_Broken_sword.pdf, p. 10, 14)
  • “Battle for Damian” (highest complexity): The campaign elements are “even more developed”.
    • Destroyed units: Same as “Broken Sword”, but critically destroyed units (ammo explosion, cockpit hit/crew killed for vehicles) fail for two missions.
    • Repair kits: Each player starts with six repair kits to make a destroyed unit immediately ready for the next mission. This reduces the number of kits. (BT_AS_damian.pdf, p. 11, 13)
    • Damaged units (optional): Units that have lost structure points (but have not been destroyed) may make a repair roll to be fully or partially repaired. (BT_AS_damian.pdf, p. 14)

3.2. Pilot and experience system

  • “Battle for Brixtania” and “Broken Sword”: All units start with skill 4 and there are no explicit rules for pilot survival or experience gain.
  • “Battle for Damian”: Introduction of a detailed system:
    • Pilot survival: When a unit is destroyed, a survival roll (D6) must be made for the pilot.
      • Value 1: Pilot mortally wounded. Replacement pilot with skill 4 for the next mission.
      • Value 6: Pilot wounded. Replacement pilot with skill 4 for the next mission, original pilot does not return until the mission after next.
      • Value 2-5: No effects, pilot saves himself. (BT_AS_damian.pdf, p. 12)
    • Experience gain: At the end of a mission, non-destroyed units that have destroyed at least one enemy unit can make an experience roll (2D6).
      • Value 2 or 12: Skill level of the unit increases by +1 (better).
      • Value 3-11: Skill remains constant.
      • Maximum of two skill increases per player and mission. The order of the rolls is decisive. (BT_AS_damian.pdf, p. 13)
    • Skill restrictions: Within a mission, a maximum of one unit may have skill 1 and two units may have skill 2. All others must be Skill 3 or worse. (BT_AS_damian.pdf, p. 11)

3.3. “Forced Withdrawal” rule

  • “Battle for Brixtania”: The “Forced Withdrawal” rule (forced withdrawal when only half of the internal structure remains) is generally applied in every battle. (BT_AS_Schlacht_Brixtania.pdf, p. 13)
  • “Broken Sword”: The mercenary units (Iron Revenants) are generally not subject to this rule, as they are fighting for their survival. (BT_AS_Broken_sword.pdf, p. 10, 14)
  • “Battle for Damian”: A differentiated application: “In general, the Forced Withdrawal rule applies to Clan units in every battle. Free Republic units are fighting for their survival and are not subject to this rule.” (BT_AS_damian.pdf, p. 17)

3.4. Weather/environmental conditions

  • “Battle for Damian” is the only campaign that introduces an explicit rule for weather conditions. Before each mission, roll 2D6 to influence the line of sight (LOS) (e.g. “Pitch black night with thunderstorm. LOS max. 6 inches” at 2 or 3). Optional hit modifiers can also be added by the weather. (BT_AS_damian.pdf, p. 11-12)

4. important ideas and facts

  • Three beginner campaigns: “Broken Sword”, “Battle for Brixtania”, “Battle for Damian” are designed to introduce new Battletech Alpha Strike players to campaigns.
  • Ongoing narratives: All campaigns offer a coherent story in which mission results influence the further course of the game.
  • Historical Contexts: Set in the late Succession Wars (“Broken Sword”, “Battle for Brixtania”) or the Clan Invasion (“Battle for Damian”), which influences unit selection.
  • Faction focus: Players can take on different roles (Mercenary, House Kurita, Capellan, Canopian Highlander, Clan Ghost Bear, Free Republic of Rasalhaag).
  • Rules evolution: The campaigns show an increasing complexity in the management of units between missions:
    • Brixtania: Simple, no permanent damage or pilot rules.
    • Broken Sword: Introduction of downtime for destroyed units (1-2 missions break).
    • Damian: Detailed system with repair kits, pilot survival (wound/death), experience gain for units and weather effects.
  • Core mechanics: Momentum roll, tactical win on draw, PV limits per mission, standard map sizes and various terrain types are consistent across all campaigns.
  • Different “Forced Withdrawal” application: The forced withdrawal rule is handled differently depending on the campaign and faction in order to increase the narrative tension (e.g. mercenaries and Rasalhaagans fight to the end).
  • Community product: All documents are unofficial fan products by Sören Spieckermann, created with the support of the Battletech community (Strategiespielefreunde Bad Emstal e.V., Discord user Xinthius and “Battletech DE” server).

5. summary

The three campaigns offer an excellent opportunity for Battletech Alpha Strike players to enter the world of campaigns in stages. They start with a very accessible model (“Brixtania”) and then gradually introduce more complex and immersive elements (“Broken Sword”, “Battle for Damian”). “Battle for Damian” in particular stands out for its robust system for pilot survival, experience gain and repairs, as well as the introduction of dynamic weather conditions, resulting in a richer and more consequential gameplay experience. They demonstrate how the Battletech community is actively creating content to enhance and customize the game experience.

Become part of the mission!

Help me to further expand Mechstrategen.de and strengthen the community. Whether through a small donation, donations in kind such as painted mechs or terrain, or simply through your time – every support counts!
Together we make Mechstrategen.de even better!

Clan or Inner Sphere? Doesn't matter - everyone needs to see this. Sharing is the true Mech Warrior code!
Scroll to Top