Battle for Kirovograd
Battle for Kirovograd Rulebook
Table of Contents
Table of Contents
1.0 Introduction
This game is comparatively simple for a wargame, but the rules are still numerous. Rather than trying to memorize every rule, it is best to read through the rulebook once to get an overview.
After reading the rulebook once, spread out the map, punch out the counters, and move them while following the "Detailed Play Example" section. Doing so speeds up understanding of the rules.
The Bonsai Games rulebook is organized into chapters (such as 1.0), sections (such as 1.1), and items (such as 1.1.1). When referring to a specific rule, the chapter, section, or item is given in parentheses. Important rules and exceptions are printed in red, play examples in blue, and designer's comments and similar notes in green. The rulebook, the errata and Q&A are all accessible through the two-dimensional barcodes (QR codes) in the rulebook.
1.1 Game Scale
One turn represents one actual day. The distance between opposite sides of one hex is 2 miles (3.2 km). Each unit represents a battalion, regiment, brigade, or division.
2.0 Components
This game includes the following components:
- Rulebook: 1 copy
- Map: 1 sheet (A1 size)
- Counter sheet: 1 sheet (260 counters, 13 mm square)
- Player aids: 2 sheets (A4 size)
Note: The counter sheet also includes 8 correction counters for Operation Desert Storm.
In addition to the above, at least one six-sided die is required.
Counters that represent combat units are called "units." Counters that show or record information in the game are called "markers."
- German units are gray-green. Soviet units are khaki (yellow-brown).
- Every unit has a branch symbol or an illustration of its equipped vehicle printed on it. The latter are called tank units. German tank units are battalion-sized. Soviet tank units are brigade- or regiment-sized.
- Each unit's central color indicates the higher formation to which it belongs. Some German units are corps-level units that do not belong to a division; these have no color coding.
2.1 Units
- Each unit belongs to a division (German) or an army (Soviet). The unit's higher formation is shown by the color code at the center of the unit.
- The unit's strength (left) and movement allowance (right) are printed at the bottom of the unit.
- The strength of heavy tank units is printed inside a black square.
2.1.1 Unit Size
- Tank illustration = Battalion (German), Regiment/Brigade (Soviet)
- XX = Division
- X = Brigade
- III = Regiment
The rulebook's sample counters are labeled as follows.
-
Sample 1, front side: "47PzK (47th Panzer Corps) 3rd Panzer Division Panzergrenadier Regiment." The labeled areas are: deployment/entry code; division name; division symbol1; strength2; higher formation name; formation color code; formation size; morale; loss strength; branch symbol5; movement allowance3; small unit marking4; heavy tank marking2.
-
Sample 2, front and back: "52K (52nd Army), GD (Grossdeutschland) Division, heavy tank battalion."
-
*1 Division symbols are printed only on units subject to the division stacking rule.
-
*2 Tank units whose strength doubles when firing are printed in red. Units with strength shown inside a black square are "heavy tanks" (7.2.2, 7.3).
-
*3 A black hexagon marks a motorized unit; a white hexagon marks a non-motorized unit (4.2).
-
*4 Units whose lower-right half has a pale background are small units (6.0).
-
*5 See the Player Aid for the meaning of the branch symbols.
2.1.2 Abbreviations
The abbreviations used on units have the following meanings:
- German forces: Pz = Panzer (armor); KGA = A Corps Group; PG = Panzergrenadier
- Soviet forces: G = Guards Red Army; MC = Mechanized Corps; TC = Tank Corps
2.1.3 Strength Display
All units enter the game at full strength. When combat reduces a unit's strength, the current strength is shown by the following methods.
- Full-strength counter (the unit as printed at full strength)
- Replacement counter #1
- Replacement counter #2
The diagram in the rulebook shows a 5-strength unit (47PzK, 14Pz) in the following stages, labeled A to D:
- A. A full-strength unit with 5 strength that loses 1 strength is turned to its reverse side (current strength: 4).
- B. A unit that has lost 2 strength is replaced by a replacement counter (current strength: 3).
- C. If it loses 1 more strength, it is turned to its reverse side (current strength: 2).
- D. If it loses 1 more strength, it is replaced by the next replacement counter (current strength: 1).
A unit destroyed by losing its last strength point is eliminated.
Important: Replacement counters, which have a yellow line printed across the center of the unit, represent units that have lost strength. Replacement counters are provided only for motorized units. Non-motorized units show their remaining strength with damage markers. (If the player wishes, motorized units may also show remaining strength with damage markers.)
2.2 Markers
Counters used to display or record game information are called "markers." This game uses the following markers. How each marker is used is explained in the relevant rules.
- Game Turn Marker: Used on the Game Turn Record Track to record the progress of the game. The front side is the Bayerlein line; the back side is Konev.
- Damage Marker: Placed beneath a unit that has lost strength in combat. The number shows the strength the unit has lost (2.1.3).
- Active / Done Marker: Used when it must be distinguished whether a unit is active (in the middle of its activation) or has completed its activation (3.1).
- Done Facing Marker: Used to orient both sides' units east-west or north-south to show that they have completed their activation (3.1).
- Victory Point Marker: Placed on the Victory Point Record Track to record the victory points earned during the game (11.0).
Design note: Because units are turned to show that they have completed activation, the units' facing must always be kept uniform. Place a Done Facing Marker in an unobtrusive location on the map to indicate whether units that have completed activation face east-west or north-south. Use it to turn the units that have completed their activation in that direction.
2.3 Map
The map depicts the terrain of the battlefield. The hexagonal cells that cover the entire map are called "hexes," and they are used as the reference for unit positions and movement. Every hex has a unique four-digit number (the hex number), which is used when referring to a specific hex.
- Terrain affects unit movement and combat. See the Terrain Effects Chart on the Player Aid.
- The map also prints the Game Turn Record Track and the Victory Point Record Track.
Beginner's note: The above definitions may look complicated, but the rules themselves are simple. For details and practical use, see the combat rules and the "Detailed Play Example."
2.4 Player Aids
Each side has one Player Aid. One side of it has the Combat Results Table and the Terrain Effects Chart; the reverse side has the Order of Battle.
3.0 Sequence of Play
The game proceeds by repeating Game Turns. There are 12 Game Turns (hereafter GT), and the game ends after the 12th. In each GT, the Soviet player takes a Player Turn, and then the German player takes a Player Turn. When the German Player Turn ends, the GT ends. Move the GT Marker one space forward on the Game Turn Record Track and begin a new GT.
3.1 Game Turn Sequence
- A. Soviet Player Turn
- B. German Player Turn
Veterans' note: This game has no separate "movement phase" or "combat phase." During your own Player Turn you may move and fight with your units in any order. However, the following restrictions apply:
- The player whose Player Turn it is is the "Active Player"; the opponent is the "Passive Player."
- During your own Player Turn, each of your units may move once and attack once. A unit may attack after moving, but may not move after attacking. A unit that has finished attacking, or that has moved and then does not attack, is turned 90 degrees and, for the rest of that Player Turn, is shown as having completed its activation (it can neither move nor attack).
- Use Done Facing Markers, placed in an unobstructed location on the map, to turn units that have completed activation in the chosen direction.
- To attack an enemy unit in a hex, one of your units must move into a hex adjacent to it (or already be adjacent to it from the start). If several of your units are attacking the same target, all of them must move to adjacent hexes first, and then they attack jointly. To show that multiple units are moving to attack, place Active Markers on the units that will take part in the attack. If, before the attack is resolved, any of your units is moved to a hex other than one adjacent to the target, the attack is considered cancelled, and the units that had been adjacent to the target are set to Done.
- Once any number or all of your units have finished moving and attacking, the Player Turn ends. When your Player Turn ends, turn all of your units to the Done facing, whether or not they were activated.
- During the enemy's Player Turn you may perform Defensive Fire (7.0), but this does not prevent you from moving and attacking normally during your own Player Turn.
Beginner's note: The above definitions may look complicated, but the rules themselves are simple. For the detailed procedures and practical use, see the combat rules and the "Detailed Play Example."
4.0 Movement
During its own Player Turn, a player may move its own units. Movement is optional; not all of a player's movable units must move.
4.1 Basic Movement
Units move one at a time. Each time a unit moves into an adjacent hex, it spends movement points (MP) from its movement allowance according to the terrain of the hex it enters and the terrain of the hexside it crosses. If the unit cannot spend the MP required, it cannot move any further. See the Terrain Effects Chart for the cost of each terrain type.
Important: A unit may not move into a hex occupied by an enemy unit.
Important: Neither side may move units off the map.
4.2 Unit Types
A unit whose movement allowance is printed inside a black frame is a motorized unit. A unit whose movement allowance is printed inside a white frame is a non-motorized unit. This difference affects only the cost of crossing rivers.
Example: A unit in hex 2819 crosses a river hexside into hex 2820 (flat terrain). If the unit is non-motorized, the river costs +1, so the move costs 1 + 1 = 2 MP. If the unit is motorized, the river costs +2, so the move costs 1 + 2 = 3 MP.
4.3 Road Movement
A unit moving into an adjacent hex along a road pays the road movement cost, regardless of the terrain of the hex it enters or the hexside it crosses. If a unit enters a hex that contains a road but does not move along the road, it must pay the normal movement cost.
Example: A motorized unit in hex 3437 moves to hex 3337. It pays 2 + 2 = 4 MP. If it moves from 3437 to 3436, it is road movement, so it pays 0.5 MP.
4.4 Completing Movement
- When a unit finishes moving in a hex not adjacent to any enemy unit, the unit cannot conduct combat (7.0). It is turned to the Done facing to show that it cannot act again during that Player Turn.
- When a unit finishes moving and immediately attacks an adjacent enemy unit, the combat is resolved. The unit is then turned to the Done facing.
- When a unit finishes moving in a hex adjacent to an enemy unit, and the player intends to attack that hex and to have other friendly units join the attack, place an Active Marker on the unit that has moved. Resolve the combat only after all friendly units taking part in the joint attack have finished moving. Then place a Done Marker on every friendly unit that took part in the combat.
Important: If a friendly unit that is not planned to attack together with an active unit is moved, all active units are considered to have cancelled their attack.
Design note: Because completed activation is shown by turning the unit, the Active Marker's reverse side (Done) does not need to be used.
Example: At the start of the Soviet Player Turn, two Soviet units are adjacent to German units. The mechanized brigade of the 5th Guards Mechanized Corps cannot move into hexes 2420 or 2521, because that would be a direct move from EZOC to EZOC. However, it can reach 2420 by first moving through 2321, which is outside the EZOC. The 252nd Rifle Division is adjacent to a German unit, but the EZOC does not extend to its hex, so it can move directly into 2419 (1 MP). It must, however, end its move in that hex to enter the EZOC.
Example: The red-shaded area is the zone of control of two German units (the 384th Infantry Division and the 14th Panzer Division). Because the area lies across a lake hexside, no ZOC extends into hex 2519.
5.0 Zone of Control
All units exert a zone of control (ZOC) over the six adjacent hexes, regardless of their current strength. A ZOC exerted on a unit of the opposing side is called an "EZOC" (Enemy ZOC).
Exception: ZOC does not extend across a lake hexside. All other terrain is subject to ZOC.
- A unit that enters an EZOC during movement must stop in that hex, regardless of how much movement it has left.
- A unit that starts its move in an EZOC may leave that EZOC without penalty. However, it may not move directly from one EZOC to another EZOC. After moving into a hex that is not in an EZOC, it may again enter an EZOC.
- Entering or leaving an EZOC does not require any additional MP.
- When a unit enters an EZOC during a retreat (7.7), the whole stack loses one step.
- During post-combat advance (7.9), a unit may move directly from one EZOC to another EZOC.
6.0 Stacking
Placing more than one friendly unit in the same hex at the same time is called "stacking." One or more friendly units occupying a single hex together are also called a "stack." Friendly and enemy units may not stack together.
6.1 When Stacking Limits Apply
There are limits on the number of units that may stack (6.2, 6.3). Stacking limits are checked at the following times. At other times, a stack may temporarily exceed the limit.
- When each unit completes its movement
- When a retreat is completed
- When a post-combat advance is completed
6.2 Soviet Stacking Limits
Soviet units may stack in any one of the following combinations:
- One division only (that is, no stacking is possible), or
- Up to three small units belonging to the same corps, or
- Up to two small units, regardless of corps
Note: Soviet small units represent brigades or regiments.
Important: Soviet units belonging to different armies may not stack together.
Example of Soviet stacking: Small units may stack up to three if they belong to the same corps (in the illustrated case, 7GMC). If they belong to different corps (in the illustrated case, 7GMC and 5GA Direct), only two may stack.
Army-direct tank regiments: The Soviet forces have three army-direct tank regiments:
- 53rd Army: 34th Tank Regiment
- 5th Guards Army: 57th Guards Tank Regiment
- 7th Guards Army: 27th Tank Regiment
These tank regiments may stack with the rifle divisions of the same army. They may not be stacked with units of a different army.
Stacking example (Soviet Player Turn): The motorized rifle brigade of the 29th Tank Corps has completed its activation in hex 3033. Then two rifle divisions each moved and placed Active Markers to conduct a joint attack against a German unit. The Soviet player tried to bring the 29th Tank Corps' tank unit into the attack. Because a unit that has already completed its activation is in hex 3033, moving the tank unit there would also make it Done, so the joint attack could not be conducted. Instead, the player moved the tank unit into hex 2934 and conducted the joint attack with the two rifle divisions.
6.3 German Stacking Limits
German units may stack in any one of the following combinations:
- Up to two regiments, regardless of parent formation, or
- All units belonging to the same division
Note: German divisions made up of three or more units print a division marker.
Important: German units may stack together even if they belong to different armies, provided the stacking limits are met.
- Regiments: up to 2 (regardless of parent formation)*
- Same division: all units
* Up to four small units (if from different divisions) to six small units (three each from the same division) may also stack.
Stacking example (German forces): Two small units count as one regiment; if they all belong to the same division, three small units count as one regiment. Units belonging to the same division (GD) may all stack regardless of size (in the illustrated case, six units).
7.0 Combat
A player who attacks during its own Player Turn (that is, starts combat) is called the "attacker," and the opponent is called the "defender."
- Combat is optional. A unit adjacent to an enemy unit is never forced to attack.
- There is no limit on the number of combats that may be conducted during one friendly Player Turn.
- During one friendly Player Turn, each attacking unit may attack only once. A unit that has attacked is turned to the Done facing and may not move or attack again during that Player Turn. Defending units may be attacked more than once.
- During one friendly Player Turn, multiple attacks may be made against the same defending hex. Also, a single attack may be made simultaneously on the same defending hex from several adjacent hexes.
- Attacking units stacked together may attack with all or some of them, but any stacked attacking unit that does not attack is also considered to have completed its attack and is turned to the Done facing (7.4). An attacker may not target only part of the defenders in a stack; it attacks all defending units in the target hex.
- Exception: A friendly unit that finished movement in a hex occupied by a friendly unit that has completed activation may not attack from that hex. It is immediately turned to the Done facing (7.4).
Procedure for resolving one attack:
- The attacker chooses a target hex and declares which adjacent friendly units will attack it. If some units attacking the same hex have not yet moved, they complete their movement first and the combat is resolved after all of them have reached their attacking hexes. Friendly units that will attack together receive Active Markers until all attacking units have reached their attacking hexes.
- Defensive Fire: The defender totals the strength of its friendly units in the target hex to resolve Defensive Fire. Only the defending units in the attack target hex may conduct Defensive Fire. The player rolls one die and checks the result.
- Offensive Fire: After the results of Defensive Fire are applied, the attacking units that remain fire on the target hex. The strengths of all attacking units are totaled, the player rolls one die, and the result is checked.
- If all defending units are eliminated or retreat, the attacker may conduct a post-combat advance (7.9). The defender may not conduct a post-combat advance.
7.1 Fire Procedure
Defensive Fire and Offensive Fire are resolved by the following procedure.
- The player conducting the fire totals the strength of the firing units. A unit's strength is reduced by damage. Tank units may double or triple their strength (7.2).
- The player finds the column of the Combat Results Table (CRT) that corresponds to the total strength. Then all modifiers (7.3) are applied. In Defensive Fire, the attacker (the side being fired upon) gets no terrain modifiers.
- Once the column to be used is determined, the player conducting the fire rolls one die and checks the result. The result is applied immediately.
7.2 Strength Modifiers When Firing
7.2.1 Strength Loss: Each unit displays its maximum strength on its front side. When a unit loses 1 strength point, it is turned to its reverse side. When it loses further strength, a damage marker is placed to record its current strength. Its current strength is the printed strength minus the value of the damage marker, or the unit is replaced by a replacement counter.
7.2.2 Tank Units:
- When a tank unit fires, its current strength is doubled for the calculation.
- When a heavy tank unit fires at a target that includes one or more enemy tank units (including heavy tanks), its current strength is tripled instead of doubled. If the target contains no enemy tanks, its current strength is doubled.
- When a unit other than a tank fires, it uses its current strength unmodified.
7.3 Column Shifts
Find the CRT column that corresponds to the total strength after modification. Then apply the following shifts to that column. A left shift is favorable to the target side; a right shift is favorable to the firing side.
7.3.1 Terrain: When the defender is in a village, city, or rough hex, apply the left shift shown in the Terrain Effects Chart when resolving Offensive Fire. When all attacking units attack across a river, apply a 1-column left shift. If even one attacking unit attacks from a non-river hexside, the river left shift is not applied.
Important: No terrain modifiers apply to Defensive Fire.
7.3.2 Heavy Tank Units: If the target stack includes one or more heavy tank units (units whose strength is printed inside a black square), apply a 1-column left shift.
7.3.4 Column Limits: Column shifts are cumulative. If, after applying the modifiers, the result is to the left of the "1-2" column, the fire result is automatically "No Effect." If the result is to the right of the "35+" column, the fire is resolved on the "35+" column.
Note: The rulebook's numbering of the column-shift sections runs 7.3.1, 7.3.2, 7.3.4 as printed; there is no section 7.3.3 in the source.
7.4 Attacks by Multiple Stacks
Before resolving an attack, the attacker may move as many friendly units as it wishes into hexes adjacent to the target.
- An attack may target only one hex.
- During the same Player Turn, a unit may not move into a hex containing a friendly unit that has already attacked (and is therefore in the Done state), and attack again from that hex.
- A unit that is already adjacent to the target from the start, without moving, may join the attack on that target. Because it becomes Done after the attack, it cannot move after attacking.
- If some of the units in a stack conduct Offensive Fire, the units in that stack that did not conduct Offensive Fire are also considered to have attacked, and must be turned to the Done facing.
7.5 Combat Results
- If the result is "-", the fire has no effect and the target takes no damage.
- If the result is a single number (selected loss), the player receiving the fire chooses either to lose that many strength points or to retreat that many hexes (strength loss or retreat; the two may not be combined). If retreat is chosen, the entire affected stack must retreat.
- If strength loss is chosen, the strength of units in the target stack is reduced. The order of applying strength loss follows 7.5.2. After that, the stack containing the units that lost strength makes a morale check. A stack that fails its morale check must retreat a number of hexes equal to the selected loss value (7.8).
Example: If the selected loss is 2 and the player chooses strength loss, even if the stack loses only 2 strength points, if the stack fails its morale check it must retreat 2 hexes.
Important: If failing a morale check would eliminate all units in a stack, strength loss may not be chosen for the selected loss.
- If the result is two numbers, the left value is the selected loss. The right value is the forced loss: that many strength points are removed from units in the target stack. The order of applying strength loss follows 7.5.2.
The following summarizes how combat results are applied. See the following rules for details.
| Result | Offensive Fire | Defensive Fire |
|---|---|---|
| Forced loss | # strength loss | # strength loss |
| Selected loss: strength loss | # strength loss + morale check (+# DRM) | # strength loss + morale check for # stacks (+# DRM) |
| Selected loss: retreat | # hex retreat | All stacks retreat # hexes; Offensive Fire not possible |
7.5.1 Defensive Fire: Defensive Fire against multiple attacking stacks is resolved as follows.
- Defensive Fire is conducted not against a particular stack but against the entire attacking stack group.
- If a forced loss results from Defensive Fire, the attacker decides which units in all stacks take the strength loss, according to rule 7.5.2.
- If the attacker chooses retreat for a selected loss, all attacking stacks must retreat.
- If strength loss is chosen, the following steps are taken:
- According to rule 7.5.2, the attacker decides which units among all stacks conducting the attack take strength loss.
- Next, the defender selects as many attacking stacks as the number of the selected loss. If the selected loss value is greater than the number of stacks, the excess is ignored.
- The attacker makes a morale check (7.8) for each stack the defender selected. Stacks that suffered a forced loss and had strength loss applied add the number of strength points lost to the die roll (making a successful morale check harder). Strength loss from a selected loss does not affect the morale check.
- An attacking stack that fails its morale check retreats and may not conduct Offensive Fire. An attacking stack that passes its morale check conducts Offensive Fire.
7.5.2 Order of Strength Loss
Whenever strength is reduced from a stack, whether by forced loss or selected loss, the following order of priority must be followed. Where several units have the same priority, the player receiving the fire chooses which unit loses strength.
Important: When a forced loss occurs and the player has chosen strength loss for a selected loss, first apply the forced loss in accordance with the priority order, and then apply the strength loss of the selected loss again in accordance with the priority order.
Example: The target stack contains one tank unit and two infantry units, and the fire result is "2-1." The player receiving the fire decides to absorb the selected loss through strength loss. First, the forced loss causes the tank unit to lose 1 strength point. Next, the selected loss reduces the stack by 2 strength points. In this case too, following the priority order, the tank unit loses 1 strength point first, and then 1 strength point is removed from one infantry unit (chosen by the player receiving the fire).
- If the target stack contains a tank unit, the first strength point lost is applied to a tank unit. If there are several tank units, it is applied to a heavy tank unit. Otherwise, the player receiving the fire decides which tank unit loses strength.
- The remaining losses are assigned by the player receiving the fire to any units in the target stack. However, no unit may lose 2 strength points from a single unit until all units have lost 1 strength point. If the strength loss still remains to be applied after 1 strength point has been removed from each unit in the target stack, return to priority 1 and apply the remaining strength loss.
7.5.3 Strength Loss and Retreat
If the defender chooses strength loss for a selected loss, the defending stack must make a morale check (7.8) after the strength loss is applied. If the defender chooses retreat for a selected loss, no morale check is made, and the stack must retreat immediately.
7.6 Strength Loss
A unit that loses its first strength point is turned to its reverse side. When it loses further strength, a damage marker is placed, or the unit is replaced by a replacement counter, to record its current strength (7.2.1). A unit whose current strength reaches zero is eliminated and removed from the game.
7.7 Retreat
A stack that chose retreat for a selected loss, or a stack that failed its morale check (7.8) after choosing strength loss for a selected loss, must retreat a number of hexes equal to the selected loss value. An attacking stack that retreats as a result of Defensive Fire may not conduct Offensive Fire.
- A stack must retreat as a stack. Its units may not retreat in different directions.
- A retreating stack must move as far away as possible from the enemy units that fired on it.
- It must avoid entering an EZOC wherever possible. It may enter an EZOC only when no other hex is available for retreat. Each time it enters such a hex, the whole stack loses 1 strength point. The retreating player may freely decide which units lose strength (there is no priority order).
Important: A retreat may not end in an EZOC. Units must retreat additionally to a hex that is not in an EZOC.
- A retreat through a lake hexside, or a retreat into a hex containing an enemy unit, is prohibited. Units may not retreat off the map.
- A unit that cannot retreat is eliminated regardless of its current strength.
7.7.1 Retreat and Stacking Limits: If a unit ends its retreat in a hex where it exceeds the stacking limit, it must retreat one additional hex to comply with the stacking limit.
7.7.2 Retreat by the Defender: Even if a defending unit retreats, it may act normally during its next friendly Player Turn.
7.8 Morale Check
A player that receives a selected loss and chooses strength loss must make a morale check after the strength loss is applied. The morale values of both sides are as follows. The values do not change by branch or current strength.
-
German morale value: 5
-
Soviet morale value: 4
-
A morale check is made per stack, not per unit.
-
Roll one die. If the result is equal to or less than the morale value, the morale check succeeds. If it is higher, the morale check fails.
-
Die roll modifier: A stack that suffered a forced loss and lost strength adds a number equal to the forced loss to the die roll.
-
If the morale check succeeds, there is no additional effect. An attacking stack that succeeds in its morale check after being hit by Defensive Fire may remain in its hex and conduct Offensive Fire.
-
A stack that fails its morale check must retreat a number of hexes equal to the selected loss value (7.7).
Combat example: Three Soviet units attack one German unit.
- Defensive Fire: The current strength of the German unit is 7 (2 x 2 + 3). The "5-7" column of the Combat Results Table is used. The die roll is 1, and the result is "2." The Soviet player chose strength loss. The first strength point lost is applied to the tank unit. The next is applied to a rifle division of the player's choice (the 78th was selected). Then two stacks (the tank and the 78th) are chosen for morale checks. The tank passed its check, but the 78th Guards Rifle Division failed and retreated 2 hexes.
- Offensive Fire: The Soviet player uses the remaining two units to conduct Offensive Fire. The current strength of the tank unit is 2, which is doubled to 4 (7.2.2). The strength of the 93rd Guards Rifle Division is 5, for a total of 9. Because the defender is in rough terrain, the column is shifted one step left to the "5-7" column. The die roll is 2, and the result is "1." Because the German unit is surrounded (in an EZOC), the German player must retreat. The German player chose retreat and intended to retreat to hex 2932, but because that hex is within an EZOC, the unit loses 1 strength point and must retreat additionally to hex 2931 or 3031 (7.7). Because the defender retreated, the two units that conducted Offensive Fire may conduct a post-combat advance (7.9).
Example: A 5-strength attacking unit receives a "2-1" result in Defensive Fire and chooses strength loss. The unit first loses 1 strength point from the forced loss, and then loses 2 strength points from the selected loss (3 strength points in total). The remaining strength is 2. The unit then makes a morale check with a +1 die roll modifier (for the 1 point of forced loss). If the check succeeds, the unit remains in its hex and conducts Offensive Fire. If it fails, the unit retreats 2 hexes and may not conduct Offensive Fire. If a second hex also attacked, that stack makes its morale check without a die roll modifier (because the selected loss result was "2").
7.9 Post-Combat Advance
When all defending units are eliminated or retreat as a result of fire, all attacking units that took part in that combat may conduct a post-combat advance. A post-combat advance is never mandatory.
- Even if the attacker is eliminated by Defensive Fire, the defender may not conduct a post-combat advance.
- Each attacking unit may advance a number of hexes equal to the selected loss value the attacker inflicted on the defender.
- No MP is spent during a post-combat advance. Advances across a lake hexside are not allowed.
- A post-combat advance may be made in any direction. Units do not need to enter the hex the defending unit occupied.
- Units are still affected by EZOC during a post-combat advance. However, EZOC may be ignored only when entering the hex the defending unit originally occupied.
Example of post-combat advance: The combat resulted in 1 strength loss to the German side and a 2-hex retreat, so the two Soviet units that attacked may conduct a post-combat advance. The motorized rifle brigade of the 29th Tank Corps, which was adjacent to the combat hex but did not take part in the attack, and the 78th Rifle Division, which took part in the attack but retreated after being hit by Defensive Fire, may not advance. The 93rd Guards Rifle Division, which pursued the retreating German unit, advanced into hex 2831. Similarly, the tank unit of the 29th Tank Corps advanced into hex 2833 rather than into the combat hex. This ends the combat.
Note: Unlike many other wargames, a post-combat advance does not oblige units to advance into the combat hex.
8.0 Special Units
8.1 Heavy Tank Units
- When a heavy tank unit fires at a stack that includes one or more enemy tank units (including heavy tanks), its strength is tripled instead of doubled.
- When a unit is fired upon, if the target stack includes one or more heavy tank units (units whose strength is printed inside a black square), apply a 1-column left shift.
9.0 Setup
Decide which player will command which army, and take the units of the army you command. Sort your units by deployment/entry code. Place markers off the map, in a location both players can easily reach.
9.1 Front Line
A red dotted line is printed on the map; this is the front line at the start of the game. German units with deployment codes A-H, and Soviet units with deployment codes A1-A7, B1-B6, C1-C8, and D1-D3, must be deployed in hexes adjacent to this front line, in accordance with the stacking limits.
9.2 Order of Battle
Refer to the Order of Battle on the Player Aid and place the units that are deployed at the start on the map. Deploy the German units first, then the Soviet units. After that, place the GT Marker on "1" of the Game Turn Record Track.
Important: The units that must be placed adjacent to the front line are listed in order from north to south. Units must be deployed in this order. Also, all hexes adjacent to the front line on your side must either contain one of your units or be within the ZOC of one of your units. Soviet units may be deployed within the ZOC of German units.
9.3 Special Rules for the 3rd Panzer Division
Each unit of the German 3rd Panzer Division is deployed in one of the four city hexes of Kirovograd (not a town hex). Units of this division may not leave the Kirovograd city hexes until they are released from reserve (they may move among the four city hexes).
- At the start of the German Player Turn in GT 1, the German player rolls one die. If a "1" is rolled, the 3rd Panzer Division is released from reserve, and all its units may move and fight normally.
- If the division is not released in GT 1, at the start of the German Player Turn in GT 2, the German player rolls one die. If a "1" or "2" is rolled, the 3rd Panzer Division is released from reserve.
- In GT 3, the 3rd Panzer Division is automatically released from reserve.
- If even one unit of the 3rd Panzer Division is attacked by Soviet units during GT 1 or GT 2, the entire division is immediately released from reserve, and from then on all its units may move and fight normally.
9.4 Recording Victory Points
At the start of the game, all objective hexes are controlled by the German side (11.1.2). Of these, the hexes that score for the German side are Kirovograd (20 VP) and Novo-Dobrovka and Azamka (10 VP each). To indicate this, place the light-colored German VP marker on "0" of the VP Record Track, and the dark-colored German VP marker on its front side at "40" of the VP Record Track.
The Soviet VP markers: place the light-colored one on "0" of the VP Record Track, and the dark-colored one on "00."
If the VPs earned exceed 100, turn the dark-colored marker over to its "+100" side to record the VPs.
10.0 Reinforcements and Replacements
10.1 German Reinforcements
Units that enter the game after it has begun are called "reinforcements." Only the German side receives reinforcements. Which units enter, when, and from where is listed in the Order of Battle. Each unit also carries an entry code showing its entry GT and entry location. If a player wishes, the entry GT of reinforcements may be delayed, but the entry location may not be changed. Reinforcements enter the map by movement during the entry GT's friendly Player Turn. If the first hex is a road that connects to the off-map area, road movement (4.3) may be used to enter the map.
- There is no limit on the number of reinforcement units that may enter from one hex.
- If an enemy unit is in the entry hex, the unit may enter from the nearest map edge hex that does not contain an enemy unit. Entry into an entry hex within an EZOC is permitted (the unit ends its movement in that hex).
10.2 Soviet Replacements
Recovering strength lost by a unit is called "replacement." Only the Soviet side receives replacements.
At the start of GT 6, the Soviet player receives 10 Tank Replacement Points (TRP). TRPs may all be used in GT 6, partly used, or not used at all. Unused TRPs may be used at the start of GT 7 or any later GT. Once all 10 TRPs have been used, no further replacements may be made. Use the TRP marker on the Game Turn Record Track to record the remaining TRPs.
10.2.1 Strength Recovery: A Soviet tank unit that meets the following conditions may use TRPs. Soviet units other than tanks may not use TRPs.
- A tank unit that is not in an EZOC.
- A tank unit that did not conduct combat during its own Soviet Player Turn (it may have moved).
- A tank unit that can trace a line of communication (11.1.1).
Note: A unit that began the friendly Player Turn in an EZOC may still receive replacement if it moves, without fighting, to a hex not within an EZOC.
A Soviet tank unit that meets the above conditions may use TRPs at the end of its own Player Turn. Each TRP used removes 1 damage point. There is no limit on the number of TRPs one unit may use in one turn. However, TRPs may not be used to raise a unit above its original strength.
10.2.2 Rebuilding Destroyed Tank Units: A destroyed Soviet tank unit may be rebuilt using TRPs. Each TRP used rebuilds the unit with 1 strength point. A unit may be rebuilt at full strength or at partial strength (that is, still in a damaged state). Rebuilding takes place at the end of the friendly Player Turn, and a rebuilt unit enters the map during the next friendly Player Turn in the same way as reinforcements (10.1), from the road hexes on the eastern map edge (3546 or 2046) that do not contain German units.
11.0 Victory Conditions
The game ends after GT 12, and victory is determined as follows.
11.1 Victory Points
11.1.1 Victory Points for Damage Inflicted: The damage each player inflicted on the enemy during the game (the strength points the enemy lost) is compared to determine the winner. Each strength point lost is worth 1 victory point (VP).
Important: The Soviet side may recover strength lost by its units through replacements (10.2). Damage markers removed by replacement do not count as VPs for the German side. (That is, if the Soviet side uses 10 TRPs, the German side earns 10 fewer VPs than the damage it actually inflicted.)
Lines of communication: At the end of the game, a unit that cannot trace a path to its own map edge without passing through a hex containing an enemy unit, or through a hex within an EZOC, is considered destroyed. Having your own units in a hex does not cancel an EZOC. The path a unit traces to its own map edge is called its "line of communication."
- Soviet map edges: For the Soviet side, the friendly map edge is the Soviet side of the front line, together with the north and east edges of the map.
- German map edges: For the German side, the friendly map edge is every map edge other than those of the Soviet side.
11.1.2 Victory Points for Geographic Objectives: At the end of the game, the player who controls the following hexes earns VPs:
- Kirovograd city: A player who controls all four city hexes of Kirovograd earns 20 VP at the end of the game.
- Towns: A player who controls all hexes that make up a town bearing its own marker earns 10 VP for each such town at the end of the game. If even one hex that makes up a town is controlled by the enemy, no VP is earned from that town.
- Control: A player controls a hex if its own unit is in that hex, or if the last unit to enter it was its own, and that player can trace a line of communication (11.1.1) from that hex.
11.2 Determining the Winner
Subtract the lower VP total from the higher, and determine the winner:
- 0-19 VP difference: Draw
- 20-39 VP difference: Tactical victory for the player with more VP
- 40 VP difference or more: Strategic victory for the player with more VP
Designer's note: VPs may be totaled all at once at the end of the game, or recorded during the game. In the latter case, place the VP markers on the VP Record Track to record the VPs earned by both sides.
12.0 Optional Rules
12.1 Mechanized (Armored Infantry) Units
Mechanized (armored infantry) units include armored combat vehicles. To reflect this, when these units fire, their current strength is multiplied by 1.5 (rounding down). When multiple mechanized (armored infantry) units fire together, total their strengths, multiply by 1.5, and then round down.
When this rule is used, a German heavy tank unit firing at a mechanized unit has its current strength tripled (7.2.2).
12.2 German Fire Shifts
- When German units belonging to the same division fire alone, apply a 1-column right shift in addition to other modifiers.
- When German units belonging to several divisions fire simultaneously from several hexes, apply a 1-column left shift in addition to other modifiers.
- In either case, units that do not belong to a division (such as assault gun battalions) are ignored when considering whether these modifiers apply.
Example: A regiment of the 2nd Fallschirmjäger Division and the 203rd Assault Gun Battalion stacked together fire: a 1-column right shift applies. If these two units are stacked with one regiment of the 384th Infantry Division, no fire shift is obtained. If one regiment of the 384th Infantry Division fires jointly from a different hex, a 1-column left shift applies.
13.0 Designer's Notes
The first simulation of the Battle of Kirovograd that I played was Jack Radey's Kirovograd (3W, 1983). After that, I created my own game reproducing the battle of Kirovograd, with a system similar to Korsun Pocket—though artillery and anti-tank guns were made into units—and played it many times. However, I always felt something was lacking. This battle was a close fight, and the historical fact that the Soviet forces who took Kirovograd won by a narrow margin made it hard to simulate. I never imagined I could make a game of the Battle of Kirovograd with the same system as Korsun Pocket (that is, without artillery and anti-tank guns as independent units) until Korsun Pocket was released.
Even after deciding to use the Korsun Pocket system, the game was revised further. Enlarging the map gave more room for maneuver, but it no longer fit in 34 x 22 inches (roughly the Japanese A1 size). The order of battle was also changed several times. The "Korsun system" did not include a German reconnaissance battalion, but I decided to add one. The order of battle for the Soviet side in David Glantz's book Surprise and Maskirovka in Contemporary War was used as well. Thanks to this, the Soviet order of battle was fundamentally revised, the northern part of the front was advanced to the west, and the Soviet rifle divisions were strengthened. Finally, because the scale of Korsun is 1 turn = 2 days and Kirovograd is 1 day, I adjusted the combat results. Army-direct tank regiments, which in Korsun had their rules changed, may now stack with the rifle divisions of their own army. This change slightly increased the Soviet offensive capability.
Early on, both sides' mechanized (armored infantry) units were planned to multiply their strength by 1.5 when firing, unlike motorized infantry. However, this rule gave the Soviet side a long-term advantage, and multiplying by 1.5 was troublesome to calculate. So it was kept as an optional rule for balance adjustment (12.1).
As usual, I will not discuss the techniques of this game with players. The Soviet side will likely try to break through the German line in several places if possible. Next, it must decide what to do after breaking through. Soviet units are strong, but as they pass through breakthroughs in the line, their strength quickly wears down. Surrounded German units are also troublesome. The Soviet player will try to eliminate them, but doing so requires considerable strength and time.
Another challenge for the Soviet player is when to switch from offense to defense. If the Soviet side keeps attacking even after strong German reinforcements arrive, it exposes its units to danger, and the German counterattack becomes stronger. Consider in advance where you will meet the German units.
The best strategy for the German player is to hold the line for as long as possible, but give up ground when necessary and make use of the defensive effects of terrain. For surrounded units, a cold judgment is required: attempting a rescue risks the rescuer being trapped too. If luck is with you, a surrounded unit may break out on its own.
The designer's closing acknowledgements to the playtesters, publisher, and collaborators, and the designer's signature and date, are omitted from this transcription as credits.
Extended Example of Play
From here on is an example of play for Battle for Kirovograd. In practice, spread the map on the table, punch out the counters, and proceed with the game while reading this text. This speeds up understanding of the rules. The map diagrams that accompany the example in the original are not reproduced in this transcription; the text describes the moves and results they show. The original's "Before Starting the Game" box, which lists general-retail accessories (dice, dice trays, card stands and similar), is omitted as non-rules content.
Setup
Set up the game following rule 9.0. Place the German units first, then the Soviet units.
- First, arrange the units that are deployed in hexes adjacent to the front line. Note that units with deployment codes A-H must be placed in hexes adjacent to the front line. Also, during setup, only units bearing the same letter may stack together.
- Stacking limits are applied after each unit finishes its movement. If a rifle division is in a hex you want to attack with tanks, that division must be moved first, and it cannot attack during that GT. The Soviet player should keep the hexes from which it intends to launch an attack subject only to ZOC.
- After you have confirmed that the front-line deployment conditions are met, set up the units that are placed behind the front line.
An example of initial deployment is shown on the next page of the original.
Soviet Player Turn
Victory is determined by victory points (VP). VP are earned from damage inflicted on enemy units and from control of cities and towns. Strong German reinforcements arrive in GT 4, so the Soviet player should aim to break through before then and to establish the encirclement of Kirovograd and control of the towns to the west of the map.
53rd Army Attack
1. The 5th Guards Mechanized Corps attacks one regiment of the 320th Infantry Division. For this reason, no rifle division was placed in the front-line hexes 3045 and 3035.
- Defensive Fire: The infantry regiment's strength is 3, so the "3-4" column is used. The die roll is 5, and the result is "-."
- Offensive Fire: The Soviet total strength is 32: the tanks (4 + 6) x 2 = 20, and the infantry 4 x 3 = 12. The rough terrain modifier is applied, and the "25-29" column is used. The die roll is 4, and the result is "2-1." The German player chose retreat for the selected loss, lost 1 strength point, and then retreated 2 hexes. The 5 units of the 5th Guards Mechanized Corps advanced as shown in the diagram. As a result of the advance, 2 German regiments were encircled.
2. The 5th Guards Mechanized Corps attacks the motorized infantry regiment of the 11th Panzer Division, which it has encircled. First, the army-direct tank regiment stacks with the 89th Rifle Division. (Unlike Korsun Pocket 2, tanks and rifle divisions of the same army may stack together.) The attack is made from 3 hexes.
- Defensive Fire: The infantry regiment's strength is 4, so the "3-4" column is used. The die roll is 1, and the result is "1." The Soviet player chooses strength loss and applies it to the stack containing the tank. The German player makes a morale check for that stack. The die roll is 4, and the check succeeds.
- Offensive Fire: The Soviet total strength is 4 + 4 + 5 + (1 x 2) = 15. The die roll is 4, and the result is "1." The German player chose retreat and withdrew the unit to hex 2736. Because the hex is in an EZOC, the unit lost 1 strength point. Each Soviet attacking stack advanced 1 hex.
5th Guards Army Attack
3. Having passed through the breakthrough opened by the 53rd Army, the 7th Mechanized Corps attacks the 2 units of the German 11th Panzer Division in the front line, encircling them. The 7th Mechanized Corps moves 3 units into hex 2738 and 2 units into hex 2839, and also moves the 95th Rifle Division and the 57th Guards Tank Regiment into hex 2740, attacking from 4 directions.
- Defensive Fire: 5 strength is used to fire. The die roll is 1, and the result is "2." The Soviet player chooses strength loss. The first strength point lost is applied to the 57th Guards Tank Regiment, and the remaining strength point is applied to the 95th Rifle Division. Because the German player wants to secure a retreat route, it makes morale checks for the stacks in hexes 2738 and 2740. The stack in hex 2738 (2 tanks and 1 motorized infantry) fails on a die roll of 5 and retreats 2 hexes to 2937. The stack in hex 2740 succeeds in its morale check.
- Offensive Fire: The Soviet total strength is 4 + 5 + 5 + 4 + (1 x 2) = 21. The die roll is 4, and the result is "2." The German player chose retreat and moved 2 hexes into Subbotsy (2538). (If the Soviet morale checks in Defensive Fire had both succeeded, the retreat would pass through an EZOC, so 1 strength point would be lost.) The attacking Soviet stacks each advanced 2 hexes. As a result, the motorized infantry regiment of the 11th Panzer Division, which had retreated in the earlier combat, was encircled again.
4. The 29th Tank Corps attacks the armored grenadier regiment of the 14th Panzer Division. The 50th Rifle Division of the 7th Guards Army also takes part in this attack.
- Defensive Fire: 5 strength is used to fire. The die roll is 5, and the attack misses.
- Offensive Fire: The Soviet total strength is 4 + 5 + [(3 + 6 + 5 + 6) x 2] = 49. The die roll is 2, and the result is "3-2." The German unit loses 2 strength points and retreats 3 hexes. A 3-strength unit is replaced by a replacement counter, or 2 damage markers are placed to show the strength loss. The Soviet side may advance 3 hexes. The 50th Rifle Division moved into hex 2241 and encircled one regiment of the 10th Panzer Grenadier Division. One stack of the 29th Tank Corps advanced into hex 2141, and another stack advanced into hex 2142.
5. The 18th Tank Corps is used to further widen the breakthrough opened by the 29th Tank Corps. Two stacks move into hexes 2041 and 2042 respectively. The 41st Guards Rifle Division moves into hex 1943, attacking from 4 directions.
- Defensive Fire: 6 strength is used to fire. The die roll is 2, and the result is "1." The tank unit with 2 strength loses 1 strength point. The German player makes a morale check for the strongest tank stack (6 strength and 5 strength). The die roll is 6, and the check fails. The stack retreats 1 hex (moving to hex 2143).
- Offensive Fire: The Soviet total strength is 4 + 5 + 3 + [(3 + 1) x 2] = 20. The die roll is 2, and the result is "2-1." The reconnaissance battalion loses 1 strength point and retreats 2 hexes (moving to hex 1940). Because it entered an EZOC, it loses 1 more strength point. The German player chose to avoid losing a unit and applied the 1 strength loss to the motorized infantry regiment instead. In hindsight, if the morale check had been applied to the stack in hex 2141 (and had failed), this strength loss could have been avoided. The Soviet units advanced as shown by the arrows. The stack of the 18th Tank Corps and the 41st Guards Rifle Division are adjacent to Azamka, and the 303rd Rifle Division advanced to hex 4841.
6. One stack of the 8th Mechanized Corps (2 tanks and 1 mechanized infantry), together with the 6th and 9th Guards Airborne Divisions, attacks the German motorized regiment in hex 2342. This movement is not shown in the diagram.
- Defensive Fire: 3 strength is used to fire. The die roll is 6, and the attack misses.
- Offensive Fire: The Soviet total strength is 4 + 4 + 4 + [(5 + 3) x 2] = 28. The die roll is 5, and the result is "2." The German player chose retreat. Because it passed through an EZOC, the unit lost 1 strength point and moved to hex 2440. The Soviet side advanced 2 hexes and encircled the German stack in 2541 (this retreat and advance are not shown in the diagram).
The other stack of the 8th Mechanized Corps (2 mechanized infantry) advanced to hex 2141 and attacked the armored grenadier regiment of the 14th Panzer Division, but both Defensive Fire and Offensive Fire missed.
With this, the Soviet attacks are complete, and the Soviet player moved the units it did not use to attack. The situation at the end of the Soviet Player Turn is as shown in the diagram. After this, the German Player Turn of GT 1 is conducted.
Historical Note
"The enemy could not achieve the decisive breakthrough that would have encircled our forces at the Dnieper bend."
— Erich von Manstein, summarizing the Battle of Kirovograd
The winter of 1943–44 found the German forces in southern Russia in a very difficult situation. The Soviets retook Kiev in November and continued their advance to encircle the German forces along the Dnieper. In January 1944, Konev's 2nd Ukrainian Front captured Kirovograd, the strategic supply hub, and planned to destroy the 8th Army.
Battle for Kirovograd (the bonus game in the magazine) depicts this Red Army offensive and the German counterattack and withdrawal at the operational level.
Translator's note: the magazine's back-cover product copy (designer blurb, component list, price, barcode, and publisher copyright line) is not reproduced; the designer's name appears there as a credit.