Report an issue
Bug, broken command, or something on the site that's out of date — this is where it goes. There's no form to fill out and no ticket number. You just show up in Discord and say what happened.
/info in Discord tells you what's actually running right now.
Report it in Discord
The support server is the only place bug reports actually land. It's the fastest way to reach the team, and it means the discussion happens somewhere it can be looked at, replied to, and linked to later. One person runs the whole thing — going through the server is how a report gets seen.
Describe what happened, what you expected to happen, and — if it's a command — what you actually typed. Exact text beats paraphrase every time.
Open support server →DM the developer
If the report is about something you'd rather not post publicly — a privacy concern, a security issue, or something else where the support server feels wrong — send a direct message instead. Include the same details: what happened, what you expected, and how to reproduce it.
Response time varies. It's a spare-time project, and this is one person's inbox.
@dx.rom on DiscordWhat to include
A report with these five things gets fixed in about five minutes. A report without them usually turns into a back-and-forth that stalls for days.
- What you actually typed. The exact command, including the prefix and any arguments. If it's a slash command, copy-paste it. If it's a prefix command, do the same.
- What happened. The actual error message, or "nothing happened at all," or "it responded but with wrong info." Don't describe what you think the problem is — describe what you saw.
- What you expected. The same command working correctly. If the site or
/helpdescribes a certain behavior and the bot did something else, that's the shape of the report. - A screenshot if it's visual. A picture of the actual message is worth more than a paragraph explaining it. Crop it to the relevant part if you can.
- Whether it happens every time. If it worked once and then stopped, that's a different kind of bug than one that always fails. Saying which one it is saves a whole round of questions.
What not to report
A few things that get treated as expected behavior rather than bugs, so you don't have to spend the time writing them up:
- A command that's on the "coming back" list. If it's retired, it not responding isn't a bug — it just hasn't returned yet.
- Site copy that's more ambitious than the bot. The About page explains this. It's not a bug, it's how the project is currently structured.
- Discord itself being slow. If other bots in the server are also lagging, it's almost never a bot-specific issue.
- "Can you add this feature." Not a bug report. Feature requests are welcome, but they belong in general chat in the support server, not as a report.