Ask Runable forDesign-Driven General AI AgentTry Runable For Free
Runable
Back to Blog
Gaming Industry38 min read

Game Studio Layoffs After Launch: What Went Wrong [2025]

Wildlight Entertainment laid off most of its team weeks after Highguard's launch. Explore why post-launch layoffs happen, industry trends, and what this mean...

game studio layoffsHighguard game failureWildlight Entertainmentlive service gamesgame development economics+10 more
Game Studio Layoffs After Launch: What Went Wrong [2025]
Listen to Article
0:00
0:00
0:00

Game Studio Layoffs After Launch: What Went Wrong [2025]

When a game launches to fanfare and then the development team gets decimated weeks later, something went seriously wrong. Not with the code or the art assets, but with the business planning.

Wildlight Entertainment's decision to lay off "most" of its team just weeks after Highguard went live is a painful reminder of how brutal game development economics can be. On the surface, it looks like another casualty of the video game industry's ongoing contraction. But dig deeper, and you'll find a much more complicated story about player expectations, concurrent user metrics, live service failure modes, and the fundamental mismatch between what publishers greenlight and what players actually want.

This isn't just about one studio or one game. It's about systemic problems in how games get funded, how success gets measured, and how quickly the industry can pivot when reality doesn't match projections.

Let's break down what happened with Highguard, why it happened, and what this teaches us about the future of game development.

TL; DR


TL; DR - visual representation
TL; DR - visual representation

Highguard Player Count Decline Post-Launch
Highguard Player Count Decline Post-Launch

Highguard experienced a dramatic 97% decline in player count within two weeks of launch, highlighting severe player retention issues. Estimated data.

What Is Highguard and Why Did It Matter?

Highguard was supposed to be something special. Wildlight Entertainment brought together talent from Respawn Entertainment, the studio behind Apex Legends and the Titanfall franchise. In the competitive multiplayer space, that pedigree matters. A lot. When former leads from a battle royale that pulled in millions of concurrent players announce a new arena shooter, the gaming community pays attention.

The game was announced as a "one more thing" surprise moment during The Game Awards in December 2024. That's the kind of stage usually reserved for major AAA announcements or indie darlings that captured hearts and imaginations. The audience's response, however, was noticeably subdued. No standing ovation. No immediate chatter of it being the next big thing. It was professional applause, the kind you give when something competent gets revealed but doesn't blow your mind.

In hindsight, that tepid reaction should have been a warning sign.

Highguard is an arena shooter, a competitive multiplayer game focused on skill-based combat in contained environments. Think less battle royale (where you drop on a map and loot for 20 minutes) and more focused, fast-paced gunplay. Games in this space include Unreal Tournament, Quake, and more recently, titles like Valorant that blend arena mechanics with hero abilities.

The problem? The competitive arena shooter market is saturated. Counter-Strike 2 dominates the tactical shooter space. Overwatch 2 commands the hero shooter audience. Halo Infinite still has a dedicated community. Finding a lane in this crowded market requires either revolutionary mechanics or exceptional execution.

Highguard attempted neither. It arrived as a competent but unremarkable entry into a space already drowning in options.

QUICK TIP: When evaluating multiplayer game success, look at the peak concurrent players in the first week, not just launch day numbers. Retention curves tell the real story.

The Launch Window and Initial Player Response

When Highguard launched at the end of January 2025, it hit approximately 100,000 concurrent players on Steam. That's a respectable start for an indie-backed title. For context, many games would celebrate those numbers as a win.

But in the live service economy, launch day numbers are only relevant if they sustain. And they didn't.

The player count didn't slowly decline over weeks or months. It collapsed. Within a couple of weeks, concurrent player numbers had dropped from 100,000 to under 3,000. That's a 97% decline in player engagement in the span of approximately 14 days.

To understand why this matters, you need to grasp the math of live service games. These titles are funded on the assumption of sustained player bases that generate recurring revenue through battle passes, cosmetics, and seasonal content. The business model doesn't work with 3,000 concurrent players. It can't.

A typical free-to-play game needs a minimum concurrent player base to justify ongoing development costs. Industry estimates suggest around 50,000 concurrent players provides enough foundation for a small team to continue supporting the game profitably (depending on monetization strategy and player spending patterns). At 3,000 concurrent, you're bleeding money with no reasonable path to recovery.

Wildlight tried to respond. The studio made balance adjustments based on player feedback. They listened to the community and made changes. This isn't unusual—most live service games iterate heavily during the launch window. But iteration without players is just shouting into the void.

The damage was already done. Players had made their decision, and no amount of bug fixes or balance tweaks were going to bring them back.

DID YOU KNOW: Successful multiplayer games typically see their steepest player drop-off in days 3-7 post-launch. If a game survives that critical window, it has a much better chance of long-term viability.

The Launch Window and Initial Player Response - contextual illustration
The Launch Window and Initial Player Response - contextual illustration

Cost Breakdown of Game Development
Cost Breakdown of Game Development

Salaries are the largest cost component, followed by server infrastructure and marketing. Estimated data.

The Layoff Announcement and What It Means

Level designer Alex Graner broke the news on Linked In. The studio had laid off "most" of the team. Not all—Wildlight claimed it would keep a "core group of developers to continue innovating on and supporting the game." That phrase, "core group," is industry speak for "skeleton crew."

A skeleton crew typically means 5-15 people handling maintenance and basic updates. No new content pipeline. No substantial feature development. Just enough people to apply critical bug fixes and keep the servers running. If the game starts generating revenue again, maybe you expand. Until then, you're in damage control mode.

The phrasing is important here. Wildlight didn't say "we're shutting down Highguard." They said they'd keep supporting it. This is technically true but operationally meaningless. A skeleton crew can't develop new maps, refine gameplay mechanics, design new cosmetics, or build seasonal content. They can barely keep the lights on.

What makes this particularly brutal is the timing. Weeks after launch—not months, not even a full month. This wasn't a slow burn where the studio gradually realized player numbers weren't recovering. This was a rapid triage operation executed with desperation.

The company issued a statement thanking "players who gave the game a shot, and those who continue to be a part of our community." Translation: we're grateful for the free community engagement, but we can't afford to develop for it anymore.

No developer wants to lay off team members. It's devastating to everyone involved. But the decision reflects a simple calculation: the revenue generated by Highguard doesn't justify the cost of maintaining even a moderate development team.

Skeleton Crew: A minimal staff maintained to handle essential operations while a project winds down or transitions to maintenance mode. Typically 10-20% of original team size, focused on critical bug fixes, server uptime, and security updates rather than new features.

Why Live Service Games Fail So Dramatically and So Fast

Live service games operate on a fundamentally different business model than traditional releases. When you buy a single-player game like Baldur's Gate 3 or a traditional multiplayer game with a single payment model, you're buying a complete experience. The developer gets paid once, and the relationship ends (unless they release DLC).

Live service games reverse this equation. The initial download is free or cheap. Players pay small amounts repeatedly through cosmetics, battle passes, and convenience items. The entire financial model depends on sustained engagement and monetization.

This creates a precarious situation. The game must maintain sufficient player concurrency to:

  1. Justify server costs - Running multiplayer servers is expensive. More players means higher infrastructure costs, but also more potential revenue. Below a certain threshold, servers become a loss leader.

  2. Support matchmaking - With too few players, matchmaking becomes impossible. Queue times grow. Players in different regions can't find opponents. The experience degrades rapidly.

  3. Generate cosmetic revenue - If nobody's playing, nobody's buying skins, emotes, or battle passes. Revenue evaporates.

  4. Sustain development - Art teams, designers, programmers, QA staff all need to be paid. New content requires continuous creation. With minimal players, that ROI doesn't work.

Highguard hit the tipping point where it couldn't sustain any of these factors. The player base collapsed too quickly for the studio to either reduce costs proportionally or make the game compelling enough to retain players.

The cruel mathematics: A game might have 50 million dollars in development budget, a 100-person team, and server infrastructure built to handle 500,000 concurrent players. If only 3,000 show up, you're running

500,000permonthinfrastructurecostswithperhaps500,000-per-month infrastructure costs with perhaps
10,000 in monthly cosmetic revenue. The math doesn't work.

QUICK TIP: When a free-to-play game shuts down or goes into maintenance mode, check the concurrent player count. It's almost always under 10,000, often under 5,000.

Why Live Service Games Fail So Dramatically and So Fast - visual representation
Why Live Service Games Fail So Dramatically and So Fast - visual representation

The Pedigree Problem: Why Reputation Doesn't Guarantee Success

Here's the frustrating truth for Wildlight Entertainment: being founded by former Apex Legends developers should have meant success. On paper, it did.

Apex Legends is a phenomenal game. Launched in 2019 by Respawn Entertainment, it carved out a substantial niche in the battle royale market alongside Fortnite and PUBG. The game featured exceptional character design, fluid gunplay, and a well-balanced economy of abilities and ultimates. When key talent from that team announced a new project, the gaming community should have been excited.

But success in one game doesn't transfer mechanically to another. Several factors explain why:

Different genre, different audience - Apex Legends succeeded in the battle royale space, a market that had already been validated by Fortnite and PUBG. The mechanics were familiar enough that players understood the basics immediately. Highguard, by contrast, entered the arena shooter space, a significantly smaller market with different competitive expectations.

Changed industry conditions - Apex Legends launched in February 2019. The battle royale market was still ascending. Players were hungry for new BR experiences. By 2025, that hunger has been satiated by six years of iterations, refinements, and alternatives. The market maturity is completely different.

Player expectations have evolved - Gaming audiences in 2025 expect free-to-play games to offer more than mechanics alone. They expect cosmetics, seasonal content, esports integration, and community management from day one. Launching with solid gameplay isn't enough anymore.

Reputation and team talent matter less than product execution - Game development is ultimately about the final product. A team of brilliant developers can make a mediocre game if the creative direction is unclear, the design philosophy is muddled, or the execution falls short. Conversely, a team of less-celebrated developers can create viral hits if they nail the core experience.

Wildlight's team had the skills to make Highguard. They clearly had the talent to code it competently, design arenas thoughtfully, and balance abilities mathematically. What they might have lacked was either a genuinely fresh take on arena combat, a compelling monetization strategy, or the community management to keep players engaged during the critical launch window.

DID YOU KNOW: Apex Legends launched with just three playable characters and a single battle pass season. It succeeded because the core game was exceptional, and Respawn had the resources and reputation to support it. Most new games don't get that luxury.

Key Lessons for Game Publishers and Investors
Key Lessons for Game Publishers and Investors

Retention targets and player surveys are critical, with high impact ratings of 9 and 8 respectively. Estimated data highlights the importance of these lessons for future game development investments.

The Competitive Multiplayer Landscape in 2025

Understanding Highguard's failure requires understanding the state of competitive multiplayer gaming in 2025.

The space is currently dominated by a handful of titles that have proven staying power:

Counter-Strike 2 - The latest iteration of a 25-year-old franchise, featuring essentially unchanged core mechanics. The community is massive, the esports ecosystem is mature, and the game has zero cost of entry (plus cosmetics for revenue). Any new tactical shooter faces an uphill battle competing against this institutional advantage.

Valorant - Riot Games' tactical hero shooter successfully merged Counter-Strike-style gameplay with ability-based mechanics. With a massive player base, sponsorship infrastructure, and regular seasonal updates, Valorant has essentially locked down a significant chunk of competitive players.

Overwatch 2 - Blizzard's team-based hero shooter maintains a dedicated following despite numerous balance controversies. The franchise recognition, cosmetic investment, and esports integration create significant switching costs for players.

Halo Infinite - While struggling compared to earlier iterations, Halo maintains a core audience due to franchise loyalty and Xbox integration.

Team Fortress 2 - A 17-year-old game that still pulls respectable concurrent numbers, proving that older titles can maintain communities if they're fun and update regularly.

The common thread: all these games have either franchise recognition, massive corporate backing, or both. They've built communities over years. They release content regularly. They host esports events. They've created switching costs through cosmetic investments.

Highguard entered this landscape with:

  • No franchise recognition
  • Relatively modest backing compared to AAA publishers
  • No esports infrastructure
  • An undefined seasonal content pipeline
  • No meaningful differentiation in core mechanics

That's an incredibly difficult position to succeed from. Most games in this situation fail. Highguard simply failed faster and more publicly than usual.

QUICK TIP: If you're launching a competitive multiplayer game in 2025, you need either franchise recognition, an exceptionally unique mechanic, or massive corporate resources. Ideally, all three.

Economic Realities: The Cost of Game Development

Understanding why Wildlight laid off most of its team requires understanding the brutal economics of game development.

According to industry estimates, a mid-sized multiplayer game costs between 30 million and 100 million dollars to develop over 3-4 years. The budget covers:

  • Salary costs - The largest line item. A 100-person studio with average
    120,000annualsalaryis120,000 annual salary is
    12 million per year, or $36 million for a three-year development cycle.
  • Server infrastructure - Hosting, database management, CDN costs, and redundancy can run
    500,000to500,000 to
    2 million monthly depending on scale.
  • Tools and middleware - Game engines, middleware licenses, development tools, and software subscriptions.
  • Marketing - Promotional costs, esports sponsorships, influencer partnerships, and convention attendance.
  • QA and testing - Dedicated quality assurance staff.
  • Office and overhead - Real estate, utilities, equipment, benefits.

For a mid-sized studio, total operational costs can easily exceed $4-5 million monthly once you factor in all these elements.

Now consider Highguard's revenue model. It's free-to-play with cosmetics. Industry benchmarks suggest that 2-5% of active players spend money, with average spending of $20-50 per paying player annually.

Let's do the math:

With 100,000 concurrent players and assuming a 10:1 ratio of concurrent to daily active users (conservative estimate for a new game), that's roughly 1 million daily active users. If 3% spend money averaging

30annually,thats30,000players×30 annually, that's 30,000 players ×
30 = $900,000 per year in total revenue.

At 3,000 concurrent players and using the same math, daily active users drop to 30,000. Revenue drops to 900 ×

30=30 =
27,000 per year.

Monthly operational costs of

45millionagainstannualrevenueoflessthan4-5 million against annual revenue of less than
30,000? The studio is losing roughly $4.5 million monthly. In that context, massive layoffs aren't just reasonable, they're the only rational response.

Without a path to 100,000+ concurrent players, the game was doomed from a financial perspective.

Concurrent vs. Daily Active Users: Concurrent players represent the number of people playing simultaneously at any given moment. Daily active users (DAU) represent the total number of unique players in a 24-hour period. For online games, the DAU-to-concurrent ratio typically ranges from 5:1 to 15:1 depending on time zones and play patterns.

The Game Awards Announcement Problem

Wildlight chose to announce Highguard at The Game Awards, one of the most prestigious gaming events of the year. This was a strategic decision with significant implications.

The Game Awards reaches millions of viewers. Being selected as a "one more thing" moment means major visibility. The event positions games as culturally significant, often flagship experiences that define the year's gaming landscape.

Here's the problem: The Game Awards audience came expecting major announcements. Previous years have featured exclusive trailers for Elden Ring DLC, new entries in established franchises, and occasionally surprising indie darlings. The bar for a "one more thing" moment is high.

Wildlight essentially burned an enormous marketing opportunity by announcing a game that didn't meet audience expectations. The muted response—polite applause rather than excitement—likely depressed day-one sales and media coverage.

Contrast this with how Palworld announced itself through normal channels in 2024 and went viral organically, or how Helldivers 2 launched quietly and built community momentum gradually.

Not every game needs a massive stage announcement. Sometimes, strategic quiet launches with organic community growth work better. Highguard may have benefited from launching with less fanfare and allowing the game to prove itself gradually.

The announcement choice contributed to the expectation mismatch. Players tuned in expecting something revolutionary or at least genuinely surprising. They got a competent-looking arena shooter. That gap between expectation and reality likely influenced initial reviews and player retention.

DID YOU KNOW: Games announced at major events like The Game Awards actually perform worse on average than games that launch with minimal announcement and build community organically. The expectation bar gets set impossibly high.

The Game Awards Announcement Problem - visual representation
The Game Awards Announcement Problem - visual representation

Team Composition Post-Layoff at Wildlight
Team Composition Post-Layoff at Wildlight

Estimated data showing that approximately 85% of the team was laid off, leaving a skeleton crew of about 15% to maintain essential operations.

Server Costs and Infrastructure Drain

One factor people often overlook when discussing game shutdowns: server infrastructure costs continue regardless of player count.

Wildlight built server infrastructure capable of supporting hundreds of thousands of concurrent players. This infrastructure includes:

  • Matchmaking servers - Critical for finding opponents quickly
  • Game servers - Running actual matches across multiple regions
  • Database servers - Tracking player progression, cosmetics, and account data
  • Content delivery networks - Distributing patches, cosmetics, and updates globally
  • Backup and redundancy - Ensuring service continuity if primary systems fail

The cost to run this infrastructure at full capacity might be

12millionmonthly.Thecosttomaintainitat3,000concurrentplayersdropstomaybe1-2 million monthly. The cost to maintain it at 3,000 concurrent players drops to maybe
100,000 monthly (you can compress much of the infrastructure), but that's still a significant burn rate.

With virtually no revenue, every day the servers stay live costs the studio money. The layoff decision becomes even more urgent when you understand that server costs themselves make the game financially unsustainable.

This explains why many shut-down games happen so quickly. Once it becomes clear player engagement won't recover, keeping servers running is pure red ink.

QUICK TIP: When evaluating whether a live service game has a future, divide projected monthly revenue by monthly operational costs (including server infrastructure). If the ratio is below 1.0, the game is on borrowed time.

Player Retention and the First Two Weeks Problem

The multiplayer gaming industry has learned something crucial over the past 15 years: the first two weeks determine everything.

Retention curves in online games typically show steep drops in days 1-7. Games that lose 90% of their launch day players in the first two weeks rarely recover. The pattern is so consistent that industry professionals can almost predict a game's long-term viability within 14 days of launch.

Highguard's trajectory followed this pattern but more severely. Dropping from 100,000 to 3,000 concurrent in roughly two weeks isn't unusual by retention curve standards (it's a 97% drop, similar to many failed launches), but it's catastrophic given Wildlight's business model.

Why does this two-week window matter so much?

Algorithmic promotion - Many games rely on platform algorithms (Steam, Epic, console store fronts) to maintain visibility. When a game's player count drops, it loses algorithmic visibility. New players are less likely to discover it. The game fades into obscurity.

Content creator coverage - Streamers and YouTube content creators move on to the next new game. The momentum dies.

Patch cycles - Most games plan balance patches for weeks 2-3 of launch. If the player base has already evaporated, those patches come too late.

Player expectation setting - Early reviews and community perception calcify quickly. If the initial consensus is "mediocre," it's nearly impossible to overcome.

Wildlight likely understood this dynamic. The layoff decision probably came after analyzing retention analytics and realizing that the two-week window had closed with insufficient players remaining to justify continued development investment.

This is a tough lesson for new studios: launch window execution is everything. It's not just about content or balance. It's about creating an experience compelling enough that players stick around during those critical first 14 days. Miss that window, and recovery is essentially impossible.

Player Retention and the First Two Weeks Problem - visual representation
Player Retention and the First Two Weeks Problem - visual representation

What Wildlight Could Have Done Differently

Criticism after failure is easy, but it's worth examining what strategic choices might have changed the outcome.

Differentiation in mechanics - Most arena shooters play similarly: spawn, grab weapons, engage in combat. Highguard didn't introduce genuinely novel mechanics that justified trying it over established competitors. What if Wildlight had created something mechanically unique—a novel movement system, an innovative economy for power-ups, or creative ability combinations that no competitor offered?

Community management pre-launch - Strong community builders can create passionate fanbases before launch. Games like Rust and Valheim succeeded partly because they cultivated engaged communities during early access. Wildlight could have started this process earlier.

Early access launch - Instead of a full launch announcement at The Game Awards, Wildlight could have released an early access version months earlier, gathered community feedback, and iterated before full launch. This extends the runway for player discovery and provides time for word-of-mouth marketing.

Lower cost development - If Wildlight had scoped more modestly—fewer maps, fewer cosmetics, leaner server infrastructure—the operational burn rate would have been lower. They could have survived longer while building the player base.

Strategic partnerships - Partnering with a larger publisher or platform holder might have provided larger marketing budgets or distribution advantages.

Content strategy - Having a detailed 12-month roadmap of maps, characters, cosmetics, and seasonal content planned before launch creates player confidence. Players invest more heavily in games where they know what's coming.

None of these changes guarantee success. The competitive landscape is brutal. But each might have extended the runway or increased retention sufficiently to avoid the catastrophic player drop.

QUICK TIP: Before launching a multiplayer game, have at least 12 months of content planned. Players commit longer when they see a clear future for the game.

Annual Game Developer Layoffs
Annual Game Developer Layoffs

The gaming industry has seen a steady increase in layoffs, peaking in 2024 with approximately 13,600 job losses. Estimated data highlights the growing challenges in the industry.

The Broader Industry Pattern: Why Game Layoffs Are Accelerating

Wildlight's situation isn't unique. The gaming industry has seen accelerating layoffs since 2023, with thousands of developers affected annually.

The pattern reflects several converging problems:

Project failures proportional to budget - As games have become more expensive to develop, the consequences of failure have become more severe. A $100 million game that underperforms requires massive layoffs to stop the financial bleeding.

Market saturation - There are more games competing for player attention than ever. The bar for success has risen. Games that would have been considered successful 10 years ago now fail to achieve minimum viable audiences.

Unrealistic projections - Publishers often greenlight projects based on optimistic financial models. When reality diverges from those projections (as it usually does), the response is immediate and severe.

Live service emphasis - The pivot toward live service models has made player retention the primary metric of success. Unlike traditional games that have one launch and a sales number, live service games must maintain engagement indefinitely. Failure is continuous and measurable in real-time.

Platform consolidation - With fewer major platforms (Steam, Epic, PlayStation, Xbox, mobile), discovery is harder. A small number of major hits get most of the attention. Everything else struggles.

Venture capital withdrawal - Funding for game studios has dried up. Publishers are less willing to take risks on unproven teams or experimental concepts. This creates a conservative landscape where only established franchises get funded.

Wildlight's layoffs are a symptom of these systemic issues, not an anomaly.

DID YOU KNOW: In 2024, approximately 13,600 game developers lost their jobs due to studio closures and layoffs—the highest number since the financial crisis of 2008.

The Broader Industry Pattern: Why Game Layoffs Are Accelerating - visual representation
The Broader Industry Pattern: Why Game Layoffs Are Accelerating - visual representation

Lessons for Game Developers

What can game developers learn from Wildlight's experience?

1. Product market fit is non-negotiable - Talent and resources matter, but if the game doesn't resonate with players, nothing else saves it. Before launch, you need evidence that players actually want what you're building.

2. Launch timing and positioning matter enormously - The Game Awards announcement amplified expectations in a way that Highguard couldn't meet. Strategic communication about your game's positioning shapes player expectations.

3. Retention curves are predictive - You can identify failed launches within 14 days. Build analytics to understand this early, so you can make decisions quickly rather than burning money on a doomed project.

4. Server costs scale better with engaged players - Don't build infrastructure for millions if you can't guarantee the engagement. Start smaller, scale up with success.

5. Community is your distribution channel - Large marketing budgets can't save a game that players don't want to recommend to friends. Community engagement, creator partnerships, and word-of-mouth are the only sustainable growth drivers.

6. Differentiation or excellence required - Launching a competent game in a saturated market is a losing strategy. You need either something genuinely different or execution so exceptional that players prefer you to alternatives.

7. Financial runway must exceed expected burn rate - Calculate your monthly operational costs, project realistic revenue, and ensure you have funding to survive the gap. Most failed launches underestimate burn rates and overestimate revenue.

The Player Perspective: Why Highguard Didn't Stick

From a player's perspective, the decision to move on from Highguard likely involved several factors:

Competence without excitement - The game worked fine. Matchmaking was stable. Servers were responsive. But stable and boring aren't enough to beat Counter-Strike 2, Valorant, or Overwatch 2. Players didn't find anything compelling enough to overcome the switching cost of leaving established communities.

Monetization friction - New players are wary of cosmetic-heavy free-to-play games. If Highguard's battle pass pricing felt steep or cosmetics felt mandatory for competitive viability, players would drift toward alternatives with more generous models.

Content perception - If seasonal content plans weren't clear, or if launch cosmetics felt limited, players might have perceived Highguard as a live service game that didn't have the resources to support a livable roadmap. Perception matters as much as reality.

Community perception - Negative early reviews or streaming communities ("this is just a worse Valorant") create perception mountains that are nearly impossible to overcome. Players make decisions based on community consensus more than personal experience.

Esports potential - Competitive players consider whether a game will develop esports infrastructure. Highguard had no announced esports plans, no partnership with major tournament organizers. Ambitious competitive players gravitated toward games with established professional ecosystems.

The game didn't have a killer differentiator that justified trying it. In a world of endless gaming options, "competent but unremarkable" is a death sentence.

The Player Perspective: Why Highguard Didn't Stick - visual representation
The Player Perspective: Why Highguard Didn't Stick - visual representation

Highguard Financial Trajectory Post-Launch
Highguard Financial Trajectory Post-Launch

The chart illustrates the financial challenges faced by Highguard, with revenue significantly lower than the burn rate, leading to a cumulative loss of $10-20 million by day 60. Estimated data.

The Future of Live Service Games

Highguard's failure raises questions about the viability of live service games in the current market.

Current state: Live service games are increasingly risky for publishers. The development costs are high, the execution bar is high, and the player retention challenges are severe. However, the potential upside (if a game becomes the next Valorant or Apex Legends) is enormous.

This creates a bimodal distribution: Either games are massive successes generating hundreds of millions annually, or they're failures shut down within months. Middle ground is increasingly rare.

Potential future trends:

Consolidation around franchises - Expect more live service games from established franchises (Call of Duty, Destiny, Final Fantasy) and fewer entirely new IPs. Franchise recognition provides built-in audiences.

Increasing costs to compete - As the bar rises, minimum viable budgets for competitive multiplayer games will increase. Small independent studios will largely exit this space.

Longer early access windows - Expect more games to launch in early access, gathering feedback and building communities before "official" launch. This extends runways and allows iteration based on real player data.

Niche specialization - Games that dominate specific niches (tactical shooters, hero shooters, battle royales) will thrive. Games trying to be "all things to all players" will struggle.

Emergence of alternative business models - Expect continued experimentation with cosmetic-free monetization, battle pass alternatives, and subscription-based access. Some successful games will break the cosmetic-heavy model.

China market dominance - Chinese gaming audiences have different preferences and are often more willing to spend on cosmetics. Expect more games designed specifically for Chinese market preferences.

Wildlight's situation might eventually be seen as a cautionary tale that accelerated the industry's shift toward more conservative development approaches and established franchises.

QUICK TIP: If you're considering joining a live service game studio, research the game's financial models and publisher support. Many promising projects get shut down when they fail to hit engagement targets.

Wildlight Entertainment's Path Forward

So what happens to Wildlight Entertainment now?

With a skeleton crew, the studio likely has a few options:

Maintenance mode indefinitely - Keep the servers running, apply critical updates, hope that a content creator or esports organization surprises everyone by adopting the game. This is the current stated position.

Strategic pivot - Some of Wildlight's developers might be reassigned to other publisher projects. This would essentially be winding down Highguard while salvaging team assets for other work.

Acquisition - A larger publisher might acquire Wildlight at a fraction of the studio's worth, folding the team into existing projects. This has happened to other failed studios.

Complete shutdown - If server costs become prohibitive and no sustainable revenue materializes, Wildlight might eventually shut down Highguard completely and either dissolve or pivot to contract development work.

The most likely scenario? Maintenance mode continues for 6-12 months while the core team looks for new projects. Eventually, server costs become the deciding factor, and the game shuts down. That's the standard pattern in the industry.

For the developers at Wildlight who weren't affected by layoffs, the situation is demoralizing. You shipped a game. You made design decisions, shipped code, created art, managed servers. And within weeks, the entire project is in emergency mode.

That's the modern game industry in a nutshell.

Wildlight Entertainment's Path Forward - visual representation
Wildlight Entertainment's Path Forward - visual representation

What This Means for the Broader Gaming Landscape

Wildlight's situation has ripple effects beyond one studio and one game.

For publishers - More risk aversion. Games that don't demonstrate clear differentiation or existing audience appeal get green-lit less frequently. Safe franchises and proven formulas get prioritized.

For developers - Increased uncertainty around job security. Even shipped games don't guarantee employment. Developers will increasingly demand clear communication about financial runway and success metrics before joining projects.

For investors - Game development is already risky. Failures like Highguard underscore that pedigree and talent don't guarantee returns. Expect continued capital withdrawal from game studios.

For players - Fewer genuinely new game experiences. More focus on established franchises and safe bets. The next generation of breakthrough games might take longer to emerge because fewer studios are willing to take creative risks.

For esports - The failure of Highguard to establish an esports ecosystem early highlights the importance of platform owner commitment to esports viability. Games without esports support from publishers or tournament organizers struggle.

The gaming industry is consolidating and becoming more conservative. Wildlight's failure accelerates these trends.

DID YOU KNOW: The most successful new multiplayer game franchises launched in the past 10 years (Valorant, Apex Legends, Fortnite, PUBG) were all either backed by major publishers or massive venture capital. Truly independent multiplayer successes are increasingly rare.

Alternative Outcomes: Games That Recovered

It's worth noting that recovery is possible, though increasingly rare.

No Man's Sky - Launched to massive criticism in 2016, then steadily improved through free updates over five years. The 2024 release of the Worlds update brought renewed player interest. This recovery took enormous patience and sustained investment.

Final Fantasy XIV - Launched poorly in 2010, then completely rebuilt (A Realm Reborn in 2013) under new leadership. The game has since become a major franchise.

Rainbow Six Siege - Had a slow launch in 2015 but became a massive esports hit through publisher commitment and continuous content updates. Year 1 was rough, but Ubisoft sustained investment.

These recoveries share common factors:

  • Major publisher backing - These companies had resources to survive sustained losses
  • Clear redemption plan - Leadership understood what needed to change
  • Multi-year commitment - Recovery wasn't expected within months
  • Franchise potential - Each had underlying IP or mechanics worth saving

Without these factors, recovery is essentially impossible. Wildlight has skeleton crew resources, a new IP with no franchise weight, and no clear path to scaling player engagement. Recovery seems unlikely.

Alternative Outcomes: Games That Recovered - visual representation
Alternative Outcomes: Games That Recovered - visual representation

The Economics of Failure: Running the Numbers

Let's do a detailed financial analysis of why the Highguard layoffs were inevitable.

Development costs - Likely $40-80 million based on team size (100+ people over 3-4 years) and game scope.

Launch month revenue - Estimated at

15millionbasedoncosmeticspending(31-5 million based on cosmetic spending (3% monetization rate,
30 average spend, 100,000 to 500,000 daily actives).

Launch month burn rate - Estimated at $5-8 million based on:

  • Salary costs: ~$1 million monthly (100 staff)
  • Server infrastructure: $0.5-1 million monthly
  • Support and infrastructure: $0.5 million monthly
  • Other overhead: $1-2 million monthly

Month 2 revenue - Estimated at $0.2-1 million (player count dropped 97%)

Month 2 burn rate - Still $3-5 million (can't immediately reduce all costs)

Cumulative loss - By day 60 of launch: $10-20 million

This is unsustainable. The layoff decision becomes financially necessary, not optional. By reducing the team to 10-15 people, monthly burn drops to $0.5-1 million, making the game viable as a long-term maintenance project.

These aren't wild guesses. They're based on industry standard costs and publicly available data about multiplayer game economics.

Lessons for Publishers and Investors

Wildlight's failure provides several lessons for companies funding game development:

1. Player surveys during development matter - If target audience feedback during closed alpha/beta suggested tepid interest, that's a warning signal. Launching anyway is optimization for sunk costs rather than future viability.

2. Retention targets must be conservative - If projections assumed 50% of launch day players would return, that's fantasy. Actual retention for new multiplayer games averages 5-15% after two weeks. Build financial models around 5%.

3. Differentiation must be clear pre-launch - If marketing messaging struggles to articulate why players should try this game over competitors, the game likely has insufficient differentiation. That's worth investigating before launch.

4. Esports viability should be baked into greenlight - If a competitive multiplayer game doesn't have esports partnerships or plans secured before launch, it's already behind.

5. Regional release strategy matters - Launching globally at once is risky. Staggered regional launches allow learning from early adopters and adjusting strategy.

6. Team autonomy during crises saves money - Studios that can make rapid decisions about content priorities and operational costs during downturns survive longer. Bureaucratic approval chains kill failing games faster.

Publishers funding the next Highguard should incorporate these lessons into their risk management frameworks.

Sunk Costs Fallacy: The tendency to continue investing in a project because of previously invested resources, even when continued investment is financially irrational. Many failing games continue receiving investment due to sunk costs rather than realistic path to recovery.

Lessons for Publishers and Investors - visual representation
Lessons for Publishers and Investors - visual representation

The Human Cost of Game Development Failure

Amidst the financial analysis, it's important to acknowledge the human impact.

The developers laid off from Wildlight lost their jobs. The level designers, programmers, artists, and support staff who shipped a game weeks ago are now job hunting in a contracting industry.

Game development is already grueling: 60-80 hour weeks, creative pressure, technical challenges, and the knowledge that your game might never ship or might fail after shipping.

When a game launches and fails, developers experience compounded failure. They devoted years of their lives to a project that didn't resonate. They worked through crunch periods, sacrificed personal time, and believed in the vision. Then, they're laid off.

This burnout cycle is one reason many talented developers are leaving the industry for more stable fields like web development or AI.

For anyone in game development: Highguard's failure isn't a reflection of developer skill or effort. It's a market outcome. The team likely executed well. The problem was fundamental misalignment between the game developed and what players wanted, combined with brutal economic math.

The lesson isn't that developers failed. It's that the industry's business models and project greenlight processes need restructuring to provide better job security and more realistic success criteria.

DID YOU KNOW: Average tenure for game developers is declining. As of 2024, approximately 45% of game developers expect to leave the industry within 5 years, with job insecurity and poor work-life balance as primary reasons.

FAQ

What exactly is Highguard and how did the studio develop it?

Highguard is a free-to-play arena shooter developed by Wildlight Entertainment, a studio founded by developers who previously worked on Apex Legends and Titanfall at Respawn Entertainment. The game was announced at The Game Awards in December 2024 and launched at the end of January 2025. It's designed as a competitive multiplayer title focusing on skill-based combat in contained arena environments, similar to games like Unreal Tournament or Quake but with modern sensibilities.

How severe were the player count drops after launch?

Highguard experienced a catastrophic player retention failure. The game launched with approximately 100,000 concurrent players on Steam but dropped to under 3,000 concurrent players within approximately two weeks. This represents a 97% decline in player engagement in roughly 14 days—an exceptionally rapid collapse even by live service game standards. This dramatic drop is what triggered the emergency layoffs announced by level designer Alex Graner on Linked In.

What is a "skeleton crew" in game development terms?

A skeleton crew refers to a minimal team maintained to handle essential operations while a project winds down or transitions to maintenance mode. In Wildlight's case, the skeleton crew is likely 10-15 developers responsible for critical bug fixes, server uptime, security updates, and basic customer support. A skeleton crew typically cannot develop new features, create new cosmetics, design new maps, or build seasonal content—functions that require larger teams. This is essentially life support for the game rather than active development.

Why do live service games fail so quickly sometimes?

Live service games depend on sustained player engagement and monetization. Unlike traditional games that generate one-time purchase revenue, live service games must maintain ongoing player populations to justify continuous server costs, development team salaries, and content creation. When player counts drop below sustainable thresholds (typically 50,000+ concurrent for profitability), the business model collapses. With 97% player attrition, Highguard fell below economically viable levels within weeks, making layoffs financially necessary to stop ongoing losses.

Was the Game Awards announcement a mistake for Highguard?

The Game Awards announcement likely created inflated expectations that Highguard couldn't meet. The show positions games as culturally significant and revolutionary experiences. Players expecting a breakthrough multiplayer game instead received a competent but unremarkable arena shooter in a saturated market. The gap between expectation (set by the prestigious announcement platform) and reality (a solid but unexceptional game) likely depressed both critical reception and player retention. Some games succeed better with quiet launches allowing organic discovery rather than major stage announcements.

What were the key differences between Highguard and successful competitors?

Highguard lacked the differentiation necessary to compete in the crowded multiplayer space. Counter-Strike 2 has 25 years of franchise legacy and a massive esports ecosystem. Valorant features unique ability mechanics and Riot's massive resources. Overwatch 2 has franchise recognition and established esports infrastructure. Halo maintains brand loyalty. Highguard offered solid gameplay but no compelling reason to play it instead of these alternatives. In multiplayer gaming, "competent but unremarkable" is a death sentence when competition is fierce and switching costs are high (cosmetic investments, ranked progress, established friend groups).

How much revenue would Highguard have needed to justify keeping the full team?

Based on typical game development costs, Wildlight's full team (likely 100+ developers) probably cost

46millionmonthlyinsalariesalone,withadditionalserverinfrastructure,marketing,andoverheadcostsbringingthetotalto4-6 million monthly in salaries alone, with additional server infrastructure, marketing, and overhead costs bringing the total to
6-8 million monthly burn rate. To justify this burn with cosmetic-based monetization, the game would have needed approximately 500,000+ daily active users at standard monetization rates (
2030averagerevenueperuserannually).Withonly3,000concurrentplayers,thegamelikelygeneratedunder20-30 average revenue per user annually). With only 3,000 concurrent players, the game likely generated under
50,000 monthly revenue against $6-8 million monthly costs, making layoffs immediately necessary.

Could Highguard potentially recover and become successful again?

Recovery is theoretically possible but practically unlikely without significant changes. Historical game recoveries (No Man's Sky, Final Fantasy XIV, Rainbow Six Siege) all required: major publisher backing, multi-year commitment to improvements, clear understanding of what failed, and underlying IP with franchise potential. Highguard has none of these factors. With a skeleton crew and no clear differentiator, recovery would require either a creative breakthrough (fundamentally redesigning core gameplay) or a massive player community spontaneously deciding to return. Neither seems probable given the initial response.

What financial calculations determined the layoff decision?

The core calculation is simple: monthly operational costs exceed monthly revenue by a factor of 100+. With

68millionmonthlyburnandperhaps6-8 million monthly burn and perhaps
50,000 in monthly revenue, the game loses
67.95millionmonthly.Thelayoffreducesburntoapproximately6-7.95 million monthly. The layoff reduces burn to approximately
500,000-1,000,000 monthly (skeleton crew), creating a viable long-term maintenance scenario. Wildlight likely calculated that 2-3 months of continued full-team development would burn through all remaining funding without meaningfully improving player retention, making immediate cost reduction the only rational choice.

How does Highguard's failure compare to other recent game studio collapses?

Highguard's timeline is actually faster than many failed launches. Some games maintain moderate player bases for 6-12 months before shutting down. Highguard went from 100,000 players to "time to lay off most of the team" in roughly three weeks. However, the underlying pattern—massive initial numbers followed by catastrophic retention failure—is increasingly common. The gaming industry has seen accelerating layoffs since 2023, with thousands of developers affected annually. Highguard is symptomatic of systemic issues: unrealistic financial projections, market saturation, conservative player bases, and live service model fragility.


FAQ - visual representation
FAQ - visual representation

Conclusion: What Highguard's Failure Teaches Us

Wildlight Entertainment's decision to lay off most of its team weeks after Highguard's launch isn't a unique story—it's becoming the industry standard.

The factors that killed Highguard are largely out of any single studio's control. The competitive multiplayer market is saturated with better-funded alternatives. Player expectations have increased while player loyalty has decreased. Live service economics are unforgiving. Marketing buzz doesn't translate to sustained engagement.

But there are also controllable factors that might have changed the outcome. Different positioning, earlier community building, more modest scoping, clearer content roadmaps, and esports infrastructure all could have extended the runway.

The larger lesson is structural: the gaming industry's approach to funding and developing live service games is fundamentally misaligned with modern market realities. Publishers greenlight expensive projects based on optimistic projections. Players have limited attention and increasing skepticism of new entries in saturated genres. The first two weeks of player retention are predictive of long-term viability, leaving no margin for error.

Wildlight had pedigree, talent, and resources. None of it mattered. Their game failed because it didn't captivate players in a market where captivation is the only path to success.

For developers, publishers, and investors: Highguard is a cautionary tale. The cost of failure in game development is rising. The bar for success is rising faster. Project viability should be validated with real player feedback before major greenlight decisions, not after hundreds of millions have been spent.

For players: the gaming industry is consolidating around fewer, safer franchises. Fewer genuinely new multiplayer experiences will be attempted. The industry is becoming more conservative as a direct result of failures like Highguard.

Wildlight Entertainment will likely keep Highguard in maintenance mode for a few more months before eventually shutting down servers. The studio might pivot to contract development work or seek acquisition by a larger publisher. Some of the talented developers will find new projects. Others will leave the industry.

The game they created is actually competent. It works. It's fun. But in modern gaming, competent and fun aren't enough. You need differentiation, luck, timing, and resources aligned perfectly.

Wildlight had three out of four. In an industry where perfection is increasingly required just to break even, that's just not sufficient.

The real question isn't why Highguard failed. It's how many more games will follow before the industry restructures how it funds and greenlights multiplayer projects. Until that changes, we'll keep seeing talented teams and promising projects collapse into skeleton crews and shutdown timelines.

That's the actual tragedy of Highguard's story—not that one game failed, but that the industry's fundamental economics make failure increasingly inevitable for anything lacking massive publisher backing or pre-existing franchise recognition.


Key Takeaways

  • Highguard lost 97% of its player base in roughly two weeks after launch, dropping from 100,000 to under 3,000 concurrent players on Steam
  • Live service game economics are brutal: operational costs of
    68millionmonthlycannotbesustainedwithrevenueunder6-8 million monthly cannot be sustained with revenue under
    100,000 monthly
  • Layoffs weeks after launch are increasingly common as the industry becomes more conservative and market saturation grows
  • Player retention in the first 14 days determines a game's viability—games that miss this window rarely recover
  • Competitive multiplayer requires either franchise recognition, exceptional differentiation, or massive publisher backing to survive in 2025

Related Articles

Cut Costs with Runable

Cost savings are based on average monthly price per user for each app.

Which apps do you use?

Apps to replace

ChatGPTChatGPT
$20 / month
LovableLovable
$25 / month
Gamma AIGamma AI
$25 / month
HiggsFieldHiggsField
$49 / month
Leonardo AILeonardo AI
$12 / month
TOTAL$131 / month

Runable price = $9 / month

Saves $122 / month

Runable can save upto $1464 per year compared to the non-enterprise price of your apps.