Mortain Counterattack: The Drive to Avranches Rulebook

Table of Contents

Table of Contents

• 1.0 Introduction
• 2.0 Game Equipment
  • 2.1 The Game Map
  • 2.2 Charts & Tables
  • 2.3 The Playing Pieces
    • 2.3.1 How to Read Units
    • 2.3.2 Definition of Terms
  • 2.4 Game Scale
• 3.0 Setting Up the Game
• 4.0 Sequence of Play
  • 4.1 Sequence Outline
• 5.0 Movement
  • 5.1 Procedure
  • 5.2 Movement Restrictions
  • 5.3 Stacking Restrictions
  • 5.4 Effects of Terrain
    • 5.4.1 Road Movement
    • 5.4.2 Trail Movement
  • 5.5 Mobile Movement Phase
• 6.0 Zones of Control
  • 6.1 Effects on Movement
  • 6.2 Effects on Retreat & Advance After Combat
• 7.0 Support Fire Markers
  • 7.1 Allocation of Support Fire Markers
  • 7.2 Support Fire Application
• 8.0 Bombardment & Ground Combat
  • 8.1 Bombardment
    • 8.1.1 Range
    • 8.1.2 Procedure
    • 8.1.3 Results
    • 8.1.4 Terrain Effects
    • 8.1.5 Bombardment Retreat
  • 8.2 Ground Combat
    • 8.2.1 Combat Procedure
    • 8.2.2 Effects of Terrain
    • 8.2.3 Fortifications
    • 8.2.4 Combat Resolution
• 9.0 Supply
• Combat Results Table (System Rules)
• 10.0 Introduction
  • 10.1 First Player
• 11.0 Reinforcements
  • 11.1 Quantity of Reinforcements
  • 11.2 Allied Replacements
  • 11.3 German Replacements
• 12.0 Lines of Communication
• 13.0 The Start Line (Set-Up)
• 14.0 Unique Terrain
  • 14.1 Hedgerows
  • 14.2 See River
• 15.0 Hill 317
• 16.0 Support Fire Random Draw
• 17.0 The 116th Panzer Division
• 18.0 Surprise
• 19.0 Victory Conditions
  • 19.1 Exiting the Map
  • 19.2 US Victory
• 20.0 Scenarios
• 21.0 Game Notes
• Integrated Combat Results Table

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.

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.

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.

[Diagram: Leg Combat Unit, front. Labels: Unit Type Symbol, Unit ID, Attack Strength, Unit Size Symbol, Parent Formation, Defense Strength, Movement Allowance.]

[Diagram: Leg Combat Unit, back (reduced side).]

[Diagram: Mobile Combat Unit, front. Labels: Mobile Unit Designator. Key: Black box = Leg Unit; Red box = Mobile Unit.]

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.

[Diagram: Support Fire Marker, front and back. Labels: Type Symbol, Support Strength.]

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.

• 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.

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.

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.

• 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: 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.

Example: The previous diagram shows the hexes (shaded) that are in the zone of control of the unit depicted.

• 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.
• 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.

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.

[Diagram: a unit that does not exert a ZOC.]

• 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.

• 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).

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.

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, 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.

1. The attacker identifies the enemy unit he will bombard.
2. He may select a maximum of two support fire markers, stating the number he has selected and their total strength.
3. 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).

4. 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 of an attack.

b) Both players may select available support fire markers in support of the current combat. This is a five-step process:

1. 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.
2. 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.
3. 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.
4. 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.
5. 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: 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.

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).

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 (System Rules)

The system Combat Results Table as printed in the Fire & Movement System Rules. Columns are numbered 1 to 12 for reference; each terrain row lists its own combat differentials from the left. Results in bold are No Effect when conducting bombardment. The Integrated Combat Results Table at the end of the exclusive rules is the table used for Mortain Counterattack.

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.

10.0 Introduction

Mortain Counterattack is a simulation of the German counterattack after the Allied breakout from the Normandy beachhead. The 47th Panzer Corps was to drive toward the city of Avranches to cut off George Patton's US Third Army from its supply lines. Under direct orders from Hitler, the Germans had assembled the best of their remaining panzer divisions (2nd, 1st SS, 17th SS and 2nd SS) to break through the Allied lines around Mortain, opening the route to Avranches. Facing these veteran German units is the exhausted but reinforced US 30th Infantry Division. Its defense was centered in Mortain and the nearby Hill 317, the dominant height in the area. A quick German victory would have potentially severe repercussions for the Allies; anything less would be just anther lost German opportunity.

10.1 First Player

The German player is 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. 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

German reinforcements arrive during game turn 2 (Aug 7th).

GERMANY

Game Turn One

Unit Type	Hexes
3-3-10 (I/2)	3201-3221
3-3-10 (I/304)	3201-3221
1-2-16 (2)	3201-3221
2-3-7 (II/2)	3201-3221
2-3-7 (2/304)	3201-3221
1-5-7 (2)	3201-3221
4-4-10 (I/3)	3201-3221
3-4-10 (38)	3201-3221
2-5-10 (38)	3201-3221
3-3-10 (II/3)	3201-3221
2-2-10 (III/3)	3201-3221
3-3-10 (1/2)	3201-3221

Game Turn Two

Unit Type	Hexes
3-4-10 (I/1)	3201-3221
3-3-10 (I/2)	3201-3221
3-3-10 (II/2)	3201-3221
3-3-10 (III/2)	3201-3221
2-1-7 (Pio)	3201-3221

11.2 Allied Replacements

Once per game, during his own movement phase, the US player automatically receives one replacement, which may be used to bring any eliminated unit onto the map (as depleted), or rebuild any depleted unit already on the map (even if within an enemy ZOC). The US player is not required to utilize his eligible replacement during any particular game turn, but once he does so, no further replacements are afforded to the US player throughout the remainder of the game. An arriving US replacement must arrive on the US supply symbol hex on the northwestern map-edge (0102) but may only arrive if that hex is not presently occupied by any German unit or within any German unit's ZOC.

11.3 German Replacements

Once per game, during his own movement phase, the German player automatically receives one replacement, which may be used to bring any eliminated unit onto the map (as depleted), or rebuild any depleted unit already on the map (even if within an enemy ZOC). The German player is not required to utilize his eligible replacement during any particular game turn, but once he does so, no further replacements are afforded to the German player throughout the remainder of the game. An arriving German replacement must arrive on the German supply symbol hex on the eastern map-edge (3212) but may only arrive if that hex is not presently occupied by any US unit or within any US unit's ZOC.

12.0 Lines of Communication

Each side has a supply symbol along the edge of the map, representing their lines of communication to rear areas off the map. There is one US supply symbol (hex 0102), and one German supply symbol (hex 3212); if any supply symbol hex is currently occupied by an enemy unit, the side that lost its supply symbol will lose half (rounded down) its support fire marker allotment for each subsequent turn's allotment while that supply symbol hex is occupied by any enemy unit.

13.0 The Start Line (Set-Up)

The red hex line running across the center of the map represents the general positions of the US forces prior to the German assault, and serves as the set-up boundary for the US side. No Germans set up on the map, as they all enter the map via the east map edge. The US player may only set up his units northwest of the start line, per the following parameters.

• US 9th Infantry units (1/39, 2/39, 3/39): Must set up in any hexes north of the See River, west of the set-up line.
• US CCB units (1/33, 1/36, 2/33, 2/36, 3/33, 2/119, 703/CCB, Various/CCB (Engineer), Various/CCB): Must set up in any hexes within three (3) hexes of any Cuves town hex(es).
• US 30th Infantry units (1/119, 3/119, 1/120, 2/120, 1/117, 2/117, 3/117, 105, 30, 823, 743): Must set up in any hexes northwest of the start line.

14.0 Unique Terrain

14.1 Hedgerows

Hedgerows are a terrain feature that affect movement and combat normally. In addition, zones of control do not extend into any hedgerow hex unless a road or trail is also present in that hedgerow hex. Any other type of terrain is irrelevant in this regard; for example, a zone of control does not extend into a hex that is a hedgerow and also woods.

Any attacks on an enemy unit in a hedgerow hex must be resolved using the "Hedgerow" terrain type on the Combat Results Table (regardless of which direction the attack is from; Hedgerows in this game, being in-hex instead of hexside, are not nullified by attacks from any other particular direction or multiple directions).

14.2 See River

No movement or attacks are permitted across any See River hexside, except across a hexside that is bridged (assuming that bridge has not been demolished). Bombardment is permitted normally, however, against any unit occupying a hex adjacent to the See River.

15.0 Hill 317

Hill 317 was the dominant height in the area (rising to over 1,000 feet) and was the ideal vantage point to call in artillery and direct airstrikes, especially against enemy positions that were otherwise obscured by hedgerows. To represent the importance of Hill 317 (hex 2815), the allotment of US support fire indicated on the turn track is doubled during each game turn in which any US unit (even if depleted) began that turn occupying the Hill 317 hex (2815).

Example: If a US unit is present on Hill 317 at the beginning of the "Aug. 6th" game turn, the allotment of US support fire for that turn is thus increased from "6" to 12 instead.

This doubling of the US support fire allotment applies throughout each game turn that any US unit begins that turn in hex 2815, even if that occupying US unit is eliminated or subsequently departs that hex during that same game turn. A doubling of the US support fire allotment does not automatically carry over into any subsequent turn (unless a US unit is present in hex 2815 at the beginning of each subsequent game turn).

If the US support fire allotment has been halved per 12.0, that halved allotment is doubled per 15.0 normally.

16.0 Support Fire Random Draw

Instead of the normal procedure of selecting Support Fire markers (per rule 8.1), each player must draw his eligible allotment of Support Fire markers randomly from his own Support Fire chit pool.

17.0 The 116th Panzer Division

The commander of the 116th Panzer Division (Gen. von Schwerin) refused to order an attack in support of the German assault towards Avranches, thereby disjointing the entire start of the offensive. Moreover, the commander of 116th had been ordered to detach a battalion of his few remaining tanks to join up with the 2nd Panzer Division, but refused to do so, delaying the jump-off timetable. As such, during the first game turn (only), no German unit of any type may end its movement adjacent (regardless of ZOC) to any other German unit.

This penalty only applies to the German player during the Aug. 6th game turn, and is never reinstated thereafter.

Designer's Note: The 116th Panzer Division is not featured in the game. The division was reported as being "ridiculously understrength," and did npt participate in the offensive until General Schwerin was relieved and replaced. When 116th did begin to attack, all surprise had been lost, and no progress was achieved.

18.0 Surprise

During the first game turn (Aug. 6th), no US unit may move from its current set-up hex.

19.0 Victory Conditions

To win the game, the German player must exit at least five full-strength mobile units (any German unit with printed movement allowance of 10 or more) off of any west edge map hex(es), as well as capture all three Mortain town hexes (2514, 2515 and 2414). To qualify as "captured," a German unit must either currently occupy or be the last to have occupied hexes 2514, 2515 and 2414). Each captured Mortain hex must not be within any enemy unit's zone of control.

Note: German units may not exit the map as a result of any retreat combat result; a retreating unit doesn't qualify as an exited unit for purposes of determining victory.

If the German player fails to achieve both victory conditions before the last game turn, the game is a US victory.

Designer's Note: These victory conditions would not have culminated in a German operational victory, historically (that is to say, the Germans could not have reached—much less captured—Avranches, even if they had swept aside all resistance in the Mortain area), but a German victory in the game is gauged as having at least defeated US Combat Command B's attempt to stop the offensive.

19.1 Exiting the Map

A German unit that exits the map must expend movement points to enter an imaginary hex presumed to be adjacent to the map's edge. The terrain is assumed to be identical to the terrain in the German unit's last hex before it exits the map, and it must pay the movement point cost in the imaginary hex as in that last occupied hex. A unit moving along a trail or road leading off of the map is assumed to be moving into an imaginary trail or road hex, per the road movement cost.

A German unit may only exit the map during the German Movement or Mobile Movement Phase, not during any combat phase.

Any US unit's zone of control is assumed to be projected into the imaginary hex normally for purposes of movement.

Once any German unit exits the map, it may not return for any reason.

19.2 US Victory

The US player wins the game by simply preventing the German player from achieving his victory conditions as outlined above (19.0).

20.0 Scenarios

Mortain Counterattack has one historic scenario of the German attempt to overrun the American positions in the Mortain region.

Set-up (Germans): No German units are set up on the map; all German units enter via the east edge of the map.

Set-up (US): The US player sets up second, and he must set up per the stipulations of 13.0.

21.0 Game Notes

The German plan, conceived by Hitler personally, had no chance to achieve the ambitious goal of cutting off Patton's Third Army supply lines at Avranches. Ultra intelligence had tipped off the Americans about the impending assault, and Gen. Bradley had held back two divisions to the west in the event of a German penetration. Even assuming the Germans had swept aside the 30th Infantry Division, they would have eventually encountered the entirety of 3rd Armored Division. Assuming the Germans could have overrun the 3rd without enduring onerous casualties, they would have eventually encountered the 4th Armored Division in defensive positions around Avranches. Besides this, the German columns would have been harried incessantly by prowling Allied fighter-bombers, and Gen. Bradley could have brought other units into the area if needed. Even if the four participating German panzer divisions (2nd, 1st SS, 2nd SS, and 17th SS) had been at full strength, the prospects were dubious because the nature of the offensive was a deep penetration strike, meaning there were flanks and supply lines to protect, diminishing the Germans' strength in direct proportion to the depth of the penetration. On paper, the odds may have appeared favorable to Hitler, but the panzer divisions were so understrength as to be nothing more than the equivalent of a kampfgruppe. Only the Panther tanks gave the Germans any kind of advantage at all, but this was more than offset by Allied air cover.

In game terms, this scenario simulates a foregone conclusion. A German victory within the scope of the game would have had no prospects to actually achieve the capture of Avranches, but the German player is nevertheless provided with the challenge of outperforming his historic counterpart. This may not be too difficult when you consider the Germans' poor showing at Mortain. They only penetrated about six or seven miles, and never captured Hill 314 (allowing the Americans to direct artillery with exacting precision). Considering that the panzer battalions were already well below strength and being steadily depleted by Typhoons and P-47s, the German excursion was preordained to fail. However, the German plan was supposed to account for this by relying on a heavy fog that had rolled in the night before to prevent any such harassment. Unfortunately for the Germans, the fog burned off much earlier than anticipated, exposing the offensive to constant strafing. To make matters worse, one of the German armored regiments was in column along a road and became delayed when an Allied plane that was shot down by AA fire crashed into the column's lead panzer and blocked the road (just one example of what an unlucky die roll may represent in real life).

With regards to the design itself, it's always a challenge to simulate a battle with no real prospects for success for one side. Even if the fog had lain heavy throughout most of the day, driving on to Avranches was still never going to happen. Ironically, a more interesting game may be a hypothetical scenario that presumes that the four German panzer divisions (five if you include the 116th, which did not participate) are not squandered at Mortain, but are instead used in a defensive role (where you can imagine how much more effective well-emplaced Panthers would be). This is not a war-winning alternative by any measure, but it may have made the Allied liberation of France more costly, or given the German spearheads during the Ardennes Offensive more punch. Of course, this also assumes the Germans didn't fritter away their strength elsewhere, such as at Arracourt, as they often did.

Such alternative scenarios would be speculative particularly because there is no definitive source as to how many German panzers participated in the Mortain counterattack. Even the Germans didn't know precisely how many panzers were available due to the variances of combat from day to day. Still, intensive research was devoted to this game (including a very detailed study by the US Army), and Mortain Counterattack probably features the most accurate accounting of unit strength of any other scenario on the subject. The US order-of-battle is particularly accurate, since detailed information about American units, even the ad hoc formation that comprised Combat Command B, was easy to obtain. In the end, all of this extensive detail serves to underscore the futility of the German operation, and it prompts us to wonder how much longer the war would have been prolonged if the Germans had not squandered their forces in this and other forlorn counterattacks.

Integrated Combat Results Table

The Integrated Combat Results Table as printed in the Mortain Counterattack exclusive rules. Columns are numbered 1 to 12 for reference; each terrain row lists its own combat differentials from the left. Blank cells are No Effect (•), as in the System Combat Results Table.

Terrain Type	1	2	3	4	5	6	7	8	9	10	11	12
Peak (Hill 317), Woods-Hill	-1	0	+1	+2,+3	+4,+5	+6,+7	+8,+9	+10
Hill (non-woods), See River (bridged)	-2	-1	0	+1

• De = The defending unit is eliminated.
• D3 = The defending unit must retreat three hexes (or deplete one unit of the defending player's choice, instead; see 7.8).
• D2 = The defending unit must retreat two hexes (or deplete one unit of the defending player's choice, instead; see 7.8).
• Ex = One attacking unit and one defending unit must be flipped to their depleted side (or eliminated if already depleted).
• A1 = The attacking unit(s) must retreat one hex (or deplete one unit of the attacking player's choice, instead; see 7.8).
• A2 = The attacking unit(s) must retreat two hexes (or deplete one unit of the attacking player's choice, instead; see 7.8).
• A3 = The attacking unit(s) must retreat three hexes (or deplete one unit of the attacking player's choice, instead; see 7.8).
• (A) = One attacking unit must be depleted (or eliminated if already depleted).
• Ae = All attacking units are eliminated.
• • = No effect.