Warcraft II Tides of Darkness Review The RTS That Made Blizzard A Household Name Before StarCraft Existed

Right, let me tell you something about Warcraft II that people have totally got backwards. Everyone bangs on about how StarCraft revolutionised real-time strategy and made Blizzard famous. Rubbish. It was Warcraft II: Tides of Darkness that actually did the dirty work, and I will die on this hill because I spent hundreds of hours with both of them on the original hardware.

Not nostalgia by the way. I still have the CDs, I’ve run it on the right hardware, and I’ve experienced the horror of dial-up multiplayer, the bane of PC gaming in the mid-90s. When Warcraft II launched on 9 December 1995 (ComicBook), it perfected the genre like the original had seeded it and the numbers back this up. Selling 1.2 million copies worldwide by November 1996 (Wikipedia), it eventually reported sales of over 2 million copies (GamesBeat). Dime a dozen for a PC exclusive in the mid-90s.

And here’s the thing that matters. Warcraft II perfected the RTS that Command & Conquer had begun and StarCraft would build on. Had the game not shown that complex strategic games could make it to mainstream audiences, there’d be no StarCraft, no Age of Empires boom, nothing. This was the one that established Blizzard as a major player, not some cult developer cobbling together niche fantasy games.

The Combat System That Actually Made RTS Strategy Matter

Look, the original Warcraft was basically just a fantasy reskin of Dune II. Same basic unit types, same resource gathering, same click-and-wait combat. Warcraft II threw all that out and built something genuinely strategic from the ground up.

The key innovation was unit diversity that actually mattered tactically. You had your basic footsoldiers, sure, but then you had proper naval units, flying units, and siege weapons that all interacted in meaningful ways. The Destroyer could hit submarines but couldn’t touch flying units. Dragons could demolish ground forces but were vulnerable to archers. Catapults could level buildings but needed protection from cavalry charges.

This wasn’t rock-paper-scissors for the sake of it. Each unit type filled a genuine tactical niche, and the campaign missions were designed to teach you these interactions progressively. Early missions focused on basic army composition. Later ones threw in naval operations where you needed to coordinate land and sea forces. The final missions required mastery of combined arms tactics that felt genuinely military rather than just “build the biggest army and attack.”

What really impressed me was how the AI responded to different approaches. Attack with just ground forces and it would focus on anti-infantry units. Bring in flying units and suddenly it’s building more archers and towers. Their adaptation was clever, but not infallible, there was a way to punish mindless tactics.

If there’s one thing I’ve come to enjoy after years of playing it, it’s a good magic system. The magic system added an interesting addition, but didn’t go overboard with it. Mages had spells like Polymorph for crowd control and Fireball to crack tough units or siege things open, but they’re a drain enough to be costly to spam your opponent with casters. Death Knights hit the table with necromancy and area denial, a flavour of damage that isn’t just a stronger colour of “Now You’re Dead”. It’s a damn force multiplier that changes the whole game of how you engage.

Unit veterancy meant that keeping your veteran force became an important strategic layer because a Veteran Knight wasn’t just more of a health bar, he was exponentially better in combat. This encouraged more careful planned tactical play instead of hyper-spamming new units forever.

The Three Dimensional Battlefield Revolution

Here’s a thing that nobody talks enough about: Warcraft II was one of the first RTS games to do terrain really matter in a strategic sense. Not just “this bit slows you down” or “there’s no walking through those mountains”, we’re actually talking tactics.

Naval combat hadn’t just been land combat on water. Ships moved differently, had different ranges, different tactical roles. Destroyers hunt subs, man, but no good way to actually deal with coastal fortifications. Battleships can bombard shore but are vulnerable to coordinated naval attacks and transports need escort and careful positioning.

The air units created a proper three dimensional battlefield before anybody was using that phrase years down the line. Dragons weren’t just winged cavaliers serving the same role. They had their own distinct movement patterns, could attack ground and air targets differently, and needed proper countering. Gryphon Riders fulfilled a different niche as fast, fragile boomers.

What made this work was that missions actually demanded combined arms thinking. You couldn’t just invest erroneously in a vast navy and ignore land forces. You were required to think ahead for coastal campaigns where ships provided fire support, ground forces had to secure beachheads, and air units provided reconnaissance and mobility. This was deep enough to be satisfying but not so complex that it became micromanagement hell.

The siege mechanics were the most clever of all. Catapults and ballista had to be painstakingly positioned, protected from cavalry charges, and flanked by infantry. Your buildings could get crushed ironically without seeing them explode from clicks. Siege only worked here through tactical positioning, pushing protect and timing.

Audio Design That Set The Standard

Right, here’s something rather neglected completely in RTS discussions: Warcraft II had exceptional audio design of its own that contributed massively to the strategy. I’m not talking about the soundtrack, that was solid enough. I mean the actual gameplay audio that provided tactical information.

Every unit move made identifiable sounds that were consumable if not looking. Footmen marched differently than Knights, having a different cadence. Ships could be recognised by their engine sounds too. Flying units had wing beats easily recognisable well enough to use in-play. This was not just flavour, practically battlefield awareness itself. You could hear mostly nothing, or enemy reinforcements approaching, and even know what was properly. The voice acting was characterised rather truly rather than generic quality and barks binding too. The Orcish units sounded genuinely different than Human units, not just in accent but in attitude. The unit acknowledgements had personality, making your forces feel like actual armies rather than game pieces.

Combat audio provided clear feedback about whether you were engaging effectively. When you hit a unit, weapon impacts sounded differently enough that you knew whether your attacks were actually connecting, whether damage was being absorbed by armour if you were attacking an armoured unit, how much damage your magic was doing, et cetera. And the way the audio was mixed kept the chaos of large battles at least intelligible rather than white noise.

Environmental audio gave you even more information about the tactical picture. You could hear when buildings were being constructed, and when units were on a resource-gathering mission. Same with siege weapons being readied. This information helped in reconnaissance and timing for attacks, and the spatial audio positioning worked well enough that you could largely deduce where something was happening off-screen just by hearing it.

The Map Editor That Changed PC Gaming Forever

The part that’s really the template for the way modern gaming communities work: included with Warcraft II was a proper map editor (Criticker) user-friendly enough for the average player, and sophisticated enough that players would go on to virtuously evil their lives away.

Much more than a simple scenario-building tool, this made custom campaigns possible, with actual unique victory conditions, a scripting language worth a damn, and a means of exchanging information via that newfangled thing called the internet. The editor was intuitive to the point that you didn’t need programming background, but powerful enough that creative players ended up producing genuinely innovative new scenarios. Tower defence, hero defence, cooperative survival scenarios, every modern multiplayer format was being experimented with in Warcraft II custom maps years before they became stocks. What made this work was that Blizzard actually supported the modding community rather than just tolerating it. The editor came with documentation, example maps, guidelines for sharing content. This wasn’t an afterthought, or a debug tool left meanly in by mistake, but rather a deliberate platform for community creativity. The technical implementation was solid enough that custom maps hardly ever had significant bugs or compatibility issues. Maps created in the original release still worked properly years later with expansion packs, plus patches. This reliability was important for developing a sustainable modding community.

Multiplayer That Defined Online Gaming

Okay, perhaps here’s where Warcraft II truly proved its importance to gaming history. Now we get to multiplayer as the “killer app” of online gaming. Make no mistake, two-player over a modem was always sorta too much like work. No, here we’re talking eight-player matches over modem or early internet connections that actually worked consistently, even if the network code was remarkably stable for 1995 tech. Rarely dropping because of connection problems rather than technical difficulties, the game handled lag and synchronisation better than many modern titles manage with dedicated servers, and this reliability was essential for building the competitive community that would end up moving to StarCraft. Game balance was tight enough that all strategies remained viable at high enough levels of play, whilst naval maps required different approaches than land maps. Resource rich scenarios made different demands than simply surviving in a limited resource hedge and the faction balance between Humans and Orcs was tight enough that preference came down to playstyle rather than objective advantage.

The lobby and matchmaking systems were primitive even by the standards of the time but were revolutionary at the time. You could browse available games, cheque ping times, filter by which map type was played and how many players were involved. This was the primitive backbone of everything that would later become Battle.net and it was used as effectively as possible to bolster a very lively competitive scene.

Why It Matters

What’s great about Warcraft II is that it’s still completely playable today without any allowances for nostalgia in viewing it. The core gameplay holds up because the strategic systems are actually deep enough that “complex” is something they actually model for the player rather than just complexity for the sake of it. The average time to finish a campaign is about forty hours (GameFAQs Q and A), which is a decent enough time for mastery rather than just blitzing through the game.

It has campaign design that whilst simple in concept, teaches strategy that’s still applicable in the genre. All the things you expect from RTS that modern RTS games presume you already know, resources, combine arms tactics, technology, defences, it’s all taught through missions in Warcraft II that are still challenging today. The fantasy setting has aged far better than the sci fi RTS. Orcs versus Humans doesn’t rely on technology that looks cheesy now or pop culture that doesn’t resonate anymore. The unit designs are clear and functional instead of being gimmicky. Everything is still immediately readable and tactically relevant.

I’m most impressed by the interface design. Unit selection, building queues, resource displays, all of this still makes intuitive sense. RTS games still try to add complexity but without improving the expressed function. Warcraft II measured exactly how much information to present before confusing players, and no one has improved that balance, only copied it.

Critics recognised it too, which is why it has a Metacritic metascore of 95 and appears on plenty of Greatest Games lists, like at Polygon. Professional reviewers keep archived expert coverage on the game, which tells you everything you need to know about the power level of this game.

The Sales That Built Strategy Gaming

So as my last arguments for why Warcraft II deserves its place in gaming history as the RTS that actually mattered the most, let’s talk sales figures. US sales of 835,680 copies in 1996 alone tracked via PC Data (GameFAQs). That’s huge, and that’s for a PC exclusive title that pushed the limit of what a high-end system was. Remember how relatively high-end your PC needed to run this. This was not a niche title for hardcore strategy enthusiasts. This kind of sales number indicates it was a mainstream game that just happened to by some miracle be great.

We are still seeing games that use the template Warcraft II rolled out, and developers are still testing new innovations and releasing them in blender-full-scale chunks. Multiple victory conditions, combined arms, asymmetric faction design, integrated naval and air combat, sophisticated “borrows” from enemies and adapts-cheating-AI. These aren’t drops of knowledge gained from slow years of development. These are concentrated design successes that happen in a single release.

David

David runs a pub in Bristol and has transformed his back room into a functional shrine to arcade cabinets and early home systems. By night he writes about arcade culture, MAME emulation ethics, and why certain games simply feel different on original hardware versus emulation. He brings a perspective that matters: he owns these machines, maintains them, and plays them regularly, rather than just holding memories of them. His technical knowledge of arcade hardware is matched only by his ability to explain why authenticity genuinely matters to the experience.