Dice Lock's Tower is playable end to end, all five bosses beatableDice Lock's Tower is playable end to end, all five bosses beatable

September 18, 2026 · Dice Lock's five-boss Tower mode is finally winnable end to end, and the Steward assistant can no longer sign up for a site the owner never approved.Dice Lock's new tower-climbing mode can now be beaten all the way through, and an automated helper can no longer sign up for a website the owner never approved.
last updated

Dice Lock's Tower is playable end to end

The Tower is a new climb mode for Dice Lock: five floors, a staircase of dice, a Guardian waiting at the top of each. Until today floors three through five could not actually be finished. The Overgrowth, the Astronomer and the Leviathan were each beaten 0 times in 30 tries during testing (JIO-1229). Not hard, impossible. Fixing that meant retuning what each Guardian does rather than the fight around it. The Overgrowth lost its no-rerolls rule and slowed its attack to once every 45 seconds instead of 20; the Astronomer kept its seventh die face but dropped its target score from 2208 to 1200, because there was no softer mutation left to try. Every floor was then run 30, 300 and 1,000 times to check the win rate held steady rather than looking fair on a lucky sample. Thirty tries alone turned out to be too noisy to trust, since even the untouched, easiest boss swung from 3.3 tries to win at thirty games to 5.2 at a thousand. All five floors now land in band, averaging between 3.3 and 6.0 tries apiece.

The staircase itself is generated, not hand-placed: a repeating three-lane pattern draws any number of floors into the same width, so a fortieth floor would need no one to lay out its dice by hand. The fight screen was rebuilt around a rule the owner set for the whole mode: nothing explains itself once a fight starts. A Guardian's name, its line of dialogue and its mutations are all shown on a card before the countdown; after that, no label, banner or toast appears for the rest of the fight, a restriction the tests now pin directly so it can't quietly regress.

An assistant that signs up for services now needs a name on a list first

The Steward is the automated role that creates accounts, mailboxes and browser profiles on the owner's behalf. Until today, permission to do that at a given site was a sentence in a Linear ticket ("go make us a Railway account"), read once and then forgotten. Nothing stopped the Steward from signing up anywhere else, and four services (huggingface, crazygames, browserbase and clerk-dicelock) already held accounts that no ticket had actually approved.

An approval is now a row in a file on disk, carrying the ticket and date that approved it, and the three commands that create a lasting identity (opening a mailbox, starting a persistent browser profile, and adding a vault entry) now check it before doing anything. An unapproved site gets refused outright rather than created and questioned later. The check fails closed: a missing or unreadable approval file blocks every site, not none of them. A second, independent copy of the same check was added to the daily account audit, so the two can be compared and neither can quietly drift from the other.

One more piece closes the loop: a refusal used to hand the whole ticket back to the owner as blocked, pulling it out of every automatic queue until they cleared it by hand. Now the session files the approval request as its own small ticket and leaves its own work sitting in the normal to-do list, unassigned, waiting only on that one line of sign-off.

Dice Lock's dice-climbing tower can now be played all the way through

Dice Lock, the dice puzzle game, is getting a new mode called the Tower: five floors to climb, with a staircase built out of dice and a boss (a "Guardian") waiting at the top of each floor. Until today, three of those five floors could not actually be won. Testing the game by having it play itself showed the last three bosses were beaten zero times out of thirty tries. Not just difficult, actually impossible to beat. Fixing that meant changing what each boss does, not just how hard the fight feels. One boss lost a rule that stopped the player from re-rolling dice, and started attacking every 45 seconds instead of every 20. Another kept its hardest trick (an extra die face most dice don't have) but needed a much lower score to beat, because there was nothing softer left to try. Every floor was then tested 30, 300, and 1,000 times in a row, because testing something only thirty times turned out to be too unreliable to trust: even the easiest, untouched boss swung between averaging 3.3 tries to win and 5.2 tries depending on how many times it was tested. All five floors now sit in a steady, fair range, each one taking between about 3 and 6 tries on average to beat.

The staircase of dice is built automatically from a repeating pattern, rather than someone placing every die by hand, so adding a fortieth floor later would need no extra manual work. The screen you fight the boss on was also rebuilt around one rule the owner set for the whole mode: nothing explains itself once a fight has started. A boss's name, its one line of dialogue, and the special rules it fights with are all shown on a card right before the countdown begins, and after that nothing pops up to explain anything for the rest of the fight. That rule is now locked in by an automated check, so it can't quietly slip later without someone noticing.

An automated assistant that signs up for websites now needs written permission first

The "Steward" is an automated role that creates accounts, email inboxes and browser sessions on the owner's behalf, at whatever site a task needs. Until today, permission to do that was just a sentence typed into a ticket somewhere ("go make us a Railway account"), read once by whoever did the work and then forgotten by everyone else. Nothing actually stopped the Steward from signing up anywhere else it decided to, and four services (huggingface, crazygames, browserbase, and a Clerk account for Dice Lock) already had accounts that no ticket had ever actually approved.

Approval is now a line in a file on disk, recording which ticket approved a given site and when, and the three actions that create something lasting (opening an email inbox, starting a browser session that keeps its login, and saving a new account record) all check that file before doing anything. A site that isn't on the list gets refused up front, instead of being created first and questioned later. The check is built to fail safely: if the approval file is missing or can't be read, every site is blocked, not none of them. A second, separate copy of the same check now also runs as part of the daily account review, so the two versions can be compared against each other rather than one silently drifting out of sync.

One more change closes a gap: a refusal used to hand the entire ticket back to the owner marked as blocked, which pulled the whole thing out of every automatic to-do queue until they cleared it by hand. Now the assistant instead files the approval request as its own small, separate ticket, and leaves its actual task sitting in the normal to-do list, unassigned to anyone, waiting only on that one line of sign-off.