Cauldron: Battle for Gazala
Cauldron: Battle for Gazala 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
- 9.0 Supply
- Combat Results Table
- 10.0 Introduction
- 11.0 Reinforcements
- 12.0 Lines of Communication
- 13.0 Enemy Zones of Control
- 14.0 Minefields
- 15.0 Tobruk Airfield
- 16.0 Escarpment Hexsides
- 17.0 Rommel's Feint
- 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.
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.
Counter diagram labels (leg combat unit, front): Unit Type Symbol, Unit Size Symbol, Unit ID, Attack Strength, Defense Strength, Parent Formation, Movement Allowance.
Counter diagram labels (mobile combat unit, front): Mobile Unit Designator.
Counter diagram labels (support fire marker, front/back): Type Symbol, Support Strength.
- 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.
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 GT RT 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.
- 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.
Diagram note: Unit does not exert a ZOC.
- 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 (next page): 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 (next page): 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.
- 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 1: 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.
Example 2: 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.
-
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 of 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: 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
Defender Terrain (one table per terrain line, as printed). Combat Differential (Attack strength minus Defense strength).
Mountain
| Die Roll | 0 | +1 | +2,+3 | +4,5 | +6,7 | +8,9 | +10 |
|---|---|---|---|---|---|---|---|
| 1 | Ex | D2 | D2 | D2 | D3 | De | De |
| 2 | Ex | Ex | Ex | D2 | D2 | D3 | De |
| 3 | • | Ex | Ex | Ex | D2 | D2 | D3 |
City, Rough, River
| Die Roll | −2 | −1 | 0 | +1 | +2,+3 | +4,+5 | +6,+7 | +8,+9 | +10 |
|---|---|---|---|---|---|---|---|---|---|
| 1 | • | Ex | Ex | D2 | D2 | D2 | D3 | De | De |
| 2 | A2 | • | Ex | Ex | Ex | D2 | D2 | D3 | De |
| 3 | A3 |
Marsh/swamp, Town, Broken
| Die Roll | −3 | −2 | −1 | 0 | +1 | +2,+3 | +4,+5 | +6,+7 | +8,+9 | +10 |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | A2 | • | Ex | Ex | D2 | D2 | D2 | D3 | De | De |
| 2 | A3 | A2 | • | Ex | Ex | Ex | D2 | D2 | D3 |
Woods, Bridge, Canal, Ditch
| Die Roll | −4 | −3 | −2 | −1 | 0 | +1 | +2,+3 | +4,+5 | +6,+7 | +8,+9 | +10 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | A3 | A2 | • | Ex | Ex | D2 | D2 | D2 | D3 | De | De |
| 2 | (A) | A3 | A2 | • | Ex | Ex | Ex |
Mixed, Clear, Desert, Stream
| Die Roll | −5 | −4 | −3 | −2 | −1 | 0 | +1 | +2,+3 | +4,+5 | +6,+7 | +8,+9 | +10 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | (A) | A3 | A2 | • | Ex | Ex | D2 | D2 | D2 | D3 | De | De |
| 2 | (A) | (A) | A3 | A2 | • |
- 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. (Bold type cannot be shown in this transcription; the source's bombardment results are governed by 8.1.3.)
- 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.
* Stiff Resistance: The affected player may choose to ignore his retreat requirement by choosing to reduce one unit instead.
** Note: On a De or Ae result, all units are eliminated. Two step units are not reduced, they are eliminated.
10.0 Introduction
Cauldron is a simulation of the battle in Libya between forces of the British Commonwealth and those of Germany and Italy. The Germans conducted a wide flanking maneuver south around the British defenses to strike toward Tobruk.
10.1 First Player
The German player is the first player throughout the game (see 3.0).
11.0 Reinforcements
The British player receives six specific reinforcement units only during the game (see 11.1).
The German player receives no reinforcements.
11.1 Quantity of Reinforcements
| Game Turn | Unit Type | Hex |
|---|---|---|
| GAME TURN SIX | 5-4-15 | 1201 |
| GAME TURN SIX | 3-4-9 | 1201 |
| GAME TURN EIGHT | 1-2-9 | 0608 |
| GAME TURN 11 | 5-4-15 | 1201 |
| GAME TURN 11 | 3-4-9 | 1201 |
| GAME TURN 14 | 3-4-9 | 1201 |
11.2 When Reinforcements Arrive
At the end of the movement phase (reinforcements may not move during the turn they arrive). Mobile units that arrive at the end of the movement phase may not move during the mobile movement phase.
11.3 Where Reinforcements Arrive
In the 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 they arrive in a hex adjacent to an accessible enemy unit. 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. There are two British supply symbols (hexes 1201 and 1410), and two German supply symbols (hexes 0734 and 2924); 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 out of each subsequent turn's allotment while that supply symbol hex is occupied by any enemy unit. If enemy units currently occupy two supply symbol hexes, that side loses its support fire allotment.
13.0 Enemy Zones of Control
Reinforcements may be placed into enemy zone of control, but must abide by the normal rules (see 6.0).
14.0 Minefields
Allied minefield hexsides are represented on the map, and are considered permanent terrain features that can neither be created nor destroyed during the course of the game. A minefield friendly to a player at the beginning of the game remains friendly throughout the game. Likewise, enemy minefields do not become friendly when captured; rather, their effects remain throughout the game.
14.1 Friendly Minefields
Friendly minefields have no combat effects on any friendly units, although friendly units must expend +2 movement points to cross a friendly minefield hexside, even via a trail or a road.
14.2 Enemy Minefields
A unit may only move across an enemy minefield hexside if it occupies an adjacent hex at the beginning of its movement. A unit that moves across an enemy minefield hexside must expend all of its movement allowance to do so, even via a trail or a road, and stop in the entered hex.
A unit may retreat through an enemy minefield, but is depleted as a result (or eliminated if already depleted or a one-sided unit).
NOTE: Zones of control extend into enemy minefield hexes normally. No unit (except commando units) may move from EZOC to EZOC across a minefield hexside.
Any attacks on an enemy unit across a minefield hexside must be resolved using the minefield terrain type on the Combat Results Table. Attacks on any enemy unit across a friendly minefield hexside (friendly to the attacker) suffer no penalty.
14.3 Fortified Boxes
The body text heads this section "FORITIFIED BOXES"; it is spelled as in the contents line here.
The various British minefield hexes on the map are considered fortified boxes. They are minefields per 14.0 normally, except any British unit occupying a fortified box may ignore any retreat result (whether a defender retreat or an attacker retreat). Any retreating British unit outside a fortified box must continue its retreat normally; its retreat is not cancelled by moving into or through a friendly controlled fortified box.
Fortified boxes may not be destroyed during the course of the game.
German units never derive any benefit if occupying a fortified box.
15.0 Tobruk Airfield
If the airfield in hex 0709 is occupied by any Axis unit, the UK player loses one support fire marker out of each subsequent turn's allotment that airfield hex is occupied.
NOTE: The British player does not lose any support fire markers if the Bir El Gubi airfield (2707) or El Adem airfield (1510) is occupied by any Axis unit. The occupation of those airfields by any player has no effect.
16.0 Escarpment Hexsides
Movement across escarpment hexsides is prohibited except via trail or road; however, movement within any escarpment hex is unaffected, and is considered to be desert terrain.
No units may attack across any escarpment hexside, except via trail or road in which case, combat is resolved using the escarpment terrain type on the Combat Results Table.
17.0 Rommel's Feint
During the first game turn, no Allied unit may move during the movement phase or the mobile movement phase, unless adjacent to an Axis unit. After the first game turn, all units may be moved normally.
18.0 Victory Conditions
The German player wins the game if he can, at any time (even if only momentarily), demonstrate a path of uninterrupted hexes (neither occupied by enemy units nor within any enemy unit's ZOC) from Tobruk (0608) to either of the two German supply symbol hexes on the west edge of the map.
NOTE: the path of hexes may not cross any minefield hexside unless both hexes astride it are occupied by Axis units.
The British player wins the game if, as of the end of the last game turn, he can demonstrate a path of uninterrupted hexes (neither occupied by enemy units, nor within any enemy unit's ZOC) from Tobruk (0608) to the UK supply symbol hex (1201) on the east edge of the map.
If neither side is able to achieve its victory conditions the game is a draw.
If either player has lost twice as many or more units (eliminated) than the other as of the end of the last game turn, the victory condition is downgraded. That is, if he has won the game per the above paragraph, his victory is downgraded to a draw. Or, if the game ended as a draw, that draw is downgraded to a defeat.
19.0 Scenarios
Cauldron has one historic scenario of the German attempt to capture the vital port of Tobruk in Libya, and the British defense of Cyrenaica.
Set-up the following units in the hexes indicated below. The map is printed with the set-up locations of each starting unit included in the game. The set-up locations have no other impact on play.
GERMANY
| Unit Type | Hex |
|---|---|
| 1-2-12 | 0334 |
| 1-2-12 | 0132 |
| 2-3-12 | 0232 |
| 2-3-12 | 0332 |
| 4-5-15 | 2723 |
| 4-5-15 | 2822 |
| 1-2-12 | 2823 |
| 1-2-12 | 2824 |
| 2-3-12 | 2926 |
| 3-2-20 | 2820 |
| 4-5-15 | 2623 |
| 4-5-15 | 2724 |
| 1-2-12 |
ITALY
| Unit Type | Hex |
|---|---|
| 1-2-7 | 0533 |
| 1-2-7 | 0733 |
| 2-3-12 | 0632 |
| 2-3-9 | 0832 |
| 2-3-9 | 0933 |
| 2-3-7 | 1231 |
| 2-3-7 | 1031 |
| 2-3-9 | 1730 |
| 2-3-9 | 1530 |
| 2-3-12 | 2128 |
| 2-3-9 | 2028 |
| 2-3-9 | 2228 |
| 2-2-12 |
UNITED KINGDOM
| Unit Type | Hex |
|---|---|
| 4-4-9 | 0228 |
| 4-4-9 | 0429 |
| 4-4-9 | 0730 |
| 4-5-9 | 0928 |
| 4-5-9 | 1126 |
| 4-6-9 | 1526 |
| 3-4-9 | 0812 |
| 3-4-9 | 0412 |
| 3-3-9 | 1008 |
| 1-2-9 | 1610 |
| 1-2-12 | 1122 |
| 3-5-9 | 1222 |
| 3-5-9 |
20.0 Game Notes
The name for the Battle of Gazala is itself an irony insofar as it implies precisely what General Rommel intended the British to believe...that his marginal attack towards Gazala near the Libyan coast would be the schwerpunkt of his main assault. In fact, Rommel prodded his mobile forces far to the south, pivoting them around the Bir Hacheim strongpoint (the furthest extent of the Allied fortifications) and then thrust them into the unfortified southern flank of the British defensive network. It is at this stage that the game Cauldron begins.
Tobruk, once again, was the crux of the battle; as a port, and particularly because of its natural breakwater geography shielding the harbor from the Mediterranean Sea, Tobruk was probably the most important anchorage in all of North Africa west of Alexandria (as it had been, in fact, for thousands of years). Rommel's intended thrust into Egypt could not be possible without first capturing Tobruk, and both sides knew it. It is no wonder that the British undertook such elaborate efforts to sew innumerable mines across nearly fifty miles of desert (from the coast southward as the crow flies) to defend a city of only 5,000 inhabitants.
Rommel's plan (known to the Axis as Operation Venezia) was a dichotomy of boldness and riskiness; the offensive absolutely surprised the British command, although it was not without its setbacks...Rommel had tasked the Italian Ariete Division to assault and capture the Bir Hacheim fortified "box" (as the British termed their various outposts in Cyrenaica), but encountered a full brigade of stalwart Free French that meted out punishing fire from their heavily fortified position. As the lynchpin of Rommel's pivoting maneuver, Bir Hacheim's stiff resistance upset the offensive's tempo, and so the entire battle then began to develop into a wider engagement of dueling armored vehicles further out in the middle of the desert...an area that became known as the "Cauldron". This presented a severe danger to the German offensive if any British mobile units could get around and isolate Rommel's panzers (which were now very far afield while fighting to reach Tobruk). Rommel was thus forced into a defensive posture while he detached an entire division to double-back and overrun Bir Hacheim, although the French brigade there continued to hold their position steadfastly nonetheless; Bir Hacheim had become the proverbial—almost literal—thorn in the Desert Fox' side.
It was then that the British overplayed their hand; General Auchinleck ordered a massive armored counterattack that benefitted the Germans' well-honed defensive tactics—particularly their employment of superior guns—that mauled the attacking British tank formations. Rommel was quick to exploit his serendipitous ambush with aggressive panzer assaults that inflicted additional losses upon the decimated British armor, which soon forced them into a wholesale retreat. British tank losses were so severe (~75% by some estimates) that the defense of Tobruk became practicably untenable thereafter, compelling Auchinleck to order a withdrawal of all Allied forces to more defensible positions to the east, and thus the abandonment of Tobruk altogether. Fortunately for the Allies, Rommel's own losses exceeded his available replacements, and so the Germans could not pursue the withdrawing British into Egypt...at least not immediately.
In game terms, the Allies field nearly as many units as the Axis (if including the arriving reinforcements), but nearly 100 more aggregate combat strength points (i.e., attack and defense strength points). However, most Allied units are out of position during the first turn of the game, and the German allotment of Support Fire markers is appreciably greater than the British (i.e., 11 versus 6). Nevertheless, the German player must be careful about his casualties because the British can afford "Ex" (Exchange) results more easily than the Germans; the loss of combat power for each "Ex" result borne by the Axis will be felt more acutely, particularly over the long term. Ergo, a battle of attrition is an inefficient German strategy, to say the least...especially when considering that the German player is granted 26 game turns to reach Tobruk...ample time to orchestrate a methodical campaign.
Operationally, the primary concern for both sides is the exposure of their respective forward supply hexes (El Adem for the British, and the depot in hex 2924 for the Axis...the latter representing continuous supply convoys feeding Rommel's offensive). These locations become strategically important during the game, just as they were historically. Players will understand why the Allied position at Bir Hacheim cannot be bypassed, and also why El Adem was the focal point of the fighting in the "Cauldron". If a supply hex becomes captured, the very tangible consequences (i.e., that player's allotment of Support Fire markers becomes halved) are exceptionally problematic...probably more so for the German player (any loss of Support Fire markers would downshift the entire Axis offensive, perhaps even halting it altogether). The British player's situation is substantively different because he can withdraw his forces to a defensive position behind the ring of anti-tank ditches around Tobruk's perimeter...and hope to hold out. But this situation is not ideal at all when the enemy can wield considerably more Support Fire markers. In view of the game's length, no defensive line can be expected to withstand repeated attacks that are augmented by surplus support fire (unless, perhaps, enemy casualties have been excessive—or at least significant—up to then). This very circumstance is what compelled Auchinleck to order the remnant Allied forces to retreat back to Egypt (rather than attempt to hold Tobruk) after the devastation of British armor in the Cauldron.
In this way the game replicates the actual battle well. Despite the historic outcome, the victory conditions in Cauldron are very achievable for either side. Of course, the Axis ultimately won the battle, but Rommel had considered his situation to be very tenuous from the outset...fully aware of the risks involved (calculated risks, albeit). Indeed, throughout Rommel's entire military career 'risks' were emblematic of his style of battle, though they were not always lucrative. At the Battle of Gazala, Rommel's risk to dash around the British defenses—hundreds of miles from his supply sources—would prove to be, arguably, his most profitable gamble of the war.