The Best-Reviewed Star Wars Game in Years Furloughed 80% of Its Studio Before Launch

3 days ago by Kael Voss 4 min read

Five days after I called Star Wars: Zero Company's critical reception a rare happy ending for this franchise's gaming track record, the actual story got darker. Up to 80% of developer Bit Reactor's staff were furloughed in the weeks before launch, and a co-founder's ownership lawsuit alleges most employees were furloughed while contractors were simply let go outright.

I wrote something optimistic about Star Wars: Zero Company on this blog last week. An 88 on OpenCritic, 91% of critics recommending it, a debut studio nailing a genre and a setting on the first try — I called it the rare Star Wars gaming story with an actual happy ending. I stand by every word of that review of the game itself. What I didn't know, because it wasn't public yet, is what was happening inside Bit Reactor while critics were writing those glowing pieces.

The Numbers Behind the Reviews

As many as 80% of Bit Reactor's staff were furloughed in the weeks leading up to the August 27 launch. Not laid off in the technical, severance-and-goodbye sense — furloughed, which in practice means most of the team that built one of the best-reviewed Star Wars games in over two decades has been going without pay while their game climbs review aggregators without them. A studio formed in 2021 by veterans of Civilization and XCOM, built specifically to make this kind of tactical Star Wars game well, apparently ran out of most of its money right before the thing it built finally shipped.

There's also an ownership dispute tangled into this that's uglier than a simple cash crunch. Co-founder Alison Kelly, who served as Bit Reactor's chief operating officer until 2024, sued studio head Greg Foertsch alleging she was pushed out and that he unjustly enriched himself — claiming she was a co-owner of the studio rather than an employee he could simply remove. That suit isn't set to go to trial until 2027, but an August 12 filing updated the claims to include the furlough situation directly: most employees furloughed, contractors reportedly cut loose entirely, weeks before the game they built hit shelves.

Sitting With the Contradiction

Here's the uncomfortable part: both things are true at once. Zero Company is a genuinely well-made game — critics who went in skeptical of another licensed tactics title came out comparing it to Rogue One and KOTOR, and that reaction wasn't manufactured or bought. The Clone Wars setting works, the tactical combat works, the original characters carry a story that doesn't lean on a familiar Jedi to hold interest. None of that praise was wrong. But it was also, it turns out, written without knowing that the people who made those systems sing may not have had paychecks coming in while critics played the finished build.

This isn't a uniquely Star Wars problem — game development across the industry has been brutal for years now, with studios shipping acclaimed titles and collapsing or gutting their staff within months, sometimes weeks, of release. What makes it sting more here is the contrast: this was supposed to be the good news story. After Star Wars: Eclipse spent years in limbo and multiple other projects quietly died in development, Zero Company was the proof that the formula still works when a studio is "allowed to actually finish the thing," which is more or less exactly what I wrote five days ago. Finishing the thing, it turns out, may have cost the people who finished it their paychecks.

What This Means Going Forward

I'm not walking back the review. The game earned its praise, and Bit Reactor's designers, artists, and engineers earned that praise too, whatever their employment status looked like the week it shipped. But a franchise-focused blog that only covers the shiny review-score version of a story and ignores the labor dispute sitting right underneath it isn't doing its job. Lucasfilm Games and EA published this title; neither company has said much publicly about what's happening at their newest critical darling's home studio, and that silence is worth noting on its own.

Whether Bit Reactor survives long enough to make a second game — whether this was a temporary cash-flow crunch solved by strong Zero Company sales, or the beginning of the studio quietly winding down the way so many acclaimed developers have before it — is genuinely unclear right now. The lawsuit alone runs into 2027. What's clear is that "the hype was justified" and "the people behind it were treated badly" aren't mutually exclusive headlines. Both belong in the same story. May the Force be with the developers who actually built this thing, wherever their paychecks currently stand.


Comments (0)