THE CASE FILE
Who Threw Your Overwatch Match?
The final scoreboard may point to a suspect. It may also show a case with too many fingerprints. Here is how to tell the difference without inventing the missing footage.
Often nobody, or everybody a little. A final scoreboard can point to one player only when their line is clearly worse than their teammates’ and the enemy in the same role on several fields. If the lines are close, it was a team loss.
Start with the right question
“Who threw?” is satisfying because it promises one answer to a frustrating loss. Final scoreboard data is usually better at a narrower question: whose visible, role-relevant line was the clearest relative underperformance? Sometimes that produces a meaningful outlier. Sometimes it produces two suspects. Sometimes it produces a team-wide pile of inconvenient receipts.
That is why a scoreboard review should be about the match’s recorded totals, not a claim about a player’s ability, intent, or character. The funniest court verdict is still not a licence to flame someone in chat, report them without cause, or carry the case into the next game.
Individual underperformance versus a team-wide loss
A clear individual concern usually has contrast. One player’s deaths may be notably higher while their relevant output is lower than teammates and comparable enemy-role players. Their line may be separated from the team in several recorded fields rather than by one isolated total. That pattern gives a final scoreboard a coherent, limited reason to highlight a main suspect.
A team-wide loss looks different. Several teammates may have similar negative signals, several roles may trail their equivalents, or the visible numbers may sit close together with no obvious outlier. In that situation, forcing one “thrower” from nearly flat evidence is less useful than admitting the court cannot find a clean scapegoat.
Neither outcome proves the complete reason for a loss. It only describes the strongest story supported by the final board.
- One line trails on several fields
- The gap holds against the enemy in the same role
- Teammates’ lines look normal
- Several players have weak signals
- Most roles trail their enemy match-ups
- No single line stands out
Deaths are useful, but they need context
Deaths are one of the most readable comparison points on a final scoreboard. More deaths can mean less survival relative to the rest of the team, and high deaths paired with weak output are a stronger negative pattern than either signal alone. Comparing against the equivalent enemy role can also help show whether the gap is broad or role-specific.
But a death count is not a replay. The scoreboard does not say where a death happened, what pressure was present, whether teammates were alive, or what came immediately before it. Do not turn “highest deaths” into a complete explanation. Use it as evidence alongside recorded eliminations, assists, damage, healing, mitigation, and role context.
Judge roles with role-aware evidence
Tanks, damage players, and supports should not be held to identical scoreboard shapes. A tank may show mitigation alongside combat output and survival. A damage player’s visible line may centre on eliminations, assists, damage, and deaths. A support may show healing and assists alongside damage, eliminations, and survival. The meaningful comparison is role-aware, not a contest to find the largest number in any column.
Tank vs tank
Mitigation, deaths and combat output against the enemy tank.
Damage vs damage
Eliminations, assists, damage and deaths against the enemy damage players.
Support vs support
Healing, assists and survival against the enemy supports.
Enemy players are useful as benchmark context, not as public defendants. Looking at the visible tank line against the enemy tank line, or a support line against the enemy support line, can identify a relative deficit. It still cannot determine positioning, target priority, decision-making, communication, ultimate timing, or every reason those totals differ.
How to spot an outlier without overclaiming
- Look for several weak signals together, not one awkward total.
- Compare a player with teammates in relevant roles before comparing unrelated columns.
- Check whether the visible gap is meaningful or whether multiple players have similar lines.
- Use equivalent enemy roles as context, while remembering that the board does not explain the match.
- Keep the conclusion match-specific: “this line looks weak” is not “this person is the problem.”
A scoreboard can support playful labels such as a main suspect, two suspects, or team diff. It cannot prove who made the decisive mistake in a particular fight. The more the verdict depends on an unseen moment, the less the final board can honestly settle it.
Tip: if one enemy hero kept winning fights, the fix is often a hero swap, not a blame thread. Check who counters that hero before the next match.
What a final scoreboard cannot prove
It cannot reveal positioning, ultimate usage, rotations, objective timing, peel, space creation, clutch moments, communication, missed shots, target priority, or decision-making. The scoreboard also isn't a reason to attack someone in chat. A scoreboard-based court is for a laugh and a useful review—not a reason to attack a teammate.
Put the scoreboard on trial, not the people
DidIThrow compares the uploaded team’s visible final-scoreboard signals, with enemy same-role totals used only as context. It turns the result into a humorous, evidence-themed verdict: maybe there is a clear outlier, maybe there are two, or maybe the numbers point to a broader team problem.
The court is deliberately ridiculous. The evidence is limited. Keep both facts in view, upload the final board, and let the numbers have their short hearing without making the queue worse for everyone else.