How do I know if my game has a soft-lock?

Look for players stuck with no way out but no crash, the distinctive soft-lock signature. The defining sign is players stuck with no way out but no crash, the game runs fine, but the player is trapped, unable to progress or get back (reports of being 'stuck with no way out' or 'trapped' where the game didn't crash). A sign is players describing being trapped in a state they can't escape (stuck in an area with no exit, a menu they can't leave, a situation with no valid action forward). And a telling sign is complaints about being unable to continue but without an error or crash (the 'no crash but can't continue' description, distinctive of a soft-lock). What distinguishes a soft-lock from a crash or freeze is that the game is running and responsive, the player is just stuck with no valid way forward. To find it, since there's no crash to capture, rely on where players report being stuck (complaints, drop-off at the trapping point) and capture the context (breadcrumbs, state) of those stuck situations to understand how players get trapped. If players report being stuck with no way out and no crash, describe being trapped in a state they can't escape, or complain about being unable to continue without an error, you have a soft-lock. The key is the signature: no crash (the game works), but the player is trapped (no valid way forward or out), which is what makes soft-locks distinctive and, because there's no crash, harder to detect via crash data alone, you find them from where players get stuck (complaints, behavioral data) rather than from errors.

What is a soft-lock in a game?

A soft-lock is when the player gets trapped in a state they can't progress from or escape, without the game crashing, they're stuck, unable to advance or get out, but the game is still running normally otherwise. This distinguishes it from a hard-lock or crash (where the game freezes or terminates): in a soft-lock the game works fine, the player just has no valid way to continue or escape. Examples: getting into an area with no exit, using up a resource needed to progress with no way to get more, an event or quest that can't be completed and can't be reset, a menu or state the player can't leave, or any situation where the only paths forward are unavailable and there's no way back. Soft-locks typically arise from edge cases and unusual sequences, the player did things in an unexpected order or combination that the designer didn't anticipate, leading to a state with no valid exit. They're damaging because, like a progression blocker, they end the player's ability to play meaningfully (the player is stuck, so they quit), but they're also insidious because there's no crash to signal something went wrong, the game just quietly traps the player, so the player may not even realize it's a bug (they might think they're missing something) and you may not see it in crash data. So a soft-lock is a no-crash trapped state: the player is stuck with no valid way forward or out, while the game runs normally, distinct from a crash (game terminates) or freeze (game hangs). It's caused by reaching a state with no valid exit, usually through edge cases and unusual sequences, and it's game-ending for the affected player (they're stuck, so they quit) despite the game technically working. This is why soft-locks are worth preventing (ensure there's always a way out of any reachable state) and detecting (from where players get stuck, since there's no crash), they quietly end players' experiences, and the no-crash nature makes them easy to miss without watching for players getting trapped.

How do I fix a soft-lock?

Find where players get trapped (since there's no crash, use complaints and behavioral data), understand how they reach the no-exit state, and fix it by ensuring there's always a way out, ideally also freeing already-trapped players. First, locate the soft-lock: since there's no crash to capture, rely on where players report being stuck (complaints describing being trapped with no way out and no crash) and behavioral data (players halting or getting stuck at a point), and capture the context (breadcrumbs, state) of those trapped situations. Then understand how players reach the no-exit state: a soft-lock is a state with no valid way forward or out, often reached through an edge case or unusual sequence (the player did something in an order the designer didn't anticipate), so reproduce or reason about how trapped players got into the state (the breadcrumbs showing the sequence help). Then fix it by ensuring there's always a way out: the core fix for a soft-lock is to guarantee that any state the player can reach has a valid exit or path forward, so provide escape/recovery options (a way back, a reset, a recovery path) so the player is never trapped, and avoid creating states with no valid exit. Address the specific edge case or sequence that led to the no-exit state (so players can't reach it, or if they do, can get out). Test the fix, including via the unusual sequences that caused the soft-lock, to confirm players can always escape or progress. Critically, also free already-trapped players: a soft-lock may have trapped players whose saves are in the no-exit state, so your fix should ideally let them out (e.g. detect and resolve the trapped state on load, or provide a recovery option), not just prevent new players from getting stuck, since trapped players are stuck until freed. So you fix a soft-lock by locating where players get trapped (complaints, behavioral data, since there's no crash), understanding how they reach the no-exit state (the edge case/sequence, via breadcrumbs), fixing it by ensuring there's always a way out (escape/recovery options, avoiding no-exit states, handling the edge case), freeing already-trapped players, and testing via the unusual sequences. The key is the principle: a soft-lock is a no-way-out state, so the fix is to ensure there's always a way out of any reachable state (escape paths, recovery options), plus addressing the specific edge case that created the trap, and freeing trapped players. Because soft-locks have no crash, finding them relies on where players get stuck (not crash data), and because they often come from edge cases, fixing them requires handling the unusual sequences and ensuring robust escapability from any state, which prevents players from being quietly trapped with no way to continue.

Signs Your Game Has a Soft-Lock

Quick answer: Watch for players reporting they're stuck with no way out but no crash, players trapped in a state they can't escape, and complaints about being unable to continue without an error. A soft-lock traps the player without crashing.

A soft-lock, the player trapped in a state they can't progress from or escape, without a crash, ends their ability to play just as surely as a game-breaking bug, but quietly. Here are the signs your game has a soft-lock.

Players Stuck With No Way Out but No Crash

The defining sign is players stuck with no way out but no crash, the game runs fine, but the player is trapped, unable to progress or get back. Reports of being 'stuck with no way out' or 'trapped' (where the game didn't crash, it just won't let them continue) point directly at a soft-lock.

Bugnet captures context and breadcrumbs, so the states players get trapped in are identifiable. Players stuck with no way out but no crash is the defining sign of a soft-lock, and since there's no crash, you find it from where players get trapped (the breadcrumbs and state leading to the stuck point), not from a crash report, capturing the context of the trapped state is how you locate the soft-lock.

Players Trapped in a State They Can't Escape

A sign is players describing being trapped in a state they can't escape, stuck in an area with no exit, in a menu they can't leave, in a situation with no valid action forward. A soft-lock is a state with no way out, so descriptions of being unable to escape a situation point at one.

Bugnet captures breadcrumbs, so the sequence leading to the trapped state is identifiable. Players trapped in a state they can't escape is a sign of a soft-lock, and capturing the breadcrumbs (the sequence of actions that led the player into the no-exit state) is how you understand how players get trapped, so you can fix the state to have an exit or prevent players from reaching the no-exit condition.

Complaints About Being Unable to Continue Without an Error

A telling sign is complaints about being unable to continue but without an error or crash, players noting the game didn't crash, it just won't let them proceed. This 'no crash but can't continue' description is distinctive of a soft-lock, distinguishing it from a crash or freeze (the game is running and responsive, the player is just stuck).

Bugnet captures context, so soft-lock situations (no crash, player stuck) are identifiable from the surrounding data. Complaints about being unable to continue without an error are a distinctive sign of a soft-lock (no crash, the game running, the player trapped), and since there's no crash to capture, locating it relies on where players report being stuck and the context of those stuck states, which capturing breadcrumbs and state helps reveal.

Watch for players reporting they're stuck with no way out but no crash, players trapped in a state they can't escape, and complaints about being unable to continue without an error. A soft-lock traps the player without crashing.