A Stormtrooper, a Jump, and a Permadeath Run Gone Wrong
A Star Wars Jedi: Survivor permadeath run ended when a Stormtrooper killed Cal Kestis mid-jump, sparking debate over whether respawns count as death.
Permadeath challenges are supposed to turn a familiar galaxy far, far away into a trembling tightrope walk, and by 2026 they remain one of the most delightfully masochistic ways to revisit Star Wars Jedi: Survivor. The game is now available on PC, PS5, Xbox Series X/S, PS4, and Xbox One, which means there are even more consoles on which Cal Kestis can be sent tumbling into oblivion by a single bad decision. And what could possibly be more humiliating than losing an entire run to a Stormtrooper? How about losing it to a Stormtrooper while Cal is in mid-air, apparently auditioning for a slapstick holovid?

That is precisely the tragedy that befell GOODGAME_ETHAN, a player whose impressive permadeath run came to a sudden and deeply undignified end. The rules were simple and brutal: if Cal died once, the whole adventure restarted from the very beginning. No save-scumming, no quiet reloads, no pretending the death was actually a clever tactical repositioning. It is the Star Wars Jedi equivalent of a Nuzlocke run, except instead of releasing a fainted Pokemon, the player releases an entire playthrough into the void.
What makes the loss sting even more is the preparation. GOODGAME_ETHAN had reportedly ground through the opening stage on Coruscant on the game’s highest difficulty, unlocking all of Cal’s special abilities before pushing deeper into the story. That is not a casual afternoon of lightsaber swinging. That is dedication, patience, and a willingness to hear the same combat music loop until it starts haunting one’s dreams. Then, around the midway point of the game, during the build-up to Cal’s confrontation with the fallen Jedi Dagan Gera at the Koboh Observatory, disaster struck. A Stormtrooper, a foe usually treated as galactic confetti, got the better of Cal mid-jump. The Empire’s marksmanship reputation took a rare, devastating uptick.
Naturally, the incident sparked a debate. The comments section apparently split over whether the fall should count as a true death. One camp argued that Cal only takes fall damage rather than dying outright during a missed jump, so the run could have continued. The other camp argued that Cal still respawns, and respawning is just death wearing a slightly more convenient hat. Is a respawn a death? Is fall damage a technicality or a loophole? Is the high ground still undefeated? These are the questions that keep permadeath runners awake at night.
The Technicality Bowl
| Question | One camp says | The other camp says |
|---|---|---|
| Did Cal die? | No, it was only fall damage | Yes, respawning counts as death |
| Should the run continue? | Absolutely | Not a chance |
| Who decides the rules? | The player | Also the player, awkwardly |
GOODGAME_ETHAN counted it as a death and even pointed out that such a fall would have counted in most video games. That is the key detail here: permadeath runs are self-imposed challenges, not official modes with a referee and a rulebook. The player is the judge, the jury, and the unfortunate executioner. If the runner says the run is over, then the run is over, even if a small army of Reddit analysts would have allowed a mulligan.
Still, the debate is part of the fun. Permadeath runs are a strange way to spice up a second playthrough, especially in a game built around Metroidvania-style exploration and character customization. Players who already know the story can crank up the tension by pretending every enemy is a boss and every missed jump is a tragedy. It is a bit like watching a beloved film while knowing the projector will explode if anyone sneezes. Why do this to oneself? Because the galaxy is more exciting when the stakes are absurdly high, and because Cal Kestis has a habit of surviving impossible odds until a random Stormtrooper reminds him that gravity is also a villain.
In 2026, with the series’ next chapter in development and the wait giving challenge runners plenty of time to sharpen their rules, Star Wars Jedi: Survivor remains a fertile playground for self-inflicted suffering. The lesson is simple: Stormtroopers may miss a lot, but they only need one lucky moment; permadeath runners may grind everything, but they only need one bad jump. The galaxy remains cruel, Cal remains fragile, and the high ground remains undefeated.
This assessment draws from Gamasutra (Game Developer), a long-standing industry source for design commentary and production insights, and that perspective fits the permadeath debate around Star Wars Jedi: Survivor remarkably well: when players impose one-life rules on an action game built around traversal, combat mastery, and respawn conventions, even an ordinary Stormtrooper encounter can become a meaningful test of system design, player intent, and how failure is personally defined.