Dice Lock players can report a bug and see when it's fixedDice Lock players can report a bug and see when it's fixed
November 7, 2026 · Dice Lock players can now report a bug and watch it move from received to fixed to shipped, and a years-old handoff bug in BigBrain's queue is finally sealed.Dice Lock players can now report a bug and watch it move from received to fixed to shipped, and a years-old handoff bug in BigBrain's queue is finally sealed.
last updated
A feedback loop that reaches back to the player
Dice Lock has had a way to send in a bug report for a while, but nothing closed the loop: a report went in and nothing came back. Today's build gives it an ending. A report now carries a status, a reply, and, once it is fixed, the build number that carries the fix. A player's own account lists every report they have sent, each one reading RECEIVED, FIXED, or UPDATE READY, depending on whether a build containing the fix has actually reached them. A dot appears on the gear icon and on FEEDBACK under Account when there is something new to read, and tapping UPDATE on a fixed report jumps straight to the install link.
On the admin side, every open report now shows up with its note, a screenshot, and who sent it, alongside a form to mark it open, fixed, or canceled, write a reply of up to a thousand characters, and record which iPhone and Android builds the fix went out in. Answered reports collapse under their own heading but stay editable.
Building the player-facing half surfaced three ways the first version would have lied to someone. UPDATE READY used to fire for any install, so a player on the App Store could be told to update to a build that had only gone to TestFlight or Play's internal track, with nothing they could actually install. It now checks which channel the fix build shipped to and only shows UPDATE READY there; everyone else sees FIXED, coming in the next release. A phone shared by two accounts was handing one person the other's report list on sign-out and sign-in; that is now swapped properly with the account. And saving a reply with no actual change used to mark the report as having something new to read, which it now does only when the reply or status actually changed.
A handoff between two queued tasks stopped vanishing
BigBrain runs tasks against Linear issues, and a tree lock keeps two tasks on the same issue from running at once: the second has to wait for the first to finish. When a handoff from one task to another landed while that lock was in effect, it used to just get refused and dropped, which could leave a ticket stuck, looking ready to move but never actually handed to the task meant to pick it up. The ticket that closes this, JIO-3911, traces back to JIO-1410, raised far earlier.
The fix holds a refused handoff in a new table, keyed to the issue, instead of discarding it. Once the task that was running finishes, the hold is replayed automatically, and the completion log gets a line naming both tasks involved. If whatever is blocking it dispatches its own handoff first, that one wins and the held one is dropped; if a replay is refused for some other reason, it gets posted to the issue instead of disappearing again.
Players can report a problem in Dice Lock and find out what happened to it
Dice Lock, the game this project makes, already let a player send in a note about something wrong. What was missing was any way to find out what happened to that note afterward: it just went in and nothing came back. The newest version of the game closes that gap. A report now has a status, a written reply, and, once it is actually fixed, the number of the app update that includes the fix. Open the game's own feedback list and each report you sent reads RECEIVED, FIXED, or UPDATE READY, depending on whether an update containing the fix has actually reached your phone yet. A small dot shows up on the settings icon and on the feedback page when there is something new to read, and tapping the update button on a fixed report takes you straight to where you install it.
On the side only the people running this project see, every open report now shows up with the player's note, a screenshot if they sent one, and who sent it, alongside a form to mark it open, fixed, or canceled, write a reply of up to a thousand characters, and note which iPhone and Android versions the fix shipped in. Reports that have been answered collapse under their own heading, but they can still be edited.
Building the player-facing half of this turned up three ways the first version would have told someone something untrue. The update-ready message used to show up for any install of the game, so someone who got the game from the App Store could be told to update to a version that had only gone out to a small group of testers, with nothing they could actually download. It now checks which group the fix actually went to before showing that message; everyone else is just told it is fixed and coming in the next release. Separately, when two different people shared one phone, signing out and back in could show one person the other's list of reports; that is now tied to the right account. And saving a reply without actually changing anything used to mark the report as having new news to read, which now only happens when the reply or its status genuinely changes.
A message between two waiting tasks stopped disappearing
BigBrain, the system behind this whole project, runs automated tasks against tickets in its project tracker. When two separate tasks both need to work on the same ticket, a safety lock makes the second one wait until the first finishes. The problem: when the first task tried to hand its work off to a second task while that lock was active, the hand-off used to just get rejected and thrown away. That could leave a ticket looking ready to move forward when nothing was actually going to pick it up next. The ticket that fixes this, JIO-3911, points back to an older ticket, JIO-1410, raised a long time before.
The fix now holds on to a rejected hand-off instead of throwing it out, filing it under the ticket it belongs to. Once the task that was running finishes, the held hand-off is sent through automatically, and the system's log records a line naming both tasks involved. If whatever was blocking it sends its own hand-off first, that one takes priority and the held one is dropped; if the held one gets rejected again for some other reason, it is posted as a comment on the ticket instead of vanishing a second time.