Did I Throw My Overwatch Game?

What players usually mean by “throwing”

In post-match chat, “throwing” often means far more than intentional sabotage. A player may use it for a rough scoreboard, a painful loss, a teammate who fell behind, or simply the emotional need to find a defendant before the queue pops again. Those are not the same claim.

A final scoreboard can show that one player’s recorded totals were low relative to a team or role comparison. It cannot establish intent, reconstruct every fight, or prove that one person caused a loss. That distinction keeps the joke funny and the review useful: treat “did I throw?” as a scoreboard question, not a verdict on a person.

What the final scoreboard can reasonably show

The useful information is comparative. A single number rarely says much by itself. Your own entries become more meaningful when read beside teammates, beside players in the equivalent enemy role, and beside the other recorded fields on the same board.

Deaths and survival

Deaths are often one of the clearest warning lights because they are visible and easy to compare. A high death total alongside low recorded output is a stronger concern than the same death total alongside substantial contribution. It also helps to compare deaths with teammates and equivalent enemy roles rather than treating a number as a universal rule.

What deaths do not reveal is why they happened. The board cannot show whether a player was isolated, pressured by several opponents, attempting a necessary contest, or caught after the decisive moment. It records the count, not the scene.

Eliminations and assists

Eliminations and assists can indicate recorded involvement in team output. Together, they are often more useful than either alone, particularly when comparing players in similar roles. A very low contribution line relative to nearby teammates may deserve a closer look. It still does not identify final blows, the order of events, or whether an assist arrived in a match-defining moment.

Damage, healing, and mitigation

Damage, healing, and mitigation describe different kinds of recorded output. They should not be stacked into one universal “who played best” ruler. Damage totals can be high without answering how that damage was distributed. Healing may be substantial without explaining every other part of a support line. Mitigation matters for some roles but should not be treated as a universal substitute for the rest of the scoreboard.

The useful question is not “which total is biggest?” It is “does this player’s visible line look unusually weak or unusually strong when compared with relevant teammates and equivalent opponents?”

Check your own line in four steps

1. Find your role.Tank, damage and support boards look different. Only compare like with like.
2. Check deaths first.Are yours clearly higher than your teammates’ and the enemy in your role?
3. Check your role output.Damage for damage players, healing and assists for supports, mitigation and survival for tanks.
4. Look for a pattern.Two or more weak signals together deserve a closer look. One weak signal usually does not.

Use role-aware comparisons

Tanks, damage players, and supports do not produce identical scoreboard shapes. A tank can have mitigation that another role may not show. A support can have healing and assists that require different context. Damage players may have a different balance of eliminations, assists, deaths, and damage. Comparing every role by one column is a quick route to courtroom malpractice.

New to the roles? What tank, damage and support players do explains each one in plain English.

A better final-scoreboard review compares role-relevant output first, then looks at broad signals such as deaths and combat efficiency. An enemy same-role comparison can add context without turning the enemy team into public defendants. DidIThrow judges the uploaded team; opponents are only a reference point for the visible totals.

Why raw totals alone can mislead

Raw totals are summaries, not a replay. They do not show how output was spread through the match, what happened before it was recorded, or what value a particular moment carried. They also cannot make roles interchangeable. A damage total is not automatically comparable with healing, and mitigation is not a direct measure of every contribution a tank made.

One weak field is especially risky evidence. Low healing does not, by itself, explain a loss. High deaths do not, by themselves, explain every death. A lower damage total does not settle a comparison across unrelated roles. Look for a pattern: weak role-relevant output, poor survival, and a meaningful gap against relevant teammates or the equivalent enemy role tell a more coherent scoreboard story than one red number.

So, did you throw?

If your line is a clear relative outlier—especially with high deaths and low relevant output—the scoreboard may provide enough evidence for a playful post-match verdict. If the gaps are small or several players look similarly weak, the fairer conclusion is that the board does not provide one clean scapegoat.

DidIThrow turns that limited evidence into an entertainment-oriented post-match court. Upload a final scoreboard to compare visible team and role signals, get a humorous verdict, and keep the result attached to that match only. The court has no replay footage. It just has receipts.

What to do after a rough game