A friend match is now joined by a four-letter code, not a linkA friend match is now joined by a four-letter code, not a link

October 11, 2026 · Dice Lock's player data pointed at six places people quit, and all six got fixed today.Dice Lock's own player data showed exactly where people were giving up, and six of those spots got fixed in one day.
last updated

Dice Lock keeps numbers on where players stop playing, and today those numbers turned into six shipped fixes, all traced to a single walkthrough of the game end to end.

Friend matches were the clearest case. Of 25 rooms created by link, only 12 ever got played: half sat empty because the link had to leave the room through a chat app to reach whoever was supposed to join it. The fix replaces the link with a four-letter code. The host's waiting screen now shows it large, over "Your friend enters this code": upper case, no I, no O, no digits, unique among open rooms. The Play a Friend page offers CREATE ROOM or ENTER A CODE, the entry screen forgives case and spacing, and a mistyped, expired or closed code comes back as a clear error rather than a dead link. A code dies with its room, so nothing is left pointing at a room that no longer exists.

The second fix tackled a different kind of quit. Of 105 Endless runs, 59 were abandoned from the pause menu, a quarter of those within five seconds of starting; 9 of 20 computer matches were quit about two seconds after the START button. The board was rising before the player had finished reading it, and the only way out threw away whatever they'd done. Every Endless run and computer match now opens on a still board with a goal line and TAP TO START over it: nothing moves until a tap, key press or pad button, and Escape opens the pause sheet instead of just quitting.

Four more fixes came out of the same walkthrough. A device's first visit now opens on a sign-in-or-guest screen before anything else, because the old tertiary "sign in" line went unread by all 22 first-time visitors it was shown to. The tutorial's Basics section now ends right after the top-out lesson instead of on the pause screen, since 15 of 31 tutorial starts were abandoned in between; pause is a control, not something worth a lesson of its own. A new SHOW ME button plays a puzzle's solution move by move for anyone stuck, at the cost of the day's streak if it's the Daily. And a lost Tower run now reports progress in the goal's own terms, "Dug 7 of 10 rows" or "Survived 1:40 of 3:00", instead of a generic score that didn't match what the floor actually asked for.

None of this came free in load time. /play has a byte budget set at a previous release, and six new screens' worth of copy and logic added 7,887 bytes to it: 1,329,689 bytes served behind the site's compression, against a 1,331,802-byte ceiling. Every other number the gate checks, paint time, frame cost, input lag, held at the same levels as before. The budget exists precisely so a day like this can't quietly make the game slower to open; today it didn't.

Dice Lock, the puzzle game, keeps track of where players stop playing. Today those numbers turned into six fixes, all found by one person walking through the whole game and checking it against real usage data.

The clearest problem was playing against a friend. Setting up a match meant sending them a web link, usually by pasting it into a chat app. Of 25 of these rooms that got created, only 12 ever had a match played in them: half sat empty, because the link had to travel through a separate app to reach someone who might already be sitting right next to the game. The fix replaces the link with a short code: four letters, easy to read aloud or type, shown big on the host's screen under "Your friend enters this code." The letters skip anything that looks like another letter or a number, so there's no mixing up an I with a 1. A wrong or outdated code now gives a clear message instead of a dead link.

The second fix dealt with a different kind of drop-off. Looking at 105 solo runs, 59 were quit from the pause menu, a quarter of those within five seconds of starting; in matches against the computer, 9 of 20 were abandoned about two seconds after pressing start. The board was already rising before the player had even finished reading what they were supposed to do, and quitting threw away all their progress on it. Now every one of these games opens on a frozen board showing the goal, and nothing moves until the player taps, presses a key, or presses a button, so there's time to read before the clock starts.

Four smaller fixes came out of the same review. A new device's very first screen now asks plainly whether to sign in or play as a guest, because the old small-text sign-in option was never once read by any of the 22 first-time visitors it was shown to. The beginner tutorial now ends right after its top-out lesson instead of lingering on the pause screen, since nearly half of people who started the tutorial quit somewhere in between those two points. A new "Show me" button will play out the solution to a stuck puzzle, move by move, though using it on the daily puzzle costs that day's winning streak. And when a player loses a run in the Tower mode, the game now tells them how far they got in terms that match the actual goal, such as "Dug 7 of 10 rows" or "Survived 1:40 of 3:00", instead of a generic score that didn't line up with what that stage was actually asking for.

Adding six new screens isn't free: it added about 7,887 bytes to the total size of the game's main page, landing at 1,329,689 bytes against a 1,331,802-byte limit the project holds itself to. Every other speed measurement, how fast the page becomes usable, how fast it reacts to input, stayed the same as before. That limit exists so a busy day like this one can't quietly make the game slower to load, and today it didn't.