Report a problem
Reach organizers about a broken challenge or platform issue.
Something looks broken? A flag that won’t validate, files that won’t download, a page that errors out? There are two ways to reach the organizers: in-app reports (always available) and, if your event runs a Discord server with the Athena bot, a Discord ticket.
Report a broken challenge
On the challenge’s page, click the Report button next to the difficulty badge. The Report challenge dialog asks what’s wrong, with ready-made reasons:
- Flag does not work or was rejected incorrectly
- Challenge instance / environment will not start
- Description is wrong, missing, or confusing
- Downloadable files are missing or broken
- Offensive or inappropriate content
- Something else…
Pick one, optionally add details such as steps to reproduce, error messages, or anything else organizers should know, then hit Submit report. Details are required if you chose “Something else…”.
Report a platform issue
For problems that aren’t about one challenge (login trouble, a slow site, wonky rankings), open your avatar menu and choose Report a problem. This dialog first asks which area is affected (login/account, challenge list, challenge pages, leaderboard, profile/settings, speed/errors, announcements, or other), then offers reasons matched to that area, plus the same free-text details.
Follow up in My reports
Your avatar menu’s My reports page tracks everything you’ve sent, with All / Open / Closed tabs. Each report is a thread: your original submission, any updates you’ve added, and organizer replies (marked Organizer, with a wrench icon).
- While a report is open, you can keep the thread current with Add an update: a reason plus new details.
- If you report the same challenge (or the same platform area) again while a report is open, your new submission is added to the existing thread. You never end up with duplicates.
- In-app reports send no notification when an organizer replies; check My reports for responses.
When organizers close a report, its status badge tells you the outcome: Resolved, Closed as duplicate, Not actionable, or simply Closed. Resolved reports come with an organizer message on the thread explaining the fix. Closed threads are read-only; if the problem comes back, open a new report.
Open a Discord ticket
If your event’s Discord server runs the Athena bot, a ticket is the second way to reach the organizers. Press Open a ticket on the panel in the tickets channel; you need a linked account first. The bot asks:
- What it is about: a challenge, or the site itself.
- Which one: the challenge, or the area of the site.
- What went wrong: the same reasons the in-app form offers.
- Details: what happened and what you tried.
Submitting creates a private thread visible only to you and the staff, and files the same report you would have filed in the app, so it also shows up under Reports on the event site. Anything you write in the thread is added to the report, and organizer replies from the site appear in the thread.
Details are optional unless you picked Something else…, where they are required. That is the same rule as the in-app form.
You can have one open report per challenge or area at a time, counting the ones you filed on the site. If one is already open the bot links its thread, or points you back to the site when the report started there. Closing the thread with its Close button locks and archives it; the report stays open until an organizer resolves it.
The challenge picker lists up to 25 live challenges, so file from the site if the one you want is missing.