Bit Reactor, the studio behind Star Wars Zero Company, furloughed most of its staff in the weeks before the RPG launched last week, even as the game sits among Steam’s current bestsellers. Furloughed staff remain technically employed but draw no wage while the furlough runs. Reported scale varies: some accounts put the Bit Reactor furloughs at around 80 percent of the workforce, others describe it only as “most” or “many” of the team.
A furlough is different from a layoff: staff keep their jobs and, depending on the terms, some benefits, but draw no salary until the company recalls them or the furlough lapses into a layoff outright. For a studio the appeal is speed: it can cut costs immediately without severance obligations, then bring people back the moment the numbers justify it. For staff, it means uncertainty without the closure, or the severance, a layoff would bring.
What triggered the Bit Reactor furloughs
A Bit Reactor representative confirmed the furloughs without giving a specific number affected. The stated reason was uncertainty over how the game would perform commercially at launch. The representative also said the decision was Bit Reactor’s own, not one imposed by EA or Disney, both of which hold stakes in the Star Wars license the game is built on. That framing casts the furloughs as ordinary financial caution by an independent studio rather than a publisher-driven cut.
The timing makes the caution look, in hindsight, overcautious: the furloughs were decided before launch, when Bit Reactor had no sales data to go on. Star Wars Zero Company then opened well enough to reach Steam’s bestseller list, the kind of result that would normally justify keeping a full team in place rather than cutting most of it loose beforehand.
Staff affected by the furloughs reportedly don’t know whether they’ll be brought back once it ends. That leaves them in limbo despite Star Wars Zero Company shipping to strong reviews and selling well enough to land on Steam’s bestseller charts within days of release. Commercial success at launch hasn’t, so far, translated into job security for the people who built the game.
A legal dispute the official explanation leaves out
Bit Reactor’s stated reason for the furloughs doesn’t mention a separate complication: a legal dispute between the studio’s founders that has put its ownership into question, reported by Eurogamer. That sits awkwardly next to the “launch uncertainty” explanation. A studio hedging against poor sales furloughs staff for financial reasons tied to the product; a studio fighting over who owns it furloughs staff for reasons that have nothing to do with how many copies a game sells. Neither Bit Reactor nor its founders have publicly reconciled the two accounts, and the studio hasn’t addressed the ownership dispute directly.
The gap matters for anyone tracking the studio’s future. Star Wars Zero Company is expected to receive post-launch support, patches and potentially further content, work that typically falls to the same developers now sitting out an unpaid furlough. Running that support with a skeleton crew, while an ownership question remains unresolved, is a different problem than the temporary belt-tightening Bit Reactor described to Game File.
What to watch next
Two threads are worth following separately: whether Bit Reactor’s furloughed staff are actually recalled once the furlough period ends, and whether the ownership dispute between the studio’s founders gets resolved, or even acknowledged, in public. Until either happens, the strong sales figures for Star Wars Zero Company and the state of the studio that made it are two different stories running in parallel.
