Medieval II: Total War

Medieval II: Total War arrived in November 2006 as something the series hadn’t produced before and hasn’t quite managed since: a game where everything worked at the same time. Creative Assembly had been refining the Total War formula across four entries by that point, each one expanding scope and adding layers. Medieval II was where those layers finally cohered.

The campaign covered Europe, North Africa, and the Middle East across roughly 450 years of medieval history. Seventeen factions, each with distinct unit rosters, starting positions, and strategic problems. England had strong longbowmen and decent cavalry but was hemmed in geographically. The Mongols arrived mid-campaign as a base game invasion event – a cavalry-heavy force that didn’t play by the same rules as everyone else and wasn’t supposed to. The Timurids followed later with war elephants. These weren’t optional challenges; they hit whether you were ready or not, and they forced you to adapt rather than grind out a comfortable win condition. The campaign had a pulse in a way that purely sandbox strategy games often don’t.

The papal system gave Catholic factions a shared political framework that complicated expansion in ways Rome: Total War’s SPQR senate mechanic had hinted at but never fully realised. Where Rome’s senate issued missions and could ultimately turn against you if you grew too powerful, Medieval II’s Pope operated across the entire Catholic world simultaneously. He could call Crusades, demand ceasefires, and excommunicate rulers who ignored him too many times. Excommunication wasn’t a minor inconvenience – it made you a legitimate target for every Catholic neighbour simultaneously. Managing your relationship with Rome while pursuing your own strategic agenda produced some of the more interesting diplomatic situations the series has generated. Non-Catholic factions operated outside that system entirely, which made playing as an Islamic or Orthodox power feel structurally different rather than just aesthetically different.

The city and castle split was one of the more underappreciated decisions in the game’s design. Settlements could be developed as cities, which generated wealth and trade but produced weaker troops, or as castles, which trained better armies but contributed less economically. The choice compounded over time. A kingdom that prioritised military capacity early often found itself cash-poor in the mid-game. One that built commercial infrastructure struggled to field armies capable of holding what it had taken. Neither path was obviously correct, which is what made it interesting.

Battles were what they had always been in Total War – large, visceral, decided by unit positioning, terrain, and morale as much as numbers – but the production scale had jumped. Edge called it “as complete a depiction of war as there has been in a videogame.” That’s a strong claim and not an unfair one for 2006. Cavalry charges scattered infantry lines. Siege escalades required breaching multiple fortification layers before the defenders broke. The AI had pathfinding problems and occasional lapses in tactical logic that reviewers noted at launch, though none of it was severe enough to undermine the battles. Naval combat remained auto-resolved, which was a limitation the series wouldn’t address until Empire: Total War in 2009.

Critical reception was strong across the board. The game reviewed in the mid-80s on Metacritic, charted in the UK through November and in the US into January 2007. It didn’t outsell Rome: Total War, which remained Creative Assembly’s commercial benchmark at that point, but it was a clear hit. Empire: Total War eventually doubled those sales figures, though it shipped with more significant problems. Medieval II’s launch was comparatively clean.

The modding community extended its life well beyond what the base game could have sustained on its own. Creative Assembly’s engine at that point was open enough to permit extensive modification, and Medieval II turned out to be the last Total War game where that was true – later titles moved to proprietary engines with far less mod support. Third Age: Total War rebuilt the game inside the Lord of the Rings setting with enough fidelity that it attracted players who had no prior interest in medieval history. Stainless Steel reworked the AI and expanded the faction roster. Europa Barbarorum II spent years in development and produced something closer to a different game than a modification. Steam still shows 92% positive reviews from the past 30 days on nearly 35,000 total reviews. That’s nearly two decades of sustained engagement.

Creative Assembly announced Total War: Medieval III in December 2025, built on a new engine called Warcore. Whatever that game turns out to be, it has a specific problem: the community that has kept Medieval II running for nineteen years has a clear benchmark, and it isn’t a low one.