TODAY’S PAPER | February 16, 2026 | EPAPER

Highguard studio Wildlight Entertainment announces layoffs weeks after launch

Wildlight Entertainment confirms layoffs at Highguard studio 17 days after servers went live


Pop Culture & Art February 12, 2026 1 min read

Wildlight Entertainment, the studio behind free-to-play raid shooter Highguard, has confirmed company-wide layoffs just 17 days after the game launched.

The California-based developer acknowledged that “a number of team members” had been let go, adding that a “core group” would remain to continue supporting the title. Exact figures have not been disclosed, though one affected employee said the cuts impacted “most of the team”.

Level Designer Alex Graner wrote on LinkedIn: “Unfortunately, along with most of the team at Wildlight, I was laid off today. This one really stings as there was a lot of unreleased content I was really looking forward to that I and others designed for Highguard.”

Other staff members, including Senior Software Engineers and artists, also confirmed their departures. Lead Tech Artist Josh Sobel said: “It was the best team I’ve ever worked with. I’ve never put so much of myself into a project before.”

In a statement, the studio said: “We’re proud of the team, talent, and the product we’ve created together. We’re also grateful for players who gave the game a shot, and those who continue to be a part of our community.”

Highguard was revealed at the 2026 Game Awards and launched shortly after a preview period. It peaked at 97,249 concurrent players on Steam but has since seen a decline.

At the time of writing, the game’s 24-hour peak stands at 3,822 players, placing it outside the top 200 most active titles on the platform.

Prior to release, developers outlined a year-one roadmap featuring new Vanguards, maps and weapons. It remains unclear how the layoffs will affect those plans or the long-term future of Highguard.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ