Company of Heroes: the RTS that made cover matter
Relic took a squad off the open ground and the whole genre noticed

Contents
Relic Entertainment released Company of Heroes in September 2006, and the thing every review from that year fixates on is the same thing that still holds up: a soldier standing behind a low wall is a different tactical object from the same soldier standing in an open field, and the game makes you feel that difference every time a machine gun opens up. Cover in Company of Heroes isn’t a passive damage-reduction stat tucked in a tooltip. It’s rendered as visible states — heavy cover behind a stone wall or inside a building, light cover behind a hedge or a low ridge, negative cover for units caught crossing open ground under fire — and the AI reads the terrain to path squads toward it automatically, which means a huge amount of the tactical texture comes from where the map lets you stand rather than from a menu of unit abilities.
That single decision reorganises everything else about how the game plays. Squads, not individual units, are the base unit of control — a rifle squad might be four or five soldiers who lose members one at a time and can be reinforced back to strength from a nearby command post, which means losses are gradual and legible rather than a unit simply vanishing. Suppression is a second layer on top of cover: sustained machine-gun fire pins a squad in the open, dropping its return fire and movement to near zero until it either finds cover or gets flanked and finishes off, which is the moment Company of Heroes stops resembling a resource-and-build-order RTS and starts resembling a small-unit tactics problem. You don’t win a firefight by having more dudes. You win it by having dudes somewhere the enemy’s line of fire can’t reach, which is a genuinely different skill from the base-building tradition the genre had been running on.
Why the resource triangle keeps the map moving
Company of Heroes ties its three resources — manpower, munitions, and fuel — to territory control on a point-to-point map rather than the tile-grid resource nodes of a Command & Conquer or a StarCraft. Capturing and holding strategic points on the connective graph between your base and the front line feeds all three resources at different rates, which means the front itself is the thing worth fighting over, not a separate economic layer sitting behind it. Munitions in particular gates the abilities that make positioning pay off — smoke barrages to break a stalemate, off-map artillery to root out entrenched cover, demolition charges to breach a wall the enemy’s been hiding behind — so the tactical layer and the economic layer are the same conversation rather than two systems bolted together. Destructible terrain closes the loop: a building providing heavy cover for a dug-in squad can be shelled into rubble, at which point it stops providing cover at all, which means no defensive position on the map is permanent and a stalemate always has an answer if you’re willing to spend the munitions for it.
The idea that positioning and squad cohesion should carry more weight than base-building didn’t appear from nothing at Relic. The studio’s previous release, Warhammer 40,000: Dawn of War in 2004, had already experimented with squad-based control and a morale system that could break an entire unit’s will to fight rather than simply reducing a health bar, and Company of Heroes reads as that idea taken further and grounded in a setting where terrain and cover carry real historical weight. Relic’s other major lineage runs back to Homeworld, the fully three-dimensional space RTS the studio shipped in 1999, and the throughline across both games is the same instinct: make losses persistent and meaningful rather than an interchangeable resource to be replaced, whether that’s a veteran capital ship in open space or a rifle squad that’s been fighting since the drop onto the beach.
The genre it was arguing with
Company of Heroes landed at a moment when the dominant RTS template — descended most directly from Dune II, which had established base-building, tech trees, and a resource-harvesting economy as the genre’s load-bearing structure back in 1992 — had spent over a decade refining that same formula into games like Age of Empires and Command & Conquer, where the skill ceiling lived mostly in economic efficiency and unit-composition counters. Company of Heroes didn’t reject that lineage outright; it still has bases, tech trees, and resource management. But it shifted where the skill actually lived, from “who macros faster” to “who reads the map better,” and that shift is why the game still gets cited as the moment the WWII RTS subgenre grew up. The series carried the idea forward across two further mainline entries, most recently the Mediterranean and North African campaigns of Company of Heroes 3, which kept the cover-and-suppression core while pushing the strategic layer outward into an operational map between battles.
The competitive scene the cover system enabled
Company of Heroes’s emphasis on positioning over pure economic macro made it an unusually good competitive game, and it built a genuine esports following in the years after release, with organised leagues and tournament circuits running well into the sequel’s lifespan. Two later expansions, Opposing Fronts and Tales of Valor, added new factions — the British Commonwealth forces and the Panzer Elite among them — each with their own take on the resource-and-cover formula rather than simple reskins of the original two sides, and each new faction’s release shifted the competitive metagame enough that the top-level strategies from the base game’s early tournaments stopped being the whole story. Commander trees, introduced in Opposing Fronts, let players choose between several branching sets of unit unlocks and abilities before a match started, adding a genuine pre-game strategic layer on top of the in-match cover-and-suppression tactics, a system the series has kept refining across every subsequent entry.
That competitive depth is a direct consequence of the cover system rather than something bolted on top of it. Because positioning carries so much weight, a Company of Heroes match between two skilled players tends to be legible even to a spectator in a way a pure build-order race often isn’t — you can watch a squad get caught in the open and understand immediately why it’s about to lose the engagement, the same way a chess spectator can see a piece hanging before it’s taken. That legibility, more than the resource economy or the tech trees, is what separated the game’s esports scene from the earlier RTS tournament circuits built around games like StarCraft: Brood War, where the skill on display is often invisible to anyone who hasn’t mastered the same execution speed themselves.
What still works and what’s aged
The campaign’s voice acting and mission scripting feel dated now — the story is functional rather than memorable, built to string battles together rather than stand on its own. And the AI’s cover-seeking, while a genuine leap for its time, occasionally still produces the specific, slightly absurd failure where a squad under fire paths itself into cover on the far side of a building from where the shots are actually coming, wasting several seconds it doesn’t have. But the core loop — advance a squad, watch it take fire, decide whether to push it into cover or pull it back, spend munitions to break a stalemate you can’t outflank — is still the yardstick every WWII RTS since has been measured against, and few have matched how legible it made a single firefight.
A map that fights back
Company of Heroes’s destructible environments deserve more credit than they usually get for how they change the psychology of holding ground. A defensive position in most RTS games is permanent until the defender chooses to abandon it — the wall is the wall for the whole match. Here, an attacker with enough munitions can simply remove the terrain feature a defender is relying on, which means no static defence is ever fully safe and a player who’s dug in still has to keep spending resources on maintaining that position rather than treating it as a solved problem. That single property changes how a match’s pacing works: stalemates don’t grind on indefinitely the way they can in a game where cover is fixed and unlimited, because the side with a munitions advantage always has a lever to break one open. It’s a quieter piece of design than the cover system itself, but it’s the reason Company of Heroes matches rarely settle into the kind of turtling stand-off that plagues RTS games where terrain is immutable.
Spoilers below
The campaign follows Baker’s Able Company from the Normandy landings through the liberation of a fictionalised version of Carentan, and the mission structure front-loads its hardest tactical lesson early: the Carentan causeway assault forces you to cross open, cover-starved ground under sustained machine-gun fire from entrenched positions, and the only viable answer is smoke cover and a flanking push rather than a frontal advance, which teaches the suppression-and-cover system under genuine pressure rather than in a tutorial. Later missions escalate into urban fighting inside the town itself, where destructible walls become the actual objective — breaching from building to building rather than fighting through the street — and the final defence against a German counterattack is built entirely around holding a network of prepared positions rather than advancing at all, which is the mission that best demonstrates how differently this game handles a defensive stand compared to the tower-rush tactics of a more traditional base-building RTS.
If the cover-and-suppression idea is what hooked you, Homeworld is worth the detour to see the same studio’s earlier, stranger answer to persistent losses mattering — just staged across open space instead of a French hedgerow. And for the genre Company of Heroes was quietly arguing against, Dune II is still the clearest look at the base-building template it chose not to discard, only to subordinate to something more tactical.




