RulesPal
Chat
Rulebook
Kosowe Pole 1389 thumbnail

Kosowe Pole 1389

Kosowe Pole 1389 Rulebook

Table of Contents

Table of Contents

  • 1.0 Basic Information
    • [1.1] Types of Units
    • [1.2] Counters
    • [1.3] Definitions
    • [1.4] Combat Ratio
    • [1.5] Combat Modifier
    • [1.6] Rounding
    • [1.7] Group Factor Calculations
  • 2.0 Phases and Turns
    • [2.1] Phases
  • 3.0 Zone of Control
    • [3.1] Units Direction
    • [3.2] General Rules
    • [3.3] Detailed Rules
  • 4.0 Movement
    • [4.1] General Rules
    • [4.2] Detailed Rules
    • [4.3] Maneuvers (turns)
    • [4.4] Leaving and Returning to Map
    • [4.5] Stacking
  • 5.0 Combat
    • [5.1] Combat Procedure
    • [5.2] General Rules
    • [5.3] Terrain Effect
    • [5.4] Retreat
    • [5.5] Pursuit
    • [5.6] Charge
    • [5.7] Countercharge
    • [5.8] Ride Down
  • 6.0 Morale
    • [6.1] General Rules
    • [6.2] Morale Test
  • 7.0 Banners
    • [7.1] General Rules
  • 8.0 Leaders
    • [8.1] General Rules
    • [8.2] Leader in Combat
  • 9.0 Disorganization
    • [9.1] General Rules
    • [9.2] Effect on Units
    • [9.3] Organization
  • 10.0 Panic
    • [10.1] General Rules
    • [10.2] Effect on Units
    • [10.3] Removing Panic
  • 11.0 Ranged Units
    • [11.1] General Rules
    • [11.2] Ranged Fire
    • [11.3] Direct Combat
    • [11.4] Archers
    • [11.5] Horse (Camel) Archers
    • [11.6] Crossbowmen
    • [11.7] Bombards
  • 12.0 Objects
    • [12.1] Fortifications
  • COMPLEMENTARY RULES
    • 13.0 Units Organization
    • [13.1] General Rules
    • 14.0 Fatigue
    • [14.2] General Rules
    • [14.3] Fatigue Effect
  • 15.0 Janissaries
    • [15.1] General Rules
    • [15.2] Palisade
  • Errata
  • Game Tables
    • Combat Table
    • Combat Disorganization
    • Terrain Influence
    • Archer Fire
    • Crossbow Fire
    • Horse Archer Fire
    • Bombard Fire
    • Morale Test and Pursuit
  • Scenarios
    • Kosovo Field – Historical Scenario
      • Initial Setup
      • Victory Conditions
      • Scenario Notes
    • Miloš Obilić – Semi-Fictional Scenario
      • Initial Setup
      • Victory Conditions
      • Scenario Notes

1.0 Basic Information

[1.1] Types of Units

Types of field units:

  • Cavalry
  • Infantry
  • Archers
  • Crossbowmen
  • Camel archers

Types of cavalry:

  • Light cavalry (armor level 0)
  • Cavalry (regular) (armor level 1)
  • Heavy cavalry (armor level 2)

Types of infantry:

  • Retainers (armor level 0)
  • Light infantry (armor level 1)
  • Heavy infantry (armor level 2)

Battle sides: Serbs, Croats, Ottomans.

[1.2] Counters

The game provides three types of counters:

  • leaders and banners
  • field units
  • auxiliary counters

Counter types include leaders, banners, Disorganization markers, Panic markers and Charge Factor markers.

Some scenarios may contain different types of counters which are described by the scenario's notes.

Each cavalry counter represents a conglomerate of "lances", with about 150 horsemen/knights. Each infantry counter represents around 300 – 350 men. These values may differ depending on battle scale. See 13.0 for more information on units' organization in the game.

The counter shows all unit's characteristics relevant for the gameplay. At the top, on the colored rectangle marking the unit's front, there are the unit number, the leading commander's initials (usually the first letter of his name) and its banner. On the left side of the unit picture there are shields showing the armor of the unit. At the bottom there are the strength (in the square on the left) and movement (in the circle on the right) point values.

Every unit has its strength defined by Strength Points (SPs). The number of SPs can decrease as a result of combat losses or other events. Loss of SP is marked by turning the unit's counter on its reverse side (if the unit's counter has a reverse). A unit losing all its SPs is eliminated.

Counter front and counter back (reverse) are shown in the rulebook.

[1.3] Definitions

  • Strength Point (SP) – reflects the unit's strength/morale/training/experience and other factors influencing the unit's combat power.
  • Movement Point (MP) – reflects the unit's maneuverability. It limits the number of fields and/or maneuvers the unit can make during a turn.
  • Zone of Control (ZOC) – marks the unit's ability to influence its front area.
  • Charge Factor (CF) – reflects the speed of cavalry units, influencing their combat and their ability to make a turn during movement (see [5.6]).
  • Regular unit – is: cavalry (but not leaders) or infantry (but not ranged units).

[1.4] Combat Ratio

Combat Ratio (CR) is the column in the COMBAT table where the combat result is to be looked up after a 2 dice (2K6) roll.

CR is calculated as follows:

  1. Attacking Player's units' SPs are divided by defending Player's units' SPs which, after rounding (see [1.6]), yields the initial combat ratio.
  2. The initial combat ratio is modified by both Players' combat modifiers (see [1.5]) in order to calculate the final combat ratio.

Example: Two cavalry units, each having 2 SPs, attack an infantry unit with 1 SP. Total attacker's strength is 5. Total defender's strength is 1. Combat ratio is 5:1.

[1.5] Combat Modifier

Combat Modifier (CM) is a column shift applied to the initial CR in order to obtain its final value. Both attacking and defending units can gain CMs through various factors like unit armor, charge factor, leaders etc.

Defender's CMs lower the initial combat ratio (shift the initial combat ratio column in the COMBAT table to the left) while attacker's CMs increase the initial combat ratio (shift the initial combat ratio column in the COMBAT table to the right).

Maximum and minimum combat ratio from the COMBAT table cannot be exceeded for the final combat ratio.

Example:

a) Attacker units' total strength is 8 and they have 3 combat modifiers. Defending units' total strength is 3 and they have 1 combat modifier.

  • Initial combat ratio is 8:3 => 2.67:1 => 3:1.
  • After attacker's CMs are applied, the combat ratio increases to 6:1.
  • After defender's CMs are applied, the final combat ratio is set to 5:1.

b) Attacker units' total strength is 6 and they have 7 combat modifiers. Defending unit strength is 1 and it has 2 combat modifiers.

  • Initial combat ratio is 6:1.
  • After attacker CMs are applied the combat ratio is 13:1.
  • After defender's CMs are applied, the combat ratio is set to 11:1.
  • The final combat ratio cannot exceed the maximum ratio from the COMBAT table, therefore its final value is lowered to 9:1.

Players must use all combat modifiers gained by armor, charge factor, leaders and other factors.

[1.6] Rounding

Any integer number division is rounded up.

Example:

a) If a unit with a strength of 1 SP should have it halved, its strength is still counted as 1. b) 5 divided by 2 is 2.5. After rounding it is 3.

For combat ratio calculations any initial CR below .5 is to be rounded down and any result above or equal to .5 is to be rounded up.

Example:

a) Attacker has 3 SPs while defender has 2 SPs. Combat Ratio is 3:2 => 1.5:1 => 2:1. b) Combat Ratio 6.49:1 is to be rounded to 6:1.

[1.7] Group Factor Calculations

For combat and other purposes there may be a need to obtain the charge factor and/or armor value for a group of units. This is done by calculating the mean of the individual units' values. A lack of factor for a given unit is included in the mean and counted as 0.

Example: Four cavalry units attack a single enemy unit. Charge factors are as follows: 3, 3, 2, 1 and armor factors are as follows: 1, 1, none, none. This group charge factor after rounding is 2 (9 ÷ 4 = 2.25) and the armor value after rounding is 1 (2 ÷ 4 = 0.5).

Note that because the group armor value is equal to 1, this group's combat factor, gained from charge factor, couldn't be greater than 2 (see 5.6.5).

2.0 Phases and Turns

Games in the medieval system are divided into turns. Every turn allows or obliges players to perform certain actions (movement, attack, defense etc.).

All actions in a turn are grouped into phases. Every phase allows for a given set of actions only. Performing an action outside the correct phase is prohibited. Each turn is finished after all its phases have been completed.

Players cannot change the order of phases. A phase can be omitted if there are no mandatory actions and both players choose not to perform voluntary ones.

After a turn has been completed, players move the TURNS (ETAPY) counter by one position and start over with a new turn.

One turn represents around 30 minutes of real time.

[2.1] Phases

Player with initiative (moves first) – player A. Player without initiative (moves second) – player B.

Phase 1 – cavalry movement of player A a) Player A can move any number of his cavalry units. All unit's movements and maneuvers are limited by the unit's MPs (see 4.0). b) Player A can shoot at enemy units if his ranged units (e.g. horse archers) have such ability. c) Player B can shoot at Player A's cavalry units. d) Player B may perform a countercharge on Player A's cavalry units.

Phase 2 – cavalry attack of player A All cavalry units of player A having enemy units in their ZoCs must attack.

Phase 3 – infantry movement of player A a) Player A can move his non-cavalry (infantry) units. All units' movements are limited by their MPs (see 4.0). b) Player B can shoot at Player A's non-cavalry units.

Phase 4 – infantry attack of player A All non-cavalry units having enemy units in their ZoC must attack.

Phase 5 – cavalry movement of player B Analogous to phase 1.

Phase 6 – cavalry attack of player B Analogous to phase 2.

Phase 7 – infantry movement of player B Analogous to phase 3.

Phase 8 – infantry attack of player B Analogous to phase 4.

Phase 9 – MORALE modifications (see 8.0). The MORALE counter should be moved by the number of fields resulting from events during the turn. The new MORALE value is valid starting from phase 1 of the next turn.

For convenience (if many events affect morale) the MORALE counter can be moved just after each event. All effects it causes are still valid starting from the next turn only.

Note: The term "turn" is used in two meanings in the rules. The first meaning (described in this chapter) describes the division of play, while the other meaning refers to the rotation of a unit. The context always indicates whether "game/play turn" or "unit turn" is described.

3.0 Zone of Control

[3.1] Units Direction

In the medieval system the direction (front, rear) of units is very important. Changing movement direction was difficult for cavalry units, especially heavy ones. Therefore in the game the position of the counter on a map is relevant.

3.1.1 Three hexes at the front of a unit (counter) are its "front area" while 3 hexes at the back of the unit (counter) are its "rear area". The front of a unit is marked by a colored rectangle on the counter.

3.1.2 Attacker gains 2 CMs for each rear area hex with attacking units.

Example: A cavalry unit is attacked by 4 enemy infantry units. Two hexes of the cavalry's rear area are occupied by attacking units. Attacker gains 4 CM in this combat.

[3.2] General Rules

3.2.1 Zone of Control (ZoC) extends onto the unit's frontal area only. 3.2.2 Archers, crossbowmen and artillery (bombards) do not have ZoC. 3.2.3 ZoC does not extend through rivers. 3.2.4 Existence of ZoC does not negate existence of enemy ZoC on the same hex.

[3.3] Detailed Rules

3.3.1 Entering enemy ZoC does not cost additional MPs. 3.3.2 A unit entering enemy ZoC must stop. Exception to that rule is 3.3.3. 3.3.3 A unit does not need to stop in an enemy unit's ZoC if its CF is greater than the enemy's by more than 1. In this case +1 MP must be spent for movement to the next hex.

Example: Unit A with a charge factor equal to 2 enters the ZoC of a unit with a CF equal to 0. Unit A does not need to stop but in order to move to the next hex it must spend an additional MP.

4.0 Movement

[4.1] General Rules

4.1.1 Players can move their units during movement phases, countercharge, retreat and pursuit. 4.1.2 Order of units to be moved during a movement phase is the Player's choice. 4.1.3 Players' units' movement and/or maneuvers during movement phases are limited by each unit's MPs. 4.1.4 A unit does not need to use all its MPs, but any "saved" MPs do not carry over to the next turn. 4.1.5 A unit cannot pass its MPs to other units. 4.1.6 Any number of units can move through a hex (see [4.5]). 4.1.7 Cost of movement for a unit of a given type is listed in the TERRAIN INFLUENCE table.

[4.2] Detailed Rules

4.2.1 A unit can enter only its frontal hex (middle hex of its front area). 4.2.2 A unit cannot enter a hex occupied by enemy units. Exception to that rule is ride down (see [5.8]). 4.2.3 Unit A can enter a hex occupied by other friendly unit B only in 2 cases: a) unit A and unit B total strength does not exceed the hex stacking limit (see [4.5]); b) unit A rides down unit B (see [5.8]). 4.2.4 Entering a hex occupied by a friendly unit costs an additional 1 MP (case a). 4.2.5 A cavalry unit entering a forest, village or swamp disorganizes automatically if the movement is not on a road. 4.2.6 An infantry unit entering a swamp disorganizes automatically if the movement is not on a road. 4.2.7 Rivers can be crossed only through bridges or fords (they are marked on the map). 4.2.8 Movement on a road reduces the cost of refraining from CF increase to 0.5 MP (see 5.6.12). 4.2.9 A unit can always move by 1 hex and make any turn, or make any turn without moving. This costs all MPs the unit had at the beginning of the movement phase. After such a move the unit's CF is reduced to 0.

This rule allows units to move onto an adjacent hex or turn into any direction even if it does not have a sufficient number of MPs at the beginning of the movement phase.

[4.3] Maneuvers (turns)

Turning allows units to change direction of movement. The ability to do this quickly and in tight formation was one of the most valuable skills of a cavalry unit during a medieval battle.

4.3.1 Base cost of each 60° turn is 1 MP. Example: Base cost of a 180° turn is 3 MPs.

4.3.2 Total cost of a cavalry unit's turn equals the base turn cost multiplied by the unit's charge factor increased by 1, with the armor level added. Example: A unit of heavy cavalry (armor level equal to 2) with a charge factor equal to 3 (at full charge) wants to turn by 60°. Cost of such a maneuver will be: 1 MP x (3 + 1) + 2 = 6 MPs.

4.3.3 Infantry always pay 1 MP for any turn (4.3.2 is ignored). 4.3.4 A cavalry unit with a charge factor greater than 1 can turn by 60° only. To turn by more than 60°, a charging cavalry unit must "break": make the allowed 60° turn, move 1 hex, and then it can make any turn. Example: A light cavalry unit (armor level 0) has moved 3 hexes in a straight line, gaining a charge factor equal to 3. In order to move back, a unit must turn by 60°, then move 1 hex, and then turn by e.g. 120°. The unit spends 3 MPs on the move by three hexes, then turns by 60° at a cost of 4 MPs, then moves by one hex for 1 MP, then turns by 120° for 4 MPs and then moves by one hex at a cost of 1 MP. Cost of the first turn is 4 MPs (1 MP x (3 + 1) + 0 = 4) and cost of the second turn is 4 MPs (2 MP x (1 + 1) + 0 = 4).

Note that such a maneuver will take more than one turn for a regular cavalry unit.

4.3.5 Presence of ZoC increases the final cost of a turn by +1 MP. 4.3.6 Terrain increases the final cost of a turn for a unit during movement. Terrain cost in MPs (from the TERRAIN INFLUENCE table) must be added to the cost of the turn. Example: A unit of heavy cavalry (not in charge, armor level 2) turns by 120° in a forest. Cost of such a maneuver is 4 MPs (for the turn) + 2 MPs (terrain cost) = 6 MPs. 4.3.7 A unit can turn in any direction after a pursuit or retreat. 4.3.8 A unit can make only one turn on a hex during a phase (a turn on one hex cannot be divided into smaller parts).

[4.4] Leaving and Returning to Map

4.4.1 A unit can leave the map only as a result of movement or pursuit. The map border is treated as impassable terrain for retreats. 4.4.2 Leaving a map ("crossing" the map border) costs 1 MP. 4.4.3 A unit that left the map can return after 3 full game turns (see 2.0). Example: a) A unit left the map in Turn 2 during its movement phase (phase 1). The unit can return to the map on Turn 5 during its movement phase at the earliest. b) A unit left the map in Turn 2 during pursuit (phase 2). The unit can return to the map on Turn 6 during its movement phase. 4.4.4 A unit that left the map can return no farther than 6 hexes from the departure hex for cavalry units and no farther than 4 hexes for non-cavalry units. Example: A cavalry unit that left the map from field 2300 can reenter it on fields 1700 to 2900 inclusive. 4.4.5 During the phase the unit returned to the game, the unit cannot move (the unit's counter is just placed on the return hex). 4.4.6 A unit cannot return to the map on impassable terrain. 4.4.7 A unit cannot return to the map on hexes occupied by enemy unit(s) or in enemy ZoC. 4.4.8 If a unit cannot or does not want to return to the map, then its return is delayed until this is possible and the player decides to do so. The delay does not influence any return limitations (e.g. the reentry zone from 4.4.4 remains the same). 4.4.9 Returning units must obey stacking limitations.

[4.5] Stacking

4.5.1 One hex can contain units with a maximum strength of 2 SPs. Exceptions to the rule are marked explicitly (e.g. 10.1.3 or 12.1.8). 4.5.2 At any moment of the game the stack limit cannot be exceeded. This means that, for example, a unit cannot move or retreat through a hex if such action caused the hex stacking limit to be exceeded. Cavalry units can ride down friendly infantry to be able to enter such a hex. Example: A full strength unit (with 2 SPs) cannot enter a hex occupied by an infantry unit with 1 SP.

5.0 Combat

[5.1] Combat Procedure

5.1.1 Combat procedure is as follows: a) Attacker selects attacking unit(s) and their target(s). b) Both sides' total SPs and combat modifiers are counted. c) Combat ratio is calculated (see [1.4]). d) Combat modifiers are applied (see [1.5]). e) Two dice (2K6) are rolled. f) Intersection of the final combat ratio column with the row respective to the dice roll provides the combat result. It should be applied before g) in the following order: first loss of SPs, then retreat and pursuit if any. g) Two dice (2K6) roll for disorganization is made and the result is checked in the COMBAT DISORGANIZATION table.

Example: Two cavalry units (each having 2 SPs), with charge factors 2 and 3, attack enemy cavalry (2 SPs) with charge factor 1. Attackers' amour values are 2 and 1, defender armor value is 0. Attack is being carried through a stream. For this combat the initial combat ratio is 4:2 => 2:1. Then it needs to include: Attacker combat modifiers: 2 from charge factors (for attack through stream the unit loses 1 CF – see 5.6.9) and 2 from armor (4 in total). Defender combat modifiers: 1 from charge and 1 from terrain (2 in total). Final combat ratio for this combat is 4:1. If the attacking player rolls 4 for the combat result then the defending unit must retreat by 2 hexes and the attacker loses 1 SP (his counter needs to reverse). Finally the roll for disorganization must be made. On results 2, 3 and 12 the defending unit is disorganized.

Note: Combat results are explained below the COMBAT table.

[5.2] General Rules

5.2.1 Combat between units takes place only during combat phases or as a result of countercharge during a cavalry movement phase. 5.2.2 All units having an enemy in their ZoCs must attack. 5.2.3 All enemy units in attacking units' ZoCs must be attacked. 5.2.4 A unit can attack only units in its front area. 5.2.5 A single enemy unit can be attacked by multiple friendly units. Multiple enemy units can be attacked by a single friendly unit. For a single combat either the attacker or the defender must be on one hex. 5.2.6 An attack from opposing directions provides 1 combat modifier for the attacking Player. 5.2.7 In combat both Players gain combat modifiers equal to their units' (group) armor value. 5.2.8 If a defending unit is eliminated during combat then its opponent can enter the hex released by the defender and then: a) can make any turn, b) move onto an adjacent hex and c) make any turn again. This counts as regular movement (the unit cannot move through an enemy's ZoC, loses CF if a turn is made etc.). 5.2.9 Combat order is chosen by the attacking player (in cavalry movement phases the player who makes a countercharge is the attacking player). 5.2.10 Combat must be concluded before any other combat starts. 5.2.11 Combat factor is reduced by 1 after combat. Example: A cavalry unit with CF equal to 3 attacks an enemy cavalry unit with CF equal to 2. After combat the attacking unit will have CF equal to 2 and the defending unit will have CF equal to 1. 5.2.12 The combat phase lasts till every attack is concluded.

[5.3] Terrain Effect

5.3.1 Terrain effect on combat is described in the TERRAIN EFFECT table. 5.3.2 If a defender fights on multiple hexes, the one with the most SPs is counted for any CMs gained by the defender.

[5.4] Retreat

Both attacker and defender may retreat as a result of a combat (if a D or A result is received in the COMBAT table).

5.4.1 Any retreats are mandatory. 5.4.2 Retreating units must retreat by the given number of hexes from the hex they fought in. Example: Result D2 means that the defender must finish its retreat 2 hexes from the hex where it was fighting. 5.4.3 A unit does not lose CF due to turns made during a retreat. 5.4.4 If a cavalry unit retreats on/through a hex occupied by a friendly non-cavalry unit then this unit is eliminated. Such a ride down is obligatory if this is the only way for the cavalry to make a full retreat. 5.4.5 Retreat is not possible into enemy ZoC or onto terrain inaccessible to the given unit. 5.4.6 If a Player cannot retreat by the required number of hexes it loses 1 SP for each hex the retreat was not possible (from all fighting units). Example: If the defender must retreat by 4 hexes (D4 result) but can move only 3 hexes from the hex the combat took place in, it loses 1 SP. If several units defended, it is the Player's choice which one suffers the loss. If the loss causes a unit's elimination it happens on the last hex of the retreat (the unit must retreat by the maximum number of hexes possible and then take the loss due to the partial retreat).

[5.5] Pursuit

After an opponent has withdrawn, the opposing side can (or must) make a pursuit.

5.5.1 Pursuit can be obligatory or voluntary. 5.5.2 Pursuit is obligatory if the unit is more than 5 hexes from its leader. 5.5.3 Pursuit is voluntary if the unit is within 5 hexes from its leader and passes a test on the leader's influence according to the table below.

PURSUIT

Hexes from leaderDice (1K6) rollResult
0*–PV
11, 2, 3, 4, 5PV
21, 2, 3, 4PV
31, 2, 3PV
41, 2PV
51PV

* leader on attacker's hex PV – pursuit voluntary

5.5.4 Obligatory pursuit can be made through the retreat path only. 5.5.5 Voluntary pursuit allows leaving the retreat path by 1 hex. Example: a) During obligatory pursuit unit A can only move through the path set by the retreating unit. b) During voluntary pursuit unit A can leave the retreat path and move to an adjacent hex.

5.5.6 The first hex of any pursuit must be the hex emptied by the retreating unit(s). 5.5.7 Enemy ZoCs are ignored during pursuit. 5.5.8 A unit does not increase CF during a pursuit. 5.5.9 A unit does not lose CF for turns less than 1200° made during a pursuit. 5.5.10 Pursuit allows cavalry to ride down non-cavalry enemy units (if the cavalry unit can enter the hex during pursuit).

[5.6] Charge

5.6.1 Charge Factor (CF) is attributed only to cavalry units. An infantry unit has an implicit CF equal to 0. 5.6.2 Minimum value of CF is 0, maximum CF value is 3. 5.6.3 A unit gains CF for every hex moved since its last turn. If the unit turns, its CF is reduced to 0. Example: A cavalry unit moves 3 hexes, gaining CF equal to 3. Then it turns by 60° and moves 2 hexes towards enemy knights. When it reaches them its CF is equal to 2.

5.6.4 A cavalry unit gains a combat modifier equal to its current CF. 5.6.5 The combat modifier gained due to CF cannot be greater than the unit's armor level increased by 1. Example: During combat, a unit with armor level 1 and CF equal to 3 gains a maximum combat modifier equal to 2. Its CF still counts as 3 for e.g. the cost of turning. The unit still receives 1 combat modifier from its armor value (according to 5.2.7). 5.6.6 CF is reduced to 0 and not counted for in an attack on units in fortifications, forest or swamps. 5.6.7 CF is reduced to 0 if a cavalry unit moves through a village, forest, swamp, ford or fortifications. Movement on a road does not save it from CF loss. 5.6.8 CF is reduced by 1 if a cavalry unit moves through a bridge. 5.6.9 CF is reduced by 1 for moving through a stream. 5.6.10 CF is reduced by 1 for each hex moved uphill. Example: A unit moves uphill by 2 hexes so its CF is reduced by 2. 5.6.11 If an attacking unit must retreat (any of its A results) then its CF is reduced to 0. 5.6.12 A unit that does not want to increase its CF after entering a hex must spend an additional 1 MP.

[5.7] Countercharge

Allows the inactive player to react to enemy moves – attack on a charging enemy cavalry unit instead of passively waiting for the attack.

5.7.1 Countercharge is made by a friendly cavalry unit on a currently moving enemy unit adjacent to its front area. 5.7.2 Countercharging units: a) can (but do not have to) make a 60° turn, and then b) must move onto a hex adjacent to the currently moving enemy unit and c) fight in a countercharge combat. 5.7.3 A countercharge combat must be resolved before the movement of the next enemy unit. 5.7.4 A countercharge combat does not prevent units from fighting in the subsequent cavalry combat phase. Example: Unit K1 moves to attack unit P1. Unit P2 countercharges in order to prevent the attack. The countercharge combat is resolved just after unit P2 moves.

If Player K started to move unit K2, countercharge on K1 is not allowed. If Player P decided to countercharge on K1, Player K can use unit K2 to attack countercharging unit P2 in the cavalry combat phase.

5.7.5 If an enemy unit is adjacent to the front areas of more than one friendly unit, all of them can countercharge. Example: An enemy unit enters a field that is adjacent to the front areas of 4 friendly cavalry units. Any (none or all) of these units can countercharge. One combat will be fought with the enemy as a result of such countercharge. 5.7.6 During countercharge all movement rules apply. Namely, a unit's CF is reduced to 0 if the unit makes a turn, and a unit's CF is increased by 1 for each hex it moves towards the enemy unit. Example: A countercharging unit with CF 1 (armor value 2), that does not turn, increases it by 1 (so it will gain CM equal to 2). If the unit turns and then moves, its CF will be 1 and the unit will gain 1 CM in the combat. The same unit countercharging through a ford will have its CF reduced to 0 and does not gain any CM in the combat. 5.7.7 A unit can countercharge only once during an enemy movement phase. 5.7.8 A unit cannot countercharge if it is in the ZoC of enemy cavalry unit(s). 5.7.9 A unit without armor (armor value equal to 0) doesn't gain CM from its CF during a countercharge fight. 5.7.10 An enemy unit cannot be countercharged if it is adjacent to another friendly unit. Example: Unit P2 cannot countercharge on K1 as it is adjacent to P1.

5.7.11 An enemy unit that was countercharged stops its movement regardless of the countercharge combat result (it can pursue if the countercharging unit(s) retreat or are eliminated due to the combat result). Example: If unit K1 wants to start movement, unit P2 can countercharge to stop unit K1.

[5.8] Ride Down

5.8.1 A cavalry unit with a charge factor more than 1, moving through a non-cavalry unit (also a friendly one), rides it down. The unit ridden down is eliminated. 5.8.2 Riding a unit down does not cause a MORALE factor change. 5.8.3 Cavalry must enter the hex occupied by a unit to ride it down. 5.8.4 In the movement phase the cost of riding down (in MPs) is equal to the SPs of the units being ridden down on a hex. Example: A cavalry unit wants to ride down two infantry units, each one having 1 SP, standing on one hex. Cost of riding down this hex is 2 MPs. 5.8.5 During a pursuit or retreat (see 5.4.4) it is enough to enter a hex occupied by an infantry unit to ride it down – the unit does not (and could not) spend MPs and its CF is not relevant. 5.8.6 Infantry in fortifications, buildings or in any kind of special formation (e.g. Scottish shiltron) cannot be ridden down.

6.0 Morale

During medieval battles the morale of fighting armies and their units was crucial to the final outcome of the battle. This is reflected in the rules by the MORALE value. For each game, the map has a special MORALE track with a counter to indicate the influence of the overall battle course on currently fighting units.

MORALE track example.

[6.1] General Rules

6.1.1 The MORALE track shows morale during a given moment of the battle. The current MORALE value influences units' behavior on the map. 6.1.2 The MORALE value provides an additional combat modifier for the Players' units in every combat. Example: If the MORALE value is "+1" for Ottomans it means that all Turkish units gain +1 combat modifier in their combats. 6.1.3 The MORALE counter start position is marked on the MORALE track. It is usually "0" at the beginning of the battle. Some scenarios may have different starting MORALE values. 6.1.4 Enemy unit elimination moves the MORALE counter by 1 field in benefit of the eliminating player. 6.1.5 Fall of a banner (even if not captured by the enemy) moves the MORALE counter by 3 fields in benefit of the opposing Player. Recapture of a banner reverses the effect – the counter is moved 3 fields in benefit of the recapturing Player. 6.1.6 Leader death moves the MORALE counter by 8 fields in benefit of the killing player. 6.1.7 Grand leader death moves the MORALE counter by 12 fields in benefit of the killing player. 6.1.8 Units with a "+2" MORALE factor must pursue (obligatory pursuit – see 5.5.4) unless on a hex with a leader. 6.1.9 The MORALE counter can be moved after every kill but its influence is set just once – at the end of the turn in phase 9.

[6.2] Morale Test

Morale test allows checking if a unit can successfully overcome difficulties during the battle.

6.2.1 In order to pass a morale test a unit must roll one die (1K6) and check the result in the table below:

MORALE TEST

MORALEDice (1K6) rollEffect
+21-5P
+11-4P
01-3P
-11-2P
-21P

P – morale test successful

6.2.2 Units within leader range add 1 to the dice roll result. 6.2.3 Units on a hex with a leader add 2 to the dice roll result. 6.2.4 A morale test is made in the movement phase. 6.2.5 If not specified otherwise, a morale test costs all MPs the unit has at the beginning of the movement phase. 6.2.6 If not specified otherwise, a morale test causes the unit to lose its CF (it is reduced to 0).

7.0 Banners

During medieval battles banners with the knights' alignment had a tremendous morale influence on the battlefield. In many cases a lost banner could harness combat morale to the point of morale break and units retreating from the battlefield.

Ottoman banner and Serbian banner are shown in the rulebook.

[7.1] General Rules

7.1.1 Every side has a number of banners (described in the scenario setup) that the player places on hexes with leader units (one banner with a leader of choice) at the beginning of the battle. Note: Banners are independent and do not need to move with the leader. A banner just always needs to be held by a regular unit.

7.1.2 A banner is not a regular unit. It does not have MPs, SPs or ZoC, it does not add to the stacking limit and it can be moved only by a regular unit. 7.1.3 A banner can be moved with only one unit during a turn. Example: Unit A holding a banner can pass it to another unit B before it makes any movement. Then the banner can be moved with unit B. If unit A moves, it can also pass the banner to another friendly unit, but this unit cannot be moved even if it wasn't activated yet. 7.1.4 A banner must always be held by a unit. It cannot be abandoned. To change holder, the banner must be passed to another friendly unit (on the same or adjacent hex). Passing a banner costs 1 MP for the banner holder. 7.1.5 A banner falls when the unit holding it is eliminated and no other friendly units to keep it are on the hex. It has to be left on the hex where the unit holding it was eliminated. 7.1.6 A banner is captured by the enemy when any hostile regular unit enters a hex with a fallen banner (during pursuit, movement or any other displacement). 7.1.7 Any friendly units on a hex with a banner and any units adjacent to it gain 1 CM. Being in range of multiple banners does not provide additional CMs (a unit can gain only 1). 7.1.8 See 6.1.5.

8.0 Leaders

Grand Leader (range 3) and Leader (range 2) counters are shown in the rulebook.

[8.1] General Rules

8.1.1 A leader is not a regular unit. It does not have SPs or ZoC. It can be stacked with other friendly units without adding to the stack limit. It can also move alone without another friendly unit. 8.1.2 A leader has 10 MPs and moves like a cavalry unit (e.g. regarding the influence of terrain on movement). 8.1.3 A leader ignores enemy ZoCs. 8.1.4 Leader death means that all units under his command lose 1 SP (see 13.0). 8.1.5 Death of a Grand Leader (all leaders with range 3) means that all of the Player's units lose 1 SP. 8.1.6 Any unit loss caused by leader death is not reflected on the MORALE track. 8.1.7 Leaders pursue and withdraw as regular units. If a leader cannot withdraw it stays on the last hex of its possible withdrawal path. Example: A leader and accompanying units must withdraw 2 hexes according to combat results but only 1 hex of withdrawal is possible. While accompanying regular units obey regular withdrawal rules, the leader withdraws by 1 hex and stops (he can be killed by enemy pursuit if the accompanying regular units are killed). If the stack could not withdraw at all, the leader stays on the hex (and can be killed by enemy pursuit if all accompanying regular units are killed). 8.1.8 Leaders do not get disorganized or panicked.

[8.2] Leader in Combat

8.2.1 Any unit stacked on a hex together with a leader gains 2 CMs. 8.2.2 Any unit within a leader's command range gains 1 CM. 8.2.3 A unit can gain CMs from just one leader. 8.2.4 If a leader is stacked with units engaged in combat and those units are forced to retreat (Dx or Ax result), a 2 dice (2K6) roll must be made for leader death. If the roll is less than or equal to the number of fields the units with the leader have to retreat, the leader dies in the fight. 8.2.5 Any SP losses inflicted by the enemy to retreating units should be subtracted from the dice roll result in 8.2.4. This also includes additional losses, e.g. in situations when units cannot retreat by the required number of hexes (see 5.4.6). Example: a) Units attacking with a leader received combat result A2 -1. A roll for leader death must be made. If the 2 dice roll is 2 or 3 the leader dies. b) Units defending with a leader on the same hex received combat result A3 -1 and can retreat by 2 hexes only (taking an additional 1 SP loss as a result). A roll for leader death must be made. If the 2 dice roll is 2, 3, 4 or 5 the leader dies. 8.2.6 A leader alone on a hex is killed when an enemy unit enters such a field during movement or pursuit. 8.2.7 A leader alone on a hex is killed if attacked during a combat phase or countercharge. Such combat is fought (which may mean losses for the attacker) using the maximum COMBAT table combat ratio, but regardless of the result, the leader is killed. 8.2.8 See 6.1.6 and 6.1.7.

9.0 Disorganization

Disorganization was often the most important reason for a unit's failure in medieval battles. It happened that the number of kills was minimal and the whole unit just scattered and abandoned the battlefield.

[9.1] General Rules

9.1.1 A unit is disorganized:

  • in combat (see [5.1]);
  • when at any moment of the game it is stacked on one hex with another friendly disorganized unit and fails a morale test;
  • as a result of enemy actions (e.g. ranged fire). 9.1.2 Each (not panicked and not disorganized) unit that, at any moment of the battle, is stacked with disorganized unit(s) must undergo a morale test (see [6.2]). Failure of the test causes disorganization of the unit. Note: Two disorganized units do not undergo a morale test when stacked on the same hex. They are already disorganized. 9.1.3 Units on a hex with a commander do not disorganize. 9.1.4 A disorganized unit is covered with a "Disorganization" marker.

[9.2] Effect on Units

9.2.1 Disorganized units have their MPs reduced by:

  • 2 MPs for cavalry;
  • 1 MP for infantry. 9.2.2 Disorganized units have their SPs, counted for the combat ratio, halved. 9.2.3 If most friendly units in a combat are disorganized, the enemy gains 1 combat modifier. 9.2.4 Disorganized units can get a maximum of 1 combat modifier from their CF.

[9.3] Organization

9.3.1 In order to organize (remove disorganization) a unit must make a morale test. If the test is successful the unit is organized.

10.0 Panic

[10.1] General Rules

10.1.1 A unit panics when:

  • it is disorganized and becomes disorganized again as a result of combat;
  • at any moment of the game it is stacked on one hex with another friendly panicked unit and fails a morale test. 10.1.2 Each unit that, at any moment of the battle, is stacked with panicked unit(s) must undergo a morale test (see [6.2]). Failure of the test causes panic of the unit. 10.1.3 Panicked units do not count for the hex stacking limit – they can enter any accessible hex even if stacking would not allow that in normal circumstances. Example: There is a 2 SPs cavalry unit on a hex. Another panicked cavalry unit can (in most cases must) enter that hex (and may cause panic in the unit). 10.1.4 A panicked unit is covered with a "Panic" marker.

[10.2] Effect on Units

10.2.1 Panicked units do not fight, do not have SPs and ZoC. 10.2.2 Panicked units, during a friendly movement phase, must move the shortest possible (and accessible) way towards the "friendly" edge of the map. Setting this route is not influenced by the presence of friendly and enemy units. Example: Movement towards the "friendly" edge of the map through the shortest possible way must be made even if such a path requires the unit to move through an enemy unit (which causes the panicked unit's elimination). 10.2.3 Panicked units are eliminated the moment they enter a hex with an enemy unit or a hex in enemy ZoC. 10.2.4 Panicked units are eliminated when they leave the map through the "friendly" edge. 10.2.5 Panicked units are covered with a panic marker.

[10.3] Removing Panic

10.3.1 In order to remove panic a unit must make a morale test. If the test is successful the unit becomes disorganized.

11.0 Ranged Units

[11.1] General Rules

11.1.1 A ranged unit's counter has a movement formation side (SP equal to 0) and a combat formation side (MPs equal to 0). [sic: as printed in the source; the parenthetical values are transcribed as they appear.] Movement formation and combat formation are shown in the rulebook.

11.1.2 A ranged unit can shoot at enemy units only when in combat formation. 11.1.3 A change of formation (turning the counter) costs 1 MP. 11.1.4 A ranged unit can be moved to an adjacent accessible hex without a formation change. 11.1.5 A ranged unit can shoot at any time during an enemy movement phase. Example: "At any time" means that e.g.: a) A ranged unit can shoot at any unit (in range) before any movement of enemy units (just after the enemy movement phase started). b) A ranged unit can shoot as soon as the unit enters its fire range (see 11.2.7). c) A ranged unit can shoot after the enemy has finished all his movement (still before the end of the enemy movement phase). 11.1.6 A ranged unit can shoot only once during a turn. 11.1.7 Specific unit characteristics – different than described in the general rules (e.g. number of shots per turn, range) – are described in the unit's section rules (e.g. for Horse Archers).

[11.2] Ranged Fire

11.2.1 Ranged unit fire range is shown in the picture below. Ranged fire range picture is shown in the rulebook.

11.2.2 If a ranged unit shoots at enemy units in a friendly ZoC then a dice (1K6) roll must be made. On 1 a friendly unit adjacent to the enemy under fire (chosen by the owning Player) suffers 1 SP of losses. In this case the enemy target unit does not suffer any losses. Example: Archers shoot at an enemy cavalry unit next to a friendly infantry unit. The Player rolls for "friendly fire" and the result is 1. As a result the enemy unit does not suffer any losses (the roll for its losses is skipped) and the friendly infantry loses 1 SP. 11.2.3 Enemy armor influences ranged unit fire. The armor level is subtracted from the ranged unit fire dice roll. 11.2.4 The ranged unit fire dice roll is modified by terrain. 1 should be subtracted if shooting at units in a forest, village or within fortifications. 11.2.5 If a ranged unit shoots at a hex with a leader, a 2 dice (2K6) roll should be made. A result of 12 means leader death. The roll is made for each unit shooting at the hex. Example: This rule even means that a friendly leader can be killed by friendly fire, e.g. in the situation described in 11.2.2 (on dice (1K6) roll 1 and then 2 dice (2K6) roll 12). 11.2.6 A ranged unit must have visibility to the target. Visibility is blocked by a hex with hills, forest, village or fortifications. Visibility is not blocked by friendly units.

Polish archers cannot shoot at unit A because visibility is blocked by a village. They can shoot at unit B. (Diagram in the source; the example describes unit A and unit B.)

11.2.7 Concurrent fire from both friendly and enemy units is made with the initial units' strength. Any losses are set after both units have shot. Example: Horse Archers enter a hex adjacent to crossbowmen. In this case both units can shoot. If both Players decide to shoot then they roll for enemy losses and any damage inflicted by the enemy is counted after both shots are finished.

[11.3] Direct Combat

11.3.1 The enemy gains 3 CMs when ranged units are present in a combat. 11.3.2 A ranged unit (in any formation) fighting alone uses only 1 SP (regardless of the number of ranged units fighting).

[11.4] Archers

11.4.1 Archers shoot according to the ARCHER FIRE table:

ARCHER FIRE – 2 dice (2K6) roll

Range123456789101112
1-------1-1-1-1-1-2
2-----

[11.5] Horse (Camel) Archers

Horse Archers had speed and maneuverability. With their light bows they were great at disorganizing enemy formations at the beginning of combat.

11.5.1 Besides the ability to shoot, horse archers are considered cavalry units (e.g. [11.3] doesn't apply, they don't have combat/movement formation etc.) with the limitations described in this section. 11.5.2 Horse Archers units' base turn cost is 0.5 MP for a 60° turn. 11.5.3 Horse Archers don't get any combat modifiers from their CF. 11.5.4 Horse archers can shoot at targets on any adjacent hex. 11.5.5 Horse archers shoot according to the HORSE ARCHER FIRE table:

HORSE ARCHER FIRE – 2 dice (2K6) roll

Range123456789101112
1---------1-1-1-1

11.5.6 Horse archers can shoot twice: in addition to the enemy movement phase fire, they can shoot during a friendly movement phase. 11.5.7 Horse archers can shoot only once during a friendly movement phase. Example: A horse archer can enter an enemy ZoC and shoot at the enemy during their movement phase. 11.5.8 The cost of firing during a friendly movement phase is 1 MP. 11.5.9 A horse archer unit that has 1 SP subtracts 1 from the dice roll when shooting. 11.5.10 If horse archers inflicted losses, the unit must also make a test for disorganization according to the COMBAT DISORGANIZATION table (B1 row). 11.5.11 Horse Archers are not influenced by fatigue (see 14.0).

[11.6] Crossbowmen

A crossbow was much more powerful than a bow and could target even the best armored knights. Its power caused such fear among knights that they called it "dishonorable" weapon and were pushing strongly to ban it.

11.6.1 Crossbowmen shoot according to the CROSSBOWMAN FIRE table (printed as "CROSBOW FIRE" in the source):

CROSSBOWMAN FIRE – 2 dice (2K6) roll

Range123456789101112
1----1-1-1-1-1-1-2-2-2
2-----

11.6.2 If crossbowmen inflict losses a dice roll should be made. On 6 the enemy unit is disorganized and stopped (cannot move any more during the current movement phase).

[11.7] Bombards

Medieval bombards were the predecessors of modern artillery. But those units didn't play an important role on the battlefield yet.

11.7.1 Bombards shoot at units according to the BOMBARD FIRE (UNITS) table:

BOMBARD FIRE (UNITS) – 2 dice (2K6) roll

Range123456789101112
1-------DDDDSDS
2-----

D – disorganization S – unit stopped (cannot move any more in the phase)

11.7.2 Bombards' range is shown in the picture below. Bombard range picture is shown in the rulebook.

11.7.3 For bombards only armor level 2 influences its fire (11.2.3 is ignored). 1 is subtracted from the fire roll result for such units. 11.7.4 Bombards cannot retreat when in combat formation. 11.7.5 Bombards can shoot at objects according to the BOMBARD FIRE (OBJECTS) table:

BOMBARD FIRE (OBJECTS) – 2 dice (2K6) roll

Range123456789101112
1-------DDDDD
2-----

D – object destroyed

12.0 Objects

[12.1] Fortifications

Fortifications are any buildings built by man and having defensive ability: bailey, ramparts, palisades and any other fortified buildings. They are described in the map legend.

12.1.1 A unit attacking through fortifications has its strength halved. 12.1.2 A cavalry unit attacking through fortifications loses its CF. 12.1.3 Movement through fortifications costs additionally:

  • +1 MP – Infantry with armor level equal to 0
  • +2 MPs – Infantry with armor level equal to 1 or 2
  • +3 MPs – Cavalry with armor level equal to 0
  • +4 MPs – Cavalry with armor level equal to 1
  • +5 MPs – Cavalry with armor level equal to 2

12.1.4 Movement through gates (marked on the map) does not cost additional MPs. 12.1.5 Pursuit through fortifications is possible only on a hex occupied by the defending unit. Example: A unit defending in fortifications received combat result D2. It retreats by 2 hexes but the attacker can enter only the hex it occupied during combat. 12.1.6 Fortifications can be destroyed by a regular unit. If the unit stays on the fortified hex for 3 full turns, then on turn 4, at the beginning of the movement phase, the fortification is considered to be destroyed. 12.1.7 If a unit is attacked during destroying fortifications the procedure described in 12.1.6 needs to be restarted. Example: An infantry unit entered a fortified hex on turn 4. The Player declared fortifications destruction and left the unit on the hex till turn 8. On turn 8, movement phase, the fortifications are destroyed and the infantry unit can move. If the unit was attacked, even by unsuccessful ranged fire, the whole procedure needs to be restarted. 12.1.8 The stacking limit for a fortified hex is 10 SPs. Such a hex can fight with a maximum strength of 4 SPs though. 12.1.9 A maximum of 2 SPs of cavalry units can be stacked on a fortified hex.

COMPLEMENTARY RULES

Rules in this section can be omitted by less experienced players as they may be confusing and too complicated for first games.

13.0 Units Organization

Basic medieval cavalry organization unit was "lance" – created by a landlord and his retinue. Lances were grouped and fought within a "banner" – which marked a group of landlords from one family or area. There were also "court" banners created by the King, Prince or Kniaź.

In "Kosovo Field 1389", for game simplicity and reduction of counters number, each counter represents several lances that fought under one commander – usually a member of the ruling family (Lazar for Serbs and Murad I for Ottomans).

[13.1] General Rules

13.1.1 Each commander has a certain number of units assigned (the exception is Ewrenos, author of the battle plan for Ottomans, to whom the Ottoman Player can assign any number of Ottoman units). 13.1.2 A unit's assignment is set in each scenario – a commander's units are listed below the commander itself. 13.1.3 For easier recognition, units originally assigned to a given commander have the same background color of their front rectangle as the background color of the commander's name rectangle, as well as the first letter of the commander's name after the unit number.

Command chart ("commands: ... and more..") is shown in the rulebook.

14.0 Fatigue

Fatigue is a factor that greatly influenced medieval battles. There were combats where, after several hours of fierce fight, both sides ceased fighting and rejoined after a couple of hours of rest.

[14.2] General Rules

14.2.1 Fatigue rules apply to the leader and his units (see 13.1.5). 14.2.2 Unless scenario-specific rules set it differently, the starting fatigue for a leader is 0. 14.2.3 If a leader moves, fights or influences any fight during the turn, his fatigue increases. Example: Murad II has made his first move. His fatigue level increases from 0 to 1. If in the next turn he influences (even) 1 combat, his fatigue increases from 1 to 2. 14.2.4 If a leader does not move, fight or influence a fight, his fatigue is lowered by 1 (but cannot be lower than 0). 14.2.5 Fatigue can change by 1 level in a turn only.

[14.3] Fatigue Effect

14.3.1 Units under command of a leader with fatigue level above 12 are treated as disorganized units during a fight. Such units still must be "normally" disorganized twice to panic.

15.0 Janissaries

The Janissaries ("new soldiers") are infantry units that formed the Ottoman sultan's household troops and bodyguards. The force was created by the Sultan Murad I from Christian boys levied through the devşirme system from conquered countries in the 14th century.

[15.1] General Rules

15.1.1 Janissary units start with a "palisade" counter at the beginning of the game. 15.1.2 A Janissary unit can move with a "palisade". In such case the unit can move only to an adjacent hex. 15.1.3 Janissary units cannot move further than 10 hexes from their commander Janissar-Aga. If at any moment of the game a unit is more than 10 hexes from him then during its movement phase:

  • unit must abandon its "palisade" on the hex AND
  • unit must move the shortest route towards the commander, if enemy is encountered it must be attacked. 15.1.4 A Janissary unit, before combat, can shoot the enemy (it will be fighting with) from its bows. On result:
  • 1 – unit loses 1 SP;
  • 2–6 – no effect.

[15.2] Palisade

15.2.1 "Palisade" assembly/disassembly costs 1 MP. 15.2.2 An assembled "Palisade" provides 2 CMs for defending Janissary unit(s) when fighting with cavalry and 1 CM when defending from infantry. The number of SPs attacked (if both infantry and cavalry) decides on the CMs gained. Example: A Janissary unit is attacked by 2 SPs of infantry and 3 SPs of cavalry. The unit receives 2 CMs for this battle. Even if there were only 2 SPs of cavalry in this fight, the unit still receives 2 CMs. 15.2.3 The "Palisade" counter affects combat in 3 frontal fields only – its direction must be set at the moment of assembly. 15.2.4 If a Janissary unit escaped after the fight then the palisade it carried is destroyed. 15.2.5 Janissary units in "Palisade" cannot be ridden down.

Errata

Some Murad I's archer counters (1/M – 14/M) have 0 MP in movement formation. The correct value is 4 MPs.

Game Tables

Combat Table

COMBAT TABLE. Columns are the combat ratio (CR); rows are the 2 dice (2K6) roll. Modifications: MORALE, armor, Charge Factor, Leaders, Banners, terrain.

2 dice roll1:41:31:21:12:13:14:15:16:17:18:19:1
2--D1D2 -1D2-1 / D2-1 / D3D-1 / D4D-1 / D4D-1 / D5DD5D-1 / D5D
3-1 / -1--1 / D1D1 -1

Examples:

  • -1 / -1 => both Players lose 1 SP
  • D2 -1 => defender must retreat by 2 hexes and loses 1 SP
  • -1 / D2 -1 => attacker loses 1 SP, defender must retreat by 2 hexes and loses 1 SP
  • -1 / D4D => attacker loses 1 SP, defender must retreat by 4 hexes and disorganize
  • A1D => attacker must retreat by 1 hex and disorganize

Combat Disorganization

COMBAT DISORGANIZATION – 2 dice (2K6) roll. Unit type columns give the dice roll results that disorganize the unit.

Combat ResultHeavy Cavalry (armor 2)Cavalry (armor 1)Light Cavalry (armor 0)Heavy Infantry (armor 2)Infantry (armor 1)Other
B12222, 122, 3, 122, 3, 11, 12
B2 / A1222, 122, 3, 122, 3, 11, 122 - 4, 11, 12
B3 / A222, 122, 3, 122, 3, 11, 122 - 4, 11 - 122 - 4, 10 - 12
B4 / A32, 12

Terrain Influence

TerrainMovement: infantryMovement: cavalry (commander)Combat
clear11-
stream+1+1.5-1
road1*1/2 (1/3)-
swamps231/2A**
forest24-2
village12-1
hill+1

* If all movement is on a road, the unit can move 1 extra hex (also on road). ** Attacker strength is halved (when attacker is on swamps).

Note: the source prints decimal commas (+1,5 and +0,5); they are shown here as decimal points.

Archer Fire

ARCHER FIRE – 2 dice (2K6) roll

Range123456789101112
1-------1-1-1-1-1-2
2-----

Crossbow Fire

CROSBOW FIRE (as printed in the Game Tables; section 11.6.1 names this table CROSSBOWMAN FIRE) – 2 dice (2K6) roll

Range123456789101112
1----1-1-1-1-1-1-2-2-2
2-----

Horse Archer Fire

HORSE ARCHER FIRE – 2 dice (2K6) roll

Range123456789101112
1---------1-1-1-1

Bombard Fire

BOMBARD FIRE (UNITS) – 2 dice (2K6) roll

Range123456789101112
1-------DDDDSDS
2-----

D – disorganization S – unit stopped (cannot move any more in the phase)

BOMBARD FIRE (OBJECTS) – 2 dice (2K6) roll

Range123456789101112
1-------DDDDD
2-----

D – object destroyed

Morale Test and Pursuit

The Morale Test table is given in section 6.2 and the PURSUIT table in section 5.5. The Morale Test table's notes read: +1 for dice roll if within leader's range; +2 for dice roll if on hex with leader.

Scenarios

Kosovo Field – Historical Scenario

This scenario presents the initial setup on the battlefield. Serbs have the initiative and they charge first towards the enemy. During the first 6 turns Serbs fight on the flanks only (Vuković and Grgur on the right – Branković and Paliniża on the left). Main forces in the center for both armies can start on turn 7 and will have decisive influence on the final battle outcome.

Such a setup follows the historical course of one of the bloodiest battles of the medieval times, which decided about the fate of the Serbian nation until the XIXth century.

Initial Setup

Serbs:

  • Lazar, banner – 2910
    • 1/L–42/L (CAV): 2309(1), 2610(1), 2910(1), 3211(1), 3512(1), 3813(1), 4113(1)
    • 1/L–10/L (INF): 2905(1), 4211(1), 4511(1)
  • Vuković, banner – 4715
    • 1/V–7/V: 4715(1)
    • 8–14/V: 5015(1)
  • Paliniža – 5314
    • 1/P–7/P: 5314(2)
  • Branković, banner – 2009
    • 1/B–7/B: 2009(1)
    • 8/B–10/B: 1708(1)
  • Grgur (F-6) – 1408
    • 1/G–7/G: 1408(1)
    • 8/G–10/G: 1708(1)

Legend:

  • Murad I, banner – 2728. Murad I (a commander) and one banner are placed on hex 2728.
  • 1/S–8/S, 5/G–8/G (GA), 4–6 GC: 1215(1), 1515(1). All following units under command of Saridże: units 1/S, 2/S, 3/S, 4/S, 5/S, 6/S, 7/S, 8/S; Genoese archers 5/G, 6/G, 7/G, 8/G; Genoese crossbowmen 4, 5, 6. May be put on hexes 1215 and 1515 and on adjacent fields.

Ottomans:

  • Murad I, banner – 2728
  • Murad II – 2824
    • 1/M–10/M (CAV): 2728(2)
    • 1/M–25/M (INF): 3424(1), 3122(1), 2824(1), 2521(1), 2221(1)
    • 1/M–14/M (AR): 3424(1), 3122(1), 2521(1), 2221(1)
  • Aga – 2725
    • 1/A–16/A (janissaries): 3125(1), 2725(1), 2425(1), 2124(1), 1824(1)
  • Ewrenos – 2728
  • Bajazyd – 4522
    • 1/B–8/B, 1/G–4/G (GA), 1–3 GC: 4121(1), 4522(1), 4823(1)
    • 20/S–24/S (CAV under Bajazyd): 4424(1)
  • Sipah, banner – 3426
    • 1/S–19/S (CAV): 3426(1), 3826(2)
  • Kraljević – 4225
    • 1/Kr–4/Kr: 4225(1)
  • Dejanović – 4725
    • 1/De–4/De: 4725(1)
  • Yakup, banner – 1223
    • 1/Y–18/Y: 1523(1), 1223(1), 822(1)
  • Saridže – 1215
    • 1/S–8/S, 5/G–8/G (GA), 4–6 GC: 1215(1), 1515(1), 814(1)

Legend: CAV cavalry; INF infantry; AR archers; GA Genoese archers; GC Genoese crossbowmen; P all units in palisades.

Victory Conditions

Both Players gain automatic victory (enemy surrender) when their VPs count is 200 greater than the opponent's.

Serbs – automatic victory when Murad I, Bajazyd and Yakup are killed or escaped from the map. Death of:

  • Murad I – +100 VP
  • Yakup, Bajazyd (for each) – +70 VP
  • Aga, Sipah (for each) – +50 VP
  • Ewrenos, Murad II, Siridże (for each) – +40 VP
  • Dejanović, Kraljević (for each) – +25 VP
  • each enemy banner captured – +10 VP
  • each cavalry unit killed or escaped – +5 VP
  • each janissary unit killed or escaped – +4 VP
  • each crossbowmen unit killed or escaped – +3 VP
  • each archer unit killed or escaped – +2 VP
  • each infantry unit killed or escaped – +1 VP

Ottomans – automatic victory when Lazar, Vuković and Branković are killed or escaped from the map. Death of:

  • Lazar – +100 VP
  • Vuković, Branković (for each) – +70 VP
  • Grgur, Paliniża – +40 VP
  • each enemy banner captured – +10 VP
  • each cavalry unit killed or escaped – +5 VP
  • each infantry unit killed or escaped – +1 VP

Scenario Notes

  • In the historical scenario the Serb army moves first.
  • In the historical scenario Serb commanders and their units can move:
    • Branković and Grgur from 1st turn;
    • Vuković and Paliniža from 3rd turn;
    • Lazar from 7th turn.
  • In the historical scenario Ottoman commanders and their units can move:
    • Saridže and Yakup from 2nd turn;
    • Bajazyd, Ewrenos (if he has any units under his command) from 4th turn;
    • Dejanović, Kraljević from 5th turn;
    • all other Ottoman army from 8th turn.
  • If a unit under a commander that cannot move is attacked, then all units under this commander can freely move and fight starting their next turn.
  • The game finishes the moment when one player gains automatic victory (either by killing enemy commanders or by enemy surrender).

Miloš Obilić – Semi-Fictional Scenario

Milos Obilić has become a hero for all who soon will be fighting the Ottoman conquest of the Balkans. He is claimed to have killed the Ottoman Grand Commander Sultan Murad I during the battle. In this scenario Players face the situation that emerged after the destruction of Ottoman infantry and archers on both Ottoman flanks and the killing of Sultan Murad I. Additionally it is assumed that the Serbian army is aware of the deed.

In this moment his son Murad II becomes the Grand Commander. Saridża and his units are no longer in the battle and Bajazyd has retreated to the main forces with only one unit left. Ewrenos does not have his own units – the Ottoman Player may assign any units under his command.

Battle has been fought for 6 turns already and the Serbs' army fighting on both flanks begins to feel the fatigue. This may be the decisive factor for the battle's final outcome. The Ottoman Player shouldn't be too relaxed however – Lazar's reserve is still deadly dangerous.

Initial Setup

Serbs:

  • Lazar, banner – 2808
    • 1/L–42/L (CAV): 2309(1), 2610(1), 2910(1), 3211(1), 3512(1), 3813(1), 4113(1)
    • 1/L–5/L (INF): 1909(1)
    • 6/L–10/L (INF): 5116(1)
  • Vuković (F-4), banner – 4622
    • 1/V–14/V (-7 SPs): 4622(1), 4121(1)
  • Paliniža (F-4) – 5314
    • 1/P–7/P (-3 SPs): 4824(1)
  • Branković (F-6), banner – 1617
    • 1/B–10/B (-3 SPs): 1617(1), 1316(1)
  • Grgur (F-6) – 916
    • 1/G–10/G (-3 SPs): 916(1), 1316(1)

Legend:

  • Vuković (F-4), banner – 4622. Vuković (a commander) and one banner are placed on hex 4622; this commander and all his units have fatigue equal to 4.
  • 1/S–8/S, 5/G–8/G (GA), 4–6 GC: 1215(1), 1515(1). All following units under command of Saridże: units 1/S, 2/S, 3/S, 4/S, 5/S, 6/S, 7/S, 8/S; Genoese archers 5/G, 6/G, 7/G, 8/G; Genoese crossbowmen 4, 5, 6. May be put on hexes 1215 and 1515 and on adjacent fields.

Ottomans:

  • Murad II, banner – 2728
    • 1/M–3/M (CAV): 2728(1)
    • 4/M–10/M (CAV): 3129(1)
    • 1/M–3/M (INF): 2728(1)
    • 1/M–3/M (AR): 2326(1)
  • Aga
    • 1/A–16/A (janissaries) (P): 2119, 2219, 2319, 2420, 2519, 2620, 2720, 2820, 2820, 2920, 3021, 3120, 3221, 3321, 3422, 3522, 3623
    • 4/M–24/M (INF), 1/M–13/M (AR): 2221(1), 2521(1), 2822(1), 3122(1), 3424(1)
  • Ewrenos (F-1) – 2728
  • Bajazyd (F-6), 5/B – 4627
  • Sipah (F-2), banner – 4126
    • 1/S–20/S (CAV): 4126(1), 4429(2), 3929(1), 2726(1)
  • Kraljević (F-1) – 5228
    • 1/Kr–4/Kr: 5228(1)
  • Dejanović (F-1) – 4928
    • 1/De–4/De: 4928(1)
  • Yakup, banner – 1223
    • 1/Y–18/Y: 1523(1), 1223(1), 822(1)

Legend: CAV cavalry; INF infantry; AR archers; GA Genoese archers; GC Genoese crossbowmen; P all units in palisades.

Victory Conditions

Both Players gain automatic victory (enemy surrender) when their VPs count is 200 greater than the opponent's.

Serbs – automatic victory when Murad II, Bajazyd and Yakup are killed or escaped from the map. Death of:

  • Yakup, Murad II, Bajazyd (for each) – +70 VP
  • Aga, Sipah (for each) – +50 VP
  • Ewrenos – +40 VP
  • Dejanović, Kraljević (for each) – +25 VP
  • each enemy banner captured – +10 VP
  • each cavalry unit killed or escaped – +5 VP
  • each janissary unit killed or escaped – +4 VP
  • each crossbowmen unit killed or escaped – +3 VP
  • each archer unit killed or escaped – +2 VP
  • each infantry unit killed or escaped – +1 VP

Ottomans – automatic victory when Lazar, Vuković and Branković are killed or escaped from the map. Death of:

  • Lazar – +100 VP
  • Vuković, Branković (for each) – +70 VP
  • Grgur, Paliniża – +40 VP
  • each enemy banner captured – +10 VP
  • each cavalry unit killed or escaped – +5 VP
  • each infantry unit killed or escaped – +1 VP

Scenario Notes

  • The Ottoman Player moves first.
  • The game starts from the 7th turn and lasts until an automatic victory occurs or one of the Players surrenders.
  • The MORALE counter should be at the first field of the "+2" section for Serbs.
  • In every Serbian cavalry movement phase (starting from the 7th turn), if the MORALE counter is "+2" for Serbs, one dice (1K6) roll should be made. On a result of 6, Dejanović and Kraljević with their units join the Serbian army.
-
-
-1
-1
-1
-1
-2
-1
-1
-1
-1
-1
-2
-2
-
-
-
D
D
D
DS
3---------DDD
-
-
-
D
D
D
D
3---------DDD
D2 -1
D2 -1
D3
-1 / D3
-1 / D4
-1 / D5
-1 / D5
-1 / D5 -1
4-1 / --1 / -1-D1D2D2-1 / D2D3 -1D3D4D5D5 -1
5A1-1 / --1 / -1-1 / D1D1 -1D2D2 -1D2D3 -1D3D4 -1D5
6A1 -1A1d-1 / --D1 -1D1 -1D2D2 -1D2D3 -1D3D4
7A1 -1A1 -1A1-1 / -1-1 / D1D1D2D2D2 -1D3 -1D3 -1D3
8AA1A1 -1-1 / ---1 / D1D1 -1D2D2D2D2D3 -1
9A2 -1A2A1A1-1 / -1-D1 -1D1 -1D2D2D2 -1D2
10A2 -1A2 -1A1A1 -1-1 / --1 / -1-1 / D1D1D1 -1D2D2D2 -1
11A3 -1A3A2 -1A1A1-1 / ---1 / D1D1D1 -1D2D2
12A4 -1DA3 -1DA2 -1DA1DA1 -1A1-1 / -1-1 / -1-1 / -1-1 / -1-1 / D1 -1-1 / D2 -1
2, 3, 12
2, 3, 11, 12
2 - 4, 11 - 12
2 - 4, 10 - 12
2 - 5, 10 - 12
B5 / A42, 122, 3, 11, 122 - 4, 11 - 122 - 4, 10 - 122 - 5, 10 - 122 - 5, 9 - 12
+0.5
-1
-
-
-1
-1
-1
-1
-2
-1
-1
-1
-1
-1
-2
-2
-
-
-
D
D
D
DS
3---------DDD
-
-
-
D
D
D
D
3---------DDD