The Sun of Austerlitz

The Sun of Austerlitz Rulebook

Table of Contents

Part 1: The Campaigns of Napoleon 1X Consolidated Rules
Part 2: The Sun of Austerlitz [1805] Exclusive Rules (Revised, Consolidated)
Part 3: The Sun of Austerlitz Exclusive Rules (Original 2003 Booklet)
Part 4: Sequence of Play and Tables
- Expanded Sequence of Play
- Charts and Tables

Part 1: The Campaigns of Napoleon 1X Consolidated Rules

Introduction

[1.] This Consolidated Rulebook applies to the Campaign scenarios of the following games in the 1X series "The Campaigns of Napoleon," and sets forth basic concepts of play. The abbreviation used for each game is in brackets following its name.

1792: La Patrie en Danger [1792]
Bonaparte in Italy—The Quadrilateral [1796], 2nd Edition
Bonaparte in Italy—The Marengo Campaign [1800], 1st Edition
The Sun of Austerlitz [1805]
1807: The Eagles Turn East [1807]
1809: Napoleon's Danube Campaign [1809]
Napoleon at Bay [1814], 3rd Edition
The Emperor Returns [1815]

Whenever special circumstances call for a rule that is not common to every campaign, a rule tailored to that game is broken out under the more general rule and is labeled with the game (in the printed rules, color-coded). Longer rules that apply to individual campaigns are found in each game's "Exclusive" Rulebook. Exclusive Rules supersede any rules they may contradict in these rules. These Consolidated Rules and the accompanying Exclusive Rules can be used in place of the Standard and Exclusive Rules published with the games listed above.

[2.] The rules below are a modified version of the rules found in The Sun of Austerlitz. These rules also contain new text including errata, updates from Napoleon at the Crossroads, and formerly exclusive rules now made applicable to other games.

How The Rules Are Organized

[3.] Most of the rules are numbered according to the step in the Sequence of Play (e.g., "I.a.2") to which they apply (see ¶49). Whenever you have a question during the course of play, refer to the section of the rules corresponding to that step in the Sequence. All rules paragraphs in this folder are numbered sequentially in order of appearance from 1 through 433.

Rules Questions

[4.] Rules questions may be submitted online. Please provide the paragraph number causing the problem. Dick Vohlers will answer questions posted on the ConsimWorld Forum at http://talk.consimworld.com/ (Era: Gunpowder (Napoleonics)). Please do not direct questions to OSG.

General Course of Play

[5.] The game is designed for two or more Players. The game map depicts the theatre of operations; the playing pieces represent the military forces available in the theatre. Those forces comprise France and her Allies versus the Coalition of nations united against her. The order in which the opposing sides interact is spelled-out by the Sequence of Play (see ¶49).

[6.] The Leadership rules (see ¶34) control the make-up of Forces deployed on the game map. Each Force is composed of Combat units, commanded by a Leader. Only Leaders are deployed on the map. A Leader may also command other Leaders in his own or adjacent hexagons (hexes). Leaders are rated according to their Initiative Rating - important in movement and combat - Subordination Rating - their ability to function under the command of another Leader - and Command Span - a limit on the number of combat units and/or Subordinate Leaders they may command.

[7.] Four important concepts in these rules are:

March Attrition, a possible (non-combat) loss of manpower by combat units, the likelihood of which will increase with increased force size and march distance;
March by Command, allowing a Force to be moved automatically;
March by Initiative, allowing a Force to be moved only if the Leader passes a check of his Initiative, determined by the roll of a die;
Combat Losses are taken either in terms of hexes retreated or number of Strength Points lost by combat units depending upon the type of battle (Pitched or Pursuit) revealed by the losing Player.

[8.] Victory Conditions, as listed in the Exclusive Rules for each game in the series, concern the will of a nation to make war. When the Morale of an army has been broken, or public opinion ceases to support the war effort, the game ends.

The Administrative Rules and the Flow of the Game

(Printed beside a diagram of the Administrative Rules hierarchy.) The diagram shows the Administrative Rules as the top of an incompletely articulated hierarchy. In function, they regulate the pace of activities in the game, through their effect on March Attrition and Communications, while only Communications can have a reciprocal effect on the amount of Administrative Points: as the Line of Communications increases in length, the APs Received drop off, and if, the Line of Communications is broken, no new APs can be added.

To continue through the Semantic Network: the Center of Operations is a playing piece moved on the map; there is only one per army. The LOC is traced from the Supply Source to this piece. It is the center of Administration on the map, and its function is to convert the stock of APs, when needed, to Movement Commands. However, the more the AP stock is depleted, the greater will be the March Attrition suffered by the army. March Attrition is simply a non-combat loss of Combat Strength by the units on the Organization Display; it will serve to limit the length of marches.

Movement Commands are used to induce Movement. Each force a Player wishes to move must either receive a Movement Command (to do this the Leader of that force must be within Dispatch Distance of the Center of Operations) or attempt to move under his own Initiative, which is resolved by a die roll. A Player may expend an additional Movement Command for a Force, enabling it to make an Extended March of up to 4 Movement Points, while Forced March occurs in a separate Forced March Phase during the Enemy Player Turn, only under Initiative.

The Leadership rules govern everything having to do with the constitution of a Force on the map. Each such Force is commanded by one Leader, who may have subordinate Leaders in his force, depending upon his Command Span and how much of that number is taken up by the other Leaders' Subordination Ratings. By this means, the Size of the Force is limited (an upper Stacking Limit is also imposed) and the size, so determined, has an effect on how much Attrition the force will suffer. The Movement rules explain how a force expends Movement Points from its Movement Allowance; these expenditures vary with the Terrain Type, each of which has its own MP cost. The ultimate Distance of March (the number of MPs expended in one Phase) will help determine how much March Attrition that force suffers.

The Zone of Control is simply the area of eight hexes surrounding a force (within certain limits of terrain). When a force enters the ZOC of an Enemy Force, Combat will ensue unless that Enemy Force is able to Force March out of the area, a question determined by an Initiative die roll (which is modified by comparison of opposing Leaders' Initiative Ratings).

Before Combat Resolution, Artillery may fire; this is a die roll modified by cavalry differential. The Combat procedure involves a die roll on the Combat Results Table (the column to use on this table is determined by Terrain Conditions). This die roll will specify a number of Casualties for one side and a Retreat for the other side (unless it is a Pitched Battle, in which case the Combat die roll procedure is repeated by each side in alternation). The Player owning the defeated force Retreats that force along a path determined by a set of Retreat Priorities. The victorious player may then make Pursuit along the Path of Retreat. The extent of Pursuit is determined by a comparison of Leader Initiative and a die roll, and determines the Casualties of the retreating side.

If certain Leaders are captured, a Battle is lost, and there is an adjustment in Morale of one space, either positive for the winner Player or negative for the losing Player, at the winner Player's option. Morale and Weather alike have an effect on attrition.

That, in outline, is pretty much the whole game.

GAME SCALE

[9.] Each hexagon represents an area 3.2 kilometers (2 miles) across. Each Strength Point represents one thousand men or 16 field artillery pieces. Game-Turn length is two days.

GAME EQUIPMENT

THE GAME MAP

[10.] The Game Map depicts the territory in which campaigning occurred as well as territory containing alternate strategic objectives of the campaign. The terrain has been conformed to a hexagonal grid. Each hexagonal cell, or “hex,” represents a discrete location which may be entered by a Force through the expenditure of Movement Points. Different terrain features require a different Movement Point cost to enter. Each hex has a four-digit identification number. In games with more than one map, each map section will have an ID code letter, and these code letters will precede the hex numbers in designating hexes.

Terrain Type of Divided Hexes

[11.] Use the prevalent terrain type in a hex. If uncertain, use the type with the highest MP cost. Ignore hill, woods, and mountain terrain which fills less than one-third of the hex.

1805: Example: 1133, 1134, 1533, 2332, 2634, 3035 are not hills; 2021, 2222 and 2323 are hills.

Dice

[12.] The game requires two six-sided dice.

THE PLAYING PIECES

[13.] The Playing Pieces will be referred to as “counters” or “markers.” There are three types: Combat Unit counters; Leader counters; and Informational markers. Combat Units remain throughout the game on the Organization Display of the appropriate nationality. The Leader they are assigned to, and the strength of the units, are shown by the spaces they occupy on the Display. They remain on this display as long as they have at least one Strength Point. If at any time they drop to zero they are immediately removed from the game. Until such time, however, they may be shuffled from one Leader’s track to another during the Friendly Command Phase provided the two Leaders occupy the same hex on the game map. Leaders may either be on the game map or the Organization Display depending on whether they are subordinate to another Leader or acting as a Force Leader. The use of the various informational markers will be explained when encountered later in this, or in the Exclusive Rulebook.

Combat Units

[14.] The combat units represent Divisions and Brigades, ranging in strength from 1,000 to 9,000 men. The combat unit counters (with the exception of Vedettes and, in most games, Garrisons) go on the Organization Displays. In some games, units with a maximum strength greater than the maximum number on the Organization Displays have “+x” on their back side, where x is the maximum track value. If “+x” is facing up it means that the maximum track value must be added to the track space on the Organization Display which the counter occupies.

[15.] The abbreviated name of the officer commanding the particular unit is given for historical reference, as is its unit type (infantry, cavalry or artillery), its unit i.d. and its size (regiment, brigade, or division).

[16.] Printed on each counter is its Maximum Strength (the actual strength of the unit will vary due to losses or the incorporation of replacements). During play the current strength of a combat unit will be indicated by the space it occupies on the Organization Display; (if in the “3” space the unit has three Strength Points). When a unit takes losses or receives replacements the counter is moved left or right on the track to reflect this new value. No unit may exceed its Maximum Strength. Once a combat Unit is eliminated, or has zero SPs, it may never be reformed. You can never bring eliminated Combat Units back with Replacements.

[17.] The unit’s Maximum Movement Allowance will also be found on the counter. Cavalry has a Movement Allowance greater than infantry but pays a greater Movement Point Cost for certain types of Terrain. Artillery uses a special Fire Table for combat, and has some restrictions on its movement.

[18.] Subordination Value is the amount of a Leader’s Command Span required to command the unit or Leader.

Leaders

[19.] Leader counters display the name of the Leader, his Initiative Rating, a Bonus Point (if any, indicated by a star), the Leader’s Subordination Value, and Command Span. (The Subordination Ratings are in brackets to distinguish leaders from combat units.) The other side of the counter will display the national insignia. When on the game map this is the only side of the Leader which may be viewed by the opposing Player except in Combat and Repulse (see ¶31).

Replacement Markers

[20.] Replacement Markers are used to record the levels of manpower residing in the replacement pool. If there is no marker provided for recording a particular type of replacement points they must be used in the turn they come available or else forfeited (see ¶109).

Major Generals

[21.] Major Generals are leader counters used to show detached combat units operating independently on the game map. Infantry Major Generals have ratings of 1 [2] 1.5 and cavalry Major Generals are rated 4 [1] 1 (Initiative / Subordination / Command Span). These generic Major Generals are identified by number and type (infantry and cavalry). Major Generals may only be activated or voluntarily de-activated during the Friendly Command Phase. The number of Major Generals that may be activated is limited only by the number provided.

Garrisons

[22.] Garrisons function as any other force, except that they have no Organization Track and a subordination cost of zero. Each Garrison has an intrinsic strength of 1 Strength Point (see ¶77 and ¶312) and a normal ZOC. (See also ¶130.)

Vedettes

Each Cavalry Vedette Counter represents a cavalry regiment divided into five or ten 50-man patrols fanned-out to create a presence over a wide area, collecting information, scouting, and screening-off enemy patrols.

[24.] Each side is provided with a number of Vedette Counters used to deceive the enemy player and obtain information about enemy forces. At the start of any scenario, up to two Vedettes may be placed on the map with each actual Force leader appearing on the map. Any remaining Vedettes are placed into a “Vedette Pool” for possible later arrival (see ¶158). You may not place more Vedettes than provided in the counter mix.

Player’s Note

[25.] Vedettes are intended to gather information, prevent your enemy from gathering information, and to bluff. Disregarded when real forces fight, they have no influence on battle outcomes (except when fighting other Vedettes).

[26.] Not used.

GAME CHARTS, TABLES, & DISPLAYS

[27.] Each game has Organization Displays, and Unit and Leader set-up Manifests for the armies. There is a Turn Record Track and other charts and tables printed on separate sheets for ready access by the Players.

Unit And Leader Manifests

[28.] All Set-Up Information is presented on the Leader and Unit Manifests. The Unit Manifests specify, for each unit, the Leader’s track on which to set-up and its strength. The Leader Manifest specifies the Leader’s hex on the map or the Force Leader (see ¶418).

Organization Displays

[29.] Each army has its own Organization Display. Beneath the Leader’s Initiative Rating, Command Span, and Subordination Value is his Subordinate Units Track where combat units which belong to the Leader’s Force are placed during play. The combat units are placed in the spaces corresponding to their current strength.

INTELLIGENCE

LEADER IDENTITY & FORCE STRENGTH

[30.] Information on the Organization Displays should be concealed from the other player. All Combat Units and Subordinate Leaders on a Leader’s track are considered to occupy the same hex as the Leader.

[31.] Force Leaders and Unemployed Leaders moving across the map remain with their informational side down, hidden from the opposing Player. Leaders are only revealed at two points during a turn: following a successful Repulse attempt (see ¶241) and during in Steps 1 and 2 of Combat (see ¶300). At such times, place all Subordinate Leaders of both sides on the map.

Exceptions: Vedettes (see ¶239 & ¶250).

[32.] Opposing Leaders must remain face-up as long as they remain adjacent.

PROCEDURAL SECURITY

[33.] The information on the Organization Display should remain confidential once Players feel comfortable with the game mechanics. If it is amenable to all Players, the following should also be kept confidential:

Die rolls for Initiative during Movement and Forced March.
The results of Attrition.
The addition of Replacements to Combat Units and their accumulation.
The identity of Subordinate Leaders when the Force is in the ZOC of an opposing Force.

LEADERSHIP

GENERAL RULE:

[34.] Before any movement can take place in the Movement Phase or the Forced March Segment, the troops to be moved must be constituted into “Forces.” Leaders make this possible. Forces on the map are represented by their leaders only.

COMMAND SPAN

[35.] A Leader may command a number of Combat units whose combined Subordination Ratings are equal to or less than his Command Span. Certain Combat units absorb more of a Leader’s Command Span than others. In general, the Subordination Value of a cavalry brigade or division will absorb one-half point of the Command Span; a cavalry corps or an infantry division will absorb one full point of a Leader’s Command Span.

Example: A Leader with a Command Span of 3 could possibly command six brigades of cavalry, or three infantry divisions, or a combined Force of two cavalry brigades and two infantry divisions, or any combination of Combat Unit counters which together have Subordination Values not exceeding the Leader’s Command Span, 3.

CAVALRY MAJOR GENERALS in Command of Infantry or Artillery

[36.] If a Cavalry Major General has an Infantry or Artillery Unit on its track on the Organization Display, reduce his Initiative Rating to “one” and increase his Subordination Rating to “two.” This change lasts as long as the Major General commands Infantry or Artillery Units.

FORCE LEADERS

[37.] Leaders may command other Leaders. A Leader who commands other Leaders is called a Force Leader. Leaders that are under the command of another Leader are called Subordinate Leaders and are placed on the Force Leader’s portrait unless part of a Multi-Hex Force. There may only be one Force Leader per Force.

[38.] A Leader may command a number of Leaders whose combined Subordination Values do not exceed the Force Leader’s Command Span.

Example: A Force Leader with a Command Span of “6” could command three Subordinate Leaders with Subordination Values of “2” each. Subordinate Leaders must be in the hex with the Force Leader, or in the Zone of Control of the Force Leader (in the case of a Multi-Hex Force).

COMMANDING COMBAT UNITS & SUBORDINATE LEADERS

[39.] A Force Leader may command a combination of Combat Units and Subordinate Leaders. A Force Leader may command any number of Combat Units and Subordinate Leaders as long as their totaled Subordination Values do not exceed the Force Leader’s Command Span. A subordinate leader cannot have his own subordinate leader.

Example: A Force Leader with a Command Span of “6” could command two cavalry brigades, and two infantry divisions (on his track), and a Subordinate Leader with a Subordination Value of “3” (in the same or an adjacent hex).

UNEMPLOYED LEADERS

[40.] A Leader, other than a Major General, without any Subordinate Leaders or Combat units at the beginning of the Friendly Movement Phase, is an Unemployed Leader. An Unemployed Leader may automatically move, regardless of Initiative or Movement Commands, up to 9 Movement Points during each Friendly Movement Phase and Forced March Segment. He pays Terrain costs as if he were a Cavalry Force. (Exception: No extra cost for bridges.) Unemployed Leaders ignore enemy Zones of Control (“ZOCs” - see ¶232) and do not exert a ZOC. When moving an Unemployed Leader the Phasing Player must inform the non-Phasing Player that the counter he is moving is an Unemployed Leader. Unemployed leaders cannot cut Lines of Communication.

[41.] An Unemployed Leader may not take command of a Force until the next Command Phase. Unemployed Leaders may move, displace, and retreat as part of a Force they are stacked with. The Subordination Rating of Unemployed Leaders is ignored. An Unemployed Major General is removed from the map the moment he becomes unemployed.

ELIMINATION OF LEADERS

[42.] A Leader may be captured when all SPs in the Leader’s Force are removed as a result of Combat or Pursuit, or an enemy force which includes cavalry repulses an unemployed leader. The capture of all leaders is determined by a die roll against their initiative to see if they escape. The repulsing or capturing Force need not reveal its Strength.

[43.] In order to avoid capture, the owning Player must roll a die no higher than the Leader’s unmodified Initiative Rating. If the Leader avoids capture he is Repulsed instead (see ¶241). Captured Leaders are removed from the game. If there are no replacement leaders in a scenario, return an eliminated leader’s counter to play after one complete turn out of play, subtracting “one” from his Command and Initiative Ratings from that point forward. Unnamed Major Generals are automatically deactivated and returned to their track for later use by the owning Player.

LEADERSHIP BONUS POINTS

[44.] A Leadership Bonus is shown by a 5-pointed star on the Leader counter. The number of stars indicates the value of the Leadership Bonus.

Effect of a Bonus Point on Attrition

[45.] The force Leader’s Leadership Bonus (if any) is subtracted from the Attrition die roll (see ¶267).

Effect of a Bonus Point on Combat

[46.] The Attacking Player may add, subtract, or ignore his Leadership Bonus when rolling the die on the CRT if the Leader in question is the Force Leader of the attacking Force (see ¶365), and from the Artillery Fire die roll (see Artillery Fire Table).

PREPARE FOR PLAY

[47.] Set up units on the Organization Displays according to the Scenario Information (see also ¶422). The location of counters on the Organization Display is confidential and for the owning Player only; position the displays in the playing area with this in mind. Place the Combat Unit counters in the space on the Organization Display specified for them in the Scenario Information. Place subordinate Leaders and markers (e.g., bridge trains) on the portrait of their Force Leader. Leaders with a map location code are now placed in the corresponding hex.

[48.] Not used.

SEQUENCE OF PLAY

THE GAME TURN OUTLINE

[49.] The game is played in sequenced turns called Game-Turns. Each Game-Turn is composed of two Player-Turns. The “Phasing Player” is the Player whose Player-Turn is in progress. The Game-Turn Marker should begin the game on the Turn Record Track in the first space of the game or scenario to be played. A Game-Turn does not end until both Players have completed a Player-Turn as outlined by the sequence below. As a Game-Turn ends, advance the Game-Turn marker to the next space in the Game-Turn Track. This process continues until the last Game-Turn ends, or until one Player achieves a Victory Condition that ends the game sooner.

[50.] All activities must take place in the order outlined below. For instance, the Second Player may not make an attack during the First Player’s Movement Phase. Keep the Sequence of Play Sheet handy as you proceed through the Game-Turn.

A. Weather Determination Phase

[51.] The effect of weather upon Movement, Combat and Attrition will vary from game to game in this series. It is the first thing determined in each Game-Turn and it is always determined by a die rolled by the First Player (see ¶70).

B. The First Player-Turn

[52.] The First Player will be designated in the Scenario Information in the Exclusive Rules. Each Player-Turn is comprised of four Phases. The Enemy Player’s activities during the Friendly Player-Turn are restricted to Forced March (III.a), artillery fire (III.b.5), and counterattacking during a Pitched Battle (III.b.12).

I. Command Phase

a. Administrative Segment [53.]

Receive Administrative Points and adjust the AP markers on the Accumulated AP Track (see ¶96).
Designate a friendly Supply Source. If it is now changed from last turn, deduct one AP (see ¶103).
Disband the Friendly Center of Operations (if desired). Deduct one AP for this (see ¶105).
Add new Replacement Strength Points to the Replacement Pool (see ¶108).

b. Organization Segment [54.]

Transfer Strength Points from the Replacement Pool to units in the field that are eligible to receive Replacement Points (see ¶114).
Activate or deactivate Major Generals and March Regiments (see ¶115 and ¶119).
Transfer combat units between Leaders which occupy the same hex on the map (see ¶129).
Transfer Strength Points from one Combat Unit to another if both Combat Units occupy the same hex and are of the same Nationality and unit type (infantry points to infantry units, etc.) (see ¶133). Any unit whose strength is reduced to zero in this process is permanently removed from the game.

II. Movement Phase (see ¶147)

a. Reinforcements [56.]

All reinforcements available to the Player this turn are placed on their indicated entry hex.

Activate the Reinforcement Force by “free” Movement Command: They are considered to have an automatic Movement Command for this turn only, that will not deplete the Movement Commands available to the Phasing Player in segment “b” below (see ¶154).
Move the Force. The reinforcements are now moved, one at a time (see ¶204).
Check for attrition (see ¶262).

b. Movement Commands [57.]

The First Player may move any of his eligible Forces by indicating that they have received a Movement Command. No Force that entered as a Reinforcement this turn may be moved again in this Segment (see ¶166). There are a limited number of Movement Commands available to the Phasing Player.

Activate the Force by expending one Movement Command.
Move the Force.
Check for attrition.

c. Initiative Movement [58.]

Any Force that did not enter as a Reinforcement this turn, or execute movement through a Movement Command, may now attempt to move by means of the Force Leader’s Initiative. Each Force may only attempt to move by means of Initiative once in this phase.

Roll one die (modified by Weather and/or adjacent Enemy Forces). If the result is less than or equal to the Leader’s Initiative, activate the Force. (The Force may expend 1 MP on certain results greater than the Leader’s Initiative - see ¶192, “Activation by Initiative.”)
If activated, move the Force.
Check for attrition.

d. Stationary Attrition [59.]

Forces that did not move in either a, b, or c above now check for attrition.

e. Consolidation Segment [60.]

The Phasing Player now consolidates any hexes that have two or more Leaders on the map, so that only one Leader counter occupies each hex (see ¶294). Subordinate Leaders in the same hex as their Force Leader are moved to the Force Leader’s track on the Organization Display. If the Forces in the hex cannot be Consolidated in this manner then part of the resulting Insubordinate Stack should already have been Displaced (see “The Force,” ¶137). Any Unemployed Leader’s subordination rating can be disregarded (see ¶41). Any Center of Operations on its moving side that did not move this Player Turn and that has a valid LOC may be flipped to its active side.

f. Bridge Segment [61.]

The Phasing Player may repair and damage bridges, and deploy and undeploy pontoons (see ¶251). The intention to build or damage bridges must be announced during movement. Construction is considered to be finished by the time of the bridge segment. (Since the MPs expended merely represent the time the troops have to spend waiting for the bridge to be completed, and not distance covered, they do not count toward attrition).

III. Combat Phase

a. Forced March Segment [64.]

The Second Player may now attempt to move any or all of his Forces through the Initiative March procedure described in IIc. above (see ¶297). Only Forces that actually move in this Segment suffer Attrition which is determined the moment the Force ends its movement.

b. Battle Resolution [65.]

The First Player is now obligated to attack all Forces of the Second Player that are adjacent to his Forces (exception: terrain such as Primary River hexsides—see ¶234 and ¶235).

The First Player designates his attacking Force (see ¶302).
The First Player designates which hex or hexes are to be attacked (see ¶313).
Both Players select a Battle Type marker. (See ¶327).
Determine the Cavalry differential (see ¶340).
The First Player resolves artillery fire (see ¶347). The Second Player resolves artillery fire.
Determine Combat odds and locate the appropriate column on the Combat Results Table (see ¶350).
The First Player rolls the die, taking into account any modifiers, and locates the result (see ¶362). The victor loses Strength Points equal to his resulting number on the CRT (see ¶367).
If the Pursuit marker was chosen by the losing side this Force must now retreat the resulting number of hexes (see ¶369); otherwise go to Step 11.
If there was a retreat in Step 8, the victor may now pursue the retreating Force causing one SP loss for each hex of Pursuit (see ¶380).
Adjust the Morale Marker now for any conditions that were achieved in the preceding battle situation (see ¶395).
If the losing side chose the Pitched marker, remove combat losses equal to the number result on the CRT (see ¶399). Combat then proceeds to the next step (exception: see Override, ¶400).
The Second Player designates his counter-attacking Force.
The Second Player designates the hexes to be attacked.

NOTE: If there are any other battles within 8 hexes, the first round of each battle must be resolved before any battle proceeds to round two.

c. Joint Consolidation [66.]

Both Players now consolidate all Multi-Force hexes according to II.e, above.

IV. Morale Phase

[67.] (see ¶411)

a. Check to see if any besieged Citadel surrenders.

b. Adjust Morale for the Capture of Political Features still in the possession of the capturing player at this point.

c. Determine if the game ends in a Strategic Victory.

C. Second Player-Turn

[68.] Phases I through IV are repeated in the same sequence as above, substituting the Second Player for the First Player and vice-versa. When this has been accomplished the Game-Turn ends. Move the Game-Turn marker to the next space on the track and begin the next Game-Turn.

[69.] Not used.

SEQUENCE OF PLAY DETAILS

Each of the remaining rules sections follows the order and numbering presented in the Sequence of Play above. They are labeled with the phase in the Sequence of Play (e.g., “A.” for the Weather Determination Phase) to which they apply (see ¶51). Whenever you have a question during the course of play, refer to the section of the rules corresponding to that phase in the Sequence.

A. WEATHER DETERMINATION PHASE

[70.] There are different types of weather, one of which must be in effect during each Game-Turn. At the beginning of each scenario, and at the beginning of each subsequent Game-Turn, the First Player must roll the die and consult the Weather Table to determine the weather for the coming turn, noting die roll modifiers as appropriate. Alternatively, Players may mutually agree to use the Historical Weather if listed on the Turn Record/ Reinforcement Track. Place the Weather Marker in the appropriate space on the Weather Track. If the result includes more than one type of weather (such as Rain/Mud), the effects of both types apply and are cumulative. If the prior turn was Mud and Rain follows, the effects of both Rain and Mud apply (and are cumulative).

[71.] Weather Types by Game. 1805: There are five types of weather: Frost, Snow, Mud, Rain, and Fair. Fog effect may apply during Snow, Mud, or Rain (see the 1805 Weather Table).

I. COMMAND PHASE

I.a. ADMINISTRATION

[72.] In order not to be considered out of supply for attrition purposes, a Force must be able to trace a line, called a Dispatch Distance (see ¶86), from a friendly depot (see ¶91) or from the Center of Operations (see ¶92) of its army. In turn, the depot must be able to trace a Line of Communications (see ¶80) from any possible friendly Supply Source, while the Center of Operations must be able to trace an LOC from the Active Supply Source (see ¶76). In order to obtain Movement Commands, a Force must also be able to trace a Dispatch Distance, though in this case the Dispatch Distance may be traced only from the Center of Operations, which again must have an LOC to the Active Supply Source.

[73.] In order to obtain Movement Commands in the campaign game, each Army draws from its pool of Administrative Points (APs). APs are expended to create Movement Commands, which the Player must provide for each force if he wants to be certain it will move. A Movement Command costs one AP. As many Movement Commands can be created per turn as there are APs available (provided that the Center of Operations is active), but each force may only move once per turn. In order to receive a Movement Command, Individual Forces must trace a Dispatch Distance from the Center of Operations that has a valid Line of Communication from the active Supply Source. This Dispatch Distance may traverse any passable terrain. Dispatch Distances for each game are listed on the 1X Series Communications Table and may vary by army within a game.

[74.] The number of Administrative Points remaining on the AP Track at the time of Movement determines the severity of March Attrition for Forces not Foraging. When determining attrition, the Player finds the strength of the Force on the column headed by the AP Level showing on the AP Track at the instant of the Force’s movement. The fewer Administrative Points accumulated, the greater will be the attrition.

Note: Forces in Forage Mode may use an alternative attrition calculation method based upon the Forage Value of the surrounding terrain (see ¶274).

SUPPLY SOURCES

[75.] The 1X Series Communications Table shows all possible Supply Sources for each Army. A hex may be a Supply Source only if controlled by the designated player. If Friendly forces capture an enemy Supply Source the enemy player may continue to use any remaining Supply Source.

1805: If Austro-Russian forces capture the French Supply Source nearest Vienna, the remaining Supply Source leading to Krems (1154) can still function, though on a less advantageous column. (See the 1805 AP Pool).

The Supply Source Marker

[76.] There are generally several possible Supply Source hexes for each army. The Supply Source marker designates which Supply Source is active at any given time for an army. This Supply Source marker may be shifted from one Supply Source to another during the Administrative Segment (I.a) of the Command Phase. The (1) on the marker indicates the active Supply Source’s garrison strength of one (see next).

Supply Source Garrison

[77.] All active Supply Sources are considered to have a Garrison of one (1) SP. These Garrisons cannot be Repulsed. They may never be part of an attacking Force. They may only defend. The Supply Source Garrison negates enemy ZOCs in the supply source hex for all purposes. Garrison units have normal ZOCs. Reactivation of a Supply Source automatically reinstates this Garrison.

1805: The French Supply Source’s 5 includes strength from the large Vienna garrison stationed directly across the Danube. If the Supply Source is changed, its strength is only 1.

Capture of Supply Sources

[78.] If the active Supply Source is attacked and the garrison is eliminated or is forced to retreat, the Supply Source is considered captured. When an active Supply Source is captured, the Active Supply Source Marker is removed from play. While the Supply Source marker is out of play, its army suffers the Interim Effects under ¶105. A Supply Source cannot be permanently eliminated.

[79.] A Supply Source Marker may be returned to play at any possible Supply Source or depot for that Army free of enemy units (or ZOCs) during any following Admin Segment. Supply Source (and depot) hexes cannot be permanently destroyed. A captured Supply Source may be reactivated the turn following the removal of enemy forces. This is considered a change of Supply Source, and hence costs 1 AP.

LINES OF COMMUNICATION

[80.] A Line of Communication (LOC) is a line of connected, primary road hexes free of enemy units (even if besieged) or their Zones of Control to a Supply Source. For a depot, the player traces this line from any of his possible Supply Sources. For his Center of Operations, the player must trace this line from his currently active Supply Source. If the LOC exceeds the maximum effective length for the game in question, the depot or Center of Operations is considered “Inactive.”

[81.] The maximum effective length (see ¶89) for an LOC applies to both sides in a game (but varies by game) and is set out in the 1X Series Communications Table (for 1805: 40 Primary Road hexes).

Tracing the LOC through EZOCs and Bridges

[82.] An LOC may include Friendly-occupied enemy ZOCs. Bridges add no additional costs and connected Primary road hexes count as one each. An LOC may not be traced across a pontoon.

“No LOC” Effect

[83.] A Force beyond, or cut off from, a Line of Communication may not receive Replacements during the Command Phase or Movement Commands during the Movement Phase and must Forage or use the “zero” or “No LOC” column on the Attrition Table (see also “In Supply,” ¶263).

Multiple Friendly Centers of Operations

[84.] If there is more than one Center of Operations under one player’s control, it must trace from its own specifically labeled Supply Source or Sources. (Exception: see “Tracing through Friendly Army's Center of Operations” ¶94.)

Vedettes and Lines of Communications

[85.] Vedettes may not interfere with a Line of Communication or Dispatch Distance (even if they occupy a depot or Supply Source). Such may be traced into or next to a hex suspected of being occupied solely by Vedettes. After the Line is defined, the opposing player need only state whether the Line is blocked. (This is his option: he may elect not to cut the line even if the unit is not a Vedette.) If the line is blocked, a new Line for that unit can’t be defined until the next Supply check.

DISPATCH DISTANCE

A dispatch can travel as fast as a horse and rider; allowing for wrong turns, about 18 hexes in 6 hours. At that distance it would take 24 hours to write and deliver the order, act upon it, write and deliver the report of the outcome. Beyond that, the orders are already out of date before they can be acted upon.

[86.] Dispatch Distance is a line of hexes traced from a Center of Operations with an LOC or active depot with an LOC to a Force. Dispatch Distance is necessary for: 1) Issuing Movement Commands or receiving Replacements through the army’s Center of Operations (in which cases the Center of Operations must be active); and 2) Determining March Attrition through a depot or Center of Operations. The Dispatch Distance is traced through any passable terrain at cavalry movement costs. The path may not be traced through enemy units or their ZOCs (unless the ZOCs are friendly-occupied) or across non-road hexsides into Mountain hexes. In calculating the Dispatch Distance, primary roads are counted as secondary roads (1 MP), with no extra costs for bridges. The Dispatch Distance in MPs varies by game (and sometimes by army) and is set out in the 1X Series Communications Table. 1805: 18 MPs for both armies.

Vedettes Out of Dispatch Distance

[87.] Vedettes that cannot trace a Dispatch Distance from a Center of Operations, Supply Source or active friendly depot during the Administration Phase of the Player-Turn are immediately removed to the Vedette Pool until the Organization Segment of the next Friendly Player-Turn. They return to play as described in ¶368.

[88.] Not used.

DEPOTS

Depots are the middle links in the supply chain – called ‘magazines’ in Napoleon’s time - where resources were collected from friend and foe alike.

[89.] A depot allows you to reduce your effective LOC. For each depot in the LOC (through which the LOC is traced) you can subtract 5 Primary Road hexes from the overall LOC length when determining availability of APs for that turn or distance from a possible Supply Source for attrition. The depot can be anywhere along the LOC.

1805: Example: With the French Supply Source in Vienna and Center of Operations in Brünn, the actual distance via Stockerau, Znaim, and Pohrlitz is 50 hexes; the effective distance traced via those depots would be 25 hexes (reduced by 5 for each depot, including Floridsdorf and Brünn).

[90.] In addition to printed depot hexes, consider any of the following terrain types to be a depot: any possible Supply Source (Active or not) and any Center, City, Primary Town, or Fortification (see ¶216) that has an LOC (see ¶80) to any possible Supply Source.

Depot Functionality

[91.] Depots cannot issue Movement Commands. However, Forces may trace Dispatch Distance from a depot that has a valid LOC to any possible Supply Source for Attrition purposes. (Exception: A besieged Citadel may not be used as a Supply Source.) All depots are functional at all times and may be used by either player as long as they have a friendly LOC and are not occupied by enemy forces. Depots do not require garrisons.

FUNCTIONS OF CENTERS OF OPERATIONS

[92.] An Army’s Center of Operations must be active in order to issue Movement Commands (or replacements), to receive new Administrative Points, or to act as a source for Attrition supply. A Center of Operations is rendered inactive if (1) it moved during the previous friendly Player-Turn (see ¶177), (2) it has no Line of Communications (see ¶80) to the Active Supply Source, or (3) it has been disbanded (see ¶106). The Center of Operations should be flipped over when inactive. It may reactivate immediately when all conditions necessary for activation are met.

[93.] In games with separate Coalition armies, there are separate Centers of Operations for each army, each of which accumulates APs separately and issues Movement Commands to leaders of the appropriate army.

[94.] Tracing through Friendly Army's Center of Operations A Coalition army may change its Communications to go through the other Coalition Center of Ops. The distance on the Admin Point Pool in this case equals the distance from the other army’s Supply Source to its Center of Operation, plus the distance between the two Coalition Centers of Operations. Note: Even though this distance is traced from the other army’s Supply Source, those points are in no way associated with the Admin System of the other army. They are neither deducted from nor determined on the column of the other army.

I.a.1 HOW ADMINISTRATIVE POINTS ARE RECEIVED

The player must see to the provisioning of his army before it can effectively be used. The Player who fails to make the most conservative use of resources will be unlikely to win the Game. Resources such as wagons and the necessary management of their contents are represented in the game by Administrative Points. APs are an abstract measure of the current materiel condition of the troops in an army.

[95.] Administrative Points are used to create Movement Commands, which the Player must expend for each force if he wants to be certain it will move. The Level of Accumulated Administrative Points determines the severity of March Attrition for Forces not Foraging.

How to Receive Administrative Points

[96.] New Administrative Points are accumulated during the Administrative Segment of the Player-Turn. The Player refers to the Administrative Point Pool and rolls two dice to determine the quantity of APs he receives. Apply any game-specific modifiers to that roll as listed under AP Pool for each game. Cross-reference the effective LOC distance (see ¶81) to the army’s Center of Operations from its Supply Source with the modified dice roll. The number obtained from the cross-reference is the quantity of Administrative Points added to the accumulated total. If the Player’s Army has an inactive Center of Operations it receives no new Administrative Points.

1805: First Turn: The French Player receives no new APs on 15-16 November (see also ¶117).

Army Commander AP Bonus

[99.] If the Army Commander, or other leader designated as the army commander-in-chief, currently resides with his Army’s Center of Operations, add one AP to the total received. (See ¶113 for a list of Army Commanders for each game.)

How to Use the Administrative Point Tracks

[100.] For each Army, use the two markers provided to indicate “Ones” and “Tens” of accumulated Administrative Points. Adjust these markers on the track to record the level as it ebbs and flows.

Example: To show “Thirteen” Administrative Points, place the Tens marker in the Number 1 space, and the Ones marker in the Number 3 space.

I.a.2. CHANGING THE SUPPLY SOURCE

[101.] The Supply Source may be changed to another friendly controlled Supply Source or depot hex.

PROCEDURE:

[102.] Flip the Supply Source Marker over (to signify that the change is underway). During the next Administrative Segment, the Supply Source Marker may be returned face-up at the other depot or Supply Source.

[103.] The cost to change the Supply Source is one (1) AP. This takes one complete turn to effect. During that turn the Supply Source marker is flipped over to its “Inactive” side. While the Supply Source marker is flipped over, the Center of Operations is “Inactive” (see ¶92); furthermore, the Center of Operations may not be used when determining attrition (see ¶264).

Interim Effects

[105.] During the turn the Supply Source Marker is flipped over, the Army may issue no Movement Commands and must use the “zero/No LOC” column on the March Attrition Table.

I.a.3 DISBANDING CENTER OF OPERATIONS

[106.] The Center of Operations may be disbanded only during Step 3 of the Administrative Segment. To voluntarily disband the Center of Operations, expend one AP, remove it from the map, and place it on the Turn Record Track three Game-Turns ahead of the current turn. The Center of Operations will appear as a reinforcement unit during that turn’s Movement Phase at the Army’s Supply Source or any Depot between the Center of Operations former location and the Supply Source on the current LOC. While disbanded, the Center of Operations is considered “inactive” (see ¶92).

[107.] Commentary: The equipment necessary to generate a new Center of Operations always exists at the Supply Source. The disbanded Center of Operations is considered broken-up and its equipment either captured or distributed along the new LOC; its staff is too mobile and dispersed to be captured.

I.a.4 REPLACEMENTS

[108.] Replacements of fresh and recovered troops become available for addition to the Replacement Track according to the appropriate Replacement Line on the Turn Record Track. (In some games there may be a Replacement Table with varied amounts determined by a die roll.) Replacements from the pool may only be added to units of the specified nationality and type that are within Dispatch Distance of its Center of Operations and that Center of Operations is active. They accumulate at the Supply Source. An army with an inactive Center of Operations may not add Replacements from the Replacement Pool to its units. Units which receive replacements are immobile and may not move during the ensuing Movement Phase and Forced March Segment.

[109.] The following abbreviations may apply: i/nfantry, c/avalry, a/rtillery, r/emounts, K/ossacks (or Kos/sacks), IG = Guard, OG= Old Guard Infantry, GC = Guard cavalry. Apply replacement points for cavalry to either regular or light cavalry; special Replacements such as Guard Infantry or cavalry may be given to line (i.e., regular) units, but line replacements may not be given to Guard. Line units that receive Guard Replacement SPs remain line units and the elite status of the replacement SPs are lost. 1805: Russian replacement points can only be added to Russian units. Austrian (A) replacement points can only be added to Austrian units. German (G) points can only be added to the Bavarian unit.

Accumulated Replacement Points

[110.] Accumulated Replacement Points are recorded on the Accumulated Replacement Point Track. Each Army has an Informational marker to record Replacement Points of Infantry, Cavalry, and others if applicable. This marker will reflect the accumulated points and should be adjusted as points are added or removed from the pool. These Replacement Points may be added to Combat Units in the field during a later Friendly Organization Segment.

[111.] During a Friendly Organization Segment, accumulated Replacements may be added directly to any units with a valid LOC. Alternatively, a Replacement Leader or Major General may be created at the Supply Source to take command of any Replacement Points accumulated there, using a March Regiment to indicate these points on the Major General’s track.

[112.] Leaders which do not begin the game on the map may be brought on later as replacements (if marked ‘repl.’) or as reinforcements (see ¶154) as specified on the Turn Record Track or the Leader Manifest.

Army Commanders

[113.] Napoleon is the French Army Commander in all games.

1805: The Austro-Russian Army Commander is Tsar Alexander.

I.b. THE ORGANIZATION DISPLAY

I.b.1. ADDING REPLACEMENTS

[114.] Replacements may be added to the strength of Combat Units during the Organization Segment. A unit that receives replacements may not move during its next Movement Phase and Forced March Segment. Place “Immobile” Markers on units as they receive replacements. (Remove these at the beginning of the next friendly Organization Segment.) A Force may not receive Replacements if in the ZOC of an enemy Force, or if lacking a valid Dispatch Distance. Replacements may be added only to units not at their Maximum Strength. Eliminated Combat Units may not be rebuilt with Replacements; i.e., their “cadre” is considered destroyed.

March Regiments

[115.] A March Regiment may be created at the active Supply Source under the command of a Major General, out of Replacement Points which are deducted from the Replacement Point Track. Several counters are provided of necessary types, and additional counters cannot be created. These are placed on the Major General’s Track on the Organization Display. These March Regiments are considered Reinforcements for Movement Command purposes on their turn of activation. They are normal combat units. March Regiments may also enter at any Friendly Supply Source or Depot-with-LOC, with replacement strength like a reinforcement (see ¶155).

[116.] March Regiments may also be created by deducting strength from units on the Organization Display. In this way they may serve as detachments.

[117.] Once committed to a March Regiment, Replacement Points may not be returned to the Replacement Pool. The SPs of a March Regiment may be incorporated into any unit of the same type and nationality, and in the same hex, during the Organization Segment. You may disband a March Regiment in an enemy ZOC. Once its strength is incorporated into another unit, the empty March Regiment counter is removed from play and becomes available for re-use.

Nationality (and Quality)

[118.] The nationality of a Player's troops must be respected. Units may not absorb SPs of any other nationality (or quality) than their own.

I.b.2. REPLACEMENT LEADERS & MAJOR GENERALS

[119.] Replacement Leaders & Major Generals are Leader counters used to show detached combat units operating independently on the game map. These Leaders may only be activated or voluntarily de-activated during the Friendly Command Phase. The number of such Leaders that may be activated is limited only by the number provided.

[120.] To activate a Replacement Leader or Major General place the Combat Unit counter to be made an independent command on the Leader’s track on the Organization Display during the Organization Segment (I.b.3), making sure its new position reflects the current Strength Point value of the Combat Unit. Then place the Replacement Leader or Major General in the Subordinate Leader’s box of the Force Leader, or in the hex with the Force Leader, depending upon the role Replacement Leader or Major General is to have in the coming Movement Phase.

[121.] Deactivation of a Replacement Leader or Major General may occur voluntarily by removing the Combat Unit counter from his track on the Organization Display and placing it upon some other Leader’s track in the same hex during the Organization Segment (I.b.3), or, involuntarily, if the Combat Unit counter is ever reduced to zero Strength.

[122.] A Replacement Leader or Major General may also be created at the Supply Source in order to create a March Regiment from Replacement Points (see ¶111).

[123.] Replacement Leaders and Major Generals are treated just like other Leaders when on the game map or in a Subordinate Leader box. They have an Initiative Rating, a Command Span, and a Subordination Value. A Replacement Leader can, but a Major General can never, be an unemployed Leader.

Replacement Counters

[126.] Combat units not called into play by the setup sheets or the Reinforcement Schedule are available as Replacement Counters. Once available, Replacement Counters are brought into play in the same manner as March Regiments. Replacement Counters are similar to March Regiments, in that they are “empty” Combat units which can be filled up with replacements and introduced into play at the Supply Source or Depot, or by “donation” of strength by a unit already in play. (Note that units which have been eliminated cannot be treated as Replacement Counters.)

I.b.3. REORGANIZING COMBAT UNITS ON THE ORGANIZATION DISPLAY

[129.] During the Friendly Organization Segment (only) a unit may be transferred to the track of another Leader in the same hex. Note: In games with units of different Coalition nationalities, leaders of one nationality may command leaders and combat units of another Coalition nationality.

Creation and Removal of Garrisons

[130.] Any friendly Citadel, Capital City, or Fortified Town can receive a garrison. If a garrison marker is available, a garrison may be created during the Reorganization Phase by deducting one SP from the Forces present in the hex. Neither player can have more garrisons in play than the quantity provided for the game. Place the created garrison directly on the map, flag side up.

[131.] During Step 3 of the Administrative Segment (only), a friendly force may absorb a non-Supply Source garrison of the same type and nationality in the same hex. The garrison absorbed is immediately removed from play, and its strength added to an infantry unit of the same nationality in the same hex. On the following turn the garrison becomes available to garrison another friendly-occupied Citadel, Capital City, or Fortified Town. Alternatively, a garrison may be treated as a March Regiment and be transferred to a leader’s track on the Organization Display.

I.b.4. STRENGTH TRANSFER

[133.] SPs from one Combat Unit may be transferred to another Combat Unit on the same Leader track, or on the track of a Subordinate Leader, as long as they are in the same hex (a Multi-Hex Force may not transfer SPs if the units doing so are not in the same hex). You may not increase the strength of a unit beyond its Maximum Strength. You may not transfer SPs among Combat Units of different unit types (light to regular cavalry, etc.) or between units in different modes (Forage or Concentrated).

[134.] March Regiments may be created by deducting strength from units on the Organization Display, placing the March Regiment on the same track or any track in the same hex.

Vedette Strength

[135.] The strength of Vedette units cannot be incorporated into the strength of regular units on the Organization Display. When two or more Vedettes are together in the same hex, only one Vedette per hex is allowed to remain on the map. The extra Vedettes in the hex are either removed to the Vedette Pool or else must move out of the hex. While in the Pool Vedettes have zero strength and are ignored for all purposes.

[136.] Not used.

THE FORCE

[137.] A Force consists of at least one Leader on the map and at least one Combat Unit on that Leader’s track on the Organization Display. More than one Leader may be in a Force but must be Subordinate to the Force Leader. The size of a Force is limited by the Command Span of the Force Leader (see ¶35 et seq.), but may never be more than 48 SPs for movement and stacking. If more than one Leader is in a Force and the Leaders occupy the same hex, Combat Units may be transferred between the Leader’s tracks during the Command Phase only (see ¶129).

Insubordinate Stacks

[138.] Where two or more Leaders are trying to occupy the same hex and there is no Leader present with a Command Span adequate to command all the others in a single Force, a Force or Forces are displaced one hex (see Priority 3 in “Retreat,” ¶371) at the moment in which their presence would create an Insubordinate Stack, according to the Priorities of Retreat.

[139.] If by deactivating a Replacement Leader or Major General a Leader would have a Command Span adequate to command, it is not considered an Insubordinate Stack if the Major General is deactivated in the next Command Phase.

Multi-FORCE Hex

[140.] Two Forces may occupy the same hex under the following circumstances: 1) Two Forces are moved into the same hex for the purpose of combining them into a single Force. A situation may not be voluntarily sustained in which two Forces coexist in the same hex. A Force may not end its movement in a hex with another Force if neither Force contains a Leader that can become the Force Leader. (However, see point 3 below.) 2) During the Command Phase, Subordinate Leaders may be removed from the Force Leader’s track on the Organization Display and placed on the game map. The instant these Leaders are on the game map they constitute new Forces and are no longer Subordinate to the Force Leader. In the subsequent Movement Phase one Force or the other must vacate the hex either through Movement Commands or the Initiative procedure (or if this fails, Displacement occurs; see ¶371). 3) If an external Leader is adjacent that can command both Forces.

Creation of a Force During Movement

[141.] A Force is defined during the Command Phase. Subordinate Leaders placed on the map during the Command Phase constitute separate Forces (see ¶140). No new Force Leaders may be placed on the map after the end of this Phase.

Exception: Subordinate Leaders may be dropped off at any time during Movement, Forced March, or Pursuit, in any hex passed through by the Force Leader. This must be done, however, the instant the Force Leader passes through the hex. To do so, simply remove the Subordinate Leader from the Organization Display and place on the map. This new Force may not continue moving and must remain in the drop-off hex for the rest of the Phase or Segment.

[142.] A Force must stop moving when any unit in that force runs out of MPs, unless it is dropped off. Thus a Force Leader can march with a mixed Force of Infantry and Cavalry, drop a Subordinate Leader off with the Infantry (if there already is a Subordinate Leader Force on the Force Leader’s track so constituted), and continue moving, or pursuing, with the Cavalry. A Force being dropped-off still determines its attrition with the rest of the Force, and the number of SPs is the number that started the movement with the Force Leader).

Creation of a Force During Combat

[143.] The attacking Player (only) defines a Force at the instant of combat (III.c.1 of the Sequence of Play). Thus he could move several Forces adjacent to the enemy and reconstitute them as one Multi-Hex Force under a single Leader if that Leader has a Command Span capable of subordinating the others into one Force.

Multi-HEX Force

[144.] For purposes of Movement and Combat a Leader may command other Leaders in adjacent hexes. Any Leader may combine the Force in his hex with Forces in adjacent hexes as long as the Leader has the Command Span to Subordinate the other Leaders. The Forces remain adjacent and may move under the Force Leader’s Initiative, or at the expense of a single Movement Command, and they may attack together. The maximum size of a multi-hex Force for movement and stacking, but not for combat, is 48 SPs. (See “Movement of a Multi-Hex Force,” ¶225; “Designate the Attacking Force,” ¶302).

Removing Losses from Combat Units

[145.] Distribute losses in Strength Points suffered by a Force (by whatever cause) throughout the Combat Units in the Force as evenly as possible so that, at the end of the last round of combat, all units have taken as even losses as possible (Exceptions: see Old Guard, ¶364, and mud attrition on artillery units, ¶269).

[146.] Not used.

II. MOVEMENT PHASE

GENERAL RULE:

[147.] Movement normally occurs during the Friendly Movement Phase and the Force March Segment of the Enemy Player-Turn. Forces move one at a time, from hex to contiguous hex in any direction or combination of directions. A Force may move no farther than its slowest unit, taking into account the differing costs of terrain (see ¶142).

[148.] Not every Force need move. Movement is optional and restricted by Movement Commands and Leader Initiative. All, some, or none of the Phasing Army’s Forces may move subject to Movement Commands and Leader Initiative. Unused Movement points may not be saved from turn to turn or given to other Forces; they are lost. The farther a Force moves the greater the severity of Attrition.

[149.] An Army’s Forces may only move during that Army’s Movement Phase or the Forced March Segment of the opposing Army’s Combat Phase.

Exceptions: A Force may move at two other times in the Sequence of Play.

When Repulsed during the Movement or the Forced March Phase.
When pursuing or retreating as a result of Combat. Once a Force has moved and rolled for Attrition, it may not move again that Phase, nor may it change its move.

PROCEDURE:

[152.] All reinforcements receive a free Movement Command on their turn of entry (see ¶154). Forces in an enemy ZOC and Forces without a viable LOC may not be given a Movement Command. After all Movement Commands have been given, the remaining Forces may attempt moving by Initiative. Whether moving by Movement Command or through successful Initiative roll, all movement follows a three-step procedure. Step 1: Activation. Either expend one Movement Command or roll for Initiative (modified for Resistance if in an Enemy ZOC - see “Exiting Enemy Zones of Control,” ¶195, ¶196) to activate the selected Force. Step 2: Movement. Expend Movement Points to cross hexsides and to enter hexes. Step 3: Attrition. Roll for Attrition (losses due to illness, straggling, and desertion) and remove Strength Points.

[153.] Repeat Steps 1 through 3 for each moving Force. During the Movement Phase, the Phasing Player also executes Step 3 alone for non-moving Forces. Further details on these procedures are provided in the following sections.

II.a. REINFORCEMENTS

[154.] Reinforcements are Leaders and combat units which do not begin the game on the map. Unless otherwise stated, Reinforcements arrive at their maximum strength. Reinforcements enter on the Turn, at the hex and strength indicated for them on the Turn Record Track or March Tables. Arriving Reinforcements enter during the Movement Phase and are considered to have a free Movement Command for the turn of their arrival.

[155.] Reinforcement combat units must enter under the command of a Major General or under a Reinforcement Leader arriving with them. Reinforcement units entering under the command of a Major General will be listed by unit designation and name. (When in doubt, use the strength of reinforcement units shown for the next Scenario Start Date, or use its full strength if there is no listing.)

[156.] Reinforcements calculate attrition as any other Force, tracing Dispatch Distance either from their Center of Operations or the nearest Friendly Supply Source or depot.

[157.] Reinforcements pay the Movement Point cost for the first hex entered on the map. If that hex has a road leading off the map the Force pays the road cost for the hex entered. If two Forces enter as Reinforcements at the same hex in the same Turn, the second Force to enter (Phasing Player’s option) is considered to have paid one (if on a Primary road) or two full Movement Points after reaching the first hex of the map.

[158.] When new forces are created or appear as reinforcements, up to two new Vedettes (if available) may be drawn from the “Vedette Pool” (see ¶24) to appear with each (quantities may vary). All other Vedettes are placed in the available Vedette Pool. When Forces are consolidated, Vedettes may remain in play on the map.

[159.] 1805 FOG: If there is Fog, the French Player may

have 2 additional Vedettes in play (if available in the Vedette Pool). The Fog Vedettes are placed during the French Player's Reinforcement Segment of any Fog turn (according to ¶24). They may move normally. They remain on the map until the following Austro-Russian Combat Segment. In Step 6, if the weather has changed and Fog is not in effect, the French Player will reduce his Vedettes on map to the number in play prior to the placement of the Fog Vedettes. (He can remove different Vedettes than the Fog Vedettes.) If Fog continues he will leave them in play.

Reinforcements & Extended March

[160.] Reinforcements may use Extended March.

Delaying Reinforcements

[161.] If the entry hex is blocked or controlled by an enemy Force the Phasing Player may delay the turn of arrival of the Reinforcement until the control of the hex or the blocking Force has been removed.

[162.] A player may delay the entry of his Reinforcements indefinitely, even if a designated entry hex is free of enemy occupation or control.

[163.] On subsequent Game-Turns the delayed Reinforcement may enter at any hex adjacent to the original entry hex but at the full cost of the terrain. (Reinforcements that enter the map into an enemy controlled hex may be Forced to retreat off the map in a subsequent battle and be eliminated.) An entering Force may use Repulse for the first hex entered (see ¶243). (A failure to Repulse will eliminate the Reinforcement.) A Force may not conduct combat, however, if it is not on the map.

[165.] Not used.

II.b. MOVEMENT COMMANDS

[166.] Movement Commands are available to each side during the Command Phase.

[167.] Any Force issued a Movement Command is guaranteed to move during the Movement Phase (II.b., of the Sequence of Play). To receive a Movement Command, a Force must start the Movement Command Segment within Dispatch Distance of the active Center of Operations of its army and no part of the Force may be within in the ZOC of an enemy Force.

[168.] 1805: Note: On 15-16 November the French may not

issue any Movement Commands—all movement must be by initiative only (see also ¶96).

ACTIVATION BY MOVEMENT COMMAND

[170.] The moving Player announces that a Force is receiving a Movement Command and immediately moves the Force. A Force given a Movement Command may not attempt to move again through Initiative in the following Segment (II.c. of the Sequence of Play). One Movement Command is issued to one Force regardless of its SPs, or Subordinate Leaders, or length of March, or its being a Multi-Hex Force.

[171.] Movement Commands are created and issued to the individual Forces of an Army during the Movement Command Segment (II.b.1). One Administrative Point is deducted from the Accumulated Administrative Points for each Movement Command created. Movement Commands may not be created if the Center of Operations currently has no Line of Communications. (Previously accumulated Administrative Points, in this case, are available for use after reestablishment of the LOC.)

II.b.1. Issuing Movement Commands

[172.] In order to receive a Movement Command, a Force must start the Movement Command Segment within Dispatch Distance of the active Center of Operations of its army and not be besieged. In the case of a multi-hex Force, only the Force Leader need be within this distance. One Movement Command is expended for the Force, regardless of its total strength or the distance of its March, so long as it is not making an Extended March.

[173.] Division of Command in the Coalition Armies In games with more than one Coalition Army, an Army may issue Movement Commands only to its own leaders. However, a Force Leader may include a leader from the other nationality in his Force. When this happens, the Force must move under the initiative of the Force Leader, and the Admin Level for attrition determination is that of the Force Leader’s army. The Administration of the two armies must be completely separate.

Dispatch Distance and Movement Commands

[174.] A Force need only be within Dispatch Distance of its active Center of Operations during Step 1 of the Movement Procedure to receive a Movement Command. It may move out of Dispatch Distance during Step 2 without consequences until the next turn.

[175.] Not used.

MOVEMENT OF CENTER OF OPERATIONS

[176.] The Center of Operations has a Movement Allowance of 5 Movement Points. For movement purposes, it moves like cavalry. It may not move under Initiative (and thus it may not Force March), but it may always move without expending a Movement Command.

[177.] On the turn the Center of Operations moves, Dispatch Distance is traced from its initial location, so the Center of Operations moves after all Movement Commands have been issued. In the following turn, the Center of Operations is inactive, while Dispatch Distance is traced from its new location (see “Effects of Center of Operations Movement,” ¶181).

[178.] A Center of Operations may not make an Extended March (see ¶185). It may not enter an enemy ZOC. It is never considered part of a Force, does not require a Leader, and does not count for stacking purposes. It is not subject to Attrition. A Center of Operations may enter any terrain. However, it must end its turn on a primary road hex in order to activate during the following turn (see ¶181). It has no Combat Strength or ZOC, cannot block the Enemy LOC or Dispatch Distance, and cannot damage bridges.

Effects of Center of Operations Movement

[181.] If a Center of Operations moves, it is inactive until the Consolidation Segment of the next friendly Movement Phase (II.e.) However, so long as it has an LOC, and units in Dispatch Distance still get the benefit of the Accumulated Administrative Point Total when determining Attrition; they are not required to use the “Zero” column simply because the Center of Operations has moved, but they must use that column if the Center of Operations is inactive because it has no LOC or is disbanded. An army with a Center of Operations that is inactive (no matter the cause) may issue no Movement Commands or receive replacements or APs.

“Flight”

[182.] The Center of Operations may never be captured. Instead, it must “flee” when placed in an Enemy ZOC or when an Enemy Force moves into the hex it occupies. If forced to flee, it is moved five Movement Points toward any Supply Source of that army free of Enemy ZOCs, at the owning Player’s choice. When displacing it ignores the presence of enemy Forces (in effect, the staff is reestablishing it further back along the LOC). Flight does not count as movement; the Center of Operations is active on the turn after fleeing.

[183.] If the Center of Operations is forced to flee and all of possible Supply Sources are in Enemy ZOCs, it flees off the map. If the Supply Source is not in Enemy ZOCs, it retreats no farther than the Supply Source.

[184.] If displaced off the map, the Center of Operations may return to any possible friendly Supply Source hex during the friendly Movement Phase after the hex is cleared of Enemy ZOCs.

Example: The French Player moves his Center of Operations in Turn 1, and flips it to its “Inactive” side. In that turn he added Administrative Points normally and issued Movement Commands. In his Administration Segment of Turn 2, he adds no Administrative Points, and issues no Movement Commands during the Movement Phase, but turns the Center of Operations back over to its "Active" (face-up) side. Thus, during his Combat Phase of Turn 2 and thereafter, the French Center of Operations is active.

II.b.2 EXTENDED MARCH

[185.] Any Force activated by a Movement Command may increase the Movement Allowance of all its units by up to 4 Movement Points by immediately expending one additional AP. This increase is termed Extended March. Forces making Extended March resolve attrition only once, at the end of their combined normal and Extended March, adding up to 4 to the Attrition Die Roll (see ¶186). An Unemployed Leader may not make an Extended March.

[186.] When determining attrition, use the line corresponding to the distance of the base (non-extended) march. Then add one to the die roll for each Movement Point of Extended March taken.

Note: If in Forage Mode, Forces making Extended March must use the “No LOC” Column.

ADMINISTRATIVE MARCH

[187.] A Force of a single leader, plus the units on his track (but no subordinate leaders), may make an Administrative March. This is a pre-programmed march over two Game-Turns. It may not include Forced or Extended March. Only one Administrative March per player may be under way at any one time.

[188.] To be eligible, the one-leader Force must be within Dispatch Distance of its Center of Operations and remain seven or more hexes away from the nearest Enemy Force throughout its route of march. Its destination, specified in advance, cannot be changed. If it comes within seven hexes of an Enemy Force it must stop and its Administrative March is terminated.

PROCEDURE:

[189.] Expend one Movement Command (this covers the entire two-turn Administrative March). Write down the exact hex of destination to be reached at the end of two marches. Move the force normally in the two Movement Phases.

[190.] Not used.

II.c. INITIATIVE

[191.] The Initiative Rating is the number to the left on the Leader counter and on the Leader’s track on the Organization Display. During the Movement Phase (or the Forced March Segment of the Enemy Combat Phase, see ¶297), a Force may attempt to move under the Initiative of its Leader. To move in this fashion does not involve the expenditure of Movement Commands.

Activation by Initiative

[192.] For each Force, the Player rolls the die. If the modified result is less than or equal to the Force Leader’s Initiative Rating, the Force may move. If the die roll exactly equals the Force Leader’s Initiative Rating, subtract 1 MP from the maximum Movement Allowance of that force for the current march. Exception: Leaders with an Initiative Rating of one may expend their unit’s full movement allowance on a die roll of “one.”

[193.] If the die roll exceeds the Initiative Rating by one or two, the Force can still expend one MP. If the next hex costs more than one MP, the Force will not be able to move.

[194.] If the die roll exceeds the Initiative Rating by more than two, the force may not move during the current Segment or Phase.

Example: If attempting to move an infantry Force Leader with an Initiative Rating of 3, and a “one” or “two” results, the Force may expend 5 Movement Points; if a “three” is the result, the Force may expend only 4 Movement Points in that march; if a “four” or “five” results, the Force may expend one MP; if a “six,” the Force may not move at all in that segment or phase.

Initiative and Exiting Enemy ZOCs

[195.] Whenever a Leader wishes to exit an enemy ZOC he must attempt this through Initiative. A Movement Command may not be issued to him. This Initiative die roll may be modified by the Initiative of the enemy Leader. Garrisons have an Initiative of “1” for initiative comparison purposes. Vedettes aren't affected by the Initiative Comparison Table, nor does their ZOC force enemy units to consult it.

[196.] This Initiative die roll modifier is called the Resistance Modifier. It is obtained by comparing the enemy Leader’s Initiative to the moving (active) Leader’s Initiative on the Initiative Comparison Matrix (see Charts & Tables). The resulting number is added to the die roll result (see ¶192).

Example: An infantry Force Leader with an Initiative Rating of “2” wishes to exit the ZOC of an enemy Leader whose Initiative Rating is “3.” The active “2” is compared to the passive “3” on the Initiative Comparison Matrix and a Resistance Modifier of “+1” is shown. This “1” is then added to the Initiative die roll for the active Leader. If he rolls a “1” the modified result is “two,” which equals the Initiative Rating - the Force may expend no more than four Movement Points in total - including the two MPs it costs to exit the ZOC.

[197.] If the active Leader is adjacent to more than one enemy Leader, the highest enemy Initiative Rating is used to determine the Resistance Modifier. If Enemy Leaders are stacked together use the Force Leader’s Initiative.

CAVALRY DIFFERENTIAL INITIATIVE MODIFIER

[198.] In any case where the Initiative Comparison Matrix is consulted to determine a Resistance Modifier, the side with superiority in cavalry may receive an Initiative Modifier. The Maximum Cavalry Modifier is plus or minus three.

Determining Cavalry Superiority

[199.] Count the amount of cavalry present, including only the cavalry in your attacking or defending Force that is in clear terrain. For purposes of this rule, villages are considered clear terrain; towns and centers are non-clear. Ignore hexside terrain. This rule treats terrain effects on cavalry slightly differently than those in combat. Here you simply do not count cavalry in non-clear terrain. Comment: Although cavalry can fight in non-clear terrain, they cannot hold the enemy unless they have the open terrain to deploy and charge. • Determine cavalry superiority (which side has the most); cavalry strength may not be withheld. • Divide the stronger side’s cavalry strength total by the weaker side’s total • Refer to the Cavalry Differential Modifier Table. • If one side has no cavalry, the modifier equals the number of Strength Points of cavalry on the other side (to a maximum modifier of plus or minus “3”). • If Pursuing, add (or subtract) the cavalry differential to the leader Resistance Modifier and apply this combined modifier to the Pursuit Die Roll. (Only count SPs actually In Pursuit for the Pursuing Force.) • If exiting an enemy ZOC, the Cavalry Differential Modifier can only be used to negate a “+” modifier from the Initiative Comparison Matrix. That is, Initiative cannot be better with combined Cavalry Differential and Resistance Modifiers than it would have been if the Force were not adjacent to the enemy.

Example: Active Initiative 4, Passive 2, would mean no Cavalry Modifier. • Cavalry need not suffer any Strength Point loss in the combat to contribute to the Cavalry Modifier.

Limit to Initiative Die Rolls

[200.] A Player may roll once for each Force he wishes to move through Initiative during the Movement Phase, and once for each Force he wishes to move during the Forced March Segment of the Combat Phase.

[201.] Not used.

MOVEMENT ALLOWANCE

[202.] Once it has been determined whether a given Force may move, that Force is immediately moved. A Force may continue to move until any unit in the Force uses its last Movement Point. The full Movement Allowance may be expended in both the Movement Phase and the Force March Segment of the Combat Phase (Exception: see “Activation by Initiative,” ¶192). A Force may never enter a hex unless every Combat Unit in the Force has sufficient Movement Points to cross the hexside and pay for the terrain in the hex.

[203.]A Force composed entirely of Old Guard infantry (plus any cavalry but not artillery or Young Guard) receives a Movement Bonus of 2 Movement Points. It may thus move up to 7 MPs in one Phase, without resorting to the Extended March procedure (which would allow the Old Guard to expend another 4 MPs, i.e., up to 11).

Expending Movement Points

[204.] A Force expends Movement Points in order to move from hex to hex. Terrain costs differ according to the unit type entering the hex. For instance, infantry find it easier than cavalry to negotiate a wooded area and, therefore, the MP cost for infantry entering woods is less than that of cavalry. If a mixed Force enters a hex where the terrain costs vary for the different unit types in the Force, a mental note must be made of the different amount of MPs expended.

WEATHER EFFECTS ON MOVEMENT & ATTRITION

Mud

[205.] 1805: Add one to the die roll on the Attrition Table.

Heat

[206.] All units add one to the Attrition die roll.

Rain

[207.] All units add one to the Attrition die roll. Subtract one from the Resistance Modifier when attempting to exit Enemy ZOCs.

Fair

[208.] No effects.

Frost

[209.] 1805: Primary Rivers and Lakes are frozen and are treated as (unfrozen) secondary rivers. Secondary rivers have the same effect whether frozen or unfrozen. For Secondary Rivers it is the steep bank and not the stream itself that presents the military obstacle.

Snow

[210.] Subtract one from the Resistance Modifier when attempting to exit Enemy ZOCs.

1805: Primary Rivers and Lakes are frozen and are treated as (unfrozen) secondary rivers. Secondary rivers have the same effect whether frozen or unfrozen. For Secondary Rivers it is the steep bank and not the stream itself that presents the military obstacle.

TERRAIN AND MOVEMENT

[212.] There are two categories of terrain types: those which apply to the area inside a hex and those which apply to the hexside shared by two hexes. The basic Movement Point cost for entering a Clear Terrain hex is one (1) MP. The MP cost to enter non-clear terrain and/or cross non-clear hexsides varies as shown on the Terrain Effects Chart. For purposes of Movement, Terrain costs are cumulative.

Roads

[213.] Marching from one road hex to another contiguous road hex (of the same road) enables a Force to pay the road cost for the type of road (primary or secondary) instead of the terrain cost for the hex. Example: Marching along a primary road in Clear Terrain costs one-half (1/2) MP for each hex entered. A Force with 5 MPs can thus march 10 hexes on the same primary road.

Rivers & Bridges

[214.] A Force may cross a Primary River hexside only through a bridge hexside. MP cost for bridge hexsides varies (see Terrain Effects Chart). If this bridge is part of a road then the cost to enter the hex on the other side of the river would be the same as for that type of road (plus hexside cost for the bridge, if any). Secondary River hexsides may be crossed at the additional MP cost noted on the Terrain Effects Chart, or by a bridge as over Primary Rivers. A Force which enters the hex before the bridge via a road hexside (primary or secondary) pays no additional MPs to cross a bridge. Note also that only 1 Force may cross a deployed pontoon bridge in each phase.

Exception: A Force in Forage Mode does not obtain the bridge benefit—it has to change to Concentrated Mode (at a cost of 3 MPs) to cross the bridge.

Crests

[215.] Crest hexsides do not cost any extra Movement Points.

Fortifications

[216.] A Redoubt hex (when attacked solely across Redoubt hexsides), a Capital City hex, a Fortified Town hex, or Citadel hex is considered a Fortification hex. No more than twenty-five (25) SPs (unmodified) may be stacked in a Fortification hex at the end of any Movement. (See¶360 for the effects of Fortifications on combat.)

1805: No more than 15 SPs may occupy a Citadel hex.

Moving in or out of a Besieged Citadel

[217.] To exit a besieged Citadel, a Force must attack the besieging enemy Force (see ¶309). A Force may not enter a besieged Citadel until the besieging Force is no longer adjacent.

Off-Map Movement

[218.] Generally, a Force may not move off the map. However, it is permitted for retreats (see ¶374) and in specific games.

Entering Occupied Hexes

[223.] A Force may never enter a hex occupied by an enemy Force (but see “Repulse,” ¶241 and “Unemployed Leaders,” ¶40). A Force may pass through any Friendly Force during Movement if that Force is not in an enemy-controlled hex.

Prohibited Hexes

[224.] Units may not enter certain hexes in some games.

MOVEMENT OF A MULTI-HEX FORCE

[225.] Leaders in different hexes which begin their move as part of a single Force must: 1) begin the move adjacent to the Force Leader; and 2) end their movement in the hex with, or adjacent to, the Force Leader. During the course of their march it is not necessary to remain adjacent to the Force Leader. Each subordinate Leader’s MP expenditure is calculated separately. The MP expenditure of the Force Leader (tallied for both infantry and cavalry) in a Multi-Hex Force is considered the march distance for all hexes of the Force for purposes of Attrition. (Use the highest amount expended by any single unit type.) Subordinate Leaders may be dropped off along the path of march in the same manner as for a single hex Force (and are counted for Attrition purposes in the same manner).

[226.] A Subordinate Leader in a Multi-Hex Force may move into an enemy ZOC while the Force Leader remains outside the ZOC, but the Force Leader must still be adjacent to the Subordinate Leader. The Force Leader’s stack would not be able to participate in the ensuing battle, however (a Force is constituted the moment of Combat and the Subordinate Leader would then become his own Force in this Phase).

[227.] Note that it is possible for a Player to move different Leaders from the same Force into different Enemy–controlled hexes - if the Movement Allowances of the units permit.

[228.] A Multi-Hex Force can be moved by the expenditure of a single Movement Command, or through the Initiative of the Force Leader. Once the Initiative die roll result is obtained for the Force Leader, no Subordinate Leader in that Force may attempt Initiative movement on his own. Note that if any part of a Multi-Hex Force is in an enemy ZOC, the whole Force must roll for initiative to leave the EZOC, even if the Force leader is not himself in an EZOC.

[229.] Not used.

MOVEMENT OF VEDETTES

[230.] The Movement Allowance of all Vedettes is 9 Movement Points. Vedettes pay cavalry MP costs. Vedettes move in every way like real Forces until their identity is revealed (except as outlined in items 1 through 6, below). Vedettes are revealed when adjacent to the enemy (see ¶250 and ¶379). A Vedette, once revealed, remains revealed until the next time it moves (regardless of the phase or segment in which it next moves). Vedettes differ from real forces as follows: 1) Vedettes do not require an Initiative die roll or Movement Command to move - nor do they suffer attrition. To disguise them, a player ought to some-times make Initiative and Attrition die rolls for them; 2) Vedettes cannot damage bridges, cannot capture pontoons or cut Lines of Communications or the like (see ¶85); 3) Vedettes are not subject to Initiative Comparison, and forces adjacent to Vedettes ignore their ZOCs when exiting (see ¶250); 4) A Vedette cannot create its own Major General, and has no track on the Organization Display (see ¶135); 5) Vedettes may not retreat after combat, and may not form part of a pursuit force (see ¶379); 6) Vedettes do not count against stacking limits.

Regular Cavalry Acting as Vedettes

[231.] The owning Player may choose to treat a cavalry Force of 1 Strength Point as a Vedette - if it is in Dispatch Distance at the moment it comes adjacent to an Enemy Force. A cavalry Force of 1 Strength Point may never damage bridges, capture pontoons, or cut Lines of Communications, dispatch distances or the like (see ¶85).

ZONES OF CONTROL

GENERAL RULE:

[232.] The Zone of Control is the hex occupied by the Force and the six hexes immediately surrounding it. All Forces exert a Zone of Control (ZOC) at all times. A hex in the ZOC of a Force is referred to as a Controlled hex. Unemployed leaders have no ZOCs (see ¶40). Adjacent opposing Forces are equally and mutually affected by each other’s ZOC. There is no additional effect if a hex is controlled by more than one enemy Force exerting control from different hexes.

[233.] Any Force in an enemy controlled hex (EZOC) at the beginning of the Friendly Battle Resolution Segment of the Combat Phase must attack an adjacent enemy Force, unless some other Friendly Force attacks that enemy Force.

TERRAIN INFLUENCE ON ZOCS

[234.] Terrain affects the extent of control exerted by a Force in some situations. A ZOC extends out of but not into a Fortification hex (see ¶216). Combat and counterattack are not mandatory for a Force inside a Fortification regardless of the size of the enemy Force that may be adjacent to it and in its ZOC, even if the force selected Pitched Battle. Vedettes cannot take advantage of the defensive benefits of a Citadel, but they do get applicable Town or Depot benefits.

[235.] A ZOC does not extend across a non-bridged Primary River hexside (see “Terrain Effects Chart”). A ZOC extending across bridged Primary River hexsides is modified in that combat is not mandatory between two Forces across the bridge, although all other effects remain the same.

EXITING AND ENTERING ZOCS

[236.] Upon entering an EZOC a Force must cease movement. (Exceptions: A Pursuing Force may ignore EZOCs in the first hex of the Path of Retreat, and the retreating Force may move through EZOCs (see “Priorities of Retreat,” ¶371, and “Pursuit,” ¶381). There is no extra cost to enter EZOCs.

Initiative for Exiting EZOCs

[237.] A Force in an EZOC (even if Flexible) at the beginning of the Command Phase may attempt to move out, but may only move by Initiative. This also applies if only part of a multi-hex force is in an EZOC. The Initiative Rating of the Force Leader is modified by the Resistance Modifier (see ¶196).

Extra Cost for Exiting EZOCs

[238.] A Force may never move directly from one EZOC to another (except in the first hex of Pursuit, or during retreat. To exit an EZOC costs two Movement Points in addition to any terrain costs of the hex newly entered. If the adjacent Enemy force has only 1 SP, there is no additional cost to exit; if 2 SPs, the cost is +1 to exit. Cavalry pays no additional cost to exit unless the enemy hex also contains one SP or more of cavalry. A Force in Forage Mode exerts a full ZOC only in the hex it occupies.

FLEXIBLE ZONES OF CONTROL

[239.] Vedette units and units in Forage Mode have flexible Zones of Control. When an enemy force enters the ZOC of a friendly-occupied hex containing only Foraging or Vedette units and does not announce a Repulse (see ¶250), the owning player must reveal the units. The enemy unit may continue moving around, but not through, the hex containing the Foraging or Vedette unit, ignoring its Zone of Control. The enemy unit may not end its move in the same hex as the Foraging or Vedette unit.

[240.] Not used.

REPULSE

GENERAL RULE:

[241.] During the Movement Phase, Pursuit, or Forced March, a Force may attempt to repulse an enemy Force in its path. To do this requires odds of at least seven-to-one. A Force in a Fortification (see ¶216) or across a bridged Primary River hexside may not be repulsed. A force attempting a Repulse into a Mountain hex may use no more than 9 SPs (see ¶356). (This means that any Force of 2 SPs or more in a Mountain hex can never be Repulsed.) Vedettes may be Repulsed (see ¶250) if the attempt is declared before the Vedette is revealed.

PROCEDURE:

[242.] The Force moves adjacent to the Force to be repulsed. (If during a Forced March, the Force must pay one additional MP to make the repulse attempt.) The owning player declares “attempting repulse,” stating the number of Strength Points in his Force. Both players reveal their leaders, but the enemy player does not reveal his strength unless the Repulse is successful. If this number (modified for terrain) is seven or more times the strength of the enemy Force, the latter simply retreats two hexes. This retreat is carried out under the same restrictions as a retreat after combat in a Pursuit battle except that there is no Pursuit. If the repulse was successful the Phasing Player may continue his movement. The required odds are modified if either unit is in Forage Mode (see ¶281).

[243.] If the repulse attempt is not successful (the odds being less than seven-to-one) then that Force ceases Movement. The exact strength of the Enemy Force is not yet revealed. In the Battle Resolution Segment the Repulsing Player must attack the Force unsuccessfully repulsed. The attacker must choose a Pursuit battle during the first round. The combat is resolved at two columns to the left of the actual odds on the Combat Results Table (a six-to-one attack becoming a four-to one attack). If the repulse attempt takes place during Pursuit and is unsuccessful, the Force ceases movement and there is no subsequent attack. In a failed Repulse during the Forced March Phase the force in motion loses one SP, gets no specific information about the enemy and its Force March ends immediately. The attempting force must stop moving, remaining adjacent to the enemy. There will be no follow-on combat with this force.

[244.] Repulse during regular Movement or Pursuit does not require the expenditure of Movement Points on the part of either the Phasing or non-Phasing Force (other than the cost to enter the hex vacated by the repulsed Force). If during a Forced March, the Repulsing Force must pay one additional MP to make the Repulse attempt. Repulse during Forced March does not require the presence of another friendly unit (see ¶297). The Force may enter an EZOC even if it isn’t occupied by, or adjacent to, a friendly unit in an enemy ZOC, if a Repulse attempt is declared at that moment. (This is an exception to ¶64).

[245.] Repulsed/Repulsing Forces may be attacked during the Combat Phase.

Multi-Hex Repulse

[246.] If a Phasing Force moves adjacent to two enemy Forces simultaneously, and wishes to attempt repulse, the attempt must be made upon both forces as one. The non-Phasing Player must have seven times the combined total of Strength Points in both Forces to achieve a successful repulse. These two enemy Forces may not be repulsed separately.

Repeated Repulse

[247.] The number of successful repulse attempts a Force may initiate is limited only by the number of Movement Points the Force has available to it. (It can attempt another repulse if the need arises during its move). There is no limit to the number of times a Force may be repulsed in a single Movement Phase.

Repulse with Vedettes

[248.] By attempting repulse, a Vedette may determine the identity of the enemy force leader and then retreat before combat. Alternatively, the Vedette can follow through with a regular attack in order to obtain the exact strength of the enemy forces during step 6 of the Combat Sequence (the Vedette will usually be destroyed, but may be recreated – see ¶368).

1805: Vedettes of all armies are prohibited from making repulse attempts during Fog.

Player's Note

[249.] There are two reasons to enter your own Vedette into an Enemy ZOC. First, by attempting a repulse, to determine the identity of the enemy leader (the Vedette may retreat before combat). Second, in order to obtain the exact strength of enemy forces in their ZOC during step 6 of the Combat Sequence (the Vedette will usually be destroyed, but may be recreated - see ¶368). Thus, Vedettes can give the owning player a “quick impression” which he can respond to during movement, but he can’t get exact information until after all movement is complete.

Repulse of Vedettes

[250.] The owning player must reveal the Vedette after his opponent has declared whether he will attempt to repulse the hidden unit. If so the repulse attempt is executed. The Vedette may not be repulsed in the current Movement or Forced March Phase unless the opposing player announced his intention to repulse prior to the revelation of the Vedette.

Exception: A Vedette which is not repulsed by the first unit to enter its ZOC may be repulsed by follow-on Forces.

II & II.f. BRIDGES

[251.] Any road crossing a Primary River hexside is a Primary Bridge. All roads crossing Secondary Rivers are Secondary Bridges. To damage or repair bridges requires the expenditure of a certain number of MPs, which cannot be carried over between turns. (Refer to the Bridging Summary table.) Primary Bridges have a higher MP cost to damage or repair, and may not be affected by all-cavalry forces. There are also MP costs to deploy or remove Pontoons. Unlike all other Movement Point costs, MPs expended relative to the damage, repair, deployment and removal of bridge structures do not count toward the total expended for determining Attrition, and the unit may receive Replacements and work on bridges the same phase. A Force which expends Movement Points relative to bridge structure (i.e. any Movement Points shown in the Bridging Summary table) may not make an Extended March that phase or expend MPs during its Forced March segment to work on bridges.

Damaging Bridges

[252.] A force can damage a bridge during a friendly Movement Phase by expending additional Movement Points according to the Bridging Summary in a hex adjacent to the bridge hexside. While the unit spends the MPs in the Movement Phase, the bridge is not actually destroyed until the Bridge Segment, so units may continue to use the bridge in the Movement Phase.

[253.] Place a Damaged Bridge marker on the damaged bridge. For movement purposes, LOC and other traces, a damaged bridge does not exist until it is repaired.

Repairing Bridges

[254.] A Force can repair a damaged bridge during a Friendly Movement Phase by expending a number of additional Movement Points per bridge according to the Bridging Summary in a hex adjacent to the bridge hexside. If an Enemy non-Vedette Force occupies the other hex adjacent to the bridge hexside, the bridge cannot be repaired. If an enemy Force occupies any other hex adjacent to the repairing force, add “three” Movement Points if the bridge spans a primary river, but only one MP if it spans a secondary river. While the unit spends the MPs in the Movement Phase, the bridge is not actually repaired until the Bridge Segment, so units may not use the bridge in the Movement Phase. Once the repair is completed, the Damaged Bridge marker is immediately removed.

BRIDGE TRAINS

[255.] A bridge train travels with a Force, and its marker is kept on its Leader’s track until it is deployed. The number of bridges available to each army depends on the game. Bridge trains are usually assigned to specific Leaders at the beginning of the scenarios, according to the Scenario Information.

[256.] Bridge Trains have no Combat Strength or Subordination cost - their Movement Allowance is 5, paying infantry costs.

[257.] A bridge train can be used to bridge any river, primary and secondary alike. A bridge train cannot be destroyed, damaged, or repaired, but it may be captured. Note that a bridge train cannot create its own Major General, may not make an Extended March, may not retreat, and may not form part of a pursuit force. If abandoned, it can be placed in the currently occupied hex on the map (bridge-train side up). It has no Combat Strength. Deployed bridged trains are called pontoons, and most bridge train markers have pontoons on their reverse sides.

Capturing Bridge Trains

[258.] Undeployed bridge trains are left in place on the map if the Force they are with makes a pursuit, or is forced to retreat, etc. Any time an enemy Force enters a hex containing an undeployed friendly bridge train, the bridge train is considered the enemy’s bridge train for all purposes. Undeployed Bridge Trains may not be damaged. Either Player may capture such an abandoned bridge train by occupying or passing through its hex with any Force, including during Pursuit. A deployed pontoon may be captured by expending 2 MPs (see ¶260).

Pontoon Deployment

[259.] A bridge train on a Leader’s track is considered to occupy the same hex as the Leader. During any friendly Movement Phase that the Leader occupies a hex adjacent to a river hexside and his Force expends 3 additional Movement Points to deploy the bridge train, he can place the pontoon on the map at the appropriate hexside. A pontoon can be used as soon as it is deployed. To remove a friendly deployed pontoon from the map, a friendly Leader must expend 2 additional Infantry Movement Points in either hex adjacent to the pontoon hexside during the Movement Phase. A Force may deploy a pontoon when adjacent to an enemy Force (even if the enemy Force is across the hexside being bridge) by expending its full MA for the turn. However, a pontoon cannot be converted back to a Bridge Train if an enemy unit occupies the hex on either side of the pontoon.

Note: A deployed pontoon cannot march or retreat.

[260.] A Leader who carries a bridge train on his Organization Display could abandon the bridge train and then leave the hex (although he may run the risk of an enemy Force capturing the pontoon). At a later date, the same or another Leader could expend 2 MPs in the bridge train hex during a march and place it back on the Leader track.

[261.] Not used.

MARCH ATTRITION

GENERAL RULE:

[262.] During the Movement Phase, all Forces currently in play are subject to attrition (regardless of whether the Force actually moves). During the Forced March Segment of the Combat Phase, only those Forces which actually move at least one hex are subject to Attrition.

In Supply

[263.] As long as a Force begins a march within Dispatch Distance (see ¶86) of its Center of Operations with an LOC or of a depot with an LOC (including any possible Supply Source of that army), that Force is regarded as “in Supply.” When determining attrition for that Force a player may use the column on the March Attrition Table corresponding to the number of Administrative Points currently in the friendly Accumulated AP Track. If the Force does not have a valid Dispatch Distance, it must forage or use the “zero” column on the Attrition Table. Dispatch Distance may not be traced from the Center of Operations or a depot which is out of LOC or if there is no active Supply Source.

PROCEDURE:

[264.] After a Force completes its move and before any other Force begins moving, the attrition for that move must be determined. Attrition is determined separately for each Force. The Phasing Player must cross-reference the total number of Infantry, Cavalry and Artillery Strength Points in the Force with the Length of March on the March Attrition Table. Use the highest MP cost expended by any single unit type. After rolling the die and taking into account any modifiers, cross-reference the die roll with the size of Force, located beneath the heading for the appropriate army. The result is the number of Strength Points lost by the Force. Adjust the Combat Unit counters of the Force on the Organization Display to reflect this loss. Attrition losses must be distributed as evenly as possible among the several combat units of a Force. A Force that started its movement out of Dispatch Distance must locate its force strength on the “zero” or “No LOC” column (the table may vary in each game).

[265.] Note that there is a separate column on the March Attrition Table for Cavalry. Use the Cavalry Column only if all units in the Force are Cavalry. Optional: A combined force of infantry and cavalry may be handled as if it were two separate Forces by determining Attrition separately but using the same die roll.

[267.] Modifiers to the Attrition Die Roll

If the Force Leader has a star indicating a Bonus Point, reduce the die roll by one (see ¶45).
Certain conditions of weather (see ¶205 to ¶211).
If the Force is Force Marching. (see ¶297).
If the Force is making an Extended March (see ¶185).
Modify the die roll for Morale or Army Condition as per the Exclusive Rules.

1805: Ignore this modifier; it does not apply.

Whenever the Exclusive Rules indicate another modifier.

[268.]Attrition Losses are specified in increments of 200 men; thus, five increments equal one Strength Point. When the Attrition Table calls for a loss of “.2,” that means 200 men (one increment) lost. These increments are recorded on each track on the Organization Display. Each leader has an Incremental Strength Marker which begins the game in the “Zero” space on his track—the left-most box. Each time an increment of 200 men is lost to attrition, the marker moves one box to the right. When the marker reaches the “4” space (800 men lost), its next increment loss will put it in the “5” space (1,000). When this happens, reduce the strength of any combat unit. For each five increments lost, reduce the strength of one unit on that track (owning player's choice) by one Strength Point (1,000 men). The Incremental Strength Point Marker does not affect the current strength of the Force until it reaches the “5” space—odd amounts of men do not affect a Force's total strength in combat; i.e., the location of the Incremental Strength Point Markers on the Tracks is ignored for purposes of combat, etc., and does not affect total Strength of the Force.

ARTILLERY

[269.] During mud, one artillery unit in a force must take the first SP of loss due to attrition. Ignore this requirement if the total artillery strength of the Force is two or less.

FRENCH OLD GUARD EXEMPTION

[270.] Certain types of Combat units never suffer attrition: Infantry, Cavalry, and Artillery of the French Old Guard, or French Young Guard Infantry that is commanded by the same Leader as any unit of the French Old Guard. These units do not count against the total number of Strength Points when figuring the attrition of a Force that might also include regular line units of the French Army. For instance, a Force of thirty eight SPs containing six Old Guard SPs and eight Young Guard SPs would only have to figure the attrition for a total of twenty-four SPs.

FORAGING ATTRITION

[271.] In addition to the normal Attrition Procedure (see ¶264), forces may also use the Foraging Attrition procedure. Any force may Forage.

Forage Mode

[272.] When an army could not supply its troops, its soldiers would disperse and forage for their own provisions and fodder in the countryside. A Force must be in Forage Mode in order to Forage (see ¶278). If a Force is not in Supply and does not forage, it must use the column on the Attrition Table headed “No LOC.” (A player may prefer to use the “No LOC” column at times when the nearness of the enemy makes it too dangerous to enter Forage Mode.) Any eligible non-besieging Force may begin a scenario in Forage Mode at the owning Player’s option.

[273.] If a Force is eligible to Forage and is also within Dispatch Distance of the Center of Operations, Depot, or a Supply Source, the owning player may elect to use the Forage Procedure or the Accumulated Administrative Level when determining Attrition.

Foraging Procedure

[274.] The player adds together the Forage Value of the hex the Force occupies and all of the adjacent hexes the Force could legally occupy. On the line labeled “Forage,” find the corresponding column on the Attrition Table instead of APs Accumulated. The quality of the forage depends solely on the total value of the Force Leader’s hex and the hexes in his ZOC (see ¶283 & ¶287).

[276.] Determine the appropriate Attrition Table Column individually for each separate Force. Forces in Enemy ZOCs may forage, and they may remain in Forage Mode in an Enemy ZOC (see ¶284).

Example: A force in a Town surrounded by clear terrain has a Forage Value of 10.2. The size of the force would be found under the heading “9+.”

Concentrated and Forage Mode

[278.] Forces operate in two modes. A Force is in Concentrated Mode unless marked with a “forage” marker on the Force Leader’s display. Forage markers are used to designate all Forces in Forage Mode. The Force changes Mode during March or Forced March. Changing to Forage Mode costs one-half Movement point. Changing to Concentrated Mode costs three Movement Points. You may attempt to change to Concentrated Mode in an Enemy ZOC through Initiative. A Force in Forage Mode does not suffer Resistance Modifiers. MPs expended to change mode do not count toward the total expended for determining Attrition, and unit may receive Replacements and change mode the same phase.

[279.] To Forage, a Force must be in Forage Mode upon completion of all Movement Point expenditures for that Phase and may not have executed an Extended March.

[280.] A Force in Forage Mode exerts a flexible ZOC. This is treated just like Vedettes which also have a flexible ZOC (see “Flexible Zones of Control,” ¶239). Enemy Forces may enter and/or leave a hex adjacent to an enemy Force in Forage Mode without stopping or having to suffer a resistance modifier.

[281.] When defending, a force in Forage Mode suffers a shift of two columns to the right (a 2-1 becomes 4-1 odds), and may choose Battle type normally. The force can roll to attempt to change mode after each round of combat. (If a Force in forage mode joins another one not in forage mode, a one-column shift is applied.) Forces in Forage Mode are repulsed at 5-1 odds (not shifted) instead of 7-1 odds, and to initiate a Repulse must have 9-1 odds. A Force in Forage Mode may attack (not shifted), alone or in concert with a Friendly Force in Concentrated Mode.

Forage Ratings

[282.] See the Terrain Effects Chart for each game for the Forage Values of hex type.

How to Determine Forage Value

[283.] Total the Forage Rating of the seven hexes adjacent to and occupied by the Force Leader in his final resting place at the end of the phase. (Exceptions: see ¶284 et seq.)

1805: Example of Foraging Attrition

An Austro-Russian Force of 28 Strength Points during regular movement in mud, expends 3.5 Movement Points. It has a Forage Value of 10, and would thus find its strength in the “9+” column. A die roll of 6 +1 = 7, yielding 3 Strength Points lost.

Effects of Enemy ZOCs on Foraging

[284.] Units in Enemy ZOCs may Forage; however, neither an enemy -occupied hex, nor a hex with enemy forces adjacent on opposite sides, may be foraged. Example: If Enemy forces (even merely Vedettes) occupy 2318 and 2517, 2417 may not be foraged.

Foraging of Multi-Hex Forces

[285.] In determining Forage Value, count all hexes occupied by and adjacent to the Force Leader only. Count each hex only once, and determine one total for the entire Force. Separate Forces which move to adjacent hexes - or to the same hex - must still resolve attrition separately.

Overlapping Forage Areas

[287.] The Forage Rating of a hex eligible to be Foraged by two or more Friendly Forces must be divided between those Forces as the player sees fit. A hex may not be counted twice.

1805 Example: Soult and Lannes arrive in Brünn by two different roads. Only one of them could forage the hex of Brünn; the other might be allowed to forage all the surrounding hexes.

Town Forage

[288.] A Force must end its move in a town, Citadel, or depot hex in order to count its Forage Rating as part of its total Forage Value. Town hexes adjacent to part of a Force which are unoccupied by a component of that Force are skipped over, counting as the value of the other terrain in the hex. (A Force in a town may count the Forage Value of surrounding countryside.)

Citadels

[289.] The force besieged in a Citadel (like all other forces) must roll each turn on the Attrition Table. Besieged units may not forage the hex they occupy, but besieging Forces may forage normally. Besieged Forces must use the zero column on the Attrition Table when determining attrition. In addition, each Citadel has an Attrition modifier that must be applied to all attrition rolls. Begin using a Citadel’s modifier as soon as a Force becomes besieged in that Citadel. Also, the Attrition modifier used by a besieged Force will increase over time, on dates specific to each game.

1805: a. Starting modifier for both Citadels: +3.

b. Increase by 1 on turn 9 (Dec. 1-2)

Revictualizing Citadels

[290.] To revictualize a Citadel, a named leader (not a Major General) of the besieged Force’s side must enter the citadel hex. This event resets the Attrition modifier to its original value; if once again besieged, begin increasing the Attrition modifier from that value.

[291.] A siege may be lifted by the removal of enemy forces, even if a named friendly leader does not enter. In this case, do not reset the modifier; however, the friendly Force may then forage normally (in games that permit foraging).

II.e. STACKING AND CONSOLIDATION

[293.] A maximum of forty-eight (48) SPs may occupy a hex at the end of a Phase or Segment. You may never have a stack of more than 48 Strength Points. (The maximum size of a multi-hex Force for movement and stacking, but not for combat, is also 48 SPs—see ¶144). There is no limit to the number of Friendly Forces that may pass through a single hex during either the Movement Phase or the Forced March Segment of the Combat Phase. (Exception: See “Fortifications,” ¶216.)

Consolidation

[294.] Leaders in the same hex that are part of the same Force must be moved onto the Subordinate Leaders box of the Force Leader’s track on the Organization Display during the Consolidation Segment of either the Movement Phase or the Combat Phase. (See also “Multi-Force Hex,” ¶140, and “Insubordinate Stacks,” ¶138.) Consolidation can be performed at any time, and not just at the two Consolidation Segments. A consolidated Force is in Forage Mode if any consolidating unit was in Forage Mode.

[295.] If not a Frost or Snow turn, begin, or complete Redoubts in any hex with a Force that didn’t move and has 12 or more infantry SPs not commanded by a Major General.

[296.] Not used.

III. COMBAT PHASE III.a. FORCED MARCH

[297.] Forced March is Friendly Initiative movement during an opposing Player-Turn. Movement Commands may not be used in this Segment. In this Segment a friendly Force may enter an enemy Zones of Control only if the hex entered is occupied by, or adjacent to, another friendly Force in an enemy Zone of Control, unless the moving unit is performing a Repulse attempt (see ¶244). Units may expend their entire Movement Allowance in Forced March (Exception: see “Activation by Initiative,” ¶192). Forces making a Forced March resolve attrition at the end of their movement by adding one to the die roll for each Movement Point of Forced March taken (rounded up), up to a maximum of four.

III.b. COMBAT

[298.] Adjacent opposing Forces attack and defend using the following procedures. To begin, Players secretly choose which type of battle they wish to fight: 1) In a Pursuit Battle the Player attempts to trade space for time; 2) In a Pitched Battle the Players are willing to trade losses rather than retreat, prolonging the battle with several rounds of attack and counterattack.

[299.] All adjacent enemy Forces must be attacked if the friendly Force is in an enemy Zone of Control (see “Terrain Influence on ZOCs,” ¶234).

PROCEDURE:

[300.] The following procedure is executed for each Force in the ZOC of the enemy during the Battle Resolution Segment of the Combat Phase. Further explanation of each step immediately follows the procedure.

Step 1: Designate the Attacking Force (see ¶302). The Phasing Player reveals the Leaders of the Force making the attack. An attacking Force in a Citadel hex may choose to become besieged in order to avoid the combat. In any round other than the first, the Phasing Player may commit units from the Reserve (see ¶322).

Step 2: Designate the Defending hex(es) (see ¶313). The non-phasing Player reveals the Leaders of the Force in the defending hex(es). A defending Force in a Citadel hex may choose to become besieged in order to avoid the combat. In any round other than the first, the non-phasing Player may commit units from the Reserve (see ¶322).

Step 3: Select the Battle Type.

a) Reveal approximate SPs in the attacking and defending Forces rounded off to the nearest ten (10). For instance, if a Force has 14 SPs, inform the opposing Player that there are ten SPs against him (four or fewer SPs would still be revealed as ten). Vedettes may retreat before combat.

1805: Fog Effect on Approximate Strength Report

If there is Fog, during Step 3a of the Austro-Russian Combat Phase, any French Force not in hill or mountain terrain can report up to 50 as an approximate Force Strength. A vedette can be represented as 50 SPs, while a Force of 48 SPs can be represented as a vedette. The true exact strength of the force will be revealed in Step 6 as usual. The French took advantage of the ground Fog lying in the valleys to conceal important forces in enemy ZOCs.

b) If using the optional Reserve rules (see ¶315), both players place the requisite number of units in Reserve. This is done only in the first round, and that is the only time that units may enter the Reserve during a battle.

c) Both Players select a battle type based on the terrain their Force occupies, and, optionally, the number of units in Reserve (see ¶327). • A Force may always select Pursuit unless it is a besieged Force attacking out of a Citadel (see ¶328). • There are restrictions on the ability to picked Pitched (see ¶329 et seq.), Refuse (see ¶331 et seq.), and the optional Rearguard (see ¶335) Battle Types.

Step 4: Determine the Cavalry Differential (see ¶340). Compare the actual amount of cavalry in both the attacking and defending Forces. If either Force has a two-to-one or greater advantage then subtract one (1) from their Bombardment die roll.

Step 5: Perform Artillery Bombardment (see ¶347). Both Players determine the amount of Artillery SPs in their Forces. The attacker resolves his fire first, then the defender fires. Note that the Artillery Fire Table is based solely upon the number of Artillery SPs firing, and is not based on an odds ratio (note die roll modifiers). Each Player rolls one die; the result is given in Enemy SPs lost. Apply the results immediately. If the bombardment destroys the enemy unit, the winning Force may advance into the hex, but may not pursue.

Step 6: Determine Odds on the CRT (see ¶350). Determine the odds by revealing the exact number of SPs in each Force and applying the effects of Terrain on the SPs. Artillery SPs are not taken into account for odds determination unless defending alone. Fractions in combat strength are rounded off to the nearest one-half SP.

Step 7: Resolve the Attack (see ¶362). If there are French Old Guard involved in the attack the French Player first announces if they are “staked” this round. Roll the die. The bold face result on the CRT odds column indicates which side loses. The winning side removes losses in SPs. The losing side reveals its Battle Marker. If the losing side chose Pitched Battle, go to Step 11.

Step 8: Perform Any Retreat (see ¶369). If the Losing side chose Pursuit Battle, then the result specifies only the length of retreat for that side. Execute retreat according to the rules governing Paths and Priority of Retreat.

Step 9: Perform Any Pursuit (see ¶380). If the winning Force wishes to Pursue the losing Force, determine the Resistance Modifier, then consult the Pursuit Table. The Pursuit die roll may be modified by the Resistance modifier, the Weather, Reserve and French Guard Modifiers, plus the number of Pitched rounds revealed by the winning Force. The result of the die roll is the number of hexes the winning Force may Pursue. If there is a Pursuit, decrease the strength of the Retreating Force by one SP for each hex of actual Pursuit. Only one Force may Pursue. The losing side always loses at least as many SPs as the winning side regardless of Pursuit.

Step 10: Adjust Morale (see ¶395). Shift the morale marker one space in favor of the victor for each occurrence: a) The battle is a Critical Battle; b) A Major Personality was captured; c) The French Imperial Guard has been “staked” and defeated. Proceed to the next battle.

Step 11: Implement Pitched Losses (see ¶399). If the losing Force revealed Pitched Battle in Step 7 above, then the result obtained in Step 7 shows the SPs lost.

Steps 12-17: Counterattack. In the event the losing side revealed Pitched Battle in Step 7 above, the non-Phasing Player becomes the attacker and executes the following steps. The old Battle type markers remain in effect until the end of one complete round – attack and counterattack.

Step 12: Designate the Attacking Force. Same as Step 1.

Step 13: Designate the Defending hex(es). Same as Step 2. In addition, the counter-attack does not have to involve all adjacent Forces, but must include the strongest adjacent hex. When counterattacking a single hex in a multi-hex force, the counterattacker must withhold half as many SPs as are present in the unattacked hex(es) of the enemy Force involved. These SPs are not required to attack, they are just withheld. Withheld SPs from a counterattacking force suffer losses with the counterattacking portion. The units withheld may be units that are in Reserve. If the counterattacking force cannot withhold the necessary number of SPs, then it must counterattack all of the attacking units.

Step 14: Determine Odds on the CRT.

Step 15: Resolve the Attack.

Step 16: Perform Any Retreat.

Step 17: Perform Any Pursuit.

Step 18: Adjust Morale. In the event that the losing side again reveals Pitched Battle, Steps 1 through 11 are repeated in their entirety for the reattack of the Phasing Player.

[301.] Forces may be freely re-defined between rounds, and the original attackers may be required to attack different defenders if the units that originally attacked those forces are no longer present.

NOTE: If there are any other battles within 8 hexes, the first round of each battle must be resolved before any battle proceeds to round two.

(Step 1 and 12) DESIGNATE THE ATTACKING FORCE

[302.] No Force may participate in more than one attack per Phase.

Exceptions: (1) If the enemy hex is vacated in the first round, the Friendly Force may join in any other adjacent Pitched Battle in its second and succeeding Rounds. (2) Failed repulse during pursuit.

[303.] No Force may be involved in more than one battle per Phase (all rounds of a Pitched Battle are considered one battle).

[304.] Combat is mandatory between adjacent opposing forces (Exceptions: Forces across Primary Bridges or in Fortifications [see ¶216], including Citadels [see ¶217]). The Phasing Player decides where his Forces will attack as long as separate Forces never attack the same hex, and as long as all adjacent opposing Forces are attacked. However, non-phasing counterattacking Forces need only attack the strongest adjacent hex of the initial attack.

[305.] A single combat may involve attacking and/or defending Leaders in any number of hexes as long as the attacking Leaders are all part of the same Force. To be resolved as a single combat the attacking Force must be adjacent to all of the defending hexes.

[306.] The Phasing Player may have more than one Force adjacent to a defending hex or hexes, but only one Force may attack this same defending hex.

Sieges

[307.] At the moment combat would normally be required, a Force in a Citadel hex must decide whether to resolve the combat normally, or use the Citadel benefit of avoiding the combat. If it chooses to resolve the combat, it may not choose Pursuit Battle.

[308.] Once a Force in a Citadel has taken advantage of the Citadel to avoid combat, all Forces in the hex are considered to be under siege. Place a Siege Marker in the hex. A besieged Citadel may not be attacked. Counterattacks against citadels are not mandatory.

[309.] Besieged Forces may attempt to attack out of the Citadel, shifting the odds on the CRT one column to the left (in addition to other terrain effects). (This shift is due to the entrenchments that besieging forces would have constructed.)

[310.] Once placed under siege, a Force remains in that condition until the beginning of any Phase in which the hex is no longer adjacent to Enemy Forces.

Vedettes in Combat

[311.] During the Friendly Combat Phase, Vedettes in enemy Zones of Control are compelled to attack (Exception: see “Vedettes Retreat Before Combat,” ¶314). Vedettes are treated as normal combat units for combat purposes, except as follows. Vedettes must combine in attacks with other friendly units in the same hex. A Vedette may attack an enemy hex only if there are no other friendly forces in the Zone of Control of the enemy unit. Vedettes have a Combat Strength of 1/2 SP when fighting alone and a combat strength of zero when combined with a real force.

Example: An attack by a unit with a strength of “two” upon a Vedette would be resolved at four-to-one odds.

Garrisons in Combat

[312.] Garrisons may not attack, and must defend as part of any other force in the hex. They must absorb the first SP lost in retreat. Garrisons have an Initiative of “1” for pursuit and for initiative comparison purposes.

(Step 2 and 13) DESIGNATE THE DEFENDING HEXES

[313.] The Phasing Player states which hex(es) the Force will attack, except if a Force chooses to become besieged (see ¶307). Enemy Leaders (and their Combat units) stacked in a hex always defend together. Several Leaders together in a hex may never be attacked separately. A Force may attack two or more enemy forces that are not adjacent to one another but must attack them as one Force, with a single die roll. Only one defending Force may counterattack the same attacking Force. During the Friendly Combat Phase, each Enemy Vedette with one or more Friendly Forces in its ZOC must be attacked. A player may not ignore a Vedette to which his Forces are adjacent during his own Combat Phase.

Vedette Retreat Before Combat

[314.] Non-Phasing Vedettes (first) and then Phasing Vedettes which are alone in the hex (as well as cavalry Forces of 1 Strength Point, see ¶231) can take an automatic, voluntary “Retreat” result, of one or two hexes, before combat resolution but after finding out the approximate strength of the enemy-occupied hex, in step 3a of the Combat Procedure (see ¶300). The enemy may not pursue. Vedettes must engage in combat normally if they do not elect to take the auto-retreat.

(Step 3, Optional) RESERVES

[315.] Units or Leaders may enter the Reserve if they are part of a Force in battle. Reserve Markers are deployed directly on top of individual combat units or leaders on the Organization Display. The Reserve rules apply to all battle types, though a Force must have a certain minimum number of units in Reserve to select Pitched, Refuse, or Rearguard Battle type.

1805: Reserve rules are recommended for use in Sun of Austerlitz.

Cavalry and Artillery in Reserve

[316.] Cavalry in Reserve counts toward Cavalry Differential. Only the cavalry still remaining in Reserve after the battle is resolved counts in determining Cavalry Differential for the Pursuit. Artillery in Reserve may not fire.

Step 3, Round 1 Entering the Reserve

[317.] Units will enter the Reserve at the beginning of any given combat (see ¶300). You must deploy to the Reserve: a) All units in a hex in excess of 20 Strength Points per hexside through which you are attacking or defending. You may not place part of a unit’s strength in reserve. Artillery not in Reserve may fire in addition to the 20 SPs per hexside.

Example: If a one-hex Force contains three units of 7 Strength Points each, attacking another one hex Force, it commits 14 Strength Points to the combat. b) If attacking or defending across a defile, such as a primary bridge or mountain pass, all units in excess of 9 Strength Points (see “Defile,” ¶325). c) Any other units the owning player chooses to place in reserve. Having a certain minimum number of units in Reserve gives the player freedom to choose any battle type (see ¶327) and Reserve units have a limited mobility (see ¶324).

[318.] A Force adjacent to a Force Leader that can command it can be considered part of that Force and can be marked as Reserve even if it is not adjacent to an enemy force at that moment.

Function of Reserve Units

[319.] Units in Reserve may not add their combat strength to attack or defense until committed to the battle. Exact Strength of Reserves is not declared during Step 6 and Step 14 of the Combat Routine, but Reserve Strength is included in approximate strength (Step 3a) and in Step 4.

[320.] Reserve units may participate in Pursuits; a force made up entirely of Reserve units receives the same modifier as a French Guard force (see ¶390.2), and they ignore the modifier for lost battle rounds (¶390.3).

[321.] Reserve units in a hex under attack only lose SPs if the committed units in the hex are destroyed. In this case all reserve units are not longer considered in Reserve. When units or leaders lose Reserve status, this status cannot be regained later. Forces or units not marked as Reserve at the start of a battle can’t gain Reserve status later in that battle.

Commitment of Reserves

[322.] New units may be committed from the reserve, by removing their Reserve marker, to return committed strength up to the maximum number of strength points allowed as described in “Entering the Reserve,” above. Reserve units designated by the player have their marker removed and are automatically committed.

[323.] Reserves can be committed in Steps 1 (attacker), 12 (counter attacker), 2 and 13 (defender). Units in Reserve can only be committed in the hex their leader occupies.

[324.] A Force in Reserve can be committed in the same hex (without an initiative roll) or it may move one hex provided it makes a successful initiative roll (see ¶237), and it doesn't cross or enter into prohibited terrain. The Resistance Modifier will apply only if the force moves one hex and exits an EZOC (see ¶196). It may exit the ZOC of one enemy force to enter the ZOC of a different enemy force. It may not move from one EZOC to another of the same force - if it moves it must first withdraw from a ZOC. The move could be used to disengage a force in Reserve from EZOCs altogether. This move of one hex takes place after the resolution of other combats within 8 hexes (see ¶301).

Defile

[325.] When attacking or defending at a defile, the total committed may never exceed 9 Strength Points at one time. A Defile is a narrow crossing, including primary bridges and mountain hexes. A mountain hex containing a road is considered a defile.

Staking the Old Guard

[326.] If the Reserve Rules are used, the Guard are considered “Staked” if and only if they emerge from the reserve.

(Step 3b) SELECT BATTLE TYPE Reserve and Battle Type Selection

[327.] A Force may freely choose a Battle Type during Step 3 of any round only if it meets the minimum Reserve strength criteria below. If it does not meet the criteria, it automatically selects a Pursuit Battle. The Phasing Player may never choose Rearguard Battle. Otherwise a Force may freely choose Refuse, Rearguard or Pitched Battle type if: a) it has at least one quarter of its total strength (including artillery) in Reserve, or 8 Strength Points, whichever is less; or b) it occupies any kind of town or Fortification.

Restrictions on Pursuit Battle Selection

[328.] A besieged Force attacking out of a Citadel hex may not choose a Pursuit Battle.

Restrictions on Pitched Battle Selection

[329.] The attacker may never choose Pitched Battle if attacking across a bridged Primary River Hexside. Major Generals with an Initiative Rating of one (1) may never choose Pitched unless in a Town, City or Fortification (see ¶216). A Vedette may not choose to fight a Pitched Battle.

Leader Initiative & Pitched Battle

[330.] A Force Leader may only reveal the Pitched marker for a number of Combat rounds equal to his Initiative. For example, a Force Leader with an Initiative Rating of two (2) may only reveal Pitched twice for any given battle. Remember, the choice of the Battle marker is only revealed the first time in a round that a Player loses a combat (receives a bold face result on the CRT). A Leader losing both the attack and counterattack in the same round has revealed only once, while a Leader winning both does not reveal at all. If more than one Force is defending, use the rating of the best defending Leader.

Exception: Forces in Towns, Redoubts, Centers and Cities may always choose the Pitched marker regardless of the Force Leader’s Initiative. If using the optional Rearguard battle type, the combined total of Pitched and Rearguard battle markers chosen may not exceed the Initiative Rating of the Leader.

Refuse Battle Type

[331.] Often, a Leader might choose not to attack on some part of the battlefield during a round. A “Refuse” is a special type of Pitched Battle which has no combat result. A Force may Refuse only if it would benefit from “Affecting” terrain and/or Woods if attacked. The Force must also meet the conditions for selecting Pitched Battle. A revealed Refuse chit is treated as a regular Pitched Battle chit, except that the revealing Force is not required to attack or counterattack. A revealed Refuse chit does not count as a Pitched Battle choice against the number of times a Leader can select Pitched Battle.

If Attacker Refuses

[332.] If you Refuse during your attack or counterattack, you automatically become the loser for that attack. No die is rolled. A Refusing Force skips its half of the Battle Round - it makes no attack. A Refusing Force remains in the EZOC. The battle then continues with the other player’s attack or counterattack (who could also Refuse). If the defender counterattacks, there is still an Artillery Bombardment (Step 5) before Step 12.

Restrictions on Choice of Refuse Battle Type

[333.] Attacker cannot Refuse on the first round. If there are three consecutive half-rounds (e.g., attack–counterattack–attack) the Battle is over. Forces remain in contact and they are subject to ZOC rules and provisions (see ¶232).

If Defender Refuses

[334.] If your opponent is attacking (or counterattacking), and you lose, your revealed Refuse chit is treated as a regular Pitched Battle chit for all purposes.

Rearguard Battle Type (Optional)

[335.] Rearguard battle type allows the selecting player (only) to implement his (losing) combat result partially in hexes retreated, and partially in Strength Points lost. The exact proportions are up to him, but the first loss must be taken as a one hex retreat.

[336.] Not used.

THE SOUND OF THE GUNS (Step 3, Optional)

[337.] It was customary in written orders to specify that a force should maneuver toward the sound of the guns. Generals would ride out from headquarters until within earshot of cannon fire - sometimes with ear to the ground - and would be able to determine from listening what was happening. The maximum distance the sound could carry, except in really large bombardments, seems to have been about ten miles.

[338.] This rule can be used only by a Force belonging to the Non-Phasing Player that did not make a Force March during previous friendly Forced March Segment and that began the Combat Phase within five hexes of an Enemy Force about to attack a Friendly Force.

[339.] Such a Force may attempt to Force March again before the commencement of the second and each succeeding Round of Pitched Battle (see ¶192). If the force makes a successful Initiative die roll, it may expend one MP per round of combat including the current round. It must march “to the sound of the guns” - directly to the battle only. The Force must check for attrition before joining the battle.

(Step 4 only) CAVALRY DIFFERENTIAL

[340.] A Cavalry differential of two-to-one or greater will subtract one from the Bombardment die roll on the Artillery Fire Table. The cavalry must be part of the same Force as the Bombarding Artillery. The bombarding Force must have at least two SPs of cavalry to receive this benefit. Cavalry superiority means nothing during combat if your Force has no artillery. (It may, however, modify the Initiative Comparison Matrix result - see ¶198.) The cavalry differential does not apply when the defender is in a Fortification (see ¶216).

(Steps 5, 7, and 9) WEATHER EFFECTS ON COMBAT

Fair & Heat

[341.] No effects.

Frost

[342.] No effects.

1805: During Frost, forces may retreat after combat across Primary Rivers and Lakes. The force is treated as retreating across a secondary river (see ¶373). Forces may never attack across—and ZOCs do not extend across—frozen Primary Rivers or Lakes.

Rain

[343.] Add one to all artillery die rolls. Add one to the Resistance Modifier in Pursuit.

Mud (Rain/Mud)

[344.] Add two to all artillery die rolls.

Snow

[345.] Add one to all combat die rolls, including Artillery Fire. Add one to the Resistance Modifier in Pursuit.

(Step 5 only) ARTILLERY BOMBARDMENT

[347.] This step is executed by each Player for each round of Battle. The effect of Artillery is to eliminate SPs before the calculation of combat odds. Cavalry differential may affect the Artillery die roll (see ¶340). Artillery units never suffer losses from Artillery bombardment unless there is no other unit type in the target hex. An artillery unit in Reserve may not fire. Modifier: If there are 30 SPs or more in the target hex, -1; if 40 or more , -2 to die. (Modifiers are per hex, not per Force, and Reserves are counted as part of the strength.)

Terrain Effects on Bombardment

[348.] Artillery fire is blocked if a crest or all-woods hexside is between the bombarding unit and target Force. Artillery in a woods hex may not bombard; a target unit in a woods hex may not be bombarded. Artillery may not bombard defenders in Citadel hexes. Add 1 to the die roll if the defender is in a mountain hex.

Batteries Forward (Optional)

[349.] Players may choose to move their artillery into the front rank before resolving Artillery Bombardment. Resolve the fire of any unit moved forward at double its normal strength, but then inflict half the losses (round down) from bombardment and regular combat on any such units. There is no material way of signifying the artillery is deployed forward. The decision to deploy forward is made freely each time the Artillery Fire Step is reached. The player may always forego the strength doubling in order to prevent further artillery losses.

(Step 6 and 14) ODDS DETERMINATION ON THE CRT

[350.] An SP comparison is expressed as a ratio between the modified attacking and defending SP totals (the attacker’s strength divided by the defender’s strength) and is rounded down to one of the odds ratios shown on the Combat Results Table (CRT). Example: Thirteen SPs attacking five SPs would be 2.6 to 1. Rounding this down in favor of the defender would simplify the ratio to a 2 to 1 on the CRT. You may never voluntarily reduce combat odds.

[351.] The same CRT is used for Pitched and Pursuit battles. At odds less than 1 to 5 add one to the die roll for each ratio less than 1 to 5. At odds greater than 6 to 1 subtract one from the die roll for each ratio greater than 6 to 1. No die roll result, however, can be greater than 6 or less than zero. Check for shifts due to units being in Forage Mode (see ¶281), attacks following an unsuccessful Repulse (see ¶243), and any other modifiers mentioned in the Exclusive Rules. 1805: Shift one column left if a Besieged Force attacks the Force besieging it.

Artillery SPs and Combat Odds

[352.] Artillery is never included when determining the actual combat odds. If the defending Force is composed completely of Artillery SPs it may still bombard as an artillery Force but must defend as one SP of infantry. It may never Pursue. It may never enter an EZOC unless part of a mixed Force, with cavalry and/or infantry. Artillery does not take losses from Pitched Battle unless defending alone in a hex.

AFFECTING TERRAIN

[353.] Some types of terrain affect the Combat odds column on the CRT. This terrain is known as Affecting Terrain. When attacking into an Affecting Terrain hex, or across any type of river hexside, the Combat odds are located on the Affecting Terrain line at the top of the Combat Results Table. There is no cumulative benefit for hex and hexside Affecting Terrain.

[354.] If a Force attacks two or more hexes at once, and at least one of defending hexes is Affecting Terrain, then the attack must be made as if all the defenders were in Affecting Terrain.

[355.] The Terrain Effects Chart states which terrain affects Combat. In general, the following is considered Affecting: Units defending across all Bridges and Secondary River hexsides; in all City, Depot, Primary Town, and Fortification (see ¶216) hexes; in all Hill and Mountain hexes. Towns and Centers are not Affecting Terrain. (Villages have no effect.) Vedettes cannot take advantage of the defensive benefits of a Fortification (see ¶216), but they do get applicable Town or Depot benefits.

Mountains

[356.] The total attack strength of a force attacking into a Mountain hex may not exceed nine Strength Points. When determining combat odds, disregard any strength in excess of nine points. Defending units in Mountain hexes receive the benefit for Affecting Terrain. If Pursuit is chosen, a force of up to 9 SPs may pursue. Cavalry units in Mountain hexes may not attack, even if the defending hex is a non-Mountain hex; there is no pursuit modifier for cavalry in Mountains. Cavalry may not attack into Mountain hexes.

Woods Effect on Combat

[357.] The strength of infantry units attacking into a Woods hex is reduced by one fourth and cavalry is reduced by one-half (round off to the nearest half point).

Swamp Effect on Combat

[359.] The Strength of units attacking into or out of a Swamp hex is halved (rounding fractions up). Cavalry Strength is halved when defending in, or attacking into or out of, Swamp hexes (rounding fractions up).

Fortifications

[360.] Units defending in a Fortification hex (see ¶216) have their Combat Strengths doubled up to a certain maximum number of SPs, which varies by game. For example, a 3 SP Force in such a hex that allows a maximum of 5 SPs to be doubled would defend at 6 SPs, while a force of 8 SPs would defend at 13 (5*2 + 3).

1805: The first 15 SPs are doubled in a Citadel hex.

Other Terrain Effects

[361.] Other types of terrain affect Combat in the manner described on the Terrain Effects Chart (TEC). For purposes of combat, Terrain strength multipliers are not cumulative. The defender chooses which terrain effect will apply, as shown on the TEC.

(Step 7 and 15) ATTACK RESOLUTION Staking the Old Guard

[362.] The Combat Strength of the Old Guard may always be included in an attacking Force without special considerations. However, the French Player may “stake” the Guard, which means that he is staking the outcome of the attack on the reputation of the Old Guard, by featuring the Old Guard troops prominently in his attacking Force.

[363.] During any combat round the French Player may state that he is “staking the Old Guard,” as long as one point of Old Guard Infantry is in the attacking Force. Staking the Old Guard will modify the French Player’s attacking, or counterattacking, die roll by minus one (-1) in addition to other modifiers.

[364.] The Old Guard must take the first SP of combat loss, and all losses taken by the French Force must be taken from the Old Guard (or Young Guard) that combat round. If there are insufficient Old or Young Guard SPs to absorb these losses, line units in the attacking Force must suffer double the remaining SP losses. A Pitched Battle when the Guard is staked is resolved as a Pursuit Battle and there is no progression into subsequent rounds for that combat (see also ¶397).

Leadership Bonus

[365.] The decision to add, subtract or ignore this bonus need not be made until seeing the actual die roll for the combat. Although this bonus may not be used for defense, it may be added to attack and counterattack (see ¶44 and ¶46).

[366.] Not used.

REMOVING LOSSES

[367.] Distribute losses in Strength Points suffered by a Force (by whatever cause) throughout the Combat Units in the Force as evenly as possible (see ¶145; exception: “Staking the Old Guard,” ¶364). The winning side is never required to lose more SPs than the losing side in a given Combat round (or Pursuit) if the losing side does not have sufficient SPs to account for its own losses and is eliminated. There is no adverse effect on an enemy force engaged in combat with a Vedette unless it is also a Vedette.

Vedettes Lost in Combat

[368.] A Vedette which is forced to retreat (due to Combat or Repulse) or suffers any combat strength loss on the CRT is removed from the map and placed on a Leader’s portrait on the Organization Display of the nearest Friendly Force within 9 MPs. During the Organization Segment of the next Friendly Player-Turn it is stacked on the game map with the nearest friendly Leader. If no such force exists within nine cavalry Movement Points it is removed to the Vedette Pool.

(Step 8 and 16) RETREAT

[369.] When a combat result requires the Retreat of a Force, it must move the full number of hexes given. Note: Results are given in terms of hexes, not MPs. Count each hex as “one.”

[370.] The Path of Retreat is the path of hexes passed through by a Retreating Force. This path must conform to the Priorities of Retreat. Retreating Forces may not enter Prohibited Terrain or enemy occupied hexes. If the Path of Retreat is blocked by Prohibited Terrain or Enemy Forces, preventing the loser from retreating the full distance, the Retreating Force retreats as far as possible; if the enemy Pursuit is sufficient to carry them into the final hex of the Retreating Force, the entire Retreating Force is eliminated. Retreating Forces may not attempt Repulse during their retreat move.

Priorities of Retreat

[371.] The following retreat path priorities are given in descending order. This list governs all retreats due to Combat and Repulse. “Descending Priority” means that the lower numbered items should be observed first, and never broken to accommodate higher numbered items. Generally, after observing all of the following priorities, there will be only a few possible retreat destinations. 1) The Retreating Force must retreat the total number of hexes called for. It must end its movement this same number of hexes away from the hex in which it began its retreat. 2) The Force may not retreat into or through the same hex during any part of the retreat. No hex of the Path of Retreat may be adjacent to more than one hex already passed through by the retreating Force. 3) The path should not be through Friendly Forces. If this is not possible then the retreating Force will displace the Friendly Force with the smallest SP value (if there is more than one Force which could be displaced). The Displaced Force is moved one hex according to the Priorities of Retreat, and the Retreating Force now moves into the vacated hex. If Displacement is not possible because of blocking (prohibited) terrain, it may not take place. Displaced units may displace other Friendly Forces in a kind of chain reaction. Displacement may ruin subsequent attacks in that Combat Phase (the Phasing Player should keep this in mind when resolving his attacks). If the Retreating Force must displace the Displaced Force again or another Friendly Forced for its next hex of retreat, the process is repeated. Retreat and Displacement are carried out hex by hex. 4) This path may include enemy controlled hexes if necessary, but must include the fewest possible. Inflict double the usual losses on the losing side, even if there is no Pursuit. 5) Retreats must be made towards the active Friendly Supply Source, and must shorten the distance (in MPs) between the Retreating Force and the Friendly Supply Source as much as possible.

Although retreat is given in terms of hexes, if two or more paths are open to the Retreating Force, then it must move on the one that would cost the least MPs during normal movement.

Retreat of a Multi-Hex Force

[372.] Leaders in the same hex always retreat together. Subordinate Leaders may not be dropped off in the Path of Retreat. The various Leaders in a Multi-Hex Force may not retreat in different directions; they must end their retreat adjacent. The path taken by a retreating Multi-Hex Force is that of the Force Leader; Subordinate Leader paths are not important; Pursuit will follow that of the Force Leader. Retreat of a Multi-Hex Force is similar to Movement of a Multi-Hex Force in that all the Leaders begin and end their retreat adjacent.

Retreat Across Rivers

[373.] A Force which retreats across a bridge primary river or an unbridged secondary river after combat loses double its normal pursuit loss (as though it were retreating through an EZOC) if the Pursuit goes at least as far as the hex adjacent to the river hexside. (All the artillery are eliminated.) Artillery may not retreat across unbridged secondary rivers. If a loss is already doubled due to retreat through EZOC, there is no further loss due to the river. Retreat across Primary Rivers is allowed only at bridges.

Retreat Off the Map

[374.] A Force may retreat off the map if there is no other alternative Path of Retreat. If a Pursuing Force Pursues up to the last map edge hex, the Force(s) that retreated off the map are removed from the game and are captured (eliminated). Forces eliminated in such a manner do count towards a Critical Battle (see ¶395).

[375.] A Force may be moved off the map during a retreat after combat if permitted by the priorities of retreat (see ¶371). Pursuit of such retreating Forces must end at the map edge hex. A Force may not retreat off the map if it can retreat through an EZOC or displace a Friendly unit instead.

[376.] The Force reenters the map in its following Movement Phase at the nearest map edge hex unblocked by enemy units or EZOCs, in the same manner as Reinforcements. A Force must reenter the map as near as possible to its point of exit, and closer to the nearest Friendly Supply Source if possible.

Retreat into Fortifications

[377.] Forces may end their retreat in a Friendly-occupied Fortification (see ¶216) or Friendly Supply Source without displacing their Garrisons, as long as the stacking limit is not violated. They may do this regardless of the remaining retreat distance, but if their stopping would violate the stacking limit, they must continue their retreat. Pursuing Forces may not Pursue into hexes with enemy Garrisons (see ¶393).

Unengaged Adjacent Forces

[378.] If the Attacker has additional Forces adjacent to the Defending Force which are not engaged with any other enemy Force, they must suffer any retreat sustained by the Attacking Force. They do not take SP losses from Battle or Pursuit.

Vedettes and Enemy Retreats and Pursuits

[379.] Neither Vedettes nor their Zones of Control interfere with the ability of enemy units to retreat or pursue during the Combat Phase. Units may always ignore a Vedette when retreating or pursuing. If there is no other alternative, units may retreat or pursue through a hex occupied solely by enemy Vedettes. (In this case the enemy player has to reveal the Vedette-only hexes that may be retreated through.) The Vedettes are displaced (see “Priorities of Retreat,” ¶371.3) or eliminated if unable to displace. A Vedette by itself may not conduct a pursuit. There is no pursuit of a Vedette eliminated in combat.

(Step 9 and 17) PURSUIT

[380.] The entire winning Force, or a Subordinate Leader of this Force, may Pursue the losing Force along its Path of Retreat. The Pursuing Force must stay on this path but may stop at any hex without being required to Pursue the full distance specified on the Pursuit Table. If the Force Leader Pursues then Subordinate Leaders may be dropped off along this path as in Movement.

Exception: If the winning Force selected Rearguard, it may not Pursue.

[381.] A Force may pursue into an EZOC but not directly from one EZOC to another (ignore any ZOCs into the first hex, which was vacated by the retreating Force, as well as the ZOCs of any Forces repulsed in the pursuit).

[382.] The retreating Force loses one SP for every hex of Pursuit. If the losing Force retreated the full specified distance then the winning Force may not Pursue into the hex occupied by the losing Force under any circumstances. If the length of Pursuit is indicated to be greater than the required length of retreat, the winning Force stops in the hex adjacent to the losing Force. The losing Force then loses one extra SP for every extra hex of Pursuit not allowed to the winning Force (this is doubled if the losing Force passed through EZOCs).

[383.] If the losing Force did not retreat the full specified distance, and the winning Force has a sufficient length of Pursuit to allow it to enter the hex of the losing Force, then the Pursuing Force may enter the hex with the Retreating Force. The Retreating Force in this case is eliminated and the Pursuing Force ends its Pursuit in that hex. Even though the Pursuit Table calls for a greater Pursuit, the retreating Force cannot be pursued beyond the hex in which it is eliminated.

[384.] A Force may not Pursue farther than the number of hexes indicated by its Length of Pursuit on the Pursuit Table. Pursuit is carried out immediately after Retreat, before any other attacks are resolved.

[385.] The Retreating Force’s losses are equal to the actual length of Pursuit but must be at least equal to the losses taken by the Pursuing side. The Artillery units in a Force are the first to take losses due to pursuit.

Which Forces May Pursue

[386.] A Force is never required to Pursue. After Pursuing, the winning Force may not attack again that Phase, even if its advance brings it adjacent to attacks that are yet to be resolved. The entire winning Force may Pursue, except that Artillery may never be included in a Pursuing Force.

[387.] A Pursuing Force may consist of any part of the winning Force as long as it has a Leader capable of commanding the units in the Pursuit. In other words, a new Force may be defined from the winning side at the instant of Pursuit. Remember that Major Generals may only be created during the Command Phase and must be already present in the battle if they are to lead a Pursuing Force or take command of artillery.

Multi-Force Pursuit

[388.] In the event of two non-adjacent enemy Forces losing a battle to a single Force, both Forces may be Pursued if there are sufficient Leaders in the winning Force to create two Pursuing Forces. Each separate force suffers its own losses. If either is unpursued, it suffers on the minimum losses.

How to Use the Pursuit Table

[389.] After the winning side has deducted its combat losses, refer to the Initiative Comparison Matrix for the Resistance Modifier. Then go to the Pursuit Table. Cross-reference the unmodified Initiative of the Pursuing Leader with the Length of Retreat (given as a Combat Result). The result of the modified die roll is the Length of permissible Pursuit.

Modifiers to the Pursuit Die Roll [390.]

The Resistance Modifier (see ¶391.). 2) A Pursuing Force composed exclusively of French Guard units or units released from Reserve (-1). (A French Guard unit released from Reserve gets the modifier only once.) 3) A Force must add to its Pursuit die roll the number of times in that Battle which it revealed Pitched.

Resistance Modifier

[391.] Consult the Initiative Comparison Matrix to determine the Resistance Modifier for the Pursuing Force (considering the winning Force to have the active Leader). Cross reference the Length of Retreat with the pursuing Leader’s Initiative Rating. Modify the Pursuit Table die roll by the resulting Resistance Modifier. (See also “Cavalry Differential Initiative Modifier,” ¶198.)

Maximum Pursuit

[392.] Regardless of the Length of Pursuit indicated on the Pursuit table, a Pursuing Force may not Pursue a distance greater than its SPs. Example: In order to Pursue eight hexes, a Pursuing Force must consist of at least eight SPs.

Pursuit to a Fortification

[393.] A Force may not Pursue into an enemy-occupied or enemy-garrisoned Fortification (see ¶216) or Supply Source. It must end the Pursuit in the first hex adjacent to the hex. Losing Forces may retreat into a Friendly-occupied Fortification hex without displacing any Force therein (see “Retreat into Fortifications,” ¶377).

Pursuit and Optional Rearguard Battle Type

[394.] The subsequent Pursuit may cause further loss of Strength Points. When determining the Pursuit, the active player uses only the portion of the combat result executed as “hexes retreated” to cross reference with his pursuit die roll. (He may voluntarily shorten the pursuit.) If at the conclusion of the pursuit the two Forces are adjacent, another round of battle ensues (see “Pitched Battle,” ¶399).

(Step 10 or 18) ADJUST MORALE Critical Battles

[395.] A battle may move the Morale Level Marker one space if it meets the criteria below: Determine the losses in SPs for both sides after any Battle (including Pursuit losses). If the Losing Force lost more than seven (7) SPs, the winning Player (non-bold result) rolls a die. If the die roll is less than or equal to the differential in SPs lost by both sides, the winning Player adjusts the Morale Track one space in his favor.

Commentary: These changes are necessary because of the smaller forces involved in these campaigns.

Example: If the Losing Force lost 10 SPs and the non-retreating Force lost 7 SPs then the differential would be three (3). The winning Player would then have to roll a 3 or less on the die for this to be a Critical Battle. If the Retreating Force did not lose more than seven (7) SPs, or if the non-retreating Force lost the most SPs, there is no change to the Morale.

Capture of a Major Personality

[396.] A Leader with a Command Span of six (6) or greater, or with a Bonus Point, is a Major Personality. The moment a Major Personality is captured, adjust Morale one space against the owning side.

Exception: If Napoleon is ever captured, the game may either end as an Operational Victory for the Coalition or Morale is adjusted two spaces in the Coalition’s favor according to the Coalition Player’s choice. A player May NOT avoid their capture and loss of morale by, for instance, making a “6” span leader unemployed and turning everything over to a “5.”

Defeat of the Old Guard

[397.] At the end of any Combat Phase where the Guard was staked and failed to win the Combat round, Morale is moved one space toward a Coalition Victory. Regardless of the number of battles in which the French Guard were staked and lost in a single Combat Phase, the Morale Track is only moved one space in any one Game-Turn because of the Guard’s defeat. The French Guard winning a combat round does not affect the Morale Track.

[398.] Not used.

(Step 11 and 19) PITCHED BATTLE

[399.] One complete round of Pitched Battle includes one attack and one counterattack. Players may only change the type of battle marker selected at the beginning of a round of Pitched Battle; i.e., after counterattack.

[400.] If the losing Force (the bold face result) revealed Pitched Battle, no retreat occurs and the Combat Result is the number of SPs lost by both sides (Exceptions: ¶316, ¶358, and Override, below). If the phasing player loses his first attack, the defender may - after the first attack only – “override” a phasing Pitched Battle chit, if he selected Pursuit or Rearguard (see ¶335.) In a “Pursuit Override,” the winning side takes its loss as a retreat and the loser may attempt to pursue, taking his combat result as SP losses. The override only applies when the opponent revealed Pitched battle.

[401.] In a Pitched Battle, the non-Phasing Player immediately counterattacks with as many of the survivors as can constitute a single Force. This attack is made against at least the strongest hex of the enemy Force (in the event that the Phasing Player employed a Multi-Hex Force for his initial attack, see ¶300.13) from which the attack was initiated. A force does not have to counter-attack if not in an EZOC, or across a primary river hexside from the enemy. A Force in a Fortified Town, Redoubt (when attacked solely across Redoubt hexsides), or Capital City, or a besieging force in combat with a force in the Citadel, does not have to counterattack or re-attack.

[402.] The counterattacker may attack with as many units as allowed by ¶262 step 13. The results of a counterattack only affect the actual hex, or hexes, being counterattacked.

[403.] Subordinate Leaders in a counterattacking Multi-Hex Force may divide their attacks between separate hexes from among the initial attackers. In other words, a Multi-Hex Force may resolve its counterattack against a Multi-Hex Force as separate attacks as long as no hex receives more than one counterattack in this round and as long as every part of the defending Force counterattacks (remember that a Force is constituted the instant of Combat).

[404.] At the end of a counterattack, even if one was not executed due to terrain (see ¶401), if Forces involved in the counterattack are still adjacent to the Force which initiated the original attack, then the Phasing Player is obliged to launch a re-attack (a new round of battle). Before doing this, the first round of any concurrent Pitched Battles must first be resolved (see ¶406).

[405.] To commence Round Two, both Players select a new Battle Marker which will apply to the result of the upcoming reattack. This sequence of attack, counterattack, re-attack and counterattack will continue as long as the losing side reveals Pitched Battle. As soon as a losing side reveals a Pursuit marker, the battle is resolved as a Pursuit battle. The maximum number of Rounds of revealed Pitched Battle per side in a given combat is limited to the Initiative Rating of the Force Leader (see ¶330). Once a force has revealed Pitched Battle the maximum number of times permitted, it must choose Pursuit on succeeding Rounds.

Concurrent Pitched Battles

[406.] If more than one battle is going to be resolved, during the same phase, within 8 hexes of any hex in combat, resolve all Round One attacks and counterattacks before going on to Round Two, etc. Use the markers provided to denote the current round of combat.

Minimum Combat Losses

[407.] The Losing side always loses at least as many SPs as the winning side (see ¶385). In a Pursuit Override, the retreating force that played the override is considered the losing force for minimum loss purposes.

Pitched Loss Greater than Total Force

[408.] If the losing Force has insufficient SPs to absorb the losses called for on the CRT, resolve the round as a Pursuit battle, regardless of the Battle marker. Example: A Force of six SPs plays Pitched in spite of the fact that it is attacked by 36 SPs. It then receives a Combat Result greater than it has SPs. Instead of taking the losses, the losing Force retreats that number of hexes. The victor may then Pursue.

(Step 1 or 12, Optional) BATTLEFIELD DYNAMICS

(Controlling the Battle)

[409.] In a Pitched or Rearguard Battle prior to each player’s counterattack (or reattack - i.e., before Step 12, or before Step 1 of the second round), the player about to attack rolls the die, modifying for Cavalry Differential. The phasing player does not roll prior to his initial first round attack. Snow cancels any positive modifier, and subtracts 2 from the die roll.

[410.] Explanation of Results

Retain control of the battle

If the modified die roll is less than his Force Leader’s Initiative, Player retains control of the battle. The player about to attack may select any of the three results that follow and implement at once.

No attack (remain in contact)

If the modified die roll equals the Leader’s Initiative, he may not attack (remaining in contact – see ¶331 “Refuse Battle Type”). Your forces remain in place. The Enemy may continue the pitched battle by attacking in a follow-up counterattack (or reattack), provided he has selected pitched battle.

Must counterattack (or re-attack)

If the modified die is greater than Initiative by one, he must counterattack (or re-attack). This is the regular way (as in Standard Rules)

Take a Retreat instead

If the modified die roll is greater than Initiative by two or more, take a Retreat instead of attacking. Based on the actual result of the immediately preceding combat resolution, there will be no pursuit if the enemy did not win.

Example: Napoleon (Initiative ‘5’) has 2000 cavalrymen and his enemy has 4000, (weather is fair). Cavalry Differential is +2 (= die roll mod). If his modified die roll is 3 or 4, he retains control of Battlefield Dynamics; if 5 he must Refuse; 6 he must Counterattack, 7 or 8 he must Retreat.

IV. MORALE AND VICTORY

[411.] Each game has a Morale Track. This track represents the will of the belligerent Nations and/or their armies to make and sustain war. Morale is affected by: 1) Critical battle (see ¶395) 2) Capture of a Major Personality (see ¶396) 3) Defeat of the French Old Guard (see ¶397) 4) Occupation of certain political features on the map such as cities (see ¶415).

Effects of Morale

[412.] The effects of Morale define the end of the game and who wins. Morale also modifies Attrition die rolls (see “Modifiers of the Attrition Die Roll,” ¶267).

IV.a. SURRENDERING OF CITADELS

[413.] A besieged Citadel will surrender if the combined number of SPs besieged is equal to or less than the indicated number and an Enemy Force is adjacent.

1805: A Citadel surrenders when the total of besieged SPs is 7 or less.

[414.] When a force occupying a Citadel surrenders, all surviving Strength Points are immediately eliminated; all Leaders are granted the “Honors of War” and become available as Replacement Leaders. Whenever a Citadel surrenders, besieging units of the victorious player may enter the hex.

IV.b. CAPTURE OF POLITICAL FEATURES

[415.] Political features and the way they affect morale are defined in the Exclusive Rulebook.

IV.c. STRATEGIC VICTORY

[416.] Levels of Victory are defined in the Exclusive Rules.

HOW TO SET-UP THE GAME

[417.] Select a scenario, and set-up according to the Leader Manifests and Unit Manifests. Sort out the counters by army and then into the following categories: Major Generals, the other Leaders, Vedettes, named Combat Units, March Regiments, Markers and other counters.

UNIT & LEADER MANIFESTS

[418.] The initial placement for the combat units and leaders is given on the Unit and Leader Manifests per scenario. Place all the units and leaders on their respective manifests before transferring the units to the Organization Displays, and the Leaders either to the Displays or to the map.

[419.] Combat units are listed on the Unit Manifests, grouped roughly by Corps or Column. Beneath the headings corresponding to the various scenario start dates you will see the leader whose track they set up on and their individual unit strengths. Combat units listed with a Leader’s name should be placed on that Leader’s track on the Organization Display to denote they are part of his Force. Set up the Vedettes – no more than 2 per real force (see ¶24).

[420.] Set up the Leaders on the Leader Manifest. A Force consists of one Leader on the map and at least one Combat Unit on that Leader’s track on the Organization Display. More than one Leader may be in a Force but must be Subordinate to the Force Leader. Subordinate Leaders go on the Force Leader’s portrait on the Display. Set-up Reinforcement units and leaders on the Turn Record Track.

[421.] Review the notes on the manifests to determine which leaders and units may be unavailable or be replacements for the scenario being played. If marked as a replacement, the unit or leader in question does not begin in play in that scenario, but is available as a replacement. If a unit, it may be filled-up with Strength Points like a March Regiment. If marked as not available, the unit or leader is not available in that scenario.

ORGANIZATION DISPLAYS

[422.] Each army has its own Organization Display. Set it beside the map. Next to the Leader’s Name, his Initiative Rating, Command Span, and Subordination Value, are his Subordinate Units Track where Combat Units of his Force are placed during play. All combat strength and loss is tracked point-by-point.

[423.] Place the combat units on the numbered track spaces corresponding to their listed strength (see “Organization Displays,” ¶29) Leader manifests may specify the name of the Force Leader or a hex on the map. Place subordinate leaders (who have a Force Leader specified) on the Force Leader’s portrait to denote they are part of his force.

1805 Example: In Scenario III, Murat’s track contains Kellermann, Nansouty, d’Hautpoul, Walther and Milhaud (as shown on the French Unit Manifest). Murat’s leader counter goes on-map in hex 1923.

Units with Both Infantry and Cavalry Components

[424.] Many units had both infantry and cavalry. A separate counter is used to track the strength of each type. The two counters may never be placed on two different tracks: they comprise a unitary formation. When cavalry from a mixed unit is in play but the corresponding infantry unit is not, place the infantry unit counter on the same leader’s track as if it were a subordinate so that the combined cost is the same even though the infantry unit is not in play.

[425.] Cavalry strength is shown in some games by a “c” above the name of the Leader’s name upon whose track the unit is place. If the unit has no cavalry strength at start, place the Cavalry Marker in the “Zero” space: Cavalry replacements may be used to add strength to the unit’s Cavalry Marker.

[426.] The cavalry constituent of one of these units can only be assigned to a Cavalry Major General if its infantry counterpart is eliminated. Its strength might be transferred to another unit.

Major Generals

[427.] Combat units that have separate set-up hexes use Major Generals as their Leaders. Use the Major General of the appropriate type (infantry or cavalry) and designation.

1805 Example: In Scenario II, Bourcier sets-up on the track of Major General Cavalry 1, in hex 3439 (as specified on the French Leader and unit Manifests).

Mixture of Coalition Forces

[428.] In games with different nationalities of Coalition leaders, Russian or Austrian Leaders may have Prussian units on their tracks and vice versa. However, no more than one unit on a Leader’s track may be of a different nationality than the Leader.

[429.] During set-up, units may be switched from one Leader to another in the same hex if necessary to accommodate Command Spans.

SECOND PLAYER’S PRE-GAME FORCED MARCH

[430.] The positions of both forces in the set-ups are approximately correct to the same day, while in fact the opposing forces ought to be able to encounter each other in a meeting engagement at an intermediate location.

GENERAL RULE:

[431.] In every Scenario the Second Player has a Forced March Phase which immediately precedes the First Player-Turn of the Scenario. All Force March restrictions and conditions apply during this pre-game Forced March Phase, including attrition.

1805: Do not use this rule in The Sun of Austerlitz.

PROCEDURE:

[432.] During the pre-game F.M. Phase, the Second Player has the option of attempting to move, by Initiative only, any of his forces up to two Movement Points. Consider the weather to be Fair unless indicated otherwised in the Exclusive rules.

[433.] All of the Second Player’s Forces have the same Pre-Game Forced March Limit of 2 Movement Points.

Campaigns of Napoleon Solitaire System

Intent

This system is designed to enable someone to play any of the Campaigns of Napoleon games in solitaire mode with the Vedettes. The rules are intended to bring a bit of uncertainty to playing solitaire and offer a rationale for using basic Napoleonic screening and support march formations. Parts of these rules could be open to interpretation, so players are advised to follow the spirit of the rules if questions arise.

Rules:

(1) All units are played face up and visible. When a non-moving force (hereafter known as the contact force) that has no enemy force in its ZOC or adjacent to it has a moving force (normal or force march) enter its ZOC (flexible or regular), the moving force determines whether the contact force is actually in the hex or whether a nearby friendly force (hereafter known as the supporting force) should be substituted for it. This is known as “fixing” a force’s location.

Note: When a moving force is force marching and attempts a repulse, the “fixing” procedure is used exactly as it would be used for a moving force using a Movment Command or Initiative.

(2) The results of “fixing” a force’s location are either a) the contact force is really at that location or b) another nearby support force is substituted for the contact force. Once a force’s location has been “fixed” it cannot be substituted for another force while it remains adjacent to an enemy force, whether it is or is not in an enemy ZOC, because the force’s position has been “fixed” to that location.

(3) Procedure for “fixing” a force’s location: The player rolls a die. On a die roll of: 1-3 = The contact force remains in place; continue the phase. 4-6 = The contact force is switched with a support force that is within 10 hexes (1x series), 5 hexes (2x series), or 3 hexes (5x series) of its location. Garrison units, Bridge Trains, units under siege, or Centers of Operation do not constitute forces for this purpose.

Die Roll Modifiers:

If the moving force contains a cavalry SP or a Vedette and the contact force does not contain a cavalry SP or a Vedette, subtract 2 from the die roll.
If both the moving force and the contact force contain a cavalry SP or Vedette, the side with more cavalry/Vedette strength points subtracts 1 (moving force) or adds 1 (contact force) to the die roll. In case of ties, there is no die roll modifier.
If the contact force contains a cavalry strength point or a Vedette and the moving force does not contain a cavalry strength point or a Vedette add 2 to the die roll.
If neither force contains any cavalry strength points or a Vedettes there is no die roll modifier.

(4) When a unit substitution is determined by the “fixing” die roll and there is more than one potential supporting force within range, determine the appropriate force randomly. To substitute a supporting force for a contact force physically switch the forces. If the force chosen for substitution is a multi-hex force, the entire force is arrayed in the new location with each component of the force placed in the ZOC of the moving force, if possible. If not possible, then the owning player may determine how to deploy the units. The contact force that originally generated the “fixing” procedure can be placed in any of the multi-force hexes or if it is itself a multi-hex force array it in the new location in a logical manner. If for any reason a series of factors conspire, such as terrain, to make the substitution illegal, either choose another force or do something reasonable. If no substitution forces are within range the force the original contact force is “fixed” in its original hex.

(5) After all movement and “fixing” of forces is complete, execute the combat phase normally.

Part 2: The Sun of Austerlitz [1805] Exclusive Rules (Revised, Consolidated)

Napoleon's Campaign in Moravia, 1805. These rules are designed to be used with the Campaigns of Napoleon 1X Consolidated Rules.

INTRODUCTION

[E1.] The Sun of Austerlitz simulates the decisive conclusion to Napoleon Bonaparte’s First Danube campaign. After a brilliant maneuver against the Austrians at Ulm, Napoleon entered Vienna on the 13th of November, 1805. The Austrian Emperor Franz I refused the French offers of peace, as fresh Russian forces arrived in Moravia to support the Austro-Russian survivors of the retreat.

[E2.] The counter sheet in this package also includes 92 expansion counters and a sheet describing their use for OSG’s La Guerre de l’Empereur game, neither of which is used when playing The Sun of Austerlitz.

[E3.] This Exclusive Rules folder contains rules particular to The Sun of Austerlitz, which is a part of the Campaigns of Napoleon Series 1X. These rules have been designed to be used with the Campaigns of Napoleon 1X Consolidated Rules, and unless otherwise stated, all the Consolidated Rules apply. Exclusive Rules either add to or modify the Consolidated Rules.

GAME EQUIPMENT

[E4.] This revised version of The Sun of Austerlitz requires the following components:

This revised Exclusive Rules booklet
The 1805 Exclusive Tables
The Campaigns of Napoleon 1X Consolidated Rules
The Common Tables for the series
One Game Map, 22" x 34"
One sheet of die-cut counters (280)
Sequence of Play/Example of Play Sheet 8.5" x 11"
Austro-Russian Organization Display 8.5" x 14"
French Organization Display 8.5" x 11"
Austro-Russian Leader & Unit Manifest 8.5" x 17"
French Leader & Unit Manifest 8.5" x 17"
Turn and Record Tracks 11" x 17"

Game Map

[E5.] The Game Map shows the fertile valley of Moravia, with its capital at Brünn. Bohemia lies to the west, Hungary begins east of the March River, Silesia lies some 50 km off the north edge, and the southernmost quarter of the map is Lower Austria. In 1805 the entire area was part of the Austro-Hungarian Empire and most of the towns were referred to in official dispatches and historical accounts by their German names. Partial hexes on the south map edge (1054 and 2854) are in play. French forces (only) may occupy them if convenient. Also ignore Posoritz P.O.

[E6.] The diagram below shows the location of the Sun of Austerlitz map in relation to the eastern section of Victory Games’ edition of 1809 in this same series.

Counters

[E7.] French units are sky blue, (the French Imperial Guard is dark blue with yellow values); Austrian units are white (with ochre stripe); Russian units are earthen brown; Prussian units are steel gray.

[E8.] The following Austrian and Russian Leaders have their own eponymous combat units: Austrians Kienmayer and Kolowrat; Russians Docturov, Przybyszewski, and Bagration. Each of these leaders must have his own combat unit on his track (as long as his leader and combat unit counters remain in play). The above leaders can be brought into play and removed from play like Major Generals, but each may only enter the map in the hex with his combat unit.

Example 1: There is one combat unit counter for the Russian I Column, and one leader counter for General Docturov, who commanded that column. If the Leader Docturov is in play, he must command his own I Column—with his combat unit counter always on his track on the Organization Display—as well as other units up to the limit of his Command Span. The Leader Docturov has a command Span of 5. His own combat unit has a Subordination Rating of 2; in addition he could also command Przybyszewski’s combat unit [2] and Kamensky’s combat unit [1]. The total of these three units under command being 5, he could command nothing further.

GAME SPECIFIC RULES

II.b.2 EXTENDED MARCH EXAMPLE

Davout’s March north from Vienna.

[E9.] Davout leads a French Force initially comprising 8 SPs of Friant’s and Viallanes’ units (later adding Bourcier’s unit en route) and uses his leader bonus.

29-30 November. Vienna to Musoff. 9:30 PM, 29 November: Departed from Vienna. With 7 APs and 8 SPs, the Force will use the 3rd line in the body of the chart to find its attrition loss. Forced March 5 MPs to 2946. The first die is a 6 + 4 (F.M. mod.) -1 (Leader) = 9— Loss of 2 SPs.

French Movement Phase

Now the force strength is 6, so the 2nd line is used. Using Extended March costs 2 APs: March Distance is 9 MPs to 2231. The 2nd die is a 2 + 4 (Extended) -1 (Leader) = 5—Loss of 1 SP. Picked up Bourcier’s cavalry division (2 SPs) in Nikolsburg, Nov 30th pm.

1-2 December. Musoff to Sokolnitz. (With Bourcier’s addition the Force strength is back up to 7, again the 2nd line is used). FM 4 MPs to 1926. The 3rd die is a 4 + 4 (F.M. modifier) -1 (Leader) = 7—Loss of 1 SP. Arrived Gr. Raigern, 7 PM, 1 Dec.

French Movement Phase

Departed at 5:30 AM, strength 6—arrived hex 2024, 10 AM, 2 Dec. March 3 MPs. The 4th die is a 6 - 1 (Leader) = 5—No Loss. Total loss for the trip: 4 SPs.

IV. VIENNA MORALE

[E10.] The French occupied Vienna on November 11th 1805. However, the Imperial Court withdrew in time to unite with the Russian Armies. The term “Vienna Morale” in this sense refers to the Court of Vienna.

[E11.] Austro-Russian morale is recorded on the Vienna Morale Track. Morale may be positive, zero, or negative. If Vienna Morale is between +4 and -5 (exclusive) at the end of the last Game-Turn, the Level of Victory is determined by the Levels of Victory Chart (¶E44).

[E12.] At the start of each Scenario, place the Vienna Morale Marker on the zero space of the Track (see ¶E36); thereafter morale will change as defined in the Standard Rules and as below:

Capture of Political Features

[E13.] In addition to Morale Changes as outlined in the Standard Rules (¶197-99), Vienna Morale also changes by one for the capture of the depots listed below. To acquire the morale shift the player must succeed in entering a named leader with 4 infantry SPs or more into the depot. These effects are reversed if the depot is recaptured. The Austro-Russian Player cannot acquire these points in games starting on 15 November. • French Player captures Olmütz: Morale -1. • Austro-Russian captures Brünn: Morale +1. • Austro-Russian captures Pohrlitz: Morale +1.

Effects of Morale on Ending the Game

[E14.] At the end of any Game-Turn in which Vienna Morale is +4, the game is over and the Austro-Russian Player wins. At the end of any Game-Turn in which Morale is -5, the game is over and the French Player wins (see ¶E37).

Effects of Morale on Determining Victory

[E15.] Level of Victory depends upon the current Morale at the end of the Campaign Game (see ¶E37).

Negotiation Table

[E16.] At the end of each Game-Turn (provided no Austro-Russian Forces occupy Brünn at that moment), the French Player will roll two dice on the Negotiation Table. As long as no Austro-Russian Forces occupy Brünn at the end of a turn, the French Player must roll on the Negotiation Table until he receives an “Austro-Russian refusal” result. Upon occurrence of Austro-Russian refusal the French player must begin to roll on the Ultimatum Table (see ¶E18).

[E17.] If “Negotiation” results, there will be a temporary halt to all combat by both sides, of up to three turns duration. Both sides execute only their respective Administrative and Forced March Segments during the turns of negotiations. Attrition has to be determined each turn as usual. After the specified number of turns, regular play will resume. The French player must continue rolling on the Negotiation Table during and after Negotiations. However, Negotiations cannot occur more than once per game. (See the Negotiation Table.)

Ultimatum Table

[E18.] At the end of each turn after a result of “Refusal” (including the turn of Refusal) the French Player will roll on the Ultimatum Table. If "Prussian Ultimatum" results on this table, the definition of the Levels of Victory will change (see ¶E37). Two turns after the Prussian Ultimatum, the Prussian units arrive under the command of Leader Hohenlohe, on hex 1301, at maximum strength.

Effects of Vienna Morale on Attrition

[E19.] The Austro-Russian Player must always subtract the current Vienna Morale from the die roll when determining Attrition. If Morale is negative, subtracting a negative will result in a positive modifier (see ¶267). French Attrition die rolls are not affected by Vienna Morale.

CAMPAIGN SCENARIO INFORMATION

[E20.] With turns of active campaigning taking about 30 minutes to complete, two Players can complete the Campaign in 6-8 hours of playing time. A shortened Campaign Game can begin on 27-28 November (saving 3 hours). Set up time: 15 minutes.

First Player

[E21.] In all scenarios of The Sun of Austerlitz, the Austro-Russian Player is the First Player.

Game Start

[E22.] In The Sun of Austerlitz, the Campaign Game can start on 15-16 November or 27-28 November. Place the Game-Turn Marker on the Turn Record Track on the appropriate date.

Game Start: 15-16 November

The Manuever of Hollabrunn: Kutusov’s Army attempts to escape from Murat and unite with Buxhöwden’s supporting Army coming from the north-east.

Alternative Start Date: 27-28 November.

The Austro-Russian Advance: This scenario will generate a free-form set-up for the battle of Austerlitz (or perhaps the battle will be fought elsewhere). Both Players will have time to adjust their dispositions and pursue alternative strategies.

Scenario End Date

[E23.] The Campaign Scenario covers the period from 15 November 1805 through 16 December. The Campaign Scenario ends with 15-16 December 1805 (exception: see ¶E14) regardless of start date. Scenario End Date: 15-16 December This was the date at which 80,000 Austrian troops under Charles would have been able to intervene, either attacking Vienna or appearing on the map around hex 3942.

Administrative Point Levels

[E24.] The Accumulated AP Levels, specified for each side in each scenario, show where on the Accumulated AP Track to place the AP Level Markers (x1, x10) at the start of the scenario. Each player will use the Attrition Table column corresponding to the number of Accumulated APs.

Accumulated APs:

15-16 November: FRENCH 3, AUSTRO-RUSSIAN 10 27-28 November: FRENCH 4, AUSTRO-RUSSIAN 16

Special Rule: French First Turn Administration

[E25.] The French may not receive or spend any Administrative Points on 15-16 Nov. (see ¶96 and ¶168).

Supply Sources At Start

[E26.] Supply Sources may be freely chosen by the players in any hex listed for that army on the Communications Table. In the Campaign Game, S/S hexes are on the mapedge only. Once assigned, the S/S may only be changed as specified under ¶101, Changing the Supply Source.

Centers of Operations

[E27.] The Centers of Operations may be set-up freely at the owning player’s discretion.

[E28.] Both Centers of Operations are Active at the start of the Campaign Game. Note: the French Player receives no new APs and cannot create any Movement Commands on the 15-16 Nov. turn.

Citadels

[E29.] Brünn (Brno) and Olmütz (Olomouc) are the only two Citadel hexes on the map. Neither is considered to be under siege at the start of either scenario, and each starts under the control of the player who has a garrison in each (see ¶E30).

Garrisons

[E30.] At the start of each scenario, in addition to the Supply Source garrison, each player may place Garrison markers as specified below. They act like Supply Source garrisons (see ¶77). If Brünn or Olmütz are captured, the capturing player may create a garrison by deducting one SP from an infantry unit in the hex.

Garrisons:

15-16 November: Russian—Brünn, Olmütz. 27-28 November: French—Brünn, Russian—Olmütz.

Vedettes

[E31.] Vedettes can be placed at start according to the rules governing their placement (see ¶24).

Bridge Trains

[E32.] The Austro-Russian Player receives two bridge trains, one of which is assigned to Kutusov, and the other to Buxhöwden. The French Player receives one bridge train which he may place with any leader at the beginning of the scenario.

Reinforcements

[E33.] Any combat unit that is not in play at the start of the scenario and not marked ‘repl.’ may be introduced into play by the owning Player as a reinforcement unit—as specified on the Turn Record Track—during the Reinforcement Segment of the Movement Phase (see ¶152 and ¶154).

Special Rule: Napoleon’s Arrival

[E34.] 15-16 November: Napoleon with his Force and Bessieres's may advance their arrival to the Forced March Phase of Turn 1 if any enemy forces approach within 7 hexes of Floridsdorf (2854).

Special Rule: Gudin’s Arrival

[E35.] Gudin’s Division was sent for at the last minute. Roll the die on 29-30 November to determine the arrival of Gudin’s Division. (Klein’s cavalry will accompany Gudin as part of his force.)

Note: The Turn Record Track shows the “Historical” arrival of Gudin’s division. Unlike other reinforcements, the units of Davout’s III Corps arrive during the French Forced March Segment of the specified turn, and may automatically move their maximum Movement Allowance during the entry segment.

Die roll results:

| Die roll | Result |

|---|---|

| 1 | Gudin‘s Force arrives 1 turn earlier than shown. |

| 2-3 | Gudin‘s Force arrives historically. |

| 4-5 | Gudin‘s Force arrives one turn late. |

| 6 | Gudin‘s Force arrives two turns late. |

Vienna Morale

[E36.] The Vienna Morale Marker begins every scenario at “zero.”

Victory Conditions

[E37.] The Victory Conditions determine who wins the game. Automatic Victory: (see ¶E14)

Other Levels of Victory:

If no automatic victory condition is met prior to the end of the game, the level of Vienna Morale at the end of the game determines the Level of Victory. This depends upon whether the “Prussian Ultimatum” result has occurred or not (see ¶E18).

| Vienna Morale | With Ultimatum | Without Ultimatum |

|---|---|---|

| +3 | Aus.-Rus. Operational | Aus.-Rus. Tactical |

| +2 | Aus.-Rus. Operational | Aus.-Rus. Tactical |

| +1 | Aus.-Rus. Tactical | Aus.-Rus. Marginal |

| 0 | Aus.-Rus. Tactical | Aus.-Rus. Marginal |

| -1 | Aus.-Rus. Marginal | Fr. Marginal |

| -2 | Fr. Marginal | Fr. Tactical |

| -3 | Fr. Tactical | Fr. Tactical |

| -4 | Fr. Operational | Fr. Operational |

ERRATA & CLARIFICATIONS

EXAMPLE OF PLAY

The example still accurately reflects the flow of play. However, it contains a few errors regarding exact positions and exact strengths, so cannot be relied upon in every detail.

MAP

Klosterneuburg (2553), Straze (3995) and Kremsier (3411) are not practicable as depots since they are not on primary roads, unless a unit is in the same hex.

COUNTERS

Change the Subordination Rating of Essen I to 1.5.

MANIFESTS

Austro-Russian Unit Manifest, 27-28 Nov.: Kolowrat is under Leader Kolowrat (not Kutusov). French Leader Manifest, 27-28 Nov.: Maj. General 1 Cav, Bourcier, should be in 3238.

GAME-TURN RECORD TRACK

• Bernadotte enters with the I Corps on turn 2. • The Songis artillery unit enters with Napoleon on turn 2. • It is correct that Ferdinand enters at the same hex as Wrede.

Part 3: The Sun of Austerlitz Exclusive Rules (Original 2003 Booklet)

Copyright 2003, Operational Studies Group. Contains the Battle Scenario Rules, the original Campaign Rules, Optional Rules, set-up and Scenario Information. Where the revised Exclusive Rules in Part 2 differ, Part 2 governs.

INTRODUCTION

[1.] The Sun of Austerlitz simulates the decisive conclusion to Napoleon Bonaparte’s First Danube campaign. After a brilliant maneuver against the Austrians at Ulm, Napoleon entered Vienna on the 13th of November, 1805. The Austrian Emperor Franz I refused the French offers of peace, as fresh Russian forces arrived in Moravia to support the Austro-Russian survivors of the retreat.

[2.] The early stages of the Danubian Campaign may be covered in an Expansion Set to be published by OSG. (See OSG’s website, www.Napoleongames.com for more information on pre-publication titles.)

[3.] The counter sheet in this package also includes replacement and variant counters for OSG’s La Guerre de l’Empereur game (see ¶26— “Replacement & Variant Counters”).

[4.] The Sun of Austerlitz is a part of the Campaigns of Napoleon Series 1X, and uses the same Standard Rules as Napoleon at Bay and Bonaparte in Italy, also published by OSG.

[5.] This Exclusive Rules folder contains rules particular to The Sun of Austerlitz. These are used in conjunction with the Standard Rules, and unless otherwise stated, all the Standard Rules apply. Exclusive Rules either add to or modify the Standard Rules. The Exclusive rules are presented in two levels, Battle Scenario Rules and Campaign Rules. Within each level, the rules are presented in order of the Sequence of Play.

[6.] The Battle Scenarios serve as an introduction to the game, with the Forces set-up on the map as the armies are about to meet in battle. The Battle Scenario Rules add only a few pages to the Standard Rules. Read the Battle Scenario rules, then play one or two of these shorter scenarios.

[7.] After you have experienced the flow of play, you will be ready to read the Campaign Rules, which add several more pages of Exclusive Rules, some of which are optional.

[8.] The “Scenario Information” gives the conditions at the start of each Scenario, including AP Levels, Start Date, and the like. (See ¶179.)

Background

[9.] Despite the catastrophe of Ulm in October and the loss of Vienna, the Austrian Emperor Franz refused to surrender. He retired into Moravia alongside the Russians under General Kutusov, meeting Tsar Alexander at Olmütz. Napoleon followed them, taking up a position near the fortress of Brünn (Brno). The Tsar was elated by his recent meeting at Potsdam with the Prussian King, Friedrich Wilhelm III, who tentatively agreed to join the coalition against France. The French were over-extended, without food and other necessities. The chill north winds reminded them of their desperate need of a conclusive battle and a halt to active operations. King Friedrich Wilhelm of Prussia despatched an ultimatum to the French camp, in care of his foreign minister, von Haugwitz, while the Austro-Russian army advanced en masse to the plain of Austerlitz. Napoleon played along, ordering his troops to feign demoralization and a panicked retreat to lure the Austro-Russian forces to their destruction.

Politics and Geo-Politics

[10.] “Nothing but a decisive victory would have answered Napoleon’s needs. Defeat would have been most disastrous, for Napoleon was in the heart of a hostile country. Moreover Prussia, alarmed at the success of his invasion of Germany, was preparing to take up arms; her ambassador had arrived in the French camp bearing the ultimatum of his govern-ment; the cabinet of Berlin fully expected war.” —John C. Ropes

Nothing in diplomacy is certain; Prussia’s promised declaration was no exception. Haugwitz, who favored the French, persuaded his government to allow him to present an ultimatum to Napoleon, and was about to hand it to the Emperor at the very moment when a scout arrived with news of the Allied advance. At that Haugwitz was packed off to Vienna. The Allies attacked, but what if they had not? Supplies were scarce and forage inadequate. Both sides were suffering in their encampments, the winter weather was terrible, and attrition to disease and desertion was high, especially on the Austro-Russian side. Had the Austro-Russians delayed their advance, Napoleon would have read the ultimatum and sent Haugwitz back to a Prussian court certain to mobilize its army on the spot. Prussia's declaration would have put the burden on Napoleon to defeat the Russians and Austrians before the Prussian Army appeared on his Line of Communications. Napoleon would have been forced to advance on Olmütz. Kutusov, the Russian General-in-Chief, wanted no part of an offensive, preferring to withdraw upon his source of supply and await Prussian aid. Already exhausted by two months of continual marching, the French would have been hard-pressed to follow the Austro-Russians had they withdrawn. Tsar Alexander of Russia was determined to finish the job and liberate Vienna. The French, however, controlled the Danube Valley, Austria’s most fertile region, and were able to draw supplies from the conquered country for as long as they did not advance far from Brünn.

[11.] Kutusov’s new Chief of Staff, the Austrian Weyrother, formulated a plan to shove the French aside and cut their LOC to Vienna. It was an enormous blunder to make a flank march against the French, in the face of the whole enemy army, abandoning the dominating feature of the Pratzen heights. Had they merely awaited an attack by the French on the Pratzen, Napoleon would have been obliged either to strike a blow, or to undertake a war of maneuver. A doubtful success, or a drawn battle, would have necessitated a French retreat all the way back to Bavaria.

[12.] The great advantage of the French Army lay with its leaders. Davout was the most capable of the marshals, who understood strategy and kept his corps under perfect discipline. Soult too was talented and, unlike many of his peers, capable of independent command. Lannes and Ney were inspiring leaders of men in action. Murat had courage, activity and dash as a cavalry leader. The army—nearly all composed of French troops, with many veterans—was the best Napoleon ever fielded. By contrast, the Austro-Russian leadership was slow and their movements were poorly coordinated.

GAME EQUIPMENT

[14.] The Sun of Austerlitz contains the following: One Box One Game Map, 22" x 34" One sheet of die-cut counters (280) Standard Rules Folder Exclusive Rules and Study Folder (including Charts and Tables Folder) Battle Resolution Worksheet 8.5 x 11" Austro-Russian Organization Display 8.5 x 14" French Organization Display 8.5 x 11" Austro-Russian Leader & Unit Manifest 8.5 x 17" French Leader & Unit Manifest 8.5 x 17" Turn and Record Tracks 11 x 17"

GAME MAP

[15.] The Game Map shows the fertile valley of Moravia, with its capital, Brünn in the center.

[16.] The diagram below shows the location of the Sun of Austerlitz map in relation to the eastern section of Victory Games’ edition of 1809 in this same series (the 1809 game is currently out of print).

Terrain Type of Divided Hexes

[17.] Use the prevalent terrain type in a hex (that type which fills more than half the hex). If uncertain use the type with the highest MP cost.

UNIT AND LEADER MANIFESTS

[18.] All Set-Up Information is presented on the Leader and Unit Manifests. The Unit Manifests specify, for each unit, the Leader’s track on which to set-up and its strength. The Leader Manifest specifies the Leader’s hex on the map or the Force Leader (see ¶174).

COMBAT UNITS & LEADERS

[19.] The combat units represent Divisions and Brigades, ranging in strength from 1,000 to 9,000 men. The combat unit counters always go on the Organization Displays. Units with a maximum strength greater than 5 have “+5” on their front side. If “+5” is facing up it means that 5 Strength Points must be added to the track space on the Organization Display which the counter occupies. Note: The flag side of the counter sheet was designated “front“—to be struck by the die during manufacturing for best alignment on that side—to prevent identifying marks.

Leader Ratings

[20.] The Leader counters have Initiative, Subordination, and Command Ratings, listed in that order. Leaders have a six-pointed star to distinguish them from combat units.

Nationality

[21.] French units are sky blue, (the French Imperial Guard is dark blue with yellow values); Austrian units are white (with ochre stripe); Russian units are earthen brown; Prussian units are steel blue-gray.

[22.] Replacement Markers are used to record the levels of manpower residing in the replacement pool. There are markers for recording artillery, infantry and cavalry. (Other markers are explained in the course of the rules.) Imperial Guard (IG) replacement points may only be added to Guard units. Russian replacement points can only be added to Russian units. Austrian (A) replacement points can only be added to Austrian units. German (G) points can only be added to the Bavarian unit. If there is no marker provided for recording a particular type of replacement points they must be used in the turn they come available or else forfeit.

Major Generals

[23.] Major Generals are leader counters used to show detached combat units operating independently on the game map. Infantry Major Generals have ratings of 1 [2] 1.5 and cavalry Major Generals are rated 4 [1] 1 (Initiative/Subordination/Command Span). These generic Major Generals are identified by number and type (infantry and cavalry). Major Generals may only be activated or voluntarily de-activated during the Friendly Command Phase. The number of Major Generals that may be activated is limited only by the number provided.

[24.] The following Austrian and Russian Leaders have their own eponymous combat units: Austrians Kienmayer and Kolowrat; Russians Docturov, Przybyszewski, and Bagration. Each of these leaders must have his own combat unit on his track (as long as his leader and combat unit counters remain in play). The above leaders can be brought into play and removed from play like Major Generals, but each may only enter the map in the hex with his combat unit.

Example 2: Leader Docturov could command, in addition to his own Combat unit, the Leader Kienmayer, with a Subordination Rating of 3; who in turn, with his Command Span of 5, could command his own Combat unit [2] as well as Miloradovich’s [2] and (Austrian General) Hohenlohe’s [1/2] Combat units.

Note: Russian leaders may command Austrian Leaders and/or Austrian Combat units, and Austrian Leaders may command Russian Leaders and/or Combat units.

Garrisons

[25.] The Citadels of Olmütz and Brünn begin the game with garrison markers (see ¶183). Garrisons function as any other force, except that they have no Organization Track, and a subordination cost of zero. Each Garrison has an intrinsic strength of 1 Strength Point (see ¶34 and 37 “Supply Source Garrisons”) and a normal ZOC.

Replacement & Variant Counters

[26.] Ninety-four counters and markers included on the counter sheet in this package are provided for use with OSG’s previously published game, La Guerre de l’Empereur. Punch these counters and store them with your copy of the game. A separate sheet in this package will describe the use of these Replacement & Variant Counters.

Battle Scenario Rules

A. WEATHER

[27.] There are five different types of weather, one of which must be in effect during each Game-Turn. The five types are Frost, Snow, Mud, Rain, and Fair. At the beginning of each scenario—and at the beginning of each subsequent Game-Turn—the First Player must roll the die and consult the Weather Table to determine the weather for the coming turn, noting die roll modifiers as appropriate (see ¶28). Place the Weather Marker in the appropriate space on the Weather Track.

[28.] If the prior turn was Mud and Rain follows, effects of both Rain and Mud apply (and are cumulative). If last turn a ‘six’ was rolled, add one to the die (see Weather Table).

I.a.1 LINES OF COMMUNICATION

[29.] A Line of Communications is considered established if it can be traced up to 18 MPs in length—over any passable terrain, from the supply source to the force. In order to use the specified Administrative Point Level (see ¶184) in determining attrition, a Force must be within 18 Movement Points of a depot or any possible friendly Supply Source. Depots include Brünn, Olmütz, Znaim, Stockerau, etc. The Communications Table shows which Supply Sources may be used for each Army. If a Force is further than 18 Movement Points from its Supply Source or friendly depot, it must use the “zero” column on the Attrition Table when determining attrition and may not be issued a Movement Command (see Standard Rules).

[30.] Tracing the LOC Use the cavalry movement rate when determining the MP cost of each hex in the LOC. Exceptions: bridges add no additional MPs and connected Primary road hexes count as 1 MP each (instead of 1/2 MP).

I.a.2. CHANGING THE SUPPLY SOURCE

[31.] The Supply Source may be changed to another Supply Source or to a depot hex with a LOC. Step 2 of the Administrative Segment is the only Administrative step taken in the Battle Scenarios. For the French and Austro-Russian Armies to change their Active Supply Source takes one complete Game-Turn to accomplish.

PROCEDURE:

[32.] Flip the Supply Source Marker over (to signify that the change is underway). During the next Administrative Segment, the Supply Source Marker may be returned face-up at the other depot or supply source.

Interim Effects

[33.] During the turn the Supply Source Marker is flipped over, the Army may issue no Movement Commands and must use the “zero/No LOC” column on the March Attrition Table.

SUPPLY SOURCE GARRISONS

[34.] The Active Supply Source has an intrinsic garrison with a strength of one and a normal ZOC (see ¶37). Supply Sources in the Battle Scenarios (only) may be in depot hexes and not necessarily on the mapedge (see ¶182).

Capture of Supply Sources

[35.] If the Supply Source is attacked or repulsed and the garrison is eliminated or is forced to retreat, the Supply Source is considered captured. When a Supply Source is captured, the Active Supply Source Marker is removed from play. While the Supply Source marker is out of play, the army suffers the Interim Effects under ¶33, above.

[36.] A Supply Source Marker may be returned to play at any possible Supply Source or depot for that Army free of enemy units (or ZOCs) during any following Admin Segment. Supply Source hexes cannot be permanently destroyed. A captured Supply Source may be reactivated as soon as the enemy forces are removed.

Garrisons in Combat

[37.] Garrisons may not attack, and must defend as part of any other force in the hex. They must absorb the first SP lost in retreat. Garrisons have an Initiative of “1” for pursuit and for initiative comparison purposes.

I.a.4 REPLACEMENTS

[38.] Replacements are not used in the Battle Scenarios.

II.a. REINFORCEMENTS

[39.] Reinforcements are used in the Battle Scenarios and appear according to the Turn Record Track.

II.b. WEATHER EFFECTS ON MOVEMENT (Steps 2 and 3)

Mud

[40.] Mud increases the severity of March Attrition. Add one to the die roll on the Attrition Table.

Fair

[41.] No effects.

Frost and Snow

[42.] Primary Rivers and Lakes are frozen and are treated as (unfrozen) secondary rivers.

Rain and Snow

[43.] Add one to the Resistance Modifier when attempting to exit Enemy ZOCs.

III.b. WEATHER EFFECTS ON COMBAT (Steps 5, 7, and 9)

Fair

[44.] No effects.

[45.] Frost. During Frost, forces may retreat after combat across lakes. The force is treated as retreating across a secondary river (see ¶62). Forces may never attack across the ice.

Rain

[46.] Add one to all artillery die rolls. Subtract one from the Resistance Modifier in Pursuit.

Mud, Rain/Mud

[47.] Add two to all artillery die rolls.

Snow

[48.] Add one to all combat die rolls, including Artillery Fire. Subtract one from the Resistance Modifier in Pursuit.

III.b.6 TERRAIN AND COMBAT

(See the Terrain Effects Chart.)

Affecting Terrain

[49.] Affecting Terrain includes all Depot, Citadel, Hill, and Mountain hexes when the defender is in the hex, or Secondary River and Bridge hexsides attacked across. Use the “Affecting” line on the CRT. Non-affecting Terrain includes Clear, and Secondary Town Hexes. There is no cumulative benefit for hex and hexside Affecting Terrain.

Mountains

[50.] The total attack strength of a force attacking into a Mountain hex may not exceed nine Strength Points. When determining combat odds, disregard any strength in excess of nine points. Defending units in Mountain hexes receive the benefit for Affecting Terrain. If Pursuit is chosen, a force of up to 9 SPs may pursue.

[51.] Cavalry units in Mountain hexes may not attack, even if the defending hex is a non-Mountain hex; there is no pursuit modifier for cavalry in Mountains. Cavalry may attack into Mountain hexes.

Woods Effect on Combat

[52.] The strength of infantry units and cavalry units attacking into a Woods hex is reduced—infantry by one fourth and cavalry by one-half (round off to the nearest half point ). Artillery in a woods hex may not bombard; target unit in a woods hex may not be bombarded.

CITADELS

[53.] Brünn (Brno) and Olmütz (Olomuc) are the only two Citadel hexes on the map. Units defending in a Citadel hex have their Combat Strength doubled.

[54.] Zones of Control extend into and out of Citadel hexes normally. Units in a Citadel may avoid all combat; a unit in a Citadel may decline to be attacked (see ¶56). Once placed under siege a fortress will surrender if the strength of the besieged force is 7 SPs or less.

Stacking Limits

[55.] A special stacking limit applies to Citadel hexes. No more than 15 Strength Points may occupy a Citadel hex.

Sieges

[56.] The decision whether or not to use the Citadel benefit is made at the moment combat would normally be required. A Force in such a hex may choose to resolve combat, but may not choose Pursuit Battle. Once a Force in a Citadel has taken advantage of the Citadel to avoid combat, all Forces in the hex are considered to be under siege. A besieged Citadel may not be attacked. Place a Siege Marker in the hex. Once placed under siege, a Force remains in that condition until the beginning of any Phase in which the hex is no longer adjacent to Enemy Forces. Note: A Force must first attack any besieging force before moving into or out of a Friendly Citadel; a force cannot move into a besieged citadel until the besieging enemy force is no longer adjacent.

[57.] Besieged Forces may not receive Movement Commands but may attempt to move, by attacking out of the Citadel, shifting the odds on the CRT one column to the left (in addition to other terrain effects). For example, a combat at one-to-one odds is resolved at one-to-two. (This shift is due to the entrenchments that besieging forces would have constructed.) Counterattacks against citadels are not mandatory. A force besieged in a citadel prevents an enemy LOC from going through the hex.

Attrition to Besieged Forces

[58.] The force besieged in a Citadel (like all other forces) must roll each turn on the Attrition Table.

[59.] Both Citadels are also depot hexes. Forces in Citadel-depot hexes may use the current Administrative Point Level when determining attrition; however, an Attrition die roll Modifier of +5 also applies to Besieged Forces.

Surrender

[60.] A besieged Citadel will surrender at the end of any Besieged Player’s Turn in which the combined number of SPs besieged is seven or less, and adjacent to Enemy Forces.

Besieged at Start

[61.] Neither Citadel is considered to be under siege at the start of any scenario.

III.b.8 RETREAT AFTER COMBAT

Retreat Across Rivers

[62.] A Force which retreats across an unbridged secondary river after combat loses double its normal pursuit loss (as though it were retreating through an Enemy ZOC) if the Pursuit goes at least as far as the hex adjacent to the river hexside. If a loss is already doubled due to retreat through Enemy ZOC, there is no further loss due to the river. Retreat across Primary Rivers is allowed only at bridges.

Retreat Off Map

[63.] A Force may be moved off the map during a retreat after combat if permitted by the priorities of retreat (see Standard Rules ¶176). Pursuit of such retreating Forces must end at the map edge hex (see Standard Rules ¶176). A Force may not retreat off the map if it can retreat through an Enemy ZOC or displace a Friendly unit instead.

[64.] The Force reenters the map in its following Movement Phase at the nearest map edge hex unblocked by enemy units or Enemy ZOCs, in the same manner as Reinforcements. A Force must reenter the map as near as possible to its point of exit, and closer to the nearest Friendly Supply Source if possible.

IV. BATTLE SCENARIO VICTORY CONDITIONS (Scenarios 2 and 3 only)

[65.] Austro-Russian Victory (either of two): (Note: Scenario 1 has its own Victory Conditions.) At the end of a battle scenario, the Austro-Russian Player (1) has a Force with an unbroken LOC with 4 or more infantry SPs anywhere on the primary road from Florisdorf (2853) to Brünn (1723); or (2) has achieved more critical battle victories than the French Player. French Victory: The French Player wins if the Austro-Russian Player achieves none of the listed conditions.

Campaign Rules

[66.] The following rules show how the long periods of a full campaign affected the operations of the armies. Their use entails some changes in the Standard Sequence of Play and some additional markers. These rules must be used when playing the Campaign Scenario. Most of these rules may be used if both players agree when playing the Battle Scenarios.

[67.] The Campaign Scenario covers the period from 15 November 1805 through 16 December. With turns of active campaigning taking about 30 minutes to complete, two Players can complete the Campaign in 7-10 hours of playing time. A shortened Campaign Game can begin on 27-28 November. Set up time: 15 minutes.

VEDETTES

[68.] Each Cavalry Vedette Counter represents a cavalry regiment divided into five or ten 50-man patrols fanned-out to create a presence over a wide area, collecting information, scouting, and screening-off enemy patrols.

[69.] Each side is provided with a number of Vedette Counters used to deceive the enemy player and obtain information about enemy forces. At the start of any scenario, up to two Vedettes may be placed on the map with each actual Force leader appearing on the map. You may not place more Vedettes than provided in the counter mix.

MOVEMENT OF VEDETTES

[70.] The Movement Allowance of all Vedettes is 9 Movement Points. Vedettes pay cavalry MP costs. Vedettes move in every way like real Forces until their identity is revealed (except as outlined in items 1 through 6, below). Vedettes are revealed when adjacent to the enemy (see ¶74 and ¶81). A vedette, once revealed, remains revealed until the next time it moves (regardless of the phase or segment in which it next moves). Vedettes differ from real forces as follows: 1) Vedettes do not require an Initiative die roll or Movement Command to move—nor do they suffer attrition. To disguise them, a player ought to some-times make Initiative and Attrition die rolls for them; 2) Vedettes cannot damage bridges, cannot capture pontoons or cut Lines of Communications or the like (see ¶72); 3) Vedettes are not subject to Initiative Comparison, and forces adjacent to Vedettes ignore their ZOCs when exiting (see ¶74); 4) A Vedette cannot create its own Major General, and has no track on the Organization Display (see ¶79); 5) Vedettes may not retreat after combat, and may not form part of a pursuit force (see ¶81); 6) Vedettes do not count against stacking limits.

[71.] When new forces are created or appear as rein-forcements, up to two new vedettes (if available) may be drawn from the “Vedette Pool” to appear with each. All other vedettes are placed in the available Vedette Pool. When Forces are consolidated, Vedettes may remain in play on the map.

Vedettes and Lines of Communications

[72.] Vedettes may not interfere with a Line of Communication, Dispatch Distance, or Supply Distance. Such may be traced into or next to a hex suspected of being occupied solely by Vedettes. After the Line is defined, the opposing player need only state whether the Line is blocked. This is his option: he may elect not to cut the line even if the unit is not a Vedette. If the line is blocked, a new Line for that unit cannot be defined until the next Supply check.

Vedettes Zones of Control

[73.] Vedette units have flexible Zones of Control. When an enemy force enters the ZOC of a friendly-occupied hex containing only Vedette units, the owning player must reveal the Vedettes. The enemy unit may continue moving through or around the hex containing the Vedette, ignoring its Zone of Control. The enemy unit may not end its move in the same hex as the vedette.

Repulse of Vedettes

[74.] The owning player must reveal the Vedette after his opponent has declared whether he will attempt to repulse the hidden unit. If so the repulse attempt is executed. The Vedette may not be repulsed in the current Movement or Forced March Phase unless the opposing player announced his intention to repulse prior to the revelation of the all-Vedette force.

Exception: A Vedette which is not repulsed by the first unit to enter its ZOC may be repulsed by follow-on Forces.

VEDETTES IN COMBAT

[75.] During the Friendly Combat Phase, Vedettes in enemy Zones of Control are compelled to attack or repulse (Exception: see ¶80, “Vedettes and Retreat Before Combat”). By attempting repulse, the vedette may determine the identity of the enemy force leader and then retreat before combat. Alternatively, the Vedette can follow through with a regular attack in order to obtain the exact strength of the enemy forces during step 6 of the Combat Sequence (the vedette will usually be destroyed, but may be recreated—see ¶78). There is no adverse effect on the enemy force unless it is also a vedette. There is no pursuit of a vedette eliminated in combat.

[76.] Player's Note: There are two reasons to enter your own vedette into an Enemy ZOC. First, by attempting a repulse, to determine the identity of the enemy leader (the vedette may retreat before combat). Second, in order to obtain the exact strength of enemy forces in their ZOC during step 6 of the Combat Sequence (the vedette will usually be destroyed, but may be recreated—see ¶78). Vedettes aren't affected by the Initiative Comparison Table, nor does their ZOC force enemy units to consult it. Thus, vedettes can give the owning player a “quick impression” which he can respond to during movement, but he can’t get exact information until after all movement is complete.

[77.] Vedettes are treated as normal combat units for combat purposes, except as follows. A Vedette may not choose to fight a Pitched Battle, and may attack an enemy hex only if there are no other friendly forces in the Zone of Control of the enemy unit. Vedettes must combine in attacks with other friendly units in the same hex. Vedettes have a Combat Strength of 1/2 SP when fighting alone and a combat strength of zero when combined with a real force. Vedettes may be Repulsed (see ¶74) if the attempt is declared before the Vedette is revealed. Vedettes cannot take advantage of the defensive benefits of a citadel, but they do get applicable Secondary Town or Depot benefits. During the Enemy Combat Phase, each Vedette with one or more enemy Forces in its ZOC must be attacked. A player may not ignore a Vedette to which his Forces are adjacent during his own Combat Phase.

Example: An attack by a unit with a strength of “two” upon a Vedette would be resolved at four-to-one odds.

Vedettes Lost in Combat

[78.] A Vedette which is forced to retreat or suffers any combat strength loss on the CRT is removed from the map and placed on a Leader’s portrait on the Organization Display of the nearest Friendly Force within 9 MPs. During the Organization Segment of the next Friendly Player-Turn it is stacked on the game map with its Force Leader. If no such force exists within nine cavalry Movement Points it is removed to the Vedette Pool.

Vedette Strength

[79.] The strength of Vedette units cannot be incorporated into the strength of regular units on the Organization Display. The only time Vedette strength is represented on the Organization Display is when two or more vedettes are together in the same hex. Only one vedette per hex is allowed to remain on the map. The extra vedettes in the hex are either removed to the portrait of the nearest friendly leader on the Organization Display, or else must move out of the hex. While on the display Vedettes have zero strength and are ignored for all purposes.

Vedette Retreat before Combat

[80.] Non-Phasing Vedettes (first) and then Phasing Vedettes which are alone in the hex (as well as cavalry Forces of 1 Strength Point, see ¶82)—can take an automatic, voluntary “Retreat” result, of one or two hexes, before combat resolution but after finding out the approximate strength of the enemy-occupied hex, in step 3a of the Combat Procedure (see Standard Rules, ¶146). The enemy may not pursue. Vedettes must engage in combat normally if they do not elect to take the auto-retreat.

Vedettes and Enemy Retreats and Pursuits

[81.] Neither Vedettes nor their Zones of Control interfere with the ability of enemy units to retreat or pursue during the Combat Phase. Units may always ignore a Vedette when retreating or pursuing. If there is no other alternative, units may retreat or pursue through a hex occupied solely by enemy Vedettes. (In this case the enemy player has to reveal the Vedette-only hexes that may be retreated through.) The Vedettes are displaced (see ¶174, “Priorities of Retreat—3” in the Standard Rules) or eliminated if unable to displace. A Vedette by itself may not conduct a pursuit

Regular Cavalry Acting as Vedettes

[82.] The owning Player may choose to treat a cavalry Force of 1 Strength Point as a Vedette—if it is in Dispatch Distance at the moment it comes adjacent to an Enemy Force. A cavalry Force of 1 Strength Point may never damage bridges, capture pontoons, or cut Lines of Communications, dispatch distances or the like (see ¶72).

Vedettes Out of Dispatch Distance

[83.] Vedettes that cannot trace a Dispatch Distance to a Center of Operations, Supply Source or active friendly Depot during the Administrative Segment of the Player-Turn, are immediately removed from play until the Organization Segment of the next Friendly Player-Turn. They return to play as described in ¶78.

I.a. ADMINISTRATION

[84.] In order to obtain Movement Commands in the campaign game, each Army draws from its pool of Administrative Points (APs). APs are used to create Movement Commands, which the Player must provide for each force if he wants to be certain it will move. A Movement Command costs one AP (see ¶186). As many Movement Commands can be created per turn as there are APs available (provided that the Center of Operations is active), but each force may only move once per turn. In order to receive a Movement Command, Individual Forces must trace a “Dispatch Distance” of 18 MPs or less to the Center of Operations. This Dispatch Distance may traverse any passable terrain.

[85.] The number of Administrative Points remaining on the AP Track at the time of Movement determines the severity of March Attrition for Forces not Foraging. When determining attrition, the Player finds the strength of the Force on the column headed by the AP Level showing on the AP Track at the instant of the Force’s movement. The fewer Administrative Points accumulated, the greater will be the attrition.

Note: Forces in Forage Mode may use an alternative attrition calculation method based upon the Forage Value of the surrounding terrain (see ¶137).

I.a. SEQUENCE OF PLAY— COMMAND PHASE CHANGE

[86.] The Administrative Segment now uses all four Steps:

Receive Administrative Points and reset the AP Marker on the Accumulated AP Track (¶94).
Designate friendly Supply Source. If this is now changed from last turn, deduct one AP (¶98).
Disband friendly Center of Operations (if desired). Deduct one AP for this (¶99).
Add new Replacement Points to the Replacement Pool (¶102).

LINE OF COMMUNICATIONS

[87.] As in Standard Rules ¶55, a Line of Communication (LOC) is a line of connected, primary road hexes free of enemy units or their Zones of Control. There are two differences. First, the LOC may not depart from primary roads. Second, the LOC runs only from the Supply Source to the Center of Operations (paying no additional MPs to cross bridges). If the LOC exceeds 40 Primary Road hexes in effective length (see ¶89), the Center of Operations is “Inactive” (see ¶97 “Functions of Centers of Operations”). The inactive Center of Operations may not be used when determining attrition (see ¶107).

[88.] The Austro-Russian Center of Operations must trace its LOC to an active Austro-Russian Supply Source and the French Center of Operations must trace its LOC to an active French Supply Source (see ¶91).

DEPOTS

[89.] Depots are the middle links in the supply chain— called ‘magazines’ in Napoleon’s time—where resources were collected from friend and foe alike. Wagons were also collected there to return to the supply source, or to range far and wide in search of fodder and forage. A depot allows you to reduce your Effective LOC. For each depot in the LOC (through which the LOC is traced) you can subtract 10 Primary Road hexes from the overall LOC length when determining availability of APs for that turn. The depot can be anywhere along the LOC. Example: With the French S/S in Vienna and Center of Operations in Brünn, the actual distance via Stockerau and Znaim is 50 hexes; the Effective distance traced via those two depots would be 30 hexes (reduced by 10 for each depot).

[90.] Depot Functionality Depots cannot issue Movement Commands. However, forces may trace Dispatch Distance to a Depot for Attrition purposes. The Depot may function as long as it has a valid LOC to any friendly Supply Source (not limited to the active Supply Source). All depots are functional at all times and may be used by either player as long as they lie on the friendly LOC and are not occupied by enemy forces. Depots do not require garrisons. (Brünn and Olmütz have special garrison units—see ¶183). Unlike in the Battle Scenarios, Depots must have an LOC— either direct to any possible friendly Supply Source, or via another friendly depot which itself has an LOC to a Supply Source (this supersedes ¶59). In addition to printed Depot hexes, Supply Sources can act as Depots.

Available Supply Sources

[91.] All North and South map-edge hexes containing exiting Primary Roads are Supply Sources. French Army: any of two primary roads exiting the southern edge of the map, leading to Vienna (2754/2853) or Krems (1154), and controlled by the French Player. Austro-Russian Army: any of the four primary roads exiting the northern edge of the map, and controlled by the Austro-Russian Player. The Supply Source (S/S) may be changed (see ¶31, “Changing the Supply Source.”) If Austro-Russian forces capture the French S/S nearest Vienna (2754 or 2853), the remaining S/S leading to Krems (1154) can still function, though on a less advantageous column. (See the AP Pool).

I.a.1 HOW ADMINISTRATIVE POINTS ARE RECEIVED

[92.] The player must see to the provisioning of his army before it can effectively be used. The Player who fails to make the most conservative use of resources will be unlikely to win the Game. Resources such as wagons and the necessary management of their contents are represented in the game by Administrative Points. APs are an abstract measure of the current materiel condition of the troops in an army.

[93.] Administrative Points are used to create Movement Commands, which the Player must expend for each force if he wants to be certain it will move. The Level of Accumulated Administrative Points determines the severity of March Attrition for Forces not Foraging.

How to Receive Administrative Points

[94.] New Administrative Points are accumulated during the Administrative Segment of the Player-Turn. The Player refers to the Administrative Point Pool and rolls two dice to determine the quantity of APs he receives. Cross-reference the Effective LOC distance (see ¶89) between the army’s Center of Operations and its Supply Source with the dice roll. The number obtained from the cross-reference is the quantity of Administrative Points added to the accumulated total. If the Player’s Army has an inactive Center of Operations it receives no new Administrative Points. First Turn: The French Player receives no new APs on 15-16 November.

Army Commander AP Bonus

[95.] If the Army Commander (Napoleon, Alexander, or other leader designated as the army commander, see ¶104) currently resides with his Army’s Center of Operations, add one AP to the total received.

How to Use the Administrative Point Tracks

[96.] For each Army, use the two markers provided to indicate “Ones” and “Tens” of accumulated Administrative Points. Adjust these markers on the track to record the level as it ebbs and flows.

Example: To show “Thirteen” Administrative Points, place the Tens marker in the Number 1 space, and the Ones marker in the Number 3 space.

FUNCTIONS OF CENTER OF OPERATIONS

[97.] An Army’s Center of Operations must be active in order to issue Movement Commands (or replace-ments), or to receive new Administrative Points. A Center of Operations may be rendered inactive in two ways: (1) if it moved during the previous friendly Player-Turn, and (2) if it has no Line of Communications. This LOC may be traced only to the active Supply Source appropriate to that army. The Center of Operations should be flipped over when inactive. It may reactivate immediately when all conditions necessary for activation are met. (Exception: see ¶110, “Movement of Center of Operations” below).

I.a.2 Changing the Active Supply Source

[98.] The cost to change the Supply Source is one (1) AP. This takes one complete turn to effect. During that turn the Supply Source marker is flipped over to its “Inactive” side. While the Supply Source marker is flipped over, the Center of Operations is “Inactive” (see ¶97, “Functions of Center of Operations”); furthermore, the Center of Operations may not be used when determining attrition (see ¶107).

I.a.3 Disbanding Center of Operations

[99.] To voluntarily disband the Center of Operations, expend one AP, remove it from the map, and place it on the Turn Record Track three Game-Turns ahead of the current turn. The Center of Operations will appear as a reinforcement that turn at the Army’s Supply Source. The Center of Operations may be disbanded only during Step 3 of the Administration Segment. While disbanded, the Center of Operations is considered “inactive” (see ¶97 “Functions of Center of Operations”).

[100.] Commentary: The equipment necessary to generate a new Center of Operations always exists at the Supply Source. The disbanded Center of Operations is considered broken-up and its equipment either captured or distributed along the new LOC; its staff is too mobile and dispersed to be captured.

[101.] To receive Movement Commands a Force must be able to trace a Dispatch Distance to the Center of Operations (see ¶108). To benefit from the Army’s Administrative Level when determining attrition, a Force must be able to trace Supply Distance to any possible friendly Supply Source, or to a Depot or Center of Operations with an LOC (see ¶109).

I.a.4 REPLACEMENTS

[102.] Replacements of fresh and recovered troops become available for addition to the Replacement Track according to the Russian or French Replacement Line on the Turn Record Track, adding the amounts specified to the Replacement Track. Replacements may only be added to units of the spec-ified nationality and type. An army with an inactive Center of Operations may not add Replacements from the Replacement Pool to its units. Units which receive replacements are immobile and may not move during the ensuing Movement Phase.

Replacement and Reinforcement Schedule

[103.] Quantity of Replacement Points and arrival of Reinforcements is specified on the Turn Record Track. Leaders which do not begin the game on the map may be brought on later as reinforcements (see ¶125) as specified on the Turn Record Track and the Leader Manifest.

Austro-Russian Army Commanders

[104.] The Austro-Russian Army Commander-in- Chief is Tsar Alexander. If Alexander is eliminated, the remaining Leader with the highest Command Span becomes the Army Commander (see ¶95, “Army Commander AP Bonus”).

I.b. ORGANIZATION SEGMENT

I.b.2 March Regiments

[105.] March Regiments are brought into the game as explained in Standard Rules ¶65, 66, 75. Place the new March Regiment on the track of some leader in the same hex. March Regiments may also enter at any Friendly Supply Source or Depot-with-LOC— create a Major General for it and place it on the map in the same hex as the combat unit donating the Strength Points. It may enter at the Supply Source with replacement strength like a reinforcement (¶106).

II.a.1 REINFORCEMENTS

[106.] Combat units which do not begin the game in play may enter according to the Turn Record Track— Reinforcement combat units must enter under the command of a Major General or under a Reinforce-ment Leader arriving with them. Reinforcement units entering under the command of a Major General will be listed by unit designation and name. (When in doubt, use the strength of reinforcement units shown for the next Battle Scenario Start Date.)

II/IIIa. IN SUPPLY

[107.] As long as a Force begins a march within Sup-ply Distance (see ¶109) of its active Center of Opera-tions, or of a Depot on its LOC, or any possible Sup-ply Source of that army, that Force is regarded as “in Supply.” When determining attrition for that Force a player may use the column on the March Attrition Table corresponding to the number of Administrative Points currently in the friendly Accumulated AP Track. If the Force does not begin within Supply Distance of the Center of Operations, a Depot, or a possible Supply Source, that Force is regarded as “out of Supply.” It must forage or use the “zero” column on the Attrition Table. Supply Distance may not be traced to the Center of Operations or to a Depot which is out of LOC or if there is no active Supply Source.

II.b.1 Dispatch Distance

[108.] A dispatch—usually issued in duplicate and carried by separate messengers taking different routes—can travel as fast as a horse and rider, allowing for wrong turns, about 18 hexes (36 miles) in 6 and one-half hours. At that distance it would take 24 hours to write and deliver the order, act upon it, write and deliver the report of the outcome. Beyond that, the orders are already out of date before they can be acted upon. Dispatch Distance is the maximum distance a Force may be from an active Center of Operations and still receive Movement Commands. The Dispatch Distance for each Army is 18 MPs (see Communications Table). The Force need only be within Dispatch Distance during Step 1 of the Movement Procedure to benefit; it may move out of Dispatch Distance during Step 2 without conse-quences until the next turn. The Dispatch Distance is traced through any passable terrain at cavalry movement costs.

Exceptions: The path may not be traced through enemy units or their ZOCs (unless the ZOCs are friendly-occupied). In calculating the Dispatch Distance, primary roads are counted as secondary roads (1 MP), with no extra cost for bridges. Note that Dispatch Distance has to do with Movement Commands, while “Supply Distance” (see below) has to do with Attrition.

[109.] Supply Distance A Supply Distance is a route of wagons moving about 10 miles per day. Horse-drawn wagons are very inefficient, and over a few days’ journey all their carrying capacity has to be devoted to fodder for the teams. Supply Distance is the maximum distance a Force may be from any possible Supply Source, Depot, or Center of Operations of an army and still be “in Supply” (see ¶113). Forces must be in Supply to use their army’s accumulated Administrative Point Level when calculating attrition, and to receive Replacements. The Supply Distance for each Army is 18 MPs (see the Communications Table). Supply Distance is traced through any passable terrain at cavalry movement costs. Exceptions: The path may not be traced through enemy units, or through enemy ZOCs (unless the ZOCs are friendly-occupied), or across non-road hexsides into Mountain hexes. In calculating the Supply Distance, primary roads are counted as secondary roads (1 MP), with no extra cost for bridges.

II.b. MOVEMENT OF CENTER OF OPERATIONS

[110.] The Center of Operations has a Movement Allowance of 5 Movement Points. For movement purposes, it moves like cavalry. It may not move under Initiative (thus it may not Force March), but has an automatic Movement Command similar to Reinforcements (Standard Rules ¶44).

[111.] On the turn the Center of Operations moves, Dispatch Distance and Supply Distance is traced toward its initial location, so the Center of Operations moves after all Movement Commands have been issued. In the following turn the Center of Operations is inactive, while Dispatch and Supply Distance is traced to its new location (see ¶113, “Effects of Movement”).

[112.] A Center of Operations may not make an Extended March (see ¶119). It may not enter an enemy ZOC. It is never considered part of a Force, does not require a Leader, and does not count for stacking purposes. It is not subject to Attrition. A Center of Operations may enter any terrain. However, it must end its turn on a primary road hex in order to activate during the following turn (see ¶113). It has no Combat Strength or ZOC, cannot block the Enemy LOC or Dispatch Distance, and cannot damage bridges.

Effects of Center of Operations Movement

[113.] If a Center of Operations moves, it is inactive until the Consolidation Segment of the next friendly Movement Phase (II.e). However, so long as it has a LOC, units in Supply Distance still get the benefit of the Accumulated Administrative Point Total when determining Attrition; they are not automatically considered out of Supply Distance simply because the Center of Operations has moved. However, an army with an inactive Center of Operations may issue no Movement Commands or replacements or receive APs.

Example: The Austro-Russian Player moves his Center of Operations in Turn 1, and flips it to its “Inactive” / "No LOC" side. In that turn he added Administrative Points normally and issued Movement Commands. In his Administration Segment of Turn 2, he adds no Administrative Points, and issues no Movement Commands during the Movement Phase, but turns the Center of Operations back over to its “Active” (face-up) side. Thus, during his Combat Phase of Turn 2 and thereafter, the Austro-Russian Center of Operations is active.

“Flight”

[114.] The Center of Operations may never be captured. Instead, it must “flee” when placed in an Enemy ZOC or when an Enemy Force moves into the hex it occupies. If forced to flee, it is moved five Movement Points toward any Supply Source of that army free of Enemy ZOCs, at the owning Player’s choice. When displacing it ignores the presence of enemy Forces (in effect, the staff is reestablishing it further back along the LOC). Flight does count as movement; the Center of Operations is inactive on the turn after fleeing.

[115.] If the Center of Operations is forced to flee and all of its possible Supply Sources are in Enemy ZOCs, it’s flight goes off the map. If the Supply Source is not in Enemy ZOCs, it retreats no farther than the Supply Source.

[116.] If displaced off the map, the Center of Operations may return to any possible friendly Supply Source hex during the friendly Movement Phase after the hex is cleared of Enemy ZOCs.

II.b.1. MOVEMENT COMMANDS

[117.] Movement Commands are created and issued to the individual Forces of an Army during the Move-ment Command Segment (II.b.1). One Administrative Point is deducted from the Accumulated Administrative Points for each Movement Command created. Movement Commands may not be created if the Center of Operations currently has no Line of Com-munications. (Previously accumulated Administrative Points, in this case, are available for use after reestablishment of the LOC.)

II.b.1. Issuing Movement Commands

[118.] In order to receive a Movement Command, a Force must start the Movement Command Segment within Dispatch Distance of the Center of Operations of its army. In the case of a multi-hex Force, only the Force Leader need be within this distance. One Move-ment Command is expended for the Force, regardless of its total strength or the distance of its March, so long as it is not making an Extended March.

II.b.2 Extended March

[119.] Any Force activated by a Movement Command may increase the Movement Allowance of all its units by up to 4 Movement Points by immediately expend-ing one additional AP. This increase is termed Extended March. Forces making Extended March resolve attrition only once, at the end of their combined normal and Extended March, adding up to 4 to the Attrition Die Roll (see ¶120).

[120.] When determining attrition, use the line corresponding to the total distance of the march. Then add one to the die roll for each Movement Point of Extended March taken.

Example: Davout’s March north from Vienna. Davout leads a French Force initially comprising 8 SPs of Friant’s and Viallanes’ units (later adding Bourcier’s unit en route) and uses his leader bonus.

29-30 November. Vienna to Musoff. 9:30 PM, 29 November: Departed from Vienna. Forced March 5 MPs to 2945—Die 5—Loss 2 SPs. With 8 SPs and 7 APs, the Force will use the 3rd line in the body of the chart to find its attrition loss. The first die is a 6 + 4 (F.M. mod.) -1 (Leader) = 9.

Extended March: 9 MPs to 2221—Die 6—Loss 1 SP. Now the force strength is 6, so the 2nd line is used. The 2nd die is a 6 + 4 (Extended) -1 (Leader) = 9. Picked up Bourcier’s cavalry division (2 SPs) in Nikolsburg, PM on the 30th.

1-2 December. Musoff to Sokolnitz. FM 5 MPs to 2025—Die 3—Loss 1 SP. The 3rd die is a 3 + 4 (F.M. modifier) - 1 (Leader) = 6 (With Bourcier’s addition the Force strength is back up to 8, so once again the 3rd line is used). Arrived Raigern Abbey 7 PM, 1 Dec.

Departed at 5:30 AM—arr. Sokolnitz 8:30, 2 Dec. March 2 MPs—Die 6—No Loss The 4th die is a 6 - 1 (Leader) = 5. Total loss: 4 SPs.

Note: If in Forage Mode, Forces making Extended March must use the “No LOC” Column.

ADMINISTRATIVE MARCH

[121.] A Force of a single leader, plus the units on his track (but no subordinate leaders), may make an Administrative March. This is a pre-programmed march over two Game-Turns. It may not include Forced or Extended March. Only one Administrative March per player may be under way at any one time.

[122.] To be eligible, the one-leader Force must be seven or more hexes away from the nearest Enemy Force throughout its route of march. Its destination, specified in advance, cannot be changed. If it comes within seven hexes of an Enemy Force it must stop and its Administrative March is terminated. PROCEDURE:

[123.] Expend one Movement Command (this covers the entire two-turn Administrative March). Write down the exact hex of destination to be reached at the end of two marches. Move the force normally in the two Movement Phases.

[124.] Extra Cost for Exiting ZOCs (See Standard Rules, ¶128) If the adjacent Enemy force has only 1 SP, there is no additional cost to exit; if 2 SPs, the cost is +1 to exit. Cavalry pays no additional cost to exit unless the enemy hex also contains one SP or more of cavalry. A Force in Forage Mode exerts a ZOC only in the hex it occupies.

II.c.1. CAVALRY DIFFERENTIAL INITIATIVE MODIFIER

[125.] In any case where the Initiative Comparison Matrix is consulted to determine a Resistance Modifier, the side with superiority in cavalry may receive an Initiative Modifier. This rule supersedes the Pursuit modifier for exclusively-cavalry forces in the Standard Rules (¶189-2). The Maximum Cavalry Modifier is plus or minus three.

Determining Cavalry Superiority

[126.] Count the amount of cavalry present. When counting cavalry strength for purposes of determining cavalry differential, count only the cavalry actually adjacent to the active force. Do not count cavalry in mountain. • Determine cavalry superiority (which side has the most); cavalry strength may not be withheld. • Divide the stronger side’s cavalry strength total by the weaker side’s total • Refer to the Cavalry Differential Modifier Table. • If one side has no cavalry, the modifier equals the number of Strength Points of cavalry on the other side (to a maximum modifier of plus or minus “3”). • If Pursuing, add (or subtract) the cavalry differential to the leader Resistance Modifier and apply this combined modifier to the Pursuit Die Roll. • If making a Forced March out of an enemy ZOC, the Cavalry Differential Modifier can only be used to negate a “+” modifier from the Initiative Comparison Matrix. That is, Initiative cannot be better with combined Cavalry Differential and Resistance Modifiers than it would have been if the Force were not adjacent to the enemy. Example: Active Initiative 4, Passive 2, would mean no Cavalry Modifier. • Cavalry need not suffer any Strength Point loss in the combat to contribute to the Cavalry Modifier.

II, IIIa. FORAGING ATTRITION

[127.] In addition to the normal Attrition Procedure (given in Standard Rules ¶137), forces may also use the Foraging Attrition procedure. If a Force is not within Supply Distance of the Center of Operations, a Depot, or Supply Source, it must Forage or use the “zero” column on the Attrition Table. Any force may Forage.

Forage Mode

[128.] When an army could not supply its troops, its soldiers would disperse and forage for their own provi-sions and fodder in the countryside. A Force must be in Forage Mode in order to Forage (see ¶132). If a Force is not in Supply and does not forage, it must use the column on the Attrition Table headed “No LOC.” (A player may prefer to use the “No LOC” column at times when the nearness of the enemy makes it too dangerous to enter Forage Mode.) Any eligible non-besieging Force may begin a scenario in Forage Mode at the owning Player’s option.

[129.] If a Force is eligible to Forage and is also within Supply Distance of the Center of Operations, Depot, or a Supply Source at the beginning of its regular Movement Phase or Forced March Segment, the owning player may elect to use the Forage Procedure or the Accumulated Administrative Level when determining Attrition.

Foraging Procedure

[130.] A Force must be in Forage Mode in order to Forage. The player adds together the Forage Value of the hex the Force occupies and all of the adjacent hexes the Force could legally occupy. On the line labeled “Forage,” find the corresponding column on the Attrition Table instead of APs Accumulated. The quality of the forage depends solely on the total value of the Force Leader’s hex and the hexes in his ZOC(see ¶137 & ¶140).

[131.] Determine the appropriate Attrition Table Column individually for each separate Force. Forces in Enemy ZOCs may forage, and they may remain in Forage Mode in an Enemy ZOC.

Example: A force in a Secondary Town surrounded by clear terrain has a Forage Value of 10.2. The size of the force would be found under the heading “9+.”

Concentrated and Forage Mode

[132.] Forces operate in two modes. A Force is in Concentrated Mode unless marked with a “forage” marker on the Force Leader’s display. Forage markers are used to designate all Forces in Forage Mode. The Force changes Mode during March or Forced March. Changing to Forage Mode costs one-half Movement point. Changing to Concentrated Mode costs three Movement Points. You may attempt to change to Concentrated Mode in an Enemy ZOC through Initiative. A Force in Forage Mode does not suffer Resistance Modifiers. Individual Forces may begin play in either mode, at the owning Player’s option.

[133.] To Forage, a Force must be in Forage Mode upon completion of all Movement Point expenditures for that Phase and may not have executed an Extended March. Forces in Forage Mode may enter Enemy ZOCs (see ¶138).

[134.] A Force in Forage Mode exerts a flexible ZOC. This is treated just like Vedettes which also have a flexible ZOC (see ¶74, “Vedettes and Zones of Control.”) Enemy Forces may enter and/or leave a hex adjacent to an enemy Force in Forage Mode without stopping or having to suffer a resistance modifier.

[135.] When defending, a force in Forage Mode suffers a shift of two columns to the left, and may choose Battle type freely. The force can roll to attempt to change mode after each round of combat. (If a Force in forage mode joins another one not in forage mode, a one-column shift is applied.) Forces in Forage Mode are repulsed at 4-1 odds instead of 7-1 odds. A Force in Forage Mode may attack (no special shift), alone or in concert with a Friendly Force in Concentrated Mode, and may choose battle type freely.

Forage Ratings

[136.] Woods—0 Hills—0.5 Mountain—0 Clear—1.2 Town—3 Depot—4 Citadel—6

How to Determine Forage Value

[137.] Total the Forage Rating of the seven hexes adjacent to and occupied by the Force Leader in his final resting place at the end of the phase. (Exceptions: see ¶138 et seq.)

Example of Foraging Attrition

Effects of Enemy ZOCs on Foraging

[138.] Units in Enemy ZOCs may Forage; however, neither an enemy-occupied hex, nor a hex with enemy forces adjacent on opposite sides, may be foraged. Example: If Enemy forces (even merely Vedettes) occupy 2318 and 2517, 2417 may not be foraged. Exception: Besieged Citadel hexes with besieging enemy forces adjacent on opposite sides may be foraged; since they are without an LOC they must disregard the depot (this supersedes ¶59).

Foraging of Multi-Hex Forces

[139.] In determining Forage Value, count all hexes occupied by and adjacent to the Force Leader only. Count each hex only once, and determine one total for the entire Force. Separate Forces which move to adjacent hexes—or to the same hex—must still resolve attrition separately.

Overlapping Forage Areas

[140.] The Forage Rating of a hex eligible to be Foraged by two or more Friendly Forces must be divided between those Forces as the player sees fit. A hex may not be counted twice. Example: Soult and Lannes arrive in Brünn by two different roads. Only one of them could forage the hex of Brünn; the other might be allowed to forage all the surrounding hexes.

Town Forage

[141.] A Force must end its move in a secondary town, citadel, or depot hex in order to count its Forage Rating as part of its total Forage Value. Town hexes adjacent to part of a Force which are unoccupied by a component of that Force are skipped over, counting as the value of the other terrain in the hex. (A Force in a town may count the Forage Value of surrounding countryside.)

Citadels

[142.] Besieged units may forage the hex they occupy. The Forces there may forage the hex they occupy at a forage value of 6. A die roll modifier applies to attrition of besieged forces (see ¶59).

II. BRIDGES

[143.] Any road crossing a Primary River hexside is a Primary Bridge. All roads crossing Secondary Rivers are Secondary Bridges. To damage or repair bridges requires the expenditure of a certain number of MPs. (Refer to the Bridging Summary table.) Primary Bridges have a higher MP cost to damage or repair, and may not be affected by all-cavalry forces. There are also MP costs to deploy or remove Pontoons. Unlike all other Movement Point costs, MPs expended relative to the damage, repair, deployment and removal of bridge structures do not count toward the total expended for determining Attrition. A Force which expends Movement Points relative to bridge structure (i.e. any Movement Points shown in the Bridging Summary table) may not make an Extended March that phase.

Damaging Bridges

[144.] A force can damage a bridge during a friendly Movement Phase by expending additional Movement Points according to the Bridging Summary in a hex adjacent to the bridge hexside.

[145.] Place a Damaged Bridge marker on the damaged bridge. For movement purposes, a damaged bridge does not exist until it is repaired.

Repairing Bridges

[146.] A Force can repair a damaged bridge during a Friendly Movement Phase by expending a number of additional Movement Points per bridge according to the Bridging Summary in a hex adjacent to the bridge hexside. If an Enemy Force occupies the other hex adjacent to the bridge hexside, the bridge cannot be repaired. If an enemy Force occupies any other hex adjacent to the repairing force, add “three” Movement Points. Once the repair is completed, the Damaged Bridge marker is immediately removed.

II. BRIDGE TRAINS

[147.] The Austro-Russian Player receives two bridge trains, one of which is assigned to Kutusov, and the other to Buxhöwden. The French Player receives one bridge train which he may place with any leader at the beginning of the scenario. A bridge train travels with a Force, and its marker is kept on its Leader’s track until it is deployed.

[148.] Bridge Trains have no Combat Strength or Subordination cost—their Movement Allowance is 5.

[149.] A bridge train can be used to bridge any river, primary and secondary alike. A bridge train cannot be destroyed, damaged, or repaired, but it may be captured. Note that a bridge train cannot create its own Major General, may not make an Extended March, may not retreat, and may not form part of a pursuit force. If abandoned it can be placed in the currently-occupied hex on the map (bridge-train side up). It has no Combat Strength. Deployed bridged trains are called pontoons, and bridge train markers have pontoons on their reverse sides.

Capturing Bridge Trains

[150.] Undeployed bridge trains are left in place on the map if the Force they are with makes a pursuit, or is forced to retreat, etc. Any time an enemy Force enters a hex containing an undeployed friendly bridge train, the bridge train is considered the enemy’s bridge train for all purposes. Undeployed Bridge Trains may not be damaged. Either Player may capture such an abandoned bridge train by occupying or passing through its hex with any Force, including during Pursuit. A deployed pontoon may be captured by expending 2 MPs (see ¶152).

Pontoon Deployment

[151.] A bridge train on a Leader’s track is considered to occupy the same hex as the Leader. During any friendly Movement Phase that the Leader occupies a hex adjacent to a river hexside and his Force expends 3 additional Movement Points to deploy the bridge train, he can place the pontoon on the map at the appropriate hexside. A pontoon can be used as soon as it is deployed. To remove a friendly deployed pontoon from the map, a friendly Leader must expend 2 additional Infantry Movement Points in either hex adjacent to the pontoon hexside during the Movement Phase. Note: a deployed pontoon cannot march or retreat.

[152.] A Leader who carries a bridge train on his Organization Display could abandon the bridge train and then leave the hex (although he may run the risk of an enemy Force capturing the pontoon). At a later date, the same or another Leader could expend 2 MPs in the bridge train hex during a march and place it back on the Leader track.

IV. VIENNA MORALE

[153.] The French occupied Vienna on November 11th 1805. However, the Imperial Court withdrew in time to unite with the Russian Armies. The term “Vienna Morale” in this sense refers to the Court of Vienna. The Archduke Charles with an army of 80,000 men would have been in a position to recapture Vienna or to unite with the Coalition Forces on the map by the last turn of the Campaign Game.

[154.] Austro-Russian morale is recorded on the Vienna Morale Track. Morale may be positive, zero, or negative. If Vienna Morale is between +4 and -5 (exclusive) at the end of the last Game-Turn, the Level of Victory is determined by the Levels of Victory Chart (¶200). At the start of each Scenario, place the Vienna Morale Marker on the zero space of the Track (see ¶195); thereafter morale will change as defined in the Standard Rules and as below:

Capture of Political Features

[155.] In addition to Morale Changes as outlined in the Standard Rules (¶193-195), Vienna Morale also changes by one for the capture of each town listed below. To acquire the morale shift the player must succeed in entering a named leader with 4 infantry SPs or more into the town. These effects are reversed if the town is recaptured. The Russian Player cannot acquire these points in games starting on 15 Nov. • French Player captures Olmütz: Morale -1. • Austro-Russian captures Brünn: Morale +1. • Austro-Russian captures Pohrlitz: Morale +1.

[156.] Effects of Morale on Ending the Game At the end of any Game-Turn in which Vienna Morale is +4, the game is over and the Austro-Russian Player wins. At the end of any Game-Turn in which Morale is -5, the game is over and the French Player wins (see ¶200).

[157.] Effects of Morale on Determining Victory Level of Victory depends upon the current Morale at the end of the Campaign Game (see ¶200).

[158.] Negotiation Table At the end of each Game-Turn, the French Player will roll one die on the Negotiation Table. The French Player must continue rolling each turn until he re-ceives an “Austro-Russian refusal” result or a “Negotiation” result. Upon occurrence of Austro-Russian refusal the French player must begin to roll on the Ultimatum Table. If “Negotiation” results, there will be a temporary halt in active operations by both sides, of up to four turns in duration. Both sides get to take their next Movement Phase—moving according to the priorities of retreat—but after that neither side will have any more Movement or Combat Phases during these turns of Negotiations—all forces are considered to be in forage mode. Since there was little chance of success behind these negotiations, they will generally not lead to a peace treaty, and regular play will resume. Negotiations can occur more than once per game. (See the Negotiation Table.)

[159.] Ultimatum Table At the end of each turn after a result of “Refusal” the French Player will roll on the Ultimatum Table. If "Prussian Ultimatum" results on this table, the definition of the Levels of Victory will change (see ¶200). Two turns after occurrence of the Prussian Ultimatum, the Prussian units Grawert, Louis, Holzendorf and Schimmelpfennig arrive under the command of Leader Hohenlohe, on hex 1301, at maximum strength.

[160.] Effects of Vienna Morale on Attrition The Austro-Russian Player must always subtract the current Vienna Morale from the die roll when determining Attrition. If Morale is negative, subtract-ing a negative will result in a positive modifier (see Standard Rules ¶138). French Attrition die rolls are not affected by Vienna Morale.

Optional Rules

III.b.3 REARGUARD BATTLE TYPE

[161.] Rearguard adds a third battle-type option, along with Pitched and Pursuit. In a Rearguard Action, like a Pitched Battle, additional “rounds” of combat are possible. The combined total of Pitched and Rearguard battle chosen may not exceed the Initiative Rating of the Leader.

[162.] Rearguard battle type allows the selecting player (only) to implement his (losing) combat result partially in hexes retreated, and partially in Strength Points lost. The exact proportions are up to him.

[163.] The subsequent Pursuit may cause further loss of Strength Points. When determining the Pursuit, the active player uses only the portion of the combat result executed as “hexes retreated” to cross reference with his pursuit die roll. (He may voluntarily shorten the pursuit.) If at the conclusion of the pursuit the two Forces are adjacent, another round of battle ensues (see Standard Rules ¶196, “Pitched Battle”).

III.b.3. THE SOUND OF GUNS

[164.] Commentary: It was customary in written orders to specify that a force should maneuver toward the sound of the guns. Generals would ride out from headquarters until within earshot of cannonfire— sometimes with ear to the ground—and would be able to determine from listening what was happening. The maximum distance the sound could carry, except in really large bombardments, seems to have been about ten miles.

[165.] This rule can be used only by a Force that failed its regular Forced March Initiative die roll and that began the Combat Phase within five hexes of an Enemy Force about to attack a Friendly Force. If successful it may expend one MP per round of combat.

[166.] Such a Force may attempt to Force March before the commencement of the second and again before each succeeding Round of Pitched Battle (see Standard Rules ¶102) until it has made a successful Initiative die roll. It must march “to the sound of the guns”—directly to the battle only.

III.b.12. BATTLEFIELD DYNAMICS

(Controlling the Battle)

[167.] In a Pitched or Rearguard Battle prior to each player’s counterattack (or reattack),* the player about to attack rolls the die:

| Die | Result |

|---|---|

| 0, 1 | Take a Retreat instead of attacking |

| 2 | No attack (remain in contact)—like Bye Battle |

| 3, 4 | Must counterattack (or re-attack) |

| 5+ | Player maintains control of the battle |

Modifiers:

Initiative Comparison
Cavalry Differential
Snow cancels any positive modifier, and -2 to the die roll.

*i.e., before Step 12 , or before Step 1 of the second round. The phasing player does not roll prior to his initial first round attack.

[168.] Explanation of Results

Take a Retreat instead of attacking

Based on the actual die roll result of the immediately preceding combat resolution, there will be no pursuit if the enemy did not win the prior combat.

No attack (remain in contact)

Your forces remain in place. The Enemy may continue the pitched battle by attacking in a follow-up counterattack (or reattack), provided he has selected pitched battle.

Must counterattack (or re-attack)

This is the regular way (as in Standard Rules)

Player maintains control of the battle

The player about to attack may select any of the three results above and implement at once.

THE BATTLE WORKSHEET

Please make extra photocopies of this form before play.

[169.] PREPARE FOR BATTLE: • Battle name (after nearby town) and date. • Force Leader name (note bonus). • Unit Roster (all units in the Leader’s Force). • Strength Points (enter in first column). • Unit Type (draw-in to left of unit name). • Total Strength Points Committed (total strength of all committed units at bottom of first column). • Battle Chit (write-in Pit, Purs, or RG).

[170.] RESOLVING BATTLE: • Strength Points Lost: write casualties from the Attack, then from Counterattack, in boxes. (Write “R” if Force retreats, then pursuit loss.) • New total (subtract losses from Total Committed). • Revealed? (when Battle type chit is revealed).

[171.] LOSSES: Record new strengths for each unit to the right.

[172.] SUCCESSIVE ROUNDS: • note fresh Strength Points committed in “+” spaces between boxes on the Total Strength Points Committed track, then add that to the “New Total” of previous round’s “Ctr” column. • Enter the sum in the next box of the “Total Strength Points Committed” Track, and begin the next round. • At the conclusion of the last round of battle, make all adjustments at once on the Organization Display.

How to Set-Up the Game

[173.] Select a scenario, and set-up according to the Leader Manifests and Unit Manifests. Sort out the counters that are not used (see ¶26, “Replacement & Variant Counters ”)‚ then sort the remainder by army (Austrian, Russian and French) and then into the following categories: Major Generals, the other Leaders, Vedettes, named Combat Units, March Regiments, Markers and other counters.

UNIT & LEADER MANIFESTS

[174.] The initial placement for the combat units and leaders is given on the Unit and Leader Manifests per scenario. Place all the units and leaders on their respective manifests before transferring the units to the Organization Displays, and the Leaders either to the Displays or to the map.

[175.] Combat units are listed on the Unit Manifests. Beneath the headings corresponding to the various scenario start dates you will see the leader whose track they set up on and their individual unit strengths. Combat units listed with a Leader’s name should be placed on that Leader’s track on the Organization Display to denote they are part of his Force.

[176.] If “Repl.” appears, the unit or leader in question does not begin in play in that scenario, but is available as a reinforcement. If a unit it may be filled-up with Strength Points like a March Regiment. If “NA” or “O.M.” appears, the unit or leader is not available in that scenario. Set-up Reinforcement units and leaders on the Turn Record Track.

ORGANIZATION DISPLAYS

[177.] Place the combat units on the numbered track spaces corresponding to their listed strength. (See Standard Rules ¶19, “Organization Displays”.) Leader manifests may specify the name of the Force Leader or a hex on the map. Place subordinate leaders (who have a Force Leader specified) on the Force Leader’s portrait to denote they are part of his force.

Example: In Scenario III, Murat’s track contains Kellermann, Nansouty and d’Hautpoul (as shown on the French Unit Manifest). Murat himself sets-up in the same hex as Napoleon, and therefore his leader counter should be placed on Napoleon’s portrait.

Major Generals

[178.] Combat Units that have a separate set-up hex use Major Generals as their Leaders. Use the Major General of the appropriate type (infantry or cavalry) and designation. Example: In Scenario II, Bourcier sets-up on the track of Major General Cavalry 1, in hex 3837 (as specified on the French Leader and unit Manifests).

Scenario Information Detail

[179.] The Scenario Information is explained below. There are three categories: Battle Scenario information, Campaign Scenario information, and general information that applies to both Campaign and Battle Scenarios.

GENERAL INFORMATION

First Player

[180.] In all scenarios of The Sun of Austerlitz, the Austro-Russian Player is the First Player.

Game Start

[181.] Place the Game-Turn Marker on the Turn Record Track on the date specified in the Scenario Information as the start of the scenario.

Supply Sources At Start

[182.] Supply Sources may be freely chosen by the players in any hex listed for that army on the Communications Table. In addition, in the Battle Scenarios only, any depot in Communications may be chosen; in the Campaign Game, Supply Source hexes are on the mapedge only. Once assigned, the Supply Source may only be changed as specified under ¶31 Changing the Supply Source.

Garrisons

[183.] At the start of each scenario, in addition to the Supply Source garrison, each player may place Garrison markers as specified in the scenario instruc-tions. They act like S/S garrisons (see ¶37). If Brünn or Olmütz are captured, the capturing player may create a garrison by deducting one SP from an infantry unit in the hex.

Administrative Point Levels

[184.] The Accumulated AP Levels, specified for each side in each scenario, show where on the Accumulated AP Track to place the AP Level Markers (x1, x10) at the start of the scenario. Each player will use the Attrition Table column corresponding to the number of Accumulated APs.

[185.] In the Battle Scenarios this level will remain constant throughout the game and will be used to determine the proper column to find while rolling for attrition.

[186.] In the Campaign Scenario, each time a Movement Command is used, reduce the AP Level by one (see ¶85).

BATTLE SCENARIO INFORMATION

Scenario End Date

[187.] The Battle Scenarios end with the conclusion of the turn specified as the end of the scenario on the Turn Record Track.

Movement Commands Available

[188.] These levels specify the number of movement commands available each turn, per side, in the battle scenarios only.

Reinforcements

[189.] Any combat unit that is not in play at the start of the scenario may be introduced into play by the owning Player as a reinforcement unit—as specified on the Turn Record Track—during the Reinforcement Segment of the Movement Phase (see Standard Rules, ¶89, ¶91, and Exclusive Rules ¶106, ¶176, ¶199 and ¶200).

Victory Conditions

[190.] The Victory Conditions for Battle Scenarios Two and Three are presented in the Battle Scenario rules. (See ¶65, “Battle Scenario Victory Conditions.”) Special Victory Conditions apply to Battle Scenario One (see ¶97).

CAMPAIGN SCENARIO INFORMATION

Scenario End Date

[191.] The Campaign Scenario ends with 15-16 December 1805 (exception: see ¶156) regardless of start date (see ¶196). This was the date at which 80,000 Austrian troops under Charles were expected to be able to intervene, either attacking Vienna or appearing on the map around hex 3942.

Vedettes

[192.] Vedettes can be placed at start according to the rules governing their placement (see ¶69).

Centers of Operations

[193.] The Centers of Operations may be set-up freely at the owning player’s discretion.

[194.] Both Centers of Operations are Active at the start of the Campaign Game. Note: the French Player receives no new APs on the 15-16 Nov. turn.

Vienna Morale

[195.] The Vienna Morale Marker begins every scenario at “zero.”

Scenario Information

[196.] In The Sun of Austerlitz there are three battle scenarios: The Maneuver of Hollabrunn, The Austro-Russian Advance, and The Battle of Austerlitz. In addition to these three, the Campaign Game can start on 15-16 November or 27-28 November.

SCENARIO I — The Maneuver of Hollabrunn

[197.] Game Start: 15-16 November.

Accumulated APs:

FRENCH 3, AUSTRO-RUSSIAN 10 Battle Scenario End Date: 25-26 November

Movement Commands Available:

FRENCH 2, AUSTRO-RUSSIAN 2. FIRST TURN: French 1, Austro-Russian 3. GARRISONS: Russian—Brünn, Olmütz. VICTORY: Kutusov and 18 of the same SPs from his original starting force occupy Olmütz.

SCENARIO II — The Austro-Russian Advance

[198.] Game Start: 27-28 November

Accumulated APs:

FRENCH 7, AUSTRO-RUSSIAN 20 Battle Scenario End Date: 11-12 December

Movement Commands Available:

FRENCH 3, AUSTRO-RUSSIAN 2. FIRST TURN: French 2, Austro-Russian 4. GARRISONS: French—Brünn, Russian—Olmütz.

SCENARIO III — The Battle of Austerlitz

[199.] Game Start: 1-2 December

Accumulated APs:

FRENCH 10, AUSTRO-RUSSIAN 15 Battle Scenario End Date: 11-12 December

Movement Commands Available:

FRENCH 3, AUSTRO-RUSSIAN 2. FIRST TURN: French 3, Austro-Russian 2. GARRISONS: French—Brünn, Russian—Olmütz.

Special Rule: Gudin’s Arrival

Gudin’s Division was sent for at the last minute. Roll the die on 29-30 November to determine the arrival of Gudin’s Division. (Klein’s cavalry will accompany Gudin as part of his force.)

Note: The Turn Record Track shows the “Historical” arrival of Gudin’s division. Unlike other reinforce-ments, the units of Davout’s III Corps arrive during the French Forced March Segment of the specified turn, and may automatically move their maximum Movement Allowance during the entry segment.

Die roll results:

| Die roll | Result |

|---|---|

| 1 | Gudin‘s Force arrives 1 turn earlier than shown. |

| 2-3 | Gudin‘s Force arrives historically. |

| 4-5 | Gudin‘s Force arrives one turn late. |

| 6 | Gudin‘s Force arrives two turns late. |

THE CAMPAIGN SCENARIO

[200.] Game Start: 15-16 November Scenario End Date: 15-16 December Alternative Start Date: 27-28 November. Accumulated APs: Same as the Battle Scenario with corresponding date. Automatic Victory: (see ¶156)

Other Levels of Victory:

If neither automatic condition (see ¶156) is met prior to the end of the game, the level of Vienna Morale at the end of the game determines the Level of Victory. This depends upon whether the “Prussian Ultimatum” result has occurred or not (see ¶159).

| Vienna Morale | With Ultimatum | Without Ultimatum |

|---|---|---|

| +3 | Aus.-Rus. Strategic | Aus.-Rus. Operational |

| +2 | Aus.-Rus. Operational | Aus.-Rus. Tactical |

| +1 | Aus.-Rus. Operational | Aus.-Rus. Tactical |

| 0 | Aus.-Rus. Tactical | Aus.-Rus. Marginal |

| -1 | Aus.-Rus. Tactical | Aus.-Rus. Marginal |

| -2 | Aus.-Rus. Marginal | Draw |

| -3 | Fr. Marginal | Fr. Tactical |

| -4 | Fr. Tactical | Fr. Tactical |

Part 4: Sequence of Play and Tables

Expanded Sequence of Play

The two-page "Campaigns of Napoleon 1X Consolidated Rules Expanded Sequence of Play" sheet reproduces the Sequence of Play (Weather Determination Phase; First Player-Turn with the Command, Movement, Combat and Morale Phases; Second Player-Turn) and the Battle Resolution step procedure (Steps 1 to 18) word for word as they appear in the Consolidated Rules. See "Sequence of Play" (¶49-¶68) and "Combat" (¶298-¶301, with Steps 1 to 18 in ¶300) in Part 1.

Charts and Tables

Tables are reproduced from "The Campaigns of Napoleon: Common Tables for All 1x Games" and "Exclusive Tables for The Sun of Austerlitz [1805]." In the Combat Results Table, the number shown in bold is the number printed in bold italics in the original (the losing side's number). Rows or notes that apply only to other games in the series (1807 asterisk note, other games' Communications Table rows) are omitted.

Combat Results Table

Attacker's Strength to Defender's Strength. Each column shows the odds for Not affecting terrain / Affecting terrain. Results are Attacker/Defender. A result with a bold number indicates the losing side (retreating if Pursuit Battle); the original also emphasizes with a blue background that the attacker loses.

Die	1-5 / 1-4	1-4 / 1-3	1-3 / 1-2	1-2 / 2-3	2-3 / 1-1	1-1 / 3-2	3-2 / 2-1	2-1 / 3-1	3-1 / 4-1	4-1 / 5-1	5-1 / 6-1	6-1 / 7-1
0	3-2	3-3	2-3	2-4	1-4	1-4	1-5	1-6	0-

KEY: # = number of Strength Points lost or number of hexes retreated: Attacker/Defender.

Column Shifts:

Shift	Condition
2 left	Attack following an unsuccessful repulse (¶243)
1 left	Besieged Force attacking Besieging Force (¶351)
1 right	Some defenders are in Forage Mode (¶281)
2 right	All defenders are in Forage Mode (¶281)

Die Roll Modifiers:

Modifier	Condition
-1	In attacks at greater than the rightmost column, for each magnitude greater than that column (¶351)
-1	Old Guard is staked in French attack or counterattack (¶363)
+/- 1	For each Bonus Point of the Attacking Force Leader (owning player's choice of direction; may ignore) (¶365)
+1	In attacks at less than the leftmost column, for each magnitude less than that column (¶351)
+1	Attack during Snow or Severe (¶345 and ¶346)

Artillery Fire Table

Die	1	2-3	4-5	6-7	8-9	10-11	12-13	14+
0	1	1	2	3	3	4	5	5
1	1	1	2	3	3	4	4	5
2	0	1	1	2

(Column headings are Artillery Strength.) KEY: Nr. Result shows enemy loss in Strength Points. Remove losses as evenly as possible from the individual units.

Die Roll Modifiers:

Modifier	Condition
-2	40 or more SPs in target hex (¶347)
-1	30 to 39 SPs in target hex (¶347)
-1	Cavalry Differential greater than or equal to 2:1 (¶340)
-1	Leader Bonus Point (¶46)
+1	Rain, Snow, Severe (¶343-¶346)
+2	Mud or Rain/Mud (¶344)
+1	Firing into Mountain hex (¶348)

Bridging Summary

Bridge Type	Type of River	Capacity	Damage	Destroy	Repair	Capture
Permanent	Primary	Unlimited	3 CNP	NP	5 CNP	NP
Permanent	Secondary	Unlimited	2	NP	4	NP
Bridge Train/Pontoon*	Either	1 Force/Phase	2	NP	2 CNP	0/2 CNP**

KEY: # = Number of MPs expended to perform action. (MPs expended for bridging do not count towards attrition.) NP = Action not permitted. CNP = All-cavalry Forces not permitted.

* = It costs 3 MPs to deploy a bridge train into a pontoon, and 2 MPs to disassemble a pontoon into a bridge train. It costs a Force its full MA to deploy a pontoon if an enemy Force is adjacent (including across the hexside being bridged).

** = Cost to capture an enemy bridge train/pontoon.

Add one MP to Damage (and Repair is Not Possible) if an enemy Force occupies the other hex adjacent to the hexside.
If an enemy Force occupies any other hex adjacent to the repairing force, add three Movement Points if the bridge spans a Primary River, and one Movement Point if a bridge spans a Secondary River.

Pursuit Table

Length of Retreat (in hexes), by Unmodified Initiative of the Pursuing Leader (columns 1 to 11, left to right; a dash is a blank cell):

Unmodified Initiative	1	2	3	4	5	6	7	8	9	10	11
0, 1	-	-	-	8+	7	6	5	4	3	2	1
2	-	-	8+	7	6	5	4

Length of Advance (in hexes), by modified die roll, in the same eleven columns:

Die	1	2	3	4	5	6	7	8	9	10	11
-1, 0	8	8	7	6	5	4	3	2	1	•	•
2, 1	8	7	6	5	4	3	2

Cross-reference length of retreat with unmodified initiative of pursuit leader. Then roll die, modify, and locate the result on the line beneath the retreat length just found. The result is the advance in hexes.

The length of advance determines pursuit losses to retreating side. Forces may not pursue into the last hex of retreat unless the losing side failed to retreat the full distance. A Force may not advance into the hex vacated by the losing side unless the result from the table is 1 or greater. A force may not pursue further in hexes than the number of SPs in the force.

A Force which retreats across a river loses double its normal pursuit loss if pursued to the river hexside.

Cumulative Die Roll Modifiers (¶390):

Modifier	Condition
+/- ?	Resistance Modifier (see below).
-1	If the Pursuing Force consists exclusively of French Guard units or units released from Reserve.
+1	For each Round of Pitched Battle revealed by the Pursuing Force (NA to units released from Reserve).

Initiative Comparison Matrix

Active/Pursuing Leader's Initiative across the top; Passive Leader's Initiative down the side.

Passive Leader's Initiative	1	2	3	4	5
0-1	0	0	0	0	0
2	+1	+1	+1	0	0
3	+1	+1	+1	+1	+1
4	+1	+2	+2	+2	+1
5

KEY: Resulting number is Initiative Die Roll Modifier.

Cavalry Differential Modifier

Passive Side Superior: 1:3	1:2	1:1.1	Equal: 1:1	Active Side Superior: 1.1:1	2:1	3:1
+3	+2	+1	0	-1	-2	-3

KEY: Resulting number is the Cavalry Differential Modifier. Example: The modifier is -2 if the ratio is at least 2:1 but less than 3:1.

Resistance Modifier Calculation (¶196)

The Resistance Modifier equals the sum of the following:

Modifier	Component
0 to +2	Initiative Die Roll Modifier
-3 to +3	Cavalry Differential Modifier
+1	For Pursuit when weather is Rain or Snow
-1	For ZOC exit when weather is Rain or Snow

NOTE: A Force in Forage Mode does not suffer Resistance Modifiers.

1X Series Communications Table (The Sun of Austerlitz [1805] entries)

Army	Dispatch / LOC Distance	Supply Sources & Notes
French	18 MPs	1154, 2854
Austro-Russian	18 MPs	0101, 1401, 2501, 3701, 3929, 3918
LOC	40

Available Supply Sources: A Supply Source occupied by enemy units or not capable of activation due to off-map enemy units does not count as a possible Supply Source.

Lines of Communication (LOC): The LOC listed is the maximum effective length for an LOC, and applies to both sides in a game (see ¶80). It must consist of Primary Road hexes. The Effective LOC may be reduced if traced through a friendly controlled depot (see ¶89).

Depots: A depot is "functional" unless under enemy control. Depots include: printed depots, any possible Supply Source, and any Center, City, Primary Town, or Fortification (see ¶90) that has a valid LOC to any possible Supply Source.

Dispatch Distance: Dispatch Distance is the maximum distance between the Center of Operations (or a depot) and a given Force, traced from the Center of Operations (or the depot) to the Force Leader (see ¶86). A valid Dispatch Distance allows the following:

If traced from an active Center of Operations, the Force may (a) Receive a Movement Command, (b) Receive a Replacement Point, and (c) Benefit from the Army's Accumulated AP Total when determining attrition; if beyond that distance, that force must forage or use the zero line of the Attrition Table.
If traced from a depot or Supply Source, (c) only applies.

A Center of Operations must have a LOC traced from the active friendly Supply Source. A depot may have a LOC traced from any possible friendly Supply Source.

Tracing Distances: Primary roads count as 1 MP (not 1/2 MP) when tracing Dispatch Distance. Otherwise, use the Cavalry cost for each hex.

March Attrition Table (1805)

The original prints this as one staggered table whose two blocks (March Distance / Modified Die Roll, and Size of Force in SPs) share the same ten result columns. Column numbers C1 to C10 and row numbers are added here for reference only.

Modified Die Roll ranges for each column, by March Distance:

March Distance	C1	C2	C3	C4	C5	C6	C7	C8	C9	C10
0	0-2	3,4	5,6	7,8	9,10	11,12	13+	-	-	-
0.5 - 2.5	-	0	1,2	3,4	5,6	7,8	9,10	11,12	13+

Strength Points lost. Size of Force in SPs, by Accumulated APs (Forage Value in parentheses):

Row	APs 11+	APs 7-10 (Forage 9+)	APs 4-6 (Forage 6-8.9)	APs 1-3 (Forage 1-5.9)	Zero (No LOC)	C1	C2	C3	C4	C5	C6	C7	C8	C9	C10
1	1-7	1-4	1-2	-	-	0	0	0	0	0	0	0	0	1

Die Roll Modifiers (see ¶267). (* Round MPs used up.)

Modifier	Condition
-1	For each Bonus Point of Force Leader
+1	For each MP of Forced March undertaken (max +4)
+1	For each MP of Extended March undertaken
+1	If weather is Mud or Rain
+3	Starting Attrition modifier for a besieged Force

Weather Table (1805)

Month	Frost	Snow	Mud	Rain	Fair
November	0	1, 2	3, 4	5, 6	7
December	0, 1	2, 3, 4	5	6	7

Bold indicates Fog also applies (see ¶142).

Die Roll Modifiers:

Modifier	Condition
-1	If previous roll was 1 (before modifier)
+1	If previous roll was 6 (before modifier)

Administrative Point Pool (1805)

LOC Distance in Primary Road Hexes, by Army and Supply Source:

Army / Supply Source	Column 1	Column 2	Column 3
French: S/S Vienna	0-20	21-40	•
French: S/S Krems	•	0-20	21-40
Austro-Russian	0-20	21-40	•

Administrative Points received, by Dice Roll (two dice):

Dice Roll	Column 1	Column 2	Column 3
2	5	4	3
3	5	5	1
4	6	5	4
5	5	3	2
6	3	2	4
7	3	2	4
8	4	3

If the Army Commander is stacked with the Center of Operations, add 1 AP to the amount received (see ¶99).

Vienna Morale Chart

Condition	Change in Levels
French capture Olmütz (see ¶E13)	-2*
French capture Allied Major Personality (¶396)	-1
French win Critical Battle (see ¶395)	-1
Austro-Russians win Critical Battle (see ¶395)	+1
Allies capture French Major Personality (¶396)	+1
Old Guard staked but loses round (see ¶397)	+1
Austro-Russians capture Brünn (see ¶E13)	+1*
Austro-Russians capture Pohrlitz (see ¶E13)	+1*
Napoleon is eliminated (see ¶396)	+2

* Reversed if recaptured.

Negotiation Table (¶E16)

Dice roll (two dice) down the side; current Vienna Morale across the top.

Dice Roll	-5 to -4	-3	-2	-1	0	+1	+2	+3
2	•	•	•	•	•	•	•	•
3	R/A	R/A	•	•	•	•	•	•
4	R/A	R/A	R/A	R/A

• = Cease rolling on the table
R/A = Roll again at the end of the next turn
* = Roll again at the end of the next turn, except during Negotiations, when it's a French Marginal Victory
N = Negotiations ensue, with the number indicating the duration in turns (starting with the following turn); all N results after the first = R/A

Ultimatum Table (¶E18)

Die Roll	Result
-1, 0, 1	Prussian Ultimatum; do not roll again on this table
2-5	Roll again next turn
6	Prussia Quits Coalition; do not roll again on this table

Die Roll Modifiers:

Modifier	Condition
-1	Vienna Morale is +2
-2	Vienna Morale is +3

Costs to Exit Enemy ZOCs

Enemy SPs	1	2	2	3	3
Enemy cav SPs	Any	< 1	1 or 2	< 1	1+
Exiting infantry	+0	+1	+1	+2	+2
Exiting cavalry	+0	+0	+1	+0	+2

Terrain Effects Chart

TEC Notes:

Terrain effects are cumulative for movement but not for combat.
Use the Infantry column for artillery and bridge trains, and the Cavalry column for the Center of Operations. Cav. in a Force with inf. pays separate costs.
Use the Cavalry column when tracing Dispatch Distance, except primary roads = 1 MP.

Hex Type	Cost Inf.	Cost Cav.	Forage Value	Affecting	Additional Combat Effects
Clear	1	1	1.2	No	None
Mountains	4	6	0	Yes	Count 9 SPs max if attacking or pursuing into or if defending in defile
Hill	1.5	1.5	0.5	Yes	None
Woods	1.5	3	0	No	Attacking into: Inf * 0.75; cav * 0.5; no bombardment into or out of hex

NA = Not applicable

* +0 if tracing LOC or Dispatch Distance, or if moving unit entered the hex before the bridge using a road

† A Force in Forage Mode exerts a ZOC only in the hex it occupies

Dice Roll	-5 to -4	-3	-2	-1	0	+1	+2	+3
2	•	•	•	•	•	•	•	•
3	R/A	R/A	•	•	•	•	•	•
4	R/A	R/A	R/A	R/A

Dice Roll	-5 to -4	-3	-2	-1	0	+1	+2	+3
2	•	•	•	•	•	•	•	•
3	R/A	R/A	•	•	•	•	•	•
4	R/A	R/A	R/A	R/A

Dice Roll	-5 to -4	-3	-2	-1	0	+1	+2	+3
2	•	•	•	•	•	•	•	•
3	R/A	R/A	•	•	•	•	•	•
4	R/A	R/A	R/A	R/A