How do I handle a bad build of my game?

Handle a bad build by confirming it is bad, stopping the damage, and fixing the underlying problem before re-releasing. Step one, confirm: check whether crashes are spiking and whether they started with this release, so you verify the build is the cause and take the right action (rather than rolling back unnecessarily or to a build with its own problems). Step two, stop the damage fast: roll back to a known-good build if a fix will take time, or ship a fast fix if you can do so quickly, the priority is to stop players from hitting the bad build, since it hurts players every minute it is live. Step three, fix the underlying problem and re-release: fix the root cause properly, verify the fix, and re-release with confidence the build is now good. Speed matters because a bad build does continuous damage, so stop the bleeding first (via rollback or quick fix), then fix properly. Bugnet supports it: per-version tracking confirms the build is the cause and identifies a known-good build to roll back to, the crash context helps you fix the problem, and per-version verification confirms the fix before re-release, so you handle the bad build fast and correctly, which is how you handle a bad build of your game.

What do I do if I released a broken update?

If you released a broken update, act fast: confirm it is the problem, stop the damage by rolling back to a known-good build (or shipping a quick fix), then fix the underlying issue and re-release once verified. The urgency is high because a broken update hurts players continuously, every minute it is live, more players hit the problem and more bad reviews accumulate, so the immediate priority is to stop the bleeding, not to perfect a fix. Concretely: confirm the update is the cause (the crashes or issues started with it, via per-version data), then take the fastest action to stop players hitting it, usually rolling back to the previous known-good build (which immediately restores a working experience while you fix forward), or shipping a fast hotfix if you can do so quickly and safely. Then fix the underlying problem properly, verify it, and re-release. Communicate with players if the impact was significant. Bugnet helps at each step: per-version tracking confirms the update is the cause and identifies a known-good build to roll back to, the crash context helps you fix the issue, and per-version verification confirms the fix before re-release, so you recover from a broken update fast, which is what to do if you released a broken update.

Should I roll back or fix forward a bad build?

Choose between rolling back and fixing forward a bad build based on how fast you can safely fix it versus how much damage the build is doing: roll back when the problem is serious and widespread and a proper fix will take time (rollback stops the damage immediately), and fix forward when you can fix it quickly or rolling back would itself cause problems. Roll back when: the bad build is causing serious, widespread harm (a crash spike, a game-breaking issue), a proper fix will take meaningful time, and you have a known-good build to revert to, rollback halts the damage now while you fix forward calmly. Fix forward when: the issue is narrow or less severe, you can fix and ship it quickly, or rolling back would lose something (new content, save compatibility). Often the best approach is both: roll back to stop the bleeding immediately, then fix forward properly and re-release. The decision needs data on the build's impact and a known-good build to revert to. Bugnet provides both: it shows the bad build's impact and confirms it as the cause (so you gauge severity), and identifies a known-good build to roll back to (via per-version data), plus verifies your forward fix, helping you decide and execute either path, which is how to choose between rolling back and fixing forward a bad build.

Steps to Handle a Bad Build

Quick answer: To handle a bad build: confirm it is bad (crashes tied to the release), stop the damage (roll back or fast fix), and fix the underlying problem before re-releasing.

A bad build is hurting players right now, so speed matters. These are the steps to handle one.

Step 1: Confirm the Build Is Bad

Start by confirming the build is actually bad and that it is the cause: check whether crashes are spiking and whether they started with this release. Confirming the build is the culprit (rather than an unrelated issue) ensures you take the right action and do not roll back unnecessarily.

Bugnet confirms it with per-version tracking: it shows whether the crash spike started in this build, so you can verify the bad build is the cause before acting, basing your response on data rather than assumption.

Step 2: Stop the Damage

Next, stop the damage fast: roll back to a known-good build if a fix will take time, or ship a fast fix if you can do so quickly. The priority is to stop players from hitting the bad build, since it hurts players every minute it is live, so take the fastest safe action to halt the bleeding.

Bugnet helps you choose and execute: its per-version data identifies a known-good build to roll back to, and the crash context helps you make a fast fix if that is the better path, so you can stop the damage by the fastest safe route, informed by what the data shows.

Step 3: Fix the Underlying Problem and Re-Release

Finally, fix the underlying problem that made the build bad, and verify the fix before re-releasing. Stopping the damage (via rollback or a quick fix) is the immediate action; fixing the root cause properly and confirming it before re-releasing prevents a repeat, closing out the bad build correctly.

Bugnet supports the fix and re-release: the crash context helps you fix the underlying problem, and per-version tracking confirms the fix works (the crash stops) before you re-release, so you re-release with confidence the build is now good rather than risking a second bad build.

To handle a bad build: confirm it is the cause (crashes tied to the release), stop the damage fast (roll back to a known-good build or ship a quick fix), and fix the underlying problem before re-releasing, speed matters since it hurts players every minute.