The end of a Dice Lock run now celebrates one thing, not three at onceThe end of a Dice Lock run now celebrates one thing, not three at once
November 8, 2026 · Dice Lock's run-end screen now picks one thing to celebrate and one next goal, the splash screen became a wall of falling dice, and production databases lost everyone's write access.Dice Lock's end-of-game screen now shows one win and one next goal, the loading screen became falling dice, and the game's databases can no longer be written to by accident.
What a run ends on
A finished run used to throw every true thing at you at once: a rank-up banner, a new-best banner, a next-goal nudge, whatever applied, often disagreeing with each other about what the moment actually was. A new rule, posterLead, now picks exactly one thing to celebrate and exactly one thing to chase next. The celebration order is a rank up, then a new best, then, folded into a single line, a first score milestone, a first chain of four, or a first ten dice cleared at once, then nothing at all. A rank-up only fires on this run's own new best and a rank that's strictly higher, so a drop caused by somebody else's run elsewhere, landing at the same moment, never gets announced as yours. The target line is the next score threshold if you just set a best, your own best otherwise, or nothing on a forfeit.
Getting there took the Sprint and Endless posters, each fixed separately against review notes (one-way leads, two-way ties, fitting a short phone, what counts as "from chains") until both were rewritten to defer to the same rule instead of carrying their own. The poster itself now closes in as two doors: a colored field slides down from above, a dark strip and footer slide up from below, and they meet in 450 milliseconds with no overshoot. A run that ends faster than its own cool-off period has that cool-off stretched to match the doors, rather than the poster cutting the slide off early. Reduced Motion skips the slide and shows the poster already shut.
Topping out gets its own beat first: the stack flashes for 400 milliseconds, a brief tremor, then every die on the board splits into four quarters that fly outward, spin, shrink and fade, with a TOPPED OUT band (BURIED! in Sprint) slamming in at 550 milliseconds and the poster itself arriving 1,250 milliseconds later. It plays on your own board in Endless, Sprint, every Tower step and a Battle loss; on a Battle win, the opponent's board takes over the screen first instead. None of it plays on a quit, a forfeit, a lesson or a replay.
The splash shown while the game loads changed too: a wall of 102 dice rises over the loading logo, a chain fires through it, and the chain leaves a hole exactly where the logo was sitting the whole time, before the wall falls away, 3.1 seconds start to finish. Reduced Motion skips straight to a lit wall, a cross-fade, and the logo. Both the new posters and the new splash went out together in build 72, uploaded to TestFlight today.
Who can write to production
Separately, an outstanding audit finding got closed: every script that reads the Dice Lock and Reckreation production databases was logging in as the owner, with read-only behavior enforced, if at all, by a setting each script remembered to turn on itself. A new role, fleet_ro, now enforces that at the database rather than trusting the caller: it can connect and read, nothing else, with temporary-table creation revoked, a 60-second timeout on every statement, and the read-only default locked onto the role itself, so a session that clears that default to try a write fails outright instead of quietly succeeding. Setup generates the password in-process and never writes it anywhere but the project's own secrets file; a rollback script exists and was tested alongside it. The dry run covered two disposable Postgres clusters running real migrations, and all 18 verification checks passed on both. The scripts that read these databases now fail loudly and name the missing key if the read-only connection isn't configured, instead of quietly falling back to the owner's own login.
What happens when a game ends
When a run finished, the screen used to throw every true thing at the player at once: a banner for moving up in rank, a banner for a new best score, a hint about the next goal, whichever applied, often not agreeing about what the moment was actually about. A new rule now picks exactly one thing to celebrate and exactly one thing to aim for next. It celebrates a rank going up first, then a new best score, then, folded into one line, a first time you hit a score milestone, chained four pieces together, or cleared ten dice at once, and otherwise nothing. A rank-up only shows when it's this run's own new best and a genuinely higher rank, so a drop caused by someone else's game finishing elsewhere at the same moment is never announced as if it happened to you. The next goal shown is the next score milestone if you just beat your best, your own best otherwise, or nothing if you quit early with no points.
Getting there meant building two separate versions of this screen, one for Sprint mode and one for Endless mode, fixing each by hand against review notes (which direction the result leans, what to do on a tie, fitting on a small phone screen) until both were rewritten to follow the same rule instead of each working it out on its own. The screen now closes in as two doors: a colored panel slides down from the top, a dark strip and footer slide up from the bottom, meeting in the middle in under half a second with no bounce. If a run ends faster than the short pause that follows it, that pause is stretched to match the doors shutting, instead of the animation being cut off early. A reduced-motion setting skips the slide and just shows the screen already closed.
Filling up the board gets its own moment first: the stack flashes briefly, shakes slightly, then every die splits into four pieces that fly outward, spin, shrink and fade away, with a big TOPPED OUT banner (BURIED! in Sprint) slamming in, and the results screen arriving just over a second later. It plays on your own board in most modes; in a two-player match you win, the opponent's board takes over the screen first instead. None of this plays if you quit, give up, are in a lesson, or are watching a replay.
The loading screen changed too: a wall of 102 dice rises over the logo, a chain reaction fires through it, and that chain leaves a gap exactly where the logo was sitting, before the wall falls away, taking about three seconds in all. The reduced-motion version skips straight to a lit wall, a quick fade, and the logo. Both the new results screens and the new loading screen shipped together in the same test version of the app, uploaded today for testers to try first.
Who can change the game's live data
Separately, a known gap got closed: every script that reads the Dice Lock and Reckreation live databases was logging in with the same full-access account as everything else, with read-only behavior enforced, if at all, only by a setting each script had to remember to turn on itself. A new account now enforces that at the database itself, instead of trusting whichever script is asking: it can look things up and nothing else, can't fill the disk with temporary data, times out any request after a minute, and has read-only locked onto it directly, so even a script that tries to write something fails outright instead of quietly succeeding. Setting the account up generates its password inside the process and never writes it anywhere except the project's own locked-down secrets file; there's also a tested way to undo it. A trial run covered two disposable test databases running the real setup steps, and all 18 checks confirming the lockdown worked passed on both. These scripts now fail loudly and say exactly which setting is missing if the read-only connection isn't configured, instead of quietly falling back to the full-access login.