Ask who invented the real-time strategy genre and you’ll get two different answers depending on which platform’s fans you ask, and both of them have a real claim. Sega Genesis owners will point to Technosoft’s Herzog Zwei from 1989. DOS players will point to Westwood Studios’ Dune II, three years later. The honest answer is that the genre has two separate parents — but only one of them wrote the specific rulebook that Warcraft, Command & Conquer, and StarCraft all later copied, and that rulebook is Dune II’s.
An Adaptation Nobody Expected to Matter This Much
Dune II: The Building of a Dynasty was developed by Westwood Studios (also credited as Westwood Associates) and published by Virgin Games in 1992. It draws its setting from Frank Herbert’s Dune novels and, more directly in tone, from David Lynch’s 1984 film adaptation, casting the player as the leader of one of three Houses — Atreides, Harkonnen, or Ordos — fighting for control of the desert planet Arrakis across a nine-mission campaign. None of that premise suggested a genre-defining release was coming. What made it one was almost entirely mechanical.
It’s also worth separating Dune II from the 1992 adventure game Dune, released by Cryo Interactive the same year and based on the same license — a common point of confusion given how close the release dates are. The two share source material and almost nothing else: Cryo’s Dune is a narrative-driven adventure and resource-trading game, while Westwood’s Dune II abandons most of the novel’s plot in favor of an original conflict between the three Houses, built specifically to carry a real-time strategy structure the license itself never called for.
The Loop Everyone Copied
Dune II’s core loop — build a base, harvest a resource, convert that resource into credits, spend the credits on units, and use those units to grind down an opponent’s base — is close enough to how a modern RTS still plays that the lineage is obvious the moment you load it up. Spice, harvested from the desert by dedicated Harvester vehicles, stands in for the ore or gold of later games. Sandworms patrol the open desert and will devour Harvesters and infantry that linger too long in the wrong spot, adding a hazard layer no earlier strategy game on DOS had attempted.
Each House brings a distinct unit roster on top of the shared systems: Atreides fields the Sonic Tank, Harkonnen the heavily armored Devastator, and Ordos the deceptive Deviator, giving the three campaigns genuinely different tactical identities rather than a single unit list reskinned three times.
Pacing Arrakis: DOSBox Cycle Counts for Dune II
Mount the installation folder (for example mount c C:\DUNE2), switch to the drive with c:, and launch the game’s executable directly. Dune II’s unit pathing and animation speed are noticeably tied to CPU cycle count in DOSBox — if units move or the game clock runs faster than expected, lower the cycles= value in your DOSBox configuration rather than leaving it on a high fixed number; a moderate, fixed cycle count (rather than cycles=max) tends to give the most period-accurate pacing, keeping Harvester routes and sandworm attacks timed the way they played on original hardware.
The Feature That Wasn’t There Yet
It’s worth being upfront about what Dune II doesn’t do, because it shaped everything that followed just as much as what it does do: there is no multi-unit selection. You direct one unit, or one group via repeated single clicks, at a time — a limitation that made large-scale battles genuinely cumbersome to manage. Westwood’s own follow-up, Command & Conquer, addressed this directly in 1995 by adding drag-select multi-unit commands, which is now considered such a baseline RTS feature that it’s easy to forget Dune II’s absence of it was ever the norm rather than an oversight.
Buildings also require Concrete Slabs underneath them to avoid gradual decay, and Carryalls handle unit and vehicle transport across the map — two more systems that later RTS games would either keep in simplified form or quietly drop. None of these constraints read as bugs in hindsight so much as the rough edges of a genre still figuring out its own vocabulary in real time, with Westwood itself sanding most of them down within a few years.
Nine Missions, Three Very Different Wars
The campaign structure itself was unusual for the time: rather than one linear nine-mission story, Dune II effectively runs three separate nine-mission campaigns, one per House, each escalating in difficulty as you advance from Arrakis’s outer regions toward its capital. Choosing a House at the start isn’t just a cosmetic decision — Atreides missions lean on balanced, defensively sound play with the Sonic Tank’s area-effect damage rewarding careful positioning, Harkonnen missions push toward attrition and raw firepower with the Devastator’s self-destruct capability as a late-game trump card, and Ordos missions reward economic aggression and the Deviator’s unusual ability to temporarily convert enemy vehicles to your side. Replaying the campaign with a different House isn’t just more of the same content; the optimal strategy changes meaningfully each time.
The Counter-Argument: Herzog Zwei Got There First
Crediting Dune II as “the first RTS” understates a genuinely earlier game. Technosoft’s Herzog Zwei, released for the Sega Genesis in 1989 (reaching North America and Europe in early 1990), already had a player directly piloting a flying, transforming mech that purchased ground units, airlifted them across the map, and issued them orders — real-time base-and-unit management, three years before Dune II, on a console rather than DOS. It’s been cited as a direct influence not just on Dune II but on the wider lineage that includes Warcraft and StarCraft.
The fairer framing, and the one most genre historians land on, is that Herzog Zwei proved the real-time strategy idea could work at all, while Dune II is the game that turned that idea into a repeatable, codified template — resource harvesting, base building, tech-gated unit production — specifically for the PC. Both claims can be true at once, and the genre owes a debt to each in a different way.
Publishing History: How a Newly Acquired Studio Got Here
The studio behind Dune II had existed since 1985 as Westwood Associates, founded by Louis Castle and Brett Sperry and best known through the late 1980s for role-playing titles like the Eye of the Beholder series rather than anything resembling a strategy game. Virgin Interactive acquired the studio in 1992 and renamed it Westwood Studios the same year Dune II shipped. Virgin’s Dune license, meanwhile, was broad enough to fund a second, unrelated 1992 release — Cryo Interactive’s adventure-strategy hybrid — from an entirely different studio under the same publishing umbrella. Westwood’s real-time strategy take turned out to be the one with the lasting genre influence, while Cryo’s is remembered today as a well-regarded but far less imitated curiosity from the same year and the same license.
Commanding Arrakis: Five Things That Help Early
- Protect your Harvesters before anything else. Losing one to a sandworm or an enemy raid early on will set your economy back further than losing several combat units.
- Build Concrete Slabs under structures as soon as you can afford to. Buildings placed directly on sand decay over time and will eventually collapse.
- Don’t linger in open desert with Harvesters or infantry longer than necessary — sandworms patrol for exactly that kind of exposure.
- Since there’s no drag-select, plan attacks as small, deliberately grouped pushes rather than trying to coordinate a large force through repeated single clicks.
- Learn your House’s unique unit early — the Atreides Sonic Tank, Harkonnen Devastator, and Ordos Deviator all reward different tactics, and playing all three the same way wastes their strongest advantage. New players often find Atreides the most forgiving of the three campaigns to start with, given its balanced, defensively sound design.
Legacy: The Template Outlived the Game
Dune II’s influence on Warcraft is direct enough that early Warcraft is sometimes described, only half-jokingly, as a reskin of Dune II’s systems with orcs and humans instead of desert Houses. Westwood then iterated on its own formula with Command & Conquer, closing the multi-unit-selection gap Dune II had left open, and the resource-harvest-and-build loop it established is still the default grammar of strategy games decades later — right down to the specific rhythm of harvest, build, mass, and attack that StarCraft players a full decade later would have recognized instantly. For where DOS strategy design headed next in Westwood’s own catalog, and for the platform’s other genre-founding releases from the same period, see our history of DOS gaming overview.
You might also like:
