Testers get a one-tap reroll, and a dashboard stops wearing the wrong colorsTesters get a one-tap reroll, and a dashboard stops wearing the wrong colors

October 3, 2026 · Dice Lock's testers get a one-tap reroll and a redrawn Tower, while Reckreation's dashboard quits painting itself in whichever group you just left.A puzzle game's testers get a faster way to roll dice, and a tournament site's dashboard stopped showing the colors of the group you'd just left.

Build 12 ships to testers, with a new way to roll

Dice Lock's build 12 went up to TestFlight today, eighteen commits past build 11. The headline is a double tap: tap a die on the board and it rerolls right there, under your finger, with no need to move the cursor onto it first. Reroll L and Reroll R still work the old way, rolling whichever pair the cursor already sits on; the new gesture is for a die you haven't aimed at yet, and it refuses in exactly the same cases the old controls do: a locked die, a die on cooldown, a Guardian that bans rerolls outright. It won't double-roll: tapping the die the cursor is already on swaps the pair twice and rolls nothing, since the first of those two taps already did the swap.

The Tower map got a redraw to match: a one-line floor title instead of a sentence, floor names on wall plates, a Guardian drawn amber with a pointer instead of a score, and a sheet introducing each Guardian (name, health, rules) before the fight starts. Settings gained a way to restart the Tower from scratch while keeping any crown already won.

One correction rode along: seven places in the project, including a line shown to testers, claimed a TestFlight upload is 40 MB. It never was. Build 12's .ipa, weighed after uploading it, is 2.4 MB. The 40 was a guess written into a decision document the day before the first build existed, then copied into three scripts and a test file by nobody who thought to doubt it. The minutes a build takes to process are real, but they come from the archive, the export and Apple's own review (23 seconds, 11 seconds, a 47-second upload, about two and a half minutes to list), not the file's size. The message shown to testers now says a build takes a few minutes, with no number left to second-guess.

A dashboard stops painting itself in the wrong group's colors

Reckreation runs its own color scheme per tournament group, and its shared dashboard page had a bug: click from one group's page over to /dashboard, and the background and title text kept the colors of the group just left, instead of switching to the one landed on. Measured directly: cream text on a near-white card, a contrast ratio of 1.16 to 1, readable only in theory. The cause was that the two rules that actually paint a page, background color and text color, were written only onto the outermost wrapper, whose colors get set once, on a browser's first load, and never touched again on the client-side navigations that follow. A different element inside that wrapper was already being updated correctly on every click; nothing on the page read its values.

The fix moves those two rules onto the element that does update on every navigation, and has it copy its colors back onto the outer wrapper too, since a few things a browser draws itself (the rubber-band bounce past the top of a scroll, the scrollbar's corner) only ever look at the outer element's color. It was confirmed against a running copy of the site rather than a static page, because the bug was about timing that reading the source alone couldn't settle.

Chasing the fix down meant nailing exactly how many of the app's color tokens change across its seventeen schemes: 26, not the 9 that three documents still claimed, one of them a comment written earlier the same day. Nine used to be right; a change made since then had widened it, and nobody had gone back to correct the explanations. All three are fixed now, with the old numbers struck through rather than deleted. Verifying the fix also turned up something unrelated: the project's generated architecture diagram had been silently stuck on an outdated picture since the day before, because a stray character in a diagram label had broken the tool that draws it. Nothing had flagged the failure; it surfaced only because this investigation happened to run that tool by hand.

A new way to roll a die, now in testers' hands

Dice Lock, a dice puzzle game, sent its twelfth test build to testers today, eighteen code changes past the last one. The biggest new thing: double tap a die on the board and it rerolls right there, with no need to move your selection onto it first. Other reroll buttons still work the same way; this is just a quicker option for a die you weren't already pointed at. It refuses wherever the old buttons do: a locked die, one cooling down, a boss fight that bans rerolling. It also won't do anything if you double tap the die you already have selected, because the first tap just reselects it, leaving nothing fresh for the second to roll.

Tower mode's map (a climb up many floors, each with its own challenge) got redrawn to show less text and more at a glance: floor names as wall signs, boss floors marked amber, and a short introduction to each boss before the fight starts. A new Settings option restarts Tower progress from scratch, keeping any crown already earned.

One more thing got corrected: seven places in the project, including a message shown to testers, said a test build upload is slow because the file is 40 megabytes. It never was. This build's file, weighed after uploading, is 2.4 megabytes. Someone wrote "40 MB" as a guess the day before the first build existed, and it got copied into several other files by nobody who checked it. The wait is real, but it's Apple's own review after the upload (roughly 23 seconds to build, 11 to prepare, a 47-second upload, then two and a half minutes to list), not the file's size. Testers now just see a build takes a few minutes, with no made-up number attached.

A dashboard's colors stopped getting mixed up

Separately, Reckreation, a site for running tournament brackets, had a color bug on its shared dashboard page. Each group running a tournament can pick its own color scheme, but clicking from one group's page into the dashboard kept showing the colors of the group you'd just left, not the one you'd arrived at. In the worst measured case, that meant cream-colored text on a background that was almost the same near-white shade, readable in name only, far below the contrast a page needs to actually be read. The cause: the two settings that actually paint a page's look, its background color and its text color, were only applied to the page's outermost wrapper. That wrapper's colors lock in once, the first time the site loads in your browser, and never update again as you click around afterward. A different part of the page was already updating correctly on every click; the fix just hadn't been pointed at it yet.

That fix makes the background and text colors follow the correctly-updating part on every click, and copies those colors back onto the outermost wrapper too, because a few things your browser draws itself (the stretchy bounce you get scrolling past the very top of a page, for instance) only ever look at that outer wrapper's colors. It was checked by watching a real, running copy of the site respond to actual clicks, since the bug was about split-second timing that reading code alone can't reveal.

Tracking the fix down meant working out exactly how many separate color settings change between the site's seventeen color schemes: 26, not the 9 that three internal explanations still claimed. One of those had been written just hours earlier, in the same work session. Nine used to be correct; a separate change made since then had quietly raised it, and nobody had gone back to update the explanations. All three are corrected now, with the old numbers crossed out rather than erased. Double-checking this also found a diagram the project draws automatically of its own structure stuck on an out-of-date picture since the day before, because one stray character had broken the tool that draws it. It was found only because this check happened to run that tool by hand.