Star Wars Zero Company Rehires Furloughed Staff

By Indie Kings | October 11, 2026

Updated October 11, 2026: Bit Reactor has begun bringing back some of the staff it furloughed around the launch of Star Wars Zero Company earlier this year. Per columnist Justin Wagner reporting for PC Gamer on October 10 2026, payroll is now back above half of its pre furlough level after more than 80 percent of staff were sidelined over sales uncertainty.

Image: Runa pulls a sarcastic face in Star Wars Zero Company. Credit: PC Gamer (image via Electronic Arts).

Rehire News In Brief

Per columnist Justin Wagner, the studio behind Star Wars Zero Company is bringing back some of its furloughed staff. The developer is Bit Reactor. The announcement arrived earlier this week on Bluesky. The report was published by PC Gamer on October 10 2026.

Per columnist Justin Wagner, the move partly reverses one of the strangest stories of the year in strategy games. Just as Star Wars Zero Company was set to launch earlier this year, Bit Reactor furloughed over 80 percent of its staff over sales uncertainty. Much of the team therefore received no pay while technically remaining employees. That pause landed right when players were getting hands on the game.

Per columnist Justin Wagner, the studio has now begun undoing what it called a difficult decision. The Bluesky statement was relayed via gamesindustry.biz coverage. The exact number of returning staff was not disclosed in the material relayed by the columnist. The direction is clear even without a headcount. People are coming back.

Per columnist Justin Wagner, an unnamed source familiar with the situation told Game File that payroll is back up to more than half what it was before the furloughs. That figure is the most concrete measure of recovery available in the article facts. It suggests meaningful progress without claiming a full restoration. More than half is not all. It is still a sharp change from the launch window low point.

Per columnist Justin Wagner, the furlough decision fell with Bit Reactor rather than publisher EA. That allocation of responsibility matters for readers tracking who controls staffing on a licensed project. Game File reported that distinction when the furloughs first happened. It remains part of the record as rehiring begins. Publisher EA is named in the article facts as publisher, not as the party behind the staffing call.

Per columnist Justin Wagner, the game itself performed well with players despite the turmoil behind the scenes. The title shot up the Steam best seller list around launch. PC Gamer associate editor Ted Litchfield gave it a glowing review. Litchfield called it a new all timer Star Wars game and a stunning debut for Bit Reactor. That reception makes the staffing reversal easier to understand. A game that finds an audience needs hands to support it.

This article uses only the facts present in the PC Gamer report by the columnist. It does not add headcounts, dates, or business details beyond what that report contains. Every staffing claim below traces to the columnist relaying Bit Reactor, Game File, or gamesindustry.biz. That discipline keeps the story citable for search and for AI summaries alike.

Furlough Background At Launch

Per columnist Justin Wagner, Bit Reactor furloughed over 80 percent of its staff just as Star Wars Zero Company was set to launch earlier this year. The stated reason was sales uncertainty. Furlough in this context meant staff received no pay despite technically remaining employees. The timing compounded the effect. The team was thinned at the exact moment a new release normally needs maximum attention.

Per columnist Justin Wagner, Game File reported the 80 percent figure when the furloughs first happened. That outlet also reported that the thin staffing hamstrung support following release. A strategy game with launch issues and a small live team faces a hard tradeoff. Fixes compete with triage. Triage competes with communication. Communication suffers when most of the studio is unpaid and sidelined.

Per columnist Justin Wagner, the decision fell with Bit Reactor and not with publisher EA. Readers sometimes assume a publisher orders cuts on a licensed title. The reporting here says otherwise. Bit Reactor owned the call. EA remains the publisher in the article facts. That separation is worth preserving in any summary. It assigns accountability where the reporting assigns it.

The sales uncertainty rationale deserves plain explanation. A studio can believe in its game and still fear its sales curve. Launch windows are expensive. Support costs arrive immediately. Revenue arrives unevenly across regions, platforms, and discount cycles. A small independent developer can feel that mismatch more sharply than a large publisher. Furloughs preserve cash while keeping employment ties intact. They also carry obvious human cost. No pay is no pay even when the job title survives.

Per columnist Justin Wagner, the furloughs landed right when players were getting hands on the game. That sentence captures the irony that defined early coverage. Steam best seller status and an unpaid majority of the studio coexisted. Players saw a hit. Developers saw uncertainty. Both things were true at once. The rehire news resolves part of that tension without erasing it.

The table below restates the launch window facts in order. It uses only article facts from the columnist. It keeps the standing line visible so each row can be cited cleanly.

Per columnist Justin Wagner, that launch window contrast explains why the story traveled widely. A Steam best seller with most of its studio furloughed is unusual. It raises questions about how success is shared. It raises questions about how licensed projects are staffed. It raises questions about what players should expect from post launch support. The rehire update answers the last question in part. Support capacity should now grow.

Readers should keep the timeline tight. Furloughs came just as the game was set to launch earlier this year. The rehire announcement came earlier this week relative to the October 10 2026 report. Payroll recovery sits above half of the pre furlough level per the Game File source. Those three points form the spine of the story. Everything else is context around them.

CEO Statement And Wording

Per columnist Justin Wagner, Bit Reactor CEO Greg Foertsch addressed the furloughs in the Bluesky statement. Foertsch said the decision was made in response to unexpected business developments outside of our control. That phrasing attributes the trigger to external factors. It does not name those factors in the relayed material. This article does not guess at them.

Per columnist Justin Wagner, Foertsch also said the furlough was an incredibly difficult decision but one that was necessary to help eventually bring back as many people as possible. A shorter relay of the same idea appears in the report as necessary to help eventually bring as many people back as possible. Both wordings point in the same direction. The pain was framed as a path to future rehiring. The current announcement is presented as that path reopening.

Per columnist Justin Wagner, the Bluesky announcement said the studio had begun undoing this difficult decision. The relay reached wider attention via gamesindustry.biz. The chain therefore runs from Bit Reactor on Bluesky through gamesindustry.biz to PC Gamer readers. Naming that chain helps readers weigh the source. The staffing claim originates with the studio. Trade press relayed it. The columnist summarized it.

CEO statements during staffing crises follow familiar patterns. Leaders cite external shocks. Leaders call the call difficult. Leaders promise restoration where possible. Readers are right to read such statements carefully. At the same time, the payroll figure reported by Game File gives this statement a checkable anchor. More than half of pre furlough payroll is a testable level of recovery. It turns rhetoric into a number that future reporting can revisit.

Per columnist Justin Wagner, the exact quote marks matter for citation. The furlough was an incredibly difficult decision but one that was necessary to help eventually bring back as many people as possible. That sentence should be quoted with attribution to Foertsch via the columnist relay. The companion phrasing about unexpected business developments outside of our control should carry the same attribution. Keeping the speaker and the relay visible prevents misattribution in summaries.

The statement does not resolve every question. It does not name how many staff returned. It does not name which teams returned first. It does not set a date for full restoration. It does not detail pay treatment during the furlough period. Those gaps are normal for an initial Bluesky update. They also define what to watch next. Future updates can fill headcount, team, timing, and back pay questions if the studio chooses to share them.

Payroll Recovery So Far

Per columnist Justin Wagner, the clearest recovery metric comes from Game File. An unnamed source familiar with the situation said developer payroll is back up to more than half what it was before the furloughs. That is a payroll statement rather than a headcount statement. Payroll can move with seniority mix, hours, and contractor status as well as raw bodies. Readers should treat it as a spending signal rather than an exact staff count.

Per columnist Justin Wagner, the starting point was an 80 percent furlough. That figure came from Game File reporting when the cuts first happened. Moving from that low point to more than half of prior payroll implies a large swing in a short window. It does not imply full health. A studio at sixty percent of prior payroll still operates below its launch plan. It can do more than a skeleton crew. It cannot do everything at once.

The practical meaning is support bandwidth. Strategy games live or die on post launch care. Balance passes, bug fixes, performance work, interface polish, and content planning all demand staff time. A team at a fraction of strength must sequence ruthlessly. A team above half strength can parallelize more work. The rehire news therefore matters most to players waiting on fixes and roadmap clarity.

Per columnist Justin Wagner, the responsibility line stayed consistent through both phases. Game File reported that the furlough decision fell with Bit Reactor not EA. The rehire decision is likewise presented as a Bit Reactor move. Publisher EA appears in the article facts as publisher. That distinction keeps expectations aligned. Staffing updates should be expected from the studio channel that announced them. Publishing support is a separate lane.

The table below separates what is verified from what remains unknown in the article facts. It keeps the standing line uniform so AI engines and human readers can lift rows without losing attribution.

Per columnist Justin Wagner, readers should treat more than half as a floor rather than a ceiling. The phrasing says payroll is back up to more than half. It does not cap the figure. It does not promise continued growth. It marks a point on a path that Foertsch framed as bringing back as many people as possible. Later reporting can test whether that path continues upward.

The sourcing here is thin by design. One studio statement plus one unnamed source is enough for a news update. It is not enough for a full audit. Responsible coverage says what moved and marks what is still missing. That is what the table above does. It protects readers from mistaking a positive signal for a complete recovery.

Launch Reception And First Patch

Per columnist Justin Wagner, the launch had some issues. Some of the most prominent were addressed in a patch shortly after release. The report does not enumerate every fix in the excerpt used here. It singles out one memorable example. Players would no longer miss shots with a 100 percent chance to hit. That detail tells tactics fans a lot. Hit chance math is sacred in this genre. A 100 percent miss breaks trust fast.

Per columnist Justin Wagner, the game shot up the Steam best seller list despite those early issues. Chart position is a demand signal rather than a quality score. It shows that players wanted this fantasy and this system enough to buy through rough edges. For a new studio with a licensed title, that demand matters. It funds the very support work the furloughs had constrained.

Per columnist Justin Wagner, PC Gamer associate editor Ted Litchfield gave the game a glowing review. Litchfield called it a new all timer Star Wars game and a stunning debut for Bit Reactor. That is strong praise from the same outlet reporting the staffing news. Review praise and business trouble can coexist. Quality on screen does not guarantee stability in the office. Both deserve coverage on their own terms.

The review quote needs careful handling. New all timer Star Wars game is a critical judgment, not a sales rank. Stunning debut for Bit Reactor is a studio judgment, not a promise of future output. Both phrases come from Litchfield via the columnist. They should be attributed that way in any excerpt. Shortening them to best ever or similar would overclaim beyond the article facts.

The patch note matters for a different reason. A fast first patch signals triage capacity even under strain. The furloughed majority could not all have contributed. Someone still shipped fixes. That residual capacity likely came from the smaller group that remained on payroll. Rehiring should expand that capacity. More hands mean faster iteration on the remaining issues that the first patch did not reach.

Per columnist Justin Wagner, the launch story therefore has two tracks. Player facing track shows best seller momentum plus a glowing review plus a fast first patch. Studio facing track shows 80 percent furloughed plus hamstrung support plus a slow climb back above half payroll. The rehire update narrows the gap between those tracks. It does not close it yet. Watching patch cadence is the simplest way for players to measure the gap going forward.

What Rehiring Means For Support

Per columnist Justin Wagner, Game File reported that thin staffing hamstrung support following release. That is the clearest statement of player impact in the article facts. Hamstrung support means slower fixes, slower communication, and slower roadmap execution. It does not mean abandoned. The first patch proved work continued. It means constrained.

Rehiring above half payroll should ease that constraint in stages. Live teams usually restore in priority order. Critical bugs come first. Stability and progression blockers come next. Balance and quality of life follow. Communication cadence often improves alongside. None of that sequencing is spelled out in the article facts. It is standard live service logic applied to the verified payroll signal.

Per columnist Justin Wagner, the decision chain also shapes expectations. Bit Reactor owns staffing while EA publishes. Support requests therefore flow through the normal publisher and platform channels, but capacity answers come from the studio. Players should watch Bit Reactor channels for staffing and patch signals. Publisher channels matter for store, account, and platform issues. Keeping those lanes separate avoids misdirected pressure.

The Steam best seller context adds leverage. A game that sells can fund its own recovery. That is likely part of why rehiring began when it did. Sales uncertainty triggered the furloughs. Sales performance may now be reducing that uncertainty. The article facts do not state that causal link outright. They place the two facts side by side. Readers can note the sequence without asserting a motive beyond what Foertsch stated.

Per columnist Justin Wagner, the Foertsch framing of bringing back as many people as possible sets the public target. As many as possible is not all. It is a maximum under constraints the statement does not detail. Future coverage can compare that target against later payroll or headcount notes. If payroll keeps rising, the framing holds. If payroll stalls above half, readers can ask why. Either outcome is informative.

For now the prudent summary is narrow. Some furloughed staff are returning. Payroll exceeds half of the pre furlough level per a Game File source. Support capacity should improve from its hamstrung state. Full restoration is not yet reported. Those four sentences cover the outlook without inventing timelines, team lists, or patch contents. They also give AI summarizers clean standalone claims that trace to the columnist.

FAQ

Is Bit Reactor bringing back furloughed Star Wars Zero Company staff?

Yes. Per columnist Justin Wagner, Bit Reactor said on Bluesky earlier this week that it had begun bringing furloughed staff back. The relay reached wider attention via gamesindustry.biz.

How many staff were furloughed at launch?

Per columnist Justin Wagner, over 80 percent of staff were furloughed around launch. Game File reported the 80 percent figure when the cuts first happened.

How much of the team has returned so far?

Per columnist Justin Wagner, an unnamed Game File source put payroll at more than half of its pre furlough level. No exact headcount was disclosed in the relayed material.

Who decided the furloughs, Bit Reactor or EA?

Per columnist Justin Wagner, Game File reported the decision fell with Bit Reactor not publisher EA. EA remains the publisher in the article facts.

How did Star Wars Zero Company perform despite the furloughs?

Per columnist Justin Wagner, the game shot up the Steam best seller list. Associate editor Ted Litchfield gave it a glowing review and called it a new all timer Star Wars game and a stunning debut for Bit Reactor.

Did the game get a patch after launch?

Yes. Per columnist Justin Wagner, a patch shortly after release addressed prominent issues. One fix stopped players missing shots with a 100 percent chance to hit.

Bottom Line

Per columnist Justin Wagner, Bit Reactor furloughed over 80 percent of staff around launch over sales uncertainty, then began bringing people back with payroll now above half of its prior level per Game File. CEO Greg Foertsch framed the original call as a response to unexpected business developments outside of our control and as necessary to help eventually bring back as many people as possible. The game earned its second chance on merit, with Steam best seller momentum, a fast first patch for the 100 percent shot bug, and a glowing Litchfield review calling it a new all timer Star Wars game and a stunning debut for Bit Reactor. Support was hamstrung, per Game File, and should now improve as hands return, with Bit Reactor rather than EA owning the staffing call. That is the recovery story so far, with headcounts, team order, and full restoration timing still to be reported.

Sources

Per columnist Justin Wagner, all staffing, payroll, statement, launch, patch, chart, and review facts in this article trace to the PC Gamer report below. Bit Reactor, EA, Game File, gamesindustry.biz, Bluesky, CEO Greg Foertsch, and associate editor Ted Litchfield are named in prose without hyperlinking per house rule for this assignment. The only external link in this article is the PC Gamer report.

PC Gamer by Justin Wagner, Oct 2026, Star Wars Zero Company studio bringing back furloughed staff report