Resource Economies in Strategy Games

Look closely at almost any strategy game and beneath the banners and battles you will find a ledger. Wood comes in from the forest, grain from the fields, stone from the quarry; it goes out again as walls, as soldiers, as bread for mouths that never stop needing it. The player's real activity, hour after hour, is the management of that ledger, and their experience of the game, its tension and its pleasures, depends far more on its structure than on any particular number written in it.

Designers often speak of a game's economy as if it were a set of prices, and they tune it that way, nudging a cost up here and a yield down there. That tuning matters, but it comes second. First comes the shape of the system: where resources originate, where they disappear, how one resource is converted into another, and how the flows respond as a player grows. Get the shape right and the numbers can be adjusted; get it wrong and no adjustment will save it.

This essay looks at that shape. It covers the basic vocabulary of sources and sinks, the structure of production chains, the role of upkeep, the uses of scarcity in pacing, and the feedback loops that make some games runaway victories and others grinding stalemates. No statistics from particular titles are claimed here; the examples are structural, and the arithmetic in them is meant only to make mechanisms visible.

Sources and sinks

Every economy, at its simplest, consists of sources that add resources and sinks that remove them. Sources in strategy games are typically gathering sites and production buildings: a lumber camp, a farm, a mine, a tax on population. Sinks are anything that consumes: construction costs, unit recruitment, research, food eaten, tools worn out, gold paid to soldiers. The stock a player holds at any moment is simply the accumulated difference between the two.

An economy with strong sources and weak sinks inflates. Resources pile up faster than they can be used, choices stop mattering because everything can be afforded, and the late game becomes a matter of clicking build on every option. This is a familiar failure in strategy and in online games alike. An economy with weak sources and strong sinks deflates into misery, every action a painful sacrifice. The designer's task is to keep the two in a tension that shifts as the game progresses.

Sinks deserve more attention than they usually receive, because they are where meaning lives. A resource that is never spent is just a score. When grain must be eaten, timber burned for warmth, and gold paid to keep an army loyal, every unit of production is already partly claimed before it arrives, and the player's surplus, the part they may actually choose what to do with, becomes small, precious and interesting.

Food and the hungry population

Food is the oldest and most intuitive sink in the genre. Villagers must eat, and they eat continuously whether or not the player is paying attention. This makes population growth a double edged decision: each new villager adds labour, a new source of whatever they are assigned to gather, but also adds a permanent drain on the granary. Expansion is no longer free. It is an investment that must keep paying for itself.

Consider a small worked example. Suppose each villager eats one unit of food per day and a farm worked by one villager produces four. A settlement of ten villagers needs ten food a day; three farms yield twelve, leaving a surplus of two, while seven villagers remain free for other work. Add five more villagers and consumption rises to fifteen, so three farms now run a deficit of three. A fourth farm brings production to sixteen and restores a surplus of one, at the cost of another worker.

The interesting property here is that the food sink scales with exactly the thing the player wants to increase. Growth demands more farms, farms demand more workers, and those workers eat. The player is always balancing labour devoted to subsistence against labour devoted to everything else, construction, defence, crafting, and this balance is the true economic decision underneath the visible ones. A famine then arrives as the natural consequence of growing faster than the fields, rather than as a random punishment.

Production chains

A production chain is a sequence in which one resource is converted into another, often through several steps. Grain is ground into flour at a mill, and flour is baked into bread; ore and charcoal become iron, and iron becomes tools or weapons. The Settlers and Anno series are well known for chains of this kind, but even a simple game with logs turned into planks has the basic structure: raw materials enter, processed goods leave, and each step requires a building and usually workers.

Chains do several things a flat economy cannot. They create intermediate goods that can run short independently, so a player may have plenty of grain and still starve because the mill burned down. They spread the economy across space, which matters when transport takes time and roads can be cut. And they give players a satisfying sense of mastery as they learn to read the system, spotting the bottleneck where flour is piling up at one bakery while the others stand idle.

Chains also carry costs. Every link is a point where the player must understand ratios: how many mills a farm supports, how many bakeries a mill supplies. When those ratios are opaque, the result is frustration rather than mastery, and designers often provide clear interfaces showing input and output rates or use simple whole number ratios that can be remembered. Long chains also delay feedback, since a change at the start takes time to reach the end, which suits slow, contemplative games far better than quick ones.

Implementing chains cleanly in an engine like Unity tends to favour data over code. Recipes can be described as ScriptableObject assets listing inputs, outputs and processing time, and production buildings simply reference a recipe. This lets designers add or rebalance a chain without touching scripts, and it lets a debugging overlay display every building's current state, starved of input, blocked on output, or working, which is invaluable when diagnosing where an economy has seized.

Upkeep and the cost of size

Upkeep is a recurring cost paid simply for having something: gold per soldier per turn, maintenance per building, food per villager. Its purpose is to tie the size of what a player owns to a continuing burden, so that accumulation is never purely beneficial. Without upkeep, a player can build armies in peacetime and keep them forever. With it, every standing unit is a question asked again each turn, whether it is still worth what it costs.

Upkeep is also one of the main tools of pacing. If a large army drains the treasury, the player is pushed to use it rather than hoard it, which drives conflict forward. If buildings decay without maintenance, a sprawling settlement must keep a share of its labour devoted to repair, which naturally limits the rate of expansion. The designer can adjust how heavily size is taxed, and with that single dial influence whether players prefer tall, compact play or wide, sprawling empires.

Upkeep that rises faster than linearly is a particularly effective brake. If each additional unit costs slightly more to maintain than the last, there is a soft limit beyond which growth becomes uneconomic, and the limit emerges from the system instead of being imposed as a hard cap. Players tend to accept such limits more readily, because they feel like consequences of their own choices rather than arbitrary rules.

Scarcity and pacing

Scarcity is what makes economic decisions real. When a player can afford only one of three buildings, the choice reveals their strategy and commits them to it; when they can afford all three, there is no choice at all. Early game scarcity is usually acute, every resource contested, and designers rely on it to make the opening moves of a game feel weighty and distinct from one match to the next.

Scarcity can be global, a shortage of everything, or specific, an abundance of wood and a famine of stone. Specific scarcity is often the more interesting, because it pushes players toward trade, expansion to new deposits or substitution of one approach for another. Placement of resources on a procedurally generated map therefore becomes an economic act, deciding whether a given start will be a struggle for food or a struggle for metal, and generators often enforce minimum guarantees to keep starts fair.

Pacing comes from how scarcity changes over time. A well designed economy loosens its grip as the player builds infrastructure, offering a growing sense of abundance, then tightens again as new demands appear: an expensive technology, a larger threat, a new resource that the old infrastructure does not supply. The rhythm of tightening and release is what keeps a long game from flattening out into routine, and each new constraint renews the player's attention.

Feedback, snowballs and catching up

Economies in strategy games are riddled with feedback loops. A positive feedback loop occurs when success generates the means for further success: more villagers gather more food, which supports more villagers. Positive feedback is exciting, because it rewards good play with acceleration, but it amplifies small early advantages into overwhelming late ones. A player who gains a modest lead in the opening can find it compounding until the outcome is settled long before the game formally ends.

This snowballing is a central problem of competitive design. Negative feedback loops are the usual counterweight: mechanisms that make further growth harder as a player gets larger, such as rising upkeep, diminishing returns from additional workers at one site, or the attention of more enemies. Catch-up mechanics act more directly on the trailing player, offering bonuses, cheaper options or events that favour the weaker side, so that a game remains contested long enough to be worth finishing.

Balancing these forces is delicate. Too much negative feedback and skilled play feels pointless, since the system erases every advantage earned. Too little and matches end early in lopsided stomps. Many designers aim for strong positive feedback within a single system, so that good economic play is rewarded, combined with negative feedback across the game as a whole, so that no single advantage can carry a player to victory unanswered.

In single player games the same tools serve a different purpose. There the loops shape difficulty, and the threat the economy must answer, raiders, winter, the dark, can grow alongside the player's wealth, so that prosperity never quite becomes safety. The ledger, in the end, is a story told in arithmetic: of a small surplus guarded through a hard season, and of what a settlement chose to spend its bread on.