Dice Lock ships as a full game in a day, and a bot gets its own front doorDice Lock ships as a full game in a day, and a bot gets its own front door

September 5, 2026 · Dice Lock went from spec to a finished, phone-ready game in one day, and the CRM bot got its own webhook that can't turn a message into a ticket.A dice game went from a plan to a finished, phone-friendly game in one day, and a support bot got a doorway that can't turn a message into a ticket.

Dice Lock ships as a full game in a day

Dice Lock, a dice battle game against an AI opponent, went from a blank spec to a finished, mobile-ready release today, live at jiolab.dev/dicelock. The spec, engine, AI, and Canvas front end landed by early afternoon, followed by the pieces that make it feel like a real game: match settings (health from 100 to 500 or off entirely, a 0-2 second reroll delay, a match timer from one to five minutes or untimed), an Endless mode that drops the opponent for a single board with climbing difficulty and a best score saved in the browser, and a help overlay that finally explains what the battle meter does and what its two abilities, Cleanse and Barrage, actually do. Gray dice, the ones locked in place by a failed reroll, can now be swapped like any other die, so a bad roll can be moved out of the way instead of sitting dead until a match happens to land beside it.

The last two pieces were about actually being able to play it. A thirteen-step interactive tutorial teaches every action (moving, swapping, rerolling, locking and unlocking, raising rows, using both abilities) by requiring the player to do it, not by reading about it, and is now offered before a first-time player's first match. And on a phone, the game didn't fit: at 375x667 the page laid itself out at 1171 pixels wide, with overflow hidden making the extra width unreachable rather than scrollable, so the title screen sat off to the side of the visible screen and no match could even start. The cause was one grid track sized to its widest item (a footer hint that wanted 1069 pixels of unbroken space) rather than anything about the boards themselves. Every track now floors at a sane minimum, the layout math reads the actual page box instead of a rectangle that was itself part of the overflow, and controls are now sized for a thumb rather than a mouse pointer.

The CRM bot gets a door of its own

Separately, on the BigBrain side: the CRM bot and the general-purpose bot both talk over Telegram, and until today they shared machinery that made it easy to fix a bug in one and not the other. The CRM bot now has its own webhook route, verified against its own secret rather than the general bot's. Telegram echoes back whichever secret a given bot's setWebhook call registered, so which secret verifies a delivery is the only signal for which bot it came from, and a wrong or unset secret now names itself in the rejection instead of pointing someone at the wrong variable to fix. More importantly, the CRM bot's handler cannot reach the code path that turns a message into a Linear ticket at all: it only recognizes a reminder button press or a typed name reply, and answers anything else with one plain sentence. The four functions both bots need moved into a shared module rather than being copied between them, because a copy is exactly how a fix lands in one bot's code and never makes it to the other's. A new health-check entry, telegramCrm, reports honestly too: it doesn't count as broken if the CRM bot's three keys are simply never set, since that's a legitimate state for a machine that isn't running it.

Dice Lock, a dice game against a computer opponent, gets built and finished in one day

Dice Lock is a dice battle game you play against a computer opponent, live at jiolab.dev/dicelock. Today it went from a written plan to a finished, phone-friendly game, all in one day. The core rules, the computer opponent, and the on-screen game board were working by early afternoon, and then it kept growing: players can now choose how much health each side starts with, from 100 up to 500, or turn it off so only running out of board space ends the match, how long you wait before you can reroll, and how long a match lasts, or make it untimed. A new Endless mode drops the computer opponent and just keeps you playing solo against rising difficulty, saving your best score right in your browser. A help screen was added explaining what the special-move meter does and what its two abilities actually do. And the gray, locked dice that show up after a bad reroll can now be swapped like any other die, so a stuck one can be moved out of the way instead of sitting there until a lucky match frees it.

The last two changes were about actually being able to play. A new tutorial walks a first-time player through every move (moving, swapping, rerolling, locking pieces, using both abilities) by having them actually do each one, not just read about it. And on a phone, the game genuinely didn't work: the page was laying itself out nearly twice as wide as the phone's screen, with the extra width hidden rather than scrollable, so the start screen sat off to the side and no game could even begin. The cause turned out to be a single line of hint text in the footer that was wide enough to stretch the whole page to fit it. That's fixed, the game now reads the real size of the screen instead of a distorted one, and the on-screen buttons are sized for a finger instead of a mouse pointer.

A support bot gets its own separate doorway, so it can't accidentally create a ticket

Separately, on the automation side: there are two automated Telegram chat bots (a general-purpose one and one dedicated to a CRM, a tool for tracking customer relationships), and until today they shared the same delivery pipeline in a way that made it easy to fix a bug for one and forget the other. The CRM bot now has its own separate doorway for incoming messages, checked against its own separate password rather than the general bot's, so a wrong or missing password now says exactly which bot it belongs to instead of pointing someone at the wrong one to fix. More importantly, the CRM bot's message handler simply has no way to reach the code that turns a message into a ticket: it only recognizes a reminder button press or someone typing their name back, and answers anything else with one plain sentence. The shared pieces both bots need were moved into one common file instead of being copied between them, because copying is exactly how a fix reaches one bot and never the other. A new status check for the CRM bot also reports honestly: it isn't marked broken just because its three settings have never been turned on, since that's a normal state for a machine that isn't running it.