Kasserine: Baptism of Fire, February 1943
Kasserine: Baptism of Fire, February 1943 Rulebook
Table of Contents
Table of Contents
- 1.0 Introduction
- 2.0 Game Equipment
- 3.0 Setting Up the Game
- 4.0 Sequence of Play
- 5.0 Movement
- 6.0 Zones of Control
- 7.0 Support Fire Markers
- 8.0 Bombardment & Ground Combat
- 8.3 Retreat
- 8.4 Stiff Resistance
- 8.5 Advance After Combat
- 9.0 Supply
- Combat Results Table
- Kasserine Exclusive Rules
- 10.0 Introduction
- 11.0 Reinforcements
- 12.0 Lines of Communication
- 13.0 Enemy Zones of Control
- 14.0 Minefields
- 15.0 Youks-les-Bains Airfield
- 16.0 US Engineers
- 17.0 Prohibited Movement
- 18.0 Victory Conditions
- 19.0 Scenarios
- 20.0 Game Notes
1.0 Introduction
Each game represents an actual or hypothetical battle, as included in the Exclusive Rules.
The map included with the game represents each different battle's terrain. The pieces represent the actual (or hypothetical) units that participated or might have participated in the battle. The System Rules are rules that fit all games using the F&M system, and the exclusive rules are specific to each represented battle.
Note: These rules use the following color system: Red for critical points such as errata and exceptions, Blue for examples of play.
2.0 Game Equipment
See exclusive (scenario) rules.
2.1 The Game Map
The map sheet portrays the battle area. Printed over the terrain features is a hexagonal grid to regulate the movement and positioning of the game pieces throughout the game.
2.2 Charts & Tables
Various visual aids provide the players to collate, simplify and illustrate certain game functions. They are the Combat Results Table (CRT), the Terrain Key, and the Game Turn Record Track (GTRT). Exclusive rules may contain additional charts.
- Consult the exclusive rules to determine the placement of support fire markers. The support fire number may be on the GTRT. The number signifies the number of support fire markers (not points) available each GT.
Important: There has been a major update to the bombardment rules. Players may use these bombardment rules in previous games in the series, however, they have not been subject to play test with all games.
- The GTRT may contain other information pertinent to game play. See the exclusive rules for details.
2.3 The Playing Pieces
The cardboard playing pieces (counters) represent the actual military units that took part in the battle. The different colored units (combat units) represent forces of opposing sides. The numbers and symbols on the counters represent the attack and defense strength, movement capability, and type of unit represented by each counter.
Important: In the system rule diagrams and examples, the exact units may not appear in the current game; however, all designations and terms used are consistent with the units in the current game unless the exclusive rules dictate otherwise. See exclusive rules for unit type symbols.
The diagrams in the system rules label the parts of a leg combat unit (front): Unit Type Symbol, Unit Size Symbol, Unit ID, Parent Formation, Attack Strength, Defense Strength and Movement Allowance. The leg combat unit (back) is the reduced side, a mobile combat unit (front) carries a Mobile Unit Designator, and a support fire marker (front/back) carries a Type Symbol and a Support Strength.
Note: The front side of a combat unit is the full-strength side and the back of the unit is normally its reduced side. For most games in the series, the reduced side shows the unit type symbol having the same background color as the counter. Not all combat units have a reduced side and thus are one-step units.
Important: The exclusive rules will list the specific types of units available in each game.
2.3.1 How to Read Units
Most units contain identifiers (or names) and sizes. The identifier or name of a unit has no bearing on play, except as part of set-up and reinforcement rules. An identifier that lists two numbers separated by a slash represents the battalion number and then the regiment number from which that battalion derives (though that parent regiment may or may not be in the game).
Example: A unit printed with 4/47 is referring to the 4th Battalion of the 47th Regiment. A single number identifier typically refers to a single formation of its type (9 could refer to the 9th Division).
Unit sizes:
- •••: Platoon
- I: Company
- II: Battalion
- III: Regiment
- X: Brigade
- XX: Division
- XXX: Corps
Note: Games may include additional unit sizes. See exclusive rules.
2.3.2 Definition of Terms
Attack Strength: The relative strength of a unit when attacking other units, expressed in terms of attack strength points.
Bombardment Attack: An attack conducted by the active player using support fire markers only. Bombardment attacks take place during each player's Bombardment Phase (8.1).
Defense Strength: The relative strength of a unit when defending against the attacks of enemy units, expressed in terms of defense strength points. See attack strength.
Combat Modifier (Support Strength): The strength of support fire markers. They represent everything from corps artillery, naval support, aerial bombardment and organic mortars used to attack enemy units. The combat modifier (expressed in terms of a "+") value that players may add to the strength of a friendly unit during combat or as an attack strength when conducting bombardment.
Movement Allowance (MA): The number of movement points (MP) a unit may expend in a single Movement Phase. Each hex a unit moves into and/or each hexside crossed forces the unit to expend a given number of MP.
Leg Unit: A unit that is not a mobile unit. It represents any type of unit that lacks inherent conveyance or transport.
Mobile Unit: A unit that is not a leg unit. It represents any type of unit that moves by a means other than by foot. A mobile unit can be anything from tanks to wagons. Only mobile units may move during the Mobile Movement Phase and/or conduct attacks during the Mobile Combat Phase (4.1).
Support Fire Markers: Represent naval gunfire from ships offshore, bombers/fighters providing ground support or interdiction support, or artillery units of all types and sizes not represented as units in the game.
2.4 Game Scale
The exclusive rules will indicate the scale of the map and the time that each game turn (GT) represents.
3.0 Setting Up the Game
Players should determine the side each will play. Players then consult their respective setup instructions in the exclusive rules. The instructions will list the strength and position of each unit in play on the map during the first GT. The exclusive rules:
a) Will indicate the player who is the first (starting) player and the player who will set up first.
b) May assign units specific set-up hexes, general areas near a specific location/hex number, or instruct the players to choose the set-up hexes for their units.
c) Will specify the number and GT of arrival for any reinforcements scheduled for that battle. Players should place reinforcements to the side of the map or place them on the GTRT in the GT box for the GT they will arrive.
4.0 Sequence of Play
Players conduct each game in successive GTs, each turn is composed of alternate player turns. During the GT players maneuver their units and resolve combat according to the sequence outline and within the limitations provided by the rules.
4.1 Sequence Outline
Each GT consists of a First Player Turn followed by a Second Player Turn. One player takes the First Player Turn while the other player plays the Second Player Turn. The GTRT on the map and/or exclusive rules will indicate which player is the first player. Complete each player turn in the order given below. Complete each phase before beginning the following phase.
Support Fire Marker Phase: Both players organize their support fire markers as outlined in 7.0 or as dictated by the exclusive rules.
First Player Turn
Movement Phase: The current (active) player may move any number of his eligible units, as he desires within the limits and restrictions of the rules of movement (5.0), zones of control (ZOC) (6.0) and the exclusive rules. The active player may bring reinforcements onto the map as allowed by his reinforcement schedule and the reinforcement rules.
Important: Mobile units that move during this phase cannot move during the upcoming Mobile Movement Phase.
Bombardment Phase: The active player may conduct bombardment attacks against enemy units (8.1).
Combat Phase: The active player may use his units to attack enemy units (8.2).
Important: Mobile units that participate in combat during this phase cannot conduct combat during the Mobile Combat Phase.
Mobile Movement Phase: Only mobile units can move during this phase. Mobile units that moved during the preceding Movement Phase cannot move this phase. Movement in this phase is otherwise identical to the Movement Phase.
Mobile Combat Phase: Only mobile units can attack this phase. Mobile units that participated in an attack during the preceding Combat Phase cannot conduct attacks this phase. Combat in this phase is otherwise identical to the Combat Phase.
Second Player Turn: After the first player has completed his turn, the second player then conducts his turn using the same procedures and order given for the first player.
Game Turn End Phase: After the second player completes his player turn, the GT ends. If it is the last turn of the game, players determine victory. If there are turns remaining, advance the turn marker one space along the GTRT and conduct that turn using the above procedures.
5.0 Movement
5.1 Procedure
During the Movement Phase, the active player may move any number of his eligible units as he desires.
- Units may move in any direction or combination of directions, up to the limits of each unit's printed MA.
- Always move units one at a time, tracing a path of contiguous hexes through the hex grid.
- As each unit enters a hex, it pays one or more MP from its movement allowance.
5.2 Movement Restrictions
Movement cannot take place out of sequence. Neither player can conduct movement during the opposing player's Movement or Mobile Movement Phase. A player can only move units during his own Movement or Mobile Movement Phase.
- A unit:
a) Cannot expend more MPs than its total printed MA during any one turn.
b) Cannot accumulate unused MPs from phase to phase or from turn to turn, nor can players transfer MP from one unit to another unit.
c) Cannot enter a hex if the unit does not possess enough remaining MPs to pay for the cost to enter, as well as the cost of any hexside terrain the unit crossed.
d) Cannot enter a hex containing an enemy unit.
e) Cannot enter a prohibited terrain hex or cross a prohibited hexside.
f) Cannot exit the map unless specifically allowed by the exclusive rules.
-
Units may have their movement affected by enemy zones of control (EZOC) (6.0).
-
Players may not move a unit that has completed its movement during that same turn except as a retreat or an advance after combat.
Important: There is no minimum number of hexes a unit may move; a unit may not have enough MA to move to any adjacent hex, in which case it may not move at all.
Important: Advance and retreat may take place during a Bombardment Phase, Combat Phase or Mobile Combat Phase. Advance after combat and retreat after combat are not movement and do not require the expenditure of MP.
5.3 Stacking Restrictions
Units cannot stack.
- Only one unit can occupy a hex at the end of any phase.
- A unit may move through hexes occupied by other friendly units at no extra MP cost.
- A unit cannot end its movement stacked with any other unit.
5.4 Effects of Terrain
A unit must expend one MP to enter a clear terrain hex.
Important: Hexes may depict more than one type of terrain. In this case, use the MP expenditure of the terrain with the highest cost in MP.
- To enter other types of hexes, a unit must expend more than one MP.
- The Terrain Key or TEC (normally printed on the map) list each type of hex and hexside terrain with the corresponding MP cost for each type of terrain.
Important: The following examples may not reflect the actual terrain types or movement costs for a particular game. Consult each game's terrain effects for specific MP costs.
Example: A jungle terrain hex costs 3 MPs to enter.
- Hexsides may display other types of hexside terrain features (such as a river) that require additional movement points to cross. This cost is in addition to the cost of the terrain in the hex.
Example: A unit crosses a river (+1 MP) and enters a clear terrain hex (1 MP). The cost to enter that hex would be 2 MP.
- In hex terrain may have a "+" and a number. If that is the case, add that number to the cost of other terrain in the hex.
Example: A unit enters a clear hex (1 MP) that contains a village (+1 MP) and that unit crossed a river hexside (+1 MP). The cost to enter the hex is 3 MP.
5.4.1 Road Movement
A unit that moves from one road hex directly into an adjacent road hex through a road hexside normally expends one-half (½) of a MP, regardless of other terrain in the hex or hexside terrain. See exclusive rules for exceptions.
5.4.2 Trail Movement
A unit that moves from one trail hex directly into an adjacent trail hex through a trail hexside expends only one MP, regardless of other terrain in the hex or hexside terrain.
5.5 Mobile Movement Phase
During the Mobile Movement Phase, the active player may move any number of his eligible units as he desires, subject to the following restrictions:
- Mobile units that moved in the Movement Phase of a player turn cannot move during the Mobile Movement Phase of the same player turn.
- Leg units cannot move during the Mobile Movement Phase.
- Units moving during the Mobile Movement Phase follow the same procedures as used during the Movement Phase (5.1 through 5.4).
6.0 Zones of Control
The six hexagons surrounding each hex constitute the zone of control (ZOC) of any unit in that hex.
Example: The previous diagram shows the hexes (shaded) that are in the zone of control of the unit depicted.
- All units not marked with a black hexagon in either the upper right or the left side of the counter exert a zone of control. ZOC are always in effect, regardless of the phase or the player turn.
- Zones of control extend into all types of terrain and across all types of terrain hexsides.
Exception: Games may have fortifications or other restrictions that will negate the projection of ZOC into specific hexes.
- Enemy and/or friendly units never affect the presence of ZOC.
- If an enemy and friendly ZOC extend into a hex, they have no effect upon each other, i.e., both co-exist. The ZOCs mutually affect the hex.
- If a unit is in an enemy zone of control (EZOC), the enemy unit is also in that unit's ZOC.
6.1 Effects on Movement
ZOCs inhibit the movement of enemy units.
- A leg unit that begins its movement in a hex not in an EZOC that then enters a hex in an EZOC must immediately stop its movement, regardless of the number of MP it has remaining.
- A leg unit that begins its movement in an EZOC can move directly into another hex in an EZOC by expending all its printed MA as long as the terrain is not prohibited and the unit has sufficient MA to expend for the hexside/in-hex terrain.
- Any unit that begins its movement in an EZOC can move into a hex not in an EZOC. The unit would expend the normal MP costs for that hex. It may continue movement normally.
- A leg unit must halt its movement if it later enters another EZOC.
Example 1: The 51st Infantry Regiment can move into the hexes connected by black arrows. It can move from its starting hex directly into hex 2311 or 2413.
Example 2: The 1st Cav can move into the hexes connected by black arrows.
Exception: A unit may not move from EZOC to EZOC across a minefield hexside or to enter a fortification hex; however, this restriction does not apply to commandos. Commandos never pay additional movement costs to enter or exit an EZOC.
- A mobile unit must expend half (round down) of its printed MA (plus the normal cost of terrain) when it moves into an EZOC (i.e., a unit with MA of "7" would expend three movement points to enter an EZOC).
6.2 Effects on Retreat & Advance After Combat
Units retreating after combat cannot retreat into hexes in an EZOC (8.3). Units advancing after combat ignore EZOCs (8.5).
7.0 Support Fire Markers
Support fire markers represent indirect fire assets not represented in the game by actual counters. Support fire markers do not exist on the map as units; they represent the incoming fire from supporting assets.
7.1 Allocation of Support Fire Markers
Important: The exclusive rules may modify the availability and allocation of support fire markers. Players should check the exclusive rules before proceeding further.
Each side has its own pool of support fire markers, allotted by the support fire allotment number printed on each turn box of the GTRT.
- The support fire number equals the total number of support fire markers the players will receive at the beginning of that GT.
- If the allotment of support fire markers indicated on the GTRT is less than the total quantity of markers in the pool for that player's side, that player must select from the lowest-valued markers before selecting higher-valued markers. Players must select support fire markers in order from lowest to highest.
- If a box has two numbers, the first number is the support fire marker allotment for the first player, the second number is the support fire marker allotment for the second player.
Example: "8/9" printed in the first GT box indicates the first player has 8 support fire markers, and the second player 9 support fire markers.
7.2 Support Fire Application
All support fire markers function the same, though markers may have different printed "+" values (the combat modifier) and different icons.
Exception: Bombardment range (8.1.1).
- See the scenario instructions for allocation of support fire markers.
- Support fire markers used during the Bombardment Phase or any Combat Phase are not available again during the same GT.
- Once used, return support fire markers to the player's pool. They are not available for the remainder of the current GT but may be available in subsequent GTs.
- Players may not accumulate support fire markers from GT to GT. If not used during the GT allotted, players must return them to their respective pools.
- Players randomly pick support fire markers from the pool (unless scenario rules instruct otherwise) when allocated to bombardment and/or combat. Players must place them face down, meaning the "+" value is not showing.
- Players can only use a support fire marker once during each GT.
- The value represents the combat strength that players may apply to bombardments or combats that occur during the turn. Whether as the attacker or the defender, the applying player places his support fire marker(s) and then adds the support fire markers "+" number to his total attack or defense value.
- A player may not divide or split the "+" value of a support fire marker among different targets. A player may only apply each support fire marker to one target hex only.
- Combat results (bombardment and ground combat) have no effect on the allotment of support fire markers during the current or any future GT, except when stipulated differently by the exclusive rules.
Example: If two 4-4-10 units are attacking a 2-3-8 unit; the total attack value is "8". If the attacking player has added two "+2" support fire markers, the final attack value becomes "12". If the defending player has added one "+6" support fire marker to that same combat, the final defensive value would then become "9".
8.0 Bombardment & Ground Combat
There are two types of combat: bombardment which takes place during the Bombardment Phase (8.1), and ground combat which takes place in the Combat or Mobile Combat Phases. The rules below apply to both bombardment and ground combat.
- The active player is the attacker and the inactive player is the defender, regardless of the strategic or tactical situation.
- Combat is not mandatory. There is no requirement for unit to attack, although a defending unit cannot avoid combat.
- A single defending unit can be the subject of an attack in each of the Bombardment, Combat and the Mobile Combat Phases; however, it can only suffer one attack in each of the above phases.
- A single attack may only attack one defending hex (i.e., attackers may not attack more than one hex during a single attack).
- There is no requirement for an attacker to declare all his intended attacks at the outset of the Bombardment or Combat Phase. He can declare each eligible attack as he reviews the map and conducts each individual attack.
- Players must resolve each attack prior to conducting any other attacks.
- The attacker can resolve attacks in any order the attacker wishes, provided he resolves each combat before declaring the next combat.
8.1 Bombardment
During the Bombardment Phase, the active player may conduct attacks using support fire markers only.
- Bombardment attacks do not require a friendly unit to be adjacent to the enemy units attacked.
- Friendly ground units do not participate in a bombardment in any way, including advance after combat. Bombardment does not affect friendly units except as outlined in 8.1.3.
- Each support fire marker may only target one enemy occupied hex.
- A maximum of two markers may bombard the same hex during the same player turn.
- Markers may be of any value from among the markers drawn from the player's pool.
- Once a player uses a marker, follow the procedures outlined in the exclusive rules to determine the marker's eligibility for reuse in a later game turn.
8.1.1 Range
A player may use support fire markers to bombard targets anywhere on the map. The exclusive rules may assign specific ranges for certain types of support fire markers.
8.1.2 Procedure
To conduct a bombardment, the active player may select any enemy unit that is in range of the support fire markers used (8.1.1). Follow the procedures below, in the given order, for each bombardment.
-
The attacker identifies the enemy unit he will bombard.
-
He may select a maximum of two support fire markers, stating the number he has selected and their total strength.
-
Calculate the combat differential by totaling the support strength value minus the total defending unit's strength value. Locate the line on the CRT that matches the terrain in the defender's hex (8.2.2).
Exception: Do not apply hexside terrain (8.2.2).
- Next, on that line locate the column on the CRT that corresponds to the final combat differential. Roll one six-sided die and cross-reference the result within the combat differential column on the CRT. Apply the results immediately.
8.1.3 Results
Apply the results the same as ground combat with the following exceptions:
Ae, A1, A2, A3 & Ex: Treat as no result.
(A): Apply this result only if there is at least one unit friendly to the bombarding player adjacent to the hex bombarded (friendly fire).
8.1.4 Terrain Effects
Players may use bombardment regardless of intervening terrain or units (enemy or friendly). It is not subject to line of sight restrictions, except when stipulated differently by the exclusive rules. In all cases, the defending units benefit fully from the terrain in the hex they occupy (not hexside terrain) per the CRT.
8.1.5 Bombardment Retreat
Conduct retreat after bombardment using the procedures outlined in 8.3.
- The retreating unit must, if possible, retreat farther away from the closest enemy unit.
- If there are no enemy units on the map, the unit must retreat towards the closest friendly unit.
8.2 Ground Combat
Ground combat can only take place when friendly units are adjacent to enemy units.
- The active player may declare any number of attacks by eligible units as he wishes.
- The attacking player may decide which of his units will be participating in an attack against which defending units.
- A mobile unit cannot attack in both the Combat Phase and again in the Mobile Combat Phase of the same player turn.
- There is no requirement for all adjacent units to attack.
- Units that do not participate in one attack may participate in a later attack against another hex if the unit meets all other requirements.
- A player may attack a unit from all adjacent friendly occupied hexes.
- A unit cannot attack across a prohibited/restricted hexside or into a hex prohibited to the attacking unit.
- The type of terrain the attacking unit(s) occupy has no effect on their eligibility to attack.
- All attack and defense strengths are unitary. A player cannot divide a unit's strength among different combats, whether as the attacker or the defender. A unit may not combine its attack and defense strengths for any reason.
8.2.1 Combat Procedure
Follow the procedures below, in the given order, for each attack.
a) The attacker states the quantity and the strength of his attacking units, and the enemy unit that is the subject of the attack. Once declared, the attacking player cannot call off an attack.
b) Both players may select available support fire markers in support of the current combat. This is a five-step process:
-
The attacking player may select one support fire marker placing it value-side down near the battling units to indicate it will support that combat.
-
The defending player may then select one support fire marker placing it value-side down near the battling units to indicate it will support that combat. The defender may do this whether the attacker did or did not place a support fire marker.
-
The attacker may then select a second (one additional) support fire marker. He may do this whether either player did or did not already apply a support fire marker.
-
Finally, the defender may select a second (one additional) support fire marker. He may do this whether either player did or did not already apply any support fire markers.
-
Both players reveal their support fire marker values (flip the markers over).
Important: After each step, neither player can change his mind about having placed, or not placed, a support fire marker in a previous step.
c) Each player adds the combat strengths of his ground units and support fire markers into one total.
d) Calculate the combat differential by subtracting the defender's total from the attacker's total. Locate the line on the CRT that matches the terrain in the defender's hex, including hexside terrain. Then on that line locate the column on the CRT that corresponds to the final combat differential. Roll one six-sided die and cross-reference the result within the combat differential column on the CRT. Apply the results immediately.
8.2.2 Effects of Terrain
Only defending units benefit from the terrain in the hex they occupy and/or that hex's hexside terrain feature. The terrain within the hexes occupied by attacking units has no effect upon combat.
- Defending units do not benefit from river or ditch hexsides unless all the attacking units are attacking that defending unit across a non-bridged river or ditch hexside into that hex. If all units are attacking across a river and at least one of the units is attacking across a bridged hexside, use the bridged line on the CRT.
- The effect of terrain on combat is an integral part of the CRT. Refer to the terrain in the defending unit's hex and/or hexside and cross-reference that terrain type with the combat differential (8.2.1).
Important: River hexsides contain a bridge wherever a road crosses a river. If at least one attacking unit is attacking across a bridged river hexside, that attack is an attack across a bridge (not across a river) when resolving an attack on the Combat Results Table (CRT).
Important: Hexes may depict more than one type of terrain and may have hexsides that impact combat. In this case, use the terrain most beneficial to the defender.
8.2.3 Fortifications
If a game includes fortifications (whether printed, or as counters), the following applies to any unit occupying a hex containing a fortification:
- Double the printed defense strength of a unit.
- Halve (round down) the combat modifier (the "+" value) of an attacker's support fire marker when applied to a fortification hex.
- This rule does not apply to support fire markers applied by the defending player.
8.2.4 Combat Resolution
The combat results listed on the CRT are as follows:
De: Eliminate the defending unit(s).
D3: The defending unit(s) must retreat three hexes.
D2: The defending unit(s) must retreat two hexes.
Ex: Flip one attacking unit and the defending unit to their depleted side (or eliminate if already depleted or a one-step unit). Among multiple attacking units, the attacker chooses the unit to deplete.
A1: The attacking unit(s) must retreat one hex.
A2: The attacking unit(s) must retreat two hexes.
A3: The attacking unit(s) must retreat three hexes.
(A): Deplete one adjacent unit (or eliminate it if already depleted or a one-step unit). If conducting bombardment, this result applies if friendly unit is adjacent to enemy unit being bombarded.
Ae: Eliminate all attacking units.
•: No Effect.
* Note: The retreating player may choose to ignore his retreat requirement by declaring stiff resistance and depleting his unit instead (8.4).
** Note: On a De, or Ae result, eliminate all units. Do not deplete two-step units, eliminate them.
Important: If the combat result is a retreat, the retreating player retreats his own units in accordance with the retreat rules (8.3).
8.3 Retreat
When a combat result requires a unit to retreat, the owning player must immediately attempt to move that unit the indicated number of hexes away from its current hex. A retreat is not movement and does not require the expenditure of movement points.
Important: If a rule states that a unit is to deplete, eliminate the unit will if already depleted or is a one-step unit.
- If a unit cannot retreat at least one hex (for any reason), eliminate the retreating unit (this does not nullify the retreat).
- A unit should (if possible) end its retreat closer (in hexes) to a friendly map edge (or a friendly source of supply).
- If possible, a retreating unit must retreat along a path of vacant hexes (not occupied by other friendly units). A unit may retreat through friendly occupied hexes if no other retreat route of vacant hexes is possible. See 8.3.1 for effects.
- Under no circumstances may a unit retreat into or through a hex occupied by an enemy unit or a hex in an EZOC.
Important: Friendly units and friendly units with a ZOC into a hex do not negate any EZOC into that same hex for the purposes of retreat.
- A unit may not retreat into or through prohibited terrain (an all-sea hex).
- Seaborne units required to retreat to a sea hex must deplete (scenario rules will identify units that may be seaborne and may supersede this rule).
- A unit that must retreat must stop its retreat the number of hexes away required by the combat result retreat number (from its original combat hex). If the unit can retreat at least one hex but cannot retreat the required number of hexes for any reason, deplete the unit in the last hex to which it can legally retreat. If depleted, then eliminate the unit.
- Unless specifically stated in exclusive scenario rules, units may not retreat off the map.
8.3.1 Displacement
If a retreating unit's only available final hex in a retreat path is occupied by another friendly unit, the retreating player may choose to displace (move) that other friendly unit from its hex to one adjacent hex as if that other friendly unit was also retreating because of combat.
- Displacement is voluntary; a retreating unit unable to retreat because of the presence of other friendly units may deplete instead of displacing a friendly unit.
- A retreating unit may not displace a friendly unit if any eligible vacant hex is available.
- Displacements cannot be into a prohibited hex, into an EZOC, or into a hex in which the displaced unit would stack with another unit.
- After the displaced unit has moved, the retreating unit may retreat into the displaced unit's formerly occupied hex.
- A displaced unit can displace another friendly unit using the same procedure.
- The displacement of units may continue until all units are in a hex that does not contain a friendly unit.
- A given unit may displace more than once in a phase.
- An attacker's displaced unit is ineligible to conduct an attack during the remainder of the attacker's turn.
- A retreating unit does not displace a friendly unit when moving through that other unit's hex during a retreat, but only if ending a retreat in the other unit's hex.
8.4 Stiff Resistance
Instead of obeying a retreat combat result, a player may declare stiff resistance. The player makes this decision after the combat die roll. A player may use stiff resistance when defending against bombardment and ground combat.
- When declaring stiff resistance, there is no requirement to retreat.
- The unit conducting stiff resistance is immediately depleted. If the attacker declares stiff resistance, any unit that does not retreat must suffer depletion.
- A player may opt to declare a depleted or one-step unit to offer stiff resistance to avoid the retreat combat result. The player must eliminate the depleted or one-step unit and still fulfill the requirements of the stiff resistance. This prevents any advance after combat into that combat hex (8.5).
8.5 Advance After Combat
A player can only advance after combat following a retreat combat result on an attacked (defending) enemy unit (i.e., D2 or D3). Advance after combat does not take place after an Ex or De result.
- A defending unit may never advance after combat.
- There is no advance after combat when conducting a bombardment.
- When an enemy unit retreats due to combat, it will leave a path of vacant hexes behind it, called the path of retreat. If a unit was unable to retreat the required number of hexes, the retreat path is the last hex into which the retreating unit could legally retreat. This includes units when unable to complete the entire retreat (8.3).
- Any or all units that participated in the combat that caused the retreat are then eligible to advance along the path of retreat.
- The decision to advance after combat must come immediately after the retreat is complete.
- Advance after combat is voluntary and the owning player always determines which units and how far they advance.
- Advancing units ignore all EZOC along the entire path of retreat.
- Unit(s) advancing after combat may end their movement in any of the hex(s) along the path of retreat, but they may not stray from the path of retreat while moving.
- If multiple units advance after combat, no more than one unit may end its movement in any one hex of the path of retreat.
- After an advance after combat, an advancing unit is not eligible to attack or perform any other activity during that player turn (unless specified otherwise by an exclusive rule).
- An advanced unit is subject to attack by any eligible enemy units in the immediately following enemy Combat Phase, just like any other unit.
9.0 Supply
There are no supply rules (unless otherwise noted in a specific game's exclusive rules). All units are always in supply. Isolated or surrounded units suffer no penalties.
Combat Results Table
Column numbers 1 to 12 are added for reference; the printed table has none. Each terrain row lists its own combat differentials from the left. Results in bold are No Effect when conducting bombardment.
| Defender Terrain | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Mountain | 0 | +1 | +2,+3 | +4,5 | +6,7 | +8,9 | +10 | |||||
| City, Rough, River | −2 | −1 | 0 | +1 | +2,+3 |
- Attacks at less than the lowest differential are resolved at the lowest differential.
- Attacks at greater than +10 are resolved as +10 attacks.
- When conducting bombardment treat the results in Bold as No Effect.
- De**: The defending unit is eliminated.
- D3*: The defending unit must retreat three hexes.
- D2*: The defending unit must retreat two hexes.
- Ex: One attacking unit and one defending unit must be flipped to their reduced side. If already reduced or is a one-step unit the unit is eliminated. Among multiple attacking units, the attacker chooses the unit to deplete/eliminate.
- A1*: All attacking units must retreat one hex.
- A2*: All attacking units must retreat two hexes.
- A3*: All attacking units must retreat three hexes.
- (A): One attacking unit must be reduced. If unit is already reduced or a one-step unit it is eliminated. Among multiple attacking units, the attacker chooses the unit to reduce/eliminate. If conducting bombardment, this result only applies if a friendly unit is adjacent to the enemy unit being bombarded.
- Ae**: All attacking units eliminated.
- •: No Effect.
Kasserine Exclusive Rules
Source: "Kasserine: Baptism of Fire, Exclusive Rules" (© 2010, Decision Games, file tag KasserineRules_V3), sections 10.0 to 20.0, as printed. Typographical errors in the printed text (for example "hexisde", "FORITIFIED" and "rouge") are reproduced as printed.
10.0 Introduction
Kasserine is a simulation of the Axis offensive against the inexperienced US II Corps in Tunisia during late February 1943.
10.1 First Player
The Axis player is considered the first player throughout the game (see 3.0).
11.0 Reinforcements
Enter reinforcements in the hexes listed, or in any hexes within the hex-range listed (inclusive) at the beginning of each respective player's movement phase or mobile movement phase (except per 15.0). A unit may move immediately during the same turn it arrives on the map; however, no unit may arrive and end its movement stacked in the same hex with any other unit.
11.1 Quantity of Reinforcements
Reinforcements generally arrive during specific game turns, though various reinforcements from both sides only arrive if specific events have occurred (even if only momentarily), and are titled as such below. If a titled event does not occur, the indicated reinforcements listed under that event may not arrive on the map. Note that the term "Axis" refers to German or Italian units, and the term "Allies" refers to US or other Allied units.
Germany (Axis)
Game Turn One
| Unit Type | Hexes |
|---|---|
| 6-5-10 | 3918-3920 |
| 5-3-12 | 3918-3920 |
| 3-4-11 | 3918-3920 |
| 3-4-11 | 3918-3920 |
| 2-2-9 | 3918-3920 |
| 2-2-9 | 3918-3920 |
| 5-3-12 | 3726 |
| 2-2-9 | 3726 |
| 5-3-12 | 3225 |
| 3-4-11 | 3225 |
| 3-4-11 | 3225 |
| 2-2-9 | 3225 |
Game Turn Two
| Unit Type | Hexes |
|---|---|
| 3-2-16 | 2526 |
Game Turn Four
| Unit Type | Hexes |
|---|---|
| 2-2-11 | 3920 |
| 1-2-9 | 3921 |
| 3-2-16 | 0623-1423 or 2126-2926 |
| 4-3-12 | 0623-1423 or 2126-2926 |
| 4-4-11 | 0623-1423 or 2126-2926 |
| 4-4-11 | 0623-1423 or 2126-2926 |
| 2-2-9 | 0623-1423 or 2126-2926 |
| 4-3-9 | 0623-1423 or 2126-2926 |
Game Turn Five
(Only if any Axis unit has captured Sbeitla; if not, delay each turn until captured ):
| Unit Type | Hexes |
|---|---|
| 3-2-11 | 0623-1423 or 2126-2926 |
| 3-3-11 | 0623-1423 or 2126-2926 |
| 2-1-7 | 0623-1423 or 2126-2926 |
| 2-1-7 | 0623-1423 or 2126-2926 |
United States (Allies)
Game Turn One
| Unit Type | Hexes |
|---|---|
| 1-3-7 | 0724-1223 |
| 2-2-9 | 0724-1223 |
| 2-1-16 | 0724-1223 |
| 3-3-12 | 3906-3911 |
Game Turn Two:
| Unit Type | Hexes |
|---|---|
| 1-2-7 | 0105 |
| 2-1-11 | 3906-3911 |
| 3-2-12 | 2701 |
| 1-4-6 | 1601 |
Once any Axis unit enters any hex west of Kasserine (2014)
| Unit Type | Hexes |
|---|---|
| 1-2-7 | 3906-3911 |
| 2-3-7 | 3906-3911 |
| 1-1-6 | 3906-3911 |
| 2-1-10 | 3906-3911 |
| 2-5-7 | 2701 |
| 2-3-7 | 2701 |
| 1-1-7 | 2701 |
| 1-1-7 | 2701 |
Once any Axis unit captures Sbeitla (2706)
| Unit Type | Hexes |
|---|---|
| 1-2-7 | 0104 |
| 2-3-7 | 0105 |
Once any Axis unit enters any hex north of Sbeitla (2706)
| Unit Type | Hexes |
|---|---|
| 2-2-12 | 1301-1901 or 2401-3001 |
| 2-1-12 | 1301-1901 or 2401-3001 |
| 2-1-12 | 1301-1901 or 2401-3001 |
| 2-2-11 | 1301-1901 or 2401-3001 |
| 1-2-7 | 1301-1901 or 2401-3001 |
Once any Axis unit is adjacent to Thala (2003) or Tebessa (0306)
| Unit Type | Hexes |
|---|---|
| 3-2-12 | 0104 |
11.2 When Reinforcements Arrive
Reinforcements arrive at the beginning of a player's movement phase. A unit arriving when the movement phase begins must expend movement points in the first hex entered normally, and may then continue to move thereafter. Mobile units that did not arrive during the movement phase may arrive at the beginning of the mobile movement phase instead, and may continue to move normally thereafter.
11.3 Where Reinforcements Arrive
In the hexes or range of hexes listed under 11.1.
11.4 Reinforcements and Combat
Reinforcements may participate in combat normally during the combat phase of the same turn they arrive. If a reinforcement unit's arrival hex is occupied by any enemy unit, the reinforcement may not arrive until a game turn wherein that hex is no longer occupied by any enemy unit.
12.0 Lines of Communication
Each side has supply symbols along the edge of the map, representing their lines of communication to rear areas off the map (they also function as entry hexes for reinforcing units). If any supply symbol hex is currently occupied by an enemy unit, the side that lost its supply symbol will lose one support fire marker (per each supply symbol hex currently occupied by an enemy unit) from each subsequent game turn's allotment while that supply symbol hex is occupied by any enemy unit.
13.0 Enemy Zones of Control
Reinforcements may be placed into an enemy zone of control, but must abide by the normal rules (see 6.0).
13.1 US Rangers
The US Commando unit (which represents the US 1st Ranger Battalion) may always ignore enemy zones of control.
14.0 Minefields
US minefield hexsides are printed on the map and are considered permanent terrain features that can neither be created nor destroyed during the course of the game. US minefields remain friendly to the US throughout the game. US minefields do not become friendly to Axis units when captured; their effects remain throughout the game.
14.1 Friendly Minefields
US minefields have no combat effects on any Allied units, though Allied units must expend +2 movement points to cross any US minefield hexside.
14.2 Enemy Minefields
An Axis unit may only move across a US minefield hexisde if it occupies an adjacent hex at the beginning of its movement. An Axis unit that moves across a US minefield hexside must expend all its movement allowance to do so and stop in the entered hex.
An Axis unit may retreat through a US minefield hex, but is depleted as a result (or eliminated if already depleted or a one-sided unit).
NOTE: zones of control extend into US minefield hexes normally. No unit (except commando units) may move from EZOC to EZOC across a minefield hexside.
Any Axis attacks on any Allied unit across a minefield hexside must be resolved using the minefield terrain type on the Combat Results Table. US attacks on any Axis unit across a US minefield hexside suffer no penalty.
14.3 FORITIFIED BOXES
The three US minefield hexes are considered fortified boxes. They are minefields per 14.0, except any US unit occupying a fortified box hex may ignore any retreat result (whether a defender retreat or an attacker retreat). Any retreating US unit outside a fortified box must continue its full retreat normally; its retreat is not cancelled by merely moving into or through a fortified box.
German units never derive any benefit for occupying a fortified box.
15.0 Youks-les-Bains Airfield
The towns of Thala and Tebessa represent the routes to the Youks-les-Bains airfield (not depicted on the map). As such, if any German or Italian unit captures Thala (2003) or Tebessa (0306), the German player will then receive two additional reinforcements as of the game turn after Thala or Tebessa has been captured (even if only momentarily).
| Unit Type | Hexes |
|---|---|
| 3-4-11 | 3909 |
| 3-4-11 | 3911 |
As per 11.2, these units arrive at the beginning of the movement phase (not the mobile movement phase), and may move normally per 11.2 unless 11.4 applies.
16.0 US Engineers
Any Allied unit currently within a US engineer unit's movement allowance (counted in hexes, not by MP), including an engineer unit itself, is assumed to be fortified per 7.5.
17.0 Prohibited Movement
Movement into or through grayed "Prohibited" hexes is forbidden to all units.
17.1 Fredendall's "Penny Packets"
During the first two game turns, no Allied unit located west of the Kasserine (2014) hex row may move during the movement phase or the mobile movement phase (including arriving reinforcements after they've moved onto the map). After the second game turn, all units may move normally.
18.0 Victory Conditions
The German player wins the game if he can, at any time (even if only momentarily) capture at least three of the red objective hexes printed on the map; they include the towns Sbeitla (2714), Tebessa (0306), Thala (2003) and the red star objective hexes 0104, 0105 and 1601. To qualify as "captured," an Axis unit must either currently occupy or be the last to have occupied a particular objective hex. Further, each captured objective hex, furthermore, must not be within any enemy unit's zone of control.
If the German player has only captured two of the red objective hexes (at any time, even if only momentarily) the game is a draw until the German player captures a third objective hex. If the German player fails to capture more than one of the red objective hexes before the end of the last game turn, the game is a US victory.
Source note: section 11.1 prints the Sbeitla hex as 2706, while section 18.0 prints it as 2714. Both are reproduced as printed.
19.0 Scenarios
Kasserine has one historic scenario of the Axis assault into the Kasserine Pass, as well as the US attempt to prevent the Germans from breaking through toward the Youks-les-Bains airfield.
Set-up the following units in the hexes indicated below. The map is printed with the set-up locations of each starting US (and Allied) unit included in the game. Set-up locations have no other impact on game play.
Germany: No Axis units begin the game on the map.
United States
| Unit Type | Hexes |
|---|---|
| 1-3-7 | 3718 |
| 1-2-7 | 3922 |
| 1-2-7 | 3722 |
| 3-2-12 | 3819 |
| 2-1-14 | 2714 |
| 2-3-11 | 2814 |
| 2-3-11 | 3911 |
| 2-1-11 | 3810 |
| 3-2-12 | 3811 |
| 1-2-7 | 1704 |
| 1-3-7 (E) | 0804 |
| 2-3-11 | 0312 |
20.0 Game Notes
The Battle for Kasserine Pass effectively decimated the inexperienced US II Corps, and presented an acute threat to the Allied rear areas in Algeria. In game terms, a US defeat is already underway when the scenario begins (Gen. Fredendall had sown the seeds of the II Corps' defeat well before the first turn of the game). However, Gen. Rommel's victory at the Battle for Kasserine Pass was not total; the Germans had routed the US II Corps, it is true, but not thoroughly. After the Germans' initial blow, US forces began to regroup and show a more spirited defense as the German forces pushed towards Algeria. Rommel advanced towards the towns of Thala and Tebessa (beyond which led to the Youks-les-Bains airfield to the northwest) but could not break through the stiffening US resistance to capture either town (aided in part by some ad hoc Allied units that arrived in Thala to bolster its defense, and incessant barrages from the US 9th Infantry Division's artillery).
Rommel's problems were always the same in North Africa…an interminable lack of men and matériel. Despite his victory at Kasserine, Rommel was unable to capture Thala or Tebessa, and lacked enough forces to advance to the Youks-les-Bains airfield, which would have been a severe setback for Allied forces in Tunisia when the Luftwaffe was still marshalling parity with the Allies in the air (and even occasionally air superiority, as occurred during the opening phase of the Battle of Kasserine Pass). Fortunately for the US, the Germans were unable to push into Thala or Tebessa, eventually forcing Rommel to withdraw beyond the range of US artillery, leaving the US II Corps considerably weaker, though considerably wiser.
The situation in Kasserine is typical; the attacking player possesses a stronger force (and is thus on the offensive) with an initial superiority of support fire assets. However, he must thrust quickly to seize his objectives before the defending player begins to muster his reinforcements and accrue support fire. In that regard, the defending player must stall for time, and thereby attempt to deny the attacking player the map's objective hexes until after the last turn of the game. US units are weaker than the German units, but the German player must be careful not to suffer too many "Ex" (Exchange) results, especially when the trade-off is unprofitable; it's not a wise strategy to routinely lose a company of tanks to capture an enemy position. The most obvious solution to this dilemma is to conduct attacks with panzers and infantry (in the event of an "Ex" result, or the occasional "(A)" result, the German player can then choose to deplete an infantry battalion instead of a valuable schwere panzer battalion). This is quite suitable as a game mechanic because it compels players to employ "combined arms" tactics, which had been shown to be a superior tactical doctrine during the Second World War. Unfortunately, however, infantry are generally too slow to keep up with tanks, although the German player in Kasserine is provided with a handful of mechanized infantry battalions (i.e., panzer grenadiers), which can keep pace with the panzers.
That being said, there may be occasions whereby the German player may opt to venture his panzer battalions well ahead of the main body to maintain momentum, or perhaps to exploit a weakness in the US lines. Gen. Rommel orchestrated several such attempts…not all of which were successful (several of Rommel's armored thrusts were beaten back by US artillery barrages). To that point, the US player's circumstance in Kasserine is quite manageable, actually; there are adequate Allied reinforcements to form a respectable defense, especially considering the map's rugged terrain. However, the American units are brittle, and so the US player should usually retain a small reserve to check any unexpected breakthroughs (incidentally, the German player should maintain a reserve as wel—even if only a single A.T. battalion—to counter infiltrations by enemy light tank or recon battalions that may attempt to capture Axis supply hexes). The US player must also be careful not to over-commit to one area of the battlefield; most of the German units are mobile, allowing the German player to redirect the focus of his assault with ease. In that regard, the key to a rapid German advance is the trails and roads. The US player must defend critical junctions, particularly those wending in and through broken or rouge terrain hexes; an undefended trail or road can give the German player a sudden opportunity to blitz through the Allied player's lines, especially if he has panzers primed to exploit during the mobile movement phase.
Indeed, throughout the long history of warfare, roads have often been the key to victory, particularly in direct proportion to the terrain of the battlefields. Kasserine exemplifies this truism well, especially because of the generous movement allowances of most mobile units in the game. A battalion of tanks can cover a fair distance while traveling along an extended wadi, but can cover nearly half of the map if moving down an open road. Like the old adage says, 'All roads lead to Rome'...or in this case, Tebessa.