Skip to main content
As a player, you cannot file a dispute directly — only your team manager can do that. But you play a crucial role in the process: gathering evidence, communicating what happened, and acting quickly before the dispute deadline passes.
Disputes must be filed within 24 hours of the result being submitted. After that, results auto-confirm and cannot be changed without staff intervention. Tell your manager immediately if something went wrong.

​
Your role in a dispute

What you doWhat your manager does
Screenshot the scoreboardGo to the match page
Save the replay fileClick Dispute Result
Tell the manager what happenedFill in the dispute form
Be available for staff questionsSubmit evidence and communicate with staff
The faster you get information to your manager, the better the chances of a successful dispute.

​
Step 1: Gather evidence immediately after the match

Do not wait. As soon as you suspect something is wrong, collect:
1

Screenshot every game's final scoreboard

At the end of each game in the series, press your screenshot key (F12 in Steam by default, or your platform’s equivalent) while the scoreboard is visible. This captures the score and all player names.Example Rocket League end-of-game scoreboard screenshot showing team scores and player stats
2

Save your replay files

Do not close Rocket League until you have located the replay files. See Uploading Replays for the file location. Note which replay file corresponds to which game.
3

Note what went wrong

Write down clearly:
  • What the actual score was for each game
  • What the opposing team submitted (if you can see it)
  • The name of any ineligible player you noticed
  • The time the issue occurred
4

Contact your manager on Discord immediately

Send a message with all of the above. Include your screenshots and replay files (upload them to Discord or a shared Google Drive folder).

​
When a dispute is appropriate

Your manager should file a dispute if:
  • The submitted score does not match what actually happened on screen
  • The opposing team used a player who was not on their roster or who was ineligible
  • The opposing team never showed up and the forfeit was not properly recorded
  • The opposing team used prohibited game settings or violated lobby rules
A dispute is not appropriate for:
  • Lag, disconnections, or poor internet on either side
  • You losing a game fair and square but feeling it was unfair
  • Personal arguments or bad sportsmanship (use a Code of Conduct report instead)
  • Things that happened in voice chat or Discord outside the match

​
Timeline and what to expect

Once your manager files a dispute:
  1. The match result is frozen — it will not auto-confirm during review.
  2. Staff review the submitted evidence from both teams.
  3. Staff may contact your manager (and sometimes players directly) via Discord for more information.
  4. A decision is issued — the result is confirmed, corrected, or ruled a forfeit.
Staff aim to resolve disputes within 72 hours. Check the match page for status updates.
Staff decisions are final. If you disagree with a ruling, your manager can request a review via Discord, but reversals require new evidence that was not part of the original dispute.

​
Frequently asked questions

No. Only team managers have the Dispute button on the match page. If your manager is unavailable, try to reach them urgently — the 24-hour deadline waits for no one.
Once confirmed, results are locked. Your manager can contact staff via a support ticket. Staff may be able to review it at their discretion, but this is not guaranteed and is handled case-by-case.
Save all your evidence (screenshots, replays) regardless. If a false dispute is filed, staff will review the evidence from both sides and make a fair decision. Document everything.
If the issue is behavior-related (slurs, harassment, threats) rather than a score dispute, your manager should include that in the dispute description and tag it as a rule violation. Staff handle both score disputes and conduct violations, but they are separate processes.