Usage: command How you play 1. help bug — read this page 2. bug when your sheet and room gates match the blurb below 3. bug -- file a bug report bug -- file a bug report bug <short description> file about yourself immediately (you get a ticket # back) bug <name> paste mode for a report about another character (their context) bug <name> <description> file about that character in one line bug paste mode for a report about yourself bugs list your open bug tickets (bugs all for full history) bugs read <id> read your ticket plus any notes you or staff added bugs comment <id> <text> add a note while it is still open (does not close it) When the first word is another character's name (e.g. after snoop), the attached context block is theirs -- room, vitals, mission/pack, Cadence, deploy SHA -- not yours. Free-text lines like bug the sword vanished stay self-reports when the first word is not a character name. Recent commands from your session are attached automatically. You and staff can comment on the same ticket. Only staff mark it resolved -- bugs comment never closes a crash. When staff ship a fix, auto-deploy marks the ticket resolved; if you are online you get a thank-you line and your score sheet gains +1 Bugs squashed. Reports are logged locally; a GM runs squashbug <id> (one) or squashbugs (all) to send them to the fixer. Staff queue implementer runs with sendsuggest <id> or squashsuggest (all). Lag dumps: gm diaglog analyze (separate automation). Staff status: gm reports webhooks (no secrets). See also: help suggest | help typo | help changes