Quick answer: Frustrated players file many reports in rapid succession. Cool-down periods (30 seconds between reports) prevent spam without losing signal.

Spam-filing reports doesn't help engineering. Cool-downs balance.

30-second cooldown

UI disables for 30s after submit. Players cool off; second report comes with more thought.

Or rate-limit at SDK

Per-session rate cap. Excess queued; submitted with delay.

Empty-report bypass

If player wants to submit an additional file (screenshot), skip cooldown. Genuine multi-step report.

Discord-only for instant

Frustrated players go to Discord. Bugnet is for deliberate; Discord is for raw.

“Cool-downs filter spam. Spam is the silent majority of report flow.”

If your team is drowning in reports, the cool-down is one of several throttling strategies. Document.

Related reading