Shingle: The Anzio Beachhead 22 Jan. - 3 Mar. 1944
Shingle: The Anzio Beachhead 22 Jan. - 3 Mar. 1944 Rulebook
Table of Contents
Table of Contents
- Folio Standard Rules
- 5.0 Movement
- 6.0 Zones of Control
- 7.0 Combat
- 8.0 Support Fire
- 9.0 Supply
- Shingle Exclusive Rules
- 10.0 Introduction
- 11.0 Scenarios & Set Up
- 12.0 New Terrain Types
- 13.0 New Unit Types
- 14.0 Sequence Modifications
- 15.0 Logistics
- 16.0 Reinforcements
- 17.0 The Gustav Line
- 18.0 Combat Modifications
- 19.0 Support Modifications
- 20.0 Game Notes
- 21.0 Orders of Battle
- 22.0 Optional Rules
Folio Standard Rules
1.0 Introduction
Each folio game represents an actual or hypothetical battle, as included at the end of the Standard Rules section (known as the Exclusive Rules). The map included with the game represents that actual battle's terrain, and the pieces represent the actual units which participated in the battle. The Standard Rules are rules that generally fit all of the folio games, and the Exclusive Rules are specific to each battle represented.
2.0 Game Equipment
This game should include the following components: 16 page rules booklet including both the folio standard rules and the exclusive rules for this game 280 die cut counters one 34 x 22 map
2.1 The Game Map
The map portrays the battle area. A hexagonal grid is superimposed over the terrain features to regulate the movement and positioning of the game pieces throughout the game.
2.2 Charts & Tables
Various visual aids are provided for the players to aid, simplify and illustrate certain game functions. They are the Combat Results Table, the Terrain Key, and the Turn Record / Reinforcement Track. Some Exclusive Rules will mention additional charts.
2.3 The Playing Pieces
The cardboard pieces represent the actual military units that took part in the battle. The numbers and symbols on the pieces represent the strength, movement capability, and type of unit represented by each piece. Those pieces will hereafter be referred to as units.
2.3.1 How to Read Units
Most units contain identifiers or names, and sizes. The identifier or name of a unit generally has no bearing on play, except as part of some set-up and reinforcement rules. An identifier that lists two numbers separated by a slash represents the battalion # and then the regiment # from which that battalion derives (though that parent regiment may or may not be included in the game). For example, a unit printed with 4/47 is referring to the 4th Battalion of the 47th Regiment. A single # identifier typically refers to a single formation of its type (for example, 9 could refer to the 9th Division). Unit sizes are identified by a roman numeral:
I = Company III = Regiment II = Battalion X = Brigade
2.3.2 Definition of Terms
Attack Strength is the relative strength of a unit with regard to attacking other units, expressed in terms of attack strength points.
Defense Strength is the relative strength of a unit with regard to defending against the attacks of enemy units, and is expressed in terms of defense strength points.
Combat Modifier is the strength of support fire markers (representing everything from corps artillery, naval support, aerial bombardment, organic mortars, etc.) used to attack enemy units, and is expressed in terms of a + value that may be added to the strength of a friendly unit during combat or as a bombardment value.
Movement is the maximum number of clear terrain hexes through which that unit may be moved during a single movement phase; each such hex requires one movement point of the movement allowance. More than one movement point will be required for other types of (non-clear) hexes, though road and trail hexes will negate terrain costs.
Leg unit is a unit that is not a mobile unit, which generally represents any type of unit that lacks conveyance or transport.
Mobile unit is a unit that is not a leg unit, which generally represents any type of unit that moves by a means other than human feet. A mobile unit can be anything from tanks to wagons. Only mobile units are permitted to move during the mobile movement Phase (see 4.1).
2.4 Game Scale
Each hexagon on the mapsheet represents from several hundred to several thousand yards from side to side. Each game turn is equivalent to one or many days of real time.
3.0 Setting Up the Game
The cardboard playing pieces should be punched out of the counter sheet; the differently colored units represent forces of opposing sides. Players should determine which side each will play. Then the players consult their respective Initial Deployment Charts found in the Exclusive Rules. Those charts list the strength of each unit in play on the map during the first game turn. Unit values are listed as follows. For example, a 5-6-8 is a unit whereby 5 is the unit's attack strength, 6 is the unit's defense strength, and 8 is the unit's movement allowance.
Support fire markers simply list a single modifier (such as the +2 above). Units may be assigned specific set-up hexes, or the players may be instructed to choose the set-up hexes for their units, in which case one player or the other will be instructed to deploy his units first. Units specified as reinforcements are to be placed in a space on the Turn Record Track / Reinforcement Track. The Exclusive Rules for each battle will specify the quantity of reinforcement units that arrive and on which game turn. Other information printed on the Turn Record Track / Reinforcement Track appears as follows:
The support fire # is the allotment of support fire markers (not points) per game turn. Generally, the support fire allotment represents such things as naval gunfire from ships far offshore, or bombers flying in from distant bases or aircraft carriers, as well as artillery units of all types and sizes (which are not represented as units in the game). The support fire allotment number equals the total number of support fire markers a player will receive at the beginning of that current game turn.
The Exclusive Rules indicate which player is the first (starting) player. The victory conditions indicate how the game can be won. Play proceeds according to the sequence of play for the number of game turns specified by the Exclusive Rules.
4.0 Sequence of Play
This game is played in successive game turns, each of which is composed of alternate player turns. During each game turn the players maneuver their units and resolve combat according to the sequence outline, and within the limitations provided by the rules. At the conclusion of the last game turn, the victory conditions are consulted and a winner is determined.
4.1 Sequence Outline
Each game turn is divided into a First Player Turn followed by a Second Player Turn (one player takes the First Player Turn while the other player afterward plays the Second Player Turn). The turn track on the map indicates which player is the first player. Each of the player turns must be played through according to the following sequence.
Movement Phase. The current player may move all, some or none of his units as he desires within the limits and restrictions of the rules of movement, zones of control, terrain effects and any exclusive rules. The current player may bring reinforcements onto the map as allowed by his reinforcement schedule and the reinforcement rules. The other player may not move any of his units at this time.
Any mobile units that move during this phase will not be eligible to move during the upcoming mobile movement phase.
Combat Phase. After all movement is completed, the current player uses his units to attack the other player's units. The current player may execute his attacks in any order he desires, but each attack must follow this sub-sequence.
A) The current player states the quantity and the strength of his attacking units, and what enemy unit is being attacked by them. B) The current player may but is not required to assign a support fire markers to add to the strength of his attack (as described in 8.3). This may be done once or twice depending on the scenario, always before the defending player chooses whether or not to add a marker. C) The opposing player may but is not required to add support fire to assist his defense (as described in 8.3). This may be done once or twice depending on the scenario, always after the current player chooses whether or not to add a marker. D) Calculate the combat differential: the total attacking strength value minus the total defending strength value. Adjust that differential according to the type of terrain occupied by the defending unit. Then consult the column on the Combat Results Table that corresponds to that final combat differential. Roll a six-sided die and cross-reference that result within the chosen combat differential column on the CRT, and apply the results immediately.
Mobile Movement Phase. After combat, mobile units (only) are permitted to move during this phase if such units did not already move during the preceding regular movement phase. Mobile movement is identical to regular movement, except that only mobile units (not leg units) may move during this phase.
Mobile Combat Phase. After the mobile movement phase, mobile units (only) are permitted to attack this phase if such units did not already attack during the preceding combat phase. Mobile combat is identical to regular combat, except that only mobile units (not leg units) may attack during this phase.
After all movement and combat by the first player have been completed, the second player begins his movement and combat, using the procedure described above. After the second player has completed his movement and combat, the game turn ends. Remove all Support Fire markers (whether used or not) from the map, but keep them handy to be available for support fire allocation during the next game turn. Then advance the Turn marker one space along the Turn Record Track / Reinforcement Track, signaling the start of a new game turn.
5.0 Movement
During the movement phase, the current player may move as many or as few of his units as he wants. The units may be moved in any direction or combination of directions (into non-prohibited terrain) up to the limits of each unit's printed movement allowance. Units are always moved one at a time, tracing a path of contiguous hexes through the hex grid. As each unit enters a hex, it pays one or more movement points (MP) from its movement allowance (MA).
During the mobile movement phase, the current player may move as many or as few of his mobile units as he desires, but only those that hadn't already moved during the preceding movement phase of the same player turn.
The mobile units may be moved in any direction or combination of directions (if into non-prohibited terrain) up to the limits of each mobile unit's printed movement number (in hexes). Mobile units are always moved one at a time, tracing a path of contiguous hexes through the hex grid. As each mobile unit enters a hex, that unit pays one (or sometimes more) movement points from its printed movement allowance.
5.1 Movement Restrictions
Movement may never take place out of sequence. A player's units may only ever be moved during his own movement phase (or mobile movement phase, if a mobile unit). During the combat phase, a unit that has either attacked or defended may possibly advance or retreat, but that is not considered a move, and does not require the expenditure of any movement points. Neither player may ever conduct movement during the opposing player's movement phase and/or mobile movement phase.
A unit may never enter any hex containing an enemy unit, nor enter any prohibited terrain hex (such as an all water hex). No unit may ever leave the map.
A unit may never expend more movement points than its total printed movement allowance during any one turn. A unit may expend all, some or none of its movement points during any single turn, though any unused movement points may not be accumulated from phase to phase or from turn to turn, nor ever transferred to another unit.
When any unit's movement has been completed, it may not be moved again during that turn, except as a retreat or an advance after combat.
5.1.1 ZOC Movement Effects
Any leg unit that begins its movement in a hex not in an enemy zone of control (EZOC; see 6.0) and enters a hex adjacent to an enemy unit must stop its movement immediately, regardless of how many MP it has remaining.
A mobile unit must expend half of its printed MA (plus the normal cost of terrain) when it both exits and enters an EZOC during the same Movement Phase. However, when a mobile unit exits an EZOC and enters a non-EZOC hex (or exits a non-EZOC hex and enters an EZOC hex), only the normal cost of terrain applies.
Any leg unit that begins its movement in an EZOC may move into an adjacent hex that is not in an EZOC per the normal terrain cost, and may continue movement normally. However, that leg unit must halt its movement if it enters another EZOC.
A mobile unit does not expend half its MA to leave an EZOC, but would be required to expend half of its MA if it then entered another EZOC during that same movement (as well as the normal cost of terrain in each entered hex).
5.1.2 Infiltration
Any leg unit that begins its move already adjacent to any enemy unit (in an EZOC) may move into one adjacent EZOC hex if it expends all of its MA (disregard the normal movement cost in that adjacent hex).
Any mobile unit that begins its move already adjacent to any enemy unit (in an EZOC) may move into one adjacent EZOC hex if it expends half of its printed MA (rounded down) plus the normal terrain movement cost of the hex it enters. It may continue moving if it has MPs remaining.
In either case, it's therefore possible to move any unit from one EZOC to an adjacent EZOC. Mobile units may be able to infiltrate from one EZOC to another, move out of EZOC, move several more hexes, and enter another EZOC.
EXCEPTION: Unit may generally not move from EZOC to EZOC across a minefield hexside or to enter a fortification hex; however, this restriction does not apply to commandos. Commandos don't pay any additional movement costs to enter or exit EZOC.
None of the above applies to retreat or advance after combat, which isn't considered normal movement.
5.2 Effects of Terrain
Any unit must expend one movement point to enter a clear terrain hex. To enter other types of hexes, a unit must expend more than one movement point; see the Terrain Key printed on the map for the movement cost for each type of terrain entered (for example, 2 MP = 2 movement points required to enter that hex). Additionally, some hexsides are printed with other types of hexside terrain features (such as a river), which also require movement points to cross in addition to the movement points required to enter the hex itself. That cost is in addition to the terrain cost for entering the hex. All movement point costs are cumulative.
No unit may enter a hex if that unit does not possess sufficient movement points remaining to pay for the cost to enter, as well as the cost of any crossed hexside terrain feature, if any.
5.2.1 Road Movement
Any unit that moves from one road hex directly into an adjacent road hex through a road hexside expends only ½ movement point, regardless of other terrain in the hex.
5.2.2 Trail Movement
Any unit that moves from one trail hex directly into an adjacent trail hex through a trail hexside expends only one movement point, regardless of other terrain in the hex.
5.3 Stacking Restriction
No unit may ever end its movement stacked with any other unit (although a unit may move through hexes occupied by any other friendly units at no extra MP cost). Stacking is prohibited.
6.0 Zones of Control
The six hexagons surrounding each hex constitute the zone of control (ZOC) of any unit in that hex. Hexes into which a unit exerts a zone of control are called zone of control hexes. All units exert a zone of control at all times, regardless of the phase or the player turn, during the entirety of every game turn.
Zones of control extend into all types of terrain and across all types of terrain hexsides. However, some fortifications (for example, the West Wall) will negate enemy zones of control into the fortification's hex.
The presence of zones of control is never affected by other units, enemy or friendly. If enemy and friendly zones of control extend into a hex, they have no effect upon each other; both co-exist, and the hex is mutually affected by both ZOC. If a unit is in an enemy ZOC, the enemy unit is also in that unit's ZOC.
6.1 Effects on Movement
Zones of control inhibit the movement of enemy units, as explained under 5.1.1.
6.2 Effects on Retreat and Advance After Combat
Units retreating after combat are prohibited from retreating into hexes in an enemy ZOC (see 7.7). Units advancing after combat ignore enemy ZOC (see 7.9).
7.0 Combat
Combat is only ever possible among opposing units that are presently adjacent, but is not mandatory. Any support fire markers being used as bombardment are exceptions (being adjacent is not a requisite), though bombardment is not considered to be combat.
The current player (of the current player turn) is the attacker; the other player is the defender. Combat only ever occurs during the current player's combat phase, per the steps outlined under rule 4.1.
The current player is not required to declare all of his intended attacks at the outset of the combat phase; he may decide each attack as he reviews the map, though all attacks must be resolved to completion one at a time. Separate combats can be resolved in any order the attacker wishes, provided each combat is resolved before the next combat is declared.
7.1 Which Units Attack
Among all of the opposing units adjacent to each other, the attacking player may decide which of his units will be participating in an attack on which defending units, as well as which of his units will not be participating in any attack. A defending unit can be attacked by as many (or as few) attacking units as the attacking player desires, as long as all the attacking units are adjacent, and provided each of the attacking units is not attacking across prohibited or restricted terrain (such as a sea hexside).
The type of terrain the attacking unit(s) are in has no effect on their eligibility to attack, except in the case of a prohibited hexside between the attacker and the target hex. Eligible attacking units from two (or more) hexes (if they are each adjacent to the defender's hex) can add their printed attack values together to attack as a combined value. Support fire may be added per 8.0.
The current player may conduct as many attacks (only during his own combat phase) as there are existing enemy units on the map to be attacked (by the current player's adjacent eligible units, if any).
7.2 Combat Parameters
No particular unit may attack more than once during the same combat phase, and no enemy unit may ever be attacked more than once during the same combat phase (though an enemy unit may be subjected to bombardment by support fire and then a normal attack during a combat phase).
7.3 Combat Differential
The combat differential is the net quantity of attack strength points (including any support fire) compared to the net quantity of defense strength points (including any support fire). The differential is the sum of the total defense value subtracted from the sum of the total attack value.
After calculating the combat differential (see 4.1), consult the Combat Results Table and cross-reference the column indicating the terrain type in that combat hex (the defending unit's hex) with the die roll. In other words, the intersection of the die roll line and column yields a combat result. Implement the indicated combat result immediately (before resolving any additional attacks).
NOTE: Support fire, if available, may be added by a player during his own combat phase. The defending player may also add his own support fire markers, if available, to combat during the other player's combat phase. In any case, support fire markers used during a player's own combat phase are not available to be used during the enemy combat phase, nor vice versa, during the same game turn.
NOTE: all attack and defense strengths are always unitary. That is, a unit's strength may not be divided among different combats, whether as the attacker or the defender. Likewise, a unit may not have its attack and defense strengths combined for any reason.
7.4 Effects of Terrain
Defending units, only, benefit from the terrain in the hex they occupy and/or that hex's perimeter hexside terrain feature. The terrain within the hexes occupied by attacking units has no effect upon combat.
Defending units do not benefit from river or ditch hexsides unless all of the attacking units are attacking that defending unit across a non-bridged river or ditch hexside into that hex.
The effect of terrain on combat has been integrated into the Combat Results Table. Simply refer to the terrain in which the defending unit is present, and cross-reference that terrain type with the combat differential per 7.3. The combat die roll result must correspond to that column.
Terrain benefits for combat are never cumulative; a defending unit always benefits only from the most defensively advantageous terrain type in its hex. For example, a unit in rough terrain surrounded by a river hexside would benefit only from the rough type of terrain.
7.5 Fortifications
If a particular game includes fortifications (whether printed, or as game pieces), the printed defense strength of any unit in a fortification hex is doubled while that unit is in that hex. Moreover, the combat modifier (the + value) of any attacker's support fire or bombardment marker applied to a fortification hex is halved (round down). This rule does not apply to support fire markers applied by the defending player.
7.6 Combat Resolution
The combat results, as printed on the Combat Results Table, are explained as follows:
De = The defending unit is eliminated. D3 = The defending unit must retreat three hexes (7.7) or deplete one unit (7.8). D2 = The defending unit must retreat two hexes (7.7) or deplete one unit (7.8). Ex = One attacking unit and the defending unit must be flipped to their depleted side (or eliminated if already depleted). Among multiple attacking units, the attacker chooses which unit becomes depleted. A1 = The attacking unit(s) must retreat one hex (7.7) or deplete one unit (7.8). A2 = The attacking unit(s) must retreat two hexes (7.7) or deplete one unit (7.8). A3 = The attacking unit(s) must retreat three hexes (7.7) or deplete one unit (7.8). (A) = One attacking unit must be depleted (or be eliminated if already depleted, of the attacker's choice among multiple units). Ae = All attacking units are eliminated. ' = No Effect.
7.7 How to Retreat
When a combat result requires a unit to be retreated, the owning player must immediately attempt to move that unit the indicated number of hexes away from their combat position. This movement is not normal, and therefore requires no movement points to be expended.
A retreating unit must retreat a path of hexes that is farther away from the enemy unit(s) that caused the combat result (or, farther away from the defending unit that caused an attacker retreat).
If possible, a retreating unit must retreat along a path of vacant hexes (that is, not occupied by other friendly units), though a unit may retreat through friendly occupied hexes if no other retreat route of vacant hexes is possible. Under no circumstances may a unit retreat into or through any hex presently occupied by an enemy unit or in an EZOC.
A unit may not retreat into or through any prohibited terrain (such as an all-sea hex). Seaborne units that are required to retreat to a sea hex must be depleted (or eliminated if already depleted or a one-sided unit).
While retreating, a unit may not enter any hex in an EZOC. Friendly units and friendly units with a zone of control into a particular hex do not negate any EZOC into that same hex for the purposes of retreat.
Any unit that must retreat must terminate its retreat movement the number of hexes away required by the combat result retreat number (from its original combat hex). If it can not, it is depleted in the last hex it can legally retreat to or is eliminated if already depleted or is a one-sided unit. In that case, the retreat path is considered to be the last hex that eliminated unit could legally retreat into; see 7.9.
If any unit is unable to retreat per those restrictions, it is eliminated instead.
7.7.1 Bombardment Retreat
A unit that must retreat because of a bombardment must retreat farther away from the closest enemy unit, or toward a friendly unit of the owning player's choice if there are no enemy units on the map. If such a retreat will cause a unit to inevitably retreat closer to an enemy unit, it may retreat toward either one, but must then be depleted. If any unit is unable to retreat after bombardment, it is eliminated.
7.7.2 Displacement
If a retreating unit's only available final hex in a retreat path is occupied by another friendly unit (not involved in that same attack), the retreating player may choose to displace (move) that other friendly unit from its hex (in order to allow the retreating unit to occupy its hex) to one adjacent hex as if that other friendly unit was also retreating as a result of combat. Such displacements may never be made into a prohibited hex, nor into an EZOC, nor into a hex in which the retreating unit would be stacked with another unit. After the displaced unit has moved, the retreating unit may retreat into that other friendly unit's formerly occupied hex.
Additionally, a displaced unit is also permitted to displace another friendly unit using that same procedure, and that other displaced unit may displace yet another friendly unit, and so forth (a given unit may be displaced more than once). Note, however, any unit displaced is assumed to have suffered a retreat (as if a normal combat result), and is thus ineligible to conduct any attack during that turn.
Displacement is voluntary; a retreating unit unable to retreat because of the presence of other friendly units may be depleted or eliminated instead of displacing, as described in 7.8, rather than displace another friendly unit.
A retreating unit may not displace another friendly unit if any eligible vacant hex is available. Similarly, a retreating unit doesn't displace another friendly unit when merely moving through that other unit's hex during the course of a retreat.
7.8 Stiff Resistance
Instead of obeying a retreat combat result, a player may declare stiff resistance instead, whereby that unit is not required to retreat at all; however, that unit must then be immediately depleted. A player may opt to declare a depleted or one-sided unit to offer stiff resistance to avoid the retreat combat result. (The depleted or one-sided unit must be eliminated in that case, but the retreat result is thereby nullified.) That prevents any advance after combat into that combat hex; see below.
7.9 Advance After Combat
Attacking units are only permitted to advance after combat following a retreat combat result on an attacked (defending) enemy unit. No defending unit may ever advance after combat, even after an A1, A2 or A3 combat result.
Whenever an enemy unit is forced to retreat or is eliminated as a result of combat, it will leave a path of vacant hexes behind it called the path of retreat (this includes units that were eliminated when unable to complete the entire retreat; see 7.7). Any or all units that participated in the combat that caused the retreat are then eligible to advance along that path of retreat. The decision to advance after combat must come immediately after the retreat is completed, but no unit is ever forced to advance after combat. Advance after combat is special insofar as all of the advancing units that caused the retreat may ignore enemy zones of control along the entire path of retreat.
Any unit(s) advancing after combat may end their movement in any of the hex(es) along that path of retreat, but they may not stray from the path of retreat while moving. If multiple units advance after combat, no more than one may end its movement in any one hex of the path of retreat.
After an advance after combat, an advancing unit isn't eligible to attack or perform any other activity during that player turn (unless specified otherwise by a particular Exclusive Rule). An advanced unit is subject to attack by any eligible enemy units as of the immediately following enemy combat phase.
8.0 Support Fire
Support fire represents indirect fire assets not represented in the game by actual game pieces. As such, support fire exists as markers players are allotted from a chit pool, which may only appear on the map during the resolution of combat. In other words, support fire markers do not exist on the map as units; they simply represent the incoming fire from such supporting assets.
Each side is provided with its own pool (chit pool) of support fire markers, which are allotted by the support fire allotment number printed on each space of the Game Turn Track / Reinforcement Track. The support fire # is the allotment of support fire markers (regardless of their value) per game turn. The support fire allotment number equals the total number of support fire markers a player will receive at the beginning of that game turn. If two numbers are listed, the first number is the support fire allotment for the first player, whereas the second number is the support fire allotment for the second player. The Exclusive Rules indicate which player is the first (starting) player.
For example, 8/9 printed in the first game turn space of the Crusader game map indicates the British player (who is the first player) is allotted 8 support fire markers, and the German player (who is the second player) is allotted 9 support fire markers (see 3.0 and 10.1).
8.1 Allotted Support Fire Markers
If the allotment of support fire markers indicated on the Game Turn Track / Reinforcement Track is less than the total quantity of markers in the pool for that player's side, that player must select from the lowest-valued markers before selecting higher-valued markers. That is to say, selected support fire markers must be selected in order from lowest to highest.
8.2 Support Fire Limitless Range
Support fire markers have no range limits; they may be added to any combats occurring anywhere on the map unless stated otherwise by the Exclusive Rules.
8.3 Support Fire Application
All support fire markers function the same, though some markers have different printed + values (the combat modifier). The value represents combat strength players may apply to combats that occur during the course of the turn. Naturally, the higher valued support fire markers are more powerful than the lower valued markers. A support fire marker may only be used once during each game turn.
When any combat is announced, the attacking player may declare his intention to apply support fire to that combat, as may the defending player. However, the attacking player must always apply the first support fire marker, if he chooses to do so. Then the defending player may decide to also apply a single support fire marker of his own. Thereafter, the attacker may apply his second support fire marker to that combat, if he chooses (whether or not the defender applied a support fire marker of his own). Finally, the defender may apply the last support fire marker, if he chooses (even if no support fire markers had been applied by either player until then). In other words, the attacker and the defender alternate applying their own support fire markers, if they choose, to each announced combat.
If the attacking player declines to play a second support fire marker, the defending player may apply his second support fire marker nonetheless, although the attacking player may not then play any additional support fire markers after-the-fact.
If the defending player declines to play his first support fire marker, he is nonetheless eligible to apply his second support fire marker, though the defending player may not then retroactively play his first support fire marker. Once a player declines to apply his first or second support fire marker, his opportunity is forever lost during that announced combat.
Applying support fire is always voluntary, though once declared, a player may not change his mind, nor may the announced combat be canceled.
As implied, a player may add up to a maximum of two support fire markers to an attack or defense from among the markers he has been allotted that game turn to any particular combat. Once used, they are then returned to the player's chit pool.
Whether as the attacker or the defender, the applying player simply places his support fire marker(s) in the combat hex (the target hex of the declared attack), and then adds the support fire markers + number to his total attack value (for example, if two 4-4-10 units are attacking a 2-3-8 unit, the total attack value is 8; if the attacking player then adds two +2 support fire markers, the final attack value becomes 12. If the defending player adds a +6 support fire marker to that same combat, the final defensive value would then become 9, that is, a defending 2-3-8 unit +6 = 9).
8.4 Bombardment Support Fire
Prior to resolving any announced combats, Support Fire markers may be used alone to attack enemy units (that is, not in concert with any actual ground attack), in a process known as a bombardment. To conduct a bombardment, the current player may select any enemy unit(s) anywhere on the map as the target of each bombardment (only during his own combat phase and prior to the resolution of the first regular ground attack). He then conducts each bombardment exactly as if a normal attack using the Support Fire marker's + value (combat modifier) to calculate the differential (minus the targeted unit's defense strength). In such a case, a bombardment is resolved like normal combat, except Ex results only affect the target never the bombarding marker. Further, an A1, A2 or A3 result is always ignored.
Each Support Fire marker may only target one enemy occupied hex. Further, a maximum of two markers may be used to bombard the same hex during the same player turn, though both the markers may be of any value from among the markers drawn from the chit pool. Once a marker is used, it's returned to the chit pool where it's eligible for reuse as described in 8.1.
8.4.1 Counter-Battery Fire
A player may also add (a maximum of two) support fire markers (per the same alternating procedure as 8.3) to the defense of any friendly unit that is the target of a bombardment. The value of the defending player's own support fire marker(s) thus simply reduces the bombarding player's total bombardment value by an equivalent amount. (For example, if the bombarding and the defending player's support fire markers are each +6, then the bombardment value is thus 0).
8.4.2 Friendly Fire
After resolving a bombardment, if the Combat Results Table indicates any type of (A) result, the bombarding player must apply that result to a single friendly unit that is closest to that originally targeted enemy unit. If there are multiple friendly units equidistant to that enemy unit, the bombarding player may choose which of his own friendly units is affected by the (A) result.
8.5 Terrain Effects
Support fire may be used anywhere on the map, regardless of intervening terrain or units (enemy or friendly). Support fire is not subject to line of sight restrictions, except when stipulated differently by the Exclusive Rules. In all cases, the defending units benefit fully from the terrain in the hex they occupy when attacked by any support fire, per the adjustment integrated into the Combat Results Table.
8.6 Support Fire Restrictions
Combat results have no effect on the allotment of support fire markers during the current or any future game turn, except when stipulated differently by the Exclusive Rules. A player may not divide or split the + value of any support fire marker among different targets. Each support fire marker must be applied to one particular target hex only. Support fire markers may never be accumulated from game turn to game turn. If they are not used during the game turn that they are allotted, they are returned to the chit pool. No individual hex may be subjected to more than one bombardment (see 8.4) per game turn.
9.0 Supply
There are no supply rules (unless otherwise noted in a specific game's Exclusive Rules). All units are always considered in supply. Isolated or surrounded units suffer no penalties.
Shingle Exclusive Rules
10.0 Introduction
10.1 Historical Background
By the end of 1943 the Italian campaign, aimed at Germany's supposedly soft underbelly, had run afoul of rugged defense and even more rugged terrain. The Gustav Line, anchored on the Garigliano river, the Apennines (including the strongpoint of Monte Cassino), and a series of river lines on the eastern side of the peninsula, had brought the Allies to a halt. Thought was given to shutting down the campaign for the winter, but the invasion of France was still six months off and the Allies could not afford – militarily or politically – to go over to the defensive in Italy. A new offensive was needed. To get through the Gustav line, the Allies planned to make use of their greatest relative strength: sea power.
The reinforced US VI Corps was pulled off the line and embarked at Naples. In mid-January 1944, it headed for the small coastal town of Anzio, just over 30 miles from Rome and even closer to the supply arteries for the Gustav Line. A quick lunge would crack open the German front without the expected attrition battle.
The Germans long had suspected such a move and had positioned small forces along the coast. They could not prevent the invasion, but could delay its rapid movement inland. This thin screen was backed up by designated forces as far away as Yugoslavia, Germany, and France: their job would be to destroy the invading force.
In the event, neither side got what it planned for, and the result was a bloody, four-month stalemate.
10.2 Game Scale
Each hex represents one kilometer. Each turn represents one day. Units are battalions of 400-800 men, depending on type. Supporting units (13.1) generally are half-battalions of 20 armored fighting vehicles, or a few hundred men with heavy weapons. The support markers represent several battalions of artillery, several squadrons of aircraft, a flotilla of cruisers and destroyers, or a single massive cannon mounted on rail cars.
10.3 Standard Rule Modifications
The time and distance scales of this game, along with the unusual situations encountered at Anzio, required some changes to the standard rules. Except as noted in the following sections, all standard rules apply.
10.4 Unit Colors & Information
Allied Units British = Tan US = Olive
German Units German Army = Field Gray Italian = Light Green Luftwaffe = Sky Blue Waffen SS = Black
Mobile Units have a white box behind the Movement factor.
10.5 One-Step Units
Some combat units in the game have only one step, meaning they do not have a depleted side; these units are printed on their reverse sides only. Support units (13.1) also have one step, but have the unit information on the front with only the support unit indicator on the reverse.
11.0 Scenarios & Set Up
Design Note. Anzio took place as part of the much larger Italian campaign, which in turn was competing for Allied resources with the ongoing aerial bombardment of Germany and the planning for the upcoming Allied invasion of France. As a result, the high commands of both sides had a number of options to weaken or strengthen their efforts at Anzio. The following rules give each player the freedom to select secretly from among those options.
11.1 Choice of Scenario & Strategy
There are two scenarios in the game: the short scenario (recommended for first-time players) and the full game. When playing the full game, each player has three strategy choices. The historic strategy uses all rules and schedules as printed. The two variations make some change to the units and logistic support available, and modifies the objectives needed to win. A list of the necessary information for each scenario and strategy is provide on pages 14 (Allies) and 15 (German). The choice of strategy should be made secretly by each player prior to starting the game; we recommend writing the choices on slips of paper and sliding them under the map edge, to be revealed at the appropriate time.
11.2 Victory Considerations
Via Appia. The road from 0301 to 4212 is the Via Appia, which runs through several Allied victory objectives. Lines of Communication (LOC). In several scenarios, the Allies are required to occupy a particular hex (usually a town) with an LOC. An LOC exists if the Allied player can trace a line of road and/or track hexes from the victory hex to Anzio (hex 2129). The LOC may not pass through a German unit or German ZOC.
11.3 Set Up Sequence
After deciding which scenario will be played, which player will control which side, and (if applicable) each player makes his choice of strategy, set up the map and sort the units according to side and unit ID (see 3.1). Place the Turn marker, "Clear" side up (see 14.2), in the turn one box of the TRT. Place each player's LP marker in the zero box of his LP track. Place the Gustav Line status marker (17.1) in the "4" box of the Gustav Line box on the map. Consult each player's Reinforcement Schedule (pages 14 and 15); units listed under Initial Set Up begin the game on the map, all other units enter as reinforcements (16.0).
11.4 Beginning of Game
The game begins with the regular movement phase of the Allied player turn (see 14.0).
12.0 New Terrain Types
12.1 Allied Landing Zones
There are three Allied landing zones (Peter Beach, X-Ray Beach, and Anzio). The two beach zones each consist of six boxes, each associated with a single hex. For example, the northernmost box of Peter Beach must land on hex 1024. Each box may be used to land a single counter on the associated hex. The beach zones may be used only during the first movement phase of the game or after the Germans have captured hex 2129 (see 16.4). The Anzio boxes may be used in both movement phases of every turn; all four boxes are connected to hex 2129.
12.2 Mud
Mud is clear terrain for combat purposes but costs leg units 2 MP, mobile units one-half their MA.
12.3 Wadis
These steep-sided canyons got their name from British soldiers with North African experience.
Zones of Control: ZOC do not project into or out of wadi hexes; a unit in a wadi may move through a hex adjacent to an enemy unit, and enemy units may through hexes adjacent ot it.
Movement: If a unit moves from a wadi hex to another wadi hex across a hexside crossed by the wadi (moving along the wadi as though on a road), treat the hex like a mud hex. A leg unit entering or leaving a wadi across a non-wadi hexside pays its entire MA. A mobile unit may enter or leave (including during combat, retreat, or advance), a wadi only along a road or trail.
Combat: A unit attacking into or out of a wadi uses the wadi line on the CRT. A unit retreating or advancing into (but not out of) a wadi stops in the first wadi entered, even if it has more hexes of retreat left.
12.4 Bridges
A bridge exists wherever a road or trail crosses a river, stream, or canal. Bridges negate the movement effects of the watercourse but not its combat effects. They cannot be destroyed.
12.5 Canals
A leg unit may cross a canal by expending its entire MA (it must start and end the move adjacent to the canal). A mobile unit may cross a canal only at a bridge. No unit may cross a canal into a EZOC.
12.6 Embankments
If a unit attacks across an embankment hexside, use the embankment line on the CRT, even if other units attack the same defender across non-embankment hexsides. ZOCs do not cross an embankment in either direction.
12.7 Towns & Settlements
Settlements are a collection of buildings too small to qualify as a town, but otherwise treated the same. A unit defending a town or settlement always may choose the stiff resistance tactic (7.8); no die roll (18.4) is needed.
13.0 New Unit Types
13.1 Support Units & Stacking
Units with a colored band across the middle are support units. They operate in all ways like other units except they may end a phase in the same hex with other units. One or two support units may stack in a hex, with or without one non-support unit. No other stacking combinations are allowed.
13.2 AFV
Many support units consist of armored fighting vehicles (AFV; those counters with a vehicle pictograph). They operate like other support units but are susceptible to anti-tank fire (see 18.1); non-AFV units with antitank ratings are not susceptible to antitank fire. The armor rating of an AFV is used in antitank fire resolution. AFV are affected differently by some terrain types for movement. When calculating a combat differential, use the AFV's defensive factor when attacking across or into any terrain type except Clear or Mud.
13.3 Special Forces
Special forces units ignore all EZOC unless the SF unit is in a clear or mud hex and the hexside between it and the enemy unit exerting the ZOC is clear or mud.
13.4 Reconnaissance Units
A reconnaissance unit is any unit type including the cavalry symbol (with or without other symbols). If engaged in an attack alone or with other recon unit(s), it may treat an exchange result as an A2 result (the defending unit suffers no loss). A recon unit defending alone or with AFV against an attack may treat an exchange result as a D3 (the attacking unit may advance). The decision to retreat must be made before the combat is resolved, but may be made before or after either/both bombardment and anti-tank fire have been resolved. Regardless of the timing of the decision, the retreat is not made until after bombardment and antitank fire have been resolved.
13.5 US Engineers
Engineers are one-step support units with two additional capabilities.
Fortification. If an engineer begins a regular movement phase stacked with another unit, neither of which has moved, the engineer may be flipped to its front (fortified) side by expending one LP (see 15.0). Place the engineer atop the other unit. The stacked unit is doubled if attacked; bombarding support markers are halved when bombarding it. The stacked unit may not attack, and may always choose the stiff resistance tactic (7.8). The engineer may be lost to satisfy a combat result. If the unit retreats or moves, the engineer is flipped back to its reverse (unit) side.
Bridging. If an engineer unit begins its regular movement phase adjacent to a watercourse, and does not move, treat the watercourse as bridged for the remainder of that turn. The engineer unit may not move during that turn.
13.6 Goliaths (301 StPz Abt)
Goliaths were miniature remote-controlled tanks. Although a failure in reality, they had potential. The unit performs like any other support unit for all purposes except its combat strength is variable (indicated by the asterisks). When the unit attacks, roll two dice; the result is the unit's attack strength for that combat. When defending in mud or clear terrain, the unit has a defense factor of "0." When defending in any other terrain, roll one die to determine the unit's defense factor. The unit must be the first casualty in any attack in which it participates.
14.0 Sequence Modifications
14.1 Modified Turn Sequence
The sequence is detailed below, with a summary on the map. As with the standard sequence, each step must be taken in precisely the listed order.
- Storm Determination (Allies only; 14.2): Roll one die, consult Storm Table, flip turn marker as directed.
- Logistics (15.0): Consult the TRT and roll dice as needed to receive LP.
- Reinforcements (16.2): Move units from the Available and/or Replacement boxes to the Arriving box (16.2), then select any desired support markers (19.2), then, if desired, withdraw units from the Mainland box to the Available box (16.2). Move units from the Released box to the Arriving box, then move units from Theater Reserves and/or Gustav Line to the Released box, then move units from the Replacement Box to the Arriving box, then select any desired support markers, then, if desired, a division may be withdrawn from map to the Gustav Line box.
- Gustav Line Attack (17.0): If desired, launch an attack on the Gustav Line.
- Movement (5.0, 13.1): Standard movement rules apply with the addition of stacking for support units.
- On Call Support Placement (19.4): Deploy on call markers.
- Enemy Counterbattery Support Placement (19.5): Inactive player deploys counterbattery markers.
- Combat (7.0): For each combat:
- Conduct bombardment (19.6)
- Conduct antitank fire (18.1)
- Calculate the differential
- Resolve the combat
- Enemy Support Marker Removal (19.4): Remove any of the inactive player's support markers still on the map.
- Mobile Movement Phase (14.3). Mobile units move normally, leg units receive half their MA.
- Mobile Combat Phase (14.4). All units attack normally. No bombardment or anti-tank fire is conducted.
Map Errata. The Player Turn Sequence summary on the map lists the Storm Determination after the receipt of LPs. This is incorrect; the Storm Determination is made first.
14.2 Storms
During each storm determination phase, the Allied player rolls one die and consults the storm table. If the result is clear, flip the turn marker to its "Clear" side and play normally. If the result is a storm, flip the marker to its "Storm" side. During Storm turns, play is affected as follows:
- All LP awards are halved (see 16.2).
- All MAs are halved.
- No aircraft support markers may be used.
- Only one fire support marker may be used per bombardment of any kind.
- The maximum combat differential is +3 regardless of the actual differential.
- All retreats and advances are limited to one hex.
- Omit the Gustav Line phase, mobile movement phase, and mobile combat phase.
Clarification to 14.3 & 14.4: ignore the standard rule 4.1 restriction for a unit to move and fight only once per turn. All units may move in both the regular and mobile phases, and all units may attack in both the regular and mobile combat phases.
14.3 Mobile Movement Phase
All units may move during the mobile movement phase. Mobile units move normally, leg units may move one-half their MA.
14.4 Mobile Combat Phase
All units attack normally. No bombardment or antitank fire is conducted. The effects of some combat results are altered as listed below and on the CRT.
- D3 = treat as D2.
- Ex = treat as no effect.
- A2 = treat as A1.
- A3 = treat as A1.
- (A) = treat as A1.
15.0 Logistics
Note. Both sides in this battle had tenuous logistic support. The Allied limitation was caused by the increasing diversion of men, materiel, and munitions to the upcoming invasion of France. For the Germans, resources of all kinds were in short supply in the fifth year of the war, and most of what was available was needed to shore up the reeling armies in Russia and to prepare defenses on the French coast. Throughout the game, both players will face randomly reduced support and will be forced to make choices on where that support will be concentrated.
15.1 Logistics Points & Tracks
Each player receives logistics points (LP) at the beginning of his player turn (15.2). LP are used throughout the turn for a variety of reason; unused LP may be saved for following turns. Use the marker on the logistics track to keep count of the number of LP available. Each time an LP is expended, move the marker down the track, but never lower than zero. Each time an LP is added, move the marker up the track. When the count reaches the highest box, flip the marker to the +10 side and return it to the zero box. The highest box +10 is the maximum LP each side may have at any one time; excess LP received are lost.
15.2 LP Awards
The number of LP awarded to each player each turn is listed on the turn record track. The award consists of a fixed number plus the results of the roll of one or more dice (1d = one die, 2d = two dice, and so on). For example, on Turn 2, the Allied player receives 6+1d; if he rolls a 4, then he receives 6+4=10 LP.
15.3 LP Expenditures
LP may be expended as follows:
- To prepare a fortified position by flipping an engineer unit (13.5).
- To bring a unit onto the map (16.2-16.5).
- To replace eliminated units or steps (16.7).
- To launch an attack on the Gustav Line (17.0).
- To select a support marker (19.0).
16.0 Reinforcements
16.1 Reinforcement Boxes
Each player has a set of reinforcement boxes on the map, with slightly different procedures for each. The boxes contain a summary of these procedures, which define how units move from box to box and eventually into play.
16.2 Allied Reinforcement Procedure
The Allied player has three reinforcement boxes: Mainland, Available, and Arriving (see 16.7 regarding the Replacement box). During each Allied reinforcement phase, consult the Allied Reinforcement Schedule to see if any reinforcements will arrive that turn. If there are reinforcements, place them in either the Available box, the Mainland box, or the Available Support box as indicated on the schedule. During the same or any subsequent Allied reinforcement phase, the expenditure of 1 LP allows a single counter (unit or support marker) to make one of the shifts listed below. Except for units entering play at the Anzio beachhead (see 16.3), there is no limit to the number of units/markers shifting between any two boxes in a single phase.
- Mainland box to Available box: 1 LP per unit
- Available box to Mainland box: 1 LP per unit
- Available box to Arriving box (units only): 1 LP per unit
- Replacement box to Mainland box: 1 LP per unit; two step units move with the depleted side showing (see 16.7).
- Replacement box to Arriving box: 1 LP per unit; two step units move with the depleted side showing (see 16.7).
- Available Box to Available Support box (support markers only): 1 LP per marker.
- Arriving box into play (units only): Units land (see 16.3 & 16.6); units are not required to land but may remain in the Arriving box indefinitely. Note Allied support markers are placed on landing zone boxes, but instead of entering the hexfield they are moved to the Available support box. Note: no LP expenditure is needed to land a unit from the Arriving box.
Map errata: delete the "1 LP per unit" line in the Allied Arriving box (as printed on the map).
16.3 Allied Landings
To enter play, an Allied unit or support marker in the Arriving box must be shifted to one of the Allied landing zones (12.1). Units may land at Anzio (hex 2129) on every turn unless it is occupied by the Germans (see 16.4). Units may land on the two beach zones only on Turn 1 or on a turn after the Germans have captured Anzio. To land a unit, move it from the Arriving box into one of the boxes associated with the chosen landing zone. Only one counter may land per box per movement phase. Support markers must occupy a landing zone box, but shift to the Available Support box rather than landing. On Turn 1 (both movement phases), only leg units may land; on subsequent turns, all unit types may land at Anzio. The Allied player thus can land as many as 32 units on Turn 1 (all leg), and up to eight units of any kind at Anzio on each subsequent turn. See also 16.6.
16.4 German Occupation of Anzio
If a German unit occupies hex 2129, no Allied reinforcements may enter Anzio until the turn following the evacuation of the hex by the German. All Allied LP awards are halved until the turn following its evacuation. Allied leg units (only) may land using the X-Ray and Peter Beach boxes at a cost of 1 LP per unit.
16.5 German Reinforcement Procedure
The German player has four reinforcement boxes: Gustav Line, Theater Reserves, Released, and Arriving (see 16.7 regarding the Replacement box). Note the Released and Arriving boxes are broken into three geographic zones, one corresponding to each of the northern, eastern, and southern map edges. During each German reinforcement phase, consult the German Reinforcement Schedule to see if any reinforcements will arrive that turn. If there are reinforcements, place them in either the Gustav Line box, the Theater Reserves box, or the Available Support box as indicated on the schedule. During the same or any subsequent Allied reinforcement phase, counters (unit or support marker) may be shifted from box to box as listed below. There is no limit to the number of units/markers shifting between any two boxes in a single phase.
- Gustav Line box to Released box: the expenditure of 1 LP allows the transfer of up to three units to the Released box. If only one or two units are shifted, it still costs 1 LP. The units may be placed in the South or East portions of the Released box only; which units go into which portion is up to the German player.
- Theater Reserves box to Released box: the expenditure of 1 LP allows the transfer of up to three units or a single support marker to the Released box. If only one or two units are shifted, it still costs 1 LP. The units may be placed in the East or North portions of the Released box only; which units go into which portion is up to the German player. Support markers must be placed in the Available Support box.
- Released box to Arriving box: a unit beginning a turn in the Released box automatically moves to the Arriving box (note it takes two turns to move from the Gustav Line or Theater Reserves to the Arriving box). No LP expenditure is required. Units must remain in the same geographic portion of the Arriving box. For example, a unit in the South Released box must move to the South Arriving box, and so on.
- Arriving box into play: A unit in the Arriving box may enter the map (see 16.6) during any German movement phase; the unit need not enter but may remain in the Arriving box indefinitely. A support marker in the Arriving box is moved directly to the Available Support box during any German movement phase. No LP expenditure is required. Each portion of the Arriving box is associated with a number of hexes on the corresponding map edge (noted in the Arriving box). Any number of units may arrive in a zone or at a single hex in a single movement phase.
16.6 Unit Arrival Restrictions
Units entering the map get half their MA during the movement phase of arrival (the MA of leg units is quartered during the mobile movement phase). Each unit must expend the appropriate MP to enter the hex, but a unit always may enter the map regardless of the MP cost. It may enter the map in an EZOC. A unit arriving by a road or track leading off the map may use road/track movement for the first hex. In all other ways an arriving unit operates normally from the moment of arrival.
16.7 Replacements
Each player may replace a lost step by expending 1 LP during his regular movement phase (not the mobile movement phase).
On-Map Replacement. A depleted two-step unit on the map may be flipped back to full strength. To be replaced, the unit must be able to trace a line free of EZOC from its hex to an eligible entry hex (any hex will do; it does not matter where the unit entered the map). The unit may not be in an EZOC and may not move during the phase (not turn) it receives replacements.
Eliminated Units. A unit eliminated from the map is placed in the Replacement box of the owning player's reinforcement area on the map. Only one step of the unit may be rebuilt; a two step unit may only be rebuilt to its depleted side. The rebuilt unit is then placed in the owning player's Arriving box (the German player may place the unit in any of the arrival zones). It is eligible to return to the map in the next movement phase, even of the same turn.
Other Boxes. Depleted units in the German Gustav Line or Allied Mainland boxes may receive replacements; those in the German Released box may not. A depleted unit in either player's Arriving box may receive replacements, but may not enter the map in the same phase.
17.0 The Gustav Line
Design Note. In the week leading up to the Anzio landing, the Allied armies on the main front launched a series of attacks intended both to pin the German reserves, and if possible to breakthrough the German front to link up with VI Corps. Throughout the campaign, the spectre of renewed attacks prevented the Germans from committing maximum strength to the Anzio front.
17.1 Gustav Line Status
There is a five-box track in the Gustav Line box of the German reinforcement area. The Gustav Line status marker is placed on the highest box at the beginning of the game. Either player may launch attacks on the line (17.2-17.3) during his Gustav Line phase; Allied attacks may shift the marker down the track, German attacks may shift it up. The marker may never go off the track; excess shifts in either direction have no effect.
As long as the marker is in any box except zero, the Gustav Line is stable; keep the marker "Stable" side up.
If the marker reaches the zero box, flip the marker to its "Crisis" side. While the Gustav Line is in crisis, the German LP award is limited to the roll of one die per turn; ignore the awards printed on the TRT.
17.2 Allied Attacks on the Gustav Line
Conduct the following steps if the Allied player chooses to execute an attack.
- Expend 5 LP.
- Total the attack factors of the Allied units in the Mainland box. Divide by 10; round up a remainder of five or more.
- Total the defense factors of German units in the Gustav Line box. Divide by 10; round up a remainder of five or more.
- Calculate the differential. Shift the differential one column rightward for each increment of 5 LP expended (over and above the expenditure in 1 above).
- Roll the die and consult the CRT, using the Broken line. Shift the Gustav Line marker as follows:
- Ex = down 1.
- D2 = down 2.
- D3 or De = down 3.
17.3 German Attacks on the Gustav Line
Conduct the following steps if the German player chooses to execute an attack.
- Total the attack factors of German units in the Gustav Line box. Divide by 10; round up a remainder of five or more.
- Total the defense factors of the Allied units in the Mainland box. Divide by 10; round up a remainder of five or more.
- Calculate the differential. Shift the differential one column rightward for each increment of 5 LP expended.
- Roll the die and consult the CRT, using the Clear line. Shift the Gustav Line marker as follows:
- Ex or D2 = up 1
- D3 or De = up 2
17.4 German Withdrawals
During each of his reinforcement phases, the German player may elect to withdraw one division (only) from the map back to the Gustav Line box. No LP are expended. Pick up all units of that division currently on the map and place them in the Gustav Line box. Depleted units remain depleted. Any units of the division in the Theater Reserve, Released, or Arriving boxes also shift to the Gustav Line box. Any units of the division in the Replacement box remain there, but if replaced must be moved to the Gustav Line.
Once in the Gustav Line box, the units of a division may be moved back to Anzio by expending the necessary LP. Not all the units need be moved back. A unit may be moved back and forth between Anzio and the Gustav Line any number of times per game. However, when a division is withdrawn, all units of that division on the hexfield must be withdrawn at the same time.
18.0 Combat Modifications
18.1 Anti-Tank Fire
Anti-tank fire occurs whenever an AFV unit (see 13.2) is involved in a combat against a unit with an anti-tank factor. If multiple units of one or both kinds are involved, all anti-tank capable units fire. Each fires only once. A single AFV may be targeted by multiple AT units. Defending AT units fire first, (surviving) attacking AT units fire second.
To fire a unit, roll one die. If the result is less than or equal to the firing unit's AT factor, the AFV has been hit.
If the firing unit's AT factor is less than the target unit's armor factor, add one to the die roll. However, a die roll of "1" always scores a hit, and aircraft support markers ignore the armor factor.
A hit AFV takes no further part in that combat to include firing AT; it is not eliminated, but is temporarily ineffective (flip the counter as a reminder). An ineffective AFV may be used to satisfy a step loss and must retreat if the units stacked with it are forced to retreat. Flip it back to its front side after the combat is resolved.
18.2 Allied Divisional Integrity
Subtract two from the final differential in any combat involving units from more than one Allied division. This restriction does not apply to:
- any one attack in the Allied (Regular) Combat phase.
- attacks involving non-divisional units; any number may attack with units of a single division.
- attacks on the Gustav Line.
18.3 German Divisional Integrity
Add two to the final differential in any combat involving units from only one German division. This restriction does not apply to:
- attacks involving non-divisional units; any number may attack with units of a single division.
- attacks on the Gustav Line.
18.4 Retreat & Advance Modifications
7.7.2 Displacement. Do not use this rule. If a unit cannot retreat without displacing another unit, it is forced to invoke stiff resistance.
7.8 Stiff Resistance. Units may not offer stiff resistance automatically in this game. If a player wishes to invoke stiff resistance, he must roll a die. If the result is greater than the unit's printed defense factor, it must retreat. A roll of 6 always requires retreat regardless of the defense factor. No die roll is necessary if the unit cannot retreat without displacing another unit, or is in a fortified (13.5), town, or settlement hex.
7.9 Advance After Combat. No advance may be made after an Exchange result unless the defender is a recon unit choosing to retreat (13.4).
19.0 Support Modifications
19.1 Support Marker Modifications
In lieu of a single support factor, each fire support marker has the following pieces of information.
- Type: used purely for purposes of identification. Other than a few specialty items (19.7), all support markers function the same way.
- Attack Factor: used when bombarding enemy units (19.6) during the owning player's combat phase.
- Defense Factor: used when bombarding enemy units (19.6) during the enemy player's combat phase.
- Range: the distance from a friendly unit a support marker may reach (19.3).
- AT Factor: used in any combat phase when attacking enemy AFV (19.6 & 18.1).
- LP Cost: the number of LPs to be expended to utilize the marker.
19.2 Support Availability & Deployment
Each player has a Support box divided into three portions: Available, On Call, and Counterbattery.
Support markers arrive in the game as directed by the Reinforcement Schedules. In some cases, the markers are placed directly in the Available portion of the player's Support box. Most support markers arrive as though they were units (16.6), including an LP cost to make them available. Instead of moving onto the hexfield from the owning player's Arriving box, they move to the Available portion of the Support box. The markers should remain face up (numbers showing) while in the Available portion.
An available marker may be deployed by the owning player during his reinforcement phase. A marker with an LP cost of zero always may be deployed; a marker with a cost greater than zero may be deployed by expending the appropriate LP. Once expended, the LPs cannot be recaptured, even if a marker is not used.
Once a player has selected and paid for the desired markers, move them out of the Available box and flip them face down, then place them in either the On Call (19.4) or Counterbattery (19.5) portions of the box. The markers should remain face down until flipped again at the moment of combat (19.6).
19.3 Support Range
Support markers with a "U" range have unlimited range and may be placed on any hex on the map.
The Allied fleet marker may bombard a target within seven hexes of a coastal hex (the last hex in each hex column on the map). Count the number of hexes from the fleet's hex to the target; do not count the fleet's hex, do count the target hex.
All other support markers may fire at a target within range of any friendly unit. Select a friendly unit and count the number of hexes to the target; do not count the friendly unit's hex, do count the target hex. If the range is less than or equal to the marker's range, it may bombard that target.
19.4 On Call Support Placement
Support markers in a player's On Call box may be placed on the map by the player at the beginning of his combat phase (14.1). He may place up to two markers on each target hex.
In lieu of attacking an enemy unit, a marker may be placed on a friendly unit, to be used during the following enemy player turn. If an enemy unit moves adjacent, whether it attacks the placement hex or not, move the marker onto the enemy unit during the owning player's counterbattery placement.
At the end of the enemy's next combat phase, remove any markers still on the map or in the On Call portion of the Support box to the Available portion of the box.
19.5 Counterbattery Support Placement
Support markers in the Counterbattery portion of a player's Support box may be placed during the enemy player's combat phase, after the enemy player has finished placing his On Call markers. Placement is made in the same way as the On Call markers, except that only one marker may be placed on each target (though another might already be there if placed during the player's previous on call support placement phase).
19.6 Support Utilization
Bombardment (8.4) is the only kind of attack allowed for support markers. Counterbattery markers bombard just like On Call markers. Each bombardment is separate; do not subtract the counterbattery marker value from the bombarding marker value.
Each support marker attacks each enemy unit in the target hex. Roll separately for each bombardment. For attacks against AFV, use the marker's AT factor; if there is no AT factor, the AFV cannot be attacked. If the support marker is an aircraft marker with an AT factor, conduct the AT fire per 18.1 but ignore the AFV's armor rating. For attacks against non-AFV units, use the attack factor during the owning player's combat phase, the defense factor during the enemy player's combat phase. Cross index the factor with the appropriate terrain line of the CRT. Do not consider the target unit's strength. Once the bombardment is resolved, replace the marker face up in the Available portion of the owning player's Support box.
19.7 Special Support Units
The support markers listed in this case function like all other support markers except as detailed below.
Allied Bomber. This marker may not bombard enemy units adjacent to friendly units and may not be used during the enemy player's combat phase. When making its strike, use the first attack factor (8) on each unit in the target hex, and second attack factor (4) on each unit in each adjacent hex. If used within 3 hexes of an Allied-occupied, conduct friendly fire against that hex; if there is more than one qualifying hex, the German player selects the hex to be attacked. In lieu of rule 8.4.2, the bomber conducts a normal bombardment against the friendly hex.
Allied Strike. This marker may be used to interdict German movement. Place the marker on a hex. Any and all German units moving through that hex or any adjacent hex may be attacked. Any D result (De, D3, D2) stops the unit's movement. Ignore all other results. If the moving unit is an AFV, use the AT factor; a hit stops the enemy movement. If the moving unit is stopped in a hex already occupied by a friendly unit, retrace its path until it reaches a hex it can occupy.
German Railgun. This marker may not bombard enemy units adjacent to friendly units and may not be used during the enemy player's combat phase. The marker may be used to attack Allied supply stockpiles (any LP on the LP track). Roll one die; if the result is less than the marker's attack factor, reduce the Allied player's saved LP by the die roll result.
German Strike. This marker has two special capabilities. It may be used to attack the Allied fleet. Roll one die; if the result is less than (not equal to) the marker's attack factor the Allied player omits one die from his LP roll the following turn. Alternatively, the Strike aircraft may be used to attack Allied stockpiles. Roll one die; if the result is less than the marker's attack factor, reduce the Allied player's saved logistics points by the die roll result.
19.8 Dummy Support Markers
The dummy markers function exactly like regular support markers, but revealed, they are returned to the Available portion of the Support box without affecting enemy units.
20.0 Game Notes
20.1 Designer's Notes
Anzio is a classic situation in that both sides must attack and defend, each had the potential for a war-changing victory, but neither achieved it due to serious errors in strategy and execution.
There were two critical and difficult parts of the design. First was the need to restrain the players from attacking all-out every turn – it just didn't happen on the battlefield. The primary reason for that was the logistical limitation each side faced. The logistics rules handle that with a minimum of bookkeeping.
The second major problem was the fact that the Germans never really developed their full potential in the battle. Largely this was the need to keep some reserves near the main front, where the ongoing battle for Cassino was interspersed with attacks along the Garigliano River. Had one of those attacks succeeded, especially if it succeeded quickly, the battle at Anzio would have been moot. The Allies have less to worry about in this regard, but their Mainland box and the ability to attack the Gustav Line should keep the German player honest.
20.2 Player Notes
Tactics. The addition of logistics, supporting units, the antitank subroutine, and more elaborate support rules has altered the bare-bones force-on-force nature of the original system. The use of these force multipliers is critical if you expect to pierce an enemy line. It's no longer enough to have more units, you have to have the right mix of men, weapons, and logistic support. Use bombardments to deplete strong units and eliminate supporting units. The Allied aircraft are especially useful: fighter-bombers to knock out heavy tanks, strike bombers to bottleneck reinforcements, and heavy bombers to make a big hole in the ground. For the Germans, it's all about tanks. Mass them and keep coming. Take as much advantage as you can of the secrecy of your support deployments; all you need is one good sucker punch at the right place and time to swing a battle around.
Grand Tactics. Both players can generate the power to knock holes in the enemy line. But unless your opponent has made a big mistake, it won't be enough to allow a rapid and deep penetration toward your victory objectives. There are plenty of units, and a wise player always will keep a few battalions as a second line to prevent just that kind of breakthrough. To keep a battle moving, it is necessary to maintain the application of combat power over several turns. This requires careful management of your reserves and – above all – of your LP. Keep enough units on hand to feed fresh ones into the line while replacing depleted units. Maintain some supporting fires every turn; grand slams are great but probably won't gain much more than one or two hexes at a time. Victory is as much about management of the battle as it is about taking a given hex.
Strategy. This paragraph will not apply to the short scenario, or to players (probably most of you) who agree beforehand to play the historical campaign. When playing the campaign game with its strategy options, those choices will be crucial to the outcome. On the map, the Allies always will attack early while the Germans defend, then the Germans will set up a counterattack. Within that broad outline, both players must be subtle in their moves to avoid telegraphing specific attacks or the strategic choice too early. You should anticipate both players moving tentatively for the first 10 turns or so.
21.0 Orders of Battle
The numbers next to each formation below indicate the number of battalions in it. If there are two numbers, for example 1/2, the first number is the number of battalions, the second number is the number of counters representing that unit in the game. The Allies have a total of 54 battalions and 40 support units, the Germans 72 and 42 respectively.
21.1 Allies
All Allied units taking part in the invasion and ensuing beachhead battle came under command of the US VI Corps of the US Fifth Army. In many respects the force was a microcosm of the polyglot array of Allied forces in Italy. All divisions had a variety of supporting units – anti-tank, anti-aircraft, pioneers (combat engineers), etc.– encompassed by the supporting units in the game.
Abbreviations
- Arm Armor
- AT = Antitank
- Bn = Battalion
- Bde = Brigade
- Cdo = Commando
- Eng = Engineer
- Fus = Fusilier (a regimental title for infantry)
- Inf = Infantry
- Para = Parachute
- RA = Royal Artillery
- Rif = Rifles (a regimental title for infantry)
- Rgr = Ranger
- Rgt = Regiment (British tank and cavalry regiments are battalions)
- Sqdn = Squadron (battalion)
- TD = Tank Destroyer
- Tk = Tank
US Forces
1st Armored Division
- 1st Arm Rgt (3/6 with 49 M-3 Stuarts & 96 M-4 Shermans)
- 13th Arm Rgt (3/6 with 49 M-3 Stuarts & 96 M-4 Shermans)
- 6th Arm Inf Rgt (3)
- 81st Mobileanized Reconnaissance Sqdn (1)
- 16th Arm Eng Bn (1)
The 13 Arm Rgt and the 2/6 Arm Inf formed Combat Command B, left on the mainland for most of the Anzio campaign.
3rd Infantry Division
- 7th Inf Rgt (3)
- 15th Inf Rgt (3)
- 30th Inf Rgt (3)
- 10th Eng Bn (1)
45th Infantry Division
- 157th Inf Rgt (3)
- 179th Inf Rgt (3)
- 180th Inf Rgt (3)
- 120th Eng Bn (1)
Independent Units
- 1st (US/Canadian) Special Service Force: 1st, 2nd, & 3rd Rgts (3)
- 36th Eng Rgt: 2826th, 2827th, 2828th Eng Bns (3)
- 39th Eng Rgt: (2)
- 191st Tk Bn (1/2; 45 M-4 Shermans, usually served with 1st Arm Div)
- 504th Para Inf Rgt (3)
- 509th Para Inf Bn (1)
- 601st TD Bn (1/2 with 45 M-36 TD, usually served with 3rd Div)
- 701st TD Bn (1/2 with 45 M-36 TD, usually served with 1st Arm Div)
- 645th TD Bn (1/2 with 45 M-36 TD, usually served with 45th Div)
- 751st Tk Bn (1/2 with 45 M-4 Shermans, usually served with 1st Arm Div)
- 753rd Tk Bn (1/2 with 45 M-4 Shermans, usually served with 3rd Div)
- 894th TD Bn (1/2 with 45 M-36 TD, served with British 1st Div)
- 6615th Ranger Force: 1st, 3rd, & 4th Rgr Bns (3)
British Forces
1st Infantry Division
- 2nd Bde: 1st Bn/Loyal Rgt, 2nd Bn/North Staffordshire Rgt, 6th Bn, Gordon Highlanders (3)
- 3rd Bde: 1st Bn/The Duke of Wellington's Rgt, 2nd Bn/Sherwood Foresters, 1st Bn/King's Shropshire Light Infantry (3)
- 24th Guards Bde: 5th Bn/Grenadier Guards, 1st Bn, Irish Guards, 1st Bn, Scots Guards (3)
- 1st Reconnaissance Rgt (1)
- 2/7th (Machinegun) Bn/Middlesex Rgt (1)
56th Infantry Division
- 167th Bde: 8th Bn/Royal Fus, 9th Bn/Royal Fus, 7th Bn/Oxfordshire & Buckinghamshire Light Inf (3)
- 168th Bde: 1st Bn/London Irish Rif, 1st Bn. London Scottish, 10th Bn/Royal Berkshire Rgt (3)
- 169th Bde: 2nd/5th Bn/Queen's Royal Rgt, 2nd/6th Bn/Queen's Royal Rgt, 2nd/7th Bn/Queen's Royal Rgt (3)
- 44th Reconnaissance Rgt (1)
- 6th (Machinegun) Bn/Cheshire Rgt (1)
- 8th AT Bn RA (1)
Several British battalions have a notation like 2nd/5th; this means that there were two similarly-numbered battalions, in this case the 5th, in that regiment.
Independent Units
- 2nd British Special Service (Commando) Bde: No. 9 Cdo, No. 10 Cdo, No. 40 Royal Marine Cdo, No. 43 Royal Marine Cdo (4)
- 46th Royal Tank Rgt (1/2 with 45 M-4 Shermans)
- 50th Royal Tank Rgt (1/2 with 45 M-4 Shermans)
21.2 German Order of Battle
The German beachhead front came under the command of Fourteenth Army, which divided the front between 1st Parachute Corps and 76th Panzer Corps. In common with the whole Italian front, the battle was fought by some whole formations and fragments of others; the Germans were masters at forming ad hoc battlegroups. The units at Anzio were a fair representation of the German army at this point in the war: excellent mobile divisions, veteran infantry division, newly-formed infantry divisions (some still in the process of formation while the battle raged), plus bits and pieces from company to regimental size. All divisions had a variety of supporting units – anti-tank, anti-aircraft, pioneers (combat engineers), etc.– encompassed by the supporting units in the game.
Abbreviations
- Abt = Abteilung (a battalion not part of a regiment, though some were called battalions)
- Aufkl = Aufklarungs (reconnaissance)
- Bn = Battalion (those forming part of a regiment were denoted with Roman numerals)
- FJ = Fallschirmjaeger (Parachute)
- Fus = Fusilier; a "fast" (often bicycle-mounted) battalion
- Inf = Infantry
- Jg = Jaeger (essentially infantry with slightly lighter equipment for operation in rugged terrain)
- Lehr = School units (training and demonstration)
- Pz = Panzer (armor)
- PzGr = Panzergrenadier (mobileanized/motorized infantry)
- PzJg = Panzerjaeger (antitank)
- Pzkw = Panzerkampfwagen (tank)
- Rgt = Regiment
- StPz = Sturmpanzer (also known as StG for Sturmgeschtz; assault guns)
- zbv = zur besonderen Verwendung, literally "for special purpose," it often was used to describe extemporized units
Herman Goering (HG) Panzer Division
- Hermann Goering Aufkl Abt (1)
- Hermann Goering Pz Rgt (2/4 with 35 Pzkw III, 27 Pzkw IV, 14 StPz)
- 1st Hermann Goering PzGr Rgt (3)
- 2nd Hermann Goering PzGr Rgt (3)
- Hermann Goering PzJg Abt (1)
1st Fallschirmjger Divsion (part)
- 1st FJ Rgt (4)
3rd Panzergrenadier Division
- 8th PzGr Rgt (3)
- 29th PzGr Rgt (3)
- 103rd Pz Abt (1/2 with 44 StPz)
- 103rd PzAufkl Abt (1)
- 103rd PzJg Abt (1)
4th Fallschirmjger Divsion
- 10th FJ Rgt (3)
- 11th FJ Rgt (3)
- 12th FJ Rgt (3)
- 4th FJ PzJg Abt (1)
- Italian Nembo Parachute Bn (1)
I/12 FJ Bn was a specialist assault unit.
15th Panzergrenadier Division (part)
- 104th PzGr Rgt (3)
- 115rd Pz Abt (1 with a mix of about 25 Pzkw IV and StPz)
- 115rd PzAufkl Abt
16th SS "Reichsfuehrer" Panzergrenadier Division
- II/35th SS PzGr Rgt (1)
- II/36th SS PzGr Rgt (1)
- Ad hoc Heavy Weapons Abt (1)
26th Panzer Division
- 26th Pz Rgt (1/5 with 23 Pzkw III, 91 Pzkw IV, 14 StPz)
- 9th PzGr Rgt (2)
- 67th PzGr Rgt (2)
- 26th PzAufkl Abt (1)
- 51st PzJg Abt (1)
I/26 Panzer, equipped with the division's Panther tanks, was on the eastern front. It is likely some of the vehicles in the regiment were organized into a second, unofficial, battalion.
29 Panzergrenadier Division
- 15th PzGr Rgt (3)
- 71st PzGr Rgt (3)
- 129th Pz Abt (1/2 with 44 StPz)
- 129th PzAufkl Abt (1)
- 129th PzJg Abt (1)
65th Infantry Division
- 145th Inf Rgt (2)
- 146th Inf Rgt (2)
- 147th Inf Rgt (2)
- 165th Fus Bn (1)
- 165th PzJg Abt (1)
71st Infantry Division (part)
- 194th Inf Rgt (3)
- 171st Fus Bn (1)
III/194 was composed of Slavic "volunteers."
90th Panzergrenadier Division (part)
- 200th PzGr Rgt (3)
- 190th Pz Abt (1 with a mix of about 25 Pzkw III, Pzkw IV, and StPz)
- 190th PzAufkl Abt (1)
114th Jaeger (Light) Division
- 721st Jg Rgt (3)
- 741st Jg Rgt (3)
- 114th Fus Bn (1)
- 114th PzJg Abt (1)
362nd Infantry Division
- 954th Inf Rgt (2)
- 955th Inf Rgt (2)
- 956th Inf Rgt (2)
- 362nd Fus Bn (1)
715th Infantry Division
- 725th Inf Rgt (3)
- 735th Inf Rgt (3)
- Italian Barbarico Bn (1)
This division is identified as "motorized" is some sources. German sources do not so identify it, and as it had been formed recently from two reserve infantry regiments, with few heavy weapons, for anti-guerrilla operations in Yugoslavia, it seems highly unlikely it would have been given priority for Germany's dwindling motor vehicle stocks.
Independent Luftwaffe Units
- FJ Lehr Bn (1)
- XI Luftwaffe StPz Abt (1 with about 25 StPz)
- 1st Machinegun Bn (1)
- 7th Jg Bn (1)
- 302nd (Heavy) FLAK Bn (1)
- 304th (Heavy) FLAK Bn (1)
Independent Infantry Units
- Lehr Rgt (2; most of II Bn left behind)
- 1027th PzGr Rgt (2)
- 1028th PzGr Rgt (2)
- zbv (4; these battalions game represent a variety of unit fragments and individuals pressed into emergency service at Anzio).
Independent AFV Units
- Pz Company Meyer (1 with 8 Pzkw VI Tiger)
- I/4 Pz Rgt (1/4 with 76 Pzkw V Panther)
- 216 StPz Abt (1/3 with 57 Brummbr StPz armed with a 150mm howitzer)
- 301 StPz Abt (1 equipped with Goliath remote-control vehicles)
- 508 Pz Abt (1/3 with 45 Mk VI Tiger)
- 540 PzJg Abt (1 with about 20 Hornisse PzJg)
- 1/653 PzJg Abt (1 company with 11 Ferdinand PzJg)
I/4 Panzer, part of the 13th Panzer Division, was training with its new Panthers in France when called to Anzio. The unit remained in Italy, eventually becoming part of 26th Pz Rgt.
22.0 Optional Rules
22.1 Battle of the Caves
During the historical battle, hexes 1018, 1118, and 1217 were the object of what became known as the "Battle of the Caves," but the wadi-type features in those hexes were too small for inclusion on the map. Should players choose, those hexes may be treated as either three one-hex wadis or as rough terrain.
22.2 Tank Destroyers
All US tank destroyer (TD) units have attack and defense factors of "0." During the battle, there were a few examples of TDs providing close support to infantry using their machineguns. Should players choose, treat TDs as having a defense strength of "2" when stacked with a friendly infantry or engineer unit. The TD must be the first step lost in any combat result.
22.3 Panthers
The four AFV counters of the German I/4 unit represent Pzkw V Panther tanks. These tanks are given an armor rating of "5" because the thick armor on their turrets and front slopes was all but proof against current Allied anti-tank guns. The Panthers' armor was quite thin on the sides and flank. Should players choose, the Panthers may be treated as having an armor rating of "3" if attacked from the air or if fired on by Allied anti-tank fire from two non-adjacent hexes.