Dice Lock adds four-player raids; this blog now writes its own weekly recapDice Lock adds four-player raids; this blog now writes its own weekly recap
November 9, 2026 · Dice Lock's four-player co-op raid mode shipped, sharing Battle's room-code lobby, with fixes landed first for a vanishing host and a seat two players could grab at once.Dice Lock now lets four players fight one boss together, using its room-code system, with fixes landed first for a leader who steps away and a clashing seat.
Four players can now raid a boss together
Dice Lock picked up a new way to play today: up to four people can host a room, share its code, and fight one boss together instead of against each other. A raid room reuses Battle's own lobby code pool, so joining one works exactly like entering any other room, just with four seats instead of two, each claimed by a compare-and-swap write so two phones racing for the same seat can never both win it.
The boss shares one life bar across the whole party, and a win gets recorded on its own ladder, synced to your account rather than lost when the room closes. It stays separate from solo Tower climbing in both directions: beating a raid level doesn't unlock anything in the Tower, and clearing one with a group only opens the levels below it for play, it doesn't mark them beaten. Full credit for those still has to be earned on their own.
Getting there took five fixes to the raid's referee logic, found in a review before launch rather than after it. A party fixed before the fight's row existed left a seat that walked out mid-join still counted when life was scaled to the group, so a ghost fought alongside everyone else and the fight couldn't be lost. A host who stepped away between fights used to freeze the room, since only the host could start the next one; the room now hands that role on to whoever's still sitting there. And closing a room while its fight was still live used to leave the row open with no winner and no word to the other phones; a fight closed that way now always ends with an announcement everyone hears.
The blog now writes its own week, not just its days
This site's own blog section got rebuilt earlier in the day: instead of a month calendar, /blog is now a stack of months, each one a row of day tiles linking straight to that day's post, followed by the week's own summary once one exists. The shape shipped with nowhere yet to get a summary from. Nothing was generating one.
By the end of the day, a second change closed that gap: the nightly sweep now writes a finished week's summary itself, once every day in it is published and no summary for it exists yet, and publishes it the same way an ordinary post goes out. A model call that comes back refused is retried once with the refusal fed back into the prompt; refused a second time, the sweep gives up for the night rather than publish something it isn't sure of, and the week stays due until the next run.
Four players can now team up to fight one boss
The dice game Dice Lock got a new way to play today: up to four people can open a shared room, hand out its code, and fight one big boss together instead of competing against each other. Joining a raid room works exactly like joining any other room in the game, just with four seats open instead of two, and the game now makes sure two phones can never grab the same seat at the same moment by accident.
The boss has one health bar shared by the whole group, and a win gets saved to your account rather than disappearing when the room closes. It's tracked completely separately from playing the game's tower by yourself: beating a boss with a group doesn't unlock anything in the solo tower, and clearing a high boss level with help only opens the easier levels below it so you can play them, it doesn't mark them as already beaten. You still have to beat those yourself to get credit.
Getting the feature safe enough to release took five separate fixes, all caught by checking the work over before it went out rather than after. One bug let a player who left a room right as a fight started still count as part of the group, so the fight's difficulty was set for a player who was never actually there, and a fight like that could never be lost. Another left the room stuck with nobody able to start the next fight if the player in charge of it stepped away between rounds; now that job passes to whoever is still there. A third let someone shut the room down mid-fight with no result recorded and no message sent to the other players; a fight ended that way now always tells everyone it's over.
This blog now writes its own week, not just its days
The part of this site that shows the blog got rebuilt earlier in the day. Instead of a calendar grid, the blog page is now a stack of months, each one broken into weeks, each week a row of little tiles you can click through to that day's post, followed by a short write-up of the whole week once one exists. When this shipped, there was nowhere yet to get that weekly write-up from. Nothing was actually writing one.
By the end of the day, a second change filled that gap in. Every night, once a finished week has had all its daily posts published and still has no weekly write-up, the system now writes one itself and publishes it the same way an ordinary day's post goes out. If the AI writing it gets turned away and refused, it's asked again once, told why it was refused the first time; if it's refused a second time, that night's attempt is abandoned rather than publishing something it isn't confident in, and the week stays unwritten until the next night's attempt.