Guest feature by Søren Ahrensborg Kamper
Zero Company makes permanent loss explicit, but some of the most memorable Star Wars games have always understood the same thing: a galaxy feels more personal when defeat leaves something behind.
Star Wars has always been very good at loss. Hands disappear. Mentors die. Planets vanish. Han Solo spends a surprisingly long time as expensive wall decoration. The films understand that adventure becomes meaningful when something cannot simply be put back exactly as it was.
Games have a harder relationship with that idea. They are built around failure, but they are also built around trying again. Miss the jump, reload. Lose the fight, reload. Pick the dialogue option that makes everyone furious, stare at the screen for three seconds, then quietly reload before anyone notices. Darth Vader may be terrifying, but he has never truly defeated the quick-load button.
That is why Star Wars games become especially interesting when failure survives the loading screen. Across more than four decades of Star Wars games, the best examples are not necessarily the hardest. They are the ones that let a mistake, defeat or bad decision stay true long enough to reshape what comes next.
Zero Company Makes Loss Part of the Story
The important thing about Zero Company’s permadeath system is that it is not simply an on/off difficulty toggle. An Operator who is downed takes an Injury, and with permadeath enabled, a third Injury means that character is Killed in Action and removed from the squad permanently. Hawks is the exception: losing the commander fails the mission instead.
Since the 15 October 2026 update, new campaigns can choose additional Injury and death rules. The three-Injury limit remains the default.
That sounds mechanical when written in a guide. In a campaign, it changes the emotional arithmetic of every move. The sniper on two Injuries is no longer merely a collection of statistics. Moving them into an exposed position means risking a person the squad has already invested time, equipment and relationships in. A rescue becomes more than recovering combat power. It is an attempt to keep part of your campaign’s history alive.
Beskar Mode pushes the idea further by limiting the campaign to a single save and removing manual saving. The distinction matters. Permadeath threatens the roster; Beskar Mode threatens the player’s ability to negotiate with the past. You cannot keep reopening yesterday until it becomes the version you prefer.
StarWars.com explicitly recommends trying permadeath because losing key Operators adds emotional weight to the story. That is unusually candid design language for a licensed game. The system is not pretending death is fun. It is arguing that absence can be meaningful.
Battlefront II Let Defeat Stay on the Map
The modern Battlefront games are remembered for huge multiplayer battles, spectacle and atmosphere, but the 2005 Battlefront II understood consequence in a much smaller, almost board-game-like way.
Its Galactic Conquest mode starts the player with planets, a fleet and credits, then asks them to fight for control of the galaxy one battle at a time. Credits can be spent on new unit classes, bonuses and fleets. If a fleet is defeated, it is lost. If every base and fleet is gone, the campaign ends.
That is not permadeath in the XCOM sense, but it gives defeat a physical address.
Lose a space battle and the galaxy map looks different afterwards. The fleet you expected to use for the next attack is no longer there. Rebuilding costs money. A route that looked safe a turn ago may suddenly be exposed. One bad battle creates another problem instead of politely disappearing once the results screen fades.
It is a wonderfully simple trick. Galactic Conquest does not need a branching script to tell you that the war has changed. It just leaves the hole on the map and lets you notice it yourself.
Empire at War Understood the Value of Retreat
Star Wars: Empire at War took that persistence much further. Its own manual describes the strategy layer as persistent: decisions on the Galactic Map and the results of previous battles continue to affect the galaxy. Fleets, armies, planets, production and routes all exist in a strategic layer that remembers what happened.
The clever part is that loss is not limited to total defeat. Empire at War lets you retreat.
That single option gives consequence texture. If a battle turns ugly, the question is no longer simply whether you can win. It becomes whether the remaining ships are worth saving, whether the planet can be sacrificed, and whether retreating now will prevent a larger disaster two turns later.
A Star Destroyer lost in a battle is not just an explosion. It is production time, credits and military pressure that will be missing somewhere else. A planet taken by the enemy can change income and movement across the map. The campaign does not need to shout “THIS MATTERS” in enormous letters. The next problem arrives and proves it for you.
This is an important distinction when talking about permanence. A consequence does not have to last until the credits. It only has to remain true long enough to force a new plan.
KOTOR Made the Party Screen Remember Your Decisions
Knights of the Old Republic, one of the defining Star Wars RPGs of the original Xbox era, handles permanence very differently. Its consequences are narrative rather than strategic, and some of them are hiding inside what initially looks like a normal dialogue choice.
Minor spoilers for Knights of the Old Republic follow.
Several party members can be permanently lost depending on what the player decides. Juhani can die instead of joining the party. Later dark-side decisions can remove other companions entirely. Those outcomes are not temporary debuffs or angry conversations that reset after the next quest. The person can simply be gone from the rest of that playthrough.
Yes, KOTOR allows multiple saves. A player can always reload if regret arrives quickly enough. But that does not make the design meaningless. The important part is what happens when the player accepts the decision.
The empty place in the party becomes evidence.
That is one reason companions in KOTOR feel more substantial than a menu of interchangeable abilities. They are useful in combat, certainly, but they are also characters whose continued presence can depend on what kind of person the player chooses to become. The party screen becomes a small archaeological site of your decisions.
For a Star Wars game, that is especially effective. The franchise is full of moral declarations about choice, loyalty and the temptation of the dark side. KOTOR occasionally has the nerve to make those ideas inconvenient.
Outlaws Shows That Consequences Do Not Have to Be Permanent
Star Wars Outlaws offers a useful counterexample. Its syndicate reputation system is built around an ever-changing relationship with groups such as the Pykes, Crimson Dawn, the Hutts and the Ashiga Clan. Betray the wrong people and access, jobs and safety can change. Work for them again and the relationship can recover.
Nothing about that system needs to be permanent to matter.
In fact, the ability to repair a damaged reputation is part of the fantasy. Kay Vess is a scoundrel, not a commander writing names on a memorial wall. Burning a bridge and then finding an expensive, slightly embarrassing way to rebuild it fits the character better than an ironman rule ever would.
What matters is that the galaxy remembers for a while.
A decision follows you into the next district, the next contract or the next encounter. The game creates friction between what you want now and what you may need later. That is consequence in a softer form, but it comes from the same design principle as Zero Company: choices become more interesting when they leave residue.
Consequence Is Not the Same Thing as Punishment
None of this means every Star Wars game needs permadeath, one save file and a small funeral after every badly thrown grenade.
Different fantasies need different levels of permanence. A fast action game can become miserable if every mistake destroys hours of progress. Accessibility matters. Experimentation matters. Sometimes reloading is exactly what a game should allow, especially when the player is still learning systems or simply wants to experience the story without turning every mission into a tax return with blasters.
Zero Company gets this right by making permadeath optional. Outlaws gets it right by making reputation recoverable. Battlefront II and Empire at War use strategic persistence rather than character death. KOTOR lets narrative decisions do the damage.
The common thread is not cruelty. It is memory.
A game becomes more personal when it remembers enough of what happened that the player has to live with a version of events they did not fully plan. That is where stories appear that no writer had to script in advance: the fleet you lost over one insignificant planet, the Operator you protected for six missions and could not save on the seventh, the companion who never joined because of something you said twenty hours earlier.
Star Wars does not need more punishment. It needs more scars.
The films tell us what the galaxy has lost. Games can go one step further and make us responsible for losing some of it ourselves. That is often the difference between a campaign you finished and one you still remember years later.
About the author
Søren Ahrensborg Kamper is the editor of Star Wars: Gaming, an independent fan publication covering the history, design and evolution of Star Wars video games since 2009. He writes about game history, preservation, design and the stranger corners of the galaxy far, far away.
