Star Wars Zero Company lets squad failure tell the story

Narrative choice has trained us to look for the machinery. A dialogue wheel appears. Somebody asks whether the prisoner lives, the town burns, or we say the heroic thing, the cruel thing, or the suspiciously flirtatious thing. We choose and wait for the story to react.

That model works, and the return of narrative-choice games made a good case for why it is finding new life. Star Wars Zero Company is interesting because it often moves the choice somewhere else. Sometimes the important decision is not what Hawks says. It is whether you spend the last Action Point on a risky shot when one of your Operators already has two Injuries.

That is a less glamorous place to hide a narrative system. It is also where some of the game’s best stories happen.

Choice can happen after the dialogue wheel disappears

With Permadeath enabled, an Operator who is Downed gains an Injury. Rally can get them back into the fight, but it does not erase what happened. Reach three Injuries and that squad member is gone permanently.

The clever part is that the third Injury is rarely the whole story. One Injury says somebody had a bad mission. Two Injuries change how we read the same piece of cover next time. Do we risk the veteran because their build is perfect for the situation, or send a less experienced recruit because the veteran has become too valuable to gamble on a 70% shot? The game does not need a cutscene explaining that we are afraid to lose them. We have already started behaving like it.

That effect was captured neatly in our Zero Company review, where Chris Melnyk described returning to the ship after a battle and noticing one seat empty. The objective was complete, yet the campaign had acquired a hole a new recruit could not immediately fill.

A replacement is not the same character with fresh paint

Tactics games are exceptionally good at making us irrationally attached to spreadsheets with names. Give a soldier a promotion, a lucky escape and a ridiculous helmet, and ten hours later we are negotiating with the universe on their behalf. Zero Company adds biographies, Specializations, equipment and relationships.

Customization matters because it creates authorship. Choosing an outfit is not narratively profound on its own. Nobody has completed a dissertation because a Twi’lek received nicer boots. But the more small decisions we make about a character, the more that character belongs to our version of the campaign. Permadeath then gives the game the nerve to take those decisions seriously.

Knights of the Old Republic remains a useful comparison because character building and story choice reinforce each other. Zero Company reaches similar territory from the opposite direction: tactical investment changes how much the squad means before the story asks for a dialogue choice.

Bonds turn relationships into something you actually use

The Bonds system makes this more than a permadeath story. Operators grow closer through missions, Operations and combat support. Stronger Bonds unlock support and cross-training benefits, while some dilemmas can strengthen or weaken those relationships. The relationship does not live in a codex entry waiting to be remembered.

If two people work well together, the tactical layer can reward that history. Calling for Backup is no longer only a damage calculation; it is another repetition of a partnership the campaign has been building. Lose one of those Operators and the cost is not simply one gun. A replacement may eventually learn the same job, but they arrive without the history.

The best consequences do not need a new ending

Branching narrative has a practical enemy: scale. If every decision creates a separate branch, scripts, voice recording and testing multiply until somebody has to explain why a missing sandwich needs three endings.

Good choice-driven games therefore cheat elegantly. They converge branches and track smaller variables that make scenes feel personal. Zero Company already generates those through play: who survived, who is injured, which pair has a strong Bond, and which Operator has become essential.

That means the game can change the texture of a campaign without rebuilding the entire final act. The broad history of the Clone Wars may remain fixed, but the route through it can still belong to this squad. A personal story does not require a unique final cinematic. Sometimes it only requires the game to remember who reached it.

Failure works best when the game remembers it

Zero Company still lets players restart Tactical Missions, and Hawks dying can fail the mission outright. It is not an ironman simulator determined to slap the reload button out of your hand. That flexibility is sensible; forced misery is still misery, even when the menu calls it authenticity.

But when we accept a bad result, the game can carry it forward. Injuries survive the firefight. Bonds can change. A costly victory can reshape the roster. The Memorial exists because some names are expected to become history. None of this requires a completely different story path. It simply stops failure from evaporating when the results screen appears.

That distinction matters. A game can contain 50 dialogue choices and still feel frictionless if every mistake is cleaned up before the next chapter. Another can tell a mostly fixed central story and still feel deeply personal because the systems carry scars forward. The number of branches is not the same thing as the weight of a decision.

Let the player write the smaller stories

The Clone Wars is well suited to this approach. We know where the Republic is going, what will happen to the Jedi and which gentleman in a hood has been suspiciously productive. Zero Company cannot hand us that history without turning canon into very expensive fan fiction.

What it can do is make the space underneath that history personal. One campaign remembers the sharpshooter retired after two Injuries. Another remembers the custom Operator who began as roster filler and became indispensable. Another remembers a Bond made fragile by one terrible deployment.

For the mechanical side of Injuries, Bonds, builds and campaign systems, the complete Zero Company guide at Star Wars: Gaming collects the practical details. The broader narrative lesson is simpler: players do not need authorship over the whole plot to feel authorship over the experience.

A dialogue wheel can tell us that a decision matters. A tactics game can make one square of half cover matter because of everything that happened before it. The galaxy may still reach the same destination. The company that arrives there does not have to be the same one that left.

Søren Kamper

Søren Kamper is the editor of Star Wars: Gaming, an independent site covering Star Wars video games, their history and the people who make them.