Plevna
Plevna Rulebook
Table of Contents
Table of Contents
- 1.0 Introduction
- 1.1 Game Components
- 1.2 The Counters
- 1.3 The Map
- 1.4 Player Aids
- 1.5 Game Scale
- 1.6 Preparing for Play
- 2.0 Sequence of Play
- 3.0 Reinforcements
- 4.0 Movement
- 5.0 Stacking
- 6.0 Fire Zones
- 7.0 Combat
- 8.0 Morale
- 9.0 Disintegration
- 10.0 Victory Conditions
- 11.0 Commanders
- 12.0 Defensive Works
- 13.0 Bridges
- 14.0 General Withdrawal
- Plevna Scenario
- 17.0 General Errata
- 18.0 Additional & Advanced Rules
- New Rules
- 15.0 Special Tactics
- 16.0 Fog of War, Screens and Balloons
- 17.0 Friction
1.0 Introduction
If you are new to simulation gaming or have been away a while, we suggest you proceed this way:
- Examine the counters without punching them out, and skim through the Basic Rules. Do not try to memorize them.
- Study the game map and refer to the corresponding Battle Rules for details on how to set up the game.
- Punch out the counters needed for the battle and start moving them around on the map, referring to the rules as you move and fight.
These rules are a slightly modified version of the Empires at War boxed game. Players can use them to update the original Empires at War game.
1.1 Game Components
Chancellorsville & Plevna should contain:
- 1 Rulebook including Basic and Battle Rules.
- 1 battle map containing a map of the Chancellorsville and Plevna battle areas.
- 280 die-cut counters (one set for Chancellorsville on the left side, one set for Plevna on the right side, and one set of markers used in common).
- Players will need to provide two six-sided dice.
1.2 The Counters
The counters represent the forces engaged in the original battles. These are hereafter identified as "units." Additionally, there are counters used for various game functions, which are called "markers."
- Infantry, Cavalry, Artillery, Mitrailleuse and Engineers are considered combat units. The front side represents "Good Order;" the back side represents "Disrupted." Disrupted units have lower fire and movement values.
Unit Identification information is usually abbreviated in order to save space; see the Unit Abbreviations sections in the scenario rules.
Entrenchment markers are the game counters with the crooked (crenellated) line. Fieldworks are represented by the reverse side of this marker. Destroyed on-map entrenchments/redoubts are indicated by placing a blank marker in the hex, or by removing the appropriate marker from the map.
Mitrailleuse have an "arrow" symbol. There are no Mitrailleuse in Chancellorsville/Plevna, but this is for completeness.
Counter Errata
- The Union Res/II artillery should have the same colored stripe as the other II corps units.
- The Russian "GD" leader should have the same colored stripe as the other "GD" corps units.
- The Balloon and Cavalry Screen markers are for use in future game variant scenarios.
- The Disintegration and Army Ordered markers should be in contrasting colors to distinguish which armies they indicate.
- The Confederate HQ counter identified as "McLaw" should be spelled "McLaws."
- The Confederate HQ counter identified as "Picket" should be spelled "Pickett."
The "TURN" marker among the Confederate counters for Chancellorsville should be used as the "Game Turn" marker for both games.
Ignore the "SEGMENT" and "PLAYER" markers among the Confederate Chancellorsville counters; they are not used in either of these two games.
Plevna Counters
- The Turkish 1st Regiment of the 1st Infantry Division has a leadership rating of "E" on the front. It should be a "D". It should also have a morale value of "E" on the front.
- The Russian Cossack artillery unit should have the horse artillery symbol.
- The Russian HA/4/IV horse artillery unit (1 V 3) should be (1 V 5) on the front and (1 V 3) on the back.
1.3 The Map
The game maps show the area where the actual battles took place. A hexagonal grid is superimposed over the terrain to regulate placement and movement of units. Those hexagons are hereafter referred to as "hexes."
Plevna Map (omission): map north is toward the edge next to the Disintegration Track.
1.4 Player Aids
Assault Combat Results Tables (CRTs): there are two of these, "Skirmish" (used for light infantry tactics), and "Charge" (used for major assaults).
Bombardment Range Chart: shows the range of artillery units. See page R14.
Bombardment Table: used to resolve artillery bombardment attacks. See page R15.
Command Range Chart: used to indicate how many hexes away from a commander a unit can be and still be in command. See page R14.
Disintegration Chart: indicates the number of morale points lost or gained for various game events. See page R14.
Disintegration Track: records changes in morale points for each army; on the mapsheet.
Turn Record Chart: indicates the current game turn; on the mapsheet.
Leadership Table: generates command control status for units. See page R15.
Morale Table: used to rally disrupted units. See page R14.
Terrain Chart: shows the effects on movement and combat of various types of map terrain; on the mapsheet.
Sequence of Play: indicates the particular segment of a turn in progress. See section 2.0.
1.5 Game Scale
Each hex represents one mile in Chancellorsville or one kilometer in Plevna. Turn scale is set by scenario. Each division-sized unit represents 5,000-10,000 men; each brigade contains 1,000-3,000 soldiers.
1.6 Preparing for Play
-
After the players decide which side each will command, they place their side's units according to the deployment instructions in the Battle Rules. (The Special Rules section for each battle gives specific instructions for the battle chosen.)
-
The player designated as deploying first places units on deployment hexes printed on the map, according to the instructions. If a unit can be placed in more than one deployment hex, the owning player chooses one of the hexes. Units may be allocated among eligible deployment hexes in any fashion the owner desires. Deploy units within stacking limits (5.1).
-
Place each side's Disintegration Limit marker in the numbered box on the Disintegration Track, as specified in the Battle Rules. Both Ordered markers usually begin at zero (that is, to the left of the 1 space).
-
Place the Game Turn marker in the box on the Turn Record Chart containing the starting time listed in the Battle Rules. Place the Battle Ends marker in the box on the Turn Record Chart containing the ending time listed in the Battle Rules.
-
Place each side's reinforcement units (see Section 3) in the appropriate boxes (hour of entry) on the Turn Record Chart.
2.0 Sequence of Play
A game proceeds through a series of turns. Each "game turn" is divided into two "player turns," one for each player. A player turn is composed of a number of "segments." The Battle Rules specify which player is the first player in each game turn.
2.1 First Player Turn
-
Reinforcement Segment: the first player places new units on the map, according to the Battle Rules and rules for reinforcements.
-
Bombardment Segment: perform bombardment (7.1) with any and all friendly artillery and mitrailleuse units the first player wishes.
-
Movement Segment: during every friendly movement segment, the player must make a leadership check for all friendly units. That's done by first checking for commanders in order of echelon, and then finally individual units that aren't within any commander's command range. No unit may attempt movement until it makes a leadership check or a check is made for it by an eligible commander.
-
Assault segment: any and all infantry, cavalry and engineer units belonging to the first player may attack adjacent enemy units, if the owner wishes (7.2).
-
Rally segment: the first player attempts to restore all friendly disrupted combat units to good order (8.2). Place entrenchments and bridges on eligible friendly engineers.
2.2 Second Player Turn
Perform the same segments in the same order as in the First Player Turn, but substitute "Second Player" for "First Player." The Second Player's units are now considered "friendly."
- Reinforcement segment
- Bombardment segment
- Movement segment
- Assault segment
- Rally segment
2.3 End of Game Turn
-
Advance the game turn marker to the next space.
-
If the next box on the Turn Chart contains "Night," all the effects of night (Chancellorsville Scenario Special Rules 8.0) begin and last until the game turn marker enters the next box containing the word "Morning."
3.0 Reinforcements
Certain units enter play on certain turns specified in the Battle Rules under "Scheduled Reinforcements."
3.1 Placement
During the friendly reinforcement segment, reinforcements are placed off the map edge, adjacent to a designated entry hex. If there are two or more hexes from which to choose, place each unit on the map edge next to any one hex.
3.2 Entering the Map
3.21 During the friendly movement segment following the reinforcement segment, reinforcements must pay all normal movement costs to enter the entry hex.
3.22 Units may enter via road march (4.9).
3.23 Reinforcements are automatically "in command" during the movement segment they enter the map. They don't need to make a Leadership check (4.1).
3.24 Reinforcements must attempt to enter play on the designated turn.
3.3 Delay
3.31 Reinforcements that can't enter the map without violating normal movement and stacking rules must be delayed. A delayed unit is left adjacent to its initial entry hex.
3.32 A delayed unit must attempt to enter play during the next friendly movement segment at the same entry hex, or in any map edge hex within four hexes of the original entry hex. The hex selected becomes the new entry hex, in case the unit must be delayed again.
3.33 A unit may be delayed repeatedly without suffering a penalty; however, a delayed unit must attempt to enter play each and every turn until it succeeds.
4.0 Movement
Each unit moves individually from hex to hex, expending movement points (MPs) from its printed movement allowance for each hex entered. MPs cannot be saved from one turn to the next, or given to another unit. A unit's movement is final: once a player has moved a unit he may not retrace its movement that turn unless the opponent permits it.
4.1 Leadership
4.10.6 Leadership (addition): A Commander who receives an "I" result may be moved such that he ends his movement on any friendly unit of his command, as long as it is the one that is in closest contact with the enemy. i.e., a Commander does not have to charge ahead of his command and make a suicide run at the enemy.
(Additional commentary on rule 4.0): If a player makes command check for a Supreme Commander this means that all subordinate commanders and combat units within his Command Range, as well as commanders and units within extended command range must use that command result. For instance, if you have Hooker in a hex and he rolls an Out of Command result, he puts all corps commanders within four hexes Out of Command, as well as any units that might be within the corps commanders' Command Ranges. This would also apply to divisional commanders within those corps commanders' ranges. Effectively, the rule is "all or nothing." A poor commander is going to slow down his subordinates. A good commander will have his skills amplified by them. You can mitigate against a poor superior commander by moving him out of range and allowing his possibly higher leadership subordinates to conduct their own actions independently (although see the Hooker Special Rule), but bear in mind that since they roll for Leadership one at a time, this may lead to a fragmented battle—the historical outcome, QED!
4.2 Commanders & Leadership
4.21 There are three ranks of commanders: supreme, army and corps.
Plevna change:
- Russian. There are three ranks of commanders: supreme, corps and division.
- Ottoman. There are two ranks of commanders: supreme and division.
4.22 The supreme commander must select all friendly units within his range for leadership checks.
4.23 An army commander must select all friendly corps commanders with the matching army designation within range. He must also select combat units bearing the army designation, plus combat units subordinate to any of his corps commanders.
4.24 A corps commander must select all friendly division commanders with the matching corps designation within range. He must also select combat units within range bearing the same corps ID number and color stripe.
4.25 A division commander must select combat units within range bearing the same division ID number and color stripe.
4.26 Certain units within a corps may not have divisional commanders; they are commanded directly by the corps commander.
4.27 Leadership Markers. Players can, at their option, use the Leadership markers ("B," "C," "I," "O") to indicate the command status of units within a formation, and to indicate which units have completed their movement.
This is a change to the original Empires at War rules, where originally a player could choose whether a commander would take command of subordinate commanders and units or let them roll for themselves. Optionally, players may use the original rule, but this revision better reflects the conditions of 19th century warfare where inept commanders frequently overrode more adept subordinates.
4.3 Command Range
4.31 A commander can only select for leadership checks those eligible subordinate commanders and units within his command range. The range is measured in hexes, without respect to terrain costs. Count the subordinate's hex but not the commander's when determining the range.
4.32 Command Ranges are as follows:
- Supreme Commander = four hexes
- Army Commander = three hexes
- Corps Commander = two hexes
- Division Commander = one hex
4.33 Nothing restricts or blocks the tracing of command range, including intervening units, enemy fire zones and prohibited terrain.
4.4 Chain of Command
4.41 The supreme commander always performs the first leadership check of the friendly movement segment if he is in play, followed by the army commanders if any are in play, followed by the corps commanders, and then any division commanders (and, finally, any units outside the command range of all commanders). If two or more commanders of the same rank wish to make a check, the owner decides the order in which that occurs.
4.42 Determine which (if any) subordinate commanders and combat units the commander making the check will affect. There is no limit to the number of eligible subordinate commanders and units within his command range a single commander may affect.
4.43 Any unit or commander that receives a superior commander's leadership check doesn't make a leadership check for itself or other subordinate units during the same movement segment. One chance is all any unit gets each turn. Cover checked units with spare markers or rotate them 90 degrees as a reminder.
4.44 For example: a supreme commander can affect a friendly corps commander four hexes away, who can, in turn, affect a friendly division commander two hexes away, who finally affects a friendly combat unit one hex away. The use of commanders can, therefore, extend a supreme commander's range.
4.5 Combat Units
4.51 Most combat units are assigned to a particular corps or division, and therefore possess a color stripe running along the top of the counter to help players quickly identify their parent corps. Some combat units are directly attached to an army, indicated by the white stripe and black box enclosing the parent ID. A few have only a white stripe and no parent ID, which means they can only be selected for leadership checks by the supreme commander.
4.52 Once all commanders have made leadership checks or passed, each combat unit that hasn't yet been checked must make its own individual leadership check. A combat unit can only check for itself; it cannot have subordinates like a commander.
4.6 Procedure
After selecting a commander or unit and designating any subordinates, roll two dice, cross-index the result with the line on the Leadership Table corresponding to the leadership rating (printed inside a circle) of the unit or commander making the check, and apply the result to all units selected to receive the check, regardless of their printed leadership values. See the Leadership Table for outcomes.
Note that generally the leadership ratings generally go from best (A) to worst (F); however, "D" indicates an aggressive commander, who may in some circumstances be more useful than a good or average commander.
4.7 How Units Move
4.71 A unit may always move one hex in a friendly movement segment, regardless of terrain costs. No unit, however, may ever enter or cross prohibited terrain or enter an enemy-occupied hex.
4.72 A unit that has already moved at least one hex may not enter another hex or cross a hexside that would cause it to exceed its current movement allowance. It must either select another path or stop moving for that movement segment.
4.73 Units are allowed to move together in stacks, as long as all members of the stack begin the movement segment in the same hex and receive the same leadership check result (C, O or I). Units moving in stacks may be dropped off anywhere along the path of movement, but no new units can be picked up. Units in a stack that can move no farther must be dropped off, but some or all other units in the stack may also stop moving and remain with dropped-off units.
4.8 Terrain Effects
4.81 Each clear terrain hex entered costs one movement point (MP).
4.82 Certain hexes contain terrain that costs more than one MP to enter. When a unit attempts to move more than one hex, it must be able to pay the additional costs to cross into or enter each new hex. See the Terrain Effects Chart for a complete listing.
4.83 The following types of terrain and water features occur along the border of a hex (hereafter called a hexside) rather than inside a hex: river, stream, slope, ravine and bridge. There is a movement cost incurred when moving across such hexsides, which is added to costs for terrain types within hexes entered. For example, to cross a slope hexside to enter a town hex would cost two MPs for the town and one MP for the slope hexside crossed, a total of three MPs expended to move one hex.
4.84 Water
4.841 Hexes containing only sea or lake are prohibited to all units.
4.842 Movement across a river is prohibited except over a bridge.
4.843 Units moving across a bridge do not add the additional hexside movement cost if crossing a stream. They use only the bridge hexside cost.
4.85 Entrenchments
4.851 A hex with an entrenchment costs an extra MP to enter, over and above the normal cost for entering the hex.
4.852 Either side's units may enter a vacant entrenchment and make use of it normally. Entrenchments are always friendly to the side currently occupying them. They do not face in any particular direction.
4.9 Road March
A unit using Road March:
-
doubles its printed movement allowance — for example, four becomes eight;
-
pays one movement point per hex entered and crosses a bridge hexside at no additional cost. Slope and ravine hexside costs must be paid;
-
must begin and end its movement in a road hex and may only move through hexsides crossed by a road;
-
may never begin in a hex adjacent to an enemy unit or enter such a hex while moving;
-
may not enter a hex containing other friendly units, but may exit such a hex. Combat units may never use road movement while stacked with other combat units, commanders may.
-
obeys an impetuous movement result, but like other road marching units, it cannot move adjacent to enemy units. If an Impetuous unit can move adjacent to an enemy unit using normal movement, it may not use road march.
4.91 Trails. Some scenarios have trails. Units move along trails the same as roads, except they use their normal movement allowance, paying one MP per hex entered.
4.92 A unit may combine both road and trail movement in the same turn, doubling its movement on roads and paying one movement point per trail hex entered.
4.10 Impetuous Movement
4.10.1 A unit that receives an impetuous result on the Leadership Table must end its movement adjacent to the nearest enemy unit (in hexes), if it has the MPs to do so. If an impetuous unit cannot move adjacent to any enemy unit, it must end its movement closer to the nearest enemy unit. In case of ties, the moving unit's owner chooses the enemy unit to approach. Ignore all intervening units and terrain costs when determining the nearest enemy unit. Enemy commanders not stacked with combat units are eligible to be the nearest enemy unit.
4.10.2 An impetuous unit that begins movement adjacent to an enemy unit doesn't move at all. An impetuous unit may not enter or cross hexes containing enemy units or prohibited terrain.
4.10.3 Overstacking due to impetuous movement is resolved as in 5.4.
4.10.4 In the case of moving closer but not adjacent to an enemy unit, an impetuous unit must employ road march (4.4) if eligible.
4.10.5 Impetuous units that can't move due to any of the above suffer no penalties.
4.11 Fall Back Movement
4.11.1 A unit that receives a fall back result on the Leadership Table must move as far and as directly as possible toward the nearest map edge or other location identified as a friendly line of communication (LOC) in the Battle Rules.
-
Such units may never enter prohibited terrain, enemy-occupied hexes or enemy fire zones.
-
If such a unit can't move at all, or can't move any farther due to the restrictions in 1 above, it stops moving for the segment and makes a morale check (8.1). If it passes, nothing further happens. If it fails, the unit is disrupted due to rout.
-
A unit that stops moving simply because it lacks the remaining movement points to enter another hex doesn't make a morale check.
-
A friendly unit using fall back movement must use road march if it begins movement on a road hex that is part of a connected line of road hexes of any length leading to a friendly LOC and there is no enemy combat unit on or adjacent to a road hex within five hexes of the friendly unit. A unit that falls back using road march must attempt to follow the shortest path of connected road hexes leading to the nearest LOC.
-
If a unit falling back using road march would be forced to move adjacent to enemy units or into a friendly occupied hex, it stops in the previous hex and makes a morale check. If it passes, it stops moving for the segment without further penalty. If it fails, it is immediately disrupted.
-
A fall back unit that reaches a map edge simply stops. It doesn't exit the map. EXCEPTION: if General Withdrawal is in effect, see rule 14.0.
5.0 Stacking
Each hex may contain only a certain number and type of combat units at the end of each movement or assault segment.
5.1 Stacking Limit
A hex can contain: one infantry or one cavalry unit (not both), plus one artillery or one mitrailleuse unit (not both), plus one engineer unit, plus any number of other units (for example, commanders) or markers.
5.2 During Movement
Units may move through a friendly occupied hex in excess of the stacking limit without penalty, except during road march (4.4). Overstacking is resolved at the end of each movement segment (see Overstacking below).
5.3 During Assault
Units may move through a friendly occupied hex in excess of the stacking limit without penalty. See retreat (7.3) and advance after combat (7.4). Overstacking is resolved at the end of each assault segment (see Overstacking below).
5.4 Overstacking
5.41 If stacking limits in a hex are violated at the end of a movement or assault segment, excess units of the owning player's choice must displace into an adjacent safe hex that contains no enemy units or prohibited terrain. Obey the three priorities for retreat movement (7.3). Displacing units make morale checks (7.35, 8.1) like retreating units.
5.42 The owner continues to select and displace excess units in each overstacked hex until stacking limits are met. Units unable to perform displacement due to the presence of enemy units or prohibited terrain are eliminated.
5.5 Secrecy
Enemy units placed beneath the top unit in a stack may not be examined unless a friendly unit is currently adjacent to the stack. An enemy stack may be examined the instant that condition is met, and any time thereafter, as long as a friendly unit remains adjacent to it.
6.0 Fire Zones
The six hexes surrounding a unit (whether in good order or disrupted) form its fire zone (FIZ). An artillery or mitrailleuse unit only exerts a FIZ into adjacent hexes, regardless of its maximum firing range. The presence of enemy units, enemy FIZs and prohibited terrain don't limit the effects of a friendly FIZ.
6.1 During Movement
6.11 A unit that begins its movement outside an enemy FIZ must stop when it enters an enemy FIZ. It may move no farther that turn.
6.12 A unit that begins its turn in an enemy FIZ may exit without penalty, but may not enter another FIZ during the rest of its movement that segment.
6.12 Fire Zones (Clarification): Furthermore, units may never move directly from one fire zone to another fire zone.
6.2 During Assault
6.21 Units may advance after combat into and through enemy FIZs, without penalty.
6.22 A unit may retreat into an enemy FIZ, but must perform a morale check each time it does so. See Retreat (7.3) for details.
7.0 Combat
There are two types of combat in the game: bombardment (ranged combat) and assault (adjacent). Bombardment is conducted by artillery and mitrailleuse units using the Bombardment Table in the bombardment segment. Assault is conducted by infantry, cavalry and engineer units using either the Skirmish or Charge Combat Results Tables (CRTs) in the assault segment.
7.1 Bombardment
Artillery and mitrailleuse units may fire at enemy occupied hexes within range. Bombardment in no way limits a firing unit's ability to move during the upcoming friendly movement segment.
7.11 Some, none or all friendly artillery and mitrailleuse units may fire during the friendly bombardment segment. Each unit can direct its fire at one target hex per segment. Units may fire by themselves or in groups, as long as the single enemy target hex is within the range of all firing units.
7.12 A target hex can be attacked any number of times by bombardment during a segment, as long as no attacking unit fires more than once. The number, type and strength of units in the target hex do not affect the outcome.
7.13 The Bombardment Range Chart lists the maximum ranges for artillery and mitrailleuse units belonging to each side in a battle. Units may fire only at enemy occupied hexes within range. Count the target hex but not the firing unit's hex when determining the range.
7.14 Each unit conducting bombardment at a range of two or more hexes does so at half fire strength. Bombarding a target inside a ravine also halves a unit's fire strength. If both conditions apply at the same time, divide the unit's printed strength by four. Drop fractions as indicated on the Bombardment Table.
NOTE: A target is inside a ravine if it's adjacent to the teeth of two or more ravine hexsides and each bombarding unit fires through a ravine adjacent to the target.
7.15 Line of Fire
A unit may always fire into an adjacent hex. If the range is more than one hex, trace a line of fire (LOF) to the target. LOF is a straight line from the center of the firing unit's hex to the center of the targeted unit's hex. If a LOF intersects any blocking terrain, the firing unit may not fire at the selected target, but may then still choose another target.
7.151 Blocking Terrain
- Town and City
- Woods
- Fort and City Wall
- Slope hexside
- Peak (see 7.155 below)
7.152 Terrain inside a firing or target hex never blocks LOF. Terrain along hexsides adjacent to a firing or target hex also doesn't block LOF.
7.153 A Slope hexside blocks LOF whether it's traced up or down the slope, unless the firing or target unit is adjacent to the slope. LOF can be traced directly along a slope hexside (between two hexes) if there is no other type of blocking terrain in either adjacent hex. LOF may not be traced directly along the hexside of a hex containing non-slope blocking terrain.
7.154 Combat units block LOF traced by a mitrailleuse unit. LOF for a mitrailleuse unit may not be traced directly along the hexside of a hex containing enemy or friendly combat units. Only regular artillery could employ indirect plunging fire.
7.155 Peak: LOF into and out of a peak hex are never blocked for any reason, as long as the LOF is traced through a slope hexside adjacent to the peak hex. (This gives a realistic "higher ground" advantage to Bombarding units.)
7.156 If conflicts about LOF determination can't be resolved any other way, settle the matter with a die roll or coin toss.
7.16 Bombardment Procedure
-
Add together the fire strengths of all units firing at a single target hex.
-
Find the appropriate column on the Bombardment CRT. Attacks of less than one are not allowed; attacks worth more than eight are resolved on the 8(+) column.
-
Shift a number of columns left for terrain, as indicated on the Combat Modifiers: Bombardment column of the Terrain Chart. NOTE: A target in an entrenchment always receives that shift, no matter from what directions the bombardment fire enters its hex.
-
Roll a die and apply the results as indicated beneath the table. Ignore disruption results against units already disrupted. There are no retreats or advances after bombardment.
7.2 Assault
Infantry, cavalry and engineer units must attack adjacent enemy occupied hexes in the assault segment. Attacking is mandatory for these combat unit types. A player must attack in such a manner that all adjacent defending units are attacked.
7.21 Each unit can attack once per segment. Each enemy occupied hex may be attacked any number of times in a segment.
7.22 Units in different hexes may attack a single adjacent defending hex in any one of the following ways:
- all available units combine in one attack;
- each unit attacks individually;
- some units combine into one or more attacking groups while the remainder attack individually.
7.23 Attacks by different units or groups of units may be resolved in any order the attacker desires. Each separate attack must be directed at a single enemy hex. If attacking units are adjacent to more than one enemy hex, they may select one or more units to attack. Each attacking group can choose a different CRT (skirmish or charge).
7.24 Choice of CRT
The attacker can choose to use either the skirmish or charge CRT for each combat. To use a particular CRT, units with at least 50 percent of the printed attacking combat factors must be involved in the attack. Qualification is stated in the scenarios. For example, the player attacks with five factors of skirmish-qualified infantry and four factors of charge-qualified cavalry. He could attack only using the skirmish CRT.
7.25 Multiple Unit Attacks
7.251 If there is more than one attacking unit in a hex, each may attack different enemy hexes. All defending units in a single hex must be attacked as a combined whole. The attacker may allocate units for specific attacks at any point in the assault segment; however, if he fails to attack all enemy units to which he had friendly units adjacent at the start of the segment, any friendly units that are adjacent to enemy units that weren't attacked are automatically eliminated, regardless of the outcome of other combats.
Artillery. Artillery defends against adjacent units using its printed fire strength the same as cavalry, infantry and engineer units (it does not bombard in the defense). Artillery adjacent to enemy units may never attack using assault combat. Artillery may not advance after combat (it is subject to retreat).
Commanders. Commanders are not required to attack; however, if they are stacked in a hex with a unit, they may provide their morale value for morale check results, and may be subject to retreat and advance after combat (see 7.3 & 7.4).
Design Note. The mandatory assault rule is a change from the original Empires at War game. It represents the tendency of units to become engaged in firefights as they approached enemy formations.
7.26 Entrenchments
7.261 The shift for defending in an entrenchment or fieldworks hex is always received, regardless of what direction the attacker's units are coming from. Units attack out of entrenchments normally.
7.262 If an engineer unit is participating in an assault attack against an entrenchment, redoubt or wall hex, shift the combat odds one to the right cumulative with other shifts.
7.27 Assault Procedure
-
Designate the attacking unit(s) and the single defending hex.
-
Choose either the skirmish or charge section of the assault CRT. Units may only combine for an attack if they can all use the same section of the CRT. All infantry, cavalry and engineer units may use the Charge CRT. Only skirmish-capable Infantry and cavalry can use the Skirmish section.
-
Total the fire strength of all the attackers. If that is larger than the total strength of all defenders (including artillery and mitrailleuse units) in the target hex, divide the attacker's total by the defender's total and drop any fraction. The result (N) is expressed as a ratio N/1. If the attacker's total is smaller than the defender's total, divide the defender's total by the attacker's total and round up any fractions to the next whole number (N). The result is expressed as a ratio 1/N. Odds of less than 1:3 are treated as 1:3. Odds of greater than 6:1 are treated as 6:1.
-
Make any column shifts left or right for the defender's terrain; see the Assault column under Combat Modifiers on the Terrain Chart. All shifts for terrain effects are cumulative, except when some units attack through unbridged stream hexsides while others in the same combat attack through bridge hexsides. In that case the -1 shifts aren't added together to create a -2 shift. Instead, the shift remains -1.
-
Roll a die and apply the results listed at the bottom of the Assault CRTs.
7.27.1 The 1.5/1 odds column is used when the attacker has 50 percent or more strength than the defender but less than twice as much (for example, eight combat factors to five).
7.3 Retreat
7.31 Each unit may retreat individually or as part of a stack containing other retreating units, but units retreating from the same hex aren't required to conduct retreat movement in a stack.
7.32 A unit or stack required to retreat by the result of a particular attack is immediately moved by the owning player according to the following three priorities:
- into a vacant hex NOT in an enemy FIZ;
- into a friendly-occupied hex;
- into a hex containing an enemy FIZ, but not an enemy unit.
7.33 A retreating unit must make a morale check (8.1):
- after it enters an enemy FIZ, whether vacant or already occupied by friendly units; or
- after it retreats across a stream or bridge hexside.
If the unit passes, there is no effect or, if required to retreat two hexes, retreats another hex as per above. If it fails, the unit is eliminated.
7.34 Retreating units required to retreat two hexes may move through friendly occupied hexes in excess of the stacking limit at no penalty. Retreating units that end their retreat overstacked (regardless if after a one or two hex retreat) must resolve the overstacking by displacement at the end of the assault segment (see 5.4).
7.35 A unit that can't retreat at least one hex because it can only cross or enter prohibited terrain or enemy occupied hexes is immediately eliminated. A unit required to retreat two hexes that retreats one hex but cannot retreat farther (prohibited terrain or enemy occupied hexes) makes another morale check. If it passes, it stops and remains in the hex. If it fails, it is eliminated.
7.4 Advance After Combat
7.41 After all assaults are rolled and resolved, if one side's units are cleared from a hex, any of the other side's units involved in the combat that are still adjacent to the cleared hex may advance into it. No Leadership checks are required. Overstacking (5.4) is resolved at the end of each advance after combat.
7.42 Units may advance after combat into and through enemy fire zones without making morale checks, but no unit may advance into or across prohibited terrain or into enemy-occupied hexes.
A cavalry or leader unit may choose to advance up to two hexes. The first hex must be the vacated enemy hex. The second may be any (then) adjacent hex not occupied by enemy units or containing prohibited terrain. All other rules for advance apply. Artillery units may never advance after combat. They do retreat normally.
7.5 Disruption
Units on their front side that receive a disruption result due to any game function are flipped to their reverse side. Unit combat and movement values are lower on the reverse side. A disrupted unit that is disrupted again is not further reduced or eliminated, with the exceptions noted under the retreat rule (7.3). Disrupted units recover to their full strength via rally (8.2).
Design note: the resiliency of disrupted units to combat results represents the difficulty of close assaulting units owing to the greater defensive range of weapons as well as the use of skirmish formations.
8.0 Morale
Each combat unit has a morale rating that's used to make morale checks for various game functions.
E = Elite, T = Trained
V = Veteran, R = Recruit
8.1 Morale Checks
-
Roll a die for each unit and cross-index the result with the unit's morale rating on the Morale Table. The unit will either pass or fail the check, depending on the die roll.
-
A disrupted unit that fails a morale check after retreating into an enemy fire zone, or across a stream or bridge hexside, is eliminated. In all other cases, additional disruption results have no effect on an already disrupted unit; it remains disrupted.
8.2 Rally
During the friendly rally segment, each friendly disrupted unit rolls for rally on the Morale Table. If the unit passes, it is immediately flipped over to its stronger good order side. If it fails, it remains disrupted but suffers no further penalty.
9.0 Disintegration
Disintegration refers to the overall morale of an army. The Battle Rules list the initial placement of each side's Disintegration Limit marker on the Disintegration Track. Use an Ordered marker to keep track of the current disintegration level. Each side keeps track of its own level.
9.0 Disintegration Chart
(clarification): A disrupted unit which is disrupted again increases the Disintegration Level by 1 point (remember, a disrupted unit which is disrupted again in combat is not eliminated (except if retreating through an enemy Fire Zone, see [7.33]). A unit which is eliminated owing to a retreat through an enemy Fire Zone counts for Disintegration Points.
(clarification): "No friendly unit attacks during friendly bombardment or assault segment," means that if you do not conduct any attacks in a turn (that is, no bombardments and no assaults), then you will reduce your Disintegration Level by 5 points. The intent of the rule is that if a player conducts no offensive combat during a turn, his army recovers some of its cohesion.
9.1 Disintegration Level
9.11 Both Ordered markers begin the game at zero (that is, to the left of the 1 space) on the Disintegration Track, unless otherwise specified in the Battle Rules.
9.12 Certain game events will cause a side's disintegration level to rise or fall, according to the Disintegration Chart.
9.13 When a side's Ordered marker enters or passes through the numbered box containing its Disintegration Limit marker, that side suffers disintegration. Flip the ordered marker over to its broken side. Once a side is broken, it remains so for the rest of the game. It is no longer necessary to keep track of that side's disintegration level (broken = disintegration).
9.14 Disintegration can occur whether or not the opposing side has already suffered disintegration.
9.15 The disintegration level never falls below zero.
9.2 Effects of Disintegration
Morale ratings for all units are lowered by one level for all game functions: E becomes V; V becomes T; T becomes R; R remains R.
9.22 Leadership radii are reduced to zero (the same hex as a commander). Leadership ratings are not changed (for example, an A commander would remain an A).
9.23 A unit that receives an I result on the Leadership Table during a friendly movement segment treats the results as an F (Fall Back). See 4.11.
9.24 A unit that receives a C or O result on the Leadership Table during a friendly Movement segment behaves normally.
9.24 Disintegration (omission): Also, a unit that receives a B result may execute a Brilliant Maneuver.
10.0 Victory Conditions
The Battle Rules list specific conditions for achieving a particular Victory Level.
10.1 Victory Levels
- Marginal: the enemy is pushed back, but escapes intact and the war continues.
- Tactical: enemy military strength is destroyed in this theater. The war continues, and will probably go in your favor; you get a medal.
- Decisive: the enemy capitulates. You are on the way to winning the entire war.
10.2 Multiple Victory Levels
If both sides achieve a victory, subtract the lower level from the higher level to determine the final outcome. Example: one player attains a decisive victory and the other a marginal, which results in the superior player winning a tactical victory.
10.3 Draws
If both players attain the same victory level, or neither player attains any type of victory, the game ends in a draw.
11.0 Commanders
Commander units provide bonuses for leadership and morale.
11.1 Leadership
11.11 Commanders must make leadership checks just like combat units. A commander may not automatically move as the owning player wishes.
11.12 See Leadership (4.1-4.6) for details about the special role commanders can play in the process.
11.2 Movement
11.21 Commanders may move by themselves like combat units. They may also move in stacks, but must obey all basic game rules for movement and retreat in stacks (also see 15.3).
11.22 A commander who, after receiving an impetuous or fall back leadership check, completes his movement in a hex that doesn't contain any friendly combat units may be picked up by the friendly player and placed with the nearest friendly combat unit. That's done at the end of the friendly movement phase, after all units have completed their movement. The hex moved to must be within four hexes of the commander's hex and may not be through enemy units, FIZs or prohibited terrain. In case of ties for the nearest unit, the friendly player decides. This prevents leaders from becoming separated from their men unrealistically and subject to overrun on the battlefield.
11.3 Stacking
11.31 Any number of commanders may occupy a single hex without violating stacking limits.
11.32 Enemy units may not enter hexes containing only commanders. That is, commanders block enemy movement in their hex as if they were combat units.
11.4 Combat
11.41 Commanders have no fire strength or fire zone and never contribute to attack or defense.
11.42 A commander is eliminated whenever he is in a hex that does not contain a friendly combat unit and:
- the hex suffers a bombardment result of A (only one commander is eliminated if two or more occupy the hex; make the choice randomly) or;
- the hex undergoes an enemy assault.
11.43 Any number of commanders may advance after combat with a combat unit, as long as they begin the advance in the unit's hex and end the advance stacked with the unit.
11.44 If all friendly combat units in a hex are eliminated in combat or retreat, all commanders in the hex are also eliminated.
11.45 Leaders retreat with other friendly units in their hex.
11.46 Commanders are otherwise never affected by disruption results.
11.5 Morale
11.51 A combat unit making a morale check (8.1) for any purpose has the option to use the morale rating of one commander occupying its hex in place of its own morale rating.
11.52 A commander may substitute his morale rating for each and every unit making a morale check in his hex.
11.53 Ignore chain of command, army, corps and division assignments, and other command restrictions when substituting morale ratings. In effect, any commander can help any friendly unit in his hex if the owning player wishes. For example, a corps commander may rally units of another corps, though he couldn't normally command them.
11.6 Disintegration
11.61 Eliminated commanders count toward disintegration, and commander morale ratings are reduced when disintegration takes effect.
12.0 Defensive Works
Entrenchments and redoubts provide advantages to the defending player (see the Terrain Effects Chart for their effects on movement and combat). Entrenchment markers represent prepared positions. Redoubts represent prepared positions that face in only one direction. There are no redoubts in Chancellorsville/Plevna, but the rule is included for completeness.
12.1 Entrenchments
12.12 Removing Entrenchments
12.121 Entrenchments of all kinds remain on the map even if there are no units occupying them.
12.122 Entrenchments never retreat, disrupt, or become eliminated by combat. If an enemy unit occupies friendly entrenchments, the enemy player gains their defensive advantages.
12.123 Only an engineer unit can destroy an entrenchment marker or an entrenchment symbol printed on the map. The engineer must perform the same procedure as the one for building an entrenchment. Remove the marker or place a Destroyed marker over the printed entrenchment during the friendly rally segment.
12.2 Redoubts
12.2 Redoubts are treated the same as printed entrenchments, except the defender receives the defensive benefit for the redoubt only if all attacking units are attacking through the outer teeth of the redoubt; if any attacking unit attacks through another hexside, the defensive benefit is lost.
13.0 Bridges
13.1 Bombardment
-
During a friendly bombardment segment, a player designates a target hex within range of all participating artillery units that contains at least one bridge hexside, then selects one bridge as the actual target of the bridge attack.
-
Make a normal bombardment attack. Mitrailleuse units may not participate. (Machinegun fire against bridges was ineffective.)
-
A result of D or A (including D? and A? results if the attacker passes a morale check) destroys the bridge.
-
Units adjacent to the bridge are never affected by fire directed at the bridge.
13.2 Engineers
13.21 An engineer unit that meets the usual qualifications for building or repairing a bridge (see above) can instead attempt to destroy one bridge of its choice spanning an adjacent hexside.
13.22 Perform a morale check during the rally phase.
- If it passes, the bridge is destroyed. Remove the bridge marker or place a destroyed marker on the printed bridge symbol.
- If it fails, the bridge remains intact. The engineer may try again next turn if it meets all the normal requirements.
13.3 Building Bridges
Engineer units are capable of repairing destroyed bridges. This is done during the rally phase. To do so, the engineer unit must be adjacent to a bridge hexside that has been destroyed. It also may not have moves in this player turn. Make a morale check: if it passes, remove the bridge destroyed marker; otherwise, the bridge remains destroyed. Engineer units may also build pontoon bridges, if they have been assigned pontoons by the scenario. Follow the same procedure for repairing bridges, except the unit may be adjacent to any river or stream hexside. If successful, place a pontoon marker on the hexside and it functions as if it were a printed bridge. Each pontoon may be used only once per game. If destroyed, it is permanently removed from play.
14.0 General Withdrawal
A player may call for a general withdrawal at any time during a friendly player turn. Flip the friendly Disintegration LIMIT marker to its Withdraw LIMIT side to indicate that general withdrawal is in effect. That action is not reversible; it remains in effect for the remainder of the game.
14.1 Effects of General Withdrawal
- Increase the disintegration points of the withdrawing side by 20. If that causes that side to reach or exceed its disintegration limit, indicated by the Withdraw LIMIT marker, disintegration immediately takes effect.
- Decrease the opponent's disintegration points by 10 if the opponent has not already declared general withdrawal.
- Impetuous and fall back units must move directly toward the nearest friendly line of communication, as in 4.10 & 4.11. If they reach the map edge they must exit the map.
14.2 Exiting the Map
Units belonging to a side that has declared general withdrawal may exit through any map edge designated as a friendly LOC during friendly movement, or as a result of retreat from combat. Simply move or retreat the unit to a hex bordering the LOC map edge, pay an additional movement point (or retreat another hex if permitted by the combat result), and remove the unit permanently from play. Units withdrawn in that manner may not return to play, but neither are they considered eliminated for disintegration and victory purposes.
Plevna Scenario
Scenario notes: the game covers the great assault of 11 September 1877, in which the Ottomans repulsed the Russians after fierce fighting.
Plevna Scenario, Russian Empire Deployment. The references to the Rumanian "2", "3" and "4" Corps are the "2", "3" and "4" Divisional deployment zones printed on the map.
1.0 Sequence of Play
First Player: Russian Empire. Second Player: Ottomans.
2.0 Time Limits
First Turn: 0900 Last turn: 1800 Night Turns: none
3.0 Disintegration Limit
Russian Empire: 30. Ottomans: 30.
4.0 Lines of Communications
Russians: All north and east map edge hexes.
Ottomans: All hexes of Plevna.
5.0 Victory Conditions
Russian Empire:
- Marginal: occupy at least 15 Ottoman entrenchment hexes.
- Tactical: Ottomans become broken.
- Decisive: Occupy all hexes of Plevna.
Ottoman:
- Marginal: Russians occupy five or fewer Ottoman entrenchment hexes.
- Tactical: Russians become Broken (historical result).
- Decisive: Occupy at least four road hexes on the north or east map edges.
6.0 Deployment
Ottoman:
Deploy first. Must be placed within stacking limits.
In any Ottoman entrenchment and/or Plevna town hexes: Osman Army Commander, 1st Division, 2nd Division, 3rd Division and Reserve Division. Ottoman player must place at least one infantry and one artillery unit in Dolnyi Dubujak (1602).
Russian Empire:
Deploy second, in or adjacent to indicated hexes containing green symbols. Must be placed within stacking limits.
Plevna Scenario, Russian Empire Deployment (omission): The army level (9V2) siege artillery is deployed the same as the other army level units. The references to the Rumanian "2", "3" and "4" Corps are the "2", "3" and "4" Divisional deployment zones printed on the map.
General: References to "Contingency Reinforcements" should be ignored; they are for use in a later variant game.
Russian Army Level: Zotoff Army Commander, Escort Cavalry, 3rd Engineers, 1/11 Cavalry, Don Cossacks, Cossack Artillery, on or adjacent to any Russian "SK," "IV," "IX" or "Cav" deployment hexes. [SK 0813, 0912; IV 0617, 0620, 0820; IX 1122, 1124, 1313, 1324; Cav 0902, 1303, 1705, 2004, 2109; 4 1623, 1823; 3 2020, 2119, 2 2515, 2517.]
Russian IV Corps: Kryloff Commander, 16th, 30th Divisions, 4th Engineers, on or adjacent to any "IV" deployment hexes.
Russian IX Corps: Krudener Commander, 5th, 31st Divisions, 9th Engineers, on or adjacent to any "IX" deployment hexes (19th Regiment/5th Division starts the game disrupted).
Skobeloff Detachment: Skobeloff Commander, 2nd Division, 4th Rifle Brigade, Caucasian Cavalry, on or adjacent to any "SK" hexes.
Russian 4th Cavalry Division: 4th Cavalry Division units may be placed on or adjacent to "IV" and/or "Cav" hexes.
Russian 9th Cavalry Division: 9th Cavalry Division units may be placed on or adjacent to "IX" and/or "Cav" hexes.
Rumanian Army Level: Karl Commander may be placed on or adjacent to "2," "3," or "4" hexes.
Rumanian 2nd Division: all units are placed on or adjacent to any "2" divisional deployment hexes.
Rumanian 3rd Division: all units are placed on or adjacent to any "3" divisional deployment hexes.
Rumanian 4th Division: all units are placed on or adjacent to any "4" divisional deployment hexes.
Rumanian Cavalry Division: May be placed on or adjacent to "2," "3," "4" or "Cav" hexes.
Not initially deployed: Grand Duke Nicholas Commander, Guard division, deployed only if using Special Rules.
7.0 Scheduled Reinforcements
Russian Empire: none. Ottoman Empire: none.
8.0 Special Rules
-
CRTs. All Russian and Ottoman line infantry and engineer units are qualified to use both the skirmish and charge CRTs. Ottoman irregular infantry may utilize only the skirmish CRT. All regular cavalry units may utilize only the Charge CRT. All irregular cavalry units may utilize only the skirmish CRT.
-
Russian/Rumanian Alliance. All Russian and Rumanian units are considered to be the same for purposes of command, etc.
-
Russian Command Structure. Zotoff is the Russian supreme commander; he may command all Russian units. All Russian and Rumanian commanders are subordinate to him. (Technically, Zotoff was chief of staff to Prince Karl of Rumania, the actual supreme commander, but Zotoff actually ran the battle.)
-
Ottoman Command Structure. Osman is the Ottoman supreme commander. There are no Ottoman corps commanders; all division commanders are directly subordinate to Osman.
"What If?" Forces. Players may add the following units to any game of Plevna by mutual agreement:
Russian Guard: using this option, the Russian player adds all Guard Division ("GD") units to his starting deployment. They may be placed on or adjacent to any one Russian deployment hex. The Russian player adds the Grand Duke Nicholas commander to his starting force, replacing Zotoff, who is removed from play. Nicholas becomes the Russian supreme commander. Nicholas may be placed on or adjacent to any Russian deployment hex. The Guard is a division-level echelon of command, directly subordinate to the Russian supreme commander. Raise the starting Russian disintegration limit by 10 points. Shift the final victory level one in favor of the Ottomans. (For example, a Russian tactical becomes a marginal, a draw an Ottoman marginal, etc.)
Unit Abbreviations (Plevna)
Russian Empire:
- Art: Artillery
- C: Cossack
- Cauc: Caucasian
- Cur: Cuirassier
- GD: Guard
- HA: Horse Artillery
- Izm: Izmailoff
- Mosc: Moscow
- Rif: Rifle
- Rum: Rumanian
- Sapp: Sapper (Engineer)
Ottoman Empire:
- Aux: Auxiliary
- BB: Bashi Bazouk
- Cauc: Caucasian
- Nizam: Regular Army
- Redif: Reserve Army
- Rel: Relief
- Res: Reserve
17.0 General Errata
Map Terrain Key (omission): Entrenchments are the type of terrain in Plevna hex 1115. There are actually no redoubts on either map. Fieldworks are the game counters with the crooked line.
Terrain Effects Chart:
(error): Bridges are +1 to cross the hexside without road march (and +0 with road march).
Terrain Effects Chart:
(error): Ignore the Fieldworks note, "Defensive benefit only if all attackers attacking across." Fieldworks actually provide defensive benefits to units in their hex.
(clarifications): Entrenchments are the type of terrain in Plevna hex 1115. Redoubts and Fieldworks are not on either map. References to Flanking and Sapper Attacks are for use in game variants or other scenarios.
18.0 Additional & Advanced Rules
(Add to [12.0] DEFENSIVE WORKS)
12.3 Fieldworks
12.31 Any infantry or engineer unit can build Fieldworks. In Chancellorsville, cavalry units can also build fieldworks. Each unit can build any number of Fieldworks during the course of an entire Battle, but only one per unit per friendly player turn.
12.32 Procedure: The building unit may not move, be in an enemy Fire Zone, or attack during the player turn of building. At the conclusion of the friendly Rally segment, place a Fieldwork marker in the unit's hex.
12.33 Fieldworks are removed from the map at the instant that a friendly unit no longer occupies one. If an enemy unit occupies friendly entrenchments, then the Fieldwork marker is eliminated (the enemy may not capture and use friendly Fieldworks). 12.34 There may never be more than one type of defensive work in a hex. A player may build an Entrenchment in a hex containing a Fieldwork marker, but the Fieldwork marker is removed at the instant that the Entrenchment marker is placed. Fieldworks or Entrenchment may never be built in a hex containing an Entrenchment or Redoubt.
12.35 Players may recycle destroyed Entrenchments and Fieldworks or make additional markers if the supply runs out. Players may also remove Entrenchment and Fieldworks markers from the map by mutual agreement, to reduce needless clutter.
New Rules
15.0 Special Tactics
15.1 Cavalry Pursuit Attacks. After completing an advance of one or two hexes, a cavalry unit may immediately attack again.
15.11 Any number of eligible cavalry units involved in an Assault attack may conduct Pursuit Combat. Pursuit Combat is resolved for each advancing cavalry unit individually, and each cavalry unit must resolve all Pursuit activity before another may perform Pursuit. Use all normal rules for Assault combat, plus pursuing unit's Fire Strength is doubled after all other modifications. Units may not combine their Fire Strengths in Pursuit combat.
15.12 If a Cavalry unit advances after resolving Pursuit combat again, and ends its advance adjacent to an enemy unit, then it may immediately perform another Pursuit attack. The process continues until the Cavalry unit cannot advance after combat, chooses not to advance, does not end its advance adjacent to an enemy-occupied hex, or is eliminated.
15.2 Cavalry Retreat Before Combat
Any Good Order cavalry unit which is attacked by any enemy non-cavalry units in an Assault Segment may Retreat Before Combat. This is executed at the instant that the attack is declared. Retreat Before Combat may be attempted only in an enemy Assault Segment and at no other point in the game turn.
15.21 Procedure. The cavalry unit makes a Morale Check.
If it fails, then it remains in place (and receives any attack normally).
If it passes, then it is moved by the friendly player one or two hexes, utilizing normal rules of retreat. The enemy may advance after combat normally. The unit may be attacked again in this Assault Segment if it ends up adjacent to enemy units. However, enemy units which advanced after a cavalry unit which retreated before combat may not attack again in the same Segment.
15.3 Flank Attack
If during Assault Combat a defending unit is attacked such that attacking units are on or adjacent to the hexes on all six hexsides of the defending hex, then the attacker receives a shift of +1 (increasing combat odds by two columns). A Flank Attack could occur if there were at least two attacking units on opposite sides of the same hex, or at least three attacking units on every other adjacent hex. Only attacking units which are attacking a specific hex count for determining if a flank attack is taking place. Other adjacent attacking units which are attacking other hexes do not count.
15.4 Sapper Assaults. Engineer units which conduct Assault Combat provide a +1 positive column shift modifier when attacking enemy units defending in an Entrenchments or across Redoubt hexsides (but not against Fieldworks). This benefit is received regardless if the engineer unit is attacking by itself or in conjunction with other friendly units.
16.5 Disengagement. Change 6.1 as follows: Only Cavalry and Commanders may freely leave enemy FIZs as per 6.1. Other units must make a Morale Check. If they succeed, they may exit the enemy FIZ normally. If they fail, they remain in place (they are not disrupted by failing the Morale Check).
15.6 Routing through Friendly Formations. Whenever a unit retreats into or through a hex containing another friendly unit, then the units in that hex must immediately make a Morale Check. If they pass, nothing happens. If they fail, then they are disrupted. Already disrupted units remain disrupted if they fail the Morale Check, but must retreat one hex.
16.0 Fog of War, Screens and Balloons
16.1 Players may examine enemy stacks only during combat or if they have units adjacent to them. Artillery may still fire on unexamined stacks.
16.2 Additionally, a friendly unit on the upper side of a slope hexside may examine any enemy unit within four hexes, if they can trace a path of hexes in the same manner as an artillery Line of Sight [7.15].
17.0 Friction
The numerous imponderables of war and unexpected twists of fate that degrade or enhance an army's capabilities are called "Friction."
17.1 At the start of each Player's Turn, before any other game activity occurs, there is the Friction Segment. The player rolls two dice and consult the Friction Table to determine whether an event occurs. Friction results are applied immediately. A result may occur more than once, unless otherwise noted.
17.2 See specific battle rules for any Contingency Reinforcements.
Friction Table
Roll two dice. The first number rolled is the first digit, the second is the second digit. Then cross index with the event (e.g., if you roll a "3" and a "1" then event "31" occurs).
- 11-13: Ammunition Shortages
- 14-15: Army Morale
- 16: Command Breakdown
- 21-22: Intelligence
- 23-24: Extreme Weather
- 25-26: Poor Visibility
- 31: Contingency Reinforcements
- 32-33: Accelerated Reinforcements
- 34-36: Delayed Reinforcements
- 41-46: Scenario Special Event "A"
- 51-53: Scenario Special Event "B"
- 54-66: No event this player turn
Friction Events Explanation
Accelerated Reinforcements: move friendly reinforcements located in any one space on the Turn Track to the previous Turn space (one turn earlier). Units may not be accelerated to the turn prior (obviously!). If no units qualify, treat as "No Event."
Ammunition Shortages: Shift all friendly Bombardments and Assaults one to the left (1L) this player turn.
Army Morale: Roll one die. If the result is odd, raise the friendly Disintegration Level by that amount; if even, lower the friendly Disintegration level by that amount.
Command Breakdown: Reduce command range of all Commandeers to "0" (their own hex) for this Player Turn.
Contingency Reinforcements: receive friendly contingency reinforcements during the current player turn (see the Scenarios). If none, treat as "No Event".
Delayed Reinforcements: same as "Accelerated Reinforcements," but move reinforcements to the next Turn space (one turn later). If no units qualify, treat as "No Event."
Extreme Weather: Both of the following apply:
- Subtract ONE (-1) from each friendly unit's printed Movement Allowance.
- Shift all Assault attacks one column left this player turn.
Intelligence: The player may do ONE of the following:
- Examine all enemy units in any single hex.
- Restore any one eliminated Screens to the map, placing it on any friendly unit.
No event: Nothing unusual happens.
Poor Visibility:
- Subtract ONE (-1) from the Command Range of all Commanders. (if reduced to 0, a Commander must be in the same hex as a subordinate unit to include it in his Leadership Check.)
- Maximum Bombardment Range and LOS this player turn: 2 hexes.
- Balloon units may not be used this turn.
Scenario Special Event: See battle rules.
Plevna Variant Rules
Plevna Scenario Special Events (Friction Table)
a. Russian Special Event "A" (Russian Stolidity). If the Russian player rolls Special Event "A" then all Russian (but not Rumanian) "T" and "V" class combat units which make a Rally check during this turn's Russian Rally Segment are treated as if they have a Morale Value of "E". This does not apply to Leaders.
b. Ottoman Special Event "A" (Ottoman Fanaticism). If the Ottoman Player rolls Special Event "A" then all Ottoman "T" and "V" class combat units which make a Morale Check during this turn's Ottoman Assault Segment (as a result of an Assault CRT "MC" result) are treated as if they have a Morale Value of "E". This does not apply to Leaders.
c. Russian and Ottoman Special Event "B", Extreme Weather. If either player rolls Special Event "B", treat it the same as "Extreme Weather".
Plevna "What If?" Forces: Ottoman Relief Force
(1) Using this option, the Ottoman player receives the Relief ("Rel") Division units as Contingency Reinforcements. This reinforcement is received if the Ottoman Player rolls the Friction Event "Contingency Reinforcements" or Special Event "B" (in addition to "Extreme Weather"). These units are placed on the West map edge.
(2) If using this option (and only if the reinforcements are actually received), shift the final Victory level one in favor of the Ottomans (e.g., an Ottoman Tactical becomes a Marginal, a Draw a Russian Marginal, etc.).
(3) The Ottoman Supply Convoy ("Convoy") unit is received as part of the relief Division. This is treated as a combat unit, with the following additional rules: (a) it does not count for stacking; (b) it may not attack but defends normally; (c) if it ends any Ottoman Movement Segment in a town hex of Plevna, it is removed from the map and the Ottoman Player immediately reduces his Disintegration Points by "10".
(4) If both the Russian Guard Corps and Ottoman Relief Force options are used, then do not shift the Victory condition levels (the shifts cancel out).