Player Reports

Player Reports

Player reports let any logged-in user report another user for bad behavior (a "bad actor" report). They share the ticket infrastructure behind Bug Reports but are a distinct flow: a report targets a specific user, carries a reason, and lands in a shared moderator queue. The reported user never sees the report.

Filing a player report

A Report action appears wherever you encounter another trainer: their trainer profile, the social and friends pages, and inside a Raid Finder lobby. It opens a form with:

• A reason: GPS spoofing, botting / automation, harassment, hate speech, threats / safety, scam / fraud, impersonation, inappropriate username, inappropriate profile, spam, or other.
• A details field (up to 4000 characters) describing what happened.

You cannot report yourself. If you already have an open or pending report against the same user, filing again reuses that existing report instead of creating a duplicate.

What happens next

• The report is filed with subject Player report: @username (reason) and routed to a shared moderator bucket: every moderator can see it. If there are no moderators it falls to admins, and failing that to the superadmin.
• You are added as the reporter and can keep talking to staff in the thread, exactly like a bug report. The reported user is never a participant and is never notified.
• Staff are pushed a "New player report" notification when push is configured.

Staff handling (admin panel)

Moderators and admins get a separate Player Reports tab in the admin panel:

• Reports land in the shared bucket so every moderator sees them. Self-assign to take ownership; "Assigned to me" is your working queue.
• Triage uses the same thread, reply, internal-note, priority, and label tools as bug reports.
• Enforcement (strikes, raid bans, disabling an account) is carried out in the Users tab. Once a player has been dealt with, use Resolve (action taken) on the report to close it and thank the reporter (a push and a public thread message are sent).

For self-hosters

• Player reports need migration section 41 (see Database Guide), which adds a type discriminator, reported_user_id, and reason to bug_reports. Sections 39 and 40 (the bug report tables) must be applied first.
• See API Reference for the endpoints and Admin Guide for the triage workflow.