What causes a 15-puzzle shuffle generating an unsolvable board?

The board is filled with a random permutation of tiles, but only half of all permutations are solvable, so a plain shuffle frequently produces an impossible configuration.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a 15-Puzzle Shuffle Generating an Unsolvable Board

Quick answer: Either scramble by applying random legal moves from the solved state, or generate a random permutation and check its inversion-parity solvability rule, regenerating if it fails.

Half of all 15-puzzle arrangements cannot be solved. A naive random shuffle lands on an impossible board about 50% of the time. Use a parity check or scramble from the solved state to guarantee solvability.

How to fix it

1. Scramble with random legal moves

Start from the solved board and apply a few hundred random tile-into-gap swaps. Every resulting state is reachable and therefore solvable by construction.

2. Or check inversion parity

For an even-width board, count inversions and the gap's row from the bottom; the puzzle is solvable when their combined parity matches the solved state's. Regenerate if it does not.

3. Avoid leaving it solved

When scrambling by moves, ensure the final state differs from the goal; if a short random walk returns to solved, apply more moves before presenting the board.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every HTML5 error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.