What should I do when I find a critical bug?

Assess its scope, fix it fast or roll back, and verify the fix, a critical (game-breaking) bug is top priority because it stops players from playing, so respond with urgency proportional to how many players it affects. A critical bug, one that breaks the game (crashes it, blocks progression, loses progress, makes it unplayable), demands immediate action, but the right response depends on scope. First, assess scope: check your captured data for how many players the bug affects and under what conditions, a bug breaking the game for everyone is a drop-everything emergency (roll back or hotfix immediately), while one affecting a specific segment (a device, a condition) is urgent but more contained (target that segment). Second, act fast: if you can fix the bug quickly (the captured stack trace and conditions point at the cause), hotfix it, if it's widespread and the fix will take time, roll back the release to stop players hitting it while you fix it properly. A critical bug warrants dropping other work, every affected player is blocked. Third, verify: confirm per version that the bug is resolved (its occurrences stopping on the fixed build), since a bug this severe can't be left to assumption, you need to know players can play again. So when you find a critical bug, assess its scope (how many players, what conditions), fix it fast or roll back (based on scope and fix speed), and verify per version. Bugnet captures the bug with context and impact ranking (for scope assessment and the cause), supports fast fixing or rolling back (context and per-version data), and verifies the fix (per-version tracking), so you can respond to a critical bug with the speed and information it demands, resolving it fast and confirming players can play again.

How fast should I fix a game-breaking bug?

As fast as possible, a game-breaking bug is top priority and warrants dropping other work, because every hour it persists is players blocked from playing, churning, and leaving bad reviews. A game-breaking bug, by definition, stops players from playing, crashing the game, blocking progression, losing progress, or rendering it unusable. Unlike a minor bug that players can work around or tolerate, a game-breaking bug gives affected players no recourse, they can't play, so they quit (often angrily) and leave negative reviews. This makes the cost of every hour it persists high: more players hit it, more churn, more bad reviews, more damage to your game's reputation. So the answer is to fix it as fast as possible, treating it as an emergency that warrants dropping other work and prioritizing the fix (or a rollback) above everything else. The exact speed depends on scope (a bug breaking the game for everyone is more urgent than one affecting a narrow segment) and your ability to fix fast, but the priority is maximal. If you can't fix it quickly, roll back to stop the bleeding while you fix it properly, rather than leaving the bug live. The goal is to minimize the window during which players hit the game-breaking bug. So you should fix a game-breaking bug as fast as possible, dropping other work, because its cost per hour (blocked players, churn, bad reviews) is high, and rolling back if needed to stop players hitting it while you fix. Bugnet helps you respond fast by capturing the bug with the context to diagnose it quickly (stack trace, conditions), ranking by impact (so you gauge urgency), supporting a fast rollback (per-version data), and verifying the fix (so you know it's resolved), enabling the rapid response a game-breaking bug demands, which is what limits the damage from a bug that blocks players from playing.

Should I roll back for a game-breaking bug?

Roll back if the bug is widespread and you can't fix it fast; hotfix if you can resolve it quickly, the goal is to stop players hitting the game-breaking bug as fast as possible, by whichever route is faster. For a game-breaking bug, both rolling back and hotfixing aim to stop players hitting it, and you choose based on which gets there faster. Roll back when: the bug is widespread (affecting many or all players), it was introduced by a recent release (so reverting to the previous build removes it), and you can't turn around a fix quickly, rolling back immediately stops players hitting the game-breaking bug by returning them to the working previous version, buying you time to fix it properly without a live game-breaker. Hotfix when: you can identify and fix the bug fast (the captured context points clearly at the cause), so a targeted hotfix resolves it quickly while keeping the current release's other improvements. The decision factors: how widespread the bug is (more widespread favors rolling back for speed), whether a release introduced it (if so, rolling back is clean), and how fast you can fix it (a fast, clear fix favors hotfixing). When in doubt for a widespread game-breaker, rolling back is often the safer, faster way to stop the bleeding, you can fix properly afterward. So you should roll back for a game-breaking bug if it's widespread and you can't fix it fast (stop the bleeding now), and hotfix if you can resolve it quickly, choosing whichever stops players hitting it faster. Bugnet's per-version tracking shows whether a release introduced the bug (making rollback clean) and how widespread it is (informing the choice), and its captured context helps you gauge fix speed (for the hotfix option), so you can decide between rolling back and hotfixing based on data, then verify per version that the game-breaking bug stopped, by whichever route you chose.

What to Do When You Find a Game-Breaking Bug

Quick answer: Assess how many players the bug affects using captured data, fix it fast with a hotfix or roll back if widespread, and verify per version that it's resolved. A game-breaking bug is top priority.

A game-breaking bug, one that stops players from playing, is a top-priority emergency. Fast assessment, decisive action, and verification are what limit the damage. Here is what to do when you find a game-breaking bug.

Assess How Many Players It Affects

First, assess the scope: a game-breaking bug is urgent, but how urgent depends on how many players it hits. Check your captured data for how many players are affected and under what conditions, a bug breaking the game for everyone is a drop-everything emergency, one affecting a narrow segment is urgent but more contained.

Bugnet captures the bug from the field and ranks by affected players, so you immediately see how many players the game-breaking bug hits and the conditions. That scope assessment shapes your response, whether to roll back the whole release (widespread) or hotfix a specific condition (narrower), based on real data rather than panic.

Fix It Fast or Roll Back

Act decisively and fast: if you can fix the bug quickly (the captured context points at the cause), hotfix it, if it's widespread and a fix will take time, roll back the release to stop players hitting it. A game-breaking bug warrants dropping other work, every player hitting it is blocked from playing.

Bugnet's captured context (stack trace, conditions) helps you fix fast, and its per-version tracking lets you roll back the release that introduced the bug. Whether you hotfix or roll back, the captured evidence and per-version data let you act fast and target the right thing, resolving a game-breaking bug quickly rather than scrambling without information.

Verify the Fix Resolved It

Verify per version that the game-breaking bug is actually resolved, the captured occurrences stopping on the fixed build, since a bug this severe can't be left to chance. Confirm in the field that players can play again, rather than assuming the fix worked.

Bugnet tracks the bug per version, so after fixing you can confirm it stopped on the new build and players are no longer blocked. For a bug this critical, this verification is essential, you see the game-breaking bug gone in the field data, confirming players can play again, rather than hoping the high-stakes fix held.

When you find a game-breaking bug, assess how many players it affects, fix it fast or roll back if widespread, and verify per version that it's resolved. A game-breaking bug is top priority because it stops players from playing.