Homeworld: the RTS that went fully three-dimensional

Relic Entertainment’s Homeworld shipped in September 1999 and solved a problem almost nobody else in the RTS genre had seriously attempted: what does real-time strategy look like when the battlefield has no floor? Every RTS before it, going back to Dune II and through Command & Conquer and Warcraft, had assumed a flat plane you looked down on from above. Homeworld put its fleets in open space with full six-degrees-of-freedom movement, no up or down privileged over any other direction, and then had to solve an interface problem nobody in the genre had faced: how do you select, move, and understand the relative position of ships when the camera itself is floating in the same featureless void they are.

The answer Relic landed on was a horizontal reference plane you could project any selected group onto, plus a set of camera and movement-plane tools that let you constrain an order to a flat layer of that 3D space when you needed the precision of a traditional top-down RTS and free yourself from it when you needed to bring a bomber wing up and over a defending screen. It’s a genuinely clever piece of interface design solving a problem that a lot of “3D” strategy games since have quietly ducked by keeping combat functionally two-dimensional with decorative verticality. Homeworld’s verticality wasn’t decorative. Fighter squadrons could dive from above a capital ship’s weakest firing arc; a fleet caught in a pincer had to be pinched from genuinely different angles in three-dimensional space, not just flanked left and right on a flat map.

The fleet that remembers what it lost

The mechanic that made Homeworld’s campaign land emotionally rather than just technically is persistence: your fleet in mission one is the same fleet, ship for ship and veteran crew for veteran crew, that you carry into the final mission. Capture an enemy vessel and it’s yours from then on. Lose a strike craft and it’s gone, permanently, with no respawn between missions to paper over the cost. That single design choice — carrying losses forward rather than resetting the roster at each mission’s start, the way most RTS campaigns of the era did — turned every tactical decision into something with weight beyond the immediate skirmish. Sending an under-escorted resource collector out to grab a nearby asteroid field wasn’t just a risk to that mission’s economy; it was a risk to a fleet you’d need intact three missions later.

The story wrapping that mechanic is a slow-burn refugee narrative: the Kushan people, exiled on a desert homeworld for millennia, discover an ancient stone tablet revealing they are not native to that planet, build the ark-ship Mothership described in that same tablet’s instructions, and set out across hostile space to find their actual homeworld, pursued by an empire determined to stop them. It’s a straightforward premise dressed in unusually mournful, understated presentation — long, near-silent stretches of drifting derelicts and empty starfields, scored with a soundtrack that leans on licensed orchestral and choral pieces alongside Paul Ruskay’s original score rather than the bombastic stings a lot of the genre reached for. The tone matches the mechanic: this is a fleet that is genuinely, permanently thinning as it crosses the galaxy, and the game wants you to feel every ship it costs you.

Why the ancestor trace runs through this studio twice

Relic’s next major release after Homeworld’s sequel was Warhammer 40,000: Dawn of War, and the studio’s biggest hit after that was Company of Heroes — and the throughline across all three is the same underlying conviction: a unit’s history should matter more than its stat block. Homeworld’s veteran capital ships and irreplaceable strike craft are the same idea Company of Heroes would later apply to a rifle squad that’s been fighting since the Normandy landings, just staged across open space instead of a hedgerow. It’s rare to be able to point at one studio’s output across a decade and trace a single design conviction mutating to fit two completely different settings, but Relic’s catalogue makes the case cleanly.

The economy that makes persistence cost something

Homeworld’s resource loop is deliberately spare compared to a land-based RTS: Resource Collectors harvest raw floating debris fields or asteroid clusters and ferry it back to a Resource Controller or the Mothership itself for processing into Resource Units, the single currency funding every ship built. There’s no separate tech-tree resource, no second currency to juggle — just one number, contested by sending unescorted collectors into space that may or may not be safe. That simplicity is what makes the persistence mechanic bite as hard as it does: because there’s only one economic lever, a lost collector or a raided resourcing operation has an immediate, uncomplicated cost, and because ships carry forward between missions, an economic setback in mission four is still being felt in mission nine. A land-based RTS can usually out-produce a bad early skirmish within the same match. Homeworld’s campaign structure means a costly mistake can shadow a fleet for the rest of the game.

Multiplayer skirmishes stripped away the persistence layer by necessity — matches are self-contained, starting fresh each time — but kept the resourcing tension and the full 3D movement model, and the competitive scene that grew up around Homeworld and its 2003 sequel valued exactly the skills the campaign had been quietly training: reading the vertical axis of an engagement, escorting collectors properly, and using a captured or salvaged ship as a genuine strategic asset rather than a novelty. It never reached the scale of StarCraft’s competitive following, partly because the interface demands more of a new player than a flat-map RTS does, but it built a dedicated following that the 2015 remaster’s continued online support was clearly built to serve.

The parts that show their age

Homeworld’s pathing and formation-keeping haven’t aged gracefully — large fleets in the original release could tangle into each other in ways that look more like a bug than an emergent tactic, and the interface, while groundbreaking for 1999, asks a lot of a modern player used to more forgiving camera controls. The 2015 Homeworld Remastered Collection, produced by Gearbox with the original team’s involvement, addressed most of the worst interface friction and rebuilt the visuals at a scale the original hardware couldn’t have rendered, and it’s the version worth playing now rather than the 1999 original. A prequel, Homeworld: Deserts of Kharak, moved the series to ground combat in 2016, and a further mainline entry has been announced and was in development as of this piece, though nothing about its eventual release changes the case for the original: it remains the moment the genre proved space combat could be simulated in genuine three dimensions rather than staged on a flat map with a starfield painted behind it.

The sound design doing half the emotional work

A lot of what makes Homeworld’s tone land is easy to miss if you’re focused purely on the tactical layer: the game pairs original orchestral and choral compositions from Paul Ruskay with a handful of licensed pieces, including tracks adapted from Barclay James Harvest and Yes, deployed sparingly enough that a swelling piece of music during a hyperspace jump or a fleet reunion after a costly battle registers as a genuine event rather than wallpaper. Combat itself is comparatively hushed — there’s none of the constant explosive scoring a lot of the genre reaches for, and long stretches of a mission can pass with only ambient hums and distant ship chatter, which makes the score’s entrances land harder when they come. That restraint matches the persistence mechanic’s emotional logic: a game about a fleet slowly, permanently thinning across a long journey earns more from silence and a well-placed swell than it would from continuous bombast.

Spoilers below

The tablet the Kushan uncover in the opening act reveals they are descendants of a species called the Taiidan, exiled to the desert world of Kharak generations earlier as punishment for a rebellion, and the game’s mid-campaign turn comes when the current Taiidan Empire, upon detecting the Kushan fleet’s approach, responds with the near-total destruction of Kharak itself instead of any negotiation, wiping out the homeworld the Kushan just left and making the fleet you’re commanding the entire surviving population of its species. That single event is the moment the persistence mechanic stops being a gameplay convenience and becomes the actual stakes of the story: every ship lost from that point on is a fraction of everyone who’s left, well beyond a mere tactical setback. The campaign’s final confrontation, at Hiigara — the true, ancient Kushan homeworld the tablet was leading them toward all along — plays out as a fleet battle against the Taiidan home defence force, and winning it restores a people to a world none of them have ever actually seen.

The interface problem Homeworld solved is also worth dwelling on for what it reveals about why so few strategy games since have attempted true 3D combat at all. Selecting a formation floating above and behind another in open space, then issuing an order that needs to account for both groups’ relative altitude, is a genuinely harder input problem than clicking a unit on a flat plane, and most of the genre’s few other attempts at 3D space RTS design have either quietly flattened combat back onto an effective 2D plane with cosmetic verticality, or given up on precise multi-axis control in favour of simplified auto-engagement. Homeworld’s willingness to make the player do the harder work — learn the movement-plane tool, learn to read a tactical situation from an unfamiliar camera angle — is exactly why it’s remembered as a landmark rather than as one entry in a crowded subgenre; there was barely a subgenre to be crowded, because almost nobody else was willing to solve the same interface problem the hard way.

If the persistence-and-loss idea is what stuck with you, Company of Heroes is the clearest look at the same studio applying it to squad-level ground combat instead of capital ships; and for the genre template Homeworld took its camera and economy assumptions from before discarding the flat map entirely, Dune II is still the place to see where the RTS’s basic vocabulary came from.