RulesPal
Chat
Rulebook
Siege of Jerusalem AD70 thumbnail

Siege of Jerusalem AD70

Siege of Jerusalem AD70 Rulebook

Table of Contents

Table of Contents

  • 1.0 Introduction
    • 1.1 Scale
  • 2.0 Components
    • 2.1 Map
      • 2.1.1 Map Definitions
      • 2.1.2 Charts, Tracks, & Displays
      • 2.1.3 Command Pool
    • 2.2 Counters
    • 2.3 Combat Units
      • 2.3.1 Unit Information
      • 2.3.2 Good Order & Disordered Units
      • 2.3.3 Unit Designations, Nationalities & Sides
      • 2.3.4 Unit Abbreviations
    • 2.4 Markers
    • 2.5 Terminology
  • 3.0 Victory Conditions
    • 3.1 Sudden Death Victory
    • 3.2 End Game Victory Points (VP)
      • 3.2.1 Judean VP
      • 3.2.2 Roman VP
      • 3.2.3 End Game Level of Victory
  • 4.0 Set Up
    • 4.1 Roman Set Up
    • 4.2 Judean Set Up
    • 4.3 First Player
    • 4.4 Command Markers
    • 4.5 Other Markers
  • 5.0 Sequence of Play
    • 5.1 Structure
    • 5.2 Sequence of Play
  • 6.0 Building & Reinforcements
    • 6.1 Build Points
    • 6.2 Roman BP
    • 6.3 Judean BP
    • 6.4 Building Reinforcement Units
    • 6.5 Reinforcement Deployment
    • 6.6 Replacements
    • 6.7 Roman Special Reinforcements
  • 7.0 Activations
    • 7.1 Leader Activations
    • 7.2 Determining Command Radius
    • 7.3 Roman Contingents
    • 7.4 Judean Contingents
    • 7.5 Effects of Activation
    • 7.6 Unit Initiative
    • 7.7 Disposition of Command Markers
    • 7.8 Summons of the Trumpet
    • 7.9 Maximum Effort Command Marker
      • 7.9.1 Maximum Effort Effects
  • 8.0 Events & Morale Checks
    • 8.1 Event Procedure
    • 8.2 Morale Check Procedure
  • 9.0 Siege
    • 9.1 Missile Engines
    • 9.2 Siege Towers
    • 9.3 Battering Rams
    • 9.4 Siege Engine Attacks
    • 9.5 Siege Attack Procedure
  • 10.0 Ramps, Breaches & Rubble
    • 10.1 Building Ramps
    • 10.2 Ramp Effects
    • 10.3 Ramp Destruction
    • 10.4 Breaches
    • 10.5 Rubble
    • 10.6 Effect of Breaches & Rubble
  • 11.0 Stacking
    • 11.1 Stacking Limits
  • 12.0 Zones of Control
    • 12.1 ZOC Negation
    • 12.2 EZOC & Movement
    • 12.3 Disengagement
  • 13.0 Movement
    • 13.1 Movement Procedure
    • 13.2 Terrain Costs
    • 13.3 Road March
  • 14.0 Judean Infiltration
    • 14.1 Restrictions
  • 15.0 Combat
  • 16.0 Melee Combat
    • 16.1 Melee Combat Sequence
    • 16.2 CRT Shifts
      • 16.2.1 Leader Shifts
      • 16.2.2 Maximum Effort
      • 16.2.3 Terrain Shifts
      • 16.2.4 Other Shifts
  • 17.0 Missile Fire Combat
    • 17.1 Range
    • 17.2 Targeting & LOS
    • 17.3 LOS & Height Advantage
    • 17.4 Rubble & Breaches
    • 17.5 Missile Fire Procedure
    • 17.6 Shifts
    • 17.7 Fire Combat Details
  • 18.0 Combat Results
  • 19.0 Retreat
    • 19.1 Direction of Retreat
    • 19.2 Retreat Restrictions
    • 19.3 Retreat & Multiple Defense
  • 20.0 Pursuit
    • 20.1 Pursuit Procedure
    • 20.2 Mandatory Pursuit
  • 21.0 Fall Back
    • 21.1 Roman Fall-Back Procedure
    • 21.2 Judean Fall Back Procedure
  • 22.0 Unit Status & Rally
    • 22.1 Rally from Disorder
  • 23.0 Special Units
    • 23.1 Leaders
    • 23.2 Elites
  • 24.0 Roman Camps
    • 24.1 Camp Characteristics
  • 25.0 Special Tactics
    • 25.1 Flank Attacks
    • 25.2 Cavalry Charge
    • 25.3 Roman Orbis
    • 25.4 Roman Multiple Lines
  • 26.0 Roman Outer Walls
    • 26.1 Effects of the Outer Walls
  • 27.0 Stratagems
    • 27.1 Return
    • 27.2 Fog of Treachery
  • 28.0 Fog of War
  • 29.0 Greater Judea
  • 30.0 Optional Rules
    • 30.1 Additional Roman Forces
    • 30.2 Roman Marines
    • 30.3 Repairing Breaches
    • 30.4 Stacking & Attack Order
    • 30.5 Pursuit Combat

1.0 Introduction

Siege of Jerusalem is a two-player wargame simulating the epic Roman assault on the city of Jerusalem in AD 70. The battle pits a veteran Roman army commanded by Titus Flavius against Judean rebels who are making an epic stand. The game system emphasizes command control and the use of both troop and siege units. Players randomly pick command markers to generate actions, modeling the chaos of battle. The Roman objective is to take Jerusalem, while the Judean objective is to delay the Romans long enough to claim an apocalyptic victory.

There are two players in the game: Roman and Judeans. The game consists of five months of battle (one game turn (GT) each). Within each month there will be several impulses, each generated by the pick of a command marker.

Designer's Note: Siege of Jerusalem is based on the Alesia (S&T issue 312) and Fight the Fall (S&T issue 324) game systems, but there are modifications to model this campaign.

1.1 Scale

Each hex on the map represents 200 yards. Each Roman Legionary unit represents two cohorts (800 to 1000 men). Cavalry units are about 400 each. Auxiliary units represent groupings of 1000 men. Judean units range from 500 to 2500 fighters. A leader represents a great man or a lower commander along with their staff and elite guard troops.

A GT represents about a month of operations. Each GT will include Impulses representing anywhere from a day to a couple weeks of intense combat plus periods of reorganization.

2.0 Components

A complete game of Jerusalem includes a 22×34-inch game map, this rule set, and a sheet of 228 9/16-inch counters. Players must provide two six-sided dice to resolve combat and other random game events.

2.1 Map

The map shows the city of Jerusalem and its environs as it was in AD 70. A hexagonal (hex) grid has been superimposed over the terrain features on the map to regularize the movement and positioning of the playing pieces.

  • Each hex contains in hex and hexside terrain that can affect unit movement and combat. The various terrain features on the map have had their exact real-world configurations altered slightly to make them coincide with the hex-grid, but the relationships among the differing terrain types from hex to hex are accurate enough to present players with the same space/time dilemmas that would have been faced by their historic counterparts.
  • Every hex on the map has a unique four-digit identification number printed within it. These will help players find exact locations more quickly and allow for the recording of unit positions to save a match.

2.1.1 Map Definitions

Jerusalem refers to all hexes within the walls. There are four sub-areas within Jerusalem:

  1. Old City (including the Upper City and Lower City)
  2. Second (Middle) City
  3. Temple Compound (including the Antonia Fortress)
  4. New City

Defenses: Wherever there are both wall and fortress symbols in a hex, the fortress takes precedence.

2.1.2 Charts, Tracks, & Displays

Each side is provided with various displays (holding boxes). Their use is described in the pertinent sections of the rules. Additionally, various tracks, tables, and charts are provided.

  • Month of Battle Track: Used to indicate the current GT.
  • Terrain Effects Chart (TEC): Lists the effects of terrain on movement and combat.
  • Combat Results Table (CRT): Used to resolve combat (Melee and Fire).
  • Siege Engine Attack Results Table (SERT): Used to resolve siege engine attacks.
  • Build Charts: Lists the cost to recruit reinforcements.
  • Build Point Tracks: Used to indicate the number of build points (BP) available for each side.
  • Stratagems Table: Lists the effects of stratagem markers.
  • Events Tables: There is one Roman and one Judean Events Table. They are used to resolve random events.
  • Siege Engine Effects Summary: Displays the effects of terrain and possible results when conducting siege unit attacks (9.0).
  • Judean Infiltration Table: Used to determine the success of Judean infiltration (14.0).

2.1.3 Command Pool

Players will need two large-mouth opaque containers, such as empty coffee cups or inverted helmets. One is the Roman Command Pool; the other is for the Judean Command Pool. Throughout the course of a game, players will draw command markers at random from their respective pools.

2.2 Counters

There are two basic types of counters: combat units and markers.

  • Combat units represent the combat formations that existed at the time.
  • Markers allow players to note the specific status of a hex or unit(s) and function as memory aids.
  • After reading these rules at least once, carefully punch out the counters. Trimming off the dog ears from their corners with a fingernail clipper will facilitate easier handling and stacking during play and enhances their appearance.

2.3 Combat Units

Each combat unit counter displays specific types of information: nationality, historic identification, unit type, combat strengths, and special abilities.

Leader Units (counter diagram labels, as printed): Name; Leader Value; Combat Factor; Movement Factor; Roman Regular Reinforcement Code; Army Commander; Subordinate Commander.

Important: The colored boxes around the leader value of Roman subordinate commanders matches the color of the unit type symbol of those units that are part of that leader's sub-command.

Combat Units (counter diagram labels, as printed): Designation; Unit Type Symbol; Elite Unit Box; Combat Factor; Movement Factor; Missile Range.

Roman Unit Types (counter key): Army Commander; Subordinate Commander; Legionary Infantry; Classis Infantry; Light Infantry (Auxiliary Cohorts); Missile Infantry (Sagittarii); Heavy Cavalry (Cataphractarii); Medium Cavalry (Equites); Horse Archer (Equites Sagittarii); Siege Engine (Scorpions & Towers); Antesignani (ANTSIG) Legionaries trained as light infantry (optional, 30.1); Roman Camp (Static Unit); Battering Ram; Ramp.

Judean Unit Types (counter key): Army Commander; Subordinate Commander; Fanatic (Zealot) Infantry; Regular Infantry (Lorica Rebels); Militia Infantry; Missile (Archers); Siege Engine (Scorpions).

2.3.1 Unit Information

  • Combat Factor: The unit's combat strength when attacking.
  • Movement Factor (MF): The number of hexes through which a unit can move in a single impulse (in hex and hexside terrain may affect the number of hexes). Units with a movement factor of zero cannot move.
  • Leader Value (command radius): The number of hexes (exclusive of the leader's hex and including the unit's hex) away a leader can provide command to subordinate units.
  • Range Value: A missile unit can conduct offensive missile combat.
  • Important: When determining command status or range for a missile unit, do not count the hex the leader/missile unit occupies, but do count the hex occupied by a subordinate unit or target unit (17.1).
  • Missile Unit: Units which can use offensive ranged combat and fire defensive fire.
  • Elite Unit: Units that receive combat enhancements and have a colored box around their combat factor.
  • OPT: Optional units are only used when optional rules are being played.
  • R: Roman regular reinforcement (other reinforcements are designated by scenario rules).

2.3.2 Good Order & Disordered Units

Combat units are printed with two sides: the front of the counter is the unit's good order side while the back of the counter is its disordered side.

2.3.3 Unit Designations, Nationalities & Sides

Units may be identified by a title, a number, or a name.

Each Roman Legion consists of a leader, a camp, five infantry units, and an optional light infantry unit.

Contingents: Each side is divided into contingents. Each contingent is identified by the color of the unit counters. Contingents affect command control and stacking.

  • Judean: There are two Judean contingents:
    • Simon Force: Dark Blue (scorpions are light blue).
    • Yohanan Force: Green (scorpions are light green).
  • Roman: There are two Roman contingents:
    • Roman Regular Legionaries: Red.
    • Roman Auxiliaries: Light Red.
    • Important: Roman legionaries and Roman Auxiliaries are part of a single contingent.
    • Roman Allied: Brown. Roman Allied units represent various client forces.
    • Roman Siege Units: Orange (siege units are not a contingent, they are colored differently to allow players to easily identify them).

2.3.4 Unit Abbreviations

  • Alx: Alexandriae
  • Antsig: Antesignani (legionary light infantry (30.1))
  • Apol: Apollinaris
  • Classis: Marines (30.2)
  • Coh Eq: Cohortes Equestrian (mixed infantry/cavalry)
  • Eq Sing: Equites Singularis (guard cavalry)
  • Expl: Exploratores (reconnaissance)
  • Fre: Fretensis
  • Ful: Fulminata
  • Lncr: Lanciarii (spearmen, i.e., Guards (6.7))
  • Mac: Macedconicae (spelling as printed in the booklet)
  • Praet: Praetorians (6.7)
  • Eq Sagt: Equites Sagittarii (Horse Archers)
  • Vol: Volunteers (6.7)

2.4 Markers

Command Markers: Each side has seven command markers. They provide command control and special events.

  • Roman Command Markers
  • Judean Command Markers

Tactical markers: Represent various special battlefield situations:

  • Breach: (printed on the backs of the rubble markers) Indicates a destroyed wall hexside.
  • Cavalry Charge: (printed on the backs of Orbis markers) Roman special cavalry tactic.
  • Infiltration: (printed on the backs of Orbis markers) Judean special movement tactic.
  • Orbis: Roman special tactic formation.
  • Outer Walls Built: Indicates that the Romans have built a line of fortifications to cut off Jerusalem.
  • Rubble: Indicates an urban, fortress, objective hex, or wall hexside, that has been destroyed.
  • Stratagems: Extraordinary actions and skullduggery.

Administrative Markers:

  • Month: Used on the Month of Battle Track to indicate the current GT.
  • Activate Romans / Activate Judeans: Used on the map to indicate the activated leader.

2.5 Terminology

  • Build Points (BP): A quantification of materiel and morale, used to recruit reinforcements.
  • Deploy: The act of placing a unit on the map (either during initial setup or as a reinforcement).
  • Discard: Remove a marker without playing it.
  • Force: A group of units taking an action together.
  • Friendly/Enemy Units: Friendly units are units controlled by one player; enemy units are those controlled by the other player.
  • Impulse: A subdivision of a GT in which players move and attack with their forces. Each GT may consist of up to 14 impulses.
  • Intact: A map feature (such as a Fortress hex) that has not been destroyed (i.e., rubble or breach marker placed).
  • May: The player may choose to take or not to take an action.
  • Must: The player is required to take the action.
  • Occupied: A hex is occupied if one side or the other has a unit in the hex.
  • Pick: Randomly draw a command marker from the pool.
  • Select: The player may choose the exact unit or marker.
  • Stack: One or more units in a single hex.

3.0 Victory Conditions

There are two ways to win Jerusalem: Sudden Death and End Game.

3.1 Sudden Death Victory

A player wins a Sudden Death victory if one of the conditions below is in effect. At this point, the game comes to an end and victory is declared.

  • Roman Sudden Death Victory: If at any time the following are both in effect:
    • a) Roman or Roman Allied infantry/cavalry units occupy all fortresses (including the temple fortress) and objectives in Jerusalem; and,
    • b) There are no Judean leaders on the map.
  • Judean Sudden Death Victory: Beginning GT 2, if at the start of the Monthly Interphase (5.0), the Romans do not occupy any fortresses (intact or not).

3.2 End Game Victory Points (VP)

If neither side achieves a Sudden Death victory, then the game will come to an end at the conclusion of GT 5 and each player will determine the number of VP awarded.

3.2.1 Judean VP

Award the Judean player VP for each of the below eliminated Roman units:

  • Roman or Roman Allied Leader: Number of VP equal to the leader's value.
  • Elite Unit: 1 VP.
  • Other Units: 0 VP.

Award the Judean player VP for each of the below hexes, if occupied by Judean combat units (the hex may contain a rubble marker):

  • Temple Hex: 12.
  • Other Fortress Hex: 2.
  • Objective Hex: 1.

3.2.2 Roman VP

Award the Roman player VP for each of the below eliminated Judean units:

  • Judean Leader: Number of VP equal to the leader's value.
  • Elite Unit: 1 VP.
  • Other Units: 0 VP.

Award the Roman player VP for each of the below hexes, if occupied by Roman or Roman Allied combat units (the hex may contain a rubble marker):

  • Temple Hex: 5.
  • Other Fortress Hex: 3.
  • Objective Hex: 1.

Important: Eliminated units that are replaced do not count for VP.

3.2.3 End Game Level of Victory

At the end of the game, each player totals their respective VP. The side with fewer VP subtracts its total from the side with more VP. The players then determine the level of victory for the side with the greater number of VP.

  • 0–12: Draw
  • 13–24: Provincial Victory
  • 25–36: Consular Victory
  • 37 or more: Triumphant Victory

4.0 Set Up

Players set up the game using the following procedure. All units are initially placed face up (good order side up). Stacking restrictions must be met (11.0).

4.1 Roman Set Up

The Roman player sets up first. Deploy the following units within two hexes of any map edge hex between hex 2607 and 2619 (inclusive) and/or within two hexes of any map edge hex between 0102 and 0113 (inclusive). Units may also be placed in the Greater Judea Display:

  • Leaders: Titus and Alexander.
  • Legions: V, X, XII, XV (each legion consists of one leader and five legionary units).
  • Auxiliary Units: All 25 Auxiliary infantry, missile, and cavalry units.
  • Roman Allied Units: The Roman player randomly picks ten Roman Allied units.
  • Roman Reinforcements Display: Place the seven Roman units with the "R", all remaining Roman Allied units, all five Roman Camps and all Roman siege units in the Roman Reinforcement Display. Place the unit listed as Event aside. It may enter as a special reinforcement (6.7). Important: Only use OPT units if using the optional rules.
  • Build Point Marker: Place the marker in the "4" box of the Roman Build Points Track.
  • Command Markers: Place the four Roman command markers and the event marker in the Command Pool.

4.2 Judean Set Up

The Judean player sets up second. Units are deployed in specific areas within Jerusalem defined as:

  • New City: All New City hexes.
  • Eastern Sector: Lower City (east of the slope), Temple Compound, and Antonia fortress.
  • Western Sector: Upper City (west of the slope) and 2nd (Middle) City.

The Judean player deploys the following units as desired within the areas listed below:

  • Eastern Sector and New City:
    • Leaders: Yohanan and Eleazar.
    • Yohanan Contingent: Randomly pick 12 non-siege engine combat units.
  • Western Sector and New City:
    • Leaders: Simon and Cathlas.
    • Simon Contingent: Randomly pick 20 non-siege engine combat units.
  • Judean Reinforcement Display: All remaining Judean units (including all siege units).
  • Build Point Marker: Place the marker in the "0" box of the Judean Build Points Track.
  • Command Markers: Place the four Judean contingent command markers and the event marker in the Command Pool.

4.3 First Player

The Roman player is the First Player, and the Judean player is the Second Player (5.2).

4.4 Command Markers

Each player places their Maximum Effort and Morale Check markers aside.

  • The maximum effort marker may be placed in the pool during a GT (7.9).
  • Both morale check markers are added to their respective command pools at the beginning of GT 2.
  • All remaining command markers are placed in their respective command pools.

4.5 Other Markers

Each player places his stratagems markers in their respective Stratagems Pool. Rubble, Breaches, Ramps and Tactics are set aside until required.

5.0 Sequence of Play

Jerusalem is played in GTs (maximum of five).

  • Each GT is comprised of a Build Phase and multiple Impulses followed by an Inter-Phase.
  • Each impulse is generated by the pick of a command marker and each Impulse consists of up to six phases.
  • The player who is conducting the impulse is the phasing player, the other player is the non-phasing player.
  • During a player's Impulses, the phasing player will activate units, conduct movement, and execute combat.
  • Each GT ends with an Inter-Phase in which players perform various administrative actions.

Important: All actions within a phase takes place in the order given.

5.1 Structure

Each GT will consist of a variable number of impulses. Players continue conducting Impulses until one of the following occurs:

  1. One side wins a Sudden Death Victory (3.1).
  2. There are no more command markers remaining in both players' pools.
  3. If this is Month V, then the game comes to an end and players check for victory (3.2).

5.2 Sequence of Play

Build Phase

  1. The Roman player conducts the following: a) May remove one or more camp units (24.1). b) Determines the number of BPs received (6.2). c) Expends BP to build reinforcement units, camps, ramps, siege units, stratagems (4.5), and outer walls.
  2. The Judean player conducts the following: a) Determines the number of BPs received (6.3). b) Expends BP to build reinforcement units, siege units, and stratagem (4.5).

First Player Impulse: The Roman player is always the First Player.

  • Command Marker Phase: The phasing player picks one command marker from his Command Marker Pool and places it in his Command Marker Display (7.7).
  • Activation Phase: The Phasing player indicates the leaders and/or units that are activated (7.0).
  • Ranged Fire & Siege Attack Phase: The phasing player conducts the following in any order desired:
    1. Siege Engine Attacks (9.0)
    2. Offensive Missile Fire (17.0)
  • Movement Phase: The phasing player may move friendly activated units (7.0 & 13.0). If the Roman player is the phasing player, Orbis markers can be removed and placed (25.3).
  • Melee Phase:
    1. If the Roman player is the phasing player, ramps may be placed at the beginning of the phase (10.1).
    2. The phasing player (Roman or Judean) conducts melee combat with friendly units that are adjacent to enemy units (16.0). Battering rams may be employed at this time.
  • Activation Removal Phase: The phasing player removes all activation markers from friendly units.

Second Player Impulse: The Judean player conducts the impulse as outlined in the First Player Impulse.

Subsequent Impulses: Continue alternating between the First and Second Impulse turns until one of the conditions of 5.1 apply.

Monthly Inter-Phase: If this is the end of Month V, the game comes to an end and players determine victory (3.2). If this is the end of Month I, II, III or IV, perform the following:

  • Command Marker Return Phase: Both players place all command markers back into their respective Command Markers Pool. If a player's maximum effort command marker has not been used in this game, the player may place the marker in his Command Pool (7.9).
  • Fall Back Phase: First the Romans and then the Judeans move applicable units per (21.0).
  • Rally Phase: Both players rally disordered units (22.1).
  • Game Turn Advance: Move the GT marker to the next box on the Month of Battle Track and begin the next GT.

6.0 Building & Reinforcements

Both players use Build Points (BP) to recruit combat units, siege units and stratagem markers. The Build Table provides BP costs and deployment locations.

6.1 Build Points

Players record build points on their respective Build Points Track using the marker.

  • A player's total BP can never exceed 25 nor may it ever go below zero.
  • BP can be accumulated from GT to GT.
  • Each player begins the game with the number of BP listed in 4.1 and 4.2 and receives BP each GT (including the first GT) during the Build Phase.

6.2 Roman BP

The Roman player receives the following BP at the start of each Build Phase:

  1. Roll two dice (2d6) and total the results.
  2. For each good order Roman camp on the map add two.

6.3 Judean BP

The Judean player receives the following BP at the start of each Build Phase:

  1. Roll 2d6 and add the results together. Important: If the Roman player has completed the Outer Walls, only roll one die (1d6) (26.1).
  2. If a Judean unit occupies the Temple fortress hex and the fortress is intact, add two.
  3. For each other intact fortress hex occupied by at least one Judean unit, add one.

6.4 Building Reinforcement Units

Players build reinforcements during the friendly Build Phase. Players consult the appropriate Build Table.

  • Reinforcements received via events (8.0) do not cost BP.
  • Reinforcement units are not activated by being deployed.
  • Units deployed during initial setup do not cost BP (4.0).

Important: The number of unit counters is a design limit. A player may not build more units of any type than there are existing counters.

  • The Roman player conducts the following procedure:
    1. Determine the type of unit that will be built.
    2. Expend the required BP.
    3. The Roman player may select any unit within the type being built. The units may come from the Roman Eliminated Units Display or the Reinforcement Display.
  • The Judean player conducts the following steps:
    1. Determine the type of unit that will be built.
    2. Expend the required BP.
    3. Determine the contingent that will build the type.
    4. Randomly pick the unit to be built from the unit type and contingent selected above. The units may come from the Eliminated Units Display or Reinforcement Display.

6.5 Reinforcement Deployment

Placing reinforcements on the map is called deployment. Deployment locations are listed on the Build Table.

  • The deployment of units may require that another unit must be in the deployment hex. In such cases, the required occupying unit must have been in the hex at the beginning of the Build Phase.
  • If a unit is built and it is then determined there is no valid deployment hex, the unit is returned to the appropriate display. A player may not delay the deployment of a unit (the BP is still considered spent).
  • Units may be deployed in an enemy zone of control (12.0). They may not be deployed in a hex occupied by an enemy unit, nor may they be overstacked (11.0).

6.6 Replacements

When units are eliminated, they are placed in the appropriate Eliminated Units Display. Exception: Army commanders cannot be replaced. When eliminated they are placed aside, they may not return to the game.

6.7 Roman Special Reinforcements

These units are not part of any Legion:

  • Praetorian Cohort: The unit marked as Event is deployed per the Vespasian event.
  • Volunteers, Lanciarii, and Tribunes: May be built and deployed as reinforcements (those units marked with an "R").

7.0 Activations

Players activate Leaders to initiate movement and offensive missile fire. Unless specifically required by a rule, a unit does not have to be activated to perform other actions.

7.1 Leader Activations

When a player picks a command marker, he may activate the number of leaders equal to the number on the marker.

  • Place an activated marker on each such leader. The marker remains on that leader until the Activation Removal Phase, at which point it is removed.
  • Example: If a marker reads III, then the player may activate three leaders.
  • The activated leaders and all friendly units within the leader value/command radius are activated. This is determined during the Activation Phase.
  • An army leader can activate subordinate leaders; however, a leader activated in this manner does not apply its command radius to other units.

7.2 Determining Command Radius

The command radius is traced from the activated leader's hex (exclusive) out to the distance in hexes equal the leader's command radius.

  • Example: A leader with a command radius of two would activate all units in its hex and all units up to two hexes from that leader.
  • Command radius is not blocked by enemy units, EZOC, or terrain.
  • A leader with a command radius of zero only activates units in the same hex.
  • There is no additional effect if more than one leader exerts a command radius into a hex.

7.3 Roman Contingents

When a Roman activation marker is picked, the Roman player may activate any combination of Roman Regular, Auxiliary, and Allied units/leaders.

  • An activated Roman army commander can activate all friendly units of any contingent or legion within its command radius.
  • A legion commander may only activate legion units of his own legion and any Allied/Auxiliary units within his command radius.
  • An activated Allied leader can only activate Allied units.

7.4 Judean Contingents

When a Judean activation marker is picked, it will specify either the Simon or Yohanan contingent.

  • Simon: Only leaders and units belonging to Simon Force may be activated.
  • Yohanan: Only leaders and units belonging to Yohanan Force may be activated.

7.5 Effects of Activation

Units need to be activated to:

  1. Move in the Movement Phase (13.0).
  2. Fire in the Ranged Fire & Siege Attack Phase (17.0).
  3. See Special Tactics Rules (25.0) for additional information on activations and actions.

Important: Units do not need to be activated to engage in melee combat, or other game actions not listed above.

7.6 Unit Initiative

Instead of activating a leader, the player may designate one hex containing friendly units of any type. Activating a unit or stack of units in this manner expends one activation.

Important: The Judean player may only designate units corresponding to the contingent that was drawn.

Example: The Judean player picks the Simon II marker. The player could activate one leader and one stack of units in the same hex that are part of the Simon contingent.

7.7 Disposition of Command Markers

After a command marker is picked, it is placed in the appropriate Command Markers Display. All command markers are returned to the Command Marker Pool during the Command Marker Return Phase.

7.8 Summons of the Trumpet

  • No Passing: If a player has command markers remaining in the pool, the player must pick a command marker.
  • Multiple Activations: A unit may be activated more than once per GT.
  • Asymmetry: One side may have more command markers in their pool. This means they may be taking successive impulses (no enemy impulse) if one side has remaining markers and the other side does not.

7.9 Maximum Effort Command Marker

Each player has a maximum effort command marker.

  • A player may add this marker to his Command Pool during the Command Marker Return Phase of any GT.
  • The maximum effort marker may only be played once during a game. Once placed in the pool and then drawn it is set aside.
  • Players are not required to tell their opponent that the marker has been added to the command pool.

7.9.1 Maximum Effort Effects

When drawn, the maximum effort marker allows:

  1. The player to activate all friendly leaders of all friendly contingents. Non-leader units cannot be activated (unit initiative (7.6)) if not within the command radius of an appropriate friendly leader.
  2. Awards one right column shift to all friendly melee attacks.

8.0 Events & Morale Checks

Each player has one event and one morale check marker.

  • If one of the above command markers is picked (during the Command Marker Phase (5.2)), the player will conduct the event or conduct a morale check. Once the event or morale check is complete, the player's impulse is complete (i.e., do not pick another command marker). No combat or movement take place. Subsequent impulses are taken normally.

8.1 Event Procedure

When a player picks an event command marker, the player consults his Events Table and rolls 1d6, cross-referencing the result with the appropriate event. The event is applied immediately.

  • If the event calls for reinforcements, the player follows the procedures in 6.0 and immediately deploys the unit(s). The player does not expend BP.

8.2 Morale Check Procedure

When a player picks a morale check command marker, the player must conduct a morale check for friendly units.

  • The phasing player must determine the morale break value for his army by totaling the following:

Roman Player:

  • +1: For each Roman Camp on the map.
  • +1: For each Roman occupied Fortress hex (intact or not).
  • −2: If Titus is not on the map.

Judean Player:

  • +2: If the Temple is friendly occupied.

  • +1: For each Judean occupied fortress hex (intact or not).

  • −1: If Simon is not on the map.

  • −1: If Yohanan is not on the map.

  • −1: If the Roman Outer Walls are in effect (26.1).

  • The phasing player then rolls 2d6 and totals the result. Important: For both sides, if the unmodified dice total is two it is an automatic pass. If the unmodified dice total is 12, it is an automatic Panic.

  • Panic: If the total is greater than that player's morale break number, that player's army panics. If panic occurs the player must:

    1. Immediately conduct a fall back (21.0).
    2. Pick one friendly command marker from the pool and place it in the Command Marker Display without playing (if there are no markers remaining, there is no further effect).
  • Pass: If the total is equal to or less than the morale break value, the player may:

    1. Rally all disordered leaders and elite units.
    2. Rally all disordered non-elite units that are within any friendly leader's command radius (all leaders). Contingent requirements apply.
    3. Select one friendly command marker from the Command Marker Display and return it to the Command Marker Pool. Important: Following the outcome of the morale check the GT proceeds as normal.

9.0 Siege

Players use siege units to attack various map features and provide mobility advantages. Siege units include the following:

  • Missile Engines

  • Siege Towers

  • Battering Rams

  • Siege units are built using the reinforcement procedures in 6.4.

  • Only one siege unit may be in a hex. This is in addition to any other units in the hex (11.0).

  • Siege units are treated as mobile units.

  • Siege units may conduct melee (16.0) and may conduct missile fire (17.0). They may also make siege attacks.

  • Siege units cannot pursue and are eliminated if forced to retreat.

Important: The number of siege unit counters is a design limit. Players cannot build more siege units than there are siege unit counters.

9.1 Missile Engines

Missile engines may conduct melee attacks during the Melee Phase. They may conduct ranged fire against enemy units or conduct a siege attack during the Ranged Fire and Siege Attack Phase (not both).

Important: A unit is adjacent to a wall hexside if in a hex that has at least one hexside with a wall.

9.2 Siege Towers

Siege towers may conduct melee attacks during the Melee Phase and ranged fire or a siege attack during the Ranged Fire and Siege Attack Phase. Siege towers also confer the following benefits to other units in the same hex:

  1. Friendly infantry units and/or leaders that are conducting melee combat across an adjacent enemy occupied intact wall hexside or into a fortress hex receive one right column shift on the Combat Results Table. The attacker shifts are cumulative with other combat shifts.
  2. If a siege tower starts a friendly Movement Phase adjacent to an intact wall hexside or fortress hex that is not occupied by enemy units, the infantry units only expend one movement point to enter a fortress hex and one movement to cross a wall hexside.

9.3 Battering Rams

During the Melee Phase, Battering Rams may conduct siege attacks against an adjacent intact wall hexside, or fortress hex.

Important: Battering rams may not conduct melee attacks.

9.4 Siege Engine Attacks

A player conducts siege attacks by using siege units to attack an intact fortress, objective, urban hex, or a hex with an intact wall hexside (15.0).

  • A player may conduct siege attacks with missile engines, battering rams, and siege towers during the friendly Ranged Fire and Siege Attack Phase.
  • Missile engines and siege towers can conduct siege attacks against any intact wall, fortress, urban, and objective hexes within their missile range. Battering rams must be adjacent to an intact wall hexside, and urban and fortress hexes.

Important: See line of sight rules (17.3).

9.5 Siege Attack Procedure

Siege attacks occur during the Ranged Fire and Siege Attack Phase.

  • The phasing player declares that a siege unit is making a siege attack and declares the target of the attack (wall hexside, fortress, objective, or urban hex).
  • The player consults the Siege Engine Attack Results Table and rolls 1d6, applying applicable terrain die roll modifiers (DRM) as appropriate. See Siege Engine Attack Results Table.
  • The player then cross-references the die roll with the type of siege unit to determine the result of the attack.

Important: The combat factor of the siege unit does not affect the attack. The only DRMs that apply are listed on the SERT.

  • When conducting siege attacks against a wall hexside range is determined by counting the closest hex that contains the targeted wall hexside.
    • Example: A siege unit in hex 0603 firing at a wall hexside in hex 0804 would count hex 0704 and 0804 for a range of two.
  • Siege attacks can be in any order, before, after or intermixed with other ranged fire.
  • A given unit can conduct only one siege attack per phase.

Important: Missile engines and siege towers may only make one attack (one regular missile or one siege) per Ranged Fire & Siege Attack Phase.

  • The target of a siege attack does not have to be enemy occupied.
  • The target hex cannot be occupied by a friendly unit.

10.0 Ramps, Breaches & Rubble

Ramps, breaches, and rubble are special markers that change the terrain in a hex or hexside.

10.1 Building Ramps

Only the Roman player may build ramps (6.0). The number of ramps on the map at any one time is limited to the counter mix.

  • When built the player places the ramp marker in the Built Ramps Display until placed on the map during any ensuing Melee Phase.
  • Ramps are placed at the beginning of any friendly Melee Phase on any activated Roman (not Allied or Auxiliary) legion infantry unit that is adjacent to an intact wall hexside or fortress hex.
  • Only one ramp may be in a hex.

10.2 Ramp Effects

Ramps confer the below benefits to any infantry unit and/or leader/commander (of either side):

  1. When moving from a hex containing a ramp across an adjacent intact wall hexside or into a fortress hex, the unit only expends one movement point (this applies when crossing a wall hexside from either direction).
  2. When attacking from a hex containing a ramp across an intact wall hexside or into a fortress, the attacking force receives two right column shifts. The wall or fortress defensive left shifts still apply.

Important: This is not cumulative with any siege tower effect.

10.3 Ramp Destruction

A ramp is destroyed if:

  1. A successful Judean mining stratagem occurs (27.0).
  2. At the start of a Build Phase, a hex containing a ramp is occupied by any Roman infantry unit (not Allied or Auxiliary), the Roman player may remove the ramp from the map. In this case the ramp is eligible to be rebuilt in any eligible hex during the same Build Phase.

10.4 Breaches

A breach represents the destruction of wall hexsides.

  • A breach may be created when:
    1. A missile engine, siege tower, or battering ram conducts a successful siege attack against a wall hexside; or,
    2. The Judean player conducts a successful Judean mining stratagem.
  • A breach affects all wall hexsides of a single hex.

Example: The Roman player conducts a successful breach in hex 2106. The player places a breach marker in the hex and both wall hexsides (2106/2006 and 2106/2005) are breached.

  • When a breach is created the attacking player places the breach marker in the hex to indicate all wall hexsides in that hex are breached.

Important: Breaches are not created by mandatory pursuits.

10.5 Rubble

Rubble represents the destruction of man-made in-hex terrain.

  • Rubble is created in a fortress, urban, or objective hex when:
    1. A missile engine, siege tower, or battering ram conducts a successful siege attack; or,
    2. The Judean player conducts a successful Judean mining stratagem; or,
    3. As a result of a successful pursuit.
  • When rubble is created the player places a rubble marker in the hex to note that the manmade terrain in the hex has been destroyed.
  • If a Roman unit (any type) advances after combat due to a mandatory pursuit (see Combat Results Table) and the unit enters an urban or objective hex, the advancing player must place a rubble marker in the hex.

10.6 Effect of Breaches & Rubble

Once placed, breach and rubble markers remain in place for the remainder of the game.

Important: The number of breach and rubble markers provided are not a limit. Players may create additional markers.

  • Breached wall hexsides no longer exist for all purposes.
  • Fortress, urban, and objective hexes that have a rubble marker are treated as open terrain. Exception: Cavalry must expend three MF when entering rubble hexes.
  • Breach and rubble markers have no effect on stacking.
  • Only one breach and one rubble marker may be placed in any hex.

11.0 Stacking

Having more than one friendly unit in a hex is called "stacking."

  • All types of units can stack together. Important: Units of different contingents cannot stack together. Roman Legionaries and Roman Auxiliaries are in the same contingent (2.3.3).
  • Stacking limits apply at all times. A player cannot move units into a hex in excess of stacking limits, even to move through them.
  • See 19.2 for the effect of stacking when conducting a retreat.
  • If at the end of any Movement or Combat Phase (both friendly and enemy), a hex is found to be overstacked, the owning player must eliminate enough units to reduce the stacks so that it meets the stacking limits.
  • Friendly ground units cannot enter a hex containing enemy units. This includes siege units.
  • Markers of all types do not count for stacking.
  • In general, players are free to arrange the stacking order of friendly units during the friendly Movement Phase (13.0), when retreating (19.0) or pursuing (20.0).

11.1 Stacking Limits

The maximum number of units that may stack in a hex are as follows:

  • Roman:
    • Two combat units (of any type); and,
    • One siege unit; and,
    • One camp unit; and,
    • Any number of leaders.
    • Important: The Roman player may stack up to three units per hex if all three are from the same legion.
    • Example: The Roman player could have three infantry units of the V Mac Legion, any number of leaders, a camp, and a siege tower in the same hex.
  • Judean:
    • Two combat units per hex; and,
    • One siege unit; and,
    • Any number of leaders.

12.0 Zones of Control

The six hexes immediately surrounding a good order combat unit's hex constitute that unit's zone of control (ZOC). The ZOC projected by an enemy unit is referred to as an enemy zone of control (EZOC). Hexes into which a unit exerts a ZOC are called controlled hexes.

  • ZOC have varying effects on enemy movement and combat.
  • All good order combat units (including leaders, camps, and siege units) exert a ZOC. Disordered units do not exert a ZOC.
  • Good order units always exert a ZOC. The activation status of a unit does not affect its ability to project a ZOC.
  • EZOC are not negated by other units, enemy or friendly.
  • Both friendly and enemy units may simultaneously exert 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.

12.1 ZOC Negation

ZOC do not extend into:

  • Fortress Hex: ZOC do not extend into fortress hexes. Units inside of fortress hexes do exert ZOC normally.
  • Roman Camps: Judean ZOC do not extend into Roman camp units. Roman units stacked with camp units do exert ZOC normally.

12.2 EZOC & Movement

A unit must cease its movement when it enters an EZOC. The unit may not conduct any further movement during the current Movement Phase.

  • A unit may never move directly from one EZOC to another EZOC. The EZOCs may be projected by the same or by different enemy units.

Important: Units in an EZOC must conduct melee combat during the Melee Phase.

12.3 Disengagement

A unit that is in an EZOC, must remain in its current hex until one of the following conditions exist:

  1. A unit conducting retreat (19.0) or pursuit (20.0) may exit an EZOC.
  2. The enemy unit(s) no longer project an EZOC into the hex.
  3. The following units may move out of an EZOC: a) Leaders; and, b) Cavalry units, if there are no ZOC of enemy cavalry or leader units exerted into the hex. c) Units using road march (13.3).
  • When applying 3), the first hex the unit enters after exiting an EZOC must be a hex that does not contain an EZOC. The unit may (after the first hex) enter a hex containing an EZOC.

13.0 Movement

A player moves their activated mobile units during the friendly Movement Phase.

  • A player may move any number of activated units.
  • Activated units may move in any direction or combination of directions to the limit of their movement factors.
  • A unit can move out of command radius of a leader.
  • An activated leader may move up to its full movement factors.

Important: Moving an activated leader does not allow the activation of additional combat units, even if those units are now within the command radius of the activated leader.

  • All units can move anywhere on the hex portion of the map.
  • Only Roman units may exit the map. See rule (29.0) for Roman off-map movement.

Designer's Note: Players should move leaders after all other units have been moved to keep things sorted out.

13.1 Movement Procedure

Each unit has a movement factor printed on the counter. Units move by tracing a path of contiguous hexes through the hex grid, until:

  1. The unit has expended all movement factors; or,
  2. The unit enters an EZOC; or,
  3. The owning player decides to cease moving the unit.
  • A unit may expend any number of its printed movement factors in one Movement Phase.
  • Unused movement factors may not be accumulated from phase to phase or GT to GT.
  • Movement factors may not be transferred from one unit to another.
  • Mobile units may always move at least one hex (minimum movement), regardless of the number of movement factors required to enter the hex. Exception: Units using minimum movement may not enter an enemy occupied hex or enter prohibited hexes, nor move directly through from one EZOC to another EZOC.
  • Units with printed movement factors of zero never move once placed onto the map.
  • Once a unit has been moved and the player's hand removed from it, it may not be moved again.

13.2 Terrain Costs

A unit must expend the number of movement factors designated by the Terrain Effects Chart (TEC) to enter a hex.

Important: Roman and Judean units may pay different movement costs for certain terrain types.

  • If there is more than one type of terrain in a hex, use the highest single movement cost from among all the terrain involved.
  • Certain terrain runs along hexsides (such as slopes). Units pay both the hexside movement factor cost and the cost of the terrain in the hex. Fortresses are considered hex terrain, not hexside terrain. The cost listed on the TEC for fortresses (including the Temple) is the total cost for entering the hex.

Important: Cavalry and siege units cannot cross intact walls, unless the hexside contains a gate.

13.3 Road March

Roads enhance mobile unit movement.

  • Units using road march double their printed movement factors.
  • Units using road march ignore all other terrain in a hex when conducting movement.
  • A unit may only use road march if the unit:
    1. Begins and ends its movement on a road hex.
    2. Only moves along contiguous road hexes.
  • Units using road march may begin and/or end their movement in an EZOC.
  • Units that used road march during the Movement Phase may attack, pursue, and/or advance normally.
  • Units entering the map from the Greater Judea Display may use Road March (29.0).

Important: Units using special tactics (25.0) cannot employ road march.

14.0 Judean Infiltration

The Judean player may use infiltration to move certain units directly from one hex within Jerusalem to another without moving through the hex grid.

  • Infiltration movement is conducted during the friendly Movement Phase.
  • Infiltrating units must start in an intact fortress, objective, or urban hex within Jerusalem.
  • At the start of a friendly Movement Phase, the Judean player may place infiltration markers on any number of activated leader or infantry units (this is not limited by the counter mix).
  • After placing any desired infiltration markers, the Judean player must then determine the outcome of the infiltration move by following the below procedure:
    1. Designate one marked unit (or stack of units) at a time; and,
    2. Consult the Judean Infiltration Table (on the map).
    3. Roll 1d6 and implement the result.
  • If the result of the infiltration succeeds the Judean player may move the unit from its current location to another fortress, objective, or urban hex. This move does not require the expenditure of movement factors, nor does it require that the player be able to trace a path from the start hex to the end hex (just pick up the unit and move it to its new location).
  • The unit may not over stack in the end hex.

14.1 Restrictions

  • A unit can make only one Infiltration attempt per Movement Phase.
  • All infantry or leader units in a hex with an infiltration marker must conduct infiltration and must move to the same target hex.
  • EZOCs have no effect on Infiltration.
  • Units cannot end their infiltration move in a hex containing an enemy unit.
  • Units conducting infiltration movement cannot conduct any other type of movement in the same Movement Phase. They do operate normally during any ensuing phase.
  • Infiltration movement may be through any type of terrain, through enemy units, and EZOC.

Designer's Note: Infiltration represents movement by underground tunnels and reflects the greater Judean familiarity with the city.

15.0 Combat

Units engage in combat to force back or destroy enemy units, and to seize terrain. There are three types of combat:

  • Melee

  • Missile Fire

  • Siege Attack

  • Melee and missile fire are resolved on the Combat Results Table (CRT). Siege attacks are resolved on the Siege Engine Attack Results Table (SRT).

  • The phasing player is termed the "attacker"; the non-phasing player is the "defender," regardless of the overall strategic situation.

  • No unit, or stack of units, can launch an attack against more than one enemy occupied stack in a single combat phase. This is so even if adjacent to more than one enemy occupied hex.

  • No unit may attack more than once per phase.

  • A single enemy unit may be attacked more than once per phase if each attack is conducted by different attacking units.

  • The phasing player may only attack from one friendly occupied hex at a time.

Example: The Roman player has two stacks of units adjacent to an enemy occupied hex. The Roman player may declare an attack from one friendly stack and after resolving the melee attack if there are enemy units remaining in the defending hex, the player could then declare another attack against that same hex using the second stack of friendly units.

  • All units may conduct melee attacks; however, only those units that have missile fire capability may conduct ranged missile fire.
  • A unit's combat strength is always unitary. A unit's strength may not be divided among different combats.
  • Units cannot combine their combat strengths when resolving combat.
  • The attacking player may choose which enemy stack to attack and the order in which attacks will be made. The player is not required to declare all attacks in advance. The player declares one attack and after resolving that attack, he may (if eligible units remain) declare another attack.

16.0 Melee Combat

Melee combat is conducted by friendly units attacking adjacent enemy units during the friendly Melee Phase.

  • All friendly units in an EZOC at the start of the Combat Phase must engage in melee combat. They must attack a hex occupied by enemy units exerting a ZOC into their hex.
    • Example: It is the Roman Melee Phase, and a stack of Roman units is adjacent to a hex containing a good order Judean unit and a hex containing a disordered Judean unit. The Roman player must attack the good order units.
  • Units do not have to be activated to engage in melee.
  • Friendly units not in an EZOC may attack adjacent enemy units.
    • Example: A Roman unit is adjacent to a disordered Judean unit. The Roman unit is not required to attack; however, the Roman player may opt to attack the disordered unit.
  • All units in the same hex must attack the same enemy occupied hex. This is so even if units are in the ZOC of more than one enemy occupied hex.

16.1 Melee Combat Sequence

Follow the below melee combat sequence in the order given:

  1. Attack Declaration: The attacker declares which stack will attack which enemy stack. For each attacking stack, all units individually attack the enemy stack.
  2. Combat Strength Determination: For each attacking unit, determine its combat strength. Consult the CRT and locate the column that matches the unit's combat strength.
  3. Combat Shift Determination: Determine and apply the column shifts for the attacker and defender (cumulative) (16.2).
  4. Combat Resolution: Roll 1d6 and cross index the result beneath the final strength column heading. Implement the combat result immediately. Execute any retreats and/or pursuit combats.

Important: The strength of the defender does not figure into this procedure.

16.2 CRT Shifts

Certain conditions will "shift" the combat column. On the CRT Column Shifts Chart, a shift to the right is noted with a "# R" and a shift to the left is noted with a "# L".

  • A CRT column shift to the right means the column is increased by the number of columns indicated (in favor of the attacker).
  • A shift to the left means the column is decreased by the number of columns indicated (in favor of the defender).
  • If both the attacker and defender have shifts, use the cumulative difference.

16.2.1 Leader Shifts

Only one leader on each side may award shifts in each individual combat. A leader does not have to be activated to provide shifts. If there is a leader unit in the same hex as attacking and/or defending units, apply the following shifts (attacking leader provides right (R), defending leader (L) shifts):

  • 2R/2L: If the leader is Simon, Yohanan or Titus.
  • 1R/1L: For any other leader.

Important: A leader shift applies to all units in the stack, including the leader's attack as well as other leaders.

16.2.2 Maximum Effort

If the maximum effort marker was drawn, all friendly attacking units receive one column shift to the right.

Important: Special Tactics (25.0) and Stratagems (27.0) may award additional shifts to the attacker and/or the defender.

16.2.3 Terrain Shifts

Defending units benefit from the terrain in the hex they occupy and, in certain cases, along that hex's sides. Players should refer to the TEC to determining terrain shifts.

  • Roman and Judean units may receive a different number of shifts for a single terrain type.
  • Both natural features and man-made features are referred to as terrain.
  • Benefits for terrain are not cumulative. A defending force can receive only the shift for one type of terrain. If a force potentially has more than one defensive terrain shift available to it, it uses the single best one for that defense.
  • The below terrain types have unique requirements when determining if a shift applies or what exact shift applies:

Ravine Hexes: If a force is defending in a ravine hex, and at least one attacking unit is in a non-ravine hex, shift the combat one to the right.

Designer's Note: Ravines give the attacker a shift because they represent low ground.

  • Jerusalem Urban Hexes:
    • Melee: Only Judean units defending in an urban hex receive a one column shift to the left. Roman units do not receive this shift.
    • Fire Combat: Both sides receive a one column shift to the left.
  • Wall Hexsides: Only award defender shifts if attacking units are attacking from the exterior side of the wall (from the non-teeth side) to the interior side of the wall.

Important: All types of units may attack across wall hexsides (even cavalry).

16.2.4 Other Shifts

In addition to the above, apply the following shifts (if applicable):

  • Roman Camps: Are a unique combat unit, they provide an additional one column shift for Roman defenders, in addition to any terrain shift. This is applied to all units in the hex including the camp itself.

Designer's Note: Roman camps are units, not terrain. So, the Judeans cannot capture and use them, though they can be eliminated.

  • Siege Towers: Roman units attacking when stacked with a siege tower across a wall hexside or into a fortress hex receives one column shift to the right.
  • Ramps: Roman units attacking when stacked with a ramp and attacking into adjacent wall hexsides and fortress hexes receive two column shifts to the right.

Important: Siege tower and ramp shifts are not cumulative.

17.0 Missile Fire Combat

Activated units with a range factor may (including archers and siege units) engage in missile fire combat.

  • Missile fire combat occurs during the friendly Ranged Fire & Siege Attack Phase.

Important: When conducting a melee only, if an "A" result is obtained and if the defender is a missile unit with a range factor the attacking player is disordered. No actual missile fire takes place.

Designer's Note: There is no additional die roll for defensive fire. Also, if more than one fire capable unit is in a hex being attacked, apply only one (A) result.

Important: Disordered units may lose their range factor, in this case, they cannot engage in fire combat. They would regain this capability when rallied.

17.1 Range

Range is the number of hexes through which a unit can conduct missile fire.

  • Range is measured from the unit's hex (exclusive) to the target hex (inclusive).
  • A unit's range is printed on the unit counter.
  • There is no range attenuation.

Designer's Note: This is due to light units operating as skirmisher clouds, thus moving outside their own hex beneath the scale of the game.

17.2 Targeting & LOS

A missile unit can fire at any one enemy stack within range and within the firing unit's line of sight (LOS).

  • A missile unit may only fire at a target unit if the target unit is in range and in the firing unit's LOS.
  • LOS is determined by tracing a line of hexes from the firing unit to the target unit.
  • An LOS is blocked if any hex between the firing unit and the target unit contains the following types of terrain:
    • Urban Hexes
    • Objective Hexes
    • Fortress Hexes
    • Temple Hexes
    • Wall Hexsides

Important: A wall hexside does not block an LOS if both the firing unit and target unit are in adjacent hexes.

  • Urban, objective, fortress, and temple hexes block LOS only through the hex. Units can always fire into and out of these hexes.
  • Hexes with rubble markers, and walls with breach markers, do not block LOS, regardless of their original terrain.
  • Units occupying fortresses and the temple can fire over any type of terrain. Similarly, units can always fire at units occupying fortresses and the temple. This does not apply if there is a rubble marker in these hexes.
  • Slopes do not block LOS (they were not steep enough to do so).
  • The terrain in the firing unit's hex and the targeted hex do not affect LOS.

Example: A missile unit could fire from an urban hex through a clear hex to a fortress hex.

17.3 LOS & Height Advantage

The location of units may allow those units to have a height advantage when determining LOS.

  • Units in fortress hexes can fire through any type of terrain (they would be firing from the rooftops).
  • Siege towers can fire over any type of terrain when conducting ranged fire or siege attacks.
  • Missile engines and siege towers can fire over any type of terrain if the target is in a fortress or objective hex. This applies to both missile fire and siege attacks.

17.4 Rubble & Breaches

Hexes and/or hexsides with rubble or breach markers are treated as open terrain for LOS purposes.

17.5 Missile Fire Procedure

Follow the below fire combat sequence in the order given:

  1. Attack Declaration: The attacker declares which unit will attack which hex. The target hex must be within range of the firing unit and there must be a clear LOS between the firing unit and defending hex/unit.
  2. Combat Strength Determination: The player determines the combat strength of the firing unit and then consults the CRT, locating the column that matches the unit's combat strength.
  3. Combat Shift Determination: Determine and apply the column shifts for the attacker and defender (cumulative) (17.6).
  4. Combat Resolution: Roll 1d6 and cross index the result beneath the final strength column heading. Implement the combat result immediately.
  5. Roll 1d6 and apply the results normally. Execute any retreats required. Units using missile fire cannot pursue.

Important: A unit which engages in missile fire can engage in melee combat in the same turn.

17.6 Shifts

Apply only terrain and Roman camp column shifts (16.2) when conducting missile fire combat.

  • Units targeted by missile attacks use the best single terrain in the hex for any defensive shifts.
  • They receive the benefit for a wall hexside only if being fired at through a wall hexside.

17.7 Fire Combat Details

Units conducting missile fire combat:

  1. Are not affected by "A" or "Aa" results.
  2. Cannot advance after combat (even if mandatory pursuit (+P) result occurs).

18.0 Combat Results

Combat results are applied immediately.

  • Results are explained in the Combat Results list near the CRT on the map. The effects of unit disorder are explained in 22.0.
  • The player controlling the units affected by the result determines which unit is affected if there is a choice.
  • If a stack of units attacks an enemy occupied hex, and the first (or subsequent) combat resolution eliminates or retreats all enemy units in the defending hex, the remaining attacking units in that stack cannot be switched to attacking other enemy hexes. However, they can conduct pursuit into the hex formerly occupied by the defender (20.0).

19.0 Retreat

A retreat combat result "R" causes all defending units in the force to move involuntarily. The player controlling such units must move them the indicated number of hexes.

  • There are two types of retreat; Withdrawal and Rout.

  • Retreat is not regular movement; its execution does not use movement factors. Retreat is conducted in terms of hexes.

  • Units must always retreat the number of hexes indicated, regardless of their printed movement factors.

  • Roman units defending in camps may choose to ignore the retreat (Roman player's choice on a unit-by-unit basis). Exception: If the camp is eliminated in combat, then other units in the hex subsequently affected by a retreat result must retreat (after eliminating the camp).

  • Roman and Judean units defending in intact fortresses may choose to ignore the retreat.

  • A unit that retreats into an intact fortress, and Roman units that retreat into a camp, may cease the retreat in that hex (controlling player's choice).

  • Withdrawal: The following units always withdraw; leaders, units stacked with leaders, and elites (but not units stacked with elite units). A unit that withdraws must retreat one hex.

  • Automatic Elimination: Siege units are automatically eliminated if forced to retreat. Other units stacked with the siege unit retreat normally.

  • Rout: All units not listed as eligible for withdrawal or automatic elimination always rout when receiving a retreat result. When a unit routs, the owning player rolls 1d6 and then retreats the unit the number of hexes equal to the die roll.

19.1 Direction of Retreat

Units must be moved in the following directions:

  • Judeans:
    1. If the units begin their retreat outside Jerusalem's walls, they must retreat towards the closest Jerusalem hex (and keep retreating into the city).
    2. If the units begin their retreat inside Jerusalem's walls, they may retreat in any direction.
  • Romans: Roman units must retreat towards the nearest hex containing a Roman camp or Roman occupied fortress hex (Roman player's choice).

Important: The nearest hex is defined regardless of terrain type. If more than one hex is nearest, the owning player chooses the nearest hex.

19.2 Retreat Restrictions

Retreat is subject to the following strictures. Within these limits, units may be retreated in any direction.

  • Units may not retreat into hexes containing enemy units, or into otherwise prohibited terrain. If there is no other alternative, they are eliminated in the last hex into which they were able to retreat.
  • Leaders, cavalry, and elite units can retreat into and through EZOC. Other units are eliminated if forced to retreat into an EZOC.
  • Units may retreat into and through hexes containing friendly units. Units must obey all stacking rules in the final hex of their retreat path. If they end their retreat in violation of any stacking rules, the owning player must eliminate excess to restore the stacking limit.
  • If a unit retreats through a hex containing friendly units and (at that moment) the hex is over-stacked, all units in the hex are disordered (including the retreating unit).
  • A retreating unit may not be moved through the same hex more than once, nor re-enter the hex from which it began the retreat. It must end its retreat the indicated number of hexes away from its combat position. If it can retreat only a portion of the number of hexes called for in the combat result, it is eliminated in the last hex into which it was able to retreat.
  • Units cannot retreat across intact wall hexes unless there is a gate. Roman units can retreat across ramps and siege towers.
  • Roman units can retreat off the map. They are placed in the Greater Judea Display.
  • Judean units cannot retreat off the map. If the only eligible retreat path is off map, the unit is eliminated.
  • A unit may not be retreated into a hex that would cause it to be eliminated or over-stacked at the end of the retreat if another retreat path is available.

19.3 Retreat & Multiple Defense

Under certain circumstances a unit may end its retreat adjacent to an enemy unit. Such units may be attacked again if the enemy units have not previously conducted an attack in the same phase.

20.0 Pursuit

Pursuit is a special form of movement that can occur after combat.

  • The attacking player may pursue with a unit if it is part of a stack of attacking units which has cleared all defending units from a hex.
  • Units in other stacks that previously attacked the hex cannot pursue. Nor can units attack into an empty hex to gain a pursuit result.

20.1 Pursuit Procedure

If a combat result allows a player to conduct pursuit, the player may, but is not required to, immediately move any number of eligible units the following number of hexes:

  • Leader and Cavalry Units: 2

  • All Other Mobile Units: 1

  • Static units and units conducting missile fire cannot pursue.

  • All siege units cannot conduct pursuit.

  • Cavalry units cannot pursue across intact wall hexsides.

  • Infantry units pursuing from outside to inside of a wall hexside or into a fortress hex cannot pursue unless it is a mandatory pursuit, or the wall is breached and/or a fortress hex contains a rubble marker. Additionally, units attacking from a siege tower or ramp may pursue.

  • The first hex must be the hex the enemy units formerly occupied. The second hex, if allowed, may be in any direction.

  • Pursuit differs from normal movement in that it is in terms of hexes, not movement factors.

  • Pursuit may only be into hexes into which pursuing units could normally move.

  • If a pursuit is more than one hex, pursuing units may stop in the first hex, and others in the second or subsequent hexes.

  • Pursuing units are not affected by EZOCs, they may move through them freely.

20.2 Mandatory Pursuit

Combat results of "+P" require all mobile units in a stack involved in a melee attack to pursue if the attack results in all enemy units being cleared from the hex.

  • Mandatory pursuit follows the normal pursuit rules.
  • Cavalry units must pursue two hexes if possible (if not possible, cavalry ceases movement in the first hex).
  • If a leader is stacked with units that received a mandatory pursuit result, the owning player may choose to not conduct a pursuit.

21.0 Fall Back

During the Fall-Back Phase or when failing a morale check (8.0) players must execute fall back. The Roman player and then the Judean player conducts fall back.

21.1 Roman Fall-Back Procedure

The Roman player must pick up all Roman mobile units that are in hexes inside the Jerusalem walls and that do not occupy a fortress, or objective, or a hex that contains a wall hexside (intact or not) or a Roman camp.

  • Units subject to fall back must be placed in or adjacent to a Roman occupied fortress, objective, wall hexside, or a Roman camp, or the Greater Judea Display.
  • The Roman player may conduct fall back for all other Roman units or they may remain in place.

Important: Ramps and camps do not fall back.

21.2 Judean Fall Back Procedure

The Judean player must pick up all Judean mobile units outside of the Jerusalem exterior walls (3rd and/or 1st walls) and place them in any fortress, objective or hex adjacent to a wall hexside (inside the wall) that are not occupied by or adjacent to Roman units.

Exception: They may not fall back into Herod's Tomb.

  • The Judean player may (player's choice) conduct fall back with all other Judean units.

22.0 Unit Status & Rally

Most units have two sides: the front is the good order (full strength) side, and the back is the disordered (reduced strength) side.

  • Units are disordered due to combat or other game actions as noted. A disordered unit which is disordered again is eliminated.
  • A unit with only a good order but no disordered side is eliminated when disordered.
  • Disordered units do not project ZOC.
  • A disordered missile unit which has lost its range factor cannot apply (A) results.

22.1 Rally from Disorder

A disordered unit remains disordered until it rallies.

  • Rally is conducted during the Rally Phase of the GT Inter-Phase. At this point, flip all disordered units to their good order side.

Important: A morale event may cause units to rally.

23.0 Special Units

23.1 Leaders

Leaders are treated as combat units with special capabilities (as explained throughout the rules). Leaders:

  1. Do not count for stacking (11.0).
  2. Have a command radius that is used for movement and offensive fire activation (7.5).
  3. Provide combat shifts (16.2.1).
  4. Negate rout results (19.0).
  5. Can countermand mandatory pursuits (20.2).
  6. Automatically rally if an army passes a morale check.

23.2 Elites

These units automatically rally if an army passes a morale check. When required to retreat, they withdraw (they do not rout).

24.0 Roman Camps

The Roman player may deploy camp units on the hex map (not in the Greater Judea Display). Camps affect Roman defense (16.2.4), retreat (19.0), morale (8.2), and serve as a fallback location (21.1).

24.1 Camp Characteristics

Camps are static units. Once placed, they cannot move. They have ZOC (when in good order), a combat factor and are missile capable units.

  • Camps do not count for stacking. Only one camp may be in a hex.
  • A camp may be destroyed by melee or missile combat.
  • The Roman player may remove a camp unit from the map at the start of any Roman Build Phase. The camp is immediately available for building elsewhere on the map in the same phase (or later).
  • Camps may melee attack (but are not required to since EZOC do not extend into them).
  • Camps missile fire normally.
  • Units defending in a camp receive a one column shift to the left. This is in addition to any terrain effects.
  • Camps and Roman units defending in a camp may ignore retreats.

25.0 Special Tactics

The number of Special Tactics markers used is not limited by the counter mix.

25.1 Flank Attacks

A flank attack gives the attacker an additional right shift during melee combat.

  • A player may declare a flank attack when two or more stacks attack a single enemy occupied hex, and at least one stack is 180 degrees from the first stack or there are three or more stacks, each 120 degrees from each other.
  • All units making a flank attack receive a one column shift to the right.
  • The player must declare all such attacking stacks for a single combat. Once declared, such attacks cannot be called off, even if an attack by the first stack clears the defender's hex. Such stacks could pursue.

25.2 Cavalry Charge

Cavalry charges conduct a modified form of melee combat.

  • A player may declare a charge for activated, good order cavalry units (including horse archers) at the start of the Movement Phase.
  • Place a charge marker in each hex that contains cavalry units conducting a charge.
  • All cavalry units in a hex with a charge marker must charge.
  • A player moves cavalry units marked with a charge marker up to three hexes (no more). All three such hexes and the target hex must be open terrain, further, they cannot contain a rubble marker. Charging units cannot charge through friendly occupied hexes and the unit to be charged cannot be adjacent to the charging cavalry's starting hex. The charge must be a minimum of one hex, but otherwise can be in any direction.
  • The movement cannot be into or across a ravine hex, across a gate, or breached wall, or slope hexside.
  • All charging units that began the Movement Phase stacked together must move together.
  • Charging cavalry units receive one right shift on the CRT.
  • Leaders may also participate in a charge (they cannot charge by themselves). They also receive the charge bonus as well as applying their own leader bonus.

25.3 Roman Orbis

The Roman player may form legionary units into an Orbis at the beginning of the friendly Movement Phase.

  • The Roman player may declare an Orbis for any hex containing one or more legionary infantry units (and any leaders stacked in the hex).
  • All such units must be activated and in good order. There can be no other unit types in the hex.
  • Roman Allied or Auxiliary units cannot enter Orbis.
  • Units in an Orbis have their movement factors reduced by one.
  • All eligible units that began the Movement Phase in the same hex and that are marked with an Orbis marker must move together. They cannot move into different hexes and all units must stop movement if one unit stops movement.
  • Units in Orbis may enter a hex containing a siege engine, camp, or other legionary/leader units but must immediately cease movement.
  • Units in Orbis cannot enter hexes containing Roman cavalry, Roman Allied, or Auxiliary units.
  • If a siege engine or other non-Orbis eligible units enter a hex containing an Orbis, those units must cease movement in the Orbis hex.
  • Units in Orbis are not affected by flank attacks.
  • Enemy missile units firing at an Orbis receive a one column shift to the left.
  • Units in Orbis ignore any defensive fire (A) result.
  • Units in Orbis ignore all retreat results. They pursue normally.
  • Units remain in Orbis until:
    1. Any unit in the hex becomes disordered.
    2. The units are eliminated.
    3. The Roman player may voluntarily remove an Orbis marker from activated units at the beginning of the Movement Phase (prior to moving any units).

Important: Leaders may leave an Orbis without moving the marker.

25.4 Roman Multiple Lines

Normally, all units in a hex must attack a single enemy occupied hex. However, if a Roman hex contains only Roman legionary infantry units of the same Legion (plus any friendly Leader), then the player may have units attack in one direction, and others into the hex 180 degrees to their rear. These are resolved as two separate attacks.

26.0 Roman Outer Walls

Roman outer walls represent the lines which Titus built to cut off Jerusalem from outside support.

  • The Roman player may attempt to build outer walls during any friendly Build Phase.
  • The Roman player must expend the required BP and then roll 1d6 to determine when the wall will be completed.
    • 1 to 3: The wall is completed this GT.
    • 4 to 5: The wall is completed the next GT.
    • 6: The wall is completed in two GTs.
  • If the wall is completed in the current GT, the Roman player places the marker in the box in the Outer Wall Display.
  • If the wall is completed in one or two GTs, the Roman player places the marker on the Month of Battle Track in the appropriate GT box. On that GT move the player moves the marker to Outer Wall Display.
  • No matter the GT of completion, the Wall is built before the Judean BP die roll.
  • There is no deployment of markers on the map, the outer walls are assumed to be intact beyond the area of operations.
  • Once built the outer walls remain in effect for the remainder of the game.

26.1 Effects of the Outer Walls

The Judean player only rolls 1d6 to determine the number of BP received per GT instead of two (6.3). Additionally, the Judean player deducts one from the Judean Morale Break Point.

27.0 Stratagems

Players may build Stratagem markers, representing assorted skullduggery attempts.

  • Stratagem markers begin the game in the Stratagem Pool. Players may use the Stratagem Pool on the map or a cup/bowl as the pool.
  • To build them, pay the BP cost and randomly pick a stratagem marker. Place the marker face down in the appropriate Available Stratagem Display. The owning player may look at the marker after purchasing it.
  • Stratagem markers are played during the phase designated on the Stratagem Chart on the map (before taking any other action in that phase). Reveal the marker and implement its effects.
  • See the Stratagems Chart for effects.
  • Each player may play a maximum of one stratagem per phase.

27.1 Return

After employing a stratagem roll 1d6, if the result is within the range given in the return column on the chart, return the marker to the Stratagem Pool. Otherwise, permanently remove the marker from play.

27.2 Fog of Treachery

A player may examine stratagems after picking them. A player cannot examine stratagems belonging to his opponent until they are played.

28.0 Fog of War

A player may always examine friendly units. Enemy stacks may be examined when:

  • The Judean player can always examine all Roman units on the hex map regardless of location. The Judeans cannot examine Roman units in the Greater Judea display.
  • The Roman player may always examine Judean units outside the walls of Jerusalem. Judean units within the walls cannot be examined by the Roman player.
  • At the instant of combat (any type) players may always examine the attacking and defending force.
  • You cannot examine enemy units in reinforcement displays, command markers in the enemy pool, and stratagem markers.

29.0 Greater Judea

The Greater Judea Display represents the larger areas surrounding Jerusalem which serve as Roman lines of communications.

  • Roman units enter the Greater Judea area by moving adjacent to any map edge and pay one additional MF to enter the display. This ends the unit's movement for the turn.
  • Roman units may enter the Greater Judea Display via retreat (19.2) and fallback (21.1).
  • Roman units in the Greater Judea Display can enter the map by moving out of the display and onto any map edge, paying the movement cost for the hex and any hexsides crossed. If entering the map via a road hex, the Roman units may use road movement (13.3).
  • There can be an unlimited number of Roman units in the display.
  • A single activated Roman leader in the display can activate all units in the display. Leader radius does not extend outside the display.
  • The Roman player may use a single BP to activate all units in the display.
  • ZOC do not extend into or out of the display.
  • Units may not conduct combat into or out of the display.
  • Roman units may retreat into and (for a two-hex pursuit) pursue into Greater Judea.

30.0 Optional Rules

30.1 Additional Roman Forces

Antesignani (ANTSIG) were legionaries trained as elite light infantry. When using this rule, the Roman player may convert one legionary infantry unit per legion to an Antesignani.

  • To convert a legionary infantry unit to an Antesignani unit, the Roman player:
    1. Expends one BP.
    2. Selects one good order legionary infantry unit in a Roman camp or Greater Judea Display.
    3. Places the legionary unit to the side of the map and replaces it with the Antesignani unit with the same legion identification.
  • The Antesignani unit remains on the map until eliminated. If eliminated place the removed legionary unit in the Eliminated Display and set the Antesignani unit to the side of the map.
  • An Antesignani unit may replace a legionary unit any number of times.

30.2 Roman Marines

The Classis unit represents Roman marines who were often used as pioneer troops. Treat it as a heavy infantry unit with the following special cases:

  • It costs three BP to build the Classis unit.
  • Once on the map, the Roman player may deploy any Roman siege engine in the same hex as the Classis.

30.3 Repairing Breaches

Both players may repair breaches. A player must have a friendly unit (of any type) in a hex adjacent to a breached wall during a friendly Build Phase. The player then expends one BP and removes the breach marker. The wall is restored.

Important: Rubble markers cannot be removed.

30.4 Stacking & Attack Order

When conducting an attack, the phasing player must use the top unit in a stack to make the first attack, then the second, etc.

  • When defending, the top unit in the stack must take the first loss, then the second, etc.

30.5 Pursuit Combat

Units which conduct a pursuit (20.0) can, upon completion of the pursuit movement, may conduct a melee attack if adjacent to an enemy stack.

  • If the attack leads to another pursuit, the pursuing units can conduct additional pursuit combat.
  • In the event of a two-hex pursuit, only the units moving into the second hex can conduct pursuit combat.
  • In the event of a mandatory pursuit result (P) the attacking player must conduct pursuit combat if ending up next to an enemy stack.
  • Place a rubble marker in each hex that the pursuing units end their move (10.5.2).