Medieval strategy and role-playing games 12 min read

Why medieval armies need more than a troop list

Medieval armies are often presented in games through a short list of unit types: levy, militia, spearman, archer, knight and mercenary. These labels are useful, but they can also hide the difficult questions that shaped warfare. Who recruited the soldiers? Who paid for their equipment? How long could they remain in the field? Would they obey orders under pressure? A convincing game model must deal with these practical issues as well as with weapons and armour.

The word levy usually describes people called to military service by a lord, ruler or community. It does not automatically mean an untrained peasant carrying a pitchfork. A levy might include men with useful experience, local weapons and some protection, but the quality and reliability of the group could vary greatly. A knight was not simply a stronger infantryman. The term points toward a social and military role connected with landholding, service, equipment, training and status. A mercenary served in return for payment or an agreed contract, although medieval military employment could involve mixed motives, local ties and political obligations.

Games turn these complicated realities into rules. The best systems do not necessarily include the most statistics. They give each category a clear function while showing the trade-offs behind it. A levy may be inexpensive and numerous but weak in morale. A knight may be powerful in the right terrain but costly to field and vulnerable when isolated. Mercenaries may offer specialist skills without requiring a ruler to maintain a permanent force.

What historical evidence can and cannot tell us

There was no single medieval army system. Recruitment and equipment changed according to period, region, political structure and campaign. An English force in the twelfth century cannot be treated as a universal model for a fourteenth-century army in Italy or the eastern Mediterranean. Game designers and players therefore need to identify the setting before deciding whether a rule feels plausible.

Several types of evidence help establish a framework:

  • Legal texts can show who was expected to serve and what equipment certain groups were required to possess. The English Assize of Arms of 1181 and the Statute of Winchester of 1285 are examples of documents that reveal official expectations, although they do not prove that every obligation was fulfilled in practice.
  • Administrative records can show payments, contracts, musters and supplies. The so-called White Company agreements and other late medieval military contracts illustrate how service could be organised through negotiated terms.
  • Chronicles describe battles, commanders and reputations, but they may exaggerate numbers or simplify events. They are most useful when compared with other evidence.
  • Archaeology and surviving equipment help establish what weapons and armour existed, but an object’s existence does not show how common it was or who used it.
  • Illustrated manuscripts provide visual clues about clothing, weapons and formations, though artists often worked with conventions rather than producing technical diagrams.

These sources support broad models rather than exact unit statistics. A game should make clear which parts are historical evidence and which parts are design decisions. That distinction helps players understand why a rule has been included without presenting an uncertain reconstruction as a proven fact.

Levies: quantity, local knowledge and limited endurance

Levies are often the foundation of a medieval army because rulers could call on local obligations more easily than they could maintain a professional standing force. Their main advantages in a game are usually availability, low cost and numbers. Their disadvantages should be more specific than a simple penalty to attack.

A levy system can model several realistic limitations:

  • Short service periods: people leaving farms or trades may not be available for a long campaign. A rule can increase upkeep or reduce morale after a set number of turns.
  • Uneven equipment: some levies may carry spears and shields, while others have improvised or outdated weapons. Instead of making every levy equally weak, a game can use equipment bands or a small number of quality categories.
  • Local loyalty: a levy may defend its home territory more willingly than it marches into a distant region. This can affect recruitment, desertion or willingness to accept losses.
  • Limited cohesion: a group gathered quickly may struggle to manoeuvre, exploit an opening or recover after its formation breaks.
  • Useful defensive roles: levies can guard walls, protect baggage, hold a village or delay an enemy. They should not be defined only by failure in open battle.

For a tabletop game, one practical approach is to give levies a low recruitment cost but a higher risk of retreat when neighbouring units break. In a strategy videogame, the same idea might appear through mobilisation time, regional unrest and a reduced campaign range. In a role-playing campaign, levies can be allies with local knowledge rather than disposable combat statistics.

Players should also avoid treating “peasant” as a synonym for “militarily useless.” Farming communities understood local roads, rivers, weather and fortifications. A levy unit may be poorly suited to a formal cavalry engagement while remaining valuable in an ambush, a fortified position or a supply-cutting operation.

Knights: social status translated into battlefield power

Knights are commonly modelled as elite heavy cavalry, and this captures an important part of their battlefield identity. Horses, armour, weapons and training required substantial resources. A mounted knight could deliver shock, threaten exposed formations and move quickly between parts of a battlefield. However, a knight was not automatically decisive in every encounter.

A useful game model separates at least four features:

  1. Protection: armour can reduce the effect of some attacks, especially poorly placed blows, but it should not make a knight immune to massed missile fire, polearms, terrain or fatigue.
  2. Mobility: mounted movement creates options for flanking, pursuit and rapid reinforcement. It becomes less useful in forests, marshes, steep ground, narrow streets and prepared obstacles.
  3. Shock: a charge can disrupt an unsteady formation. The impact should depend on speed, cohesion, formation, ground and whether the target is prepared.
  4. Command and status: high-status warriors may improve morale or leadership, but their loss can also have political and psychological consequences.

Mounted combat should not be reduced to a permanent damage bonus. A knight may dismount to fight on foot, defend a breach or operate in difficult ground. Historical armies often combined mounted and dismounted roles according to the mission. Rules that allow a unit to change posture at a cost can create better tactical choices than rules that force every knight to remain mounted.

Cost is another essential part of the model. If knights are powerful and inexpensive, the game encourages ahistorical armies made entirely from elite troops. Their price can be represented through recruitment resources, upkeep, limited availability, political obligations or the need to protect valuable horses. A balanced system does not need to make knights weak. It needs to make their advantages depend on circumstances.

Mercenaries: contracts, specialist skills and uncertain loyalty

Mercenaries are often described as soldiers who fight only for money. That is too narrow for game design. Medieval military employment could involve contracts, political alliances, personal followings, debt, land grants, religious commitments and the search for employment after a conflict. Payment remained important, but loyalty was not always a simple choice between gold and betrayal.

Mercenary units work best in games when they fill a clear capability gap. Examples include crossbowmen, mounted troops, engineers, experienced infantry, sailors or soldiers familiar with a particular type of warfare. Their value can be balanced through several mechanics:

  • Upkeep: a contract may require regular payment. Failure to pay can reduce morale, remove special abilities or trigger renegotiation.
  • Availability: specialist troops may appear only in certain regions, seasons or political circumstances.
  • Contract length: a unit may be reliable for a defined period but leave when the agreement ends.
  • Political risk: hiring foreign or rival troops may upset local elites, create diplomatic problems or increase tension with the population.
  • Professional cohesion: experienced soldiers may manoeuvre more effectively and recover from disorder faster than a newly raised levy.

It is usually more interesting to model mercenaries as dependable within limits rather than as random traitors. A contract dispute, unpaid wages or a change in strategic purpose gives players a reason to manage relationships. Random betrayal without warning may create drama, but it teaches little about the economic and political conditions that made military employment possible.

Morale, cohesion and command matter as much as weapons

Many games focus on attack and defence values while giving morale a small supporting role. Medieval warfare benefits from the opposite approach. A formation could lose a battle because it became disordered, isolated, frightened or unable to understand commands, even if many of its soldiers were still alive.

Morale and cohesion should be related but not identical. Morale concerns willingness to continue. Cohesion concerns the ability to act as an organised group. A disciplined mercenary unit might retain cohesion after taking losses, while a levy might remain willing to defend its village but lose formation during an advance. A knightly retinue might have high morale because of shared status and leadership, yet suffer badly if its commander is killed.

Practical rules can include:

  • morale checks after a commander falls, a flank is exposed or a neighbouring unit routs;
  • cohesion penalties for difficult terrain, night movement, poor communication and rapid changes of direction;
  • benefits for standards, drums, recognised leaders and prepared positions;
  • different responses to defeat, such as an orderly withdrawal, local retreat or complete rout;
  • recovery rules that reward rest, resupply and effective leadership.

Command range is another useful abstraction. Orders travelled slowly and battlefield visibility was limited. A system can represent this without requiring players to calculate historical signalling distances. For example, units outside a leader’s command range might follow their last order, act defensively or require a successful command test before changing direction.

Logistics: the rule that prevents endless campaigning

Armies need food, water, fodder, equipment, replacement horses and money. Logistics is sometimes omitted because it appears less exciting than a charge, but it provides the reason why campaigns have routes, pauses and objectives. It also prevents the strongest units from operating at full effectiveness indefinitely.

A game does not need to track every sack of grain. A practical logistics system can use a few meaningful variables:

  • Supply sources: towns, castles, ships, roads and captured stores can sustain an army.
  • Consumption: larger armies should consume more, with horses creating particular demands for fodder.
  • Distance: an army far from its base should face higher costs or greater risk.
  • Season and terrain: roads, harvests, rivers and weather can affect movement and supply.
  • Baggage: equipment, camp followers and supplies slow an army but increase its endurance.

Logistics also changes the role of each troop type. Levies may be numerous but hard to keep assembled. Knights require valuable horses and equipment. Mercenaries require payment at an agreed time. A mixed army therefore creates an administrative challenge as well as a tactical advantage.

For families and new players, logistics can be introduced through a simple campaign rule: an army must end each turn in a supplied location or lose readiness. More advanced groups can add forage, damaged equipment, ransom, prisoners and seasonal movement. The aim is not to reproduce every medieval account book. It is to make strategic preparation matter.

Terrain and formations should change what each unit can do

Unit labels have little meaning if every battle takes place on an open flat field. Terrain is where the differences between levies, knights and mercenaries become visible. A dense formation of spearmen may be difficult for cavalry to break from the front. Archers need suitable lines of sight and protection. Mounted troops lose some advantages in narrow or broken ground. Local troops may gain information or movement benefits in familiar terrain.

Useful terrain categories include:

  • Open ground: favourable for mounted movement and large formations, provided the surface is firm enough.
  • Woodland: reduces visibility and limits cavalry manoeuvres, while offering cover and ambush opportunities.
  • Marsh and steep ground: slow movement and increase disorder, especially for horses and heavy equipment.
  • Settlements: create defensive positions but restrict movement and can turn combat into a costly close engagement.
  • Fortifications: change the balance between attackers and defenders, making preparation, artillery, engineering or blockade relevant.

Formation rules should remain playable. A few clear states, such as line, shielded formation, column and disordered, are usually more useful than a long list of technical formations. Each state should have a purpose and a cost. A shielded formation might resist missiles but move slowly. A line might fight effectively but become vulnerable if its flanks are exposed.

How to judge whether a game model feels convincing

Historical accuracy is not the only measure of a good game. A model can simplify the past while still encouraging historically informed decisions. Players can test a system with a short checklist:

  1. Does recruitment have a cost beyond money? Time, politics, obligations and local stability can all matter.
  2. Can different troop types perform useful non-combat roles? Scouting, guarding supplies, holding crossings and defending walls should not belong only to elite units.
  3. Are elite troops powerful but limited? Their cost, availability, terrain and endurance should shape deployment.
  4. Can morale and command change a battle? Victory should not depend only on reducing hit points.
  5. Does the campaign system reward preparation? Routes, supply and seasonal timing should influence decisions.
  6. Are uncertain historical details presented as choices rather than facts? A game can offer alternative rules for different interpretations.

A useful exercise is to build a small force with one levy unit, one professional or mercenary unit and one knightly unit. Give each a distinct task before the battle begins. The levy might secure a village, the mercenaries hold a difficult flank and the knights remain in reserve. If the game makes these roles meaningful, its army model is likely doing more than assigning different attack values.

Designing a balanced medieval army for play

When creating a force for a board game, miniature battle or digital strategy scenario, begin with the objective rather than the strongest available units. A force defending a bridge needs different qualities from an army raiding a border or besieging a town.

A practical planning sequence is:

  1. Define the mission, such as holding ground, escorting supplies, raiding or breaking a siege.
  2. Choose a reliable core that can remain cohesive when the first attack fails.
  3. Add levies for numbers, local defence and control of objectives.
  4. Add knights or other elite troops as a reserve, striking force or command element rather than placing them everywhere.
  5. Use mercenaries to cover a specific weakness, not simply to increase every statistic.
  6. Set aside resources for upkeep, replacements and movement.
  7. Decide what happens if the army loses its commander, supply line or main position.

This approach creates decisions that resemble the pressures of medieval campaigning without claiming that every historical army followed one template. It also works across different game formats. A family game can use three troop categories and a few morale tokens. A detailed miniature system can add equipment, formation and command rules. A role-playing game can turn recruitment into political choices and personal obligations.

FAQ: Medieval armies in games

Were levies always poorly trained?

No. Training, equipment and experience varied. Levies were often less consistently organised than professional retinues, but they could provide effective local defence and might include people with previous military experience.

Were knights always mounted?

No. Knights were associated with mounted warfare, but they could fight on foot when terrain, tactics or defensive needs made that appropriate. Games should treat mounted and dismounted roles as meaningful options.

Did mercenaries always betray their employers?

No. Contracted troops could be reliable when paid and properly commanded. Their distinctive risks concerned contracts, wages, political alignment and the end of their agreed service, not an automatic tendency to treachery.

What is the most important rule for modelling a medieval army?

Make recruitment, morale, terrain, command and supply affect decisions alongside combat strength. A list of weapons alone cannot explain why armies were organised in different ways.

How can beginners explore the subject without using complex rules?

Start with three unit types, one supply rule, two morale effects and several terrain features. Expand only when a new rule creates a decision that players could not previously make.

Learn more about this: