Valley of Tears: The Yom Kippur War, 1973

Valley of Tears: The Yom Kippur War, 1973 Rulebook

Table of Contents

BCS Introduction
BCS 1.0 Basics
BCS 1.1 Units
BCS 1.2 Core Concepts
BCS 1.3 Formations
BCS 1.4 Command Radius (CR)
BCS 1.5 Support
BCS 1.6 Fire Events
BCS 1.7 Prepared Defense
BCS 1.8 Fatigue
BCS 1.9 Safe Paths
BCS 1.10 Fog of War
BCS 2.0 Game-Turn Sequence
BCS 2.1 Reinforcements
BCS 2.2 Replacements (Repls)
BCS 2.3 Assignment
BCS 2.4 [Optional] Orders
BCS 2.5 Activations
BCS 3.0 Formation Activation Sequence
BCS 3.1 Main Supply Routes (MSR)
BCS 3.2 SNAFU
BCS 3.3 Objectives
BCS 3.4 Activities
BCS STOPPED/FINISHED Chart
BCS 3.5 Clean Up
BCS 3.6 Isolation
BCS 3.7 Fatigue Recovery & Failure Flip
BCS 4.0 Movement
BCS 4.1 Terrain Effects
BCS 4.2 Stacking
BCS 4.3 Zones of Control (ZOCs)
BCS 4.4 Stopping Engagements
BCS 4.5 Engagement Zones
BCS 4.6 Screening
BCS 4.7 HQs & Combat Trains
BCS 4.8 Voluntary Retreats
BCS 4.9 [Optional] Realistic Movement
BCS 5.0 Combat
BCS 5.1 Regular and Shock Attacks
BCS 5.2 Engagements
BCS 5.3 Attack by Fire
BCS 5.4 Barrage
BCS 5.5 Retreats
BCS 5.6 Advance After Combat
BCS 6.0 Odd Situations
BCS 6.1 Urban Warfare
BCS 6.2 Formation Destruction
BCS 6.3 Attacks From Off-Map
BCS 6.4 [Optional] Planned Fatigue
BCS 6.5 [Optional] Stand Off AV vs. Red Support
BCS Glossary
BCS AV Types
BCS Unit Capabilities Chart
BCS Quick Reference Boxes
BCS Unit Key
VoT Introduction
VoT 1.0 Common Special Rules
VoT 1.1 Weather & Special Map Symbols
VoT 1.2 Series Rules Matters
VoT 1.3 Two Front War
VoT 1.4 Amphibious Units & Bridges
VoT 1.5 Air Warfare
VoT 1.6 The Air Phase
VoT 1.7 Tasking
VoT 1.8 Mission Specific Rules and Resolution
VoT 1.9 SAMs and Tanks
VoT 2.0 Israeli Special Rules
VoT 2.1 Specialized Units
VoT 2.2 Frontal Split of the Airforce
VoT 2.3 Extreme Tempo (XT)
VoT 2.4 Airlifts
VoT 3.0 Arab Special Rules
VoT 3.1 Special Units
VoT 3.2 Egyptian Plans & Defenses
VoT 3.3 Strategic Reserves
VoT 3.4 Commandos
VoT 4.0 Victory
- 4.1 Victory Conditions
- 4.2 Ending the Game
VoT 5.0 Optional Rules
VoT 5.1 Simplified Air Rules
- 5.2 Splitting the Israelis
- 5.3 Free Frontal Air Allocations
- New Series Rules
VoT 6.0 Scenarios
VoT 6.1 The Yom Kippur War: Two Front Campaign
VoT 6.2 On the Banks of the Suez: Sinai Front Campaign (Large)
VoT 6.3 Syrians at the Border: Golan Front Campaign (Medium)
VoT 6.4 Duel for the Golan (Small)
VoT 6.5 Iraqi Intervention (Medium)
VoT 6.6 Aryeh Dov (Small)
VoT 6.7 Operation Stouthearted Men (Medium)
VoT 6.8 Africa (Large)
VoT Errata (6 Aug 24)
VoT Glossary
VoT Israeli Order of Arrival
VoT Arab Order of Arrival
VoT Terrain Effects Chart

BCS Introduction

The Battalion Combat Series (BCS) is a simulation of grand tactical warfare from the advent of mechanized armies in the late portion of World War I to the present.

It was created to show that warfare at this level has its own distinct nature and behaviors. A level wedged between tactical and operational warfare. It is neither a large scale version of one, nor a small scale version of the other.

BCS attempts to find the best balance between simulation accuracy and playability and not compromise either unduly.

BCS 1.0 Basics

1.0a Scale. Most units are Battalions. A hex ranges from 1 km to slightly over 1 mile, depending on the needs of the game. One game turn represents one day of actual activities. Game Rules will state that game’s exact ground and unit scales. Note that there is no concept of “Morning” and “Afternoon” associated with “Initial” and “Second” Activations.

1.0b The Series Rules. Each BCS game contains both Series and Game rulebooks. The Series Rules contains rules applicable to all series games. The Rules booklet concentrates all the series rules in a format that follows the Sequence of Play as much as possible. It also includes the master Series Index. Two special characters are used:

The Diamond is a bullet point list, but not a list of specific requirements or restrictions as is the case with the Check.
✔ The Check indicates a list of requirements or restrictions.

1.0c The Game Rules. The Game Rules give the details needed for a specific game, including special rules, scenarios, and setup information. Where the Game Rules and the Series Rules disagree, the Game Rules including Scenario and Set Up instructions take precedence.

1.0d The Support Booklet. The Support booklet includes the main Designer’s Notes, the larger examples of play, and the more extensive commentary originally included in the main rulebook as well as the Charts and Tables that are only needed on less common occasions.

1.0e Map. Every fifth hex row is numbered, but hex numbers count all the hexes. So, B21.32 is the 21st hex column, two hexes above the.30 hex row on Map B. Only hexes with half a hex or more showing are playable. Units cannot conduct Off-Map movement. Retreating Off-Map is allowed (5.5h). The player can retain Reinforcements Off-Map until he chooses to have them enter.

1.0f Setup Notes. The Game rulebook contains setup information for the various scenarios presented. Except as amended in the Game rulebook, always apply the following:

“w/i X” always means at or within X hexes.
Units can set-up anywhere within a zone specified to include its boundary lines, provided no unit starts in a hex they could not enter during movement.
Units can set-up on either counter side, as restricted by terrain.
If a number is shown in brackets, such as [3], it is the unit’s current available Steps. If no value is given, the unit starts at full-strength.
If a unit is listed as ‘in Support’ you can place it near the HQ or Off-Map as desired and give the HQ the appropriate Support marker. Units only start in Support if listed as such in the set-up.

1.0g The First Turn. Modify the first phases of every scenario:

The scenario specifies the First Player for the first turn and might list other times where the First Player is designated. On all other turns, make the normal dice roll to determine the First Player.
The Weather may be pre-determined.
Roll for Weather and Air Points normally if not pre-determined by the scenario.
Do not roll for Replacement Points.
There is no Assignment Phase.
Orders (optional) can be freely assigned on the first turn, except that any Formation listed in the set up in Prepared Defense must remain that way at least until Turn Two.
A Formation listed as “Done” in the set-up may not Activate during the first turn. Set its Formation Activation marker aside for the next turn.
A Formation listed as “Used” in the set-up must attempt a Second Activation during the first turn.

BCS 1.1 Units

Units are any counter in play that is not any type of game marker (e.g. Arty or Air Point markers). HQs, Combat Trains, and Support units are considered units, even though they have special requirements and representations that are different from, say, a run-of-the-mill Infantry unit.

Important: The Unit Capabilities Chart provides a list of each unit type’s available functions.

1.1a Unit Values.

Assault Arrow: This symbol is used to identify units as Attack-Capable. Only Attack- Capable units can be the “Attack unit” in a regular Attack.
Movement Allowance: A unit’s Movement Allowance or MA is the maximum available number of Movement Points (MPs) available.
Movement Class (MA Class): The number’s color shows the unit’s MA Class on that counter side. A Red MA is Tactical, a Black MA is Truck, and a White MA is Leg.

Design Note: These are the same as their OCS predecessors, except ‘Tactical’ has replaced ‘Tracked’ as Armored Cars are included.

Armor Value & Range: Rated by vehicle and gun. Vehicles have only one number. Range is assumed to be one hex, if no value is printed.
Action Rating: A rating from 0 to 5 (best) representing a unit’s leadership, training, morale, and the unit’s other soft qualities.

1.1b Steps. “Steps” measure unit resilience; they are the number of losses a unit can absorb and remain effective. Units are rated for their size and organization.

The printed Step value on a unit is its full-strength. A unit can never obtain more steps than this number. Any unit without a Step Loss marker is assumed to be at full-strength.
Place a Step Loss marker under a unit that has suffered losses, set with the number facing the same way as the unit indicating its remaining steps.
Rotate and/or flip the marker as needed to show the current steps available when losses or rebuilds occur.
When a unit’s steps available becomes less than 1, send it to the Dead Pile.
There are no other step loss effects beyond the unit’s eventual removal.

1.1c Unit Counter Sides. Most unit counters have two printed sides. The distinguishing feature between them is the Movement Allowance. The side with the lower MA is called Deployed or Deployed-side. The side with the higher MA is called Move or Move-side.

If a unit has only one printed side, it is assumed to be showing its Move-side.

The side printed on the physical counter’s front will be the side most used.

Important: The side currently showing defines that unit’s capabilities using the Unit Capabilities Chart.

Design Note: Many will note the similarity between the ‘sides’ concept here and the ‘Modes’ as shown in the Operational Combat Series. What I’ve done here is a bit looser than the OCS Mode structure and I wanted what the side shows to be different depending on the unit type involved, some of which aren’t really a ‘mode’ in any event. So, dealing with the ‘side showing’ gets the job done without any fuss.

1.1d Unprepared Units. An Unprepared unit is one that is neither Attack-Capable nor has an AV showing at the moment.

An Unprepared unit:

Has no ZOC.
Cannot Attack or Assist.
Cannot use Prepared Defense effects.
Cannot use Support.
Cannot Jump HQs or Combat Trains.
Cannot enter an enemy Screen Zone or an enemy controlled Victory Hex.
Can spot for Barrages.
Counts as a defender’s second unit.

1.1e Unit Types.

Intrinsic Units. These are units with a “Formation Affiliation” on the right of their Unit Symbol and (in all the games except Last Blitzkrieg and Baptism by Fire) have a colored bar on their counters. They only belong to that Formation.

Independent Units. These units do not have a designation to the right of their symbol, nor any colored bar. They can be:

Assigned to any Formation (where they will act like its Intrinsic units).
Left Unassigned to any Formation.
Taken from one Formation and assigned to another as the player might wish.

Headquarters (HQs). Headquarters represent a Formation’s command and control hub.

Combat Trains. Combat Trains are a Formation’s forward logistical establishment.

Artillery. Artillery is not explicitly represented in the game, but has been abstracted into “Arty Points.” Arty Points can be Intrinsic (those printed on the HQ’s counter) or shown via separate Arty Point markers that can be assigned to the HQs as desired.

Infantry. Any unit that has no printed Armor Value (AV) number is “Infantry” for terrain DRM purposes on the Combat Table.

Dual Units. A unit that is Attack-Capable and has an Armor Value.

AV Units. An AV unit is one with an Armor Value.

Variations on AV or Dual units.

Support. These are AV units dispersed into small groups among the Formation’s non-AV units to bolster them. Support units are not “Real” units as they have no specific location on the game map.
Red AV Units. A unit with a Red AV showing. These units are more capable of offensive action than the other varieties of AV units. They can give a DRM on the Combat Table to the attack or defense of other units when in Support.
Limited AV Units. A unit with an “Outline” AV showing. These units are more defensive in nature than Red AV units. They suffer a penalty on the Engagement Table as a Firer. They can give a DRM on the Combat Table to the defense (but not the attack) of other units when in Support.
Stand Off AV Units. A unit with a Black AV showing. These units are more defensive (like Limited AV), but have uniquely long ranges and ability to be concealed. They can give a DRM on the Combat Table to the defense (but not the attack) of other units when in Support, but also have a Target DRM on the Engagement Table. They are more difficult to hit on the Barrage Table. Unlike other Support units, Stand Off units in Support require Stopping Engagements when enemy AV units enter their Host’s ZOCs.
Light AV Units. A unit with a White AV showing. These units are more defensive in nature than Red AV units and equipped with low caliber weapons (e.g. MGs) on vehicle mounts. They cannot initiate Engagements as the Firer. When in Support, Light AV units function exactly like Limited AV.
Hard Units. These have a Yellow background to their unit symbol based on the vehicles involved. Open-top armor or WW2 mech infantry would not be shown as Hard units.
Breakthrough AV Units. These have a ‘Breakthrough Armor designation’ on their unit symbol. They use heavily armored vehicles to penetrate strong defensive positions. These units are always qualified to conduct Shock Attacks.

1.1f Recon. Any unit with a Cavalry-slash in its symbol or listed as “Recon” in the Game Specific Rules can make use of the special abilities given Recon units in 3.3f, 3.3g, and 4.6.

1.1g Non-Rebuildable Units. Any unit with a Yellow Dot printed behind its Action Rating cannot accept Replacement Points. If destroyed, a non-rebuildable unit cannot return to play.

1.1h Static Units. These units defend their location, but that is all. Normal rules apply to Static units based on their counter values. If Independent they cannot be Assigned, so they cannot make use of Support or Spot a Barrage.

BCS 1.2 Core Concepts

1.2a Play of the Game. In the most general form, BCS game-turns play as follows. (This description assumes “given other rules” of which it does not supersede.)

a) Reinforcements. One player (it does not matter which) rolls for the Weather, and each player rolls to determine the available Air and Replacement (Repl) Points they will get. Both players simultaneously collect any Reinforcements called for by the Order of Arrival. These are placed for arrival in this turn depending on where they are to enter and the type of unit they are.

Repls are used to rebuild losses. This might be on the map (a unit having lost some of its steps), upcoming Reinforcements on the OOA, or in the Dead Pile (a unit which has lost all of its steps). Each Repl can rebuild one step—a unit in the Dead Pile that has rebuilt a step “comes back to life” and returns to the map where it could continue to repair its lost steps.

The Air Points the player obtains are kept in a pool to use for the entire turn (each one able to be used once). Any leftover Air Points will be wasted. He can use them in any Activation of the turn as desired.

b) Assignments. Independent units and Arty Points can be Assigned or Unassigned during the Assignment Phase. He can also re-assign Arty Points already assigned, by un-assigning them this turn and assigning them elsewhere next turn, as desired.

Critically, the Assignment Phase is when the player can decide to commit units to the Formation’s Support or to release units currently in Support to be “real” again.

c) Orders. If being used, Orders are issued to the Formations regarding the Turn’s planned movements of their HQs, to establish Prepared Defense, and recover Fatigue.

d) First Player Determination. Determine the First Player this turn if listed in the scenario (for Turn 1 only), or by a dice roll between the sides (on all other turns). This will determine which player will get to go first. That player will select one Formation to conduct an ‘Activation.’ Each Formation usually gets to run one Activation per turn. This is when it will get to do all the things the player wants the Formation to do. This might allow that Formation to run a “Second Activation” and do even more. Note that a Formation that runs both its Initial and Second ‘Activations’ does so under the rubric of the one Activation that Formation gets to do. The players alternate Activations until all the Formations in play have Activated (or attempted to do so and failed).

e) Activations. Each time the player’s turn in the alternation occurs, he can select any of his available Formations to try to Activate. There may be a time at the end of the Game-turn where one side’s Formations are “Done” and the other must keep going alone to use up its remaining Formations. Each turn, all Formations available to Activate must do so.

During an Activation, use the tools in your tool box to damage the enemy and try to achieve whatever objectives you need to win with your side. Some units can do certain things that others cannot (see the Unit Capabilities Chart to determine which). At the same time, while a given unit could do regular Attacks, Shock Attacks, Assists, Engagements, Attack by Fires, or spot for Barrages… only some of these might be the most effective and best use for the unit at that moment (see the Play Note regarding Combat-Type Integration on page 26 for more details). Knowing the right tool to use in various situations comes with experience.

f) Game-turn Ends. When all Activations have been completed, flip or orient all HQs to their Unused sides. Advance the Turn marker and begin a new turn.

The “Alternating Activations” are the heart of the system of play.

The Activation routine is straightforward: Determine SNAFU (how “good” of an Activation this one will be), place OBJ markers (where the Formation intends to fight), move and fight with the Formation’s units, check to see if Fatigue increases, and finally roll to see if the Formation gets a Second Activation.

If it does, repeat the above (starting with SNAFU), the Formation’s units move and fight again, and it will check to see if Fatigue increases again. The Formation will be “Done” at this point and play passes to the enemy for their next Activation.

If you fail to obtain your Second Activation, none of the activities in the above paragraph occur, but instead you mark your HQ as “Done” and play merely passes to the enemy.

1.2b The Core Rules. The following basic BCS rules must be known and understood to be able to make play function at any time in the game-turn. They defy easy placement in any single major rules section as their understanding is needed at many times during the turn sequence.

These are given greater explanation (and full internal rules) in sections 1.3 through 1.9. Those can be read for the details when you are ready. Below is a description of what each rule does to establish a fundamental understanding.

1.2c Command Radius (CR). Command Radius is a limit on how far away from the Formation’s HQ its units can move and where some functions can be accomplished. (1.4)

1.2d Support. Support is the distribution of small numbers of AV weapons among the Formation’s plain infantry to bolster their attack or defense. Support allows for DRMs on several tables and may inhibit some actions of AV units. (1.5)

1.2e Fire Events. Fire Events restrict the use of certain actions by a unit in an Activity Phase. (1.6)

1.2f Prepared Defense (Prep Def or PD). Prepared Defense shows a Formation’s improved defensive works and pre-planned Fire Support posture. Prepared Defense applies some DRMs, affects retreats, decreases Barrage losses, and may reduce a Formation’s overall SNAFU result. (1.7)

1.2g Fatigue. Fatigue is a measure of the relative Formation exhaustion/disrepair and the effect of combat operations upon them. (1.8)

1.2h Safe Paths. Safe Paths allow freedom of movement (below the game’s scale) between a unit and its HQ. A unit without a Safe Path might not be able to do certain game functions and might be cut off from its HQ. (1.9)

1.2i STOPPED and FINISHED. Units that STOP are generally unable to move further. Units that FINISH have completed their part of their Formation’s Activation and can still do only a couple of actions (and are STOPPED as well). These are levels of completion for a unit during an Activation. Each means certain actions are no longer possible, while the unit can still do specific others. See the STOPPED/FINISHED Chart for a complete summary of their effects as well as 3.4e and after.

BCS 1.3 Formations

“Formations” are military commands containing specific (aka intrinsic) units, and its own HQ and Combat Trains.

Formations are the functional block of units in the game. The main Sequence of Play revolves around the activities of one Formation at a time, alternating between the two sides.

A Formation’s units share (given other requirements) its common Support units, Fatigue Level, Main Supply Route, SNAFU result effects, total Artillery Points, Prepared Defense status, Orders, OBJ markers, and HQ Command Radius.

1.3a Formation Sizes. Formations vary in size from game to game. Formations might be Divisions in one game or Brigades in another. Specific Task Forces or Kampfgruppen (KGs) of various sizes can exist in either of these formats.

1.3b Intrinsic vs. Assigned units. Intrinsic units are those with a printed affiliation to the right of their unit symbol.

Formations can never assign Intrinsic units to another Formation. Independent units and Arty Point markers can be reassigned between Formations as the player sees fit according to the Assignment Rules.

Other than the possibility of later reassignment, an Assigned Independent unit or Arty Point is treated exactly like any Intrinsic part of its current Formation.

1.3c Blobs. A Formation has a defined area of operations termed a “Blob” which could be violated by other friendly Formations, causing reduced efficiency to it when two or more Formations become “Mixed.” (3.2d)

A Formation’s Blob is a smooth map shape as outlined by its outermost units. Ignore Combat Trains, Out of Command units, Unassigned units, Reinforcements, and Buddies when determining a Blob.

BCS 1.4 Command Radius (CR)

“Command Radius” is an abstraction that keeps a Formation’s units from wandering too far from their Formation HQ, to allow the Formation to be effectively under the HQ’s command and control.

1.4a Each HQ’s Command Radius is printed on its counter. Command Radius is the maximum distance from the Formation’s HQ its units can function normally. Beyond this distance, penalties and restrictions apply.

Important: The placement of OBJ markers is unaffected by Command Radius.

1.4b Command Radius is measured in hexes (not MPs) from the HQ to the unit’s hex. Literally, just count hexes, while ignoring terrain, EZOCs, Engagement Zones and even enemy units.

Use the Formation HQ’s current position to determine the extent of its Command Radius. A Formation’s unit is “Out of Command” if the unit’s distance to the HQ exceeds Command Radius.

1.4c Unassigned Independent units are unaffected by Command Radius. Once assigned, Independent units obey their assigned Formation’s Command Radius.

1.4d Out of Command Effects. Out of Command units function normally except where explicitly mentioned below:

Out of Command units are subject to Isolation losses.
Out of Command units CAN make Regular or Shock Attacks. Barrages can be made Out of Command, but require proper OBJ Zones and Spotter units.
Units that begin the phase Out of Command cannot Spot for Barrages, Jump enemy HQs or Combat Trains. It also cannot end Movement or Retreat in a hex to block an enemy MSR, when that enemy Formation has no available alternative MSR.

For the last point, a unit that is already blocking an enemy MSR when found to be Out of Command may continue to do so (both physically and/or with its EZOC).

1.4e Staying in Command Radius. Units (except Combat Trains) must end Activations within Command Radius. If this is not possible, the unit must either move or Attack in a way that will help it do so without foot-dragging OR it can stay in its original hex and not move.

Command Radius does not restrict Advance after Combat.

BCS 1.5 Support

“Support” is the distribution of packets of armor and anti-armor weapons to the (mostly infantry) units of a Formation. Depending on the type of Support unit allocated, these weapons help the other units in the Formation attack or defend more effectively. Defeating enemy Support will also allow your Support to be more effective in helping your units.

Any unit with a printed AV rating can be assigned to Support. Game specific rules and unit assignment rules may also restrict this.

1.5a A Formation’s Support is available to all its non-Dual Attack-Capable units (including assigned Independents); such units are called “Hosts.” A Support unit’s ability is unaffected by the number of possible Hosts nor the Support’s available Steps.

1.5b “Support Only” Units. If a unit has “Support” printed on its counter, it must be in Support when that side is showing. If a unit

has only one printed counter side and it is labeled “Support,” the unit must always be in Support.

1.5c Entering or Exiting Support. Units can only enter (or exit) Support in the Assignment Phase. See the Assignment Procedure Chart and 2.3.

No unit can both enter and exit Support in the same turn.

Entering Support. Units that are assigned to a new Formation can instantly enter Support at the same time. A unit must be capable of being in Support to enter Support.

Exiting Support. Support-Only units cannot exit Support to become a Real unit. They must be re-assigned Off-Map.

1.5d Multiple Support Units. Multiple units in Support can help defend against Engagements via a DRM. Follow 5.2b regarding which Support you must use if more than one is available.

1.5e Place each available Support unit near the HQ on its Support side (if any) or apply a Support marker of the right type to it. The Support’s counter should show its greater printed AV or Range rating or its counter-side displaying the word “Support,” if any.

Mark each stack with the type of Support available: Red, Limited, or Stand Off.

Example: Support Display on the Map

Support should be splayed out from the HQ’s hex in any convenient manner to facilitate play.

Stack A has two separate units in Support, but only displays the Red Support marker since the Red Support marker can do anything the Limited Support can do (and then some).

Stack B is an option available for display using fewer counters for units that have a Support side to their counter. It is only shown here as an option, since effectively it should be in the Stack A as well (no need to expend extra map space on that unit).

Stack C, associated with the 99 ID, has no Red Support, only Limited, so it is marked with a Limited Support marker so the player knows the Support there is not capable of giving a Support DRM for attack purposes.

In Support, Light AV and Limited AV are identical; mark both as “Limited.”

1.5f Support Unit Handling. A unit in Support never:

Counts for stacking.
Moves under its own power.
Affects any of their Formation’s “real” unit movements.
Takes losses from Barrage, Attack by Fire, Regular Attacks or Shock Attacks.
Counts as the “second unit” in any defense.

1.5g Effects of Having Support. Hosts obtain:

A Support AV ZOC.
Possible Combat and Engagement Table DRMs.
An AV to use for enemy Engagements (and any loss from the Engagement Table applies to the Support, not its Host).
Protection from Shock Attacks and Attacks by Fire.

1.5h Units which cannot Access Support. The following cannot access Support:

Dual units.
Units that are not Attack-Capable (to include all Unprepared units).
A unit which is in a hex not allowing Tac MA movement.
Units currently “Dropped Support.”
Units from a Formation with no Support assigned.
Those falling under any Game Specific Restrictions.

1.5i Dropped Support. “Dropping” is the act of a Host unit losing whatever Support it might have had available. This could be from a lack of available assigned Support, terrain, or enemy action.

Depending on the reason for the Drop, the Host will not be able to make use of any Support until either the situation changes or the current Activation (friendly or enemy) ends.

i) Placement. Place a Dropped Support marker when:

A Host unit moves or retreats into/across terrain that is Prohibited for Tac MA.
A Formation lacking Support has Support assigned, but the Support “cannot get to the unit” if there is no Support Establishment Safe Path (1.9c).

Note that units retain any Support they might have had when a Support Establishment Safe Path is blocked. The disruption of that Safe Path only matters when the Support is Dropped for some other reason and the lack of a Support Establishment Safe Path precludes the Host’s recovery of Support afterwards.

Place a Temporary Dropped Support marker, a KT-X marker, or rely on memory, if Support is Dropped because of an Engagement Table result against the Host’s hex.

Instantly replace any Temporary Dropped Support marker with a Dropped Support marker if the Host no longer has a Support Establishment Safe Path.

ii) Removal. Remove a Dropped Support marker any time both of the following are true (even during enemy Activations):

✔ The Formation has units assigned to Support.
✔ The unit has a “Support Establishment” Safe Path.

Dropped Support lasts indefinitely until these conditions are rectified.

Remove a Temporary Dropped Support marker (or its status marking substitutes) automatically when the current Activation (friendly or enemy) ends.

BCS 1.6 Fire Events

“Fire Events” limit certain actions a unit might attempt. Only the actions listed below cost Fire Events.

1.6a A unit can only initiate up to two Fire Events per Activation. A unit STOPs upon expending its last available Fire Event. Units from a Formation with either a Full or a Partial SNAFU result still have both Fire Events. A Formation with a Fail SNAFU result has none at all.

All unit types have Fire Events, but the requirements of the activities in 1.6b might preclude a given unit from using them.

Design Note: It is simply for the purpose of standardization that “all” units have Fire Events as many cannot actually do anything with them. Rather than make a list of units that have Fire Events and those that do not, I gave Fire Events to all units. What those units can do determines if there is any point to their Fire Events or not.

While a Tac MA Attack-Capable unit (Mechanized Infantry) can make a Shock Attack, consider that a plain Leg Infantry Battalion has two Fire Events, but what can it use them for?

The Leg Infantry cannot:

Conduct an Engagement (as it is not an AV unit).
Conduct an Attack by Fire (for the same reason).
Conduct a Shock Attack (it does not have a Tac MA).
Conduct a Recon (as it is not a Recon unit).

Therefore while it has Fire Events, it cannot use them to do anything.

1.6b Each of these expends one Fire Event when performed:

Engagement.
Attack by Fire.
Shock Attack.
Conduct a Recon.

1.6c An over-stacked unit cannot use Fire Events.

1.6d A Fire Event is expended when announced, regardless of the result obtained.

1.6e Units in a regular Attack (the Attack unit or Assist) do not require or expend Fire Events, but doing so FINISHES the involved unit(s) and wastes any Fire Events they have remaining.

1.6f When a unit activates, it must either “use or lose” both of its Fire Events before another unit can activate.

BCS 1.7 Prepared Defense

(Prep Def or PD)

A “Prepared Defense” is a Formation status which trades some freedom of action for a better, yet positional, defense. Obviously, the player must consider the cost and benefits of Prepared Defense in relation to the mission a Formation must fulfill on the map.

1.7a Entry. A Formation can enter Prepared Defense if it meets all these conditions:

✔ It has at least one Artillery Point (Intrinsic or assigned, before SNAFU is applied).
✔ It has no MSR Blocked Level marker.
✔ It is an Initial, not Second, Activation.

If a Formation is in or enters Prepared Defense, mark the Formation with a Prepared Defense marker near its HQ.

Design Note: To a large extent, Prepared Defenses represent the preparation of artillery FPFs (Final Protective Fires) and Artillery/ Mortar firing points and not—as one might think—just digging holes in the ground.

1.7b Exiting. Remove a Formation’s Prepared Defense marker instantly if:

The player decides to do so anytime before or after his SNAFU roll (as long as the Orders option is not being used).
The HQ moves or is Jumped.
It obtains an MSR Blocked marker.
It no longer has an Arty Point after Assignment.

If the player chooses to remove Prepared Defense after the SNAFU roll, the SNAFU result remains (at best) a Partial. It does not “upgrade” to the Full it might have had without the Prepared Defense.

1.7c Prepared Defense Effects. A Formation with Prepared Defense:

Is restricted to “no better than a Partial SNAFU result,” regardless of how well it rolls.
Can create or maintain Prepared Defense regardless of SNAFU result (including Fail).
Can Move normally, given the SNAFU requirement.
Can place units into Screen.
Makes use of Combat and Engagement DRMs.
Has units that can only be Engagement Targets if the Firer is adjacent to their hex.
Might apply a different line on the Barrage Table.
Can recover Fatigue.
Can conduct a Second Activation, but Prepared Defense cannot be created in a Second Activation.

1.7d Eligibility. A unit can use its Formation’s Prepared Defense, provided:

✔ Its counter is on its Deployed-side (and not its Move-side).
✔ It is in Command Radius.
✔ The Formation has its Prepared Defense marker at that moment.

BCS 1.8 Fatigue

A Formation’s Fatigue measures how rested or exhausted the Formation has become. Obviously, a seriously Fatigued Formation will not perform as well as one that is well rested.

Managing your Formations’ Fatigue level is needed to ensure they are not caught flat-footed when you need them. Do this by controlling both how you use those Formations and when they recover.

Many of these rules are altered when using the optional Planned Fatigue rules, 6.4.

1.8a Fatigue Levels. A Formation tracks its “Fatigue Level” with a Fatigue marker. Fatigue level progresses from Fresh through Fatigue Levels 0, 1, 2, 3 and 4. Fat-0 is normal (Fresh is ‘better’ than normal) while Fat-4 is exhausted. Fatigue never increases beyond Fat-4. Fatigue levels affect SNAFU rolls as a negative DRM equal to its level (Fat-2 is a -2 DRM). Fresh Fatigue gives a +1 (good) DRM, instead.

Keep the appropriate Fatigue level marker with the HQ to track its Formation’s Fatigue.

1.8b Fatigue Increase. Roll for Fatigue Increase every Activation in which any of the reasons listed on the Fatigue Increase Table occurs.

Do not roll, however, if none of the listed reasons occur OR the Activation’s SNAFU result was Fail.

The maximum increase to a Fatigue Level is two levels per turn (one each from both the Initial and Second Activations). If a Formation has only one Activation in a turn (for any reason), the maximum increase is one level.

Fatigue Level increases based on a die roll on the Fatigue Increase Table. Roll for the worst applicable situation (i.e., the one most likely to give a Fatigue increase) that occurred during the current Activity Phase (no matter how many times it did):

Placing any Combat OBJ marker.
Conducting any Engagements or Attacks by Fire, or by executing a Second Activation with a Full or Partial SNAFU.
Conducting the Attack Sequence.

Design Note: Many players get confused as to what a “Second Activation” really means or why “doing nothing but marching” would garner a Fatigue increase, but did not in the previous rules versions. In a nutshell, the mistaken impression seems to be that a “2 nd Act” is somehow a division of the game’s time scale. This would describe the Turn scale as “two turns per day” and the Second Activation is merely the normal “afternoon” turn. That is not correct. There is no set aside time for a Second Activation. In many activities (such as combat), the Formation’s efficiency generated a higher tempo which allowed it to do more during the day or move on to take advantage of the situation the earlier actions generated before the enemy “even knew they were there.”

But in the case of Marching all day for “free,” it isn’t that the Formation walked so much faster than normal (a higher tempo), but rather that it pushed on into the night to gain more ground. By definition these actions will generate more Fatigue (along with twice the normal march distance). Running a bunch of “clean up” activities (such as flipping units and Combat Trains) also means someone is doing all the normal things they must do overnight as well as all the next day’s activities. Expecting them to do all this without a Fatigue Increase is simply incorrect.

1.8c Other Fatigue Effects.

Fat-4 Formations cannot perform Second Activations.
Fresh Formations obtain a +1 SNAFU DRM and a +1 to their Second Activation roll.
HQs that conduct a Voluntary Retreat increase their Fatigue Level by one.

BCS 1.9 Safe Paths

A “Safe Path” means a given unit of a Formation has a “safe” way to maintain connection with its own HQ. Within a Formation, having an adequate connection with the HQ is of paramount importance for every unit. Losing this connection (aka “no Safe Path”) means that the unit may no longer be under command and control, might not get needed Support, might not be able to evacuate casualties, and might not get ammunition and fuel re-supplies. At this level, having no Safe Path is actually worse than having the Formation’s Main Supply Route (MSR) cut by the enemy.

1.9a Safe Paths are traced from each unit separately to its HQ (inclusive of both ending hexes). By definition, a unit in or adjacent to its HQ automatically has a Safe Path.

1.9b Safe Path Length. A Safe Path cannot be longer than the Formation’s Command Radius + 5 hexes. Trace a path of contiguous hexes noting that Terrain and EZOCs matter as per the below.

1.9c Movement Type Required. A Safe Path must be traversable by the unit’s Movement Class or the Movement Class required according to the following purposes:

To flip a Leg MA unit to its Tac/Truck MA side: Tac/Truck MA, as appropriate.
Support Establishment: Tac MA.
To use AV Repls: Tac MA.
To use Non-AV Repls: Leg MA.

1.9d When Needed. A Safe Path is needed to:

Flip from the unit’s Leg MA to its Truck/Tac MA side.
Remove a Dropped Support marker.
Accept Replacement Points.
Avoid Isolation Losses.
Successfully Retreat a Leg or Truck MA unit.

Safe Path does not affect Voluntary Retreats and Tac MA unit Retreats.

1.9e EZOCs. EZOCs block Safe Path according to the needed Movement Class:

All EZOCs block Safe Paths calling for a Leg or Truck MA.
Only Real AV EZOCs (not Support AV EZOCs) block Safe Paths calling for a Tac MA.

However, friendly units negate EZOCs for Safe Path purposes.

1.9f No Effect on Safe Paths.

STOP Terrain has no effect on Safe Paths.
Support has no effect on Safe Paths.
Enemy Engagement Zones, enemy Screen units, and Screen Zones have no effect on Safe Paths.

1.9g A unit that is an unassigned Independent or on the Map Edge always has a Safe Path.

Example: Safe Path

The 62 VG is severely compromised.

Unit A is obviously unable to trace a Safe Path to the HQ.

Unit C has a Safe Path to the HQ because of the negation provided by Unit B. Both Leg MA units could use a Safe Path through the Swamp at 11.09. Unit B also has a Safe Path.

If either C or B had an MA which is Prohibited in a Swamp, then those units would be unable to trace a Safe Path.

The HQ, at D, would provide a Safe Path to any unit stacked with it.

BCS 1.10 Fog of War

You are free to look at an enemy stack’s top Combat Unit and its values (to include its markers, such as Step Losses), but this freedom does not extend to units deeper in its stack. Each Formation openly displays its available Support units, Arty Points, and its Prepared Defense marker. Place these near the owning HQ so as to avoid confusion. Remaining Air Points are kept secret. Make all die rolls openly, after announcing their purpose and applicable DRMs.

BCS 2.0 Game-Turn Sequence

The following phases in order constitute the structure of a Game-turn.

a) Reinforcement.

One player rolls for the turn’s Weather. Then, both players:
Roll for new Air Points.
Roll for and apply new Replacement Points.
Place Reinforcements as listed on the Order of Arrival Charts (OOAs) into the listed entry locations.

b) Assignments. Both players can:

Assign or un-assign Arty Points.
Assign or un-assign Independent Units.
Units enter or exit Support.

c) Orders. [OPTIONAL] Both players record on a piece of paper each Formation’s Order status.

d) First Player Determination. Determine who conducts the new turn’s first Activation with a two-die roll for each side. The greater roll wins and must go first. Re-roll any ties.

e) Activations. Alternate Activating Formations until all Formations are Done.

f) Game-turn End. Flip or orient all HQs to their Unused sides. Advance the Turn marker and begin the new turn at the Turn Sequence’s beginning.

BCS 2.1 Reinforcements

2.1a The Order of Arrival lists any Reinforcements entering play each turn.

2.1b Entry Area Arrivals. Place arriving HQs and Combat Trains (with the player’s choice of arriving units) in actual Entry Area hex(es) during the Reinforcement Phase. See also 2.1h regarding the freedom accorded to Combat Trains.

All remaining arriving units (not selected above) can remain Off-Map and enter via movement in the Formation’s Activation.

2.1c Arrivals at Specific Hexes or at their HQ. Place these at the start of their Formation’s Activation OR in the Reinforcement Phase, as the player desires.

If a specified hex is enemy occupied and no option exists, the unit never arrives.

Units arriving at their HQ can enter in or adjacent to the HQ, terrain-effects permitting.

Place reinforcing Support units with their HQ and these can enter Support (or not) in the ensuing Assignment Phase.

Reinforcements can only arrive at an HQ if it has a Complete MSR. If this is not the case, delay the Reinforcements until the first Reinforcement Phase in which the Formation has a Complete MSR.

2.1d Entry Areas. Most reinforcements enter play by moving from designated Entry Area hexes during their Formation’s Activation to link up with their Formations. An Entry Area can consist of one or more hexes. If more than one Entry Hex can be used, Combat Units can choose the exact hexes during the Formation’s first Activation. The HQ and Combat Trains

must choose the exact hex during the Reinforcement Phase. That decision cannot be changed once made.

i) Place arriving HQs and Combat Trains in their On-Map Entry Area hex in the Reinforcement Phase. HQs and Combat Trains cannot wait Off-Map like regular units.

ii) The player can choose to keep an Entry Area Hex from being over-stacked by placing excess units Off-Map next to it.

Design Note: This mechanic exists to keep the hex from ending up Over-Stacked and vulnerable on entry if the Formation botches a Reactivation or SNAFU roll.

iii) These units can sit Off-Map near their Entry Areas before entering as long as you wish, even into later turns, but can only enter the map during their own Formation’s Activation.

iv) Off-Map units cannot be Barraged, Engaged, or Attacked. Those in the On-Map Entry hex can be hit normally.

v) On entering, count the unit’s MPs as if it started its move in the Entry Area hex.

2.1e Effects of Enemy Units. EZOCs have no effect on Entry Area hex use.

If an enemy unit occupies the Entry Area hex, entering units could do any of the following:

Enter via any other hexes of the same Entry Area.
Use “Attack from Off-Map” to enter. (6.3)
Nothing, they simply wait Off-Map.

2.1f Retreat Returns. Units removed by Retreat results automatically return in the next Reinforcement Phase. They return at or adjacent to their HQ, but do not require a Complete MSR to do so. See 5.5e.

2.1g Counter-side Showing. A unit can arrive showing either counter-side. Combat Trains always arrive on their Regular, not Ghost, sides. Eligible arriving units can be in Support as desired.

2.1h Combat Trains Arrival. Combat Trains, regardless of their Formation’s listed Entry location, can arrive in any Legal Hex that allows a Complete MSR.

BCS 2.2 Replacements (Repls)

Replacements are used to rebuild step losses.

2.2a Repls. Repls come in two flavors: AV and non-AV. Units with an AV (on either counter side) must use AV Repls. One with no AV on either counter side must use non-AV Repls. Otherwise given the rules below, you use your available Repls as desired.

2.2b The First Turn. Repls are not available on the first turn of any scenario.

2.2c Repl Use. i) Each Repl rebuilds one step on one unit. Repls must be used when they become available and cannot be saved for later. Unused Repls are wasted.

ii) No unit can accept more than one Repl per Reinforcement Phase.

iii) Units can never accept more steps than their full-strength step number. Reinforcing units arriving with less than their full-strength steps can be given Repls before they arrive.

2.2d On-Map Rebuild. Units that have lost steps, but are not in the Dead Pile, can rebuild their lost steps.

To use a Repl, an On-Map unit must:

✔ Have a Complete MSR.
✔ Not be Non-Rebuildable.
✔ Have a Safe Path traversable by either…
Leg MA for non-AV Repls.
Tac MA for AV Repls.

2.2e Rebuild from Dead Pile. If a dead unit receives a Repl and its Formation has a Complete MSR, place it in, or adjacent to, its HQ’s hex. EZOCs do not affect placement.

If a Dead unit’s Formation does not have a Complete MSR, it can rebuild its step loss but cannot transfer to the map until the Formation has a Complete MSR.

BCS 2.3 Assignment

2.3a In the Assignment Phase, you can do the following with Independent units and Arty Points:

Assign them to any desired Formation (given the Assignment Procedure Chart) and they will function as part of it.
Unassign them so they can be assigned elsewhere.
Units just assigned, those already assigned, and Intrinsic units can enter or exit Support.

Independent units and Arty Points must already be unassigned when the Assignment Phase begins in order to be assigned. You cannot “unassign and re-assign” in a single game-turn.

Reinforcing or rebuilt Independent units, and Arty Points can be freely assigned the turn they arrive.

Intrinsic units and Intrinsic Arty Points cannot be assigned to another Formation.

2.3b Use the Assignment Procedure Chart to determine the requirements and procedures for the change you wish to perform. This includes Assignment and Unassignment as well as Exiting and Entering Support.

2.3c Air Points are never assigned to a Formation. They are available to any friendly Formation.

2.3d On-Map unassigned Independent units never activate at all, nor suffer any Isolation effects. If on-map, they merely sit in place until assigned. Independent units may be pulled Off-Map in the Assignment Phase to await assignment as the player wishes.

2.3e Independent Static units cannot be Assigned to any Formation. (1.1h)

BCS 2.4 [Optional] Orders

2.4a Each Formation must be given one Order: HQ Move, No Orders, Prepared Defense, or Fatigue Recovery. Exception: a Formation can be given Prepared Defense and Fatigue Recovery at one time.

Be sure to give arriving Formations orders the turn they will enter play. If the player truly screws up his orders, he will get another chance next turn.

2.4b HQ Move Order. This is an order giving the movement path the HQ must follow. It should list any waypoints needed to clarify the route and the end point location. No other details are needed. No information as to what the units of the Formation are to do is needed; just lay out the movement route of the HQ.

i) If changing circumstances render your Move Order invalid, the HQ can “slow step” (or just not move), but you cannot decide to head in ‘some other direction’ on the fly (see also 2.4f).

Example: If your HQ’s route runs right through an enemy position you planned to clear, but failed to do so, the HQ can stop anywhere along its route (before the planned ending hex presumably) as needed.

ii) When a Formation Activates, place a March OBJ in its end point hex. The HQ then follows the assigned path at any speed it can manage and the player wishes. It cannot deviate from the assigned pathway. If the player underestimates how far the HQ might go, it will stop in the March OBJ’s hex until given new HQ Move Orders, regardless of remaining MA.

iii) The Formation’s units operate completely as desired as long as they obey Command Radius and other rules, regardless of the HQ Move Order. (See also 2.4h)

2.4c ‘No Orders’ Order. Such a Formation cannot move its HQ, aside from having it conduct a Voluntary Retreat. This does not affect the Formation’s units at all—only the HQ. A Formation not given any other Order is assumed to have a ‘No Orders’ Order.

2.4d Prepared Defense Order. A Formation with such orders must create or maintain a Prepared Defense when it Activates. This is easily confused. The player must designate that he wants a given Formation to enter Prepared Defense during the Orders Phase, but he cannot execute those Orders until the Formation Activates (and cannot then decide to not do so).

Formations that begin a scenario in Prepared Defense cannot intentionally leave that status until turn two. A Formation which loses its Prepared Defense defaults to No Orders. A Formation with Prepared Defense Orders cannot intentionally remove its Prepared Defense marker (even to do a Voluntary Retreat).

2.4e Fatigue Recovery Order. The Formation commits to conducting a Fatigue Recovery when it Activates. Failure Flip (3.7d) is not possible when using the Order rules.

A Formation can be given both Prepared Defense and Fatigue Recovery Orders at the same time. Simply apply the restrictions of both. If such a Formation defaults to No Orders (via 2.4d), the Fatigue Recovery Order disappears as well provided it has not already been executed.

2.4f Orders can be changed only in the Orders Phase. Existing Orders can remain active for as long as the player wishes. Changing Orders is free, merely jot down the new Order and the Formation will do just that. Exception: You may substitute a new HQ Move Order (only) for one it may have any time the Formation’s MSR is blocked during the current game-turn.

2.4g March OBJs. March OBJs control HQ movement to conform to its Orders. The HQ must move directly toward this marker as best it can manage following the route notations in the Order. The March OBJ marker can be placed in any road hex (regardless of enemy units).

March OBJs do not create OBJ Zones.
Recon units cannot create March OBJs.
March OBJs, themselves, do not trigger checking for Fatigue increase.

2.4h March Routing. Apply this rule when an Order places a March OBJ beyond the HQ’s at start Command Radius.

i) There is a route of travel for the HQ because of the Order. Regardless of the HQ’s direction of travel (advancing or retreating), the route is the path from the March OBJ marker to the HQ’s starting hex (remember the HQ must end its movement in a road hex each Activity Phase, 4.7a). Add an extension from the Combat Trains to whichever of these points is closer to the Combat Trains.

ii) This route should be simple and direct. If multiple routes are possible, note the correct one. Enemy units, EZOCs, and other friendly Formations have no effect on route selection.

iii) The Formation’s units can only move into a hex that is w/i 2 of any hex of the designated route unless exempted via part iv below.

iv) Units can move freely if:

They are currently within the HQ’s at start Command Radius.
They follow the route, reach the March OBJ marker’s hex, and then proceed farther.
Executing a Retreat or an Advance after Combat.
They are Reinforcements trying to rejoin the Formation.

Design Note: This is a concept I tried mightily to find a simple solution for in the design process. Easy enough on the face, I could not find an adequate wording that didn’t instantly find players violating the intended spirit by weaving paths to avoid being hindered by its restrictions. Others very much appreciated the added depth it gave the simulation. I present its final testing form here for your enjoyment…but if you think you might ‘play’ the path to ‘pick up units’, just do me a favor and don’t use it. If you have an understanding of what an Axis of Advance would look like in real life and want that added dimension in your play—enjoy the swim!

A nice by-product of this rule is the need to assemble a dispersed Formation to do such a movement and to move the troops out in deployment once they get to where you want them. This takes time. As such, you can’t instantly change posture from widely dispersed to a deep movement (or vice versa). Those are good things. Nicely, “posture” comes from “capability” (as opposed to the other way around). This is a better representation of real life.

Obviously, the restrictions here give you even more reason to avoid HQ micro-movements!

BCS 2.5 Activations

In the Activation Phase, Formations from both sides alternate Activating. The ‘Active player’ conducts the current Activation while the other player is the ‘Inactive player.’ The Active Player makes all dice rolls, moves units, attacks, and anything else he desires and the rules allow. The Inactive player is limited to taking Step Losses, Retreats, removing Dropped Support in certain situations (1.5i), and exiting Screen (4.6).

When one Formation is completed, the players switch roles and the new Active player selects a new Formation to activate.

2.5a You must Activate (or attempt to Activate) a Formation every time play passes to you. You cannot decline to Activate. There is no ability to “pass.”

2.5b Only one Formation Activates at a time. Exception: In group-games, multiple Activations (even from both sides) can be run simultaneously, provided the Active Formations do not interact with each other.

2.5c Each Formation must Activate at least once in a game-turn. Formations that set up “Done” cannot Activate on the first game-turn. One that sets up “Used” must attempt a Second Activation (the set up has removed its Initial Activation, so this is an exception to 2.5e). Both types of Formations return to normal on succeeding game-turns.

Play Note—Done HQs: Normally, an HQ’s ‘Done’ status is shown by orienting the HQ’s counter opposite the way of its units (with its banded ‘Used’ side showing). However, since all Second Activations must occur immediately after the Formation’s Initial Activation, the designation can be ignored on most game turns. The exception is in some scenarios, where Formations might begin already ‘Used’ but still need to attempt to Activate. In that case, it is important to know who is ‘just’ Used and who is actually Done. At other times, just flipping to Used is enough of a marking to know who is also Done.

2.5d Initial Activations require no die roll; Second Activations only occur after a successful Activation die roll.

2.5e A Second Activation, if any, must be attempted immediately after a Formation’s Initial Activation.

You can forego doing one, but no matter how you choose, you cannot later change your mind. It can be important to avoid the risk of a Second Activation when units might suffer Isolation twice or increase the Formation’s MSR Blocked Level more rapidly. A Second Activation with a Partial or Full SNAFU result always rolls for Fatigue Increase. Do not roll if they get a Fail or do not obtain a Second Activation (whether they fail the roll or the player chooses to not try for one).

2.5f Second Activation Restrictions. Formations cannot conduct Second Activations if they have:

Fatigue Level-4.
Conducted a Recovery Activation.

All others can do so (including Formations in Prepared Defense).

2.5g Prepared Defense cannot be created, or Fatigue Recovery done, in any Second Activation.

2.5h To conduct a Second Activation, roll one die. Add one to the roll if the Formation is Fresh. If the modified roll is greater than or equal to the Activation Roll on the HQ’s counter, the Formation successfully activates. Otherwise it does not.

2.5i Whether you choose to skip a given Second Activation attempt or if you fail to get it, the Formation cannot be activated again that turn. Rotate the HQ’s counter to show its “Done” status (usually opposite the normal unit orientation on your map).

2.5j The current game-turn is done once all HQs are Done. A side is completed when all its HQs are Done. The other side continues until all its HQs are Done as well. The Activation Phase ends at that point.

To be clear, a turn does not end when only one side runs out of Formations to Activate; it does so when they both run out.

2.5k [Optional] Formation Activation markers. Each Formation has a ‘Formation Activation’ marker. These can be used to keep track of Formations that still need to Activate. When a Formation is done, remove its marker from those available. It will return the next turn. These are termed “chits” in the remaining rules in this section, except 2.5n).

2.5l [Optional] Random Selection. Place the available chits in a cup and randomly draw them to determine the next Activating Formation.

2.5m [Optional] Modified Random Selection. Have the available chits from both sides in a common cup. Randomly draw three chits. The side owning the majority of those drawn selects the Formation to Activate from the drawn chits. The remaining chits go back into the cup. Set aside the used chit for next turn. If the player wins the cup draw multiple times, he could Activate multiple times in a row. If only one or two chits remain in the cup, select only one chit and that chit is the Formation to Activate.

2.5n [Optional] Activation Smoothing. Contributed by Björn Högberg.

i) Most times, one side has more Formations to Activate than the other. Normally all these “extra” Formations Activate after the side with fewer Formations is finished. This rule ensures “extra” Activations happen at random times within the turn and not at the end as a group.

ii) Call the two sides: ‘Large’ and ‘Small’ because of the number of Formations each has available. At the start of each turn, put numeric chits into a cup equal to the number of Small’s Formations. Number these chits 1 or 2. Only use a number of 2-chits equal to the difference in number of Formations between the two sides. The rest will be 1-chits. Say if Large has 8 formations and Small has 5 formations, 5 chits will be put in the cup. Three of them will be 2-chits and the last two will be 1-chits.

iii) Each time Large becomes the Active Player, he draws one chit. If it is a 1-chit, Large Activates one Formation followed by Small’s next Activation. If it is a 2-chit, Large Activates two Formations in a row before Small does one. Small does not draw any chits. Note that the Chit draw does not override the normal means of determining who goes first.

iv) Do not count any Formations that begin the Scenario “Done” in the number used to determine the chits above for the first turn.

BCS 3.0 Formation Activation Sequence

Follow this phase order to conduct any Formation’s Activation Phase. “If allowed,” “as needed,” and “if desired” assumed in all cases. If a specific function “must” be conducted, the preceding does not override that requirement.

a) HQ Initialization. Identify the Formation to activate. Flip the HQ to its “Used” side (the one with the white stripe). If the Formation HQ started the turn on its “Used” Side, skip to step (i) below.

b) Preparation. The Active player will conduct strictly in order:

Add or increase the Active Formation’s MSR Blocked marker if the Formation’s Combat Trains are Off-Map.
Remove the Active Formation’s Combat Trains if the Formation does not have a Complete MSR.
Remove the Active Formation’s MSR Blocked marker if the Formation has a Complete MSR.
Create, maintain, or remove the Active Formation’s Prepared Defense marker. Prepared Defenses can only be created in Initial Activations.
If the Active Formation is Mixed, apply Coordination markers.

Skip to step (c) if not doing a Recovery Activation, otherwise conduct the items in this shaded box.

If you wish to declare a Recovery Activation (3.7), do only the following sequential actions, if allowed or required by other rules:

Remove any Coordination marker, if the Formation is not currently Mixed.
Flip the Combat Trains out of Ghost.
Remove any Dropped Support markers.
Reduce Fatigue by one level.
Apply Isolation effects.
Set its Formation Activation marker aside for next turn.
Continue play starting with step (j).

c) SNAFU. The Active player:

Makes a modified dice roll on the SNAFU Table to determine the Formation’s SNAFU Result.
If the Active Formation is not currently Mixed, remove its Coordination marker after the roll.
Decides if the Formation is to do a “Failure Flip” Activation as per 3.7d.

d) OBJ Placement. The Active player places available OBJ markers.

e) Activities. The Active player will:

Conduct the Formation’s unit Activities. Non-FINISHED units conduct their choice of Movements, Engagements, Regular Attacks, Shock Attacks, Barrages, and Attacks by Fire.
If the Combat Trains are at Optimal Distance and did not move in any way, flip them away from their Ghost side. If they did move in any way OR are not Optimal, flip them to their Ghost side.
“Move” Combat Trains from Off-Map (as Ghost) if it creates a Complete MSR.
Intentionally remove the Active Formation’s Prepared Defense, if desired, when not using the Orders rules.

f) Clean Up. The Active player will:

Remove all OBJ, Traffic, and Temporary Dropped Support markers.
Flip Combat Trains which are not at Optimal Distance to their Ghost side.

g) Fatigue. If Fatigue Increase is possible, the Active Player rolls to see if it occurs to the Active Formation.

h) Isolation. The Active Player applies any Isolation Losses to the Active Formation’s units.

i) Second Activation. The Active player will:

Orient his Active Formation’s HQ as “Done.”
If intentionally skipping a Second Activation, Fat-4, OR a Recovery Activation, go to step (j).
Roll to attempt a Second Activation. (+1 if Fresh) If roll succeeds, go to step (b). If the roll fails, go to step (j).

j) Other Player's Turn. The new Active player follows the above sequence again for his Activation.

Continue this cycle until both sides have run out of Formations to Activate. Then move to step (f) in the main turn sequence in 2.0.

BCS 3.1 Main Supply Routes (MSR)

A Formation has a “Complete MSR” if there is a contiguous series of Legal hexes (3.1a) that connect all three of the following (in order) from the HQ through its Combat Trains, and then to a Supply Source.

i) To be perfectly clear, each hex of a Complete MSR must be independently Legal according to the requirements in 3.1a.

ii) An HQ can only use its own Combat Trains to establish a Complete MSR. It cannot do so if its Combat Trains are Off-Map.

iii) Once established, the HQ-to-Trains trace path may not change until:

The HQ or Trains move.
The enemy disrupts the trace.
The HQ/Trains are Jumped and must relocate.

Determine specific MSRs at the beginning of the scenario. Use the simplest and most obvious routing for each so that the scenario start is not done in a vacuum.

iv) Check the Formation’s MSR during each Preparation Phase. If there is no Complete MSR, the Combat Trains must be removed from the map. Off-map Combat Trains cause a -3 DRM on the ensuing SNAFU roll.

If the Combat Trains are already Off-Map, the Formation suffers an MSR Blocked marker with an additional SNAFU DRM, which might increase in severity up to a peak of “MSR Blocked Level 2.”

3.1a Legal Hexes. A Legal Hex:

✔ Contains a Primary or Secondary Road OR a Track. Tracks can only be used if the hex is between the HQ and Combat Trains (inclusive).
✔ Is connected to a Supply Source using contiguous Legal hexes or is a Supply Source itself.
✔ Does not block an existing enemy MSR if that enemy Formation has no other readily available MSR option(s).

A Legal hex cannot contain:

✔ EZOCs. Note: Another friendly unit can negate EZOCs for an HQ to make its hex Legal (and for no other purpose).
✔ Enemy Units.

Apply the “Uses Tracks” SNAFU DRM (of the value appropriate to the Trafficability), regardless of the number of Track hexes involved.

Play Note—Legal Hexes: Stand Alone: The key here is to evaluate each hex as Legal or not based on its own circumstances. The only real change here (aside from cleaning up the organization) is that you can legally place the Combat Trains in a Track hex. But, keep in mind that all the other hexes of the MSR still need to be evaluated. So, it is OK if the Combat Trains are in a Track hex, the hex next to it (outside the link between the HQ and the Combat Trains), cannot be and remain Legal.

Play Note—Legal Hexes: Connection: While the usual (and preferred) arrangement for any MSR is Complete, with Legal hexes all the way from the HQ through the Combat Trains and then to the Supply Source, this isn’t always the case. If your MSR has gotten cut by your choices, terrain, or the enemy, keep in mind that the second requirement of 3.1a does not require a Complete MSR to be Legal. It just requires the hex (itself) to be connected to (or in) a Supply Source. When Combat Trains move, they must move to a hex that creates a Complete MSR. The sequencing involved when Trains are sent off map and when MSR Blocked markers are issued is important and introduces a small time delay from the origin of your Formation’s problem and the end effect on your SNAFU rolls. Keep that mechanically rigorous so you do not confuse yourself.

3.1b When Needed. Legal Hexes are required for a Complete MSR. HQs must retreat to a Legal Hex (unless 4.7f is in effect). Otherwise, units and even HQs move freely without concern about Legal Hexes (beyond the need to have an MSR to get a decent SNAFU result).

3.1c MSR Blocked. If marked MSR Blocked, a Formation cannot keep or build any Prepared Defense. Apply the appropriate Combat and SNAFU Table DRMs. There is no Isolation effect for being merely MSR Blocked.

Only place MSR Blocked markers in the Preparation Phase if the Formation’s Combat Trains are already Off-Map. If the Formation has no existing marker, add an MSR Blocked Level-1 marker. If it is already marked MSR Blocked Level-1, increase it to Level-2.

If a Formation has a Complete MSR in the Activation’s Preparation Phase, remove any MSR Blocked marker (either Level) it might have.

Example: SNAFU

Here the 112 IR is Activating and needs to make a SNAFU roll. The pathway to the 112 Inf Combat Trains is blocked by the German unit at A. There is no other available path to the Trains (B cannot be used because it is a Railroad). So the Trains do not allow a Complete MSR. They must be removed before the SNAFU roll.

Because the Trains are Off-map and the MSR is not Complete, the various DRMs for a Complete MSR do not apply (Optimal Distance would apply for a net +1). Instead, only the -3 for the Combat Trains Off-Map applies.

CCR/9 is Buddies (Last Blitzkrieg rule 1.7) with the 112 IR, so they cannot be Mixed or suffer Crossing the Streams.

It is Dec 18, so the Game Specific SNAFU DRM is -1, giving a net DRM of -4.

With a -4, on two dice, a 6 or less will be a Fail, 7-10 a Partial, and 11 or 12 a Full.

However, even a Full will be applied as a Partial since the player wishes to keep his Prep Def.

BCS 3.2 SNAFU

The SNAFU Table reflects supply and other logistical concerns (including transportation, routing, march traffic control, and simple friction). A dice roll on the SNAFU Table plus the application of a number of DRMs listed below generates one of three SNAFU results (Full, Partial, or Fail). These define what can and cannot be done during the Activation as per the SNAFU Results Effects Chart.

3.2a Each Formation’s Activation requires a SNAFU roll. A separate SNAFU roll is made for the Second Activation.

3.2b SNAFU Table Rolls. A SNAFU roll uses two dice and an assortment of DRMs on the SNAFU Table. Game Specific rules also list additional SNAFU DRMs.

3.2c Coordination. This DRM applies if the Formation has a Coordination marker. A Formation cannot have more than one Coordination marker, but a single Formation can inflict Coordination on multiple other Formations. Formations marked with a Coordination marker must “pay” for it by applying a DRM on the SNAFU Table. Remove the marker after the roll if the Formation is not Mixed (see 3.2d in that case).

3.2d Mixed Formations. Formations are Mixed if any Active unit begins within or enters (even momentarily) during movement any hex inside an Inactive Formation’s “Blob.”

Design Note: The Blob outline should be a simple observation by eyeball. The Formations are either using the same area or not. Don’t overthink it, just look at what is going on. Yes, if a unit Retreated to a bad location, you might now be Mixed and you need to Activate to fix the mess.

i) This also applies during Advance after Combat, Retreat ending hexes, or Reinforcement placement. Mixed status varies depending on the order of activations.

ii) Mixed Formations do not apply to or from:

Combat Trains.
Out of Command Radius units.
Unassigned Independent units.
Buddies.

iii) If the Formation is currently Mixed:

Apply a Coordination marker to each Formation involved.
Apply the Mixed Formations DRM for SNAFU as well.
If the Formation is currently Mixed and has a Coordination marker, it will use a -2 DRM for SNAFU and (in theory) will remove the marker, but since it is still Mixed, it will obtain a new one instantly. In that case, apply the DRM, but do not remove the marker.

3.2e Fatigue. Fatigue Level is a negative SNAFU DRM, e.g. Fat-1 would be a -1 DRM. Fresh Fatigue is a +1 DRM.

3.2f Optimal Distance. The MSR distance from an HQ to its Combat Trains must be between 5 and 15 hexes (inclusive, counting along each road hex used) to gain the DRM. Optimal Distance also applies if Combat Trains are in an Entry Hex and the HQ is not more than 15 hexes away. The DRM cannot be applied if the Combat Trains are forward of the HQ. They are “forward” if the MSR from the HQ to the Combat Trains and the MSR from the Combat Trains to the Supply Source share any hexes (excluding the Combat Trains hex itself).

3.2g Ghost. If the Formation’s Combat Trains are currently on their Ghost side, apply this DRM.

3.2h Crossing the Streams. This DRM applies if the path between the HQ and Combat Trains uses any hex used by another Formation’s HQ and its Combat Trains (inclusive). There is no additional effect based on the number of Formations involved at once.

3.2i MSR uses Tracks. The Track DRM applies if any MSR hex uses Track instead of better road types. The number of such hexes used has no effect. Track hexes are Legal only between the Combat Trains to the HQ, inclusive. (3.1a). There are two values for this DRM; use the one associated with the current Turn’s Trafficability (due to Weather Effects).

3.2j MSR Blocked. MSR Blocked markers have a negative DRM equal to their MSR’s Blocked Level. Use this in addition to the DRM for having its Combat Trains Off-Map.

3.2k Results. SNAFU results can be Full, Partial, or Fail. The SNAFU Result Effects Chart lists their effects. Once a result is determined, it remains in effect for the entire current Activation; a new SNAFU result will be determined for each later Activation, to include the current Formation’s Second Activation, if any.

A Formation with a Prepared Defense reduces its SNAFU result of Full to a Partial.

BCS 3.3 Objectives

(OBJs)

i) You typically need OBJ markers to attack, barrage, and to take control of Victory hexes. Place them during Activations to identify where the Formation will execute active operations. There are OBJ markers allowed by the SNAFU result, those created by the Formation’s Recon units, and the one designating the HQ’s March OBJ.

ii) Of these, all but March OBJs are “Combat OBJs” which generate OBJ Zone hexes needed to conduct almost all attacks and barrages, as well as to take control of Victory Point hexes.

iii) The one exception is that Engagement Table fires do not need an OBJ Zone at all.

iv) March OBJ markers are used to identify the Formation HQ’s ending location for the Orders rules. This location restricts the HQ’s movement based on the location chosen. (2.4b)

v) March OBJ markers do not create OBJ Zones allowing any form of combat.

3.3a OBJ Zones. Each OBJ marker creates a 2-hex radius OBJ Zone. An OBJ Zone hex is required to make any:

Regular Attacks.
Shock Attacks.
Attacks by Fire.
Barrages.
Move into an uncontrolled VP hex. In the case of VP hex entry, the OBJ marker must be in the VP hex itself.

Engagements, however, do not require OBJ Zones, but could apply the DRM for a Double OBJ Zone if the target lies within it. While Double OBJ Zones have access to DRMs, there are no additional effects for multiple OBJ Zones within one hex.

Example: Objective Zones

Remember, the OBJ hex must have an enemy unit or Victory Hex in it. Using the shaded OBJ Zone…

Unit A can be Attacked, Attacked by Fire, Barraged, and have its Support Engaged.

Unit B can only have its Support Engaged.

3.3b Double OBJ Zones. These are created by two co-located SNAFU OBJ markers. The target of any Engagement or Attack in a Double OBJ Zone applies a DRM.

3.3c OBJ Marker Availability. The SNAFU Result Effects Chart gives the number of OBJ markers a Formation can place. OBJs created by Recon (3.3f) and March OBJs (if used) do not count against the number allowed.

OBJ markers cannot be saved for future Activations, given to other Formations, or saved for the Formation’s Second Activation. Remove them in the Activation’s Clean Up Phase.

3.3d OBJ Marker Placement. You can place all, some, or none of your available OBJ markers anywhere you like at any distance from the HQ. OBJ markers must be in a hex containing an enemy non-Support unit and/or a Victory Hex designation. (See 2.4g regarding March OBJs.) Once placed, the marker cannot be moved or removed until the Clean Up Phase. OBJ markers have an arrow on their counter to off-set the marker if desired.

Design Note: Obviously, having to place Combat OBJ markers literally on top of enemy units is an abstraction. Anyone who has ever looked at a real OBJ knows they are best selected by geography. This was allowed in earlier system versions, but players were doing all manner of obscene things with OBJ markers in an attempt to maximize their usefulness in hitting multiple targets or catching units that retreat. OBJs started showing up in back of enemy units and even on top of friendly ones. The time expended here was criminal. This simplification reduces the crazed planner effect.

3.3e OBJ Marker Removal. In every Clean Up Phase, remove all OBJ markers from the map.

3.3f Recon Created OBJs. Recon units can place Recon OBJs after the Activities Phase begins.

Recon OBJs are not constrained by the number of SNAFU OBJs allowed.

To conduct a Recon, the Recon unit must:

✔ Be identified both with Recon capability in the Unit Capabilities Chart and in the game specific rules.
✔ Have at least one Fire Event to expend.
✔ Not be STOPPED ** nor overstacked.
✔ Not attempt to Recon a hex already containing an OBJ; Recon units can never create a Double OBJ.

** You can waive a STOP created by AV EZOCs by winning Stopping Engagements. It does not matter if a Stopping Engagement is required or not. A Recon unit must eliminate the STOP to do a Recon.

3.3g Recon OBJ Placement Procedure. The Recon unit expends one Fire Event, rolls one die, and compares the result to the Recon unit’s Action Rating.

If the roll is less than, or equal to, the Recon unit’s Action Rating, place one OBJ marker on any enemy unit (or VP hex) w/i 2 of the Recon unit.

If the roll is greater than the Action Rating, the attempt fails. Place no OBJ marker. If the Recon unit has another Fire Event, it can attempt to recon that, or another, hex again. If another Recon unit is available, it can attempt to Recon a hex which was tried earlier but failed.

Once created, a new OBJ marker and its OBJ Zone exists for all the active Formation’s units (including the Recon unit itself).

Example: Recon OBJs

In the midst of this Activation, the German player has attacked hex A (which also contains an OBJ set earlier and the shaded OBJ Zone). The unit defending there was forced off map in its Retreat and will return to the HQ next turn.

The German Player has dispatched KG Stephan, which is Recon Capable, to set a Recon OBJ on hex B to allow a follow-on attack to clear the bridge. The player could opt to do the Recon either from the C or D hexes. The D hex is under the Support AV EZOCs of the unit in B, so to Recon from there will require dropping Support first, to eliminate the STOP. Hex E cannot be used because of the STOP Terrain. However, without an OBJ in the VC hex (with the US Star in it), units won’t be able to cross the bridge into that hex, even if the unit in B is removed.

KG Stephan uses one Fire Event for the attempt from C.

Roll one die and compare to KG Stephan’s Action Rating (5).

If the roll is 5 or less, the Recon is successful and the marker is placed on B.

If the player rolls a 6, no OBJ is placed, but KG Stephan can try again if it still has its other Fire Event.

BCS 3.4 Activities

3.4a Only the currently Active Formation’s units can perform Activities during the current Activation. If units of multiple Formations stack, only those belonging to the currently Active Formation functions.

3.4b In general, you are free to use your Formation’s units and artillery in any order you like, but you must finish moving one unit before starting another. No unit or Artillery/Air Point can be used more than once in an Activation. After its chance to move and use Fire Events, a unit can only Attack, Assist, or spot for Barrages. You cannot go back to an earlier unit for other purposes, even if MPs or Fire Events remain.

3.4c Make any desired Barrages before, during, and/or after any unit’s movement.

3.4d Units move individually, not as Stacks. One unit must end its movement for the phase before another can start. You cannot go back to a unit after starting the movement of another, except for the handful of actions listed in 3.4f.

3.4e Units STOP and/or FINISH during the course of the Activation. See the STOPPED / FINISHED Chart (on the next page) for a full listing of the causes and effects of each.

3.4f A unit that is not yet FINISHED, but is done moving and the player has started moving some other unit cannot use any remaining:

Fire Events.
MPs.

But can…

Attack or Assist.
Spot for a Barrage.

3.4g A unit FINISHES when it:

Conducts or Assists a Regular Attack.
Executes a Voluntary Retreat.

3.4h A FINISHED unit cannot:

Move (regardless of remaining MA).
Execute any remaining Fire Events.
Attack or Assist.
Enter Screen.

But, a FINISHED unit can spot a Barrage.

3.4i A STOP does not preclude executing remaining Fire Events and/or FINISHING by other means.

Play Note—Movement Sequencing Options: You can, for example, move unit A, move unit B, fire a Barrage, move unit C, attack a hex using A with B as Assist (A enters the hex after winning), fire another Barrage (using A as a spotter from its new hex), move unit D through the hex cleared by the attack, use D to initiate Engagements against some deeper enemy hex, move unit E through the same hole in the enemy line, attack with stack C with an assist from E… and so on.

What you can’t do, for example, is move unit A some MPs, fire a Barrage, move unit B… and then go back to finish unit A’s remaining MA, etc.

You also cannot move unit A, then move unit B, and then go back to unit A to conduct Engagements, Shock Attacks, or Attacks by Fire. Those must be done before starting a new unit.

You can, however, move unit A some, do an Engagement, Shock Attack, or Attack by Fire, move unit A some more and do another Engagement, Shock Attack, or Attack by Fire and then call a Barrage. Then move unit B so that A and B can make a regular Attack together (as Attack and Assist).

BCS STOPPED/FINISHED Chart

Things That Make You STOP

Using both Fire Events.
Terrain effects.
Traffic markers.
Leg or Truck MA movement into any EZOC.
Tac MA movement into an AV EZOC.
Starting to move another unit.
Truck MA movement into an Engagement Zone.
Failing a required Stopping Engagement.
Spotting a Barrage outside an Attack Sequence.

Things You Can Do STOPPED

Spot Barrages.
Initiate Engagements.
Attack.
Attack By Fire.
Assist an Attack.

Things You Cannot Do STOPPED

Move.
Recon.
Shock Attack.

Things That Make You FINISH

Participation in a Regular Attack.
Execute a Voluntary Retreat.
Entering a Required Stopping Engagement hex when Light AV or as a Screen.

Things You Can Do After FINISHING

Spot for Barrages.

Things You Cannot Do After FINISHING

Use remaining Fire Events.
Move.
Attack or Assist.
Enter Screen.

BCS 3.5 Clean Up

Do the following in every Clean Up Phase:

✔ Remove all OBJ, all Traffic, and any Temporary Dropped Support markers which have not converted into Dropped Support markers.
✔ Flip Combat Trains not within Optimal Distance to Ghost, if not already.

BCS 3.6 Isolation

Units that are cut off from their HQs suffer losses from Isolation every time they Activate. This is a more debilitating situation than when the units and HQ are “isolated” together by a Blocked MSR.

3.6a Identify Active stacks that have no Safe Path and/or are Out of Command Radius (even if from Advance after Combat). Check to see if the Formation has an MSR Blocked marker. Find these conditions for each unit using the Isolation Chart and apply any loss listed in the appropriate line.

3.6b Reinforcements. Reinforcements catching up to their Formation HQ do not apply Isolation until they start an Activation inside Command Radius.

BCS 3.7 Fatigue Recovery & Failure Flip

Fatigue Recovery enables a Formation to reduce their Fatigue level, even to Fat-0.

3.7a Limitations. No more than one Fatigue Level can be recovered in any one Game-turn. No Formation can recover to Fresh during the game. Recovering Formations cannot execute a Second Activation nor can Recovery be executed during one. Formations in Prepared Defense can recover Fatigue.

3.7b Requirements. A Recovering Formation must have a Complete MSR.

3.7c Procedure. Announce that the Formation will do a Recovery Activation during its Activation’s Preparation Phase. Make no SNAFU roll. A Recovery Activation allows only those actions listed for a Recovery Activation in the Sequence of Play and in the order presented.

3.7d Failure Flip. If you obtain a Fail SNAFU result, you can convert it into a Recovery Activation in an action called a “Failure Flip.”

i) Failure Flip can only be done in Initial Activations. A Failure Flip cannot be done in any Second Activation.

ii) Apply anything done in the Activation before the SNAFU Roll, but continue by executing only those functions in 3.7c as if you decided earlier to conduct a Recovery Activation, to include giving up any chance at a Second Activation.

iii) You can also choose to accept the Fail SNAFU result instead and continue to play normally. Failure Flips do not apply when Orders or Planned Fatigue options are used.

BCS 4.0 Movement

A player can move all, some, or none of his Activated Formation’s units given other rules; the Inactive player cannot move any of his units, except when needing to retreat.

4.0a General. i) Units move individually, but a unit can move as many or as few hexes as desired, subject to MA, SNAFU results, Traffic, enemy units, EZOCs, and terrain.

ii) Units move in any direction or series of directions, but must follow a contiguous path of hexes through the hex grid.

iii) Each unit tracks its remaining MA individually and expends MPs for each hex/hexside entered/crossed according to the Terrain Effects Chart. Units cannot transfer unused MPs to each other, nor save them for later use.

iv) Units can never enter hexes containing any kind of enemy unit, except to ‘Jump’ HQs or Combat Trains. Exception: See 4.6a, regarding Deployed-side Leg MA units and enemy Screen units.

4.0b Switching Counter Sides. Most units have two counter sides showing the unit in different postures. Flipping does not cost MPs. Units can only flip before beginning any Activities and no unit can flip more than once per Activation. A unit can only flip with the appropriate Safe Path (see 1.9). A Unit functions based on the values showing; its face-down side has no effect at all.

4.0c Halved Movement Allowance. An MA might be halved for a number of reasons. Regardless of the applicable number of reasons, halve the MA only once. Always keep fractional MA; do not round them in any way.

4.0d Traffic. Place Traffic markers in the Defender’s or Firer’s hex, based on Combat or Engagement Table results respectively. Traffic markers inflict a STOP on all units within or entering their hex. Traffic markers inflict their STOP but have no actual MP cost. If a Traffic marker exists in a hex that is already fully or over stacked, additional units cannot enter that hex even momentarily.

Design Note: In BCS games before Panzers Last Stand, Traffic markers said “Stopped” on them (short for “Traffic Stopped”). This was clarified in PLS.

4.0e [Optional] Unit Traffic. Unit Traffic has no marker. Unit Traffic exists in any hex containing any Unit except Deployed-side Active Units.

Exceptions: HQs always create Unit Traffic, but Combat Trains, Unassigned units, a unit in an Entry Hex, and any unit currently Screening are ignored entirely.

Screen Zone hexes, friendly or enemy, have no effect on Unit Traffic, or vice versa.

Units entering a Unit Traffic hex do not benefit from any roads in or entering hex. They must pay the hex’s “other terrain” MP cost (hex and hexside) instead. If the “other terrain” hex and/or hexside is Prohibited to the unit, it cannot enter the hex. “Other terrain” only applies to entering the Unit Traffic hex, and never to exiting one.

Design Note: ‘Unit Traffic’ was a part of plain Traffic and the system standard for a long time. It was always a time consuming matter and provided only modest returns. Some players loved it, others hated it. I’d suggest playing without Unit Traffic at first only adding it later if you prefer greater detail. It does work very well, but it is also a lot of work & time as players will carefully orchestrate their moves.

BCS 4.1 Terrain Effects

Each hex and hexside feature costs a specific number of Movement Points as listed on the Terrain Effects Chart. This cost varies depending on the unit’s Movement Class: Tactical, Leg, or Truck. Units have independent MAs and the MP expenditures of one unit do not affect any other. Add any hexside MPs to the hex’s cost. The moving unit must pay the entire MP cost before entry. Exception: One-hex Movement (4.1f).

4.1a Multiple Terrain Types. A hex might have more than one hex terrain symbol. The symbol’s quantity does not matter. Use the type most costly for movement if not moving on roads.

4.1b Reciprocal Moves. A unit can only move from hex A to hex B if it could also move from hex B to hex A.

4.1c Roads. A unit can pay road movement costs and ignore the normal hex and hexside MP costs, if the unit follows a continuous road path and the road is not negated by Unit Traffic. Roads within a hex are assumed to intersect, even if no intersection is literally shown.

4.1d Prohibited Terrain. Units cannot enter or cross Prohibited hexes or hexsides, unless using a bridge or road.

4.1e STOP Terrain. Units must STOP upon entering any STOP Terrain hex, regardless of their remaining MA. STOP terrain hexes cost 4 MPs.

4.1f One-hex Movement. If otherwise eligible to move and not yet moved in this phase, a unit without enough MPs can always move one hex. Units can never use this rule to:

Conduct a Shock Attack.
Move across or into Prohibited terrain.
Violate Failed SNAFU effects.
Violate EZOC effects.
Move with a printed MA of Zero.

BCS 4.2 Stacking

Normal stacking is two Combat Units. HQs, Support, Combat Trains, and all game markers do not count for stacking.

Over-Stacking is allowed (with exceptions listed in 4.2b) but brings with it DRMs on the Combat Table and multiple rolls on the Barrage Table.

4.2a A stack’s top Combat Unit must be the one with the longest printed Range (use greatest AV rating in ties). Otherwise, you can freely determine stacking order at any point during your Activation.

4.2b Over-Stacking is not allowed at the moment when:

Using any Fire Event.
Being selected as an Attack or Assist unit.
Entering a hex with a Traffic marker.

4.2c Defending an Over-Stacked Hex. Over-Stacked hexes defend normally in most cases, but with the addition of the Combat Table’s Over-Stacking DRM.

Naturally, the Barrage and Attack by Fire systems will make over-stacked hexes death traps. But, sometimes you have reasons.

BCS 4.3 Zones of Control (ZOCs)

CONTROL (ZOCs)

4.3a With the explicit exceptions in 4.3b, Combat Units have ZOCs in the hexes adjacent to them. ZOCs come in two varieties: normal ZOCs (generated by all but the units listed in 4.3b) and AV ZOCs (which are only generated by AV units).

4.3b HQs, Combat Trains, Screen units, and Unprepared units do not have ZOCs.

4.3c Restrictions on ZOCs. Terrain does not restrict ZOCs. Friendly units only negate EZOCs for Safe Paths and the movement of HQs (4.3d).

4.3d EZOC Effects. EZOCs affect movement depending on the moving unit’s MA Class and/or type. No unit can move directly from one EZOC to another that affects it. Units can freely exit any EZOC it began its movement within (provided it does not move directly into another EZOC that affects it).

i) Leg MA and Truck MA units must STOP if they enter any EZOC.

ii) Tac MA units must STOP on entering an AV EZOC (Real or Support) hex. This may require a Stopping Engagement. But, only Real AV EZOCs apply to Tac MA units for Safe Path determination. (1.9d)

iii) HQs can never enter an EZOC unless the EZOC is negated by a friendly unit.

4.3e EZOCs and Retreats. Appropriate EZOCs in a Retreat’s ending hex can inflict step losses on the retreating units. EZOCs that eliminate the Safe Path of Leg or Truck MA units might cause them to be unable to retreat and take a Step Loss instead. EZOCs have no effect at all on retreating Tac MA units.

4.3f AV ZOCs. AV ZOCs affect the movement of enemy Tac MA units, whereas normal ZOCs do not. AV ZOCs are generated by Real AV units or by Support. These are Real AV ZOCs or Support AV ZOCs, respectively. AV ZOCs are limited to hexes adjacent to it, regardless of the unit’s Range. Support AV ZOCs are available to any currently Supported unit.

BCS 4.4 Stopping Engagements

While moving into AV EZOCs requires your moving unit to STOP, winning a Stopping Engagement could allow it to “break free” (“waive the STOP”) so it can keep moving. Stopping Engagements never occur in any non-AV unit movement, Advance after Combat, or Retreat.

Some Stopping Engagements are required (meaning you must fire at least once even if you don’t intend to keep moving), while others are not (you can decide to not fire at all and merely STOP in place).

Each Stopping Engagement “shot” costs one Fire Event like any other Engagement.

4.4a Required or Not Required? A Moving unit is required to make at least one Stopping Engagement if the AV EZOC entered is generated by either a:

Real AV unit or
Host with Stand Off Support.

A Stopping Engagement is not required if the AV EZOC is exclusively from Hosts with non-Stand Off Support. The player is free to fire, anyway, in order to waive the STOP.

Exception: Light AV and all AV-armed Screening units cannot execute a required Stopping Engagement. They become FINISHED instead. If the Stopping Engagement is not required, they STOP normally.

4.4b Waiving a STOP. The STOP requirement is waived if no AV EZOC remains in the firing unit’s hex. An AV EZOC disappears if the unit providing it:

Is Destroyed.
Retreats.
Is a Host and it Drops Support.

The moving unit “wins” if the hex’s STOP is waived. It loses if it does not. If a unit ‘loses’ a required Stopping Engagement it remains STOPPED.

Regardless of the failure of any earlier Stopping Engagement, the unit can expend its remaining Fire Event as an Engagement that might open up that EZOC hex to the movement of his other units.

Example: Stopping Engagements

Here the II/16 (116 Pz) has just moved into the hex adjacent to TF Harper.

A Stopping Engagement is required as Harper has a Real AV ZOC.

There are no additional DRMs in this case so it is the German unit’s effective 7 vs the US unit’s effective 6 for a +1 over all.

The first roll is a 4 with the +1 gives a 5 and a Firer Loss & Traffic. The German player takes that loss and places a Traffic Stopped marker in the Panzer Bn’s hex and could try again.

The Pz Bn is not Attack-capable, so it could not literally ‘Attack’ Harper using the Combat Table. Shock Attack would not be possible both because of the STOP and the fact that Harper is an AV.

There is another Fire Event, so it fires again, same +1, and this time rolls an 8 for a net 9. Harper takes one loss and has a Retreat result to satisfy. The Stopping Engagement has been ‘won’ but having used its last Fire Event, the Pz Bn cannot continue to move.

Example: Stand Off Support

Here the 88mm unit is with the HQ in Command Radius of the two FJ units, both of which have their Support.

TF Rose moves up from the south and wishes to attack one of these two FJ units in the hope of cutting through to the river and blocking off further advances by the FJ.

However, once it enters 31.15, it must deal with the Stopping Engagements created by the Stand Off Support from both of these units.

In this, TF Rose is in a good spot. As there is a Required Stopping Engagement in that hex, even though it is coming from two enemy hexes, only ONE Stopping Engagement is literally required (Rose can “accept” the other as ‘just a STOP’ and isn’t forced to Engage it).

The Stopping Engagement shot on III/15 is a 5 to 8 or a net -3. A roll of a 9 manages to Drop Support on this unit. As the second (identical) shot is really an unneeded risk to Rose (who will attack III/15 with a regular Attack shortly), Rose can make use of its other Fire Event to make an Attack by Fire on III/15 in the hopes of killing a step before the combat.

TF Rose will then be out of Fire Events and locked in the unwaived AV EZOC of III/14. Both of these add up to a single STOP. It is expected that Rose will attack III/15 (which does not have Support and might be down to 5 steps). With luck this will result in III/15 scurrying off and Rose will advance into 32.15. If Rose gets a Second Activation, it will then deal with III/14.

Even if a unit eventually wins the Stopping Engagement, it STOPs if it expends its last Fire Event, and you cannot ‘pause’ one unit to help it out with another before it continues.

i) In each Stopping Engagement, the active player’s moving AV unit is the Firer. The inactive player selects the Target unit he desires.

The target unit chosen must:

Contribute an AV EZOC into the moving unit’s hex.
Follow the normal Engagement Target selection requirements in 5.2b part ii).

ii) A STOP must be waived before making any Recon attempt.

BCS 4.5 Engagement Zones

4.5a Engagement Zones are generated by AV units out to the extent of their range and give the following effects:

Truck MA units must STOP on entering an Engagement Zone.
HQs cannot move into or end a Retreat within an Engagement Zone hex.

Other than these two points, Engagement Zones have no effect at all other than where they might be able to initiate an Engagement. Unlike EZOCs, friendly units do not negate Engagement Zones for HQ movement. Only Terrain and Weather affect Engagement Zones.

4.5b Only Real (i.e. not in Support) AV units (which are not Light AV or Screening) generate Engagement Zones. Engagement Zones extend into all hexes of the AV unit’s range, possibly restricted by Terrain and Weather.

4.5c Blocking Terrain (“Line of Sight”). Terrain has no effect on an Engagement Zone into adjacent hexes, but greater ranges require no Blocking terrain on the line between the endpoint hexes. Use the line connecting their center-points.

Ignore terrain in both end-point hexes entirely. Ignore all hexside features, units of both sides, and all game markers in or between the end-point hexes..

Use the listing on the Terrain Effects Chart to determine if an intervening hex blocks or not. Count entire hexes as blocking; the specific location of the symbol is irrelevant.

If the line between the firer’s hex and the target hex runs on a hexside between a blocking and a non-blocking hex, the Engagement Zone is not blocked.

BCS 4.6 Screening

Screening allows Recon units to slow enemy movement without undue risk to themselves. A Recon unit currently on its Move-side can be marked as Screen before starting its Activity Phase. SNAFU results do not affect Screens.

You can add a Screen marker to Recon units at any time in an Initial Activation (even in a Fail SNAFU), but never in a Second Activation.

Screen markers can be removed at any time (even in an enemy Activation), instantly releasing the unit.

4.6a Screen Zone Units. A unit marked Screen:

Has no ZOC.
Can move, Recon, and spot for Barrages.
Cannot end movement or retreat stacked with any other unit. Should this happen, remove all Screen markers from the involved units.
Cannot Attack, Assist, Attack by Fire, or Initiate Engagements. They are FINISHED upon entering any AV EZOC hex and cannot enter a hex that requires a Stopping Engagement.
Cannot Jump HQs or Combat Trains.

i) Enemy Tac or Truck MA units cannot enter the hex occupied by the Screen unit itself.

ii) Enemy Deployed Leg MA units can enter the hex occupied by a Screen unit and cause the Screen unit to retreat 3 hexes.

iii) Retreating does not affect the unit’s Screen marking or cause a counter flip to occur.

4.6b Screen Zone Unit Combat. Screen units are not subject to the Combat or Barrage Tables.

Screen units can be fired upon using the Engagement Table (but cannot be the Firer in an Engagement). However, convert each “Both Loss” result into a “No Losses, Target Retreats 3 hexes” result.

4.6c Screen Zones. Screen units have no ZOC, just their Screen Zone. A Screen Zone includes all hexes around the Screen unit out to a number of hexes away from the unit (inclusive). Screen Zones exist to a radius of 3 hexes (in all BCS games, a change to Last Blitzkrieg). Ignore enemy units and terrain for Screen Zone purposes.

4.6d Screen Zone Effects. Move-side Enemy units pay +1 MP per Screen Zone hex entered. Screen Zones do not affect Deployed-side enemy units. Unprepared units cannot enter an enemy Screen Zone hex. Screen Zones (including the Screen unit itself) have no effect on:

Hex Legality for MSRs.
Unit Traffic.
Safe Paths (friendly or enemy).
Engagement Zones (and vice versa).

BCS 4.7 HQs & Combat Trains

HQs and Combat Trains cannot be destroyed or captured. They can be temporarily disrupted by enemy ‘Jumping’ (enemy units moving into their hex), and have their own movement requirements.

4.7a HQ Movement. HQs move during the Activities Phase using their own MA like any unit, except they will lose any Prepared Defense markers they have if they move. When using the Orders rules, HQ movement is strictly controlled by the orders they are given. However, an HQ under Prepared Defense Orders (2.4d) cannot do a Voluntary Retreat.

Regardless of its Movement Class, HQs cannot cross or enter terrain prohibited to Truck MA.

Important: HQs must always end their movement or retreat in a non-RR road hex which, if possible, is at the end of a Complete MSR. (3.1)

4.7b Combat Train Movement. Combat Trains (which are currently Legal or Off-Map) ‘move’ by simply placing them in any desired Legal Hex (3.1a) that also creates a Complete MSR. They cannot move to any ‘Illegal’ hex or even a ‘Legal Hex’ which doesn’t generate a Complete MSR.

If the Formation does not have a Complete MSR in the Activation’s Preparation Phase, remove the Combat Trains and place them Off-Map.

Combat Trains that are Off-Map can return to any Legal hex On-Map if doing so creates a Complete MSR during the Activities Phase. Such Combat Trains have “moved” and re-enter as Ghost.

Combat Trains which…

Move or
End an Activities Phase outside Optimal Distance from their HQ (between 5 and 15 hexes) (3.2f) …must flip to their Ghost side.

4.7c Combat Train Recovery from Ghost. Ghost Combat Trains can recover to normal if:

✔ Legal and part of a Complete MSR.
✔ Within Optimal Distance.
✔ Stationary for the preceding Activity Phase.

4.7d Jumping HQs & Combat Trains. Table Retreat results do not directly affect HQs & Combat Trains, but if an enemy unit ever enters their hex, they are ‘Jumped’ and must retreat (HQs in 4.7e and Combat Trains in 4.7h). The enemy unit executing a Jump can be moving in regular movement or an Advance after Combat.

Unprepared units, retreating units, Screen units, units starting the phase Out of Command Radius, HQs, and Combat Trains cannot Jump enemy HQs and Combat Trains.

4.7e HQ Retreats. Do these things to retreat an HQ following a Jump:

✔ Retreat the HQ at least 3 hexes to any Legal Hex (3.1a) that is free of any Engagement Zone. Just pick up and place the HQ in the desired hex, with no EZOC or Safe Path concerns along the way. Exception: See 4.7f.
✔ Flip its Combat Trains to Ghost.
✔ Remove the HQ’s Prepared Defense marker, if any.
✔ Apply a Coordination marker to the HQ.
✔ Retreat does not change an HQ’s Activation Status (Available, Used or Done).

4.7f HQ Escape into a Pocket. An HQ can ignore the need for a Complete MSR and the minimal retreat distance requirements of 3.1a & 4.7e, as well as the concerns of the Directional Retreat Guidelines (5.5b), but it must end in a hex containing one of its own units.

Other than needing a Complete MSR, ALL other Legal hex requirements apply.

4.7g HQ Voluntary Retreat. An Active Formation’s HQ can Voluntarily Retreat following the procedure in 4.8, except:

HQs never lose a step.
HQs can do so even in a Fail SNAFU.

An HQ Voluntary Retreat applies 4.7e & 4.7f normally. HQ’s under Optional Prepared Defense Orders (2.4d) cannot execute a Voluntary Retreat. If an HQ does a Voluntary Retreat it must increase its Fatigue Level by one.

4.7h Combat Trains Retreat. Jumped Combat Trains retreat by just being picked up and placed in a Legal Hex creating a Complete MSR, then flipping to Ghost. That hex must be at least 10 hexes following a road down its MSR from where it started. The resulting hex need not be 10 hexes straight-line distance from where it started. If no such hex is possible, the Combat Trains are sent Off-Map.

4.7i [Optional] Soft Jumps. If an HQ or Combat Trains is Jumped, roll one die for the hex (regardless of the numbers of HQs and/or Combat Trains in it). Make this roll before resolving any Combat Unit Retreats.

i) On a 1-4 it is a Soft Jump and follows part iii below.

ii) On a 5-6, it is a Hard Jump and applies the process in 4.7e, 4.7f, and 4.7h.

iii) On a Soft Jump, the owner moves both the Jumped HQ and its Combat Trains (regardless of which gets Jumped) as desired. Retain (but do not add) any Prepared Defense or Coordination markers. The Combat Trains retain their existing Ghost status (or not) and need not become Ghost as a result.

iv) There is no path involved; the idea is that it was there the whole time. The player can shift any desired number of hexes.

v) The chosen hexes must:

✔ Be appropriate terrain.
✔ Not contain an enemy unit, Engagement Zone, or EZOC.
✔ Not block an enemy MSR.

vi) However, the hexes need not be Legal at the moment.

Design Note: A Soft Jump might look odd at first. It is not a movement of any sort. Rather, it is an attempt to add limits to the enemy’s perfect “eye-in-the-sky” intel. His units roll into a location he was certain was correct, only to find nothing there. The “new” location is actually where the HQ was this whole time (or so it seems). The enemy’s ‘perfect’ situation map was simply wrong, again.

Example: HQ Jumping

The contents of the 106 ID’s stack are splayed out around it.

KG Stephan approaching from the south needs to establish a Recon OBJ on St. Vith. This is needed because of the 168 Engineer and a VP in that hex, not because there is an HQ. This uses one Fire Event. The player rolls one die and gets a 2, which sets the OBJ marker on the HQ in St. Vith. This allows both the Shock Attack and the entry into the US controlled VP hex.

Stephan then makes a Shock Attack on the stack from 30.10. Note that there is no Support to Drop to enable this attack as there is no unit in the hex that can take advantage of the 106 ID’s Support or Prep Def. The Shock Attack is a 6 to 4 or +2. Any roll of 9 or more will dislodge the HQ and destroy the Engineer. Because the city is Key Terrain, Situational Results will not force a Retreat.

Here the player rolls a 10.

The HQ has Retreated the required 3 hexes, it has lost its Prep Def marker, and the Engineer has been destroyed. The HQ will also need to be given a Coordination marker for having Retreated and have its Combat Trains flipped to their Ghost side.

BCS 4.8 Voluntary Retreats

In lieu of normal Movement, Active units can self-inflict Voluntary Retreats to get out of locations they couldn’t exit normally. Safe Paths, EZOCs, Engagement Zones, Terrain and enemy units themselves do not restrict Voluntary Retreats.

4.8a The retreat ending hex must be 3 hexes away. Inflict one step loss and flip the unit to its Move-side. This FINISHES the unit. If the ending hex contains an EZOC, inflict the normal additional Step loss as well. (5.5g)

4.8b HQs do the same (see also 4.7g) but can extend their retreat to fulfill the conditions of a Jumped HQ in 4.7e & f. HQs do not take any step loss. HQ Retreats must be toward their Combat Trains and see 5.5b.

4.8c HQs can Voluntary Retreat under a Fail SNAFU result. All other units require at least a Partial SNAFU result. See 4.7g for more details.

4.8d HQs under actual Prepared Defense Orders (2.4d)—as opposed to an HQ that just happens to have a Prepared Defense marker— cannot execute a Voluntary Retreat.

BCS 4.9 [Optional] Realistic Movement

Players ponder, control, redo, and rework moves to squeeze out ever-greater optimization. Their opponents must do the same to compete. The result, after a great time investment, is a level of precision that has nothing to do with reality. This rule makes cardboard units move like the real thing.

4.9a Unit Movement. Units move as the real elements. If a counter moves along the grid into a hex, it really did so. No redos, if you go down the wrong track and need to back-pedal, do so literally using your MA.

4.9b Honest Mistakes. However, if you screw up (count MPs wrong, forget a rule, or what not), let your opponent know what you did and figure out where the unit should be. Changing what you’d “like to do” doesn’t count.

BCS 5.0 Combat

Combat occurs in multiple ways, including Engagements, Attacks, Shock Attacks, Attack by Fire, and Barrage. Unit types restrict the kinds of combat a unit can conduct and be subjected to. (See the Unit Capabilities Chart.) Only the Active player can initiate any form of Combat.

Play Note—Combat Type Integration: Learning to play the game requires understanding what types of combat to use versus the kinds of targets and the capabilities of your own units.

Becoming a great player is a matter of not only knowing these things, but arranging your forces so that you have the tools available to obtain your goals as rapidly and efficiently as possible. Importantly, an expert player will know what tools to leave in the toolbox given the situation he is presented and which ones will do the needed job and how well they will do it.

Regular Attacks are set piece actions coordinated between assaulting and supporting units & fires to push the enemy out of a position on the ground. Resolve these on the Combat Table.

Shock Attacks are rapid assaults by mechanized units exploiting their protection and mobility to decisively attack an enemy location. Shock Attacks allow the attacking unit to continue movement afterwards. Resolve these on the Combat Table.

Engagements are fire exchanges between weapons platforms using AV strengths. Engagements are used to generate losses, to suppress Support, and to free friendly units for movement. Unlike Attacks, they do not represent an effort to seize terrain. Resolve these on the Engagement Table.

Attacks by Fire use AV weapons against non-AV targets. Resolve these on the Barrage Table.

Barrages use Artillery and/or Aircraft to generate Suppression effects or to inflict step losses on enemy locations. Destruction Barrages use the Barrage Table to create losses. Suppression Barrages allow the player to apply DRMs on the Combat Table, but do not inflict any step losses.

5.0a “Terrain” (as in a unit “has Terrain”) are specific terrain features that affect Combat and Barrage of listed types on the Terrain Effects Chart. Both hex and hexside features could apply “Terrain” effects. Hexside Terrain applies to the Combat Table, but has no effect on any Engagements, Attacks by Fire, or Barrages.

5.0b HQs and Combat Trains cannot be Engaged, Attacked, or Barraged. They do not absorb step losses at any time or for any reason.

5.0c Screen Units cannot be Attacked or Barraged, but could be Engaged by enemy AV units.

BCS 5.1 Regular and Shock Attacks

Both Regular and Shock Attacks use the Combat Table to represent assaults into enemy occupied hexes. Shock Attacks have a number of exceptions and special requirements, which do not apply to Regular Attacks.

5.1a All Attacks. Execute Attacks at any time and order during the Activities Phase. Attacks are never required. Each Attack involves only one “defending hex” which must contain an enemy unit which can be attacked. The defending hex must be within an OBJ Zone, but Attacks are not restricted by Command Radius.

5.1b Attack Sequence

Attacker declares the Attack and identifies the defending hex.
Defender announces if he can apply Prepared Defense.
Defender identifies his Action Rating unit.
Attacker identifies the Attack and any Assist units.
Attacker executes any Barrage.
Determine the net Combat Table DRM.
Roll on the Combat Table.
Apply the results (Losses, Retreats, Advances).

5.1c Attack Unit Requirements. All Attack units must:

✔ Provide the Attack’s Action Rating.
✔ Be adjacent to the defending hex.
✔ Be able to enter the defender’s hex in regular movement.
✔ Not be FINISHED.
✔ Not be Over-Stacked.
✔ Be used to determine Attacking DRMs.
✔ Have an MA greater than 0.

5.1d Barrages in an Attack. The attacker can select one of two kinds of Barrage using available Arty/Air Points to support his Attack. The Formation HQ’s Command Radius does not restrict Barrage. A Suppression Barrage generates a +2 DRM in a Regular Attack, or +1 DRM in a Shock Attack. In neither case does the Suppression Barrage cause any step losses. A Destruction Barrage can cause step losses from the Barrage Table, but gives no Suppression DRM. If a Destruction Barrage destroys the defending stack, execute Advance after Combat and the attack ends without rolling on the Combat Table (but still FINISHES all involved units). For Fatigue roll purposes, the Attack did occur.

5.1e Combat Table DRMs. Each side determines its Net Action Rating by adding the applicable Combat Table DRMs to their chosen unit’s AR. Subtract the defender’s Net Action Rating from the attacker’s Net Action Rating to find the final DRM. Use the terrain in the defender’s hex and any hexside terrain the Attack unit is crossing to make the attack. For the Defender to use his Second Unit DRM, he must have exactly two Combat units in his hex.

5.1f Combat Table Results. Roll two dice, add the final DRM, and read the result on the Combat Table. Results include Losses, Retreats, and Traffic. Only the Attack unit can absorb Attacker losses. If it cannot absorb all of them, ignore the excess. Losses cannot be applied to Support or Assist units. The defender must inflict the first loss on his AR unit and then distribute remaining losses to other real units within his hex, as desired. Place any resulting Traffic marker in the defender’s hex if his stack either retreats or is destroyed (otherwise ignore it). Retreat results affect all the units in the defending hex.

5.1g Regular Attacks Only. A hex can only be targeted by a single Regular Attack in a single phase. But if the enemy units retreat to a new hex, they could be attacked again (by different Attacking units).

5.1h Regular Attack Criteria. The Attack Unit must apply the “All Attack Units” list in 5.1c and must be Attack- Capable.

An Attack Unit could be STOPPED.

5.1i “Assist” Units. You can assign an “Assist” for your Attack, if you wish. An Assist gives that Attack a DRM. The Unit Capabilities Chart shows which unit types can Assist. You may select no more than one unit as an Assist.

An Assist must:

✔ Be Attack-Capable or have an AV showing.
✔ Be adjacent to the defender’s hex.
✔ Be adjacent to, or stacked with, the Attack unit.
✔ Not be over-stacked.
✔ Not be FINISHED, but can be STOPPED.

An Assist unit can Advance after Combat only if stacked with the Attack unit, and not from other locations. It can only Advance after Combat if it is capable of entering the defender’s hex in normal Movement.

5.1j Ending a Regular Attack. Regardless of any Advance After Combat, units that Attack or Assist are FINISHED.

5.1k Shock Attack Only. You can Shock Attack a hex as many times in an Activity Phase as you can manage (even with the same unit) in addition to other Attack or Barrage types—and in any desired order.

5.1m Shock Attack Criteria.

i) A Shock Attack defending hex must:

✔ Not contain any AV rating (real or Support).
✔ Cost 3 MPs or less for Tac MA (road MP rates can be used to reduce the hex’s terrain costs).

ii) The defender’s hex could contain a STOP (if using a road rate to pass the 3 MP test). That STOP applies after the unit successfully advances into that hex.

No, the unit need not pay this amount. The hex merely needs to cost that much or less.

iii) A Shock Attack unit must:

✔ Follow the “All Attacks” list in 5.1c.
✔ Be a single unit.
✔ Have at least one MP & one Fire Event remaining.
✔ Not be under a STOP.
✔ Have a Tac MA and be “Shock Attack- Capable” on the Unit Capabilities Chart.
✔ Show one or more of the following:
Attack-Capability.
Red AV.
Light AV.
Breakthrough Armor.

5.1n Other Shock Attack Special Rules. i) Shock Attacks cannot use Assists.

ii) A Shock Attack costs one Fire Event.

iii) Shock Attacks do not FINISH the attacking unit.

iv) Shock Attacks can never use more than one Arty or Air Point for barrage.

v) To obtain the “Attack by Fire DRM,” the Attack by Fire must come from the Attack unit itself and leave another Fire Event available for the Shock Attack. The Attack by Fire accrues the DRM even if it generates no loss.

5.1o Ending a Shock Attack. The Attack unit can continue to move using its remaining MA if not STOPPED (for any reason, including running out of Fire Events by doing the attack).

i) Continue movement, if any, from the unit’s current hex (be it with or without the “free” move of an Advance after Combat). Once beginning to move again, EZOCs and Stopping Engagements apply normally.

ii) If the attack fails to dislodge the Defender and the Attacker still has MA and a Fire Event remaining—it can move or even try another Shock Attack against the same hex again.

iii) Regardless, all the DRMs involved in the earlier attack are reset to zero. A new Shock Attack, even against the same target, must provide its own DRMs.

Design Note: Yes, this all means that a unit could make a successful Shock Attack against a hex, Advance after Combat into it, and thereby ‘move into the hex for free.’ Remember, they are hustling at the time and the world is not as black and white as a unit’s MA might indicate.

Example: Shock Attack

Here the Prep Def and Support for the 99 ID is arrayed nearby for visibility in the example. OBJ Zones as needed are assumed.

In the first example, the German Panzer unit 1,2/I moves into 36.22 and wishes to do a Shock Attack on the 99 ID Unit B. It cannot do one against Unit A because the terrain MP cost (4 for the STOP Terrain) is too high, but the road heading south into 36.21 allows such an attack. However, before this is possible, the Panzer unit must eliminate the STOP requirement created by the Support AV EZOC from Unit A and drop the Support from Unit B to allow the attack at all.

This, of course, is beyond the abilities of the German unit. It can try to Drop the Support from both US units, but in doing so it will be STOPPED for the Activation and out of Fire Events—unable to make any Shock Attack.

In the other example, Spitze is going to do a Shock Attack against Unit C. Here there is no Support or Prep Def as the Engineer is Unprepared and in a Village (which is not Key Terrain in case a Situational Result comes up).

As a result, both of Spitze’s Fire Events are available. The player decides to do an Attack by Fire so as to obtain the extra +1 on the Combat Table.

Spitze attacks with a 5 (AR), +1 (Dual), +1 (Attack by Fire), and +1 for Suppression (Arty) for an 8. The Engineer defends with a 2 (AR), +1 (Terrain) for a 3. The Shock Attack has a net +5 DRM. Here the German player rolls a 6 which is modified to an 11. The Engineer takes the D1. It must Retreat. However, as the unit has no printed MA, 5.5i applies and the unit is automatically destroyed.

Spitze enters the hex at no MP cost, but cannot continue to move as it has used all its Fire Events and is STOPPED.

BCS 5.2 Engagements

Engagements represent AV armed units exchanging fires. Only the Active player initiates Engagements. Resolve them on the Engagement Table.

Engagements can only be initiated against enemy AV units or Support. If an AV unit wishes to fire on a stack without any AV, use Attack by Fire instead.

5.2a Engagement Firers. i) A qualified Active AV unit, which is not in Support, can execute an Engagement by firing on a single enemy AV unit target in its Range.

The limitations on this range (the range’s maximum value, the effect of terrain in 5.2b part iv), visibility and Blocking Terrain) restricts how far away a target can be Engaged.

The Firer’s Range affects:

If the Target can be Engaged at all.

The Target’s Range affects:

If the Firer can take losses at all. (5.2d part iv)
If the Target can use the Multiple Support DRM. (5.2d part iii)

If the Target is a Support unit, measure the Target’s Range on the Support’s counter from the Host back to the Firer.

ii) Engagements require the expenditure of one Fire Event each, but do not cost MPs. If a unit no longer has a Fire Event available, it cannot initiate an Engagement.

iii) A unit can initiate an Engagement at any point in movement (including before it moves), and is free to move afterwards if this wasn’t its last Fire Event.

iv) EZOCs do not affect a unit’s ability to Engage.

v) There is no need for the Firer to be able to enter the Target's hex in any way nor is there ever an Advance After Combat after any Engagement, no matter what the results.

5.2b Engagement Targets. i) Engagements do not require the target to be in an OBJ Zone, but the Target must be inside a Double OBJ Zone to apply the Double OBJ DRM.

ii) The Inactive player selects the unit in the Target hex to be the Target of the Firer’s Engagement into that hex.

Choose the Target unit with the greatest AV and/or Range, in the following priority order:

Real AV Unit.
Support AV using a Host from a Formation with multiple Support units.
Support AV using a Host from a Formation with only one Support unit.

iii) A given target unit can be Engaged any number of times in a phase.

iv) If the Target’s hex contains “Terrain” or the Target itself is in Prepared Defense, the maximum Engagement range is reduced to 1 hex.

5.2c Special Cases. i) Light AV and Screen units cannot be Engagement Firers, but can be Engagement Targets.

ii) Support can only be Engagement Targets.

iii) If the Target is a Screen unit, convert a “Both Loss” result into “No Losses, Target Retreats 3 hexes” against it.

5.2d Engagement Table & Results. Resolve Engagements by rolling two dice on the Engagement Table, adding any applicable modifiers.

i) There are two sections in the Engagement Table: Use the top one if the Target is Real AV and the bottom one if the Target is Support. The numbers shown are the modified two dice rolls. Use the result in the same column above the modified roll made.

ii) Support uses the Host’s Action Rating to compute the Target’s Base Differential modifier (Support AV + Host unit's AR). Real AV units use their own Action Rating.

iii) The “Multiple Support” DRM applies only in a shot against Support when the Targeted Formation (not hex) has more than one Support unit and the range of each reaches into Firer’s hex.

iv) Apply the result to the side or sides indicated. However, ignore all Firer results if the Firer is outside the Target’s range.

v) Place any resulting Traffic marker in the Firer’s hex.

5.2e Engagement Results and Support units. i) Never apply losses to a Support Host, only to the Support unit itself.

ii) A Target Drop result Drops Support from every unit in the stack, even if its own Support didn’t participate.

5.2f [Optional] In any Engagement at a range greater than 1 hex, convert any “Both Loss” result into “No Effect.”

Example: Engagement

In this example, Visibility is greater than 2 hexes.

TF Harper has moved into the hex shown and has not yet expended a Fire Event. Visibility allows it to ‘see’ both German units, but Unit A cannot be Engaged from a range greater than 1 hex due to terrain.

TF Harper will Engage German Unit B. No DRMs apply, so this is a -1 shot (Harper is a 6 (AV + AR) and the German is a 7).

This is resolved on “Real AV” Engagement Table section as II/16 is a Real—not Support—AV unit.

Firing at range 2 is a smart move, as there is no risk of Firer loss while out of range of the German tanks.

Harper’s first shot rolls a modified 5 which would have been a Firer Loss & Traffic, but due to the Range both are ignored, leading to a No Result.

The next roll is a modified 7. Range converts a ‘Both Loss’ Result to a Step Loss for the Germans, but no loss to Harper. ‘Both Loss’ has no Retreat result.

Having expended both Fire Events, TF Harper is now STOPPED for the Activation, which is effectively the same as being FINISHED.

Example: Dropping Support

This example looks at the options involved when taking down Support. This is the 116 Pz Activation. The Player’s ‘mission’ is to take the bridge in the NW corner (34.06), provided the bridge isn’t blown if the Germans get that far.

He must Drop the US Mixed Inf Bn’s Support so as to do Attacks by Fire or Shock Attacks. I/16 Pz Bn makes a 9 vs 6 (+3) Engagement. Rolling an 8, the Support Drops and the AT (not the Host unit) suffers a Step Loss.

I/16 Pz Bn must complete its movement (or use its remaining Fire Event) before moving some other unit. It makes an Attack by Fire, which requires a roll of 5-6 (the target is in Terrain & Prep Def using the Attack by Fire column). The player rolls a 2 and misses. I/16 is STOPPED. It cannot do a regular Attack and is unlikely to Assist one.

The player will have II/16 Attack by Fire and then KG Stephan will Shock Attack. The two Attacks by Fire (5-6 again) score one hit (6) and one miss (3). The Mixed Inf Bn has one step remaining and no Support.

KG Stephan moves to 37.04. Technically, it could do an Attack by Fire before the Shock Attack to generate a +1 DRM, but doing so would preclude taking the bridge at 34.06.

It does a Shock Attack without the preceding Attack by Fire. Using artillery, the attack is a 5, +1 Suppression, +1 for Dual. The defense is a 2, +1 for Terrain, and +1 for Prep Def. 7 to 4 or +3. A roll of a 6 kills the remaining step (because of the Situational Retreat), inflicts a step loss on Stephan because of the Prepared Defense, and places a Traffic marker in the hex, precluding Stephan’s attempt to possibly capture the bridge.

Play Note: For those used to earlier editions of these rules, how Stand Off Support (“88s”) is used may be confusing. When deployed as a Real AV unit (meaning not in Support), the 88s have the same two Fire Events, an Engagement Zone to Engage as a Firer out to their Range, ability to Attack by Fire, and an AV ZOC. In Support, they lose these things except the ability to be Engaged as a Target and the AV ZOC for their Hosts. They also apply a Required Stopping Engagement to any enemy AV units that enter those AV ZOCs.

BCS 5.3 Attack by Fire

Attack by Fire allows AV units to attack non-AV units. Effectively, the AV unit is shelling the enemy with HE rounds. Attack by Fire is resolved using the Barrage Table, and counts as one Fire Event.

Design Note: AV units fire on other AV units using the Engagement Table, but they fire on non- AV units using the Barrage Table in the form of Attacks by Fire. The difference here comes from how the combat is being fought. Obviously, AV vs. AV is a contest of machines while AV vs. non-AV represents something more akin to shelling (like a Barrage) the target unit’s position.

5.3a Any number of Attacks by Fire can be made against a given hex. Attack by Fires can be made in any sequence, before or after any Attacks.

5.3b Attack by Fire Requirements.

✔ The Firer is adjacent to the target.
✔ The Target contains no AV (Real or Support).
✔ The Target is in an OBJ Zone.
✔ The Firer could be STOPPED but is not FINISHED.

5.3c Firing Unit Requirements.

✔ Each Attack by Fire is made by a single unit.
✔ Only unit types listed on the Unit Capabilities Chart can conduct Attacks by Fire.
✔ The firing unit must win any required Stopping Engagement before making an Attack by Fire.

5.3d Procedure. Resolve Attacks by Fire exactly like a one Arty/Air Point Barrage, using the Attack by Fire column on the Barrage Table. Every Attack by Fire is resolved individually; they are never combined, nor can they ever be combined with Arty/Air Points to create larger Barrages.

5.3e Attack by Fire as Suppression. Attacks by Fire never qualify as a Suppression barrage for a Regular Attack, but could apply as a similar DRM to a Shock Attack by that same unit immediately following its Attack by Fire. Such an Attack by Fire “Suppression” can only affect that one Shock Attack, but could be in addition to the actual Suppression DRM (+1) from Arty/Air Points.

Example: Attack by Fire

560 VG unit Support displayed for example purposes. An OBJ Zone includes the German unit.

Here, Harper will move into 27.32 adjacent to the VG unit. As the US player wants to hit the German unit multiple times with Attack by Fires, he must Drop the Support. The shot on the Support is a -1 on the Target is Support section of the Engagement Table. A roll of 8 Drops the Support.

Harper has used one of its Fire Events.

The player wants to block the road by moving into 27.31, so Harper cannot expend its second Fire Event from there as an Attack by Fire as it will not be adjacent. Staying adjacent to do so would make it STOPPED in 27.32.

At this point, TF Rose has moved into firing position with both Fire Events available (the Support that was Dropped by Harper remains Dropped for the rest of the Activation). The German unit is in Terrain (a village).

Rose makes both shots and is now STOPPED in that hex. The rolls of 4 and 6 equate to one Step Loss on the German VG unit. Note that the 4 missed because the Barrage Table’s Attack by Fire column (unlike the Artillery column) requires a 5-6 to hit.

BCS 5.4 Barrage

Barrages come in two basic forms: Destruction and Suppression.

Destruction Barrages are designed to inflict losses on the enemy. They do so using the Barrage Table and can use up to three Arty or Air Points in a single Barrage. Roll one die for each Point expended per target unit (not per stack) to determine losses.

Suppression Barrages inflict no loss, but improve your combats by allowing a positive DRM. Effectively, they force the enemy’s head down and allow your assault forces to advance to very close range before the defense can regroup.

5.4a A Formation’s associated Arty Points can be used at any point during that Formation’s Activation to execute a Barrage, but each Arty Point can only be used once per phase. The Formation’s total is refreshed in each Activity Phase, including in a Formation’s Second Activation if any. Unused Arty Points cannot be saved for later use. SNAFU results can affect the number of Arty Points a Formation might have available.

5.4b An HQ can be assigned any number of Arty Points in addition to its printed “intrinsic” Arty Points. While the printed intrinsic Arty Points never change, the player can assign or unassign the other Arty Points as desired in the Assignment Phase. Once assigned, only that Formation can use them until they are re-assigned elsewhere. Use of an assigned Arty Point does not remove it. It is refreshed each Activity Phase just like Intrinsic Arty Points are.

5.4c You could also be issued Air Points representing available aircraft strikes. Air Points follow the same handling rules as Arty Points, except you do not assign Air Points to specific HQs; they are kept in a pool available for their side. They can be used in any friendly Activation. Each Air Point can only be used once in a given turn and are not “refreshed” like Arty Points. Unused Air Points cannot be saved and used later. SNAFU results do not affect Air Points.

Example: Artillery Barrage

Here several situations will be explained, all of which assume the needed OBJ Zones. It is the German Player’s Activation.

He wishes to Barrage the three stacks of US units. These are the options that are available: He can fire one Arty Point at the hex as a Destruction Mission and make no Attack, he can Attack and then use one Arty Point as a Suppression Mission, or he can Attack and use 1, 2, or 3 Arty Points as a Destruction Mission. He can only attack one of the three hexes with the Assist DRM for the second German unit, so the other two can only get a single Point Destruction Barrage each (he could use the two German units separately and attack two hexes, but would then forgo any Assist DRM).

If the Suppression Mission option is chosen, there is no roll for Step Losses, but the +2 DRM for Suppression helping the attack is automatic.

For example purposes here, the player is going to Attack the 1/38 Inf Bn’s hex and is firing 3 Arty Points at the hex in a Destruction Mission. This gives three chances for a step kill, but no CRT DRM.

In Terrain, the roll on the Barrage Table to generate a Step Loss is 4-6. Because there are 3 Arty Points being used, this Barrage will take 6 rolls of one die to execute (3 on each unit in the target hex).

The German Player rolls 1, 6, and 2 against the top US unit for one Step Loss. He then rolls 4, 6, and 2 against the bottom US unit for two Step Losses.

These losses are marked on the two US units and the Attack Sequence continues onto the Combat Table itself. Note that in spite of the large amount of Artillery poured onto the target there is no DRM for Suppression in this case.

Either before or after executing the Attack and its Barrages, the German player fires his Arty Point at each of the other two hexes (one of which is a double stack). This obtains one extra loss. The German player has used 5 of his 6 Arty Points, but has no further targets to use. The last point is wasted.

5.4d A hex can be subject to only one Destruction Barrage OR Suppression Barrage per Activation. Attacks by Fire are not restricted by this rule. You must declare the number of Arty/Air Points to be used before rolling.

5.4e Make any desired Barrages before, during, and/or after any unit’s movement, provided:

✔ There is a qualified Spotter (1.4d & 5.4f) of the active Formation available.
✔ The target hex must be in an OBJ Zone.
✔ If the Barrage is not part of an Attack Sequence, the Spotter must STOP.

5.4f Spotting. All Barrages (of either type) must be Spotted by a unit that began the Activity Phase in Command Radius and which is:

✔ No more than 4 hexes away (or the game specific Visibility, whichever is less) from the target.
✔ It is assigned to the Active Formation, including its HQ and Combat Trains. Combat Trains are exempt from the Command Radius requirement above.
✔ On a line to the target with no Blocking Terrain for Line of Sight. (4.5c)
✔ In any status: Unused, STOPPED or even FINISHED.

5.4g Suppression Barrages. A Suppression Barrage made during a regular Attack automatically earns a +2 DRM. Suppression barrages only use one Arty/Air Point and never generate a loss roll. Shock Attack Suppression only obtains a +1 DRM using an Arty or Air Point. No Barrage made outside an Attack (either type) applies any Suppression effect.

5.4h Destruction Barrages. Resolve Destruction barrages on the Barrage Table using its Arty column. For each Arty/Air Point expended, roll one die for each unit in the targeted hex. Do not roll for Support. (1.5f)

For example, if you fire three Arty Points at a hex with a stack of two units, you will make a total of six die rolls, with three rolls against each of the units in the target hex.

i) Use the row designated by terrain and/or target type (using the lowest casualty rate row that applies). The results for each roll will be either no effect or a Step Loss (losses come from the unit being rolled against at that moment).

ii) The number of Arty/Air Points that can be used in a Destruction barrage varies according to the situation:

Up to three Points as part of a Regular Attack.
One Point as part of a Shock Attack.
One Point when not part of any Attack.

iii) Destruction barrages never apply a DRM to any Attack.

BCS 5.5 Retreats

Both the Combat and Engagement Tables produce Retreat results. There are a few types of “Retreat.” Only the Combat Table produces “Situational Retreats” (5.5d) which may allow the units to stand fast at a cost in Step Losses, and “Automatic Retreats” (5.5e) involving units regrouping back at the HQ now or in the next turn. All Engagement Table Retreat results (unless modified by another rule) and some Combat Table Retreat results merely require a Stack to retreat 3 hexes and flip to its Move-Side.

To determine the manner and type of a Retreat a unit must execute, follow the Retreat Execution Chart to apply the needed conditions.

Retreats are unaffected by Engagement and Screen Zones. Exceptions: HQ requirement 4.5a and the changes in the result against Screen Zone units 4.6b.

Retreats are generally unaffected by Terrain, enemy units, or EZOCs, except in the retreat’s ending hex and if No Safe Path applies (5.5c). The retreat itself has no “Path” and the unit will arrive at the ending hex via routes and abilities below the level of the game—remember, the game’s perfect arrangement of units on a grid does not imply such perfection also exists in real life.

Example: Yes, even THIS!

Life is never as clean, well-timed, and orderly as it looks on the map. The Cav does escape.

5.5a Retreat to the Rear. The owner retreats his units “locally to the rear.” Simply pick up the stack and place it in the new hex. Apply these guidelines to help determine the retreating stack’s final location. They are arranged in priority order. If more than one hex is roughly as qualified, the owner decides.

5.5b Retreat Direction Guidelines. Try to end a retreat in a hex based on the following guidelines (in order of importance):

Away from the local enemy units (esp. the Attack or Firer units).
Free from EZOCs.
Containing a permissible terrain type.
Better suited for defense.
Closer to the unit’s HQ.
Not Blocking enemy Safe Paths or MSRs.
Closer to the Combat Trains.
Closer to the Formation’s last Supply Source (if the Formation does not have a Complete MSR).

Your retreat should try to fulfill as many of these guidelines as possible.

HQs and Combat Trains retreat according to the guidelines above and 4.7e & 4.7h only when an enemy unit enters their hex (4.7d)—such as in an Advance after Combat (5.6d) after the other units in their hex must execute a Retreat Result or are destroyed.

5.5c No Safe Path. Always apply any listed Step Loss result first and then the following if No Safe Path exists.

If there is no Retreat result, you are done.
If there is a Retreat result and the units are Leg or Truck MA, each unit suffers one additional Step Loss and ignores the actual Retreat result.
Tac MA units and units conducting Voluntary Retreats are unaffected by No Safe Path concerns.

5.5d Situational Retreats. Given that 5.5c does not apply, units with this Combat Table result will Retreat 3 hexes and flip to their Move-side, or (if in Key Terrain or Prepared Defense) make no Retreat but each unit in the Defender’s stack must take one Step Loss.

If the Attack unit is killed in the Combat result, ignore any Situational Retreat result completely, regardless of how it ‘would’ have been executed.

5.5e Automatic Retreats. Given that 5.5c does not apply, Leg and Truck MA units with this Combat Table result must Retreat to its HQ if it qualifies as an “HQ Refuge” and flip to their Move-sides.

To have an HQ Refuge, the HQ must have a location where units can end their Retreat in or adjacent to their HQ’s hex, and this ending hex must be 3 hexes (or more) from the Retreat’s starting hex.

If its HQ Refuge is unavailable, remove the retreating units from play. They return in the next turn’s Reinforcement Phase to any hex in or adjacent to their HQ (regardless of the MSR being Complete or not). Return them on their Move-side.

Automatic Retreat results for Tac MA and unassigned Independent units are always 3 hexes and a flip to Move-side, but never require sending the unit to its HQ or removal from the map.

5.5f Retreat the Whole Stack. Retreats involve all the Combat Units in a hex. Combat Units typically retreat together to a common hex (see Play Note). If a hex contains both AV and non-AV units, the applicable Engagement Table or Combat Table result determines the retreat applicable to the entire stack, but evaluate each unit’s Safe Path effect separately based on its own MA. If a hex contains both units and HQs/Combat Trains, retreat the units first, and then apply the HQs/Combat Trains rules separately (4.7d, 4.7e & 4.7h).

Play Note: A hex containing both Leg MA and Tac MA units could get an Automatic Retreat result. The Leg MA units would go to (or adjacent to) their HQ while the Tac MA units merely Retreat 3 hexes. As a result, there might be two ending hexes, because of the two applicable sets of Retreat instructions.

A similar type of situation can occur when Safe Path or Situational Retreats apply to the units in a hex differently. Apply the above to each unit’s specific requirements.

Retreat (example). Here fires from Spitze have forced the 32 Cav to Retreat. Because this is from the Engagement Table, the Retreat is automatically 3 hexes and a flip to Move-side. The flip does not occur as the unit is already on its Move-side. Furthermore, the lack of a Safe Path does not matter as the unit is Tac MA. The most logical retreat point is to Hex F. It is away from the local enemy, in terrain, toward the HQ, and is on a road leading to the HQ the enemy could use.

A and B are both bad because they are in AV EZOCs.
C and D are not locally away from the enemy and are not closer to the HQ.
E and G are not unreasonable, but are not as useful to the player as F.
H is a possibility, but risks blocking an enemy MSR on the nearby Secondary Road and would be ruled out if that was the case.

5.5g The Ending Hex. A retreat’s ending hex cannot contain an enemy unit or be terrain the Move-side retreating stack could not enter during movement. If this causes a stack to be unable to retreat, the stack takes an extra step loss per unit and stays in the hex instead.

Each applicable unit takes one Step Loss if their retreat’s ending hex contains an EZOC that applies to the retreating unit’s MA Type:

All EZOCs affect Leg and Truck MA units.
Only Real AV EZOCs affect Tac MA units.

Tac MA units ignore all Support AV EZOCs and non-AV EZOCs.

5.5h The Map Edge. Units may freely retreat off the map edge. Such units come back as reinforcements the next turn in any friendly “controlled” Entry Area (owner’s choice) along that same map edge.

A player “controls” an Entry Area hex if his units occupy or were the last to move through that hex or can reasonably be assumed to have done so before play began.

5.5i Units without an MA. A unit with no printed MA which is forced to retreat, is destroyed instead.

BCS 5.6 Advance After Combat

5.6a If the defending stack in a Regular or Shock Attack retreats or is destroyed, the Attack unit must advance into the defender’s hex. This “Advance after Combat” does not cost MPs, ignores Command Radius, EZOCs, and does not incur Stopping Engagements. A unit can create Mixed Formations as the result of an Advance After Combat.

5.6b Assist Units. Assists can Advance after Combat if they were stacked with the Attack unit. Assist units in other locations cannot advance. Even if an advance is allowed, it is an option to an Assist. It is never mandatory as is the case with the Attack unit.

5.6c Command Radius. While Command Radius does not restrict any Advance after Combat, exiting Command Radius will still subject a unit to Isolation effects.

5.6d HQs & Combat Trains. Advance After Combat could cause enemy HQs and/or Combat Trains to be Jumped when the advancing enemy unit(s) enters their hex. (4.7d)

BCS 6.0 Odd Situations

BCS 6.1 Urban Warfare

Urban fighting is a slow, exhausting, process where the two sides expend themselves clearing the enemy out of city blocks room-by-room and floor-by-floor. Urban warfare requires special treatment.

Design Note: In a nutshell, Urban Warfare revolves around wresting Control of enemy hexes and increasing the Control of your own. If you just sit passively and absorb attacks, the enemy will win; you must be actively trying to reclaim any territory he takes. The Control marker system exists to make clearing Urban terrain take more time than the usual open field fighting. But, just because it moves slowly, doesn’t mean you can avoid participating in the back and forth.

These rules only apply to Urban hexes and never to the more common City hexes. Panzers Last Stand is the first BCS game to feature actual Urban hexes.

6.1a How Urban Warfare Works. Losses change a hex’s “Control” status until forcing a Withdrawal, leaving the hex unoccupied. The first side entering an empty hex will then Control it. Control moves back and forth depending on both side’s results over time.

Only occupied Urban hexes are Controlled. Neither player controls any empty Urban hex, regardless of where this hex is located or what units “used” to be there.

Control is on a continuum and can change in either direction. Hexes can be either “Fully” or “Partially” Controlled. A “Control marker” designates Partially Controlled hexes as listed to the left.

Urban Control?	How Marked?
None	Nothing, no marker, no units from either side.
Total Friendly	Friendly units, no marker.
Partial Friendly	Friendly units, Friendly Partial Control marker.
Partial Enemy	Friendly units, Enemy Partial Control marker.
Withdrawal	Friendly units Withdraw, Remove the Control marker, No Advance After Combat.

A hex can only obtain a “None” Control when its units have exited or are destroyed.

If a Withdrawal vacates a hex, remove its Control marker. The first Active unit to move into such a hex will establish Total Friendly Control of it. In contrast, for an empty hex from unit destruction, see 6.1c part iv).

6.1b Standard Rules Exceptions. Normal BCS rules apply to Urban hexes, except for the following:

i) Retreats. Apply all Retreat Results as “No Retreat” (regardless of retreat Type or Table) if the unit involved is in an Urban hex.

ii) No Advance after Combat. Units never Advance after Combat into or out of an Urban hex, regardless if the defending unit(s) are destroyed or Withdraw. See also 6.1c part iv).

iii) Barrages per hex. Instead of only one Barrage per hex per Activation, any Urban hex can be subject to up to one Destruction plus any number of Suppression Barrages.

iv) Attacks per hex. An Urban hex can be Attacked on the Combat Table any number of times in an Activation.

v) Singletons. If a single unit (regardless of its number of Steps) defends an Urban hex, its Attacker applies an additional +2 DRM.

6.1c Hex Control Special Cases. i) It is possible for both the Attacking and Defending hexes in a combat to have Control markers in their respective Urban hexes, but a single hex can never contain more than one.

ii) If Active units abandon a hex containing a Control marker, the marker remains until play moves on to a new Formation. If your units re-enter the orphaned marker’s hex before then, they inherit the marker.

Design Note: The timing here matters. Otherwise it would be possible to exit a hex, remove its Control marker, then move that unit or some other back into the hex. And that movement could happen in a later Second Activation as well. If the enemy gets an Activation before you can do this, then at least they had a chance to occupy the hex before your little trick was finished and possibly you gave him that hex for free. Don’t say you wouldn’t do it, because you know you or someone playing against you would do exactly that.

iii) If no enemy AV or Attack-Capable unit remains adjacent to a Control marker’s hex, remove it immediately.

iv) If Inactive units are destroyed leaving a hex vacant, the Active units adjacent to it enter and “claim the hex” (even if no attack was being made). The newly acquired hex will have its Control level shifted by 1 in the Active player’s favor as per the following example. The Active player must advance at least one adjacent unit into the hex, but can advance more than one if he prefers.

An Attack by Fire generates a Step Loss, killing a Soviet unit and leaving the hex empty. The Axis player selects his choice of Active units (in any status) adjacent to this hex to advance into it, provided he advances at least one of them.

The new Axis hex gets a Control marker based on whichever of the following was true for the original Soviet unit:

Original Situation	Result
No Control marker	Partial Soviet Control
Partial Sov. Control	Partial Axis Control
Partial Axis Control	Full Axis Control (No marker)

6.1d Hex Control Changes. In addition to normal Step Losses, each Step Loss in an Activation, regardless of how inflicted, causes one Control level change to a hex. Loss results giving more than one Step Loss (e.g. a Barrage that causes two step losses) apply one Control change level for each Step Loss inflicted. Apply all Control Changes after all parts of an Attack on a hex have been completed.

Losses to the Attacker have no effect on Control Level change.

For example, if a hex absorbs two losses from a pre-attack Barrage, and the attack’s Combat Table result gives a defender loss, three levels of Control Change occur (but are constrained by the maximum of three available changes that can apply to one hex).

This could be either from Total Friendly Control to Partial Friendly Control to Partial Enemy Control, or Partial Friendly Control to Partial Enemy Control to Withdrawal as the case might be.

If all three levels of Control change cannot be used on the one hex, any excess is lost.

6.1e Control Change Decisions. The Active player determines which hex applies a Control Change separately for each Loss. The hex selected must be either the hex that took the Loss result OR the hex containing the Attack unit or Firer. The stack containing an Assist (unless it also contains the Attack unit) cannot apply any Control Change. Execute these at the moment Loss results occur.

The player can change Control over his own Urban hex by applying a Control change for a loss that stack inflicted on an enemy occupied hex (even one that is not itself Urban).

6.1f Withdrawal. When a hex’s Control moves from enemy Partial Control to Withdrawal, execute the following.

Withdrawing units must:

✔ Move one hex into a hex free of any enemy units. If no such hex exists, destroy the Withdrawing units.
✔ Flip to their Move-side(s).

EZOCs have no effect on Urban Withdrawal, only enemy-occupied hexes do.

BCS 6.2 Formation Destruction

6.2a When Formation Destruction Applies. If a Formation loses its last non- Support unit ‘in play’ (counting both intrinsic and assigned units), the Formation itself is Destroyed.

Units returning from retreat results and any units reinforcing the Formation on the OOA are ‘in play’ and may affect Formation Destruction (see 6.2c).

6.2b Handling the Formation’s Units. Pull the following from play (after noting the effect of “Reinforcements Arriving at the HQ” in 6.2d):

HQ.
Support units, regardless if they could be Real or not, intrinsic or assigned.
Combat Trains.
The Formation’s Dead units retain any “Partial Rebuilding” that has occurred in case 6.2c applies later.
Assigned Arty Points become unassigned and are available for a new assignment in the next Assignment Phase.

6.2c Will They Return to Play? The removed Formation and its units return to play (in their original states, except Fatigue, see below) if non-Support-only units belonging to the Formation arrive later via the Order of Arrival or because of Retreat result execution. If this occurs, follow 6.2d when the first such unit arrives. If no units arrive later, the Formation is eliminated permanently.

6.2d Return to Play with Reinforcements. The HQ returns as Fat-2, regardless of what it had when removed. Dead units return to the Dead Pile in their original states (but with any partial Rebuilds intact). Support units come back with their remaining steps intact.

The HQ, the Combat Trains, and the arriving Dead and Support units return with the Reinforcements with the following exception:

If the Reinforcements are listed as “arriving at the HQ” the HQ, Support and Combat Trains stay on the map rather than getting pulled off as in 6.2b. While in that status, the Formation must still activate normally.

BCS 6.3 Attacks From Off-Map

If enemy units occupy a friendly Entry Area hex, your units can still try to enter using an “Attack from Off-Map.” For purposes of this rule, you are assumed to be the player attempting entry. If you are defending from such an attack, remember to change the references from “your units” to “his units” and so on.

Design Note: Obviously, the ‘problem’ with map edge hexes is that players use them as literally the end of the world. The above rule allows the entering units to take advantage of the fact that not only does the world NOT end right there, but there are lots of units as well as space to operate that is outside the normal scope of play. So, if you don’t want to deal with the dragons just off map, then back up to allow the normal use of the Entry Hex. Basically, ‘Attacks from Off Map’ temporarily extend the map one additional hex out from the map edge and gives a couple of benefits (Full SNAFU and the +2 DRM) to help the reinforcements get into normal play. And, no, the enemy player cannot also try to occupy that off-map hex!

6.3a You are considered to have a virtual Off-Map ‘hex’ adjacent to his unit occupying your Entry Area hex. This ‘hex’ is assumed to contain the same type of roads as the Entry Area hex itself. Both your Attack unit and Assist units (if any) are assumed to be in this ‘hex.’ Your units can Attack from that ‘hex,’ but the enemy cannot attack or barrage your units while they are in it. There is no hexside feature between your hex and the map.

6.3b The units needing to make the above attack are assumed to have a Full SNAFU result. There is no need to roll for it. If the rest of their Formation is On-Map, handle their SNAFU normally, but the Off-Map units still have their assumed Full SNAFU.

6.3c Only Regular Attacks are allowed from Off-Map. Off-Map Attacks obtain a +2 DRM on the Combat Table.

Shock Attacks, Engagements, Attack by Fires, and non-Attack Barrages are not allowed from Off-Map.

Exception: The player can make use of a Barrage as part of his Regular Attack.

6.3d Once the units are back on the map, all normal rules again apply. If the attack fails and the units do not enter the map, they remain off-map as per 2.1d part iii and can try again in their next Activation.

BCS 6.4 [Optional] Planned Fatigue

This is a series of interrelated concepts first proposed by Jim Stravers. You should use the entire package, if used at all, and only after you feel fully grounded in the standard system.

6.4a Fatigue SNAFU DRMs. Only use:

Fresh: +1
Fat-4: -1
The others are all +0.

6.4b Fatigue Increase. Do not use the Fatigue Increase Table or make any die roll. Instead, you ‘pay’ Fatigue to purchase the following:

Fatigue Increase	Action
1	Place an extra non-Recon OBJ.*
1	Place any OBJ more than 15 hexes from the HQ.*
1	Remove one Traffic marker.**
2	Conduct a Forced March.
1	Use a Second Activation DRM of +2.

OBJs can only be created in the usual time in the sequence. If you create an extra non- Recon OBJ that is also more than 15 hexes away from the HQ, the Fatigue cost for both is only 1 Level.

Both the OBJ cost (*) and Traffic marker removal (**) can be done more than once in an Activation; pay separately each time (e.g. removing two Traffic markers will generate a cost of 2).

Traffic marker removal at the end of the Activity Phase is free.

6.4c Fatigue Level-4. Fat-4 effects apply instantly when a Formation obtains a Fat-4 marker (even during the current activation). Fatigue Recovery is required if the Formation is Fat-4 when an Initial Activation begins.

Fat-4 Formations cannot ‘pay Fatigue’ for anything.

6.4d SNAFU Results. Full SNAFU results give only one “free” OBJ. Partial and Fail SNAFU results give no “free” OBJs.

6.4e Forced March. After applying SNAFU results, multiply each unit’s MA by 3. The Formation can only do this once in a game-turn and only in an Initial Activation. It requires purchase in 6.4b. No combat operations are allowed. No OBJs are placed, no Fire Events used, no bridges tested, and no units exited for victory purposes. No Second Activation is allowed.

6.4f Fatigue Recovery. Handle Fatigue Recovery normally.

BCS 6.5 [Optional] Stand Off AV vs. Red Support

Players may wish more fidelity in the actions of Stand Off AV units (Deployed or as Support) when defending against Attacks by units with Red AV Support.The additional workload and rare occurrence makes this rule strictly Optional.

It can be confusing given that a Defending Stand Off unit or Host with Stand Off in Support becomes the Firer for a very brief Engagement before the original Attack is Resolved. Don’t confuse Attacker and Firer.

The Engagement happens the instant after announcing the Attack Unit, but before determining the Combat Table DRMs. The Stand Off AV Fires on the Attack Unit’s Support use the “Target is Support” section of the Engagement Table.

The Engagement might Drop Red AV Support at the moment so the Attacker will not get his Support DRM. Apply any Step Loss (to the Firer or Target) normally, except a Firer Step Loss will not Drop any Defender Support (unless the Firer is destroyed after taking the Step Loss). The Attacker’s Support reappears the moment the Attack is completed.

There is no ability to Engage in this way if the Attack unit itself is Dual.

BCS Glossary

(+) or (-) Unit Sizes. These additional symbols in a scenario listing or on the counter show a unit’s historical status as either being augmented or reduced by detachments. They are only for historical information.

Activation. A Single Formation’s activities applying the Activation Sequence of Play (3.0). The current Formation must complete both its Initial and Second Activations (if any) before play can pass to the next enemy Formation. (2.5)

Assembly Hex. The location units exiting Support or newly assigned to a Formation use to “get back onto the map.”

Assigned/Unassigned. Independent units and Arty Points attached (or not attached) to a specific Formation. (2.3)

Attack by Fire. The effect of AV unit fires on non-AV units. While Attacks by Fire use the Barrage Table for resolution, they are not “Barrages” nor restricted by the “one Barrage per target hex” rule. (5.3)

Attack-Capable. Any unit currently showing an ‘Assault Arrow’ on its side. Only Attack-Capable units can Attack on the Combat Table or (provided they have no AV rating) make use of Support. A unit must be Attack-Capable and on its Deployed-side to use its Formation’s Prepared Defense.

AV ZOC. A type of ZOC generated by AV units. They come in two flavors: Real or Support, depending on the AV unit creating it. AV ZOCs affect enemy Tac MA units more than regular ZOCs. (4.3a, 4.3f)

Blob. A Blob is a Formation’s Area of Operations (1.3c)

Blocking Terrain. Terrain that blocks the minimal ‘line of sight’ needed to make Engagements or spot Artillery Fires at ranges greater than 1 hex. (4.5c)

Buddies. Buddies are Formations used to freely working together and avoiding many typical problems. These are identified in the Game Specific Rules. Formations listed as “Buddies” do not apply Coordination, Mixed Formations, or Crossing the Streams to each other. (3.2)

Command Radius (CR). Command Radius is the maximum distance from the HQ a unit can function normally. (1.4)

Combat OBJs. (OBJ) OBJs identify a Formation’s active combat operations area(s). They define OBJ Zones, as defined below. (3.3)

Combat Trains. These are the field logistics establishment of a Formation. They have a regular side and a “Ghost” side of the counter to indicate the status of the Combat Trains.

Combat Unit. A ‘Combat Unit’ is a unit that is not an HQ, Combat Trains, or in Support. No game marker is a Combat Unit.

Complete MSR. A Complete MSR exists if there is a contiguous series of Legal hexes (3.1a) connecting all three of the following (in order) from the HQ through its Combat Trains, and then a friendly Supply Source. (3.1)

Control. The act of wresting an Urban hex’s ownership from the enemy. (6.1a)

Coordination. An effectiveness reduction when coordinating matters with other Formations in their area or allowing coordination between Formations to slip. (3.2c)

Crossing the Streams. A condition when the path between HQ and Combat Trains from more than one Formation must share one or more common hexes. (3.2h)

Deployed-side. If a unit has an MA on each counter side, the Deployed-side has the smaller MA of the two. (1.1c)

Destruction Barrages. Arty or Air Point fires to destroy enemy steps using the Barrage Table. (5.4h)

DRM. Die (or Dice) Roll Modifier. If an event is subject to more than one modifier, the DRMs are cumulative. Exception: If DRMs are presented as an either/or situation, then you can apply only one of the presented options.

Done. A Formation after completing its Activations for the turn. A Formation that is Done can no longer Activate at all. A Formation that sets up Done can do nothing at all on the First Turn.

Double OBJ Zone (aka ‘Double Tap’). The OBJ Zone created by using two OBJ markers in the same hex. This generates a DRM on the Engagement and Combat Tables. (3.3b)

Drop Support (Drop). The removal of a stack’s access to dedicated Support weapons. (1.5i)

Play Note: KT-X brand plastic moved/fired markers are highly useful in marking Dropped Support in a way that does not hide the stack’s top unit.

Enemy Zone of Control (EZOC). Hexes adjacent to enemy units affecting friendly movement or retreats. (4.3d)

Engagement. AV unit fires used to destroy enemy AV unit steps, Drop enemy Support, and sometimes to allow a friendly unit to continue to move. (5.2)

Engagement Zone. The area around an AV unit where it could initiate an Engagement. Only non-Support AV units have Engagement Zones. Do not confuse the limited movement effects of Engagement Zones with the much more restrictive EZOCs. (4.5)

Entry Area. Hexes identified as entry locations for reinforcements. (2.1d)

Failure Flip. A Fail SNAFU result converted into a Recovery Activation. (3.7d)

Fatigue. The accumulation of stress on a Formation to the point where its dependability becomes questionable and rest required. (1.8)

FINISHED. FINISHED refers to a unit’s remaining capabilities in the current Activation. (1.2i, 3.4, and the STOPPED/FINISHED Chart)

Fire Events. A limiting means of paying for certain combat actions a unit may initiate during an Activation. (1.6)

Formation. A military command containing specific (aka ‘intrinsic’) units, its own HQ and Combat Trains. (1.3)

Fresh. A Fatigue state showing a rested and supplied Formation. They get a +1 DRM for SNAFU and Second Activation rolls. (1.8a)

Ghost Trains. Ghost Trains have been disrupted in some way and are not operating at their best abilities. They are referred to as “Ghost” because their exact location is undefined. Combat Trains become Ghost for a number of reasons, such as movement, “incorrect” distances from their HQ, or enemy actions. Ghost Trains apply a DRM for SNAFU rolls, but have no other effects. (4.7b)

Hard Units. Vehicles that have beneficial protection from barrage and other light weapons systems. This affects the roll against them on the Barrage Table and gives them a DRM when doing Shock Attacks. Hard units have a yellow background in their unit symbol. (1.1e Variations on AV or Dual units)

Headquarters (HQ). The command and control center of a Formation. Its units are required to remain within the Command Radius distance of its HQ.

Hosts. A “Host” is any unit able to make use of its Formation’s Support. (1.5a & 1.5g)

HQ Refuge. The location needed by Automatic Retreats. A hex with or adjacent to the HQ, and at least 3 hexes away from the Retreat’s starting hex. (5.5e)

Independent Unit. These are without any permanent Formation printed on the right side of its unit symbol. These units only function when assigned to some Formation. (1.1e)

Jumps. These occur when a unit moves into an enemy HQ and/or Combat Trains hex during movement or Advance after Combat. Jumps can be “Hard” or “Soft,” if the optional rule is used. The two are different in the quality of the intelligence regarding the target’s location. (4.7d)

Key Terrain. Key Terrain requires units to “stand fast” in Combat Table Situational Retreat results, but at the cost of an additional step loss. Terrain is identified as “Key Terrain” (or not) on the Terrain Effects Chart. Note that merely containing a VP symbol does not make a hex Key Terrain. (5.5d)

Main Supply Route (MSR). The contiguous hex path from a Formation HQ through the Formation’s Combat Trains to a Supply Source that keeps the Formation continuously supplied. To be useable, an MSR must be a “Complete MSR.” (3.1)

March OBJs. March OBJs control HQ movement. (2.4b)

Mixed Formations. A Formation is Mixed if units from other Formation(s) start within or enter its Blob. (3.2d)

Move-side. If a unit has a different MA on each counter side, the side with the greater MA of the two is the Move-side. A unit with only one non-Support printed side is automatically considered to be on its Move-side. (1.1c)

Movement Allowance (MA). The maximum number of Movement Points the unit can expend in a single Activation. (1.1c & 4.0a)

Movement Points (MPs). Movement Points are used to track the expenses applied to a unit’s MA by terrain according to the Terrain Effects Chart (TEC) as it moves. (4.0a)

OBJ Zone. The 2-hex radius around a Combat OBJ marker in which Attacks and Barrages can be conducted. OBJ Zones do not restrict Engagements. (3.3a)

Prepared Defense (Prep Def or PD). A Formation’s posture that trades reduced flexibility for increased defenses. (1.7)

Real AV. Any unit with an Armored Value (AV) printed on its counter which is not assigned to Support. It can be on either its Deployed or Move counter side, but not in Support at the moment.

Recovery. An Activation used to reduce a Formation’s Fatigue level. (3.7)

Regular Attack. An Attack conducted by Attack- Capable (or Dual) units using the Combat Table, but not identified as a Shock Attack. (5.1 & 5.1h)

Reinforcements. New arrivals entering play following the Order of Arrival (OOA). (2.1)

Replacement Points (Repls). These are used to replace step losses and can rebuild destroyed units. (2.2)

Roads. The word “road(s)” (no capital) designates all road types, including Tracks and Railroads. If a specific type of road is being referred to, it will be both capitalized and explicit (e.g., Secondary Road). If a road-type does apply a rule, it will be specifically mentioned (for example: “non- RR roads” would include all roads other than Railroads). (4.1c)

Safe Path. The line of communication between a unit and its HQ. (1.9)

Screening (Screen). Units executing a mission to slow enemy movement without undue risk to themselves. (4.6)

Shock Attack. Rapid attacks while moving by mechanized forces. (5.1m)

SNAFU. SNAFU represents the effect of friction, supply and other logistical matters (including transportation, routing, march traffic control, and planning) on a Formation’s operations. (3.2)

SNAFU Roll. A dice roll on the SNAFU Table to determine a Formation’s capabilities for the current Activation. (3.2)

Stack. One or more units occupying a single hex. A single unit can be a ‘stack’ unto itself. (4.2)

Static Unit. A small garrison force incapable of being assigned to any Formation. (1.1h)

Steps. Unit track their losses using Steps which show a unit’s size and resiliency. Step Losses have no direct effect on unit strength, other than their eventual removal (as dead) when they have no Steps remaining. (1.1b)

STOP. A STOP can be inflicted for a number of reasons, and precludes additional movement as well as other functions. (3.4e, 4.1e and the STOPPED/FINISHED Chart)

Stopping Engagement. The exchange occurring when one AV unit enters another’s EZOC. This could be in the form of just a STOP, or might require actual Engagement(s). (4.4)

Support. Weapon or vehicle units sent in small numbers to a Formation’s non-AV units to provide them additional firepower or protection. (1.5)

Suppression Barrages. A short barrage sharp enough so as to force the enemy’s heads down at the moment of attack. While they provide a DRM on the Combat Table, they do not generate appreciable enemy losses. (5.4g)

Terrain. Shorthand for land features identified on the Terrain Effects Chart as adding protection for defenders (or targets) while others do not. A unit “in Terrain” might suffer fewer losses.

Traffic. A condition where combat leaves an area too congested & confused to be rapidly traversed. (4.0d & 5.1f)

Trafficability. Conditions of Weather which determine the status of Terrain Effects on Movement and the DRM when a Track is used in the Formation’s MSR for SNAFU purposes. There is ‘Poor Trafficability’ in any of the earlier games where the weather conditions halved Truck MA.

Unassigned Units. An Independent unit not assigned to any Formation. (2.3d)

Unit. A ‘unit’ represents historical combat units, HQs, and their Combat Trains. Markers (of all types) are not considered “units.” (1.1)

Unit Traffic. Unit Traffic occurs when the available roads are clogged with other friendly units. (4.0e)

Unprepared. A unit not currently arrayed for combat. (1.1d)

Urban Warfare. Combat where the defender occupies an Urban terrain hex (first seen in Panzers Last Stand.) (6.1)

Used. A Formation whose Initial Activation has been completed and only has its Second Activation remaining. If it sets up that way, it must attempt a Second Activation.

Withdrawal. A change in a hex’s Control in Urban Warfare such that a side’s forces must leave a hex to the enemy. (6.1f)

Zones of Control. Hexes adjacent to a unit, where that unit affects enemy activities in several ways. (4.3)

BCS AV Types

Examples of different types of AV with their deployed side AV, range at 1km/hex scale, deployed/move Movement Allowance, game(s) they are featured, and brief note of model, gun, or comment for each.

The game abbreviations used are: LB (Last Blitzkrieg), BbF (Baptism by Fire), BC (Brazen Chariots), PLS (Panzers Last Stand).

Hard Red AV

Panzer III (short): 2 AV, Range 1, 4/14 MA (BC)—Ausf. G, H, and J with 50mm L/42
Panzer III (long): 3 AV, Range 1, 4/14 MA (BbF)—Ausf. J/1, L, and M with 50mm L/60
Panzer IV (long): 4 AV, Range 2, 4/14 MA (LB, PLS)—Ausf. F/2 and G (75mm L/43) and Ausf. H and J (75mm L/48)
Panzer V Panther: 5 AV, Range 3, 4/16 MA (LB, PLS)—75mm L/70
M3 and M5 Stuart: 2 AV, Range 1, 6/16 MA (BC, LB as LT with armor oval)—37mm L/53.5
M3 Grant/Lee: 3 AV, Range 1, 4/14 MA (BbF)—75mm L/40 and 37mm L/53.5
M4/75 Sherman: 3 AV, Range 2, 5/14 MA (BbF, LB, PLS)—Typical US Medium Tank Battalion with majority 75mm L/40
M4/76 Sherman: 4 AV, Range 2, 5/14 MA (LB, PLS)—Majority 76mm L/50 M4 tanks
Sherman Firefly: 4 AV, Range 2, 5/14 MA (LB)—1:4 ratio 17 pdr to 75mm Shermans in British Armor Units
Cruiser Mk I, II, IV (A9, A10, A13): 2 AV, Range 1, 3/12 MA (BC)—Cruiser type Mix (some fast, some slow, all poor) (2 pdr)
Crusader I (A15): 2 AV, Range 1, 4/14 MA (BC)—2 pdr
Matilda II (A12): 3 AV, Range 1, 2/10 MA (BC as Mat with armor oval)—Not Breakthrough (poor gun (2 pdr) and doctrine)
Valentine II: 3 AV, Range 1, 3/10 MA (BC as Val with armor oval)—Not Breakthrough (poor gun (2 pdr) and doctrine)
Churchill (A22): 4 AV, Range 2, 2/10 MA (BbF)—Marks III and IV with 6pdr and Marks VI and VII with 75mm L/36.5. Not Breakthrough (poor gun (6 pdr) and doctrine)
M13/40 and M14/41: 2 AV, Range 1, 2/12 MA (M13/40 in BC, M14/41 in BbF)—47mm L/32
T-34/76: 3 AV, Range 1, 6/16 MA (PLS)—76mm L/42
T-34/85: 4 AV, Range 2, 5/16 MA (PLS)—85mm L/52

Non-Hard Red AV

Humber IV/Daimler I/Staghound: 1 Non-hard Red AV, Range 1, 16 MA (LB)—2 pdr (Daimler) or 37mm L/53.5
M8 Greyhound: 1 Non-hard Red AV, Range 1, 16 MA (BbF, LB)—37mm L/53.5 as Dual Armored Cavalry
Sd.Kfz. 231/232/234/1: 1 Non-hard Red AV, Range 1, 16 MA (BbF, LB, PLS)—20mm L/55 or heavier as Dual Panzer Recon

Breakthrough Hard Red AV

Panzer VIe Tiger I: 5 Breakthrough Hard Red AV, Range 3, 4/14 MA (BbF, LB, PLS as TGR with armor oval)—88mm L/56
Panzer VIb Tiger II: 7 Breakthrough Hard Red AV, Range 3, 2/12 MA (LB, PLS as TGR with armor oval)—88mm L/71
IS-2: 6 Breakthrough Hard Red AV, Range 2, 4/14 MA (PLS as IS with armor oval)—122mm L/43
Brummbär—4 Breakthrough Hard Red/2 Limited AV, Range 1, 2/12 MA (LB, PLS as Brm with armor oval)—150mm L/12
SturmTiger—6 Breakthrough Hard Red/4 Limited AV, Range 1, 1/12 MA (LB as STgr with armor oval)—380mm L/5.4
ISU-152—6 Breakthrough Hard Red/4 Limited AV, Range 1, 3/12 MA (PLS as ISU with armor oval)—152mm L/28

Light AV

Mark VIb—0 Light AV, Range 1, 16 MA (BC as Tkt)—.50 cal MG, designated as Light Tank but defined as Tkt in BCS
L3/35—0 Light AV, Range 1, 16 MA (BC)—2x 8mm MG Tankette
Marmon-Herrington—0 Light AV, Range 1, 16 MA (BC)—1-2x 7.62 MG Armored Car
Sd.Kfz. 221/222/231/232—0 Light AV, Range 1, 16 MA (BC)—1x 7.62mm (Sd.Kfz. 221) or 20mm L/55

Breakthrough Light AV

Flammpanzer III—3 Hard Light AV, Range 1, 4/14 MA (PLS)—Flamethrower in place of main gun

Limited AV

Marder II/III—3 Red/2 Limited AV, Range 2, 3/14 MA (BbF, PLS as Mdr with armor oval)—75mm L/48 or 76.2mm L/51
StuG III (long)—3 Hard Red/2 Limited AV, Range 2, 2/14 MA (LB, PLS as StG with armor oval)—Ausf. F with 75mm L/43, Ausf. F/8 and G with 75mm L/48
Hetzer—3 Hard Red/2 Limited AV, Range 2, 2/14 MA (LB, PLS as Hetz with armor oval)—75mm L/48
JagdPanzer IV/48—4 Hard Red/3 Limited AV, Range 2, 3/14 MA (LB, PLS as JgPz with armor oval)—75mm L/48
JagdPanzer IV/70—5 Hard Red/4 Limited AV, Range 3, 2/14 MA (LB, PLS as JgPz with armor oval)—75mm L/70
JagdPanther—6 Hard Red/5 Limited AV, Range 3, 3/16 MA (LB, PLS)—88mm L/71
M3 GMC—2 Limited AV, Range 1, 2/16 MA (BbF)—75mm L/36
M10—3 Limited AV, Range 2, Support only (LB)—76mm L/53
M18 Hellcat—3 Limited AV, Range 3, Support only (LB)—76mm L/55—range increased to represent speediness
M36 Jackson—4 Limited AV, Range 3, Support only (LB)—90mm L/52
SU-76M—2 Red/1 Limited AV, Range 1, 5/16 MA (PLS as SU with armor oval)—76.2mm L/52
SU-85—4 Hard Limited AV, Range 2, 5/16 MA (PLS as SU with armor oval)—85mm L/52
SU-100—5 Hard Limited AV, Range 2, 4/16 MA (PLS as SU with armor oval)—100mm L/54
ISU-122—5 Hard Red/4 Limited AV, Range 2, 3/12 MA (PLS as ISU with armor oval)—122mm L/48.5

Stand Off AV

88mm L/56—4 Standoff AV, Range 3 (BC, BbF)
88mm L/70—5 Standoff AV, Range 3 (LB, PLS)
90mm L/53—4 Standoff AV, Range 3 (BbF)—Italian Anti-Aircraft gun
102mm L/35—4 Standoff AV, Range 3 (BC)—Naval gun mounted on truck bed
JagdTiger—8 Hard Standoff/7 Limited AV, Range 3, 1/10 MA (LB)—128mm L/55

BCS Unit Capabilities Chart

Column headings carry the notes "Only Allowed in OBJ Zones (3.3a)" and "Fire Event Use Required (max 2, 1.6a)"; the Shock Attack column is marked "Tac MA Only" (5.1k). The Unit Type column references 1.1c.

Unit Type	Regular Attack	Assist (5.1i)	Support Attack	Shock Attack (5.1k, Tac MA Only)	Attack by Fire (5.3)	Engage (5.2)	Recon (3.3)	2nd Unit in Defense	Support Defense	Spot Barrage (5.4)
Attack-Capable	Yes	Yes		Yes			Yes	Yes		Yes
Red AV		Yes		Yes	Yes	Yes	Yes

** If the unit is also Breakthrough Armor, add Shock Attack to its abilities. See also the Unit Skills and Vulnerabilities Chart.

BCS Quick Reference Boxes

Advance after Combat (5.6). If the Defender retreats (or is eliminated), the Attacker's Attack unit must advance into the defender's hex. If the Assist was stacked with the Attack unit, it may advance as well. Other units cannot advance at all. Command Radius does not restrict Advance after Combat. There is no Advance after Combat in Urban combat.

Jumping HQ/Combat Trains & Retreat (4.7d). HQs (4.7e): Retreat to a non-RR road hex 3 hexes or more hexes away without an enemy ZOC or Engagement Zone in it OR which blocks a sole existing enemy MSR. Remove any Prepared Defense and flip the Formation's Combat Trains to Ghost. Apply a Coordination marker. Combat Trains (4.7h): Displace the Combat Trains at least 10 hexes to a Legal hex which creates a Complete MSR. Flip them to Ghost. If they are unable to do so, send them off-map. See also Soft Jumps [optional], 4.7i.

Combat Trains (3.1). Legal Hexes: A Legal Hex must be connected by appropriate road hexes to both the HQ and Supply Source via hexes free of enemy units or EZOCs, making up a Complete MSR. Movement: Simply place it in a Legal hex that creates a Complete MSR and flip to Ghost. Carefully follow the sequence of events in 3.0 step b if no Complete MSR can exist. The order of events controls how rapidly an MSR Blocked marker is applied.

BCS Unit Key

Types and Special Symbols

AV Types: Red AV (the number is shown in red), Limited AV (outline), Stand Off AV (black), Light AV (white, 0).
Movement Classes: Tactical (TAC) MA (red), Leg MA (white), Truck MA (black).
Support Only: units labeled "Support." Breakthrough AV. No Rebuild Unit (yellow dot). Static Unit.
Unit Sizes: I Company; II Battalion; KG Kampfgruppe; TF Task Force; Tm Team; Grp Group; III Regiment; X Brigade; XX Division; XXX Corps; (-) Portion of the larger command; (+) Reinforced Unit.

HQs. Command Radius, Activation Roll, Arty Points, Formation ID, Formation color code bar; Unused side and Used side; MA (Truck type).

AV Units. Steps available, unit size, Hard (yellow symbol), Lower Unit ID, Formation ID, Armor Value (Red AV), Action Rating, Movement Allowance (tactical type), Range (assumed to be 1 hex if not printed).

Dual Units. Assault arrow, Armor Value, Not Hard (white symbol).

Infantry Units. Deployed Side and Move Side (here shown Unprepared), Assault Arrow, MA (Leg type), Action Rating.

Combat Trains. Regular and Ghost sides.

Markers. Prepared Defense; Step Loss (5 remaining); Game Turn; OBJ; Coordination; Activation Marker; Double OBJ; Traffic (old version said "Stopped"); Weather; Red Support; 2 Arty Asset Points; Formation Activation Marker (Higher Formation for historical information); Limited Support; 2 Air Points; Urban Hex Control Marker (Here Soviet Control); Stand Off Support; Recon Screen; March OBJ; Dropped Support; Leader; Naval Bombardment; Temporary Dropped Support; Locked Formation; Fort; Fresh Fatigue; Blown Bridge; Mines; Fatigue Level 2; Bridge tried and did not open; Minefield Breach; MSR Blocked Level 1; Bridge Not Open; Wire Breach.

All unit and marker types are not necessarily in every BCS game, only those actually needed. Specific games may require additional specialty items.

VoT Introduction

Scale

Both maps are 1 mile per hex.
Full strength Israeli Air Units represent 12 aircraft each while Arab Air Units are 24 aircraft each.

Counter Colors and Ownership

Israeli Player. The Israeli Player controls all Israeli (Blue) units.

Arab Player. The Arab Player controls all Egyptian (Orange-Tan), Syrian (Brown), Jordanian (Green), Iraqi (Olive), Moroccan (Light Green), Palestinian Liberation Army (Green), and minor Arab Allied nations—Algerian, Kuwaiti, Libyan, Saudi, and Tunisian—(Yellow-Green). Unless the rules specify otherwise, all units under the Arab Player’s control are referred to as “Arab.”

Iraqi pilots flying under the Egyptian Air Force’s organization and control are shown in Egyptian counter colors but with the Iraqi Air Force insignia in the upper-left hand corner of the counter.

VoT 1.0 Common Special Rules

VoT 1.1 Weather & Special Map Symbols

1.1a Weather. Except for one brief rain shower in the Golan Heights, the weather was consistently clear on both Fronts for the war’s duration. There is no Weather Roll or applicable effects. Trafficability is always Good. Visibility is always 4 hexes.

1.1b The SAM Boundary. A SAM Boundary is a dashed green line dividing each map into Inside and Outside zones. The Inside zone is to the west on the Sinai maps and east on the Golan map (the area when extended contains the capital of each). All hexes within each zone are either Inside or Outside and the hexes containing the Boundary are Inside. Use the Target/Defender’s Hex in all cases.

The effects of the Boundary are:

Inside the Boundary, Israeli Close Air Support (CAS) missions have greater chances of losses.
The location of the Target hex being Inside or Outside determines the number of Barrage rolls made by each Air Strike. (1.8e & 5.1)
Outside the Boundary, Egyptian units cannot use Sagger Support and have their ARs reduced by 1. (3.2d)

1.1c Defensive Zones (DZs) . These boundaries are critical locations for minor defensive features and were Objectives on the Israeli planning maps. While terrain enclosed by the DZ is handled normally, DZs themselves are for historical information only and have no game effect.

1.1d The Suez Canal. Dashed-Blue Suez Canal hexsides block all these actions/effects UNLESS the hexside contains an emplaced bridge (NOT the Israeli ferry unit):

EZOCs.
Attacks. Assists are always OK.
Engagements.
Attacks by Fire.
Spotting.

Handle solid blue Water Barrier hexsides normally and do not apply the above to them (even if they look to be “along” the canal).

1.1e Irrigation Hexes. These are a series of small waterways (actual irrigation ditches). This is the “Chinese Farm” (vic B26.10). All hexes containing any portion of an Irrigation symbol are Irrigation hexes.

1.1f Airfields. These are for historical interest and have no effect on play (yes, even for the Air War).

1.1g The Purple Line. The Purple Line is the boundary between Syria and Israel in the Golan Heights (the 1967 ceasefire line). While the game shows it as a hard single boundary in heavy purple, the actual boundary includes a UN patrolled DMZ for most of its length (marked on the map with a thin dotted purple line (left), for historical interest only). Only the heavy Purple Line matters. Hexes containing the Purple Line are Israeli.

1.1h Mt. Hermon OP. The Observation Point atop Mt. Hermon (G50.24) provided strategic observations for the entire Golan plain and accrue several special abilities to units occupying the hex. The other locations which have “OP” in their names do not confer any of these abilities and are for historical interest only.

A Unit (of any sort) occupying the Mt. Hermon OP hex can act as a Spotter for CAS Air Strikes (not Artillery Barrages) anywhere on the Golan Map during any Formation’s Activation and always has an unblocked LOS to every hex.

VoT 1.2 Series Rules Matters

1.2a Repls. Each Player obtains his Repls normally by rolling on the Replacements Table and uses them according to BCS 2.2. Roll once per side per Front in play. Repls can only be used on their own Front. The only Air Unit Repls are those in 1.5b.

1.2b Buddies. (BCS Glossary) Israelis. All Israeli Formations are Buddies with one another.

Arabs. Egyptian Tank/Mechanized Formations are Buddies with Egyptian Infantry Formations (including Commandos) and vice versa. The 130 Amph Bde (3.1c) is a Buddy with any other Egyptian Formation and vice versa. Otherwise, Egyptian Tank, Mechanized, and Infantry Formations are not Buddies with one another. No other Arab nationality’s Formations are Buddies with any other Formation.

1.2c Recon Unit Types. “Rec” unit designations do not confer Recon capability. Only units eligible according to BCS 1.1f are Recon capable.

1.2d Support. Israelis. Israelis don’t do Support. Ever.

Arabs. Only Arab units with Support printed on their counter on one side or the other can ever be in Support. The (few) Arab units with both concentrated and Support counter sides have a small “S” in the upper right of the concentrated side as a reminder. Sagger Support units never need Support Establishment Safe Paths at all (i.e., they can advance across the Suez Canal and stay in Support). Sagger Support can only be used under certain conditions, see 3.2d.

Play Note: The ramifications of no Support Establishment Path for the Egyptian Saggers are important. Infantry crossing the Canal before the bridges are up can do so with their Defensive Sagger Support, but they will not be able to access other non-Sagger Support. Also, Dropped Saggers with no Support Establishment Path can always return to Support anyway.

1.2e Supply & Isolation. Map edge Supply Sources are marked by side.

Israelis. Israeli units never suffer Isolation.

Arabs. Arab units suffer Isolation normally. Exception: Arab Commandos. (3.4)

1.2f Daily SNAFU DRMs. Each side on each Front has its own Daily SNAFU DRM on the Turn Record Track. Use the value with the Egyptian Flag for the Sinai Arabs and the Syrian Army Flag for the Golan Arabs. The Israelis use the ones under the Israeli Flag. If there are DRMs listed, use the left for the Sinai and the right for the Golan. Successful Dominique Air Strikes (1.8d) affect Arab SNAFU DRMs on the affected Front.

If the Golan has an Arab SNAFU of -1 from the Turn Record Track, and a -2 Dominique Air Strike applies, the Arabs in the Golan will use a -3 SNAFU DRM in addition to any others applicable.

1.2g Engagement Table Cap. The maximum allowed DRM (from all sources) on the Engagement Table is ±3. Any greater differential is wasted.

Developer Note: This was needed because of the possibly extreme differentials occurring here. They “broke the bank” and made it so that the Engagement Table shifted to extremes where one side might be incapable of sustaining a loss or bad result. Real life doesn’t work that way.

1.2h Orders. If the optional orders rule BCS 2.4 is in play: Conduct the Orders Phase after the Air Phase.

1.2i Bridge Access Roads. Emplaced bridges and the Israeli ferry generate “bridge access roads” which connect the roads on either side, if any. There are no printed symbols for these; they automatically exist once the bridge/ferry is operational.

1.2j Bridge Access Roads and Ferries for MSR Use. Both bridge access roads and ferries can be used as a connection for Secondary or Primary Roads needed for the MSR Trace from the Combat Trains to the Supply Source. Bridge access roads are not Tracks and never apply the Tracks SNAFU DRM.

1.2k Sequence of Play. Use the standard v2.0 BCS Sequence of Play (BCS 2.0) as amended below to contain the Air Phase (1.6) and the optional Simplified Air Rules (5.1) if used. If the XT Activation rule is in play (2.3), do not apply Activation Smoothing (BCS 2.5n).

a) Reinforcement. Both players:

Roll for new Air Points. (If 5.1 is used.)
Roll for and apply new Replacement Points.
Place Reinforcements as listed on The Order of Arrival Charts (OOAs).

b) Assignments. Both players can:

Assign or un-assign Arty Points.
Assign or un-assign Independent Units.
Units enter or exit Support.

c) Air Phase. Both players (ignore if 5.1 is used):

Task available Air Units.
Mission Execution.
Air Phase End.

d) Orders. [Optional] Both players record on a piece of paper each Formation’s Order status.

e) First Player Determination. Independently determine the first player on each Front (1.3) with the normal dice rolls. The greater roll wins and must go first on that Front. Re-roll any ties.

f) Activations. Alternate Formation Activations normally within each Front. Play each Front to completion before starting on the other Front. (1.3) When both

Fronts have been completed, the turn’s Activations are complete. Other than maintaining the right order of Activations (based on the First Player determination), players are free to conduct their Activations on the currently active Front as desired.

g) Game-Turn End. Flip or orient all HQs to their Unused sides. Remove any unused Air Points. Reset Dominique & RAM Result Tracks. Determine if any Sudden Death Victory Conditions have been met. If the Syrian Player’s VP Turn Total is greater than the current High Syrian VP total, replace it with this turn’s total. Advance the Turn marker and begin a new turn.

VoT 1.3 Two Front War

There are two Fronts: One is on the Golan Map which shows the entire Golan Heights; the other is all of Maps A, B, and C showing the Sinai along the Suez Canal. Both Fronts are relatively independent. Neither side can switch Formations, Independent Units or Arty Points from one Front to the other.

Play each Front to completion before starting any Activations on the other Front. Do not flip back and forth. Select the more interesting Front first. If you cannot agree on this, roll one die: 1-3 Golan, 4-6 Sinai.

While Arab Air Units are always confined to their Home Fronts, the Israelis split their Air Units historically between them using 2.2. Optional Exception: 5.3.

Each Player Display has boxes representing the game’s three Home Nations: Israel, Egypt, and Syria. Each Front also has an Air Display to track the results of its Air missions.

When using the optional Activation Smoothing rule BCS 2.5n, apply the rule for each Front independently (after the order of Front play is determined). Ignore potential XT Activations in the smoothing determinations. (2.3)

VoT 1.4 Amphibious Units & Bridges

1.4a Amphibious Units. Units with “Amphibious” unit symbols cross Water Obstacles using special (bracketed) Terrain Effects Chart costs. They cannot END Movement (or Retreat) in an all- Sea/Lake hex. While Amphib units can Attack (or Assist) from an all-Sea/Lake hex, destroy them if they do not Advance After Combat. Safe Paths to Amphibious units use Amphibious MA. (3.1c)

1.4b Egyptian Bridges. Mark Egyptian Suez Canal bridges built on 7 and 8 Oct 73 with “Bridge Not Open” markers at start. On the turn listed on the map, flip the markers over and the bridges are immediately usable. Suez Canal bridges cannot be damaged, destroyed or moved. The Israelis cannot interfere with their building. The needed ‘bridge access road’ exists the instant the bridge opens. These bridges can be used by either player. See 4.1a regarding their “control.”

1.4c Israeli Bridges and Ferries. Israeli bridges (for simplicity, “bridge” includes both the bridge and ferry units) must be moved to the canal. The Israeli Player can emplace a bridge on any dashed Suez Canal hexside. Emplaced bridges negate the Canal MP cost and install bridge access roads the same way as the Egyptian bridges. Ferries use the Terrain Effects Chart ferry costs but also have bridge access roads.

Bridges only take losses from Barrages and/or Attacks by Fire. Being emplaced or not makes no difference. Unlike an Egyptian bridge, Israeli bridges are eliminated when their last step is destroyed. Bridges cannot use Repls.

Once the bridge enters the desired hex, flip it to its Emplaced side and it instantly begins to function. Make sure the arrow indicator defines only one specific hexside.

Emplaced bridges cannot move or their hexside changed (they cannot return to Unemplaced)—they remain as a map-printed bridge for both sides.

Two Israeli bridges (605 and 630) must be towed by an Armor unit into position. The third (634) can move under its own power. Assign the bridges normally to Israeli Formations to use that Formation’s Armor units for towing.

Moving bridges cannot enter any EZOC. There is no effect for an Arab unit moving adjacent to them.

When moving by towing:

The towing unit must start and end the Activation stacked with the bridge.
The towing unit and bridge move using Tac MA and the number of MPs on the bridge counter in parentheses.
A towing unit can only tow one bridge per Activation.
Towing units cannot conduct Attacks by Fire, Shock Attacks, initiate Engagements, or be Assists.
Towing units can be targeted by enemy Engagements.
If the towing unit Retreats or is destroyed, abandon the bridge in the hex where this occurs.
That (or another) unit can resume towing provided it starts an initial Activation stacked with the bridge.

Design Note: The Israeli bridges and ferries are unique pieces of engineering and require special rules to handle them. There is more about the Bridging Units in the Designer’s Notes. Some will wonder if the ferry was able to carry tanks; be at ease: it can and did carry them.

VoT 1.5 Air Warfare

BCS “flying artillery” has been expanded to simulate this war’s complex aircraft, missile, and radar systems. Unlike other BCS games, you do more than roll to get Air Points. Air Units function every turn doing one of several missions to wrest control of the air or generate BCS Air Points for you to use.

Air Units are assigned (‘Tasked’) missions on each side’s Player Display and moved as their status changes. Air Units begin and end each Air Phase in their Home Nation Box. Air Units can generate Air Points used normally on the map, but the Air Units themselves are confined to the Displays and never enter the map.

Some may wish to skip the more involved Valley of Tears Air System. If desired, skip sections 1.5 through 1.9 and 2.2, and use the optional Simplified Air Rules in 5.1.

1.5a Air Units. Each Air Unit represents a specific Squadron (which the Arab nations called “Brigades”) and a specific aircraft type. Air Units are shown as either Full or Reduced Strengths by the number of aircraft icons on the counter (two = Full Strength; one = Reduced Strength) as well as a white box which also indicates Full Strength. Two-sided counters have Full on one side and Reduced on the other. Indicate loss by flipping the Air Unit if Full or sending it to the Dead Pile if Reduced.

Other counter symbols indicate the Air Unit’s possible missions.

Figure: Air Units and the Symbols on them. Counter labels: ID, Type, and capability icons (Deep Strikes, Air Sup, CAS, SEAD). Multiple Capability Air Unit: it can use any of its abilities each turn, but only one at a time. Single Capability Air Unit: this Mirage can only do Air Sup. Full Strength: two icons. Reduced Strength: one icon.

1.5b Air Repls. Only the Israelis have Air Repls, a few at start and others which arrive as Reinforcements. Keep available Air Repls in the Israeli Player Display’s Workshop Box. Handle Air Repls the same as ground Repls except each can only apply to a specific aircraft type. Two Repls are needed to revive a Full Air Unit from the Dead Pile (or the player can use only one Repl to bring a Dead Air Unit back as a Reduced Air Unit or build a living Reduced Air Unit to Full).

VoT 1.6 The Air Phase

Execute the complete Air Phase for each Front separately and in either order. Once a Front is decided upon, finish it before starting the other. Do not roll for First Activation until both Fronts are Finished.

Tasking. Both Players Task their available Air Units by moving them to their Player Display’s Mission Boxes, using 1.7. The Player Displays are secret only for this Segment.

Mission Resolution. Resolve Tasked missions using 1.8 following the number order on the Player Displays. Be sure to apply any RAM results (1.8d) before Arab CAS Air Units roll for Abort/Loss.

Air Phase End. Remaining Air Units return to their Home Nations.

1.6a Turn End Phase. Add these Segments to the Turn End Phase:

Remove all unused Air Points.
Reset Dominique & RAM Result Tracks.

VoT 1.7 Tasking

You can Task each of your Air Units as desired each turn, provided it has the needed Capability icon and the Loss/Abort Rolls have not yet been conducted (Tasking cannot be changed after its Loss/Abort Rolls have begun).

‘Task’ all, some, or none of your Air Units by placing them in your Player Display’s Mission Boxes. Each Mission Box displays the Air Unit capability icon(s) it requires—Air Units without the correct icon cannot be Tasked with that Mission. You cannot violate the Air Unit’s Frontal assignments. An Air Unit can only be Tasked one mission per turn. Past Taskings, Idleness, and multi-role Capabilities do not affect future Taskings or allow multiple Taskings per Turn.

Each Air Unit being Tasked must either be a Full Air Unit or a pair of Reduced Air units. (1.7b) Arrange the Tasked Air Units in a line for Loss/Abort roll resolution in that Mission Box (alone or in pairs based on the previous sentence). This arrangement can be left to right and/or top to bottom as desired, provided the system used is consistent and each Air Unit “slot” in the arrangement is either a Full Air Unit or a pair of Reduced ones.

A Tasked Air Unit must execute the selected mission and only that mission.

Any Air Units remaining in the Home Nation are “Idle.” Idle Air Units are not exposed to enemy action other than possible RAM mission results. (1.8d)

1.7a Missions. These are the types of missions available. Missions must be resolved in this order:

Israeli:

Air Superiority (A/S).
Suppression of Enemy Air Defense (SEAD).
Deep Strikes.
Close Air Support (CAS).

Arab:

Air Superiority (A/S).
Close Air Support (CAS).

These missions are: Air Superiority (A/S) . A/S represents an attempt to control a Front’s air space allowing you to use it freely, while the enemy cannot. The associated Air Table column determines the Loss/Abort Rolls (1.8a) used that turn. (1.8b)

SEAD Missions. SEAD missions temporarily reduce the effectiveness of SAM defenses, reducing the Loss rate they apply to CAS. (1.8c)

Deep Strikes. Deep Strikes attack either enemy Air Bases or rear area infrastructure via RAM or Dominique missions, respectively. (1.8d)

Close Air Support (CAS) . Air Units assigned to CAS convert to regular BCS Air Points (with some additional effects) to Barrage ground targets. (1.8e)

1.7b Full Air Units and Reduced Pairs. All Taskings must be made by either Full Air Units (showing two aircraft icons each) or pairs of Reduced Air Units (one aircraft icon each). Handle each Tasking separately. If any unpaired Reduced Air Units remain when Taskings are completed, they must remain idle in the Home Country for that Turn. Reduced Air Unit pairs need not be the same aircraft type; they only require the ability to conduct the same Tasking.

If a pair of two Reduced Air Units takes a Loss, the owning player chooses which to take the Loss while the other Aborts. If this same pair takes an Abort result, both Reduced Air Units Abort.

VoT 1.8 Mission Specific Rules and Resolution

1.8a Loss/Abort Rolls. Loss/Abort Rolls are read off the Sinai and GolanAir Displays based on the Air Table’s A/S Level column and the mission. Determine each Front’s A/S Level first, see 1.8b steps 1 and 2.

Using the column above, the Air Table uses the format of “d#” for each type of Mission, which represents the Air Unit’s position in the Mission Box arranged as per 1.7. The Air Units in the correct location(s) must roll for Abort/Loss. So, if the value is d2 and there are 6x Air Units, you’d roll for Air Units #2, #4, and #6. Numbers #1, #3, and #5 will not roll at all. Again, each “Air Unit” in this process can be either a Full Air Unit or a pair of Reduced Air Units as they were arrayed in 1.7.

Repeat until there are fewer Air Units than the d# remaining (referred to as a ‘partial’). Regardless of the number of partial Air Units (the only caveat is that the number of Air Units is smaller than the d#), roll only once for the last one.

If 8 Air Units obtain a d3, Air Units #3 and #6 roll normally, but then the remaining two Air Units are handled as a partial. So, Air Unit #8 also makes a Loss/Abort Roll.

Roll one die on the Loss/Abort Roll Table for each d# ‘slot’ requiring a check. Inflict a Step Loss on a roll of 1 and an Abort on rolls of 1-3 (a roll of 1 includes both a Step Loss and an Abort). Aborts have no effect except that the Air Unit does not complete the mission and is available for use again the next Turn. If the checking “Air Unit” is actually a pair of Reduced Air Units and both a Step Loss and an Abort is required, the owning player selects the Air Unit to take the loss and the other merely aborts.

If there are too few Air Units to do the d# at all, treat the whole bunch as a partial and merely roll for the last one.

1.8b Air Superiority (A/S) . Each Turn, determine the A/S column to use on the Air Table independently for each Front. The A/S column determines the Loss/Abort Rolls used by Mission Type, the number of Barrage rolls per Air Point outside the SAM Boundary, and the availability of Airlift. (1.8a, 1.8e, and 2.4) For each Front, do the following:

Step 1: Roll two dice (even if one or both sides did not Task any A/S) against the values at the top of the Table. Apply any column shift from the Advantage Box (on the sheet’s upper left, count the number of Full Air Unit units —and pairs of Reduced ones—Tasked by each side). Place the A/S marker in the resulting box. The columns are restricted to those shown. Each Turn starts the Track from scratch—the A/S column is unaffected by previous Turns.

Step 2: Make all needed Loss/Abort Rolls (1.8a) for the Air Units Tasked to A/S (on both sides) using the final column.

A/S Air Units make their Loss/Abort Rolls after they determine this turn’s A/S Level. Losses from the current turn do not affect the column used this turn.

1.8c SEAD (Israelis Only) . SEAD missions (and destroyed SAM Control hexes, 1.9) can reduce the Loss/Abort Rolls that apply to CAS missions (only) by degrading Arab SAM capabilities. Each successful SEAD Air Unit (1.7b applies) increases the CAS d# by one. Mark the resulting effect on the SEAD Track on the Israeli Player Display for the affected Front.

For example, if the Air Table calls for a CAS Loss/Abort Roll of d2 and SEAD contains two successful (remaining) Air Units (for a modifier of +2), the Loss/Abort Roll becomes d4, instead of d2.

Design Note: Despite great effort, the Israelis were unable to destroy enough SAM batteries to appreciably weaken the Arab Air Defenses. At most, they only temporarily reduced their performance. The only way to effectively destroy SAMs was with ground forces.

1.8d Deep Strikes (Israelis Only) . Deep Strikes attempt to reduce Arab effectiveness. They come in two types: RAM strikes against Arab Air Bases and Dominique strikes against Arab infrastructure. Each Deep Strike Air Unit must be Tasked specifically to either RAM or Dominique. Each Mission Type conducts its Loss/Abort Rolls separately. The number of surviving Air Units are “successful.”

No more than three Air Units can be successful per Deep Strike Task per Front each Turn. Successful Air Units beyond three are wasted and have no effect. Use the Air Display’s Tracks to record the number of successful Air Units and their effects.

RAM Missions can “sideline” Arab Air Units for several turns or possibly destroy them on the runway.

Each successful RAMMission sidelines one Arab Air Unit. Before making the CAS Loss/Abort Rolls, the Arab player freely chooses the Arab Air Units equal to the number of successful RAM Missions. All Arab Air Units (Full or Reduced, there is no requirement to pair up Reduced ones) count as one; the player is free to select only Reduced Air Units. The selections can be from any Tasking or mix of Taskings.

Roll one die for each selected Air Unit on the Front’s Air Display Sideline Period Table. On a 1, there is no effect. On a 2 through 5, the Air Unit returns as a Reinforcement the number of turns equal to that roll. On a 6, the Air Unit is destroyed (both steps if Full).

Dominique Missions award SNAFU DRMs which last the entire turn for that Front.

1.8e Close Air Support (CAS) . CAS Air Units generate BCS Air Points each turn, used normally per the series rules (with the modifications below). Do not place the actual Air Units on the map, but instead use the normal series Air Point counters to track their availability on each Front and (for the Israelis) separate Air Point availability with respect to the SAM Boundary. Place the actual Air Units used to generate Air Points back into the “Home Nation” Box.

‘Inside’ Air Points which can be used either inside (or outside) the SAM Boundary.
‘Outside’ Air Points which can only be used outside the SAM Boundary. They do not make Loss/Abort Rolls at all.

The SAM Boundary does not affect Arab Air units.

After Tasking, Israeli Inside CAS Air Units and all Arab CAS Air Units make their Loss/Abort Rolls. Convert all remaining Air Units to Air Points (two Air Points per Full Air Unit or pair of Reduced ones). Place these Air Points in a convenient location on the map for the coming Turn (identify Israeli Air Points belonging to each side of the SAM Boundary).

Exception: While Israeli Air Points dedicated to “Outside the SAM Boundary” cannot be used “Inside,” those dedicated “Inside the SAM Boundary” can be used “Outside,” but the resulting Loss/Abort Rolls make this less efficient!

These changes to the Series rule handling of Air Points apply to both the normal and Simplified Air Rules (5.1):

Air Points never require an OBJ Zone.
Arab Air Points require a normal Spotter, while Israeli Air Points only need a Spotter if the Target is in a Mountain hex. (1.1h)
The Air Point Suppression Shock Attack DRM on the Combat Table is +2 not +1. The Suppression DRM for regular Attacks or from Artillery are unchanged.
Each Air Point used as a Destruction Barrage may make multiple rolls on the Barrage Table, according to:

Outside the SAM Boundary: The number of rolls per Air Strike is on the current Air Table’s A/S Level column.

Inside the SAM Boundary: All Air Strikes make TWO rolls.

VoT 1.9 SAMs and Tanks

Place a SAM Control Destroyed marker on any Arab SAM Control hex the instant it is occupied by an Israeli AV unit. Such a SAM Control hex remains destroyed, even if the Arabs later retake it. Place a SAM Control Destroyed marker on the Israeli Player Display’s Destroyed SAM Control Box to track the count of such hexes.

Add one to the Israeli Inside CAS Loss/Abort Roll (d#) for each Arab SAM Control destroyed, e.g., if the Loss/Abort Roll is d2 and two SAM Controls have been destroyed, execute the Loss/Abort as if the d# was d4 instead.

SAM Control hexes have a distinctive symbol, such as that in Golan hex G38.10.

VoT 2.0 Israeli Special Rules

VoT 2.1 Specialized Units

2.1a Static Units. Israeli Static Units cannot be assigned to a Formation or use PD. While Static units, including those in the Fort hexes, have no ZOCs (BCS 1.1h); they can be Hard units.

2.1b Zvika. Zvika is marked with a Green Dot to remind you of these special rules.

Zvika can be assigned to any Formation even on Turn 1— as an exception to BCS 1.0g. Unless killed, he can only be reassigned during the normal Assignment Phase.
When he is destroyed, send him to any Israeli HQ. He can then Activate again when that Formation Activates (even on that same turn).
If lucky, Zivka can Activate multiple times in one turn as the result of being “killed.”
For XT Activations, Zvika is in addition to the Four Units that can Activate as per 2.3 if his Division is used.
Remove him permanently from play in the Reinforcement Phase of 8 Oct 73.

VoT 2.2 Frontal Split of the Airforce

Do not apply this rule if 5.1 is being used.

Each Israeli Air Unit type is restricted as to which Front they can be assigned but are freely Tasked to Missions based on their capabilities.

Determine each Turn’s emphasis by the F-4 & A-4 Split Chart on the Israeli Player Display, which may require a die roll depending on the date and situation. The result will emphasize either the Sinai or Golan Fronts and it determines the numbers of Air Units dedicated to each Front.

Design Note: This rule exists to avoid the ahistorical yet standard player decision-making whereby the entire Israeli Air Force is concentrated on one Front as needed each turn, but the other on the next depending on the shortest of short-term trends.

For all Splits, you can only use Full Air Units or pairs of Reduced Air Units to fill the required slots (as in 1.7).

If there are not enough Air Units to fill out the requirements, reduce each Front’s quota equally as needed. Do not reduce the Free Air Unit quota, but it can be increased by up to one Air Unit (never more than that)—so while 10-7-1 (18 total) can be reduced to 9-6-1 (16) or 8-5-1 (14), if 15 Full Air Units are available you can use 8-5-2.

Optional: Rather than rolling on the Split Chart, the Israelis pick the Front to emphasize on and after 7 Oct 73, unless superseded by Israelis west of the Suez Canal or Triggering the Homeland (4.1c).

VoT 2.3 Extreme Tempo (XT)

The Israeli Player can use “XT” on Turns 1, 2, and 3 (6, 7, 8 Oct). In a nutshell, XT allows Israeli Formations which have already completed their Turn’s normal Activations to conduct additional (small) ‘Second’ Activations, following these requirements:

The Israeli Formation must have a Complete MSR and be marked Done.
All Israeli Formations in the Golan have finished their Activations this Turn.
The Syrian Player must have Activation(s) remaining.
XTs only occur in the Golan.

XT Activations:

Potential XT Activations must make a successful “Second Activation” roll first. If the Second Activation roll fails, the XT Activation does not occur, and play goes back to the Arab Player. The Israeli player can try again in his next Activation.
Make no SNAFU Roll; a Partial SNAFU is assumed but XTs cannot place an OBJ marker.
Can be done more than once (even with the same units), given the requirements above, but only once per Israeli Activation.
Four (4) chosen Units of that Division in CR can Activate. No other Formation units can do so, including the Divisional HQ (its Arty Points will not be available).
For 36 Div XT Activations, it can Activate either the 4 Units above OR Activate 3 Units and return one of its 1-Step Armor units from the Dead Pile. This Armor unit returns w/i 1 of the 36 Div HQ with either side up and cannot function in any way during that Activation.
Zvika is in addition to these unit limits (if properly assigned above). (2.1b)
Never roll for Fatigue and cannot be used for Recovery.

VoT 2.4 Airlifts

Airlifts are a means for some Israeli units to move rapidly. Airlift can only be done within a Front—never to the other Front or to Israel.

Unit Requirements:

HQ, Airborne, or Commando units only.
Each unit is Leg MA on both sides.
No MSR needed.
Not currently Activated or Done for this Turn.

Limitations:

Limited by the scenario’s available Airlift Points. Track these on the Israeli Player Display. The total at start is all you get for the entire scenario. Each Airlift Point moves one unit of any Step Size.
Conduct Israeli Airlifts during any Israeli Activation (except the Activation of those units being Airlifted!)
The current Air Table column must allow

Airlifts, see that Front’s Air Display. Destination Hexes & Post Airlift:

The hex cannot be within 10 hexes of any operational Arab SAM Control hex.
The hex cannot contain any enemy unit or EZOC.
The hex cannot be an Arab controlled VP Hex.
Units cannot Activate after arrival.
Airlifted units arrive on their Move-side and Airlifted HQs arrive as Done.

VoT 3.0 Arab Special Rules

VoT 3.1 Special Units

3.1a Anti-Tank Guided Missiles. ATGM units cannot conduct Attacks by Fire unless the unit is a Move-side BMP. (3.1b)

3.1b BMPs. Some Arab Mechanized Infantry units are mounted in early model BMPs, rather than other more poorly armed and armored IFV types. BMPs armed with ATGMs are identified with a Red Oval in their Unit Symbol.

Unlike other ATGM units, BMPs on the side showing their AV can make Attacks by Fire.

Design Note: BMPs executing Attacks by Fire are not doing so with their ATGMs, but rather with their 73mm turret gun. The early BMPs (BMP- 1s) tested in the October War came up short in numerous ways with the usual teething problems of any complex war machine. The lessons learned were incorporated into the vehicle’s next variant (the BMP-2) and debuted in 1980.

3.1c The Egyptian 130th Amphibious Brigade. In addition to 1.4a, this Formation can trace its MSR from the HQ to the Combat Trains across or through Water Obstacles. Doing so applies the Track SNAFU modifier. The Combat Trains, themselves, must be in a normal Legal hex. The 130 Amphib Brigade is a Buddy with all other Egyptian Formations and vice versa. (1.2b)

3.1d 0-AV Units. 0-AV units are mounted in Light AV carriers (BTR-50/60s). The following only apply when the unit’s 0-AV is showing.

In addition to BCS 5.2c part I (restricting their Fires while allowing them to be Targeted), Light AV units cannot manage to INFLICT Step Losses on any Hard AV which Targets them on the Engagement Table even with really bad dice (snake eyes).
0-AV units may use only ONE Fire Event per Activation, not two.
0-AV units are rebuilt using non-AV Repls and cannot be rebuilt with AV Repls.

Design Note: BTRs must reduce the effectiveness of Israeli 50 cal MGs to safely make Attacks by Fire. Effectively, their first Fire Event is used suppressing “Support” that tanks would ignore.

VoT 3.2 Egyptian Plans & Defenses

These rules apply only to Egyptians and never to any Syrian or any Arab Allied units.

3.2a Egyptian Planning. The Egyptian Army planned a campaign that featured a short advance east of the Canal to “defeat” the Israelis by withstanding their attacks and remaining standing. The plan worked.

The Syrians desperately needed support to draw more Israeli attention away from their beaten army. To do so, the Egyptians launched a major offensive doing something they never intended: cross the SAM Boundary and slug it out with Israeli armor. The results were catastrophic.

Egyptian units outside the Sinai SAM Boundary subtract one from their AR (-1). Exception: Commando Units (3.4) do not apply this effect.

3.2b The Turn 2 PD Entry Exception. As noted in 3.2d below, Egyptian Infantry Divisions must be in Prepared Defense to use their Saggers. The phasing involved requires an exception regarding entering Prepared Defense.

On 7 Oct (only), Infantry Divisions with their HQ east of the Suez Canal can enter PD as the last action of their Initial Activation (rather than before it, as is normally the case). Do so after conducting that Activation fully and without any of the normal PD restrictions that apply.

Design Note: The point above is that the Egyptians, following their plan, will put the bridges up and as rapidly as possible install a dense mutually supporting set of defenses to maximize the effectiveness of their Sagger AT Missiles. The normal sequence of events on 7 Oct means that their HQ must move across the canal (as the bridges are just then available) but be unable to enter PD until 8 Oct. The sequencing makes for an artificial 24-hour period of vulnerability and this rule precludes it.

3.2c RPG Defenses. Non-AV Egyptian units apply a bonus +1 DRM from their newly fielded RPGs. This is the surprising effect of RPGs on the battlefield—if anything, the Israelis were more prepared for the Sagger threat than the RPG one.

Only Egyptian units showing an Assault Arrow (including Dual) obtain the RPG DRM.
There is no way to ‘Drop’ RPGs; they are not Support. The DRM is always there.
The RPG +1 DRM applies to any defense against a Regular or a Shock Attack.

3.2d Support ATGMs. New to the battlefield in great numbers, Saggers in Support apply the following:

Dropped Saggers return instantly (and are no longer Dropped) when the unit which dropped them:

Runs out of Fire Events.
Moves on to any regular Combat as Attacker or Assist. OR
Another unit begins to function.

Also:

Saggers are unaffected by terrain prohibited to Tac MA. (BCS 1.5i part i) Effectively, the Saggers are moving as Leg MA.
Sagger Support Re-establishment does not require any Safe Path. (1.2d an exception to BCS 1.9c).
Sagger Support only exists for units in Prepared Defense AND Inside the SAM Boundary (in addition to the normal Support requirements). Otherwise, completely ignore the Sagger Support and the Saggers do not count for anything.

Non-Support ATGM units do not apply the above.

VoT 3.3 Strategic Reserves

The scenario may identify Arab Formations as starting in each Home Nation’s Strategic Reserve. These are also listed on the Arab Player Display.

3.3a Trigger. The Israeli Player triggers the Front’s Strategic Reserve availability by crossing east of the Purple Line in the Golan or west of the Suez Canal in the Sinai. Each Front triggers independently. The crossing involved requires the actual movement of any Israeli unit to the Arab side of the appropriate line. Once triggered, it remains in effect and added changes have no effect.

3.3b Reinforcements. Starting the turn after the trigger and each turn’s Reinforcement Phase thereafter (if desired), the Arab Player can bring on any number of that Front’s Strategic Reserve Groups in the listed order. They cannot jump the queue. Egyptian Groups arrive at Entry Areas F or G, except Group 4 which arrives at the 3 Mech HQ. Syrian Groups all arrive at Entry Area O. Send Air Unit Groups to the Arab Player Display.

3.3c VP Penalty. Each Strategic Reserve Group (no matter its contents) released to the map gives the Israeli Player 1 VP. One Formation (the Egyptian 3 Mech Division) arrives in two separate groups and gives the Israelis 2 VPs total if both enter play. After entry, the 3 Mech Division acts as any single normal Formation.

VoT 3.4 Commandos

The Arabs have a handful of Commando units capable of raid missions. They enter via the Order of Arrival with several arrival hexes to choose from. They arrive only on that Turn and cannot use Airlifts. (2.4) Place Commandos AFTER all Israeli Reinforcements.

3.4a Arab 0-MA Commandos. These units (with 4-AR or 3-AR) arrive on both Fronts. The OOA provides a choice of landing hexes. Each must arrive that turn. You can distribute them among the listed hexes as desired. If the listed hex has a VP in it, no OBJ is needed to “land” there (an exception to BCS 3.3a). The chosen hex cannot contain an enemy unit or EZOC.

Commando units with a 0 MA:

Are on their Deployed-side. Exception to BCS 1.1c.
Cannot be Assigned to a Formation.
Never Activate.
Are not Static units but are destroyed if they Retreat.
Never suffer Isolation.
Have normal ZOCs.

3.4b 1/82 Para Co. This Syrian unit enters the map the same as the 0-MA Commandos in 3.4a, but with the following difference: It becomes a normal unit of the Syrian Cdo Grp and must Activate with it (normally) once in normal CR.

VoT 4.0 Victory

4.1 Victory Conditions

4.1a Victory Point Hexes. Israeli VP hexes are marked with Stars of David; Arab VP hexes are marked with Egyptian Eagles or Syrian Laurels. Some are marked as both. Each VP hex gives 1 VP when under friendly control. Control of enemy VP hexes does not award any VPs but denies them to the enemy.

“Control” is awarded to the side which occupies (or is last to occupy) that hex with a friendly Unit, provided the unit is:

In Command Radius.
Assigned or Intrinsic Units of an Active Formation with a Complete MSR.
Exception: Arab Commando units (3.4) ignore these requirements.

On 6 Oct 73, all Sinai VP hexes east of the Suez Canal and Golan VP hexes west of the Purple Line are Israeli controlled.

There is no special concept of “control” of bridges. Control of a bridge only matters when counting for Victory, and the only thing that matters is which side was the last to cross the bridge.

Remember: Don’t forget BCS 3.3d, Objective Marker Placement (exception 3.4a). Once under control, the feature remains in friendly control until the enemy wrests control for themselves.

4.1b Counting VPs.

The Israelis (on each Front separately) count VPs at the end of the game.
The Egyptians (Sinai Front) count VPs at the end of the game.
The Syrians (Golan Front) count VPs each turn to determine the game’s best turn. There is no “end of game” number for them. Count them at the end of each complete game turn.

So, if the Syrians control 7 VPs at the end of turn 3, but none at the end of play—they have 7 VPs. If the Israelis in the Golan had 8 VPs on turn 4, but none at the end of play, the Israelis have no VPs for the Golan. The Syrians win the Golan, 7 to 0. If, at the same time, the Israelis end up winning the Sinai, the game total is a split between the Fronts, so the complete game is a draw. A side must win both Fronts to win the war.

4.1c Arab VPs. Total the VP Hexes held by each Front. Do so each turn in the Golan to find the turn with the highest total but do so only at the end of play for the Sinai. Make sure the Other Arab VPs are totaled at the same time to create the grand total number of Arab VPs for each Front. On the contrary, the Syrian score is the highest value for any single turn for VP hexes plus the game end total for Triggering the Homeland or Israeli Air Units Destroyed. The Egyptian score is only the total calculated at the end of play.

Arab VP Hexes

Sinai:

Tamir (A25.09)
Baluza (A38.16)
Ma’adim Road (A29.03)
Amir “Chinese Farm” (B25.13)
Televizia (B28.16)
Havraga (B29.29)
Hamutal (B30.21)
Hamadia (B31.15)
Tasa (B42.19)
Polish Camp (Ofra) (C41.29)
Ras Sudar Road (C44.00)
Qarat Moura (Poligon) (C46.13)
Wadi Mabuk (C56.09)
Mitla Pass (C61.15)
Giddi Pass (C61.27)

Golan:

El ‘Al (10.27)
Arik Bridge (18.35)
Jukhader (21.21)
Tel Fares (23.20)
Tel Zabach (25.28)
Hushniya (26.23)
Bnot Yaakov Bridge (27.35)
Nafah (30.27)
Pkak Bridge (30.33)
Mt. Yosifon (Tel Abu Yusuf) (31.24)
Wasit (37.28)
El Rom (40.25)
Banias (46.30)
Fort 102 (50.24)
Hermon trail (50.25)

Other Arab VPs: In addition to the list below, the Arab player can obtain the following:

1 VP (Sinai only) for each Arab Infantry Division HQ (do not apply for any Brigade, Armor, or Mech HQ) east of the Suez Canal with a Complete MSR. Use markers to track these HQs and their MSR status on the Arab Player Display.

1 VP (Golan only) for Triggering the Homeland. This occurs if the Syrians occupy (not control) one or more of Entry Areas I (44.35 only), J (26.35), and K (19.35) with units currently in CR. No MSR is required. Even if a Suez Crossing is in effect, apply the Golan Emphasis (2.2 or 5.1) for the rest of the game.

1 VP per Israeli Air Unit in the Dead Pile. These VPs are unavailable when using the Simplified Air Rules.

4.1d Israeli VPs. At the end of play, compute the Israeli score for each Front using the below.

Other Israeli VPs: In addition to the list below, the Israeli player can obtain (only) the following:

1 VP for each Arab Strategic Reserve Group entering play as listed on the Arab Player Display for that Front.

Israeli VP Hexes

Sinai:

El Qantara (A20.06)
Port Said (A21.35)
Port Fuad (A22.33)
Ismailia (B17.22)
Fayid (B18.03)
Sarafeum (B20.14)
Purkan (B20.21)
Hizayon (B22.26)
Deversoir (B22.09)
Amir “Chinese Farm” (B25.13)
Hamutal (B30.21)
Km 101 (C12.21)
Geneifa Camp (C29.28)
Suez City (C36.12)

Golan:

Jassem (25.09)
Al-Hara (31.12)
Kafr Shams (35.06)
Kanaker (48.07)
Maschara (37.15)
Kafr Nasej (38.10)
Khan Arnabeh Fort (41.18)
Tel Merai (43.08)
Tel Shams (46.12)
Sa’sa (49.11)
Fort 102 (50.24)
Hermon trail (50.25)
Mazraat Beit Jann (51.17)
Khan al-Sheikh (56.05)
Katana (61.08)
Damascus Road (62.02)

4.1e Sudden Death Victory. If Sudden Death occurs, ignore the normal Victory Conditions, and the game ends instantly with a win to the side which scored it.

A Sudden Death Victory occurs if any of the following occur:

The Israelis capture and were the last to cross at least three Egyptian bridges and the following units cross the Canal to the west on or before 9 Oct 73. The units required are at least 6x Armor units and a Divisional HQ (the units must all come from the same division). The Armor units can be of any type and remaining size.
The Israelis exit the Golan via Entry Area O on or before 12 Oct 73 with the same unit requirements above.
The Egyptians exit two Armor or Mechanized Divs (each with its HQ and at least 8 Units) off Sinai Entry Areas A, B, or C on or before 14 Oct 73.
The Syrians exit two Armor Divs (each with its HQ and at least 8 Units) off Golan Entry Areas J or K on or before 8 Oct 73.

Formations required must be in CR and have a complete MSR at the moment they exit the map. If more than one Formation is listed, the number needed can be completed in a later turn. (Sudden Death does not occur until the full requirement is met.)

4.2 Ending the Game

The game ends in one of two ways: short scenarios which end at the time noted in their set ups using the needed parts of 4.1, or longer scenarios which end based on the dice roll for Ceasefire. Either player can accept or reject this Ceasefire—if rejected, there will be a second ceasefire which must be obeyed.

4.2a Ceasefires. Starting on 20 Oct, roll two dice against the current turn’s Ceasefire value on the Turn Record Track in the Reinforcement Phase. If the roll is equal to or greater than the turn’s value, a Ceasefire might occur. Play continues that turn, normally, until the Game-turn End Phase. In that Phase, either side can choose to violate the Ceasefire. If neither side violates the Ceasefire, the game ends. If the Ceasefire is violated, play continues, but uses 4.2b.

4.2b Violating Ceasefires. If either side violates the Ceasefire, the game continues normally (including rolling for Ceasefire again) until a second Ceasefire occurs. Neither side can “violate” a second Ceasefire—the game ends automatically at the end of that turn.

Play Note: In scenarios 6.1, 6.2, 6.3, and 6.8 the game’s duration is not fixed. If there is no Sudden Death Victory, the game’s end by Ceasefire cannot happen before 20 Oct. By the TRC’s Ceasefire dice rolls, the scenario will end sometime between the 20 th and the 27 th. In the unlikely event the game extends even further, use the information on the 27 th for any turns beyond it.

VoT 5.0 Optional Rules

VoT 5.1 Simplified Air Rules

If you wish to skip the more elaborate Air System (1.5 - 1.9 and 2.2), use these rules instead. Each turn, make three two-dice rolls (one roll each for the Israelis, Egyptians, and Syrians) on the Air Points Available Table. The result is the number of Air Points available for each nation.

Roll once to determine the Israeli Frontal “emphasis” (using the small table at the bottom of the Air Points Available Table) even when playing scenarios showing a single Front. The Israeli Air Points Available result gives two values separated by a slash. The Emphasis Roll determines which Front gets which value. In a single Front scenario, you get only the Air Points allocated to the Front you are playing.

The resulting Air Points are normal BCS Air Points available for that side (but apply the special capabilities listed in 1.8e and repeated below, modified to fit correctly with rule 5.1).

Air Points never require an OBJ Zone.
Arab Air Points require a normal Spotter, while Israeli Air Points only need a Spotter if the Target is in a Mountain hex. (1.1h)
The Air Point Suppression Shock Attack DRM on the Combat Table is +2 not +1. The Suppression DRM for regular Attacks or from Artillery are unchanged.
Each Air Point used as a Destruction Barrage may make multiple rolls on the Barrage Table, depending on the below:

Outside the SAM Boundary: Use the number Air Strike rolls listed on the Air Display for an assumed Israeli A/S level 2 (Israeli 3 and Arab 1).

Inside the SAM Boundary: All Air Strikes make TWO rolls.

ALL the other main Air Rules do not apply when using 5.1, including 1.1b (SAM Boundary) and 1.5b (Air Repls). Exception: The SAM Boundary’s location determines the number of Barrage Rolls available per Air Point above.

When using this system, do not award VPs for destroyed Israeli Air Units, nor are there any effects from Deep Strike missions.

5.2 Splitting the Israelis

This rule allows both players to enjoy using a more effective and active Israeli Army. It is played with 2.2. If an entering Formation has Entry Areas on either Front, roll one die for it:

1-3 Sinai (Entry Areas A-D) 4-6 Golan (Entry Areas I-L)

One player plays the Egyptians and the Golan Israelis, while the other player plays the Syrians and the Sinai Israelis. For Victory, total up each side by Front and award the VPs according to that same scheme.

5.3 Free Frontal Air Allocations

Ignore 2.2 and allow the Israeli player to freely divide his Air Force between the two Fronts. He can go all the way to the extreme of ignoring one Front in favor of the other, and switching his Air Units from one Front to the other every turn if he wants—or anything in-between.

Do not use 5.1 when 5.3 is in play.

Have fun!

New Series Rules

5.2c Light AV vs. Tanks.Light AV units cannot inflict Step Losses on Hard Targets via the Engagement Table even with really bad dice. (Repeat of VoT 3.1d)

5.2g [Optional] Realistic Engagement Target Selection. To avoid some unusual combinations of AV strengths and ranges, use the following for both plain Engagements and Stopping Engagements. This is more involved than the standard rules.

Important: When using this rule, do not apply the Targeting Restrictions in 4.4b part i and 5.2b part ii. Use the below instead.

If a Real AV unit (A) wishes to Engage, the Active Player must select the Strongest Inactive AV unit (B) with a range reaching A. Active Player chooses in ties.

The Inactive unit (B) may be Real or Support and need not be in A’s range. If B is Support, the Inactive player can choose (when the fire is announced) to either Engage normally or ‘self-drop.’ Self-dropped Support always remains dropped for the remainder of the Activation. The announced fire does not occur, A’s Fire Event is not used, and the Stop (if any) is Waived.

Design Note: Using B’s range “reaching A” is not a typo. One assumes that no matter what firing the Active unit wants to do, A will be forced to Engage longer-ranged enemy units nearby—not some easier target. The Support clause exists to allow a Target’s Support to remain hidden rather than risking Engaging—but doing so precludes the ability to return to providing Support in that same Activation.

VoT 6.0 Scenarios

VoT 6.1 The Yom Kippur War: Two Front Campaign

This is the full campaign, two-front war.

First Turn: 6 Oct 73 Last Turn: see 4.2 First Player on Sinai and Golan: Arab

Israeli Set Up: Israeli Player Display:

Israel: 4x F-4E, 3x Mirage IIICJ, 5x Nesher, 2x A-4E, 4x A-4H, 2x Sa’ar (One Reduced) Workshop Box: 2x F-4E Repl, 4x A-4E/H Repl Airlift Points: 6

Golan Front: Independents:

50.24: 102 Fort Plt
48.25: 103 Fort Plt
46.24: 104 Fort Plt
44.23: 105 Fort Plt
39.21: 107 Fort Plt
34.21: 109 Fort Plt
31.21: 110 Fort Plt
27.21: 111 Fort Plt
22.18: 114 Fort Plt
20.19: 115 Fort Plt
18.20: 116 Fort Plt

36 Div:

32.27: HQ (Fresh)
36.22: A/53 C Arm Co
38.24: B/53 C Arm Co
26.23: C/53 Arm Co, G/74 Arm Co
21.21: F/74 Arm Co
44.26: H/74 C Arm Co
37.28: 71/7 C Arm Bn, 75/7 Mech Bn
31.27: 77/7 C Arm Bn, Tiger C Arm Co
30.26: 82/188 Arm Bn
28.31: Combat Trains

Formation Activation Markers in Play: 36 Div

Sinai Front: Independents:

A31.28: Budapest Fort
A21.29: Orkal Fort
A21.23: Lahtzanit Fort
A21.19: Drora Fort
A21.13: Ktuba Fort
A21.06: Milano Fort
A21.03: Mifreket Fort
B22.26: Hizayon Fort
B20.21: Purkan Fort
B23.10: Matzmed Fort
B26.08: Lakekan Fort
C33.34: Botzer Fort
C38.26: Lituf Fort
C38.17: Mafzeah Fort
C38.11: Nisan Fort
C37.10: Masrek Fort

252 Div:

C62.27: HQ (Fat-0), Combat Trains, 46/401 M Arm Bn, 195/401 M Arm Bn
B42.19: 424 Shkd Arm Cav Bn (-) (Assigned to 252 Div)
B26.23: G/184 M Arm Co
B29.29: H/184 M Arm Co
B28.16: J/184 Mech Inf Co
C45.08: A/52 M Arm Co
C45.17: B/52 M Arm Co
C44.28: C/52 M Arm Co

275 Ter Bde:

A38.16: HQ (Fat-0, 1 Arty Point), 68 Inf Bn (-)
A40.14: 9 M Arm Bn (-)
A35.15: M/9 Arm Co
A28.09: A/424 Arm Cav Co
A45.17: Combat Trains

Formation Activation Markers in Play: 252 Div, 275 Ter Bde

Arab Set Up: Arab Player Display:

Egypt: 6x MiG-21 (A/S, Three Reduced), 1x MiG-21 (A/S and CAS), 1x MiG-17 (A/S, Reduced), 2x MiG-17 (CAS, One Reduced), 2x Su-7 (One Reduced)

Unreleased Strategic Reserve: Group 1: 182 Para Bde (HQ (Fresh), 38 ATGM Bn, 81, 85, 89 Abn Bn, Combat Trains), 3 Mech Div (HQ (Fresh), 229/23, 254/23, 255/23 Arm Bn, 267/23 Mech Bn, Combat Trains) Group 2: 139 Cdo Grp (HQ (Fresh), 39 ATGM Bn, 133, 223 Cdo Bn, 139 Cdo Trains), 35 Tk Bde (HQ (Fresh), 283, 284, 285 Arm Bn, 270 Mech Bn, Combat Trains) Group 3: 170 Para Bde (HQ (Fresh), 645 ATGM Bn, 75, 77, 79 Abn Bn, Combat Trains), 27 Nasr Tk Bde (HQ (Fresh), 10, 11, 12 Arm Bn, 290 Mech Bn, Combat Trains) Group 4: 3 Mech Div (3 Arm Cav Bn, 30 ATGM Bn, 217/10, 227/114 Arm Bn, 30/10, 31/10, 32/10, 340/114, 341/114, 342/114 Mech Bn)

Syria: 5x MiG-21, 3x MiG-17 (One Reduced), 1x Su-20 (Reduced)

Unreleased Strategic Reserve: Group 1: 62 Syrian Inf Bde (HQ (Fat-0), IV Arm Bn, 420, 424, 622 Inf Bn, Combat Trains) Group 2: 90 Syrian Inf Bde (HQ (Fat- 0), 491 Arm Bn, 493, 495, 496 Inf Bn, Combat Trains) Group 3: Assad Syrian Tk Bde (HQ (Fresh), II, III Arm Bn, IV Mech Bn, Combat Trains)

Golan Front: Syrian unless otherwise noted. Cdo Grp:

56.20: HQ (Fresh)
56.19: 87 Rec Cdo Bn
52.23: 82 Abn Bn (-)
55.23: 83 Cdo Bn
54.15: 133 Cdo Bn
55.13: Combat Trains

7 Inf Div:

44.14: HQ (Fresh), Tank Arm Bn (+) (Support)
42.13: AT ATGM Bn
48.22: 183 Cdo Bn
41.14: I/78 Arm Bn
43.15: II/78 Arm Bn
45.14: III/78 Arm Bn
43.14: IV/78 Mech Inf Bn
37.10: 174/121 Mech Inf Bn
38.08: 178/121 Mech Inf Bn
39.10: 179/121 Mech Inf Bn
38.09: IV/121 Arm Bn
42.19: 151/68 Inf Bn
44.19: 241/68 Inf Bn
45.21: 282/68 Inf Bn
38.18: 333/85 Inf Bn
40.18: 334/85 Inf Bn
41.18: 337/85 Inf Bn
48.20: 6 Moroccan Arm Bn
47.21: 12 Moroccan Inf Rgt
49.11: Combat Trains

9 Inf Div:

31.12: HQ (Fresh), Tank Arm Bn (+) (Support)
31.08: AT ATGM Bn
30.18: 412 Palestinian Cdo Bn
34.06: 211/43 Arm Bn
33.06: 212/43 Arm Bn
33.05: III/43 Arm Bn
34.05: IV/43 Mech Inf Bn
26.07: 451/51 Arm Bn
27.07: 452/51 Arm Bn
27.06: 453/51 Arm Bn
28.05: 454/51 Mech Inf Bn
26.16: 187/33 Inf Bn
27.17: 243/33 Inf Bn
28.17: III/33 Inf Bn
31.18: 114/52 Inf Bn
33.19: 159/52 Inf Bn
35.18: 222/52 Inf Bn
32.01: Combat Trains

5 Inf Div:

17.10: HQ (Fresh), Tank Arm Bn (+) (Support), 203/12 Arm Bn
13.06: AT ATGM Bn
18.16: 413 Palestinian Cdo Bn
16.08: 355/12 Arm Bn
19.09: 356/12 Arm Bn
21.09: 346/12 Mech Inf Bn
12.05: 152/47 Arm Bn, 154/47 Arm Bn
12.04: 499/47 Arm Bn, 393/47 Mech Inf Bn
13.13: 287/132 Arm Bn
12.12: 199/132 Mech Bn
13.14: 262/132 Mech Bn
14.12: 328/132 Mech Bn
16.17: 74/61 Inf Bn
16.16: 320/61 Inf Bn
17.17: 323/61 Inf Bn
19.16: 171/112 Inf Bn
20.15: 271/112 Inf Bn
21.16: 287/112 Inf Bn
12.02: Combat Trains

Formation Activation Markers in Play: Cdo Grp, 5 Inf Div, 7 Inf Div, 9 Inf Div

Sinai Front: Egyptian unless otherwise noted. Unassigned Independents:

B17.04: 329/AJ Palestinian Static Bn
B18.03: 339/AJ Palestinian Static Bn
B19.03: 349/AJ Palestinian Static Bn
C21.34: 359/AJ Palestinian Static Bn
C25.33: 5/Ymk Arab Static Bn
C36.12: Militia Static Bn

Pt Said Inf Cmd:

A21.35: HQ (Fat-0), Tank Arm Bn (+) (Support)
A20.26: 135/30 Inf Bn
A20.19: 136/30 Inf Bn
A20.23: 137/30 Inf Bn
A26.31: 533/135 Inf Bn
A20.29: 534/135 Inf Bn
A22.33: 535/135 Inf Bn
A20.22: 203 Cdo Bn
A19.35: Combat Trains

18 Inf Div:

A18.05: HQ (Fresh), 36 ATGM Bn, 634 AT Bn, Tank Arm Bn (+) (All in Support), 219 Arm Bn, 536/136 Mech Inf Bn
A17.06: 118 Arm Cav Bn, 1 ATGM Rgt (Assigned to 18 Inf)
A17.05: 102 ISU Arm Bn, 537/136 Mech Inf Bn
A19.06: 538/136 Mech Inf Bn
A20.03: 256 Cdo Bn
A20.07: 145/90 Inf Bn
A20.08: 147/90 Inf Bn
A20.12: 150/90 Inf Bn
A20.04: 530/134 Inf Bn
A20.05: 531/134 Inf Bn
A20.06: 532/134 Inf Bn
A13.03: Combat Trains

15 Tk Bde:

A4.02: HQ (Fresh), 244 Arm Bn, 245 Arm Bn
A3.02: 246 Arm Bn, 265 Mech Inf Bn
B1.33: Combat Trains

2 Inf Div:

B18.27: HQ (Fresh), 33 ATGM Bn, 364 AT Bn, Tank Arm Bn (+) (All in Support), 239 Arm Bn, 360/117 Mech Inf Bn
B17.28: 102 Arm Cav Bn
B19.27: 221 SU Arm Bn, 361/117 Mech Inf Bn
B19.28: 362/117 Mech Inf Bn
B21.27: 13 Cdo Bn
B20.24: 10/4 Inf Bn
B21.25: 11/4 Inf Bn
B21.26: 12/4 Inf Bn
B21.28: 507/120 Inf Bn
B21.29: 508/120 Inf Bn
B22.29: 509/120 Inf Bn
B13.28: Combat Trains

24 Tk Bde:

B16.28: HQ (Fresh), 248 Arm Bn, 252 Arm Bn
B16.29: 253 Arm Bn, 268 Mech Inf Bn
B13.31: Combat Trains

16 Inf Div:

B19.14: HQ (Fresh), 35 ATGM Bn, 646 AT Bn, Tank Arm Bn (+) (All in Support), 216 Arm Bn, 7/3 Mech Inf Bn
B18.13: 26 Arm Cav Bn
B20.13: 296 T100 Arm Bn, 8/3 Mech Inf Bn
B20.14: 9/3 Mech Inf Bn
B21.17: 73 Cdo Bn
B22.11: 16/16 Inf Bn
B22.12: 17/16 Inf Bn
B22.13: 18/16 Inf Bn
B21.14: 334/112 Inf Bn
B21.15: 335/112 Inf Bn
B21.16: 336/112 Inf Bn
B17.10: Combat Trains

21 Tk Div:

B16.14: HQ (Fresh), 200/14 Arm Bn, 201/14 Arm Bn
B16.15: 203/14 Arm Bn, 260/14 Mech Inf Bn
B15.19: Combat Trains

130 Amph Bde:

C33.30: HQ (Fresh), 602 Amphibious TF
C34.29: 603 Amphibious TF
C29.29: Combat Trains

25 Tk Bde:

C27.24: HQ (Fresh), 275 Arm Bn, 276 Arm Bn
C26.24: 277 Arm Bn, 269 Mech Inf Bn
C22.25: Combat Trains

7 Inf Div:

C34.22: HQ (Fresh), 34 ATGM Bn, 640 AT Bn, Tank Arm Bn (+) (All in Support), 226 Arm Bn, 34/11 Mech Inf Bn
C35.21: 119 Arm Cav Bn, 292 SU Arm Bn
C35.22: 295 T100 Arm Bn, 35/11 Mech Inf Bn
C35.23: 36/11 Mech Inf Bn
C37.26: 33 Cdo Bn
C37.23: 24/8 Inf Bn
C37.24: 25/8 Inf Bn
C37.25: 26/8 Inf Bn
C37.20: 37/12 Inf Bn
C37.21: 38/12 Inf Bn
C37.22: 39/12 Inf Bn
C30.24: Combat Trains

19 Inf Div:

C36.15: HQ (Fresh), 37 ATGM Bn, 641 AT Bn, Tank Arm Bn (+) (All in Support), 212 Arm Bn, 5/2 Mech Inf Bn
C35.15: 19 Arm Cav Bn, 3 ATGM Rgt (Assigned to 19 Inf)
C35.16: 6/2 Mech Inf Bn
C36.17: 47 ISU Arm Bn, 22/2 Mech Inf Bn
C37.19: 43 Cdo Bn
C38.12: 63 Cdo Bn
C37.16: 4/5 Inf Bn
C37.17: 14/5 Inf Bn
C37.18: 15/5 Inf Bn
C38.13: 2/7 Inf Bn
C38.14: 19/7 Inf Bn
C38.15: 21/7 Inf Bn
C34.12: Combat Trains

6 Mech Div:

C33.15: HQ (Fresh), 225/22 Arm Bn, 250/22 Arm Bn
C32.15: 251/22 Arm Bn, 266/22 Mech Inf Bn
C28.17: Combat Trains

Formation Activation Markers in Play: 130 Amph Bde, 21 Tk Div, 15 Tk Bde, 24 Tk Bde, 25 Tk Bde, 6 Mech Div, 2 Inf Div, 7 Inf Div, 16 Inf Div, 18 Inf Div, 19 Inf Div, Pt Said Cmd

VoT 6.2 On the Banks of the Suez: Sinai Front Campaign (Large)

This covers just the Sinai Front of the Yom Kippur War. The Egyptians were determined to retake the Sinai and planned for a methodical approach with a large anti-tank cordon. This would force the Israelis to dislodge them from their bridgehead where it was hoped that an advantageous position would put Egypt in good terms during negotiations following a UN ceasefire they knew would come.

Playing Area: Maps A, B, and C First Turn: 6 Oct 73 Last Turn: see 4.2 First Player: Arab Victory Conditions: Use the Sinai-related game victory conditions (4.1).

Israeli Set Up: Setup as Scenario 6.1 for the Sinai Front.

Israeli Player Display:

Israel: 4x F-4E, 4x Nesher, 2x A-4E, 4x A-4H, 2x Sa’ar (One Reduced) Workshop Box: 1x F-4E Repl, 3x A-4E/H Repl Airlift Points: 3

Israeli Reinforcements: Do not use the Israeli Order of Arrival. Use the below instead: 7 Oct 73

Israel: 4x F-4E, 2x A-4E, 2x A-4N

Any Israeli Entry Hex: 1/Bishof and 2/Bishof Static Cos

275 Ter Bde HQ: Lapidot M Arm TF (Assigned to 275 Ter), 162 Div (198/460 M Arm Bn)

B42.19 (Tasa): 143 Div (79/14, 196/14 M Arm Bn)

A: 162 Div (HQ (Fresh), 19/460 M Arm Bn, 113/217, 126/217, 142/217, 429/500, 430/500, 433/500 C Arm Bn, 86/460, 189 Rec Mech Bn, Combat Trains)

B: 143 Div (HQ (Fresh), 87 M Arm Cav Bn, 257/421, 599/421, 407/600, 409/600, 410/600 M Arm Bn, Combat Trains)

D: 35 Para Bde (HQ (Fresh), 890 Para Bn, Combat Trains)

8 Oct 73

Remove: 252 Div (G/184, H/184 M Arm Co, J/184 Mech Co)

Add: 2x Arty Points

143 Div HQ: 143 Div (184/14, 264/421 M Arm Bn)

252 Div HQ: 252 Div (104/164, 106/164, 183/164 C Arm Bn)

A: Nammer TF (HQ (Fat-1), 279 Rec C Arm Bn, 226/11 S Arm Bn, 54/11, 128/11, 141/204 Mech Bn, Combat Trains)

C: 440 Div (HQ (Fresh), 129/875 S Arm Bn, 89/875, 121/875 Mech Bn, Combat Trains)

D: 440 Div (A/225 T Arm Bn (-), 202 Abn Bn (-), 450 Abn Bn)

9 Oct 73

Nammer TF HQ: Nammer TF (Vilner Inf TF)

B: 274 Arm Bde (HQ (Fresh), 25, 227, 228 T Arm Bn, Combat Trains)

10 Oct 73

Any HQ: 564 Abn Bn

143 Div HQ: 143 Div (582 Shun Abn Bn)

162 Div HQ: 162 Div (Wnr/217 Abn Co)

B: 247 Para Bde (HQ (Fresh), 416, 565 Abn Bn, Combat Trains)

11 Oct 73

Any HQ: 630 Bridge Bn, 634 Ferry Bn

13 Oct 73

B35.16 (Yukon): 605 Bridge Bn

162 Div HQ: 162 Div (100/460 M Arm Bn)

15 Oct 73

Add: 2x Arty Points

143 Div HQ: 143 Div (Shmulik Abn TF)

440 Div HQ: 440 Div (182 S Arm Bn, 9400 Inf Bn)

17 Oct 73

Add: 1x Arty Point

440 Div HQ: 440 Div (52 M Arm Bn)

18 Oct 73

Any HQ: 88 DvL Amphib Rec Bn

162 Div HQ: 162 Div (271 Mech Eng Bn)

20 Oct 73

Any HQ: 50 Abn Bn

35 Abn HQ: 35 Para Bde (48, 469 Abn Bn)

Nammer TF HQ: Nammer TF (268 S Arm Bn)

A, B, or C (Use only one): Sela TF (HQ (Fresh), 105/5, 171/5, 172/5, 173/5 Inf Bn, Combat Trains), 484 Harv Arm Cav Bn and Yaron Abn TF (Both Assigned to Sela)

21 Oct 73

Workshop Box: 1x F-4E and 1x A-4E/H Repls

22 Oct 73

Workshop Box: 1x F-4E and 1x A-4E/H Repls

Any HQ: Hisdai Abn TF

252 Div HQ: 252 Div (96/179 C Arm Bn [2])

23 Oct 73

Workshop Box: 1x F-4E and 1x A-4E/H Repls

440 Div HQ: 440 Div (B/225 Arm Bn (-))

Arab Set Up: Use the setup as Scenario 6.1 for those units that set up on the Sinai Front and Egyptian side of the Arab Player Display.

Arab Reinforcements: Use the Arab Order of Arrival for units arriving on the Sinai Front and Egyptian side of the Arab Player Display.

VoT 6.3 Syrians at the Border: Golan Front Campaign (Medium)

This covers just the Golan Front of the Yom Kippur War. Unlike the Egyptians, the Syrians had planned to attack aggressively and reach the Jordan River. The Syrians knew time was against them as Israeli reinforcements would arrive and equalize the number of forces, so making an all-out effort to reach their objectives quickly was to be their key to success.

Playing Area: Golan Map First Turn: 6 Oct 73 Last Turn: see 4.2 First Player: Arab

Victory Conditions: Use the Golan-related game victory conditions (4.1).

Israeli Set Up: Use the setup from Scenario 6.1 for the Golan

.Israeli Player Display:

Israel: 3x Mirage IIICJ, 1x Nesher, 2x A-4E, 4x A-4H Workshop Box: 1x F-4E Repl, 1x A-4E/H Repl Airlift Points: 3

Israeli Reinforcements: Do not use the Israeli Order of Arrival. Use the below instead: 6 Oct 73

Any HQ: Zvika C Arm TF (2.1b)

7 Oct 73

Israel: 8x F-4E, 2x A-4E, 2x A-4N

Add: 8x Arty Points

I: 36 Div (12/1, 51/1 Inf Bn, 17/1 Inf Bn (-))

J: 210 Div (57/679, 93/679, 289/679 C Arm Bn)

K: 210 Div (HQ (Fresh), 134 Rec, 39/4, 96/179, 266/179, 278/179 C Arm Bn, 95/4, 377/9 S Arm Bn, Combat Trains)

8 Oct 73

Remove: Zvika Arm TF

Add: 1x Arty Point

L: 146 Div (HQ (Fresh), 288 Rec, 94/205, 61/205, 125/205 C Arm Bn, 181 S Arm Bn, 58/670, 83/670 Mech Bn, Combat Trains)

9 Oct 73

Remove: 36 Div (82/188 C Arm Bn)

36 Div HQ: 36 Div (Ben-Hanan C Arm TF)

10 Oct 73

36 Div HQ: 36 Div (269 Mktl Cdo Co, Katz C Arm TF)

210 Div HQ: 210 Div (42/4, 127/4, 11/9, 91/9 Mech Bn)

J: 317 Para Bde (HQ (Fresh), 471, 567 Abn Bn, Combat Trains)

12 Oct 73

210 Div HQ: 210 Div (Nati C Arm TF)

14 Oct 73

Remove: 2x Arty Points

16 Oct 73

Remove: 1x Arty Point

17 Oct 73

36 Div HQ: 36 Div (13/1 Inf Bn)

20 Oct 73

Remove: 210 Div (96/179 C Arm Bn)

21 Oct 73

Workshop Box: 1x F-4E and 1x A-4E/H Repls

22 Oct 73

Workshop Box: 1x F-4E and 1x A-4E/H Repls

23 Oct 73

Workshop Box: 1x F-4E and 2x A-4E/H Repls

Arab Set Up: Use the setup as Scenario 6.1 for the Golan and Syrian side of the Arab Player Display.

Arab Reinforcements: Use the Arab Order of Arrival for units arriving in the Golan and Syrian side of the Arab Player Display.

VoT 6.4 Duel for the Golan (Small)

This scenario covers just the opening days of the war along the Golan Front. The focus is on the Syrian offensive to reach the Jordan River and the Israeli response to recapture the Golan Heights. This became a desperate knife fight for both sides.

Playing Area: Golan Map First Turn: 6 Oct 73 Last Turn: 9 Oct 73 Turn Length: 4 First Player: Arab

Victory Conditions: Use the Golan-related game victory conditions (4.1). If Sudden Death (4.1e) is not achieved, then determine the winner by a modified Normal Victory Determination at the end of the scenario:

Syrian Victory: If the Arabs control 5 or more VPs at the end of the game.

Draw: If the Arabs control 3 or 4 VPs at the end of the game.

Israeli Victory: If the Arabs control 2 or less VPs at the end of the game.

Israeli Set Up: Use the setup from Scenario 6.1 for the Golan.

Israeli Player Display:

Israel: 3x Mirage IIICJ, 1x Nesher, 2x A-4E, 4x A-4H Workshop Box: 1x F-4E Repl, 1x A-4E/H Repl Airlift Points: 0

Israeli Reinforcements: Do not use the Israeli Order of Arrival. Use the below instead:

6 Oct 73

Any HQ: Zvika C Arm TF (2.1b)

7 Oct 73

Israel: 8x F-4E, 2x A-4E, 2x A-4N

Add: 8x Arty Points

I: 36 Div (12/1, 51/1 Inf Bn, 17/1 Inf Bn (-))

J: 210 Div (57/679, 93/679, 289/679 C Arm Bn)

K: 210 Div (HQ (Fresh), 134 Rec, 39/4, 96/179, 266/179, 278/179 C Arm Bn, 95/4, 377/9 S Arm Bn, Combat Trains)

8 Oct 73

Remove: Zvika Arm TF

Add: 1x Arty Point

L: 146 Div (HQ (Fresh), 288 Rec, 94/205, 61/205, 125/205 C Arm Bn, 181 S Arm Bn, 58/670, 83/670 Mech Bn, Combat Trains)

9 Oct 73

Remove: 36 Div (82/188 C Arm Bn)

36 Div HQ: 36 Div (Ben-Hanan C Arm TF)

Arab Set Up: Use the setup as Scenario 6.1 for the Golan and Syrian side of the Arab Player Display.

Arab Reinforcements: Use the Arab Order of Arrival for those units arriving in the Golan and Syrian side of the Arab Player Display.

VoT 6.5 Iraqi Intervention (Medium)

The Israelis conducted a counteroffensive into Syria after stopping the threat in the Golan Heights. With forces moving towards Damascus, a new enemy appeared that would divert the Israeli’s attention: the Iraqis had arrived. Followed later by a Jordanian contingent, the Arabs were joining forces again to defeat their common enemy.

Playing Area: Golan Map First Turn: 12 Oct 73 Last Turn: 16 Oct 73 Turn Length: 5 First Player: Arab

Victory Conditions: Use the Golan-related game victory conditions (4.1). The Syrians highest single turn total of VPs is 5. No Syrian Strategic Reserve Groups have been released.

Israeli Set Up:

Israeli Player Display:

Israel: 8x F-4E (Two Reduced), 3x Mirage IIICJ, 1x Nesher, 4x A-4E, 4x A-4H (Two Reduced), 2x A-4N (One Reduced) Workshop Box: 1x F-4E Airlift Points: 3

36 Div:

43.21: HQ (Fat-2, 4 Arty Points)
47.26: 269 Mtkl Cdo Co
49.19: 12/1 Inf Bn
48.25: 17/1 Inf Bn (-) [2]
48.26: 51/1 Inf Bn [4]
50.19: Tiger C Arm Co
45.17: Ben-Hanan C Arm TF
51.17: Katz C Arm Bn [2]
50.17: 77/7 C Arm Bn [2]
46.16: 75/7 Mech Bn [3]
47.18: H/74 Arm Co
39.22: Combat Trains Dead Pile: 71/7 C Arm Bn, A/53, B/53, C/53, F/74, G/74 C Arm Co

210 Div:

39.21: HQ (Fat-1, 3 Arty Points)
40.15: Nati C Arm TF
41.18: 134 Rec C Arm Bn [2]
31.22: 127/4 Mech Bn
31.21: 39/4 C Arm Bn [1]
27.21: 95/4 S Arm Bn [3]
28.21: 42/4 Mech Bn
42.13: 377/9 S Arm Bn [3]
39.20: 11/9 Mech Bn
40.18: 96/179 C Arm Bn [1]
42.14: 278/179 C Arm Bn [1], 91/9 Mech Bn
41.15: 93/679 C Arm Bn [1]
39.16: 289/679 C Arm Bn [1]
37.28: Combat Trains Dead Pile: 266/179, 57/679 C Arm Bn

317 Para Bde:

36.22: HQ (Fresh), 471 Abn Bn
35.23: 567 Abn Bn
32.25: Combat Trains

146 Div:

21.21: HQ (Fat-2, 2 Arty Points)
23.18: 288 Rec C Arm Bn [3]
26.20: 61/205 C Arm Bn [2]
20.20: 94/205 C Arm Bn [1]
22.18: 125/205 C Arm Bn [1]
18.20: 181 S Arm Bn [2], 83/670 Mech Bn
17.21: 58/670 Mech Bn
16.22: Combat Trains

Formation Activation Markers in Play: 36 Div, 146 Div, 210 Div, 317 Para Bde

Israeli Reinforcements: Do not use the Israeli Order of Arrival. Use the below instead: 14 Oct 73

Remove: 2x Arty Points

16 Oct 73

Remove: 1x Arty Point

Arab Set Up:

Arab Player Display:

Syria: 5x MiG-21 (Three Reduced), 3x MiG-17 (Three Reduced), 1x Iraqi MiG-21, 1x Iraqi MiG-17 (Reduced), 2x Iraqi Su-7 (Both Reduced), (1x Su-20 has been eliminated)

Unreleased Strategic Reserve: Group 1: 62 Syrian Inf Bde (HQ (Fat-0), IV Arm Bn, 420, 424, 622 Inf Bn, Combat Trains) Group 2: 90 Syrian Inf Bde (HQ (Fat-0), 491 Arm Bn, 493, 495, 496 Inf Bn, Combat Trains) Group 3: Assad Syrian Tk Bde (HQ (Fresh), II, III Arm Bn, IV Mech Bn, Combat Trains)

Golan Front: Syrian unless otherwise noted. 1 Tk Div: Destroyed.

3 Tk Div (-):

61.03: HQ (Fat-0), 273/21 Arm Bn (Support)
59.04: AT ATGM Bn
60.08: 354/65 Arm Bn, IV/65 Mech Bn
60.11: 363/65 Arm Bn
58.06: 365/65 Arm Bn
55.03: 112/21 Mech Bn
56.05: 161/21 Mech Bn
58.03: 246/21 Mech Bn
62.02: Combat Trains

Cdo Grp:

53.24: HQ (Fat-2), 122 Cdo Bn
50.26: 87 Rec Cdo Bn [2]
50.24: 1/82 Abn Co, 82 Abn Bn (-) [2]
50.23: 83 Cdo Bn
50.25: 133 Cdo Bn
55.13: Combat Trains

7 Inf Div:

51.10: HQ (Fat-3), Tank Arm Bn (+) [2] (Support)
53.16: 183 Cdo Bn [1]
46.13: 174/121 Mech Inf Bn [2], 549 ATGM Rgt
46.12: 178/121 Mech Inf Bn [2], 65 ATGM Rgt
47.13: 179/121 Mech Inf Bn [2]
51.14: 151/68 Inf Bn [3]
49.11: 241/68 Inf Bn [3]
52.15: 282/68 Inf Bn [3], AT ATGM Bn
43.08: 333/85 Inf Bn [3]
41.08: 334/85 Inf Bn [3]
44.10: 337/85 Inf Bn [3]
51.19: 12 Moroccan Inf Rgt [3]
55.07: Combat Trains Dead Pile: I/Assad, I/78, II/78, III/78, 172/81, 259/81, 283/81, IV/121 Arm Bn, 6 Moroccan Arm Bn, IV/78, 214/81 Mech Inf Bn

9 Inf Div:

30.13: HQ (Fat-3), Tank Arm Bn (+) [2] (Support), 412 Palestinian Cdo Bn [1]
38.10: 211/43 Arm Bn [1]
37.13: IV/43 Mech Inf Bn [2]
25.18: 187/33 Inf Bn [4], AT ATGM Bn [1]
26.19: 243/33 Inf Bn [4]
27.19: III/33 Inf Bn [4]
33.19: 114/52 Inf Bn [3]
36.18: 159/52 Inf Bn [3]
37.15: 222/52 Inf Bn [3]
28.04: Combat Trains Dead Pile: 212/43, III/43, 451/51, 452/51, 453/51 Arm Bn, 454/51 Mech Inf Bn

5 Inf Div:

18.12: HQ (Fat-3), Tank Arm Bn (+) [2] (Support), 413 Palestinian Cdo Bn [1]
15.18: 74/61 Inf Bn [4]
16.19: 320/61 Inf Bn [4]
18.18: 323/61 Inf Bn [4], AT ATGM Bn [1]
20.15: 171/112 Inf Bn [4]
21.17: 271/112 Inf Bn [4]
23.16: 287/112 Inf Bn [4]
12.02: Combat Trains Dead Pile: 203/12, 355/12, 356/12, 152/47, 154/47, 499/47, 287/132 Arm Bn, 346/12, 393/47, 199/132, 262/132, 328/132 Mech Bn

Formation Activation Markers in Play: Cdo Grp, 3 Tk Div (-), 5 Inf Div, 7 Inf Div, 9 Inf Div

Arab Reinforcements: Do not use the Arab Order of Arrival. Use the below instead:

12 Oct 73

N: 3 Iraqi Arm Div (HQ (Fat-0), Mut/12, Qtb/12 Arm Bn, 1/6, 2/8 Mech Bn, Combat Trains)

13 Oct 73

M: 3 Jordanian Arm Div (HQ (Fat-0), 2/40, 4/40 Arm TF, 1/40 Mech TF, Combat Trains)

15 Oct 73

Add: 4x Arty Points

3 Iraqi Div HQ: 3 Iraqi Arm Div (Khd/6, Mkd/6, Ymk/6, Qad/12, 3/8 Arm Bn, 1/8, 3/8, 3/12 Mech Bn)

16 Oct 73

3 Iraqi Div HQ: 3 Iraqi Arm Div (1/20, 2/20, 3/20 Inf Bn)

M: KAA Arab Mech Bde (HQ (Fresh), 1 Arm Cav Bn, 4 Abn Bn, Combat Trains)

VoT 6.6 Aryeh Dov (Small)

Israeli Command had sought to counterattack the Egyptian crossing with heavy airstrikes and a blitzkrieg type armor attack to cause the type of panic seen in the Six Day War in 1967. If the victory conditions seem tough, these were the historical expected objectives by Gonen, Southern Command Commander, to the division commanders Adan and Sharon. The objectives continued to change through the day to add to the confusion. The Egyptians stood their ground, and the result was an embarrassing defeat for the Israelis and a deeper respect for the enemy.

Playing Area: Map B First Turn: 8 Oct 73 Last Turn: 9 Oct 73 Turn Length: 2 First Player: Israeli Additional Supply Sources: B28.35, B43.35, B53.01 (Israelis)

Victory Conditions: The Israelis win if they occupy at least two of the following three forts: Hizayon (B22.26), Purkan (B20.21), and Matzmed (B23.10), as well as have at least 3x Armor units (of any size and remaining number of steps) and a Divisional HQ (all from one Division) west of the canal, with a Complete MSR by the end of the game.

Israeli Set Up: Units not listed are not used in the scenario.

Israeli Player Display:

Israel: 8x F-4E, 4x Nesher, 4x A-4E, 4x A-4H (Two Reduced), 2x A-4N, 2x Sa’ar (Two Reduced) Airlift Points: 0

Independents:

B22.26: Hizayon Fort
B20.21: Purkan Fort
B23.10: Matzmed Fort
B26.08: Lakekan Fort

143 Div:

B36.20: HQ (Fresh, 1x Arty Point)
B35.16: 87 M Arm Cav Bn
B26.23: 79/14 M Arm Bn [1]
B31.13: 184/14 M Arm Bn [2]
B26.26: 196/14 M Arm Bn [1]
B37.28: 264/421 M Arm Bn
B43.27: 257/421 M Arm Bn
B29.29: 599/421 M Arm Bn
B44.17: 407/600 Arm Bn
B47.14: 409/600 Arm Bn
B43.18: 410/600 Arm Bn
B50.17: Combat Trains

162 Div: (126 C Arm Bn is not in play)

B32.29: HQ (Fresh)
B28.35: 113/217 C Arm Bn, 142/217 C Arm Bn, 19/460 M Arm Bn [2], 198/460 C Arm Bn [2], 86/460 Mech Bn, 189 Rec Mech Bn(-))
B43.35: 429/500 C Arm Bn, 430/500 C Arm Bn, 433/500 C Arm Bn
B43.31: Combat Trains

Formation Activation Markers in Play: 143 Div, 162 Div

Israeli Reinforcements: None.

Arab Set Up: All units are Egyptian. Arab Player Display:

Egypt: 6x MiG-21 (A/S, Four Reduced), 1x MiG-21 (A/S and CAS), 1x MiG-17 (A/S, Reduced), 2x MiG-17 (CAS, Two Reduced), 2x Su-7 (One Reduced), 1x Hunter

2 Inf Div:

B22.24: HQ (Fat-0, PD), 33 ATGM Bn, 364 AT Bn, Tank Arm Bn (+) (All Three in Support), 102 Arm Cav Bn
B22.25: 239 Arm Bn
B21.22: 221 SU Arm Bn
B23.24: 360/117 Mech Inf Bn
B23.25: 361/117 Mech Inf Bn
B23.26: 362/117 Mech Inf Bn
B21.21: 13 Cdo Bn
B22.21: 10/4 Inf Bn
B23.22: 11/4 Inf Bn
B23.23: 12/4 Inf Bn
B23.27: 507/120 Inf Bn
B23.28: 508/120 Inf Bn
B23.29: 509/120 Inf Bn
B13.28: Combat Trains

24 Tk Bde:

B22.23: HQ (Fat-0), 248 Arm Bn, 252 Arm Bn
B22.22: 253 Arm Bn, 268 Mech Inf Bn
B13.31: Combat Trains

16 Inf Div:

B24.13: HQ (Fat-0, PD), 35 ATGM Bn, 646 AT Bn, Tank Arm Bn (+) (All Three in Support), 216 Arm Bn
B24.12: 26 Arm Cav Bn
B23.11: 296 T100 Arm Bn
B25.13: 7/3 Mech Inf Bn
B25.14: 8/3 Mech Inf Bn
B25.15: 9/3 Mech Inf Bn
B22.17: 73 Cdo Bn
B24.10: 16/16 Inf Bn
B25.11: 17/16 Inf Bn
B25.12: 18/16 Inf Bn
B25.16: 334/112 Inf Bn
B24.16: 335/112 Inf Bn
B23.17: 336/112 Inf Bn
B17.10: Combat Trains

21 Tk Div:

B23.15: HQ (Fat-0), 200/14 Arm Bn, 201/14 Arm Bn
B23.14: 203/14 Arm Bn, 260/14 Mech Inf Bn
B15.19: Combat Trains

Formation Activation Markers in Play: 21 Tk Div, 24 Tk Bde, 2 Inf Div, 16 Inf Div

Arab Reinforcements: None.

VoT 6.7 Operation Stouthearted Men (Medium)

After discovering the seam between the Egyptian Second and Third Armies, the desired counterattack to cross the Suez Canal was launched a day after the failed Egyptian Armored Offensive. The fighting would revolve around the Chinese Farm, so-named after misidentifying Japanese characters on irrigation equipment after the Israelis had occupied the Sinai in 1967. The battle was intense, with stubborn resistance by the Egyptians while the Israelis tried pushing them away to establish and hold a bridgehead west of the Suez Canal.

Playing Area: Map B south of XX.21 inclusive First Turn: 15 Oct 73 Last Turn: 19 Oct 73 Turn Length: 5 First Player: Israeli Additional Supply Sources:

B42.21, B41.01, B53.01 (Israelis) B20.01, B22.21, B31.01 (Arabs)

Victory Conditions: Use the Sinai-related game victory conditions for counting victory points (4.1). No Egyptian Strategic Reserve Groups have been released. The Israeli player must have at least 3x Armor units (of any size and remaining number of steps) and a Divisional HQ (all from one Division) west of the canal, with a Complete MSR.

Israeli Set Up: Units not listed are not used in the scenario.

Israeli Player Display:

Israel: 8x F-4E (Three Reduced), 4x Nesher, 4x A-4E, 4x A-4H (Three Reduced), 2x A-4N (One Reduced), 2x Sa’ar (Two Reduced) Airlift Points Available: 2

143 Div:

B36.16: HQ (Fat-0, 2 Arty Points)
B33.10: 87 M Arm Cav Bn, 79/14 M Arm Bn [2]
B33.11: 184/14 M Arm Bn [2], 407/600 M Arm Bn
B33.12: Shmulik Abn TF, (424 Shkd Arm Cav Bn (-) (Assigned to 143 Div))
B32.12: 582 Shun Abn Bn
B33.16: 264/421 M Arm Bn, 634 Ferry Bn (Assigned to 143 Div)

B35.16: 257/421 M Arm Bn, 605 Bridge Bn (Assigned to 143 Div)

B34.15: 599/421 M Arm Bn [2], 630 Bridge Bn (Assigned to 143 Div)

B30.14: 409/600 Arm Bn
B30.15: 410/600 Arm Bn [2]
B41.18: Combat Trains

162 Div:

B42.19: HQ (Fat-1, 1 Arty Point)
B46.14: 189 Rec Mech Bn (-), Lapidot M Arm TF (Assigned to 162 Div)
B48.11: 113/217 C Arm Bn [2], 126/217 C Arm Bn [2]
B49.12: 142/217 C Arm Bn, Wnr/217 Abn Co
B48.12: 19/460 M Arm Bn [2]
B48.13: 100/460 M Arm Bn
B47.14: 198/460 C Arm Bn [2], 86/460 Mech Bn
B30.21: 429/500 C Arm Bn
B41.20: 430/500 C Arm Bn [2]
B42.20: 433/500 C Arm Bn [2]
B47.19: Combat Trains

247 Para Bde:

B32.14: HQ (Fresh), 565 Abn Bn
B32.15: 416 Abn Bn
B41.17: Combat Trains

Formation Activation Markers in Play: 143 Div, 162 Div, 247 Para Bde

Israeli Reinforcements: Do not use the Israeli Order of Arrival. Use the below instead: 17 Oct 73

Enter via Airlift: 35 Para Bde (HQ (Fat-0), 890 Abn Bn) Any eligible hex: 35 Para Bde (Combat Trains)

18 Oct 73

At 143 Div HQ: 88 DvL Amphib Rec Bn

At 162 Div HQ: 162 Div (271 Mech Eng Bn)

B41.01: 252 Div (HQ (Fat-0) 106/164 [2], 183/164 [2] C Arm Bn, 46/401 [2], 95/401 [2] M Arm Bn, Combat Trains)

Arab Set Up: Egyptian unless otherwise noted. Units not listed are not used in the scenario.

Arab Player Display:

Egypt: 4x MiG-21 (A/S, One Reduced), 1x MiG-21 (A/S and CAS), 1x MiG-17 (A/S, Reduced), 2x MiG-17 (CAS, Two Reduced), 2x Su-7 (Two Reduced), 1x Hunter, 1x Mirage 5, 1x Arab MiG-21 (Reduced), 1x Arab MiG-17 (Reduced), 1x Arab Su-7 (Reduced)

Unreleased Strategic Reserve: Group 1: 182 Para Bde (HQ (Fresh), 38 ATGM Bn, 81, 85, 89 Abn Bn, Combat Trains), 3 Mech Div (HQ (Fresh), 229/23, 254/23, 255/23 Arm Bn, 267/23 Mech Bn, Combat Trains)

Group 2: 139 Cdo Grp (HQ (Fresh), 39 ATGM Bn, 133, 223 Cdo Bn, Combat Trains), 35 Tk Bde (HQ (Fresh), 283, 284, 285 Arm Bn, 270 Mech Bn, Combat Trains)

Group 3: 170 Para Bde (HQ (Fresh), 645 ATGM Bn, 75, 77, 79 Abn Bn, Combat Trains), 27 Nasr Tk Bde (HQ (Fresh), 10, 11, 12 Arm Bn, 290 Mech Bn, Combat Trains)

Group 4: 3 Mech Div (3 Arm Cav Bn, 30 ATGM Bn, 217/10, 227/114 Arm Bn, 30/10, 31/10, 32/10, 340/114, 341/114, 342/114 Mech Bn)

Unassigned Independents:

B17.04: 329/AJ Palestinian Static Bn
B18.03: 339/AJ Palestinian Static Bn
B19.03: 349/AJ Palestinian Static Bn

16 Inf Div:

B24.16: HQ (Fat-1, PD), 35 ATGM Bn, 646 AT Bn, Tank Arm Bn (+) [6] (All Three in Support), 216 Arm Bn
B23.14: 26 Arm Cav Bn
B24.17: 296 T100 Arm Bn
B28.16: 7/3 Mech Inf Bn
B26.16: 8/3 Mech Inf Bn
B25.15: 9/3 Mech Inf Bn
B27.19: 73 Cdo Bn
B27.12: 16/16 Inf Bn
B25.13: 17/16 Inf Bn
B25.11: 18/16 Inf Bn
B30.17: 334/112 Inf Bn [5]
B28.20: 335/112 Inf Bn [5]
B29.19: 336/112 Inf Bn [5]
B17.10: Combat Trains

21 Tk Div:

B21.18: HQ (Fat-2), 9 Arm Cav Bn
B21.19: 654 ATGM Bn
B21.20: 204/1 Arm Bn [2], 205/1 Arm Bn [2]
B21.21: 206/1 Arm Bn [2], 259/1 Mech Bn [4]
B25.21: 200/14 Arm Bn [1]
B25.20: 201/14 Arm Bn [1]
B24.20: 203/14 Arm Bn [1], 260/14 Mech Inf Bn [3]
B22.17: 243/18 Arm Bn, 52/18 Mech Bn
B23.18: 53/18 Mech Bn
B23.17: 70/18 Mech Bn
B21.14: Combat Trains

23 Mech Div (-):

B12.20: HQ (Fresh, HQ is Done), 350/116 Mech Bn
B15.20: 231/116 Arm Bn
B11.19: 351/116 Mech Bn
B8.16: 352/116 Mech Bn
B1.20: Combat Trains

Formation Activation Markers in Play: 21 Tk Div, 23 Mech Div (-), 16 Inf Div

Arab Reinforcements: 17 Oct 73

B31.01: 25 Tk Bde (HQ (Fat-2), 275, 276 [2], 277 [2] Arm Bn, 269 Mech Bn, Combat Trains)

18 Oct 73

Egypt: 1x MiG-21 (Reduced), 1x Su-20 (Reduced), 1x L-29 (Reduced)

B20.01: 4 Tk Div (HQ (Fat-1), 207/2, 208/2, 209/2 Arm Bn, 261/2 Mech Bn, Combat Trains)

B22.21: 24 Tk Bde (HQ (Fat-2), 248 [2], 252 [2], 253 [2] Arm Bn, 268 Mech Bn [4], Combat Trains)

VoT 6.8 Africa (Large)

Following the successful crossing of the Suez, the Israelis sought to breakout from their tenuous bridgehead and take the war into the African side of Egypt. The aim was to surround and cut off the Third Army. The Egyptians had to call on their General HQ reserves to stop the Israelis. Through confusion and denial, the response was muddled until it was almost too late. The race was on before the UN ceasefire.

Playing Area: Maps B and C First Turn: 20 Oct 73 Last Turn: see 4.2 First Player: Israeli Additional Supply Sources: B28.35, B43.35 (Israelis)

Victory Conditions: Use the Sinai-related game victory conditions for counting victory points (4.1). The Egyptians start with 1 VP (which cannot be lost) in addition to all the controlled VPs in the playing area.

Israeli Set Up: Units not listed are not used in the scenario.

Israeli Player Display:

Israel: 8x F-4E (Three Reduced), 4x Nesher, 4x A-4E (One Reduced), 4x A-4H (Three Reduced), 2x A-4N (One Reduced), 2x Sa’ar (Two Reduced) Airlift Points Available: 1

SAM Control Destroyed Markers: B9.15, B16.04 (2 for the SEAD Track)

Unassigned Independents:

C62.27: 1/Bishof Static Co
C62.14: 2/Bishof Static Co

Nammer TF:

B28.35: HQ (Fat-1), Combat Trains
B29.32: 226/11 S Arm Bn [3]
B28.34: Vilner Inf TF, 54/11 Mech Bn
B29.29: 128/11 Mech Bn

274 Arm Bde:

B34.20: HQ (Fat-1, 1 Arty Asset)
B31.25: 25 T Arm Bn [2]
B30.21: 227 T Arm Bn
B30.15: 228 T Arm Bn
B42.19: Combat Trains

143 Div:

B23.10: HQ (Fat-1, 2 Arty Assets)
B18.11: 582 Shun Abn Bn [5]
B16.11: Shmulik Abn TF [5]
B19.14: 79/14 M Arm Bn [2]
B26.08: 184/14 M Arm Bn [1]
B13.14: 264/421 M Arm Bn [2], 599/421 M Arm Bn [1]
B25.13: 409/600 M Arm Bn [2]
B24.12: 410/600 M Arm Bn [2]
B16.13: 88 DvL Amphib Rec Bn [2] (Assigned to 143 Div)
B17.14: 424 Shkd Cav Bn (-) [3] (Assigned to 143 Div)
B22.11: 634 Ferry Bn [1] (Assigned to 143 Div, Emplaced)
B22.10: 605 Bridge Bn (Assigned to 143 Div, Emplaced)
B22.09: 630 Bridge Bn (Assigned to 143 Div, Emplaced)
B35.16: Combat Trains Dead Pile: 87 M Arm Cav Bn, 257/421 M Arm Bn, 407/600 M Arm Bn

35 Para Bde:

B22.13: HQ (Fat-1), 890 Abn Bn (-) [3]
B21.14: 48 Abn Bn, 469 Abn Bn
B25.11: Combat Trains

247 Para Bde:

B22.12: HQ (Fat-2), 416 Abn Bn [4], 565 Abn Bn [4]
B25.10: Combat Trains

252 Div:

B16.09: HQ (Fat-0)
B9.09: 183/164 C Arm Bn [2]
B9.08: 106/164 C Arm Bn [2]
B11.10: 46/401 M Arm Bn [2]
B11.11: 195/401 M Arm Bn [2]
B24.10: Combat Trains Dead Pile: 104/164 C Arm Bn

162 Div:

B11.04: HQ (Fat-0, 2 Arty Assets), 271 Mech Eng Bn, 50 Abn Bn (Assigned to 162 Div)
C13.34: 126/217 C Arm Bn [1]
C14.34: 113/217 C Arm Bn [2]
C12.33: 142/217 C Arm Bn [2], Wnr/217 Abn Co
B17.06: 86/460 Mech Bn, Lapidot M Arm TF (Assigned to 162 Div)
C9.33: 19/460 M Arm Bn [1], 189 Rec Mech Bn (-)
C8.33: 100/460 M Arm Bn
C8.32: 198/460 C Arm Bn [2]
C10.32: 430/500 C Arm Bn [2]
C9.32: 433/500 C Arm Bn [2]
B17.10: 429/500 C Arm Bn [2], Combat Trains

440 Div:

C45.17: HQ (Fat-0), 9400 Inf Bn
C47.11: 450 Abn Bn
C43.06: A/225 Arm Bn (-), 202 Abn Bn (-)
C47.08: 182 S Arm Bn
C47.16: 52 M Arm Bn [2]
C45.29: 129/875 S Arm Bn [3]
C44.28: 89/875 Mech Bn
C44.25: 121/875 Mech Bn
C56.16: Combat Trains

Formation Activation Markers in Play: 143 Div, 162 Div, 252 Div, 440 Div, Nammer TF, 274 Arm Bde, 35 Para Bde, 247 Para Bde

Israeli Reinforcements: Do not use the Israeli Order of Arrival. Use the below instead:

20 Oct 73

A, B, or C (Use only one): Sela TF (Sela TF HQ (Fresh), 105/5, 171/5, 172/5, 173/5 Inf Bn Sela TF Combat Trains), 484 Harv Arm Cav Bn (Assigned to Sela TF), Yaron Abn TF (Assigned to Sela TF)

21 Oct 73

Workshop Box: 1x F-4E and 1x A-4E/H Repls

22 Oct 73

Workshop Box: 1x F-4E and 2x A-4E/H Repls

Any HQ: Hisdai Abn TF

252 Div HQ: 252 Div (96/179 C Arm Bn [2])

23 Oct 73

Workshop Box: 1x F-4E and 2x A-4E/H Repls

Any HQ: 564 Abn Bn

440 Div HQ: 440 Div (B/225 Arm TF)

Arab Set Up: Egyptian unless otherwise noted. Units not listed are not used in the scenario.

Arab Player Display:

Egypt: 4x MiG-21 (A/S, Three Reduced), 1x MiG-21 (A/S and CAS, Reduced), 1x MiG-17 (CAS, Reduced), 1x Su-7 (Reduced), 1x Su-20 (Reduced), 1x L-29 (Reduced), 1x Hunter, 1x Mirage 5, 1x Arab MiG-21 (Reduced), 1x Arab MiG-17 (Reduced), 1x Arab Su-7 (Reduced)

Unreleased Strategic Reserve: Group 3: 170 Para Bde (HQ (Fresh), 645 ATGM Bn, 75, 77, 79 Abn Bn, Combat Trains), 27 Nasr Tk Bde (HQ (Fresh), 10, 11, 12 Arm Bn, 290 Mech Bn, Combat Trains) Group 4: 3 Mech Div (3 Arm Cav Bn, 30 ATGM Bn, 217/10, 227/114 Arm Bn, 30/10, 31/10, 32/10, 340/114, 341/114, 342/114 Mech Bn)

25 Tk Bde: Destroyed.

Unassigned Independents:

B17.04: 329/AJ Palestinian Static Bn
B18.03: 339/AJ Palestinian Static Bn
B19.03: 349/AJ Palestinian Static Bn
C21.34: 359/AJ Palestinian Static Bn
C25.33: 5/Ymk Arab Static Bn
C36.12: Militia Static Bn

2 Inf Div:

B25.27: HQ (Fat-2, PD), 33 ATGM Bn [5], 364 AT Bn, Tank Arm Bn (+) [6] (All Three in Support), 102 Arm Cav Bn
B26.26: 239 Arm Bn [2]
B23.34: 221 SU Arm Bn
B28.27: 360/117 Mech Inf Bn [4]
B27.29: 361/117 Mech Inf Bn [4]
B25.30: 362/117 Mech Inf Bn [4]
B26.23: 13 Cdo Bn [2]
B27.22: 10/4 Inf Bn [5]
B28.23: 11/4 Inf Bn [5]
B28.25: 12/4 Inf Bn [5]
B26.31: 507/120 Inf Bn [5]
B27.33: 508/120 Inf Bn [5]
B26.34: 509/120 Inf Bn [5]
B13.28: Combat Trains

24 Tk Bde:

B23.23: HQ (Fat-4), 252 Arm Bn [1]
B22.22: 248 Arm Bn [1]
B24.22: 253 Arm Bn [1]
B22.23: 268 Mech Inf Bn [2]
B21.26: Combat Trains

16 Inf Div:

B24.17: HQ (Fat-4, PD), 35 ATGM Bn, 646 AT Bn, Tank Arm Bn [2] (All Three in Support)
B28.16: 7/3 Mech Inf Bn [3]
B26.15: 8/3 Mech Inf Bn [3]
B25.17: 9/3 Mech Inf Bn [3]
B24.14: 16/16 Inf Bn [1], 26 Arm Cav Bn [1]
B25.15: 17/16 Inf Bn [1]
B23.15: 18/16 Inf Bn [1], 216 Arm Bn [1]
B22.15: 73 Cdo Bn [1], 296 T100 Arm Bn [1]
B30.17: 334/112 Inf Bn [3]
B28.20: 335/112 Inf Bn [3]
B29.19: 336/112 Inf Bn [3]
B17.22: 16 Inf Combat Trains, 21 Tk Combat Trains

21 Tk Div:

B23.20: 21 Tk HQ (Fat-4), 243/18 Arm Bn [1] (Support), 9 Arm Cav Bn [2]
B22.16: 654 ATGM Bn [1]
B22.20: 204/1 Arm Bn [1]
B21.20: 205/1 Arm Bn [1]
B22.21: 206/1 Arm Bn [1]
B21.21: 259/1 Mech Bn [2]
B25.21: 200/14 Arm Bn [1]
B25.20: 201/14 Arm Bn [1]
B24.20: 203/14 Arm Bn [1], 260/14 Mech Inf Bn [2]
B22.18: 52/18 Mech Bn [2]
B23.18: 53/18 Mech Bn [2]
B24.18: 70/18 Mech Bn [2] See 16 Inf Div above: Combat Trains

182 Para Bde:

B20.17: HQ (Fat-2), 38 ATGM Bn [1] (Support)
B19.17: 81 Abn Bn [4]
B20.16: 85 Abn Bn [4]
B21.17: 89 Abn Bn [4]
B16.21: Combat Trains

139 Cdo Grp:

B18.19: HQ (Fat-2), 39 ATGM Bn [1] (Support)
B17.19: 133 Cdo Bn [2]
B18.18: 223 Cdo Bn [2]
B13.23: Combat Trains

23 Mech Div (-):

B6.20: HQ (Fat-3), 249/118 Arm Bn (Support), 32 ATGM Bn, 500/118 Mech Bn
B9.21: 23 Arm Cav Bn
B3.14: 350/116 Mech Bn [2]
B3.16: 351/116 Mech Bn [2], 231/116 Arm Bn[1]
B4.17: 352/116 Mech Bn [2]
B12.21: 501/118 Mech Bn
B14.20: 502/118 Mech Bn
B5.24: Combat Trains

3 Mech Div:

B1.11: HQ (Fat-2)
B2.12: 255/23 Arm Bn [1]
B2.11: 267/23 Mech Bn [3]
B1.11: Combat Trains Dead Pile: 229/23 Arm Bn, 254/23 Arm Bn

35 Tk Bde:

B1.09: HQ (Fat-2)
B3.06: 283 Arm Bn
B3.08: 284 Arm Bn, 270 Mech Bn
B3.10: 285 Arm Bn
B1.09: Combat Trains

4 Tk Div (-):

C4.28: HQ (Fat-2), 8 Arm Cav Bn, 653 ATGM Bn, 211/6 Arm Bn (Support)
B6.02: 208/2 Arm Bn [1]
C6.34: 209/2 Arm Bn [1], 261/2 Mech Bn [3]
C10.30: 256/6 Mech Bn
C11.31: 257/6 Mech Bn
C12.30: 258/6 Mech Bn
C1.29: Combat Trains Dead Pile: 207/2 Arm Bn

130 Amph Bde:

C33.34: HQ (Fat-3), 603 Amphibious TF [3]
C31.32: 602 Amphibious TF [2]
C31.31: Combat Trains

3 Tk Bde:

C32.24: HQ (Fat-1), 241 Arm Bn [1]
C33.25: 240 Arm Bn [1]
C33.24: 242 Arm Bn [1]
C34.23: 262 Mech Bn [2]
C35.22: Combat Trains (Ghost)

6 Mech Div:

C30.16: HQ (Fat-1), 27 Arm Cav Bn, 247/113 Arm Bn (Support)
C24.19: 31 ATGM Bn [1]
C38.11: 225/22 Arm Bn [2], 250/22 Arm Bn [2]
C39.12: 251/22 Arm Bn [2], 266/22 Mech Inf Bn [4]
C20.21: 337/113 Mech Bn [4]
C23.22: 338/113 Mech Bn [4]
C37.21: 1/1 Mech Bn [2]
C37.22: 238/1 Arm Bn [1], 3/1 Mech Bn [2]
C37.23: 20/1 Mech Bn [2]
C30.10: Combat Trains (Ghost) Dead Pile: 339/113 Mech Bn

7 Inf Div: C38.24: HQ (Fat-3, PD),

34 ATGM Bn, 640 AT Bn, Tank Arm Bn (+) (All Three in Support), 119 Arm Cav Bn

C39.28: 226 Arm Bn [2]
C41.25: 295 T100 Arm Bn
C42.22: 292 SU Arm Bn
C42.28: 34/11 Mech Inf Bn [5]
C41.27: 35/11 Mech Inf Bn [5]
C42.25: 36/11 Mech Inf Bn [5]
C42.29: 33 Cdo Bn [2]
C38.31: 24/8 Inf Bn [5]
C40.31: 25/8 Inf Bn [5]
C41.30: 26/8 Inf Bn [5]
C43.21: 37/12 Inf Bn [5]
C43.22: 38/12 Inf Bn [5]
C42.23: 39/12 Inf Bn [5]
C30.24: Combat Trains

19 Inf Div:

C41.14: HQ (Fat-3, PD), 37 ATGM Bn, 641 AT Bn, Tank Arm Bn (+) (All Three in Support), 19 Arm Cav Bn
C42.17: 212 Arm Bn [2]
C40.08: 47 ISU Arm Bn
C45.12: 5/2 Mech Inf Bn [5]
C46.13: 6/2 Mech Inf Bn [5]
C45.15: 22/2 Mech Inf Bn [5]
C41.10: 43 Cdo Bn [2]
C37.10: 63 Cdo Bn
C38.17: 163 Cdo Bn
C43.16: 4/5 Inf Bn [5]
C44.18: 14/5 Inf Bn [5]
C45.20: 15/5 Inf Bn [5]
C41.07: 2/7 Inf Bn [5]
C43.07: 19/7 Inf Bn [5]
C45.08: 21/7 Inf Bn [5]
C43.13: 3 ATGM Rgt [2] (Assigned to 19 Inf)

C34.12: Combat Trains

Formation Activation Markers in Play: 130 Amph Bde, 4 Tk Div (-), 21 Tk Div, 3 Tk Bde, 24 Tk Bde, 35 Tk Bde, 3 Mech Div, 6 Mech Div, 23 Mech Div (-), 2 Inf Div, 7 Inf Div, 16 Inf Div, 19 Inf Div, 182 Para Bde, 139 Cdo Grp

Arab Reinforcements: 24 Oct 73

F or G: 8 Alg Arab Arm Bde (HQ (Fat-0), 2, 4, 10 Arm Bn, 9 Mech Bn, Combat Trains)

25 Oct 73

F or G: 3 Lib Arab Mech Bde (HQ (Fat-0), I, II, III Mech Bn, IV Arm Bn, Combat Trains)

26 Oct 73

F or G: 2 Moroccan Mot Bde (HQ (Fat-0), II Arm Co, I Inf Rgt, Combat Trains)

Glossary AJ Ain-Jalut Alg Algerian Amph Amphibious Arm Armor A/S Air Superiority Assad Rifaat al-Assad (Hafez al-Assad’s brother) AT Anti-Tank AT-1 “Snapper” ATGM(3M6 Schmel) AT-3 “Sagger” ATGM (9M14 Malyutka) Bde Brigade BMP “Boyevaya Moshina Piehoty” Infantry Fighting Vehicle Bn Battalion BRDM “Boyevaya Razvedyvatelnaya Dozornaya Mashina” or Combat Recon Patrol Vehicle CAS Close Air Support C Centurion Tank (Sho’t Kal or Sho’t Meteor) Cav Cavalry (or Recon) Cdo Commando Cmd Command Co Company Div Division DvL Dov Lavan (“Polar Bear”) Grp Group Harv Haruv (“Carob”) IAF Israeli Air Force IDF Israeli Defense Force Inf Infantry IFV Infantry Fighting Vehicle ISU Soviet ISU-152 Jahra Al-Jahra KAA King Adbulaziz Kdf Khudhaifa Khd Khalid KhW Khalid ibn al-Walid Lajat Extensive lava flow fields in Syria Lib Libyan M M48 (Magach-3) or M60A1 Tank (Magach-6) Ma’at Al ma’atsam Mech Mechanized Infantry Mhb Muhalib Mil Militia Mkd Mikdad Mtkl Sayeret Matkal Mot Motorized Mut Al Mu’tasim Mtn Mountain Myt Mythanna Nasr Nasser Para Parachute Plt Platoon Qad Qadisiyah Qtb Qutaiba Rec/Recon Reconnaissance Rfd Rafidain RPG “Ruchnoy Protivotankoviy Granatomyot” Rocket Propelled Grenade S Upgraded Sherman Tank (M-50 and M-51) SEAD Suppression of Enemy Air Defense Missions SAM Surface to Air Missile SF Special Forces Shkd Shaked (“Almond”) Shr Sharhabil Shun Shunari SU Soviet SU-100

T Tiran (upgraded captured T-54/55) T100 Modified T-34 with 100mm gun Ter Territorial TF Task Force Tk Tank Trq Tariq Tun Tunisian VCs Victory Conditions VPs Victory Points Wnr Weiner Ymk Yarmuk

Designer Notes by Carl Fung

The Journey

The Arab-Israeli Conflicts (the Yom Kippur War, in particular) have long fascinated me. Rather than studying for college midterms, I read Trevor Dupuy’s Elusive Victory in the school library. This segued into wargames with SCS’s Yom Kippur and Heights of Courage, The Arab- Israeli Wars, Crisis: Sinai 1973, Across Suez, Elusive Victory, Sinai, Suez ’73, and the original vivid and subsequent editions of Bar-Lev.

Valley of Tears has a long origin story. In 2003, I first started designing an OCS game covering the Arab-Israeli Wars from 1948 to 1973, similar to SPI’s Sinai when BCS was only a twinkle in Dean’s eye. The OCS design moved along slowly with a rough map and initial Order of Battle but made no real progress. I was concerned over the short number of turns for the 1956 and 1967 wars (only 2-3 turns each), and the start and stop operations of the 1948 war. The Yom Kippur War lasted 19 days and was more balanced, making it the only viable situation to depict using the OCS. The design languished until 2007 when Dean created his initial BCS drafts and proposed that I convert it to BCS. Because of the granular map and unit scales, I was immediately sold on the idea. Converting the game to BCS wasn’t difficult but had factors going against it. BCS was still in its infancy, and as early playtesters can attest, was constantly evolving every week. The series rules finally started to settle in as Last Blitzkrieg was designed, and I created the foundation for the Yom Kippur War design.

Fast forward to now and I offer for your consideration… Valley of Tears.

Research Breakthroughs

Around the time that Dean asked me to convert the design from OCS to BCS, numerous breakthroughs occurred in the available research materials. The Yom Kippur War, let alone any Arab-Israeli conflict, was notoriously difficult to find detailed information. Material was limited to a handful of sources available in English and oft repeated in other books. Numerous Yom Kippur War games were built using titles such as Dupuy’s

VoT Errata (6 Aug 24)

The following published errata (VOT_Errata, 6 Aug 24) are applied in the text of this document.

Rules: In the Terrain Effects Chart, note 5, “1/2 MA” should be “1/2 MP.”
Counters: None.
Scenarios: In any case where the listing for the Israeli Workshop Box lists F-4E and A-4E/H without any designator of Repl, it should read F-4E Repl and A-4E/H Repl where needed.

VoT Glossary

Abbreviation	Meaning
AJ	Ain-Jalut
Alg	Algerian
Amph	Amphibious
Arm	Armor
A/S	Air Superiority
Assad	Rifaat al-Assad (Hafez al-Assad’s brother)
AT	Anti-Tank
AT-1	“Snapper” ATGM(3M6 Schmel)
AT-3	“Sagger” ATGM (9M14 Malyutka)
Bde	Brigade
BMP	“Boyevaya Moshina Piehoty” Infantry Fighting Vehicle
Bn	Battalion

VoT Israeli Order of Arrival

Turn	Entry Area	Units
6 Oct 73	Any Golan HQ	Zvika C Arm TF (2.1b)
7 Oct 73	Israel	4x F-4E; 2x A-4E; 2x A-4N
7 Oct 73	Any	4x Arty Points
7 Oct 73	Any Golan HQ	4x Arty Points
7 Oct 73	Any Israeli Sinai Entry Hex	1/Bishof Static Co; 2/Bishof Static Co
7 Oct 73	275 Ter Bde HQ	Lapidot M Arm TF (Assigned to 275 Ter); 162 Div (198/460 M Arm Bn)
7 Oct 73	B42.19 (Tasa)	143 Div (79/14, 196/14 M Arm Bn)
7 Oct 73	A	162 Div (HQ (Fresh), 19/460 M Arm Bn, 113/217, 126/217, 142/217, 429/500, 430/500, 433/500 C Arm Bn, 86/460, 189 Rec Mech Bn, Combat Trains)

VoT Arab Order of Arrival

Units are Egyptian unless otherwise noted in the Formation Title (not each unit).

Turn	Entry Area	Units
6 Oct 73	N	1 Syrian Tk Div (HQ (Fresh), AT ATGM Bn, 377/76, 387/76, 397/76, 173/91, 242/91, 272/91, 370/58 Arm Bn, 381/76, 164/91, 360/58, 362/58, 364/58 Mech Bn, Combat Trains); 65 Syrian ATGM Bn (Assigned to 1 Syrian Tk Div)
6 Oct 73	w/i 1 G50.24	Cdo Grp (1/82 Para Co) (3.4b)
6 Oct 73	w/i 1 G10.27 or G19.33	1/411 PLA Cdo Co (3.4a)
7 Oct 73	Syria	1x Iraqi MiG-21
7 Oct 73	w/i 1 G23.20 or G30.27	2/411 PLA Cdo Co (3.4a)
7 Oct 73	7 Syrian Inf Div HQ	7 Syrian Inf Div (I/Assad, 172/81, 259/81, 283/81 Arm Bn, 214/81 Mech Bn)
7 Oct 73	O	3 Syrian Tk Div (-) (HQ (Fresh), AT ATGM Bn, 354/65, 363/65, 365/65, 273/21 Syrian Arm Bn, 112/21, 161/21, 246/21, IV/65 Mech Bn, Combat Trains)

VoT Terrain Effects Chart

Terrain	Leg	Tac	Truck	Terrain for Combat/Barrage	Blocking Terrain?	Key Terrain?
Open	1	2	2	Open	-	-
Cultivated/Irrigation	1	2	4	Yes	-	-
Sand Dunes	2	3	4	Open	-	-
Hill	ot	ot

ot: Use other terrain in the hex for this purpose.
STOP: See BCS 4.1e (Unit must have 4 MPs remaining to enter.)
[X]: Cost for Amphibious units (1.4a)
-: No Effect.
Open: Open is automatically trumped by ‘Yes’ Combat Terrain. If it isn’t trumped, then the “Hard Red AV in Open” DRM in Combat (a benefit) applies.
Yes: Terrain that applies the effect at the top of the chart.

No unit can Attack, Engage, Attack by Fire, Spot, or apply any ZOC across the Suez Canal unless it is through an operating Bridge (not Ferry) hexside.

Notes:

Apply BCS 4.1 (Movement), 4.5c (LOS), and 5.0a (Combat effects by type). In the case of Escarpment, Terrain for Combat ONLY applies if the Attack is coming FROM the hex containing the symbol through its hexside. Others apply as Terrain, only if the attack is allowed via a Bridge.
Suez Canal is Blocking due to the high embankments constructed before the war on each side to block observation.
These do not Block if the Firing or Spotting unit is on top of the feature and adjacent to its hexside. (Remember, you can always ‘see’ adjacent, regardless of direction here.)
Water Barrier hexsides count as +2 only if entering a non-Sea/Lake hex, otherwise they have no effect.
The AT Ditch hexsides do not block roads needed for MSR purposes and the roads do connect. So, moving from one Secondary Road hex to another (with an AT Ditch between them) with a Tac MA unit would cost ½ MP (errata: the printed chart reads “½ MA”), but require a STOP on entry.
Don’t forget that STOP terrain assumes you have the 4 MPs to enter the hex in the first place. (BCS 4.1e)
The printed Forts on the map (the gear symbol) can be used by either player (depending on which side occupies the hex). Forts cannot be destroyed by either player. Forts are hex, not hexside, terrain features.
Units that cross the Canal using their Leg MA side cannot flip to a Tac or Truck MA side unless there is an emplaced and friendly controlled Bridge or Ferry within their Formation’s Command Radius.