What it does
/feedback is the one-shot channel for telling the dev team something — a bug you hit, an idea you'd like to see. Submissions land in the team's internal queue with your username, guild, and timestamp attached so context never gets lost.
Two flavors:
/feedback bug— for things that broke. Include what you ran, what you expected, what happened./feedback idea— for features, polish, or quality-of-life requests.
No screenshots in the slash command itself — drop those in the support server if you have them.
How to use
/feedback bug
/feedback idea
Each opens a modal with a few fields. Fill it in and submit; you'll get a confirmation reply with a tracking number.
Common questions
Q: Do I get a reply when the bug is fixed?
A: Sometimes. High-impact bugs that affect many leagues get a follow-up DM when shipped. For everything else, watch the support server's #changelog channel — fixes are announced there.
Q: My idea is half-baked. Submit anyway? A: Yes. Rough ideas are still useful — they reveal what users want even when the implementation isn't obvious. The team prefers seeing the friction in your own words.
Q: I want to attach a screenshot or a log. A: The slash modal is text-only. After submitting, drop the screenshot in the support Discord with your tracking number — the team will link them up.
Q: How is this different from /support?
A: /support is the invite to the live support server (back-and-forth conversations). /feedback is a one-shot drop into the queue without joining anything. Use whichever fits your moment.