Quick answer: You likely have a soft-lock problem if players get stuck unable to progress while the game keeps running. The way to confirm it rather than guess is to add stuck-state detection and an in-game report button, since crash telemetry won't catch it. That means capturing failures automatically with their stack trace, device, build, and breadcrumbs, then grouping identical ones so the pattern is obvious. A hunch becomes a fact the moment you look at real, ranked data instead of the handful of reports that happen to reach you.
“Do I have a soft-lock problem?” is a question you cannot answer honestly from your own machine, because the symptom — players get stuck unable to progress while the game keeps running — is exactly the kind of thing that hides from the developer. It runs fine for you, your inbox is quiet, and the absence of complaints feels like the absence of a problem. It usually is not. This guide covers the real signs of a soft-lock problem and how to confirm it with data instead of a hunch: add stuck-state detection and an in-game report button, since crash telemetry won't catch it.
The signs of a soft-lock problem
The clearest sign of a soft-lock problem is straightforward: players get stuck unable to progress while the game keeps running. The trouble is that this rarely reaches you as a clear signal. Most players who hit it never report it — they just leave — so a quiet inbox tells you nothing about whether the problem exists. The worse the problem, the quieter it often is.
That is why a hunch is not enough here. You need to look at what is actually happening to real players, not at the small, biased sample that bothers to complain. The good news is that confirming a soft-lock problem is entirely doable once you are working from real data.
The silent majority who never report anything
For every player who files a report, a large number simply hit the problem, sigh, and close the game. They do not owe you a bug report, and most will not write one. The failures that churn the most players are therefore the ones least likely to ever reach your inbox, which is a deeply unfair feedback loop: the worse the bug, the quieter it tends to be.
The only way out of that loop is to stop depending on goodwill. When every crash is recorded automatically, the silent majority become data. You finally see the failure that is quietly costing you installs, ranked by how often it actually happens rather than by who happened to be patient enough to complain.
Why “it works on my machine” is a trap
Your development machine is the single least representative device your game will ever run on. It is the one configuration guaranteed to work, because you built and tested the game on it. Your players live out on the long tail of GPUs, drivers, operating-system versions, resolutions, and background software, and that long tail is exactly where the failures you never reproduce are hiding.
This is why local testing, however thorough, has a hard ceiling. You cannot own every device, and you cannot imagine every combination. Field data closes that gap by letting the failures come to you with the configuration attached, so a crash that only happens on one driver version stops being a mystery and becomes a one-line filter.
Connecting failures to the build that caused them
Regressions are the cruelest class of bug because they punish your most engaged players — the ones who already own the game and updated to your newest patch. A change meant to improve things quietly breaks something else, and without build-level tracking you have no way to link the dip in retention to the release that caused it.
The fix is to attach a build identifier to every captured failure. Then a new signature that appears the day you ship a patch is unmistakable, and you can roll back or hotfix while only a few players are affected instead of discovering the problem weeks later in your reviews.
How to confirm a soft-lock problem
To know for sure, add stuck-state detection and an in-game report button, since crash telemetry won't catch it. The foundation is automatic capture: every failure recorded with its stack trace, device, build, and breadcrumbs, whether or not the player says anything. With that in place, a soft-lock problem stops being a worry and becomes a measurement — you can see how many players are affected and exactly where it happens.
From there it is a fix, not a debate. Group identical failures so the worst case is on top, read the trace and breadcrumbs, fix the root, and tie failures to builds so you can confirm the problem shrinks in the next release. The question “do I have a soft-lock problem?” becomes “how much of it is left?”
This is where a tool like Bugnet earns its place. Its SDK captures every failure automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds identical failures into one grouped issue with an occurrence count, and ties each to the build it happened on. The result is that the abstract idea above stops being theory and becomes a ranked list you work down — the worst problem first, verified fixed when its signature disappears from the next release.
The crashes you never hear about are the ones costing you most. Visibility is what turns them into a list you can actually work down.