Dice Lock's modes get names, and its Battle opponents get outfitsDice Lock's game modes get real names, and its casino opponents get outfits

November 18, 2026 · Dice Lock's four modes finally have real names, its six Battle opponents dress as casino regulars, and tests across three repos stopped littering /tmp.Dice Lock's four game modes finally have proper names, its six casino opponents got outfits to match their rank, and test runs across three projects stopped leaving junk files behind.

Dice Lock's menu used to answer to a mix of internal shorthand. Today every mode, tab and address says what the owner actually picked: Showdown, Quick Draw, Combos, Full Table, Heads-Up, The House. The tabs read from one label table instead of letting one mode borrow another's word, and the three Battle cards carry the approved lines for each format. A decision record (0629) lays out the naming choice and formally retires four older ones that argued for the names being replaced. Nothing about how a match is stored or scored changed: it is the same game, finally called what it is called everywhere a player looks.

The six Battle opponents got a matching pass. Each rank keeps its die-shaped head, pip count and face color, but the crown-and-cape look is gone, swapped for an outfit that escalates with rank: a lanyard for the Rookie, a cap and zip jacket for the Regular, a flat cap and toothpick for the Hustler, a fin and shades for the Shark, a visor and waistcoat for the Ace, a fedora and fur coat for the Kingpin. The gear is drawn from the player's own dice palette rather than a fixed color, so it still matches whatever theme is in use. A separate commit replaced the ability icons with the eleven glyphs picked earlier off a design canvas, closing a gap where one internal copy of the icon list was missing six of them entirely; a new test now fails if a tooltip's picture ever drifts from its ability's official glyph again.

Tests stopped leaving litter behind

Three repos landed pieces of the same cleanup today. On the website, five test files were mkdtemp-ing temporary directories and never removing them, leaving 84 leftover entries in $TMPDIR after a single plain test run; they now register every fixture and remove it in an after hook, win or lose. bigbrain-core's task-runner had the same problem in sixty-four test files, which were deleting their temp fixtures only when every assertion passed, so a failing test run before today could already be the real cause of a full /tmp. Each file now keeps one list of its fixtures and clears it in test.after regardless of outcome.

The other half of the same day's work was Chrome specifically. macOS ignores the TMPDIR environment variable for Chrome, so the capture and diagram-rendering scripts in bigbrain-core, plus the website's own diagram browser, were each resolving their own path to a Chrome binary and occasionally leaving behind code-signing clones of it. Both repos now try a shared $CHROME variable, pointing at one chrome-headless wrapper, before falling back to their old CHROME_PATH or CHROME_BIN settings, and their own error messages were updated to name $CHROME when it is missing. A companion change gives dispatched test suites a separate MAC_CHROMIUM_TMPDIR alongside their already-private TMPDIR, since Chrome was never going to read the private one anyway.

None of this touches what a player or reader sees. It is the unglamorous fix for machinery that was quietly accumulating disk clutter every time the test suites ran, in three different repos that had each been doing their own version of the same workaround.

Dice Lock's menu used to show a mix of internal shorthand names for its game modes instead of names a player would recognize. Today every mode, tab and web address says what the owner actually picked for it: Showdown, Quick Draw, Combos, Full Table, Heads-Up, The House. The tabs all read from one shared list of names now, instead of one mode sometimes borrowing another mode's label by mistake, and the three versions of the head-to-head format carry their approved descriptions. A written decision explains the naming choice and formally retires four older documents that had argued for the names being replaced. Nothing about how a match is saved or scored changed underneath: it is the exact same game, just finally called what it is supposed to be called everywhere a player looks.

The six computer-controlled opponents in the head-to-head mode got a matching makeover. Each rank still keeps its die-shaped head, its dot count and its face color, but the old crown-and-cape look is gone, replaced with an outfit that gets fancier as the rank goes up: a lanyard for the lowest rank, a cap and jacket for the next, then a flat cap and toothpick, then sunglasses and a fin, then a visor and vest, and a fedora and fur coat for the top rank. The clothing colors are drawn from whatever dice color scheme the player is already using, so it still matches their theme. A separate change also fixed the small icons that represent each special ability in the game: one internal copy of that icon list was missing six of the eleven abilities, so its pictures did not match what players saw on screen. A new automatic check now catches it immediately if that ever drifts again.

Automated tests stopped leaving junk files behind

Three separate codebases fixed pieces of the same underlying problem today. On the website project, five test files were creating temporary folders during testing and never deleting them afterward, leaving 84 leftover folders behind after a single run of the test suite. Those tests now track every temporary folder they create and delete it once the test finishes, whether it passed or failed. A bigger project, the one that runs background automation for all these projects, had the same problem in sixty-four separate test files, which had only been cleaning up after themselves when every check in the test passed; a test that failed before today could already have been the reason a machine's temporary storage filled up. Each of those files now keeps one list of what it created and clears all of it no matter how the test ends.

The other half of today's cleanup was about the Chrome web browser specifically. On Mac computers, Chrome ignores the usual setting that tells programs where to put their temporary files, so the scripts that use Chrome to take screenshots and render diagrams were each finding their own copy of Chrome to launch, and sometimes leaving behind duplicate, security-signed copies of the browser as a side effect. Two of the affected projects now point at one shared setting that names a single wrapped copy of Chrome to use, before falling back to their older settings, and their error messages were updated to mention the new setting by name if it is missing. A related change also gives background test runs their own separate folder specifically for Chrome's temporary files, since Chrome was never going to use the general-purpose one anyway.

None of this changes what a player or reader actually sees. It is the unglamorous fix for machinery that was quietly piling up clutter every time the automated tests ran, across three different projects that had each built their own version of the same workaround.