RulesPal
Chat
Rulebook
Path to Victory: Middle East, 1941 thumbnail

Path to Victory: Middle East, 1941

Path to Victory: Middle East, 1941 Rulebook

Table of Contents

Table of Contents

  • 1.0 Introduction
    • 1.1 Scales
    • 1.2 Commonly Used Abbreviations
  • 2.0 Components
    • 2.1 Map
    • 2.2 Frontlines & Borders
    • 2.3 Playing Pieces
    • 2.4 How to Read the Units
      • 2.4.1 Ground Units
      • 2.4.2 Air Units
    • 2.5 Unit & Marker Types
      • 2.5.1 Unit Key
      • 2.5.2 Unit Type Symbols
      • 2.5.3 Markers
      • 2.5.4 Diplomacy Markers (13.3)
      • 2.5.5 Random Event Markers (19.0)
  • 3.0 Setup & Hex Control
    • 3.1 Axis Setup
      • 3.1.1 Iraqi Setup
    • 3.2 Allied Setup
    • 3.3 Hex Control
  • 4.0 Sequence of Play
    • 4.1 GT Procedure
      • 4.1.1 Game Turn Sequence
      • 4.1.2 Random Events Step
      • 4.1.3 Diplomacy/ULTRA Step
      • 4.1.4 Reinforcements Step
      • 4.1.5 Strategic Movement Step
      • 4.1.6 Allied Step
      • 4.1.7 Axis Step
      • 4.1.8 Supply, Air Maintenance & Air Recovery Step
    • 4.2 Victory Determination
  • 5.0 Movement
    • 5.1 Restrictions
    • 5.2 Enemy Zones of Control (EZOC)
    • 5.3 Retreat & Advance after Combat
    • 5.4 Terrain
    • 5.5 Multiple Terrains
    • 5.6 Railroad Movement
    • 5.7 River & Lake Hexsides
    • 5.8 Bridges
    • 5.9 Operational Movement
    • 5.10 Strategic Movement
    • 5.11 Allied Movement from Persian Gulf Box
      • 5.11.1 Allied Kuwait City Landing
  • 6.0 Stacking
    • 6.1 Stacking Limitations
    • 6.2 Free-Stacking Units
    • 6.3 Stack Movement
    • 6.4 Splitting Stacks
    • 6.5 Different Movement Factors in a Stack
    • 6.6 Allied & Axis Stacking
  • 7.0 Zones of Control (ZOC)
    • 7.1 Enemy Zones of Control (EZOC)
    • 7.2 Multiple ZOC
    • 7.3 ZOC & Movement
  • 8.0 Combat
    • 8.1 Multiple Attackers
    • 8.2 Indivisibility of Units
    • 8.3 Concentric Attacks
    • 8.4 Attack Sequencing
    • 8.5 Stacking Limitations & Attack
    • 8.6 Fog of War
    • 8.7 Combat Procedure
    • 8.8 Combat Result Table (CRT)
    • 8.9 Combat Results
    • 8.10 Combat Modifiers
    • 8.11 Naval Gunfire Support
    • 8.12 Retreat After Combat
  • 9.0 HQ Units
    • 9.1 HQ Artillery Support
    • 9.2 HQ AA Fire
  • 10.0 Airpower
    • 10.1 Aircraft Movement
    • 10.2 Ground Attack
      • 10.2.1 Bombardment Procedure
      • 10.2.2 Interdiction
    • 10.3 Air Operations
      • 10.3.1 Escort
      • 10.3.2 Interception
      • 10.3.3 Air Combat Procedure
    • 10.4 Transport
    • 10.5 Basing
    • 10.6 Air Unit Maintenance
  • 11.0 Random Events & Reinforcements
    • 11.1 Random Events
    • 11.2 Reinforcements & Replacements
      • 11.2.1 Reinforcement Unit Placement
      • 11.2.2 Axis Reinforcements
      • 11.2.3 Break Down Units
      • 11.2.4 Multiple-Step Units
  • 12.0 Supply
    • 12.1 Allied Supply
    • 12.2 Axis & Iraqi Supply
    • 12.3 Axis & Iranian Supply
    • 12.4 Vichy France Supply
    • 12.5 Out of Supply Units
  • 13.0 Diplomacy / ULTRA
    • 13.1 Diplomacy Marker Procedure
    • 13.2 ULTRA Interception Procedure
    • 13.3 Diplomacy Markers
      • Arab Revolt
      • Iraqi Junta
      • Iran Joins the Axis
      • Vichy Syria Weapons
      • German Air Units
      • Axis Support
      • Italian Air Units
      • Vichy Syria Air Support
    • 13.4 The Iraqi Regent & the Mufti of Jerusalem
  • 14.0 Iranian, Iraqi & Vichy French
    • 14.1 Iranian Forces
    • 14.2 Iraqi Forces
    • 14.3 Vichy French Forces
  • 15.0 Soviet Forces
    • 15.1 Soviet Entry
    • 15.2 Allied Invasion
  • 16.0 Victory Points
    • 16.1 Allied Victory Points
    • 16.2 Axis Victory Points
      • 16.2.1 Pipeline VP
      • 16.2.2 Habbaniyah, Arab Revolt & Game Length VP
    • 16.3 Victory Conditions
  • 17.0 Optional Rules
    • 17.1 German Parachute Reinforcements
    • 17.2 Desert Movement
    • 17.3 Iraqi Commitment
    • 17.4 Iraqi Irregulars
  • 18.0 Designer's Notes
  • 19.0 Random Events
  • 20.0 Allied Setup & Iraqi Coup Table

1.0 Introduction

Path to Victory: Middle East, 1941, is a simulation of the operations in Iraq, Syria and Iran (Persia) during the spring and summer of 1941. In this game, both players must carefully use their limited resources (military and political) to try to wrest control of the Middle East from their enemies.

The game begins with the Iraqi coup in early April 1941. During the game, the Axis player may attempt diplomatic/military actions: supporting the Iraqi coup, trying to take control of Persia, unleashing an Arab revolt in Palestine, and sending aid to Iraq, Vichy Syria and possibly Persia/Iran. The Allied player must use their limited resources to assert control in Iraq, Persia, Syria and Lebanon as soon as possible to protect the Suez Canal and the Western Desert Front.

1.1 Scales

  • Each Game Turn (GT) represents about 10 days.
  • Each hexagon is 37 miles (60 kilometers) from one side to the opposite side.
  • Units are divisions, brigades, regiments, and battalions or equivalent, and some specialized smaller units.

1.2 Commonly Used Abbreviations

  • 1d6: One Six-sided Die
  • DR: Die Roll
  • DRM: Die Roll Modifier
  • EZOC: Enemy Zone of Control
  • GT: Game Turn
  • HQ: Headquarters
  • MP: Movement Points
  • OOS: Out of Supply
  • TEC: Terrain Effects Chart
  • ZOC: Zone of Control

2.0 Components

A complete game of Path to Victory: Middle East, 1941 includes: a 22×34-inch game map, rule booklet, and a sheet of 228 9/16-inch counters. Players must provide one six-sided die (1d6) to resolve combat and other random game events, as well as one widemouth, opaque container for Diplomacy markers.

2.1 Map

The map shows the Middle East as it was in early 1941. A hexagonal grid has been superimposed over the terrain features on the map to regularize the movement and positioning of the playing pieces. The hexagons are called hexes in the game rules.

2.2 Frontlines & Borders

The dash-dotted gray lines represent the 1941 borders between the various mandates, protectorates, and independent countries.

2.3 Playing Pieces

The pieces are referred to as units for military forces, and as markers for informational pieces.

2.4 How to Read the Units

2.4.1 Ground Units

  • Attack Factor (first number): The unit's basic combat strength when attacking.
  • Defense Factor (second number): The unit's basic combat strength when defending.
  • Movement Factor (third number): The basic number of hexes through which a unit can move in a game turn (GT).
  • Number of Steps (circled number to the left of the unit type icon): The number of step losses the unit can suffer before being destroyed (11.2.4).

2.4.2 Air Units

  • Type of air unit: F=fighter, LB=light bomber, MB=medium bomber, T=transport.
  • Air to Air Factor (first number): The unit's basic strength when fighting other air units. If the figure is in parentheses it is only used in defense.
  • Air to Ground Factor (second number): The unit's basic strength when attacking ground units or airbases.
  • Range Factor (third number): The basic range, in hexes, of that air unit.

Air units with parentheses around air-to-air factors may only use their air-to-air factor defensively (10.3.3).

2.5 Unit & Marker Types

2.5.1 Unit Key

Ground Units. Three and four step units are represented by two counters: a Front (4 steps or 2 steps as applicable) and a Back (3 steps or 1 step). The front carries the Unit ID and Entry GT; the back carries the Unit Size Symbol and Unit Factors.

  • Colored Stripe: Does not exert ZOC.
  • Replacement Counter dot: Marks a replacement counter.
  • Unit Size (Company): The unit size symbol is shown on the counter (see 2.6).

2.5.2 Unit Type Symbols

  • Armor
  • Cavalry
  • Mechanized Cavalry
  • Infantry
  • Mechanized Infantry
  • Airborne Infantry
  • HQ (Headquarters)
  • Air unit

2.5.3 Markers

  • Game Turn (front & back)
  • Out of Supply marker
  • Naval Markers (Naval Support Markers)
  • Commando
  • Disrupted
  • Axis/Allied VP Total
  • Pipeline Status marker
  • Mufti of Jerusalem
  • Iraqi Irregulars FalQ
  • Iraqi Regent

2.5.4 Diplomacy Markers (13.3)

Diplomacy markers are shown with a back (face-down) side and the following fronts:

  • Arab Revolt
  • Iraqi Junta
  • Iran Joins Axis
  • Vichy Syria Weapons
  • Air Support to Vichy Syria (Axis Support)

2.5.5 Random Event Markers (19.0)

Random Event markers are shown with a back (face-down) side and the following fronts:

  • Crete Campaign
  • Greek Campaign
  • Battle-Axe
  • Axis Offensive on the Western Desert
  • Africa Orientale Italiana (AOI)

2.6 Unit Sizes

  • XXXX: Army
  • XX: Division
  • X: Brigade
  • III: Regiment
  • II: Battalion
  • I: Company

2.7 Unit Designation & Nationalities

Units are identified by their color, and a title, a number, or a two-part designation.

  • Allied Forces
    • British Commonwealth & Arab Legion (British, Indians, Iraq Levies, Australians, Zionist, Arab Legion): Brown background
    • Free French: Dark Blue background
    • Soviets: Red background
  • Axis Forces
    • Germany: Grey background
    • Iraq: Mustard background
    • Iran: Green background
    • Vichy French: Bright Blue background
    • Italy: Yellow background

2.8 Abbreviations on the Units

2.8.1 British Commonwealth & Arab Legion Allies

  • Br: British
  • Ind: Indian
  • Cav: Cavalry
  • Lan: Lancers
  • CDO: Commando
  • CCR: Composite Cavalry Regiment
  • DC: Duke of Connaught
  • FAA: Fleet Air Arm
  • KLV: Kurd Levies
  • ILV: Iraqi Levies
  • Mist: Mista'arvim Zionists
  • Palm: Palmach Zionists
  • RAF: Royal Air Force
  • RAAF: Royal Australian Air Force
  • TJFF: Trans Jordan Frontier Force

2.8.2 Free French Allies

  • BC: Brigade Coloniale (Colonial Brigade)
  • DBL: Half Brigade of the Foreign Legion
  • CAC: Independent Tank Company
  • DLFL: Free French Light Division
  • FM: Fusiliers Marine (Navy Fusiliers)
  • GES: Spahi Cavalry Group of Squadrons
  • GET: Circassian Cavalry group of squadrons

2.8.3 Soviet Allies

  • M: Mountain
  • TD: Tank Division (black on grey)
  • SKJ: Sonder Kommando Junck

2.8.4 Iraqi Axis

  • Bs: Basra
  • Di: Diwaniya
  • FalQ: Fawzi al-Qawuqji
  • IMB: Independent Mechanized Brigade
  • Ns: Nasiriya

2.8.5 Vichy France Axis

  • BL: Levant Battalions
  • BTM: Moroccan Infantry Battalion
  • CA: Chasseurs d'Afrique (Africa Light Cavalry)
  • CLib: Chasseurs Libanais (Lebanese Light Infantry)
  • CLD: Light Desert Cavalry
  • G Rougie: Groupe Rougie
  • G Albord: Groupe Albord
  • MF: French Navy
  • REI: Foreign Legion
  • RMC: Mixed Colonial Regiment
  • RTA: Algerian Infantry
  • RTS: Senegalese Infantry
  • GRTT: Tunisian Infantry
  • SA: Algerian Spahis
  • S Lebanon: South Lebanon Sector

2.8.6 Aircraft Types

  • Audx: Audax
  • Albc: Albacore
  • Blen: Blenheim IV
  • B65: Breda 65
  • CR42: Fiat CR42
  • D520: Dewoitine 520
  • Gld: Gloster Gladiator
  • He 111: Heinkel He 111
  • Hurr: Hawker Hurricane
  • LeO45: Lioré et Olivier 45
  • M167F: Glenn Martin M167 F
  • Me109: Messerschmitt Me109
  • Me110: Messerschmitt Me110
  • Po25: Potez 25
  • P-40: Curtiss Warhawk
  • SB: Tupolev SB

3.0 Setup & Hex Control

Setup according to the following rules. Play proceeds according to the sequence given in section 4.0 for 12 GTs (GTs), from GT 1: April I, 1941, to GT 12: September II, 1941. Each month has two complete GTs.

  • Place all diplomacy markers in an opaque container. The Axis player must randomly pull 12 markers. The selected markers must be placed face down on the Diplomacy Marker Display.
  • The Axis player can look at the markers he has pulled and then places them face down on the Diplomacy Marker Display.
  • The Allied player cannot look at them during normal game play.
  • When each diplomacy marker is played it is revealed to the Allied player.

Important: Some unit counters have an entry turn number (yellow number in the upper right corner) and cannot deploy until the GT matching the number on the counter.

3.1 Axis Setup

  • The Axis player deploys the two German air units; Sonder Kommando Junck Me110 F and He111 MB at Mosul (2517).
  • Place all other Italian and German air units on the Diplomacy Marker Display. These air units can enter play only through diplomacy marker play.
  • If using the optional rule (17.1) German Parachute Reinforcements, set aside the two German parachute infantry units 1FJR and 2FJR. If not using the optional rule, remove them from play.
  • Deploy all Iranian units, no more than one division per city/town, on the city/towns of Persia. Up to two divisions can be deployed on or adjacent to Tehran (2231) and Abadan (0825) each.
  • Deploy Iranian air units at hexes 2132 and/or 1026 (Ahvaz).
  • Deploy all Vichy France ground units in Syria or Lebanon at the Axis player's discretion.
  • Deploy all Vichy France air units on airbases in Syria or Lebanon at the Axis player's discretion.
  • Place all later entry turn Axis reinforcements within easy reach.

3.1.1 Iraqi Setup

The Axis player must deploy the Iraqi units as follows:

  • Units of the 1st and 3rd Iraqi Divisions, IMB Brigade: on or within five hexes of Ramadi (1615), Baghdad (1618) and/or Karbala (1518). Exception: Not in Habbaniyah (1617).
  • Units of the 2nd Iraqi Division: On or within two hexes of Kirkuk (2218).
  • Units of the 4th Iraqi Division: On or within four hexes of Basra (0824). Exception: Not in Shaibah (0823).
  • Deploy Iraqi air units at Rashid (1619) and/or Mosul (2517).
  • Set aside within easy reach the FalQ irregular unit (17.4) and the Mufti of Jerusalem marker (13.4.2).

3.2 Allied Setup

After the Axis player finishes their setup, the Allied player can set up.

  • Deploy at RAF Habbaniyah (1617) one F air unit (GLD), two LB air units (Audx), and two local levy companies (ALV, KLV).
  • Deploy at RAF Shaibah (0823) one local levy (ILV), one F air unit (GLD), one T air unit (VAL), and one MB air unit (Wellington).
  • Deploy two MB air units (Blenheim, Wellington) at H4 Airbase (hex 1407).
  • Deploy on or adjacent to Amman (1203) and/or hex 1408: the following units: 4th and 5th Cav Bde, TJFF (two regiments), Arab Legion (AL), and one generic infantry battalion. The 4th or the 5th Cav Brigade can deploy broken down into a total of two 2-step mechanized cavalry regiments (11.2.3).
  • Deploy on or adjacent to Jerusalem (1302) and Haifa (1501): Palm., Mist. Battalions (Zionist militias).
  • Roll 1d6 and check the Allied Setup and Iraqi Coup Table (20.0). Apply results.
  • Place all other later entry turn Allied reinforcements within easy reach. The two separate tank battalions enter play only if the Battle-Axe event happens (See the Random Events Table).
  • Place all Soviet ground units in the Soviet Ground Units box and all Soviet air units in the Soviet Air box.

3.3 Hex Control

Keeping track of who controls each hex is important to trace supply and other game functions. Control of hexes is attributed to the last player that entered that hex.

4.0 Sequence of Play

Every game of Path to Victory is divided into 12 GTs.

  • The players follow the Game Turn Sequence in the order listed.
  • Each complete GT is divided into steps.
  • Player steps are further divided into a series of segments.
  • The GT ends after the Supply, Air Maintenance, and Air Recovery Step.

4.1 GT Procedure

The GT Sequence is given below. Every action taken by a player must be carried out in the appropriate order of his own player sequence.

4.1.1 Game Turn Sequence

  1. Random Events Step (11.1 & 19.0)
  2. Diplomacy/ULTRA Step (13.0)
  3. Reinforcement Step (11.2)
  4. Strategic Movement Step (5.10)
  5. Allied Step (4.1.6)
  6. Axis Step (4.1.7)
  7. Supply, Air Maintenance and Air Recovery Step (4.1.8)

4.1.2 Random Events Step

At the beginning of each GT the Allied player rolls 1d6 and refers to the Random Events Table (11.1 & 19.0).

4.1.3 Diplomacy/ULTRA Step

a) Beginning GT 1, the Axis player uses one of his diplomacy markers to perform political and military actions (13.1).

b) Beginning GT 4, the Allied player attempts an ULTRA Interception prior to the Axis player using a Diplomacy Marker (13.2).

c) Check for Iran, Iraq, or Vichy French surrender (14.0).

4.1.4 Reinforcements Step

Receive reinforcements scheduled for that GT (Skip on GT 1). Random events and diplomacy markers might change, add, or delay the arrival of reinforcements.

  • Check for breakdowns, if any (11.2.3).
  • Use Allied Replacement points, if any (11.2).

4.1.5 Strategic Movement Step

The Allied player performs Strategic Movement first, followed by the Axis player (5.10).

4.1.6 Allied Step

The Allied player must announce if he is going to invade Persia (14.1) and/or Syria-Lebanon (14.3) on that GT.

  1. Movement Segment and Axis interdiction (5.0 & 10.2.2).
  2. Combat Segment (8.0).

4.1.7 Axis Step

  1. Movement Segment/Allied interdiction (5.0/10.2.2).
  2. Combat Segment (8.0).

4.1.8 Supply, Air Maintenance & Air Recovery Step

Each player checks ground units for supply status and air units for maintenance and recovery. The Allied player completes the check first, followed by the Axis player.

  1. Check supply status. Place Out of Supply (OOS) markers on units that are OOS. Remove OOS markers from units now in supply (12.0).
  2. Carry out air unit maintenance (10.6).
  3. Carry out aborted aircraft recovery (10.7.3).
  4. Return available air units from the Flown box to friendly-controlled airbases.
  5. Remove disrupted markers (Allied, Soviet, Vichy France, and German) (10.9).
  6. Roll 1d6 for disrupted marker removal (Iraqi, Iranians) (10.9).

4.2 Victory Determination

Both players use the Victory Point Track (on map) and the VP markers to keep track of the VPs earned by each side. At the end of GT 12, determine the victor (16.0).

5.0 Movement

Each ground unit has a movement factor printed on it. Units are moved by tracing a path of contiguous hexes through the hex grid, until all movement points (MP) are expended, or the player decides to cease moving the unit, whichever comes first.

  • As each unit enters a hex it pays one or more MP from its movement factor. Consult the Terrain Effects Chart (TEC) printed on the map for further details.
  • Each Air unit has a movement range printed on it. Air units are moved by tracing a path of contiguous hexes through the hex grid.
  • As each air unit enters a hex it pays one range point as taken from its range factor.
  • Air units must end their movement in a friendly-controlled airbase.
  • Some units can be air transported (10.4).
  • Movement can be interdicted by nearby air units (10.2.2).

5.1 Restrictions

  • Unused MP may not be accumulated from GT to GT, nor may they be in any way transferred from one unit to another.
  • If one or more hexes are over-stacked following movement, the excess units must be eliminated by the owning player (6.1).
  • Units may never enter a hex occupied by enemy ground units or prohibited hexes.
  • Any air unit that cannot reach a friendly controlled airbase is eliminated.
  • Disrupted units cannot move (10.2.2).

5.2 Enemy Zones of Control (EZOC)

  • EZOC stop movement (7.3).
  • EZOC may interfere with lines of supply (12.0).

5.3 Retreat & Advance after Combat

Occurs as part of combat results and is not considered part of regular movement (8.12 & 8.13).

5.4 Terrain

To enter any given hex a unit must spend the number of MP designated by the TEC for the kind of terrain in it.

  • When the TEC calls for an MP expenditure to cross a river, that cost is in addition to the cost for entering the hex.

5.5 Multiple Terrains

If there is more than one terrain type in a hex, use the highest single movement cost from among all the terrain involved. If using a railroad or a railroad bridge, use the railroad or bridge movement rate regardless of any other terrain in that hex, as described below.

5.6 Railroad Movement

A unit which moves via railroad expends one half MP per hex entered.

5.7 River & Lake Hexsides

  • Units pay an additional MP to cross an unbridged river. That cost is in addition to the cost of entering the next hex.
  • If more than half of the hex is covered by sea/lake, movement into it is prohibited.
  • Movement across any sea/lake is prohibited.

5.8 Bridges

A river hexside crossed by a railway line is called a bridge hex. Bridges negate the effects of rivers on movement for units crossing such hexsides. Bridges are indestructible for game purposes (8.14.1).

5.9 Operational Movement

Units beginning and ending their movement not adjacent to enemy units and moving across friendly controlled hexes may triple their movement factors.

  • Operational movement can be combined with railroad costs.

5.10 Strategic Movement

During the Strategic Movement Step, units not adjacent to enemy units may move any number of hexes to a friendly-controlled hex not adjacent to enemy units through friendly-controlled railroad hexes.

  • The Allied player performs Strategic Movement first, followed by the Axis player.
  • Units must be within one hex of a railroad town/city.
  • The Allied player can move up to four units of any type by Strategic Movement.
  • The Axis player can move up to one Iraqi unit of any type by Strategic Movement, but only within Iraqi territory.
  • The Axis player can move up to one Iranian unit of any type by Strategic Movement, within Persian territory.
  • The Axis player can move up to one Vichy France unit of any type by Strategic Movement, within Syria and Lebanon territory.

5.11 Allied Movement from Persian Gulf Box

Allied units arriving from India and other fronts to the Persian Gulf Box can land during the Movement Segment in Kuwait City (0525), Basra (0824) or Bandar-e-Sharpur (0826).

5.11.1 Allied Kuwait City Landing

The Allied player can always move units from the Persian Gulf Box to Kuwait City unopposed.

  • Any Allied reinforcements may land normally from the Persian Gulf Box to Kuwait City during the Movement Segment.
  • This movement has no cost in MPs. Allied units may land at Kuwait City and perform operational or regular movement during that same GT.

5.11.2 Allied Basra Landing

When the Allied player intends to move units from the Persian Gulf Box to Basra during the Allied Movement Segment, he first announces that he is going to do such a move.

  • The Axis player must declare if he intends to use an Iraqi Junta diplomacy marker (13.3).
  • If not, the Allied forces land unopposed, and the Allied ground units are placed in Basra.
  • If there are Iraqi units in Basra, they must withdraw to an adjacent hex.
  • If they are withdrawn to a hex where they would be OOS, they receive an OOS marker.
  • If unable to be withdrawn, they are eliminated.
  • Once Basra is under Allied control, any subsequent Allied reinforcements may land normally from the Persian Gulf Box to Basra during the Movement Segment. This movement has no cost in MPs. Allied units may land at Basra and perform operational or regular movement during that same GT.

5.11.3 Axis Basra Landing Opposition

If the Axis player decides to oppose the Allied landing, he must declare and play one Iraqi Junta diplomacy marker.

  1. The Axis player must have Iraqi units in Basra.
  2. Roll 1d6. DR of 5–6: The Iraqis will oppose the landing. The Allied units will have to launch an attack on Basra from the Persian Gulf Box, with a 2L column shift for the opposed landing. These shifts are in addition to any other applicable shifts.
  3. Allied units that do not successfully land are returned to the Persian Gulf box if not eliminated.
  • If the optional Iraqi Commitment rule (17.3) is being used, the Axis opposition is automatic.

Transcriber's note: in the magazine layout, steps 2) and 3) print beside section 5.10 rather than under 5.11.3. They are placed here because their text refers to the Basra opposition procedure; the printed numbering is kept.

5.11.4 Allied Bandar-e-Sharpur Landing

Allied units can land into Bandar-e-Sharpur (0826) from the Persian Gulf box during the Movement Segment when the Allies begin the invasion of Persia (14.1).

  • If there are Iranian units in that hex, the Allied units must launch an attack from the Persian Gulf box, with a 2L column shift for the opposed landing. Note this column shift is in addition to any other applicable modifiers or shifts.
  • Allied units that do not successfully land are returned to the Persian Gulf box if not eliminated.
  • Once Bandar-e-Sharpur is under Allied control, any subsequent Allied reinforcements may land normally from the Persian Gulf Box to Bandar-e-Sharpur during the Movement Segment. This movement has no cost in MPs. Allied units may land at Bandar-e-Sharpur and perform operational or regular movement during that same GT.

Designer's Note: This rule simulates the uncertainty of the units of the Indian Army when it first landed in Basra in April 1941. Historically, the British were organized for a transport operation, not for an assault against a defended town.

5.12 Neutral Territories

Turkey and Saudi Arabia are neutral territories.

  • Neither Allied nor Axis forces may enter, move, or fly across these territories.
  • Only Allied forces can land in, enter, or fly, or move across Kuwait.

6.0 Stacking

Having more than one friendly unit in a hex is called stacking. Stacking limits vary by terrain type and are given on the TEC. Stacking limits are given on the TEC in terms of units, and each unit in the game, no matter its nominal organizational size, is one unit for stacking purposes. HQ units count as one unit for stacking purposes.

6.1 Stacking Limitations

Stacking limits apply for all units of both sides at the end of each Reinforcement Step, Movement, and Combat Segments.

  • Friendly units may move through hexes occupied by other friendly units at no extra cost.
  • At the end of each player's Reinforcement Step, Movement, or Combat Segment, if one or more hexes is over-stacked, the excess units must be eliminated by the owning player (player's choice).
  • A friendly unit or stack may never enter a hex containing an enemy unit or stack.

6.2 Free-Stacking Units

Air units and other markers have no stacking values. Such markers may be added to any hexes if the rules for their use are observed.

6.3 Stack Movement

To move as a stack, units must begin their movement already stacked. Units are not required to move together just because they started the Movement Segment in the same hex; in such situations, those units might be moved together, individually, or in smaller sub-stacks.

6.4 Splitting Stacks

A moving stack may halt temporarily to allow a unit or sub-stack to split off and move away on a separate course.

  • The units left behind in the original stack may then resume their own movement, even splitting off from other units and sub-stacks.
  • Once a unit or stack starts moving, all its movement must be completed before that of another unit/stack is begun.

6.5 Different Movement Factors in a Stack

If units with different movement factors are traveling together in a stack, the stack can move only as far as the lowest movement factor. Lower movement factor units may be left behind.

6.6 Allied & Axis Stacking

  • Soviet units cannot stack with any other nationality.
  • British Commonwealth, Free French, and Arab Legion air and land units can stack together.
  • German, Italian, and Vichy France air and land units can stack together.
  • Only German land and air units may stack with Iraqi land and air units.
  • Only German land and air units may stack with Iranian air and land units. Note: This is only after the Iran Joins the Axis diplomacy marker is in play (13.3).

Important:

  1. Soviet ground and air units may not participate in an attack that contains any other nationality, nor may any other nationality participate in an attack by Soviet units.
  2. All other Allied ground and air units may conduct attacks against the same defending units (note the above stacking restrictions still apply).
  3. All Axis ground and air units may conduct attacks against the same defending units (note the above stacking restrictions still apply).

7.0 Zones of Control (ZOC)

The six hexes immediately surrounding a ground unit's hex constitute that unit's zone of control (ZOC).

  • ZOC stop enemy movement and can block enemy supply lines (12.0).
  • ZOC also affect Retreat After Combat (8.12).
  • ZOCs are ignored during Advance After Combat (8.13).
  • Air units exert no ZOC.

7.1 Enemy Zones of Control (EZOC)

Most units exert a ZOC at all times.

  • EZOC are not negated by friendly or enemy units. Exception: Advance After Combat (8.13) and supply (12.0).
  • A unit's ZOC does not extend into hexes that the unit is prohibited from entering.
  • Battalion and company-sized units do not exert a ZOC. These units have a colored strip over their combat and movement factors.

7.2 Multiple ZOC

Both friendly and enemy units may simultaneously exert a ZOC into the same hexes.

  • There is no additional effect if more than one unit, friendly or enemy, exerts a ZOC into the same hex at the same time.
  • If a given unit is in an EZOC, that enemy unit is also in its ZOC. The two units are equally and mutually affected.

7.3 ZOC & Movement

A unit must stop its movement for that segment when it first enters an EZOC. It may move no further that segment.

  • A unit may not move directly from one EZOC to another EZOC.

8.0 Combat

Combat takes place between opposing units during the Combat Segment of every GT. Attacking is always voluntary.

8.1 Multiple Attackers

An enemy-occupied hex may be attacked in one Combat Segment by as many units as can be brought to bear from one, some or all the surrounding hexes.

  • No more than one hex may be the object of a single attack.

8.2 Indivisibility of Units

  • No single attacking unit may have part of its attack factor divided and used in more than one battle.
  • No single defending unit may have part of its defense factor divided and used in more than one battle.
  • No attacking unit may attack more than once per Combat Segment.
  • No defending unit may be attacked more than once per Combat Segment.
  • No defending unit may decline combat.

8.3 Concentric Attacks

Concentric attacks are carried out by units occupying three or more sides of a defending hex.

  • A Concentric Attack provides a 1R column shift to combat.

8.4 Attack Sequencing

There is no limit on the number of attacks each player may make during their Combat Segment.

  • They need not declare all his attacks beforehand.
  • Each attack must be resolved before the next is begun.

8.5 Stacking Limitations & Attack

  • If one or more hexes for the attacker or the defender are over-stacked prior to combat, the excess units must be eliminated by the owning player (6.1).
  • Units stacked together need not participate in the same attack. Some units might attack into one hex, while other units attack other hexes or do not attack at all.

8.6 Fog of War

Neither player may look beneath the top unit of the enemy unit or stack until both players have determined their total combat factors.

8.7 Combat Procedure

  1. Determine which ground units will attack.
  2. Both players assign Air units and resolve all air operations (10.0).
  3. Both players assign Naval markers to the combat if applicable.
  4. Add the total combat factors for each side. Once the factors are known, the attack may not be called off.
  5. Divide the attack factors by the defense factors, round remainders down, and compare them as an odds ratio, including any combat modifiers (8.10).
  6. Roll 1d6 and cross reference the DR result with the CRT.

8.8 Combat Result Table (CRT)

The Combat Results Tables (printed on map) are used to resolve combat.

  • Iraqi and Iranian units use the Infantry CRT.
  • British, Soviet, Free French, Vichy French, and German units use the Mechanized CRT.

8.9 Combat Results

In the two Combat Results Tables, the number to the left of the slash is the attacker's combat result; the number to the right is the defender's combat result. The numbers signify the number of strength-steps each side must eliminate from their forces involved in that battle.

  • Attacker losses are always removed before defender losses in each battle.
  • Losses can be distributed among all types of ground units as the owning player sees fit, but no unit may be eliminated until every multi-step unit involved in the combat has absorbed a step loss (even if they are attacking from different hexes).

Example: The Allied total attacking factors are 8. The total defending factors are 5; the odds would be two to one, or 2:1 (8÷5=1.6 rounded down to 1). The Allied player consults the Mechanized CRT under the 1:1 column. The Allied player rolls 1d6, with the result of 6. The CRT shows a result of ½, the Allied player must take one step loss while the Axis player must take two.

8.10 Combat Modifiers

The odds ratio obtained in the odds calculation process given in 8.7 may be modified by shifting, (a shift is a change of the combat odds ratio), Die Roll Modifiers (DRM), or both.

  • Odds may be shifted by the terrain in the defender hex and along the hexside(s) between the attacking and defending units. (See the TEC).
  • Important: The 1L shift for a river hexside only applies if all attacking units are attacking across a river hexside. Bridged hexsides do not negate the river shift (Exception: See 8.14.1).
  • DRMs do not shift the odds but add to or subtract from the number of the combat DR.
  • Naval Gunfire Support can provide a shift or can add or decrease the DR.
  • All combat modifiers are cumulative in their effects. In every battle, all applicable modifiers are determined and their effects calculated before the die is rolled to obtain the combat result.
  • Important: Units with printed combat factors of one and higher can never have those combat factors reduced to less than one for any reason.

8.11 Naval Gunfire Support

Allied and Vichy France units defending or attacking into coastal hexes can receive naval gunfire support.

  • The Allied Mediterranean Squadron marker can provide 1R on the attack or 1L defensive column shift in Mediterranean Coastal Hexes.
  • The Allied Persian Gulf flotilla marker can provide +1 DRM on the attack or −1 DRM in defense of Persian Gulf coastal hexes.
  • The Vichy France naval support marker (MF) can provide +1 DRM on the attack or −1 DRM in defense of Mediterranean Coastal Hexes.
  • Each marker can only be used once per GT, either on the attack or in defense.
  • A map hex containing at least part of the sea is considered a coastal hex.

8.12 Retreat After Combat

Certain units may carry out a retreat after combat.

  • Allied, German, and Vichy France units may avoid a step loss if they decide to retreat one hex.
  • They must be able to retreat to a hex not adjacent to enemy units: otherwise, they must accept all step losses.
  • Retreating units must always move towards the nearest supply source.
  • Occurs as part of combat results and does not use MP.
  • If a unit(s) retreat into a friendly occupied hex and that hex is subsequently attacked the retreated units do not contribute to the defense, however, they are subject to any combat result.

Important: Units may retreat into an over-stack situation, however, if they are still overstacked at the end of the Combat segment, 6.1 applies.

Example: Three Indian brigades in hex 1707 attack a two-step Vichy France unit at hex 1706. The combat result on the CTR [sic; printed "CTR"] is ½. One of the attacking brigades accepts one step loss. The defending unit absorbs one step loss and withdraws to hex 1705 to absorb the remaining step loss.

8.13 Advance After Combat

If an attack clears a hex of all enemy units, then one, part, or all attacking units may advance into the just vacated hex.

  • EZOC are ignored for Advance After Combat.

8.14 11th Commando Unit

The British 11th Commando unit can be used to capture bridges and disrupt enemy HQs.

8.14.1 Bridge Capture

  1. If the commando unit is adjacent to a bridged river hexside and the Allied player is attempting to attack across the bridged hexside, the Allied player may announce that he is going to use the commando unit to attempt a bridge capture. He does this before calculating combat odds in an Allied Combat Segment against Vichy French, Iranian, or Iraqi units that are across a bridged river hexside.
  2. The Allied player then rolls 1d6.
    • DR of 4–6: The defensive column shift for a river hexside is cancelled. The commando unit has taken a bridge and is available to play again the next GT.
    • DR of 1–3: The commando unit fails. The defensive column shift for attacking across a river hexside applies.
  3. If the commando unit fails, roll another 1d6.
    • DR of 1: The commando unit is eliminated.
    • DR of 2–4: It is removed, and it then returns as a reinforcement two GTs later.
    • DR of 5–6: It is removed, and it is then available, the next GT.

8.14.2 Headquarters Raid

  1. If the commando unit is adjacent to a defending unit (it does not need to participate in the combat) the Allied player may announce that he is going to use the commando unit to conduct an HQ raid. He does this before calculating combat odds in an Allied Combat Segment against Vichy French, Iranian, or Iraqi units that are [the printed sentence breaks off here; the source then repeats the instruction as follows:] He does this before calculating combat odds in an Allied combat against an HQ-supported Vichy French or Iraqi unit or stack.
  2. The Allied player then rolls 1d6.
    • DR of 4–6: The defensive support of the enemy HQ is cancelled. The commando unit has interfered with the enemy line of communication and is available for play again the next GT.
    • DR of 1–3: The commando unit fails.
  3. If the commando unit fails, roll another 1d6.
    • DR of 1: The commando unit is eliminated.
    • DR of 2–4: It is removed, and it returns as a reinforcement two GTs later.
    • DR of 5–6: It is removed, and it is then available the next GT.

Transcriber's note: the printed text of 8.14.2 step 1 is garbled in the source (the first sentence breaks off after "units that are", then the instruction repeats). It is transcribed as printed. The Allied player's target is the HQ-supported Vichy French or Iraqi unit or stack named in the second sentence.

9.0 HQ Units

HQ units represent assets at army, division, or brigade level that include field and AA artillery. HQ units provide artillery support and AA defense.

9.1 HQ Artillery Support

HQ units add their attack combat factors in attack and their defensive combat factors in defense to the units they stack with.

  • HQ units may never attack alone.
  • HQ units use their defensive combat factor when attacked alone in a hex.

9.2 HQ AA Fire

HQ units can fire back against enemy air units attacking friendly units adjacent to or stacked with the HQ unit (10.7).

10.0 Airpower

Air units play a key role in this game. Air units can perform three different missions: ground attack, air combat, and transport.

10.1 Aircraft Movement

Aircraft can move up to their range factor. Air units may not enter or fly across the neutral territories of Turkey or Saudi Arabia.

10.2 Ground Attack

Air units can be used to:

  • Bombard enemy units during the friendly Combat Segment. This constitutes an invasion.
  • Interdict during the enemy Movement Segment.

10.2.1 Bombardment Procedure

(During the Friendly Combat Segment)

  1. Select the air units performing an attack.
  2. Select an enemy unit, stack, or airbase within range of the air units performing the attack.
  3. Resolve any enemy Interceptions (10.3.2).
  4. Resolve any enemy HQ and airbases conducting AA Fire at the attackers (10.7).
  5. Surviving friendly air units now perform Bombardment. Use the air-to-ground factor of the air unit(s).
  6. Roll 1d6 and cross-reference with the Bombardment Table (on the map).
  7. Apply results.
    • The results of the Bombardment Table are given as: D1, D2, or D3. Place a disrupted marker on that number of units.
    • The defender can choose which units receive the disrupted result.
    • Disrupted ground units have their attack, defense, and movement factors halved. No unit with a combat factor of one or higher may have the factor reduced below one for any reason.
    • A Disrupted ground unit that receives another disruption result remains disrupted.
    • Disrupted air units are moved to the Maintenance box.
  8. Place any surviving friendly air units on the Flown box.

10.2.2 Interdiction

(During the Enemy Movement Segment)

  1. Select the air units performing an attack.
  2. Select a moving enemy unit or stack within range of the air units performing the attack. Movement stops until the attack is performed.
  3. Resolve any enemy Interceptions (10.3.2).
  4. Resolve any enemy HQ conducting AA Fire at the attackers (10.7).
  5. Roll on the Bombardment Table. Apply results.
    • Disrupted ground units have their attack, defense and movement factors halved, and cannot move until the next GT. Units with a combat factor of one or higher may not have the factor reduced below one for any reason.
    • A Disrupted ground unit that receives another disruption result remains disrupted.
  6. Place a disrupted marker on the affected units.
  7. Place any surviving air units on the Flown box.
  8. Ground units that are not disrupted can continue the Movement Segment.

Example: It is GT 3. A single Allied mechanized cavalry regiment moves from 1913 to 2212 in Syria. When the Allied unit enters hex 2112, the Axis player announces an Interdiction with a MB and a LB Vichy French air unit based in Aleppo (2406). The movement automatically stops until the air raid is resolved. The Vichy French units total 4 air-to-ground factors. The Axis player rolls on the Bombardment Table on the 4–6 column. The result is D1, so the lone Allied unit is disrupted. A disrupted marker is placed on the Allied unit. Disrupted units cannot continue moving until the next GT. The Vichy French air units return to the Flown box of the Axis player.

10.3 Air Operations

Fighter (F) units of both sides can be used to escort friendly Light Bombers (LB), Medium Bombers (MB) and Transport (T) units, or to intercept enemy F, LB, MB, and T units.

10.3.1 Escort

F units can be sent along with LB, MB, and T units to protect friendly air units.

  • F units can add their air-to-ground rating to any ground attack if the air raid is not intercepted by enemy fighters.

10.3.2 Interception

When one or more enemy air units attempt a ground attack or transport within five or fewer hexes of an airbase containing friendly F units, the defending player can choose to intercept. If the air units attack an airbase containing F units, the Interception is automatic. No DR needed.

  1. For air interception, roll 1d6.
    • DR of 5–6: The F units intercept the attackers. Follow the Air Combat Procedure.
    • DR of 1–4: The attackers are not intercepted.
  2. Air units surviving an enemy Interception continue their ground attack or transport.
  3. Return surviving air units to the Flown box.

10.3.3 Air Combat Procedure

Set aside all the intercepting F units and all the intercepted F, LB, MB, and T units.

  1. Add the air-to-air ratings of the attacking/intercepting F units.
  2. Add the air-to-air rating of defending/intercepted F, LB, and MB units (Units use the parenthesized rating when attacked).
  3. Roll 1d6 for the intercepting units and cross reference the DR with the Air Combat Table.
  4. Roll 1d6 for the intercepted units and cross reference the DR with the Air Combat Table.
  5. Apply results simultaneously. The owning-player chooses what air units are aborted and places them in the Maintenance box.
  6. Return surviving F air units to the Flown box.

Example: An Allied air formation, formed by one MB and escorted by one F unit (rating of 2), launches a Ground Attack against hex 1518. There is one Iraqi F unit (air to air rating of 2) in 1620. The Axis player announces that he intends to intercept the bombing force. The Axis player rolls for Interception. The result is 5, so the Interception is successful. The Axis player has a total air to air rating of 2; the Allied force has a total air to air rating of 3. The Axis player rolls a 3 and the Allied player rolls a 6. Both forces roll on the 1–3 column of the Air Combat Table. The Allied air formation remains intact and there are no aborted air units and proceeds with the ground attack. The lone Iraqi F unit is aborted, and it must be placed in the Axis Maintenance box. At the end of the GT, the Axis player must check if the air unit returns to the map or remains in the Maintenance box.

10.4 Transport

Allied units can be airlifted from one airbase to another during the Movement Segment.

  • British T units can transport up to one infantry battalion.
  • The T unit must begin the Movement Segment in an airbase, and the infantry battalion must be in the airbase or adjacent to it.
  • The Allied player declares that the infantry battalion is being airlifted to a friendly-controlled airbase. The airbase must be within the range of the T air unit.
  • If the T unit flies within five hexes of an Axis airbase containing available (not flown) F units, it can be intercepted. If the interception is successful, resolve Air Combat. If the T unit is aborted, it is placed in the Maintenance box, and the infantry battalion is eliminated.
  • No more than one interception attempt may be made per GT.
  • If the T unit lands at its objective, the infantry battalion deploys in that hex or adjacent to it and cannot move for the remainder of that Movement Segment. The T unit is placed in the Flown box.
  • EZOC are ignored for transport purposes.
  • British T units cannot participate in Ground Attack, Escort, or Interception operations.

10.5 Basing

At the end of each GT, the units in the Flown Box are redeployed.

  • Air units must be deployed on a friendly-controlled airbase, shown by an airbase symbol on the map.
  • When an airbase is captured by enemy forces, air units based there must move to one or more friendly airbases within range.
  • If there are no friendly airbases within range, or the air units are in aborted status, the air units are eliminated.

10.6 Air Unit Maintenance

Air units aborted or disrupted because of Air Combat or Bombardment are put in the Maintenance box.

  • At the end of each GT, players check for Air Maintenance of the aborted air units.
  • Check the Maintenance Table (in the Maintenance Box, on the map) and apply results. Units that are not redeployed remain in the Maintenance Box.

10.9 Disrupted Marker Withdrawal

Disrupted markers are automatically removed at the end of each GT.

  • Exception: Disrupted markers are not automatically removed from Iraqi and Iranian units.
  • Iraqi and Iranian unit's disrupted markers are withdrawn on a DR of 4–6 (roll for each unit individually), or automatically if the Axis player plays an Axis Support diplomacy marker.

10.7 AA Fire

HQ units and airbases can fire on enemy air units.

10.7.1 HQ AA Fire

HQ units can fire on air units attacking their own or adjacent hexes.

  1. Roll 1d6, cross reference the defensive combat factor of the HQ with the AA Fire Table.
  2. Apply results.
    • The owning player chooses which air unit(s) to abort.
    • Air units aborted due to AA Fire are returned to any friendly controlled airbase within range of the air unit with their aborted side up.
    • Unaffected air units continue with their mission.

10.7.2 Airbase AA Fire

Airbase hexes can fire at enemy air units attacking their own hex. All airbase hexes have a defensive factor of 2.

  1. Roll 1d6 and cross reference the defensive combat factor of the airbase with the AA Fire Table.
  2. Apply results.
    • The owning player chooses which air unit(s) to abort.
    • Air units aborted due to AA Fire are returned to any friendly controlled airbase within range of the air unit with their aborted side up.

Important: One HQ and one airbase may combine their defensive factors to a single AA Fire.

10.7.3 AA Fire Aborted Air Recovery

At the end of each GT, players check for recovery of the aborted air units. Roll 1d6 for each air unit.

  • DR of 1–3: The air unit returns one GT later to the Flown box.
  • DR of 4–6: The air unit remains on their airfield in an aborted status.
  • Place air units on the appropriate GT of the GT Record Track.

10.8 The German & Italian Expeditionary Contingent

German and Italian air units operating in Iraq are subject to special attrition due to the lack of supplies and parts.

  • Whenever a German or Italian air unit is flown, if the unit returns successfully to its base, roll 1d6.
  • DR of 1: The unit is placed in the Maintenance box instead of the Flown box.
  • The Crete campaign random event increases attrition.

11.0 Random Events & Reinforcements

11.1 Random Events

Random events can delay the arrival of Axis and Allied reinforcements.

  • Allied player places all random event markers within easy reach.
  • At the beginning of each GT, the Allied player rolls 1d6 and places the appropriate random event marker on the GT Record Track as a reminder. Players immediately applies the results of the random event per the Random Events Table (19.0).
  • Each event can be applied only once. If rolled a second time, no event takes place.

11.2 Reinforcements & Replacements

Reinforcement units arrive after GT 1.

  • Unit counters that have an entry GT number cannot deploy until that GT.
  • Beginning GT 2 the Allied player receives one replacement point every other GT.
  • Replacement points can be accumulated.
  • Allied replacements points are used to return one step to a depleted infantry brigade. One replacement point equals one step.
  • Eliminated units cannot be rebuilt.
  • If one or more hexes are over-stacked following reinforcement, the excess units must be eliminated by the owning player (6.1).
  • Unsupplied units may not receive replacements.

11.2.1 Reinforcement Unit Placement

Allied ground units can be placed in the Persian Gulf box or any Allied-controlled town or city in Palestine or Transjordan. Allied air units must be placed in an Allied-controlled airbase.

11.2.2 Axis Reinforcements

German and Italian air units (and parachute units, see optional rule 17.1) arrive through diplomacy markers and by entry turn number. Available German and Italian air units are placed in the Available Air Units box. From the Available Air Units box, they can be deployed to any Axis-controlled airbase in Iraq, Syria, Lebanon, or Persia during the Reinforcements Step.

11.2.3 Break Down Units

During the Reinforcements Step, Allied units can be broken down into infantry battalions or mechanized cavalry regiments.

a) Allied infantry brigades (Indian, Australian, British) can be broken down into infantry battalions.

  • Any remaining infantry battalion counters can be used to break down an Allied infantry brigade. Each step of an Allied infantry brigade equals one battalion.
  • A four-step infantry brigade can be broken down into one infantry battalion by reducing the four-step brigade to its three-step side or broken down into two infantry battalions and replacing the four-step brigade with their replacement two-step counter.

b) Allied mechanized cavalry brigades can be broken down into mechanized cavalry regiments.

  • Available mechanized cavalry regiment counters can be used to break down an Allied mechanized cavalry brigade. Two steps of an Allied mechanized cavalry brigade are equal to one regiment. An Allied mechanized cavalry brigade can be broken down into two mechanized cavalry regiments.

Important: When breaking units down, the replacement units must be the same nationality as the parent unit.

11.2.4 Multiple-Step Units

Allied infantry brigades have four steps. This means that when these units receive a second step loss, the four/three-step counter is withdrawn from play and replaced by its two-step counter replacement (the counter with a white dot on the upper right corner).

12.0 Supply

Units trace Lines of Supply (LOS) to supply sources. Supply is needed to be able to move and fight at full effectiveness.

  • Supply is checked at the end of each GT.
  • To be judged in supply, a unit must be able to trace a path of contiguous hexes to a friendly supply source.
  • The line of supply must be clear of enemy units or their ZOC.
  • For supply, effects of EZOC are cancelled if there is a friendly unit in that hex.

12.1 Allied Supply

Allied units must trace an LOS to a supply source to be considered in supply.

  • Allied supply sources are any friendly-controlled town, city, or airbase in Transjordan, Palestine, Iraq, and Kuwait City.
  • If controlled by the Allied player, Bandar-e-Sharpur (0826) is also a supply source.
  • Soviet units are always considered to be in supply.

Important: Cities and towns under an Arab revolt marker cannot be a supply source. When the Arab revolt marker is withdrawn, the town or city regains its supply source status.

12.2 Axis & Iraqi Supply

Iraqi and German units must trace an LOS to a supply source in Iraq to be considered in supply.

  • Iraqi supply sources are Baghdad (1618), Mosul (2517), Kirkuk (2218), and any friendly airbase in Iraq.

12.3 Axis & Iranian Supply

Iranian and German units must trace an LOS to a supply source in Persia to be considered in supply.

  • Supply sources are Tehran (2231), Tabriz (2821), Bandar-e-Sharpur (0826), and any friendly airbase in Persia.

12.4 Vichy France Supply

Vichy France units must trace an LOS to any friendly-controlled city, town, or airbase in Syria or Lebanon.

12.5 Out of Supply Units

Units judged to be Out of Supply (OOS) at the end of a GT receive an OOS marker. This marker is withdrawn in subsequent GTs if the unit is again in supply.

  • The movement, attack and defense factors of OOS units are halved. Any factor with one or higher may not be reduced below one for any reason.

13.0 Diplomacy / ULTRA

Diplomacy represents Axis military, political, and diplomatic actions to stoke anti-British unrest in the region, and the Allied ULTRA Interception represents the Allied use of code breaking to prevent those actions.

13.1 Diplomacy Marker Procedure

  • The Axis player can use up to one diplomacy marker per GT (starting with GT 1) to perform a given action.
  • Each individual marker may only be played once per game.
  • Most actions take place during the Diplomacy Step. Exception: Allied Basra Landing (5.11.2).

Diplomacy markers below (13.3) explain the effects of each diplomacy action.

13.2 ULTRA Interception Procedure

The Allied player can attempt ULTRA interception at the beginning of each GT, beginning with GT 4. Roll 1d6.

  • DR of 5–6: The Allied player randomly picks one unused Axis diplomacy marker. Discard that marker (it cannot be used during the game).
  • Additionally, the Axis player cannot play any other diplomacy marker on that GT.

13.3 Diplomacy Markers

Arab Revolt

Axis powers promote pro-Mufti unrest in Arab cities, while Allied forces struggle to regain control. Roll 1d6.

  • DR of 4–6: The Arab Revolt succeeds. Place Arab revolt markers on Haifa (1501) and Jerusalem (1302). Add a +1 to the DR if Iraq has not surrendered. Certain events (Iraqi Regent, Mufti of Jerusalem) add or decrease these DR results. These cities/towns cannot be used as Allied supply sources while the Arab revolt marker is in place.
  1. During the Allied Combat Segment, the Allied player may stop an Arab revolt.
  2. The Allied player must have at least two or more units of battalion or larger-sized units in each city/town.
  3. Roll 1d6 for each city/town in revolt.
  4. The marker is removed on a DR of 2–6.
  • This event can happen only once per game. If the Axis player has another Arab revolt diplomacy marker, it cannot be played again during the game. Remove it from the Diplomacy Marker Display.
  • If the Arab revolt lasts more than two GTs, add +1 Axis VP.

Example: It is the beginning of GT 3. The Axis player decides to play an Arab revolt marker. The Axis player rolls 1d6. The DR is 4. The Allied player is using the Iraqi Regent marker which adds −1 DRM. The Mufti of Jerusalem adds +1 DRM to the DR. So there is an Arab revolt in Palestine.

Iraqi Junta

The Iraqi Junta tries a more aggressive stance after Germany promises to send weapons and ammunition (14.2).

a) Up to two stacks of Iraqi forces may move and/or attack any Allied-held hex in Iraqi territory that GT. b) Iraqi forces oppose the Allied landing from the Persian Gulf box (5.11.2).

Iran Joins the Axis

The Germans convince the Iranian government to enter the war on the Axis side.

  • Important: This marker cannot be played before GT 4.
  • The Axis player may attempt to win over Iran up to two times per game (one for each marker, provided that the Axis player gets the two markers during game setup).
  • Roll 1d6. DR of 4–6: Iran becomes Axis-controlled for the remainder of the game until it surrenders (14.1).

Vichy Syria Weapons

The Germans urge Vichy Syria to send weapons to the Iraqi Junta. The Iraqis get 1L on the defense or can rebuild one destroyed unit. The rebuilt unit must be placed in Iraq, on any friendly-controlled town or city.

German Air Units

Germany sends in air reinforcements to Iraq, Persia, or Syria. The Axis player receives two additional German air units (Axis player's choice) and sends each of them to any Axis-controlled airbases in Iraq, Persia, or Syria.

Axis Support

Increases German support and supplies. The Axis player can use this marker to provide 1R/1L to any Iranian, Vichy France or Iraqi attack, or to withdraw one disrupted marker from an Iranian or Iraqi unit.

Italian Air Units

Italian intervention in Syria. The Axis player receives two Italian air units. These units can deploy in any Vichy-controlled airbases in Syria or Lebanon.

Vichy Syria Air Support

The Axis player sends support to Vichy Syria.

  • Pick up to three uncommitted German and/or Italian MB and LB air units. These air units operate out of Crete and Greece can operate over Syria and Lebanon that GT.
  • For range purposes, calculate range from hex 2101 in the Mediterranean Sea.
  • If aborted by AA Fire, the units must return to the nearest friendly airbase and flip to their aborted side.
  • If unable to return to an airbase, they are removed from play.
  • If not aborted, the air units return to the Axis Available Air Units box.
  • These air units can be deployed in a future GT in Syria, Iraq, or Persia if the Axis player plays an Italian or German Air Units marker.
  • Decrease Axis VP total by one.

Transcriber's note: the last three bullets print in the magazine layout beside the Arab Revolt entry. Their content (return to the Available Air Units box, later deployment, the VP cost) matches the Vichy Syria Air Support marker, so they are placed here; the rules for 17.1 confirm the one-VP air support cost.

13.4 The Iraqi Regent & the Mufti of Jerusalem

13.4.1 Iraqi Regent

The Iraqi Regent, a pro-Allied asset, managed to flee from Iraq and take refuge in Transjordan. Historically, the Regent played a key role in defeating the Junta and regaining control of the country.

  • If included in Allied setup (20.0), the Allied player can use the Iraqi Regent marker once per game.
  • When the Axis player declares that he is going to use an Iraqi Junta marker, this action is cancelled by the play of the Iraqi Regent.
  • If the Axis is playing an Arab revolt marker, the Allied player must declare if the Iraqi Regent marker will be used to apply a −1 DRM.

13.4.2 Mufti of Jerusalem

The Mufti of Jerusalem is used by the Axis player to stoke unrest in Arab territories under Allied control.

  • Apply +1 DRM to the Arab revolt DR.
  • The Mufti of Jerusalem is removed from play when Iraq surrenders.

Designer's Note: The Regent of Iraq, Prince Abd al-Ilah, fled Baghdad and was given refuge in Amman, Transjordan. From Amman, Abd al-llah called for a revolt against the insurgent government. Mohammed Amin al-Husayni, Grand Mufti of Jerusalem, was an Arab nationalist who played a key role in the Arab revolt of 1936-39 as well as supported the Iraqi coup. After the defeat of the Iraqi junta, al-Husayni fled to Persia, then Turkey, and finally Europe where he collaborated with Nazi Germany in propaganda and recruitment of Muslim units such as the Handschar Bosnian SS Division.

14.0 Iranian, Iraqi & Vichy French

14.1 Iranian Forces

The Iranian forces can participate with the Axis player if:

a) Iran joins the Axis via a diplomacy marker. b) Persia is invaded by the Allied player, including air bombardment.

  • Iranian forces move and conduct combat normally within their borders.
  • Iranian units cannot be rebuilt nor receive replacements during the game.
  • When Iran enters the war on the Axis side, the Abadan pipeline marker is moved to Closed on the map's Pipeline Status display.
  • Iranian units automatically surrender at the beginning of the first GT that begins with Tehran (2231), Abadan (0825), Ahvaz (1026), Tabriz (2821) and Dezful (1325) under Allied control. When this happens, move the Abadan Pipeline marker to Open.
  • When Iranian forces surrender, automatically withdraw from play all Iranian air and land units and place all Axis air units located in Iran, in the Axis Available Air Units box.
  • Allied units may move (including operational and strategic movement) across the country for the remainder of the game.

14.2 Iraqi Forces

Iraqi air and ground units can only move and/or attack Allied units when the Axis player plays an Iraqi Junta diplomacy marker; Iraqi ground units may defend normally.

  • Iraqi forces can only operate within Iraq.
  • Iraqi forces automatically surrender at the beginning of the first GT that Baghdad (1618), Mosul (2517) and Basra (0824) begin under Allied control.
  • When Iraqi forces surrender, automatically withdraw from play all Iraqi air and land units and place all Axis air units located in Iraq in the Axis Available Air Units box.
  • Allied units may move (including operational and strategic movement) across the country for the remainder of the game.
  • The Allied player must keep at least one unit (any type) in Baghdad, Basra, and Mosul for the remainder of the game.
  • When Iraqi forces surrender, move the Haifa Pipeline counter to open and remove from play the Mufti of Jerusalem marker.

14.3 Vichy French Forces

a) Vichy French ground and air units cannot conduct any movement, attacks, or air bombardment unless Syria or Lebanon is invaded by Allied forces.

  • Once the Allies invade Syria or Lebanon, the Axis player can operate normally with all Vichy France ground and air units.
  • Vichy France units can only operate within Syria and Lebanon.

b) When the Allied player announces the beginning of operations against Vichy Syria and Lebanon, roll 1d6.

  • DR of 1–3: Withdraw from play 1 CLD cavalry regiment unit of Vichy France.
  • DR of 4–6: Withdraw from play 2 CLD cavalry Regiments units of Vichy France.

Designer's Note: This represents the efforts of Free French commanders to convince their comrades in the Armée de l'Orient (Army of the Levant) to join the Free French cause.

c) At the beginning of the first GT that Damascus (1704) and Beirut (1802) are under Allied control, roll 1d6.

  • DR of 5–6: Vichy France forces surrender. Add +1 if either Aleppo (2406), Homs (2004), and/or Deir-ez-Zor (2211) are under Allied control.
  • Withdraw from play all surviving Vichy French forces and any other Axis forces in Syria and Lebanon. German and Italian air units are placed in the Axis Available Units Box.
  • The Allied player must leave for the remainder of the game at least one brigade or regiment-sized unit in Damascus, Beirut, and Aleppo each.
  • If Vichy France forces do not surrender, they remain in play. At the beginning of each succeeding GT the Allied player rolls 1d6. Vichy forces surrender if the result is a 4–6. The +1 DRM for controlling Aleppo, Homs, or Deir-ez-Zor still applies.

15.0 Soviet Forces

The Soviet forces are controlled by the Allied side. Soviet Forces enter play depending on the scheduled GT, Allied invasion of Persia, or diplomacy marker success.

  • Soviet forces can operate only within the borders of Persia.
  • Soviet air units operate from the Soviet Air Units box. For range purposes, the Soviet Air Units box is located two hexes of any Persian border hex.
  • Soviet units are always considered to be in supply.

15.1 Soviet Entry

  • Soviet forces are neutral during GT 1 through 5. They may not enter play for any reason. On GT 6 (June II 1941) they are automatically controlled by the Allied player.
  • If an Allied invasion has taken place, before the diplomacy marker is played, the markers are removed from play.
  • If Iran enters play via diplomacy marker, Soviet forces cannot intervene before GT 8.

15.2 Allied Invasion

  1. On the first GT of an Allied invasion, the Soviet forces can enter play from the Soviet Reserve box from the North, through map edge hexes 2821 to 2826.
  2. Two GTs after the Allied invasion, Soviet forces can enter play from the East, through map edge hexes 1932 to 2332.

Example: The Allied invasion in Persia begins on GT 7 (July I, 1941). Soviet units in the Soviet Reserve Box can enter Persia through hexes 1932 to 2332, beginning with GT 9 (August I, 1941).

16.0 Victory Points

During the game, both players should use the Victory Point Track (on the map) and the VP markers to keep track of the VPs earned by each side.

16.1 Allied Victory Points

  • Certain hexes are labeled on the map for Victory Points for the Allied player.
  • The Allied player earns 1 VP per GT for each pipeline that is reopened.

16.2 Axis Victory Points

16.2.1 Pipeline VP

  • The Axis player earns 1 VP for each GT where Abadan Pipeline (0825) is closed. Place the Abadan Pipeline marker on the Closed box of the Pipeline Status (on the map) as a reminder.
  • The Axis player earns 1 VP for each GT where the Haifa Pipeline is closed. The Haifa Pipeline is closed on GT 1 or 2 depending on the results of the Allied Setup Table. Place the Haifa Pipeline marker on the Closed box of the Pipeline Status (on the map) as a reminder.

16.2.2 Habbaniyah, Arab Revolt & Game Length VP

  • If the Axis player conquers Habbaniyah (1617) add one Axis VP. This VP is not lost even if the Allied forces retake Habbaniyah.
  • If the Arab revolt occurs, and lasts two or more GTs, the Axis player adds one VP.

Example: The Arab revolt happens on GT 3. If there is at least one Arab city still in revolt at the beginning of GT 5, the Axis player earns 1 VP.

  • If the Arab revolt lasts longer, the Axis player cannot add additional VPs.

16.3 Victory Conditions

  • At the end of the last GT (GT 12: September II, 1941) players must count the number of map-labeled VP hexes controlled by the Allied player and subtract the number of Axis VPs.
  • If the grand total is six: Then the Allied player wins an operational victory.
  • If the grand total is seven: Or more, then the Allied player has earned a strategic victory.
  • If the grand total is five or less: Then the Axis player wins.

17.0 Optional Rules

The following rules enhance the historical experience of the game. Players must decide beforehand if they want to use none, some, or all the following rules.

17.1 German Parachute Reinforcements

When playing the Air Support to Vichy Syria marker the Axis player sends in two parachute regiments and two extra air units. These units will deploy on or adjacent to any friendly airbase in Vichy Syria.

  • The Axis player decreases the Axis VP total by two (one for the Air Support to Vichy Syria diplomacy marker and one for the German reinforcements).

17.2 Desert Movement

Roll 1d6 when moving an Allied unit or stack across one or more desert hexes. On a DR of 1, units pay a movement cost of 2 MPs per hex.

17.3 Iraqi Commitment

If using this optional rule, ignore the Iraqi attack limits. The Iraqi units can move and attack normally within Iraq.

  • The Axis player does not need to play an Iraqi Junta marker to move or attack an Allied unit or stack. (Remove all Junta markers from play.)
  • Iraqi units can enter Transjordan hexes.
  • Also decrease the Axis VP total by three at the end of the game.

17.4 Iraqi Irregulars

The Axis player may use the FalQ irregular unit to harass Allied units in Iraq after GT 2. The Axis player can use the FalQ irregular unit during the Allied Movement Segment.

  1. When an Allied land unit or stack moves across any hex within four hexes of Baghdad (1618), the Axis player may announce that he is going to use the FalQ unit.
  2. The Axis player rolls 1d6.
    • DR of 4–6: The Allied unit or stack must stop that movement and may move no further that GT.
  3. The Allied player rolls 1d6.
    • DR of 5–6: The FalQ unit is eliminated. Otherwise, it is available again the next GT.

18.0 Designer's Notes

Path to Victory takes its title from the interesting work of Douglas Porch's The Path to Victory: The Mediterranean Theater in World War II. After a winter of Allied successes, Germany attacked in the Balkans in April 1941. Within a month, Yugoslavia and Greece fell. Meanwhile, the Afrika Korps defeated the British in Libya and advanced to the Egyptian border. In Iraq, the colonels of the Golden Square, emboldened by the German victories in the Balkans, restored the pro-Axis prime minister Rashid Ali and asked Germany for help. In Egypt, nationalist generals such as Aziz el Masri were in contact with the German intelligence to flee the country, and King Faruk of Egypt himself secretly conveyed to the German diplomats (by means of his son-in-law, Zulficar Pachá, minister of Egypt in Iran) his sympathies for Hitler and Germany.

This game simulates the volatile situation of the spring and early summer of 1941 in the Middle East when the British position in the Middle East seemed more fragile than ever. The events of the Arab revolt of the late 1930s were fresh in everyone's minds, and the possibility of German encouraging unrest and Arab nationalism was quite real. The possibility of a German takeover in Iran motivated the British and Soviets to invade the country in the summer of 1941.

For the Allied player, it is a race against time: they need to defeat and occupy three large countries in a limited timeframe with very scarce resources, while the Axis player must prevent them from doing so.

The Middle East campaign of 1941 was largely won by a display of airpower, hence the relatively detailed subsystems focusing on the use of airpower. Fortunately for the British, the Germans focused on the imminent Operation Barbarossa, so the Mediterranean and the Middle East was a sideshow within a secondary theatre. By mid-summer 1941, the Allied forces had stabilized the situation in the Middle East, defeating the Iraqi Junta, occupying Iran and conquering the French mandate of Syria and Lebanon, all while fighting a multiple-front campaign in Greece, Crete, East Africa and, of course, the Western Desert.

19.0 Random Events

DR 1: Greek Campaign. The Australian forces return from Greece.

  1. Roll 1d6.
    • DR of 1–3: The 21 Au and 25 Au arrive on the next GT.
    • DR of 4–6: The units arrive in the current GT.
  2. Place the Greek Campaign marker on the GT Record Track as a reminder.
    • If after GT 5, treat as No Event.
    • Treat as No Event if rolled again.

DR 2: Crete Campaign. The air assault on Crete takes a massive toll on the German air transport arm.

  1. Roll 1d6.
    • DR of 1–2: German and Italian air units are placed in the Maintenance Box instead of the Flown Box each time they are flown for the remainder of the game.
  2. Place the Crete Campaign marker on the GT Record Track as a reminder.
    • Treat as No Event if rolled again.

DR 3: Africa Orientale Italiana. Campaign against Italian East Africa takes longer than was the case historically.

  1. The 5th Indian Brigade units joins on GT 6.
  2. Place the A.O.I. marker on the GT Record Track as a reminder.
    • If it is after GT 5, treat as No Event.
    • Treat as No Event if rolled again.

DR 4: Axis Offensive in the Western Desert. Axis Offensive in Cyrenaica.

  1. Delay the arrival of up to three scheduled Allied air reinforcements until the next GT (Axis choice).
  2. Place the Axis Offensive W.D. marker on the GT Record Track as a reminder.
    • If it is after GT 5, treat as No Event.
    • Treat as No Event if rolled again.

DR 5: Operation Battleaxe. The 8th Army attacks at Sollum.

  1. Roll 1d6.
    • DR of 1–3: No Effect.
    • DR of 4–6: The British cancel Battleaxe and send extra tank units to the Middle East. Deploy two tank battalions to any Allied-controlled town or city in Transjordan or Palestine.
  2. Place the Battleaxe marker on the GT Record Track as a reminder.
    • Treat as No Event if rolled again.

DR 6: No Event.

20.0 Allied Setup & Iraqi Coup Table

Roll 1d6 and apply the result (see 3.2).

DREffects
1–2• Deploy one infantry battalion (broken down from the 20th Indian Brigade) at Habbaniyah (1617).
• Place the 20th Indian Brigade (reduced to three steps) in the Persian Gulf Box.
• Place the Haifa Pipeline on Closed on GT 1.
3–4• Deploy two infantry battalions (broken down from the 20th Indian Brigade) at Habbaniyah (1617).
• Place the 20th Indian Brigade (reduced to two steps) in the Persian Gulf Box.
• Deploy one T air unit (VAL) and one MB air unit (Wellington) to any friendly air base.
• Place the Haifa Pipeline on Closed on GT 2.
5–6• Deploy two infantry battalions (broken down from the 20th Indian Brigade) at Habbaniyah (1617).
• Place the 20th Indian Brigade (reduced to two steps) in the Persian Gulf Box.
• Deploy one T air unit (VAL) and one MB air unit (Wellington) to any friendly air base.
• Place the Haifa Pipeline on Closed on GT 2.
• The Allied player receives the Iraqi Regent marker and places it at Amman (1203). See 13.4.1.
  • 2.6 Unit Sizes
  • 2.7 Unit Designation & Nationalities
  • 2.8 Abbreviations on the Units
    • 2.8.1 British Commonwealth & Arab Legion Allies
    • 2.8.2 Free French Allies
    • 2.8.3 Soviet Allies
    • 2.8.4 Iraqi Axis
    • 2.8.5 Vichy France Axis
    • 2.8.6 Aircraft Types
  • 5.11.2 Allied Basra Landing
  • 5.11.3 Axis Basra Landing Opposition
  • 5.11.4 Allied Bandar-e-Sharpur Landing
  • 5.12 Neutral Territories
  • 8.13 Advance After Combat
  • 8.14 11th Commando Unit
    • 8.14.1 Bridge Capture
    • 8.14.2 Headquarters Raid
  • 10.9 Disrupted Marker Withdrawal
  • 10.7 AA Fire
    • 10.7.1 HQ AA Fire
    • 10.7.2 Airbase AA Fire
    • 10.7.3 AA Fire Aborted Air Recovery
  • 10.8 The German & Italian Expeditionary Contingent
    • 13.4.1 Iraqi Regent
    • 13.4.2 Mufti of Jerusalem
  • S Syria: South Syria Sector
  • SM: Moroccan Spahis (Moroccan light cavalry)
  • ST: Tunisian Spahis
  • SM79: Savoia Marchetti 79
  • Val: Vickers Valentia