Dice Lock replaced its menu list with five tabs built around what you playDice Lock replaced its menu list with five tabs built around what you play

October 19, 2026 · The main menu became five tabs that each show the mode you last played, and the app now reports a crash inside the phone itself, not only the server.The main menu became five tabs that each show the mode you last played, and the app now reports a crash inside the phone itself, not only the server.
last updated

The main menu is five tabs now, each one about the mode you're in

Dice Lock's home screen used to be a list of other screens: START, HOW TO PLAY, RECORDS, SETTINGS. Every destination was two presses away, and the screen a player opened most often had nothing on it worth looking at. That list is gone. A five-tab bar now runs along the bottom of every menu page: the mode last played, MODES, DIE, RECORDS, SETTINGS. HOW TO PLAY moved under SETTINGS, where a rules reference belongs, rather than sitting on the root a thumb opens first.

The first tab is whichever mode was played last, and it isn't a static shortcut. It's a "centre": the Tower tab shows the floor reached and the next Guardian over CLIMB ON; the Versus tab shows the record against the computer at the current difficulty, the last match's result, and REMATCH; the Puzzles tab shows the solved count, the next unsolved board, and today's Daily. Three different modes, one shared layout, each wired through a `MODE_CENTRES` table so adding a fourth doesn't mean inventing a fourth screen from scratch.

The DIE tab took the most iteration. It used to share a screen with the account settings; it's now its own page, split out after a TestFlight pass where the note was blunt: "Die and the Guest sections should be two different sections. Guest is the account part, Die is the customization part." Account is now the handle, the sync, and the way out. DIE is only the forty chips a profile can wear. For a guest, that page used to just stop after one sentence and three sign-in buttons, showing none of what it was withholding. It now draws the plain die with a padlock on its corner, every customization row visible but dimmed to 45% and disabled, so a guest can see exactly what signing in buys. Getting the sign-in flow to behave on that locked page took two more same-day fixes: a sign-in started there was landing back on the Account screen instead, and a refused sign-in came back to the same locked page with nothing said about why.

A crash inside the app can finally reach us

Until today, a fault only reached anyone if it happened on the server, where it scrolled past in a deploy log. A crash in the browser, or inside the iPhone or Android shell wrapping the game, went nowhere. That's now closed end to end. The server catches its own uncaught exceptions and unhandled rejections and forwards them to Sentry, loaded only if a Sentry key is actually configured, since the dynamic import costs 438ms against an 8ms init if it isn't needed. The browser gets the same reporting for any page that throws, with the stack and its breadcrumbs.

That browser reporting would have been quietly broken for a chunk of players: ad blockers like uBlock Origin and Brave's shields drop a direct request to Sentry's ingest domain by default, and a player running a blocker is disproportionately likely to be the player whose browser is doing something unusual, which is exactly the browser a renderer breaks on. The fix is a tunnel: the page posts the crash envelope to a path on dicelockgame.com itself, and the server forwards it byte for byte to Sentry, deliberately built so it isn't an open proxy for arbitrary traffic.

The two native shells needed their own wiring, because a dead renderer or a terminated web view never reaches the JavaScript the browser-side reporting depends on. The iPhone shell now reports through its own Sentry SDK when the web content process dies; the Android shell reports when its renderer goes, flagged as an error if the app actually crashed and a warning otherwise. Both read their DSN from build configuration rather than the app's own code. The privacy page was updated to say plainly that Sentry exists and what a crash report holds, and the alert rules behind it were written down since the project has no standing rule list elsewhere.

Dice Lock's main menu is five tabs now, each one about what you're doing

Dice Lock, the dice game, used to open to a home screen that was just a list of other screens to tap into: Start, How to Play, Records, Settings. The screen you saw most often had nothing useful on it. That list is gone. There's now a bar of five tabs along the bottom of every menu screen: whichever mode you played last, Modes, Die, Records, Settings. How to Play moved under Settings, since rules are something you go looking for, not something that belongs on the very first screen you see.

The first tab always shows whichever mode you played last, and it isn't just a shortcut back into it: it's a small dashboard for that mode. Last climbing the Tower, that tab shows the floor reached and a button to climb on. Last playing against the computer, it shows your win record at the current difficulty, how your last match went, and a rematch button. Last doing puzzles, it shows how many you've solved and the next one waiting. Three modes share one layout built from a shared list, so adding a fourth later means filling in a row, not building a whole new screen.

The die-customizing tab took the most back-and-forth. It used to share a screen with account settings, and got split apart after the owner tried a test build on their own phone and pushed back: the account part and the die-customizing part are two different jobs and shouldn't live on one page. Now the account screen is just the login and the way to sign out, and the die tab is only about the forty-odd looks a die can wear. For someone who hasn't signed in, that die screen used to stop after one sentence and three sign-in buttons, without showing what signing in would unlock. It now shows the plain die with a small lock icon, and every customization option visible but greyed out and un-tappable, so a visitor can see what they'd get. Getting sign-in to behave there took two more same-day fixes: a sign-in started on that screen was wrongly landing on the account screen instead, and a refused sign-in came back with no explanation why.

A crash inside the app can finally be reported

Until today, a problem only got noticed if it happened on the game's own server, where it just scrolled past in a log. A crash in someone's web browser, or inside the iPhone or Android app, went unseen. That gap is now closed. The server catches its own unexpected failures and sends them to Sentry, a crash-reporting service, but only loads that reporting code if a Sentry key is actually configured, since loading it costs real startup time even when nobody needs it. The web version of the game now reports the same way when a page breaks, including the full error and a trail of what led up to it.

That web reporting would have quietly failed for a chunk of players, because ad blockers like uBlock Origin and Brave's built-in shields block a direct request to Sentry's servers by default. A player running an ad blocker is more likely than most to be running an unusual setup, which is exactly the kind that tends to break things. So the fix routes around it: the page now sends its crash report to the game's own server first, which forwards it, unchanged, on to Sentry, built so that path can only be used for that one purpose.

The iPhone and Android apps needed a separate fix, because a crash severe enough to kill the app's inner browser view never reaches the web code the browser-based reporting depends on. The iPhone app now reports through its own crash setup whenever that inner view dies. The Android app does the same whenever its renderer goes, marking it a real error if the app crashed and a milder warning otherwise. The privacy page now says plainly that this reporting exists and what it collects, and the alert rules behind it got written down, since the project had no written rule list anywhere else.