Appearance
Reporting a bug
Two complaints are almost impossible to describe from memory: "it would not let me make that move" and "it moved a checker I did not choose". By the time you notice, the position has changed, and the thing that would explain it — what the board was offering at the instant you tapped — is gone.
So the client records that continuously, in memory, and lets you save it afterwards. You never have to start a recording before a bug you did not expect.
Save a report
- Open log (under the board during a match, or in the lobby).
- Press save a bug report.
A JSON file downloads. Attach it to your message. Nothing is sent anywhere until you send it yourself.
What is in it
- every tap on the board, with the moves the board was offering at that moment, the dice, and how much of the roll you had already played
- every checker that moved, and why: your tap, or the client playing out a forced remainder on your behalf
- the messages to and from the server, with the shape of each position
- your settings, your browser, and the size of your screen
What is not in it
Your private key, your signatures, your reveal chain, your email address and your public key are all replaced with [redacted] before anything reaches the recorder. The file describes what happened in a game, not who you are.
Recording your screen
On a desktop browser the log panel also has record my screen. It asks which window to share, records until you stop it, and saves a .webm file. Useful when the problem is something you saw rather than something the board decided.
On iPhone and iPad the browser cannot record the screen; use the phone's own screen recorder (Control Centre → Screen Recording). The bug report is worth saving either way — it carries the part a video cannot show.