Fishlabs’ Layoff Announcement Now Has a Human Count: 17 Workers
Fishlabs’ October 16 restructuring announcement said the studio would reduce staff across development and support. It did not say how many workers were affected. Three days later, GamesWirtschaft reported that a public referral post by studio director Angelo Bod listed 17 colleagues seeking new opportunities. That is a reported count based on the post—not a separately confirmed company headcount.
A list of people, not just job titles
GamesWirtschaft said the referral list spans art, UI, production, game design, programming and QA. That range matters: game development is a team sport, even when business plans discuss people as a line item that can be moved with the solemnity of rearranging office chairs. These are workers with different skills and careers, now looking for what comes next.
The referral post is a practical gesture in a difficult moment: it puts affected colleagues and their skills in view. It also gives the public a clearer picture of the scale than the company’s first announcement did. But the figure should stay attached to its source: GamesWirtschaft’s report on Bod’s post, rather than a number Fishlabs itself provided. A list of disciplines also reminds us that making a game involves more than the people whose names appear on a box or a launch trailer.
What Fishlabs says—and what remains unknown
In its workforce statement, Fishlabs said changing project requirements, along with client and internal needs, led it to reassess its structure. The studio also said it remains committed to its partner projects. Those are the company’s stated reasons and assurance; the available reporting does not establish that a particular game, release date or online service will change.
That distinction matters to players, too. A staff reduction can raise understandable questions about the games people follow, but questions are not evidence of a delay, cancellation or service disruption. There is no basis in these sources to attach the cuts to a specific title or player-facing outcome. The report identifies workers across several disciplines; it does not provide a project-by-project account of what happens next.
So the useful takeaway is both human and limited. The later referral post makes the scale more visible, while Fishlabs’ statement explains its restructuring in broad business terms. Players may want answers about individual projects, but the public information here does not supply them. For now, the people seeking their next roles are the clearest consequence—and they deserve more than being treated as a footnote in a project plan.