Before StarCraft was a household name, and long before World of Warcraft turned Azeroth into a place millions of people call a second home, there was Warcraft II. The 1995 sequel took a decent first attempt at real-time strategy and turned it into a genre-defining hit. If you want to understand why Blizzard’s name still means something thirty years later, this is one of the places to start.
From a Solid Debut to a Genuine Phenomenon
Warcraft: Orcs & Humans, released in 1994, proved Blizzard could build a functional RTS, but it was rough around the edges next to the competition. Warcraft II: Tides of Darkness, released the following year, is the game that fixed nearly everything: sharper unit balance, a much bigger roster, and production values that made the 1994 original look like a rough draft. It expanded the war between the Human Alliance and the Orcish Horde onto the water and into the air, adding naval combat and flying units to a conflict that had previously been fought entirely on land, and the added scale gave every mission a sense of escalation the first game never quite achieved. It sold extremely well and is remembered today as one of the handful of games, alongside Command & Conquer, that turned real-time strategy from a niche experiment into one of the biggest genres in PC gaming.
Gold, Lumber, Oil: What Actually Changed
The core loop is the one you’d expect if you’ve played any RTS since: gather resources, build a base, train an army, break your opponent’s base before they break yours. What’s worth calling out is how much Warcraft II added on top of that template. Naval combat brought oil into the resource mix alongside gold and lumber, meaning you now had to manage a third supply chain to keep transports, destroyers, and battleships in the fight. In the air, Alliance gryphon riders and Horde dragons opened up a vertical dimension the original Warcraft never touched. The spellcaster roster grew too, with mages and paladins for the Alliance and ogre-mages and death knights for the Horde, giving both sides tools well beyond basic unit-versus-unit combat. None of this reinvents the genre Dune II started, but the execution is tight enough that the formula still feels satisfying to play today.
Mistakes New Commanders Make
- Neglecting your economy early. It’s tempting to rush straight into military production, but skimping on peasants or peons and lumber gathering in the first few minutes leaves you unable to sustain an army once the fighting starts.
- Forgetting oil entirely until you need a navy. Oil platforms take time to establish, and missions with a coastal component will punish you if you wait until enemy ships are already at your shore before you start building your own.
- Ignoring upgrades at the blacksmith. Weapon and armor upgrades apply to your whole army retroactively, and skipping them means your units fall behind even if you’re producing plenty of them.
- Letting food production lag. Farms and pig farms cap your population, and running out of food supply mid-battle because you forgot to build more is a completely avoidable way to lose momentum.
How It Stacks Up Against Command & Conquer and Dune II
Warcraft II arrived in a genre that Dune II had essentially invented a few years earlier and that Command & Conquer, released the same year, was busy redefining. Dune II set the template Warcraft II still follows: gather resources, build, produce, attack, but did it with a single resource and a much smaller unit roster. Command & Conquer leaned into a faster, more streamlined pace and a stronger emphasis on narrative through its FMV briefings. Warcraft II splits the difference. It’s slower and more methodical than Command & Conquer, but considerably deeper and more varied than Dune II, with a fantasy setting that gave it a very different identity from either of its closest rivals. Which one you prefer often just comes down to whether you want fantasy or science fiction, and whether you want your strategy game to feel like a puzzle or a race.
From Azeroth to Azeroth: Warcraft II’s Long Shadow
The line from Warcraft II to StarCraft is direct. Blizzard took the lessons it learned balancing two asymmetric factions here and applied them to three wildly different ones a couple of years later. And the setting itself obviously didn’t stop mattering after this game; Azeroth went on to anchor Warcraft III and, eventually, an MMO that needs no introduction. It’s a strange thing to load up a 1995 RTS and recognize the DNA of a game that would go on to define online gaming for a generation, but that’s exactly the experience Warcraft II offers.
Getting the Battle Running in DOSBox
Once you’ve got the game files somewhere accessible, mounting them in DOSBox follows the same process as any other title: mount the folder as a drive, switch to it, and launch the executable. Where Warcraft II gets a little particular is cycle count. As a fairly demanding mid-90s RTS with a lot of units and sound effects on screen at once, it benefits from cycles set high enough to avoid slowdown during big battles, and getting Sound Blaster configured correctly matters more here than in slower-paced games, since unit voice lines are a big part of the experience. If none of that means much to you yet, walk through our DOSBox setup guide first, get sound and cycles sorted, and come back once you’re configured.
Watch Gameplay
You might also like:
