Star Wars Jedi Survivor: The Metroidvania Under the Lightsaber

Strip the lightsaber, the Force powers and the Star Wars branding off Jedi Survivor and what’s left underneath is a metroidvania — a hub world with locked doors that only open once you’ve earned a new traversal ability elsewhere, a map that rewards backtracking with its own kind of dopamine, and a critical path that keeps quietly rerouting itself around your growing toolkit. Respawn Entertainment’s sequel to 2019’s Fallen Order wears its combat and its cinematic set-pieces up front, but the structure doing the real work underneath is a genre with a much older, much less glamorous pedigree.

That’s not a criticism. The metroidvania form exists because it produces a specific, reliable pleasure — the moment you remember a sealed door three areas back and realise you now have exactly the tool to open it — and Jedi Survivor is unusually good at generating that moment on a schedule, wrapping it in Star Wars fan service rather than pixel art.

Five Stances, One Grammar

Combat is built around five distinct lightsaber stances, up from Fallen Order’s more limited toolkit: single blade, dual-wielded blades, the Inquisitor-style double blade, a blaster-and-saber pairing, and a heavier crossguard stance for slow, armour-breaking strikes. Each stance has its own combo timing, its own optimal enemy type, and its own feel in the hand, and the game expects you to swap between them mid-encounter rather than settle on a favourite and coast. A shielded trooper punishes the dual blades but folds to the crossguard’s heavier hits; a fast, evasive duelist rewards the reach of the single blade’s parry window.

What keeps this from becoming a menu-management chore is how directly the stance choice ties back into the metroidvania structure. Certain late-game areas are gated by an enemy type rather than a traversal ability, one that essentially demands a stance you may not have been using, forcing a re-engagement with tools you’d shelved. It’s a subtler form of gating than a locked door, and it’s the sign of a design team thinking about progression in terms of the player’s whole toolkit rather than just their map coverage.

Koboh as a Map, Not a Level

The game’s central hub, the planet Koboh, is where the metroidvania instinct is most visible. It’s built less like a Star Wars set piece and more like a Super Metroid map rendered in three dimensions — a web of interconnected biomes with shortcuts that only open from one side, environmental puzzles that require an ability you don’t yet have on the first pass, and a mount system that turns backtracking itself into a pleasure rather than a chore once traversal speeds up. The desk has written elsewhere about the specific dopamine hit a locked door produces once you’re holding the key that opens it, and Koboh is built almost entirely around manufacturing that moment as often as the pacing allows.

It’s worth comparing this directly to how Dark Souls folds its level design back on itself, because Jedi Survivor is doing a related but distinct trick: FromSoftware’s shortcuts collapse distance within a single, continuous space, while Koboh’s gated paths are explicitly ability-locked in the metroidvania tradition, closer to a Samus Aran power-up gate than a Souls elevator. Both produce the same emotional payoff — the map suddenly making sense as one connected object — by different mechanical means.

The Launch Everyone Remembers

It would be dishonest to review Jedi Survivor without addressing its console launch, which was rough enough to become the dominant conversation around the game for its first several weeks on shelves. Frame-rate instability, stuttering during traversal, and visual pop-in were widely reported by critics and players on PlayStation and Xbox hardware at release, serious enough that the game’s technical state overshadowed its design for a stretch most releases don’t have to survive. Respawn patched steadily in the months that followed, and the game that exists now runs meaningfully better than the one that shipped — but the initial performance problems are part of the public record around this release and worth stating plainly rather than glossing over in service of the design discussion above.

It’s a useful reminder that a metroidvania’s pleasures depend on smooth traversal more than most genres do — the joy of the locked-door-unlocked moment evaporates fast if the frame rate stutters on the way there, and Jedi Survivor’s rockiest weeks were rocky partly because the technical problems undercut the exact thing the level design was built to deliver. Playing it now, well past those early patches, the two halves of the game finally line up the way they were presumably meant to on release: a map worth navigating, rendered smoothly enough that navigating it stays a pleasure rather than a fight with the hardware.

The Force Powers as Second Set of Keys

Alongside the stances, Jedi Survivor runs a parallel progression track of Force abilities — push, pull, slow, and a handful of new powers unique to this entry — that function as the game’s other set of metroidvania keys. Where the stances gate encounters, the Force tree gates traversal and puzzle-solving: a wall you can slow down to cross safely, a gate that only pull can open, a platforming sequence that becomes trivial once you’ve unlocked a mid-air dash. This is the more traditional half of the genre’s toolkit, closer to Samus Aran’s morph ball or ice beam than to anything combat-shaped, and the game is careful to keep the two tracks legible as separate systems even as they occasionally combine — a Force-slowed enemy is easier to read for a stance swap, for instance, letting the two progression trees reinforce each other rather than sit in separate lanes.

The skill tree wrapped around both systems is generous rather than stingy, which matters for a genre that lives or dies on whether unlocking new tools feels inevitable or grindy. Jedi Survivor leans toward inevitability — you’re rarely more than an hour from the next meaningful unlock, and the game paces its ability drops against its map expansions closely enough that you’re seldom left backtracking through content you’ve already fully solved. That pacing discipline is easy to take for granted until you compare it to genre entries that front-load their toolkit and spend the back half of the game repeating the same handful of tricks.

Boss Encounters as Stance Exams

The game’s boss roster deserves particular credit for functioning as a kind of practical exam for everything the stance system has taught by that point. Rather than introducing a single new gimmick per boss in the modern action-game tradition, Jedi Survivor’s toughest fights tend to demand fluent stance-switching under pressure — reading which attack pattern calls for the crossguard’s block-breaking weight against which calls for the single blade’s faster parry window, often within the same encounter as a boss cycles through phases. It’s a design approach that rewards players who’ve actually explored the full stance kit across the open world rather than those who found one combination that worked early and stuck with it, and it retroactively justifies some of the game’s more demanding side-encounters as practice rather than padding.

This is where the metroidvania structure and the combat system genuinely reinforce each other rather than sitting side by side. A pure action game can get away with teaching only the skills its bosses test; Jedi Survivor’s world design means the skills get tested continuously, in side content, well before the story-critical boss fights arrive to grade the work.

Spoilers below

The story picks up several years after Fallen Order, with Cal Kestis and his found-family crew — Cere, Greez, Merrin and the droid BD-1 — deeper into the Empire’s tightening grip and increasingly isolated as safe havens close around them. A new ally introduced early in the campaign turns out to be operating a hidden allegiance that complicates the crew’s trust in each other for the back half of the game, a betrayal that lands with more weight than Fallen Order’s plotting generally allowed for. The campaign closes with Cal’s found family intact but scattered, setting up stakes that feel more personal than galactic — appropriate for a series more interested in one Jedi’s survival than in the war around him.

What the Setting Adds

The Star Wars dressing itself contributes real design value here rather than functioning as pure branding. Koboh and the game’s other planets draw on decades of established galactic iconography — abandoned Jedi temples, Imperial garrisons, junk-trader settlements — and the metroidvania structure gets to lean on that existing visual vocabulary to communicate progression shorthand a genre entry starting from scratch would have to build from nothing. A rusted-shut Imperial blast door reads as “come back later” instantly, in a way an abstract locked gate in a lower-budget indie metroidvania sometimes has to work harder to convey. The licence isn’t incidental to why the structure works as well as it does; it’s doing legitimate legibility work.

That said, the game is careful not to let the fan service crowd out the exploration incentives. Force-echo vision sequences — flashes of the past tied to specific locations — reward exploring the map’s quieter corners with lore rather than just loot, giving Koboh’s world-building a reason to exist beyond gating mechanical unlocks. It’s a smart use of a licensed universe’s depth: rather than treating Star Wars trivia as pure decoration, Respawn ties it to the same exploration loop that’s already doing the game’s heaviest lifting.

Jedi Survivor rewards patience with its map more than its lightsaber, and that’s the more interesting achievement of the two. If the locked-door structure is what you came for, the metroidvania canon has the genre’s purer examples; if it’s specifically the marriage of that structure to a licensed action game, Prince of Persia: The Lost Crown makes a comparable case from the opposite direction, a beloved franchise finding new life inside the genre’s old bones.