Chapter 11: Supply, Morale, and Other Subsystems

Every wargame has a mechanical core: movement, combat, sequence of play. Those systems carry the game. But the subsystems surrounding that core determine whether the simulation feels like the conflict it represents or like a puzzle with military graphics. A game about the Eastern Front without supply pressure is not a game about the Eastern Front. A Napoleonic battle without morale collapse is missing the mechanism that decided most engagements of that era. Supply, morale, command, weather: these are the connective tissue between your core mechanics and the historical reality you are trying to model.

I have heard designers say that most games get supply wrong. I disagree. Supply is one of the more straightforward things to model within a reasonable degree of plausibility. It does not require exotic mechanics or elaborate subsystems. What it requires is that the designer understand what supply is doing in the simulation and implement it at the right level of abstraction for the game’s scale. The same principle applies to morale, command, and every other subsystem discussed in this chapter. Include what the simulation demands. Abstract what it does not. Cut what adds complexity without adding decisions.

Supply

Supply is a gate. Its purpose in your design is to force players to operate within the logistical constraints that real commanders faced. At tactical scale, supply rules are rarely necessary. Turns representing five to thirty minutes of combat do not create situations where units run out of ammunition or food. The logistical infrastructure supporting a tactical engagement exists below the resolution of the game, handled by quartermasters and supply sergeants the player never sees. Supply becomes a design concern at grand-tactical scale and above, where turns represent hours or days and the question of whether a formation can sustain operations over that timeframe becomes relevant. A player who can attack anywhere on the map with full strength regardless of where their supply lines run is not making the decisions that the historical commander made. Supply forces the player to think about where their forces are relative to their rear area, which roads and railheads matter, and what happens when those lines get cut. If your game is about a conflict where logistics shaped the campaign, supply needs to be in the design. If logistics were not a significant constraint, abstract their effect into other systems and move on.

The simplest supply model, and the one I use most often, is the supply trace. A unit traces a line of hexes from its position back to a supply source: a map edge, a city, or a depot. If the trace is unblocked by enemy units or their zones of control, the unit is in supply. If the trace is blocked, the unit is out of supply and suffers penalties. The penalties vary by game: reduced combat strength, restricted movement, inability to attack, eventual elimination if unsupplied for multiple turns.

The supply trace works because it creates a spatial problem. The player does not just think about where to attack. They think about the path between their attacking units and the source keeping them fed and armed. Cutting an opponent’s supply line becomes a viable strategy, sometimes more effective than direct assault. An armored spearhead that drives deep into enemy territory and severs a supply line can paralyze an entire sector of the front without firing a shot. That kind of operational decision is exactly what supply mechanics should produce.

Zones of control interact with supply in ways that need careful handling. In most of my games, an enemy ZOC blocks supply trace unless the hex is occupied by a friendly unit. This is important. If ZOCs block supply unconditionally, a single enemy unit can cut supply to an entire army by sitting on a road hex, which is unrealistic at most scales. Friendly units in the hex negate the ZOC for supply purposes because in reality, a garrison or rear-area force would keep the road open. This exception matters more than designers sometimes realize.

At a granular level, supply shortages affect different unit types differently. A World War II armored division that cannot trace supply might be immobile. No fuel means the tanks do not move. An infantry division in the same situation can still march and fight, with reduced effectiveness because their ammunition and rations are running low. If your game operates at a scale where this distinction matters, your supply rules should reflect it. A blanket “out of supply units have halved strength” is adequate for many games, but if you are designing an operational treatment of a mechanized campaign, differentiating between fuel-dependent and foot-mobile formations adds a meaningful layer of decision-making.

The timing of the supply check within your sequence of play matters, as I discussed in the previous chapter. Checking supply at the start of the turn before movement means a player cannot maneuver out of a supply crisis before it takes effect. Checking at the end means disruption is temporary and correctable. Neither is wrong, but the choice determines how punishing supply problems are, and that should match the historical weight logistics carried in your conflict.

Some games track supply with more granularity than a simple trace, and some of those games are better for it. Der Weltkrieg, the massive World War I strategic series published by Rand Game Associates, tracks supply by subtracting supply points for attacks and defense. That sounds tedious, and in a less careful system it would be. But Der Weltkrieg is operating at a scale and complexity level where that granularity pays off. The supply point expenditure forces players to husband their resources and choose where to commit offensive effort with real economic weight behind the decision. The system works exceptionally well for what it is trying to do.

DAMOS, my operational series, takes a modular approach to supply that I think illustrates how supply mechanics should be tailored to the theater being simulated. The supply system is not standardized across the series. Each title implements supply rules specific to its conflict, because the logistical challenges of Barbarossa have almost nothing in common with the logistical challenges of North Africa.

In the Barbarossa titles, supply revolves around rail gauge conversion. The Germans must convert captured Soviet broad-gauge rail to European standard gauge before they can use it. Conversion extends 1d3 hexes per turn along the rail line. Meanwhile, the German non-rail supply trace is only 3 hexes from the nearest railhead, reduced to 2 hexes in winter. The Russians trace 5 hexes with no winter reduction. That asymmetry is the entire logistical story of Barbarossa in mechanical form. The further the Germans advance, the longer and more fragile their supply lines become. The pace of the rail conversion determines how fast the advance can sustain itself. Every hex gained stretches the line thinner. The player feels the culminating point approaching without the rules having to announce it.

In the North Africa titles, supply works differently. Physical Supply Unit counters represent logistics assets. These counters operate in two modes: mobile mode, truck columns that can only supply adjacent units, and deployed mode, established fuel dumps that project supply within a 4-hex radius. The Rommel marker can exempt one force from line of communication requirements per turn, modeling Rommel’s historical tendency to outrun his logistics through sheer audacity. Random events introduce fuel shortages, sandstorms, and convoy arrivals that directly impact the logistical situation. The desert war was defined by the supply line running along the coast road, and the supply system makes that road the spine of the entire game.

The key teaching point from the DAMOS approach is that supply mechanics should be designed for the specific conflict you are simulating, not imported wholesale from another game. A generic supply trace works for many subjects. But when logistics are central to the historical narrative, a tailored system does more to put the player in the commander’s seat than any amount of combat chrome.

If logistics do not have realistic impact in your game, it invites skepticism from informed players. The effect is similar to what happens when movement rates are wrong: the simulation loses legitimacy. A game about the 1941 Eastern Front where German panzers can operate 200 miles ahead of their railheads without consequence is not simulating Barbarossa. It is wearing Barbarossa’s uniform while ignoring everything that made the campaign what it was. Supply is a subtle mechanic, often working in the background, but the constraints it provides are essential to giving the player the correct decision space.

Morale

The importance of morale in your design depends on scale. At tactical and grand-tactical scales, morale is often the decisive mechanical factor. Firefights at squad and company level are won or lost based on which side breaks first. The physical destruction of a force matters less than its willingness to keep fighting. At operational and strategic scales, morale becomes abstracted into other systems or modeled through broader mechanisms that represent organizational cohesion rather than individual courage.

The most common tactical morale mechanic is the morale check. A unit has a morale rating printed on its counter. When triggered by incoming fire, casualties, or proximity to a threat, the unit rolls a die. Equal to or below the morale rating means the unit holds. Above means it falters. The consequences of failure vary: disruption, suppression, retreat, rout, or some combination depending on how badly the check was failed.

This is a proven mechanic because it does two things at once. It introduces uncertainty into combat beyond what the CRT provides, and it differentiates unit quality in a way that matters every time fire is exchanged. Elite troops with a morale rating of 8 on a d10 shrug off situations that send conscripts with a rating of 4 running. That distinction creates asymmetric gameplay without requiring separate rules for different troop types. The morale rating does the work.

At grand-tactical scale, morale often operates at the formation level rather than the individual unit level. A corps or division accumulates losses until it crosses a threshold, at which point the entire formation becomes demoralized. This is closer to how organizational breakdown actually works at that scale. A corps does not collapse because one regiment breaks. It collapses because cumulative losses erode the organization’s ability to function as a coordinated fighting force.

Imperial Bayonets uses this approach. A corps becomes Demoralized when its infantry strength point losses reach 40% of its starting total. The effects are severe: initiative reduced by 1, combat strength halved, no advance after combat, no construction of improved positions, no zone of control projection. The corps is not destroyed, but it is combat-ineffective until it can rebuild past the threshold. That recovery process carries its own risk. Demoralized units that roll a 5 or 6 on their initiative check during the recovery phase are permanently eliminated, not just reduced but removed from the game entirely. This models the historical reality that shattered formations attempting to reconstitute under pressure sometimes disintegrated completely. The 40% threshold and the permanent elimination risk together create a system where players must manage their corps’ exposure carefully. Committing a corps too aggressively risks pushing it past the threshold into a state that is difficult and dangerous to recover from.

Not every army in Imperial Bayonets uses the same morale structure. Italy and Piedmont-Sardinia track army-wide morale rather than per-corps morale because they lack corps-level organization. The morale mechanic adapts to the force structure of the belligerent, which is how subsystems should work: the implementation follows the history, not the other way around.

Rout is a related but distinct concept from morale failure. A disrupted or broken unit retreats in some order. A routed unit flees. The distinction matters most at tactical scale and in earlier historical periods where all-out routs were common. Ancient and medieval battles often ended with one side’s army dissolving into a panicked mass fleeing the field, suffering more casualties in the rout than in the battle itself. Marathon, one of my ancient tactical designs, includes rout movement and rout status that trigger when units accumulate enough disruption points. The transition from fighting to running captures something essential about ancient warfare that a simple retreat result on a CRT cannot.

At later periods and larger scales, rout becomes less common as a mechanic. Napoleonic armies routed, but the phenomenon was more localized. Individual battalions broke, not entire wings of an army at once (with notable exceptions like Jena). By the twentieth century, units that collapsed under pressure were more likely to surrender or disperse than to flee en masse. ASL is a notable exception: it includes rout movement for a World War II tactical game, but ASL is an exceptionally granular simulation that models squad-level behavior in detail most tactical games do not attempt. The complexity of ASL’s rout rules is part of why the system has a reputation for being among the most difficult rulesets in the hobby. Most WWII tactical designs abstract that behavior into retreat results on the CRT. Match your morale mechanics to the period, the scale, and the level of granularity you are willing to support.

At strategic scales, morale can be rationalized into a small strength point bonus or a relevant variable rather than a separate subsystem. A veteran division on the Eastern Front with higher morale than its opponent does not need a morale check mechanic. Its advantage can be built into its combat rating or applied as a column shift. The designer’s job is to decide at what point morale stops being a separate system and starts being a component of existing systems. There is no universal answer. It depends on the game.

Command and Control

Command systems follow the same scaling principle as morale. At lower scales, command is literal: units need to be within range of their headquarters to function at full effectiveness, and the mechanics model the physical communication links between commanders and their subordinates. At higher scales, command becomes abstracted into limits on how many actions a player can take or how many formations can be activated.

Sedan 1940 has one of the more detailed command systems in my designs. Each headquarters unit has a Radio Value. At the start of the turn, each HQ makes a Radio Communications Check by rolling 1d6 under its Radio Value. A failed check means the HQ is Out of Command. All units under an Out of Command HQ lose indirect fire capability and cannot receive air support. The radio represents the link between the off-map corps headquarters and the divisional HQs on the map. A single bad radio roll grounds an entire division’s long-range artillery coordination. Units outside their HQ’s Command Range suffer similar penalties regardless of the radio check: no indirect fire, a leftward column shift in assaults, no prepared assaults.

This system works for Sedan 1940 because the 1940 campaign was defined by command and control. The French collapse was as much about communication breakdown and decision paralysis as it was about German tactical superiority. Gamelin’s headquarters had no radio. Orders took days to reach the front. The German advantage was not just better tanks but faster decision-making at every echelon. The command system makes the player feel that asymmetry every turn.

At operational and strategic scales, I tend to implement command through HQ units that provide bonuses to attached or in-range units. An HQ within range provides a combat bonus, a movement bonus, or enables capabilities that units cannot access on their own. Units outside HQ range suffer penalties or lose access to certain actions. This is a lighter touch than the Sedan 1940 system, but it creates the same fundamental pressure: keep your forces within the command structure or pay a price.

Activation rolls and order delays make the most sense at tactical and grand-tactical scales, where individual commanders are making decisions that directly affect the units under them. A battalion commander freezing under fire or a brigade commander misinterpreting an order are tactical events. At strategic scale, these become abstractions. A theater commander’s indecision is better modeled as a limit on the number of offensive operations that can be launched per turn than as a die roll per HQ.

Like supply, command is a logical in-system gate, but it tends to be less subtle in its effects. A unit that is out of command suffers obvious, immediate penalties. A unit that is out of supply might function normally for a turn or two before the effects bite. That difference in immediacy matters for design. A bad radio roll forces the player to react now. A severed supply line gives them a turn or two to fix the problem before it becomes critical. Both produce tension, but of different kinds.

One practical concern: if your design already carries a complex supply system, think carefully before layering an equally complex command system on top of it. Players have a finite tolerance for administrative overhead. A game where every turn requires tracing supply for every unit and checking command range for every unit and rolling radio checks for every HQ is a game where the administrative phases take longer than the movement and combat phases. That is a problem. If supply is the more important logistical story for your conflict, keep command simple. If command breakdown is the central theme, you can afford to abstract supply. Some games carry both with full weight, but those games are designed for a specific audience that accepts that overhead as part of the experience.

Engineering, Bridging, and Fortification

Engineering capabilities (bridge construction and demolition, field fortifications, obstacle clearance) appear in wargames when the conflict demands them. These are not universal subsystems like supply or morale. They are tools the designer reaches for when a specific historical situation requires them.

The question to ask is whether engineering creates a meaningful decision for the player. If a river crossing is a major obstacle that shaped the historical campaign, then bridging rules that allow the player to build, protect, and destroy bridges add a real decision. If rivers are minor terrain features that slow movement by one hex, a separate bridging subsystem is overhead without payoff.

The same logic applies to fortifications. If the conflict you are simulating featured significant defensive construction, like the Western Front in 1914-1918, then rules for building and occupying fortified positions matter. If defensive positions were improvised and temporary, the effect can be abstracted into a terrain modifier or a combat status like “dug in” without a separate construction mechanic.

Some designers handle engineering by abstracting its function into basic rules rather than representing individual pioneer or engineer units. Infantry units that can provide their own river-crossing assistance, at some cost in movement or combat effectiveness, capture the engineering function without requiring separate counters and separate rules. The player gets the decision, do I spend the extra movement points to cross the river or find another way, without the mechanical overhead of managing engineer assets. This approach works well at scales where individual engineer battalions are below the resolution of the game.

When you do include engineering as a distinct system, keep it tightly scoped. Engineer units should have clear capabilities: they build bridges in X turns, they demolish bridges as a combat action, they clear obstacles at a cost of Y movement points. Do not let engineering become an open-ended subsystem where players can construct arbitrary fortifications anywhere on the map unless the conflict specifically revolved around that capability.

Weather and Environmental Effects

Weather belongs in your game if it affected the campaign you are simulating. Russian winter, Mediterranean storms, monsoon seasons, North African sandstorms: these are not flavor. They shaped operational decisions and constrained what armies could do. A game about Barbarossa where winter has no mechanical effect is ignoring the single most important environmental factor of the campaign.

The standard implementation is a weather table rolled at the start of each turn. The result modifies movement costs, combat effectiveness, and sometimes supply. Clear weather means normal operations. Rain or mud increases movement costs and may penalize attackers. Snow or extreme cold can restrict mechanized movement, reduce combat effectiveness, and shorten supply range. The weather table should be calibrated to the historical climate of the theater. A game set in the Sahara should not have the same weather table as a game set in Norway.

Weather is most useful when it forces the player to adapt rather than just imposing penalties. If rain turns roads to mud and doubles movement costs, the player has to decide whether to push forward slowly or wait for better weather. If winter reduces supply range, the player has to consolidate their position before the season changes. Those are real decisions driven by environmental constraints, and they mirror the decisions historical commanders faced.

The DAMOS North Africa titles integrate weather through random events rather than a separate weather phase. Sandstorms arrive without warning and shut down operations. This approach suits a theater where weather was episodic rather than seasonal. You cannot predict when a sandstorm will hit, so you cannot plan around it with certainty. That unpredictability matches the historical record and produces interesting decisions about risk.

Political Constraints

Some conflicts cannot be simulated without modeling the political context that constrained military action. Coalition warfare imposes limits on how allied forces can be used. National morale creates pressure to achieve objectives within a timeframe. Political events can force offensives or mandate withdrawals that make no military sense.

These constraints are specific to the conflict, and they should be implemented as scenario rules or special rules rather than core systems. A game about the Italian front in 1866 might require the Italian player to launch attacks against fortified positions because the political situation demanded offensive action regardless of military logic. A game about coalition operations might restrict which allied units can stack together or operate in the same sector.

Political constraints should create the correct decision space for the player. If the historical commander had to balance military logic against political pressure, the player should face the same tension. If the political situation did not constrain military operations, skip the political rules.

Integration and Restraint

Every subsystem discussed in this chapter can improve your simulation or burden it with overhead that distracts from the core gameplay. The decision about what to include is about what creates meaningful decisions for the player within the scope of the conflict you are simulating.

Supply, morale, and command are the three subsystems that appear most often in wargames because they represent the three universal constraints on military action: armies need to be fed, soldiers need to be willing to fight, and commanders need to communicate with their forces. Most games need at least one of these modeled explicitly. Many need two. Few need all three at full complexity.

The subsystems you include should reinforce each other and support the game’s central theme. If your game is about the logistical challenge of sustaining an offensive deep into enemy territory, supply should be the dominant subsystem. Morale and command can be abstracted. If your game is about the breakdown of an army’s fighting spirit under relentless pressure, morale should be the dominant subsystem. If your game is about the communication failures that led to a military disaster, command should take center stage.

Kevin Zucker’s skepticism of chrome applies here more than anywhere else in the design process. Every subsystem you add runs every turn. Every supply check, every morale roll, every command range measurement adds time to the game and complexity to the rules. Include what the simulation demands and what produces interesting decisions. Abstract everything else. The player should spend their time maneuvering and fighting, not administering.

I have seen designs collapse under the weight of subsystems that did not justify their presence. A game that takes twenty minutes of administrative phases before the player gets to move a single unit has a subsystem problem. The subsystems exist to serve the simulation. The simulation does not exist to showcase the subsystems. Keep that hierarchy clear in your design.