Combat Strength and Force Conversion
Rule in the game
Game rule
Combat compares unit strength and situational modifiers to determine damage. Melee, ranged, bombard, anti-unit roles, fortification, terrain, health, and support effects mean nominal unit count is not equivalent to effective force.
This dossier treats that rule as a deliberately small model. It describes what the standard Gathering Storm rules make causally important without importing the Civilopedia’s historical-context prose or treating game balance as evidence about history.
Model
Inputs: unit statistics, health, position, support, terrain, visibility, and matchup modifiers.
Process: relative strength is converted nonlinearly into reciprocal or one-sided damage.
Outputs: surviving force, destroyed units, positional change, and experience.
The useful unit of analysis is the conversion chain rather than any isolated number. An input can be abundant while the process that makes it usable is missing; an output can be impressive while its recurring supports are fragile. Reading the mechanic in this order also separates enabling conditions from the visible result the interface rewards.
Conditions
A unit must be able to reach, see, and legally attack its target. Damage changes future strength, and specialized classes perform differently against cities or particular opponents.
These conditions define the mechanic’s boundary. They identify prerequisites, timing, position, and capacity that must be present before the modeled conversion works. They also show why copying the output without its supporting system is unlikely to reproduce the same result.
Feedback
Victories preserve experienced units that gain promotions and fight more effectively, compounding advantage. Damage and attrition reduce combat power even before a unit is destroyed.
The mechanism kinds recorded in frontmatter name the dominant behavior: conversion-exchange, contest-bargaining-coalition, information-uncertainty. These labels make it possible to compare structurally similar dynamics across otherwise different game systems.
Strategic tension
Concentrated force can overwhelm a point quickly, while combined and distributed force covers roles and terrain but is harder to coordinate.
The tension matters because neither side is simply an error. A robust strategy must decide which risk is tolerable, what horizon matters, and which complementary capacities can compensate for the chosen sacrifice.
System connections
This dossier belongs to Conflict and Security. Its upstream inputs are supplied by other mechanics in those maps, while its outputs become conditions for later growth, coordination, exchange, conflict, or adaptation. Following those links is more informative than treating the dossier as a self-contained encyclopedia entry.
Cross-system placement is intentional. The same game rule can be an output in one map and a constraint in another; the Rulebook records both roles so causal chains remain visible across editorial categories.
Analytical translation
Analytical translation
Material units become effective power only through position, information, combined roles, and survival. Force is a conversion system, not a simple inventory.
This translation is a research prompt, not a historical conclusion. It suggests variables and relationships to investigate: who controls the inputs, which institution performs the conversion, where thresholds sit, who receives the output, who bears maintenance or external costs, and how alternatives change the balance of power.
Any later historical case must independently establish those facts. Resemblance to the game’s interface is never enough; a case may support the translation, narrow its scope, expose an omitted mechanism, or reject it.
Limits of the analogy
Limit
Combat is resolved by transparent statistics between obedient units. Morale, logistics beyond movement, command failure, civilians, weather, intelligence deception, and political objectives are radically simplified.
Three general distortions also apply. First, the player has centralized objectives and unusually broad information. Second, turns compress time and make many changes discrete, synchronized, and measurable. Third, game entities obey stable rules, while real actors interpret rules, bargain over them, and change them. Numerical tuning establishes a strategic trade-off inside the simulation; it does not establish the magnitude or even the existence of an equivalent historical effect.
Derived rules
- Force Projection Is Logistical — Force projection is a logistical achievement rather than force strength alone.
Sources
The facts in Rule in the game are original paraphrases of these Civilopedia pages. The links are evidence for the game mechanic only, not for historical claims.
civ6-gs:concepts/combat_1— Introductionciv6-gs:concepts/combat_5— Unit Combat Statisticsciv6-gs:concepts/combat_7— Combat Bonuses