BALANCEb545rel/workforce4 min read

Bit Reactor Lays Off Staff 71 Days After Star Wars Launch

Bit Reactor laid off staff 71 days after launching Star Wars Zero Company, following a pre-launch furlough of most staff and a partial October recall. The studio has disclosed no headcount.

Bit Reactor: 3-Month Furlough Ends in Layoffs [2026]
Bit Reactor: 3-Month Furlough Ends in Layoffs [2026]StartupStockPhotos / pixabay

Patch notes

  • Bit Reactor laid off an unspecified number of employees, with November 6 named as the last day for several affected staff.

  • Star Wars Zero Company launched August 27; the layoffs came 71 days later, and the October 7 recall message came 41 days after launch.

  • One report put the pre-launch furlough at roughly 80% of staff; the studio has not confirmed the figure.

  • Four former employees have been named: Michael Blackard, Ryan Mosher, Ryan Lopez, and Tyler Eichten.

  • No named source confirms sales figures, insolvency, or direction from Electronic Arts or Disney.

Bit Reactor, the studio behind Star Wars Zero Company, has laid off an unspecified number of employees, with several affected workers naming November 6 as their last day. The studio has not disclosed a total. Four former staffers have been named in coverage: Michael Blackard, Ryan Mosher, Ryan Lopez, and Tyler Eichten. That list is almost certainly a floor, not a headcount.

The sequence makes this case unusual. Bit Reactor furloughed most of its staff before the game shipped on August 27, started returning some workers in early October, then cut jobs roughly a month later. Workers caught in the middle absorbed three separate shocks in under three months.

What is confirmed, and what is not?

The confirmed facts are narrow. CEO Greg Foertsch said on October 7 that the studio had "started the process of returning more of our team back to work." By arithmetic, that is 41 days from launch to the rehiring message and 71 days from launch to the layoffs. One report put the pre-launch furlough at roughly 80% of staff; the studio has not confirmed that figure.

Several claims circulate without a named source behind them:

  • The exact number of people laid off.
  • Any link between the cuts and poor sales.
  • Any claim of insolvency.
  • Any direction from Electronic Arts or Disney.
  • A social media claim that the game sold one million copies.

None of these has verification from the studio, a publisher, or a named analyst.

What did the CEO say?

Foertsch addressed the furlough directly in an earlier public statement reported by Video Games Chronicle. He said: "Having to ask team members to step away after we navigated unexpected business developments outside of our control and so close to launch was an incredibly difficult decision, but one that was necessary to help us eventually bring as many people back as possible."

Two phrases carry weight. "Outside of our control" points to an external trigger he did not name. "As many people back as possible" framed the furlough as a bridge. The November layoffs show the bridge did not reach every worker.

The October wording also signaled a staged return. "Started the process" and "more of our team" both tell staff that some roles return and some may not.

What did affected developers say?

Two former employees posted public statements, as reported by VGChartz. Ryan Lopez, a senior environment artist, wrote: "I was laid off from Bit Reactor this week after a three-month furlough, and while it stings, I'm really proud of what we built together." Tyler Eichten, a UI engineer, wrote: "As of today, my time with Bit Reactor has come to a close due to a layoff."

Neither statement blames the studio or a publisher. That restraint is typical, since severance terms can carry non-disparagement clauses.

Lopez's wording matters for the timeline. A layoff following a three-month furlough suggests the October recall did not end the furlough for everyone. At least some workers stayed off payroll for the full stretch before a final notice.

Why did a well-reviewed game precede layoffs?

Critical praise and studio cash are different things. For a work-for-hire or licensed developer, money often arrives in milestone payments tied to contracts, not a share of retail sales. When a contract phase ends, headcount can drop even if the shipped product earns strong reviews.

The timing argues against a simple "the game flopped" story. The furlough began before launch, which means the staffing problem predates any sales figure. Furloughing most of a team right before a launch, when studios need hands for patches and day-one bugs, suggests a cash or contract problem rather than a workload problem. The studio has not said which.

Licensed games add structural risk. A rights holder controls the brand, a publisher controls funding and schedule, and the developer controls only the craft. Foertsch's phrase could describe a funding delay, a scope change, or a schedule shift. None requires poor sales.

What does this change for studios and workers?

For mid-size studios signing licensed deals, the signal is about contract terms. A praised Star Wars game that still leaves its developer cutting staff will push studios to demand milestone payments covering the post-launch period, not only the build.

For workers, the furlough layer is the real cost. A furlough keeps the employment relationship alive and asks people to wait. Workers often cannot take a full-time job elsewhere without giving up the recall promise. Lopez spent a quarter of a year in that in-between state before the layoff ended it.

Bit Reactor also stands out in the season's wider cuts. Tripwire Interactive laid off 36 people in a second round this year, and more than 25 people were named in Skydance Games cuts with no official total. The pattern of partial disclosure repeats across all three.

What happens next?

Four signals will clarify the picture: a studio statement with a headcount, any comment from the publisher or rights holder, new LinkedIn posts describing how the cuts rolled out, and any change to the game's update schedule. The key unanswered question is whether anyone brought back in October was among those cut in November. Until Bit Reactor or its partners speak, the total stays private, and the named list of four is the only public measure.

via shattered.io (Source)

Share this article:

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on video game industry at Game Dev Wire.

248 articles