How To Write Receipts That Survive The Salt
A funny but fair guide to turning a messy Smite 2 match into a useful report that shows behavior, context, and proof without turning into revenge spam.
Receipts Beat Rage Every Time
A salty match can make anyone type like a haunted vending machine. The mid is yelling. The support is pinging like they discovered electricity. Someone has decided that walking directly into danger is their new religion. You want to post the whole disaster, roast the lobby goblin, and let the internet handle the rest.
Take ten seconds first.
A good report is not just a scream with screenshots attached. A good report is a clean little case file. It shows what happened, when it happened, why it mattered, and what proof supports it. That does not mean the report has to be boring. This site is allowed to have teeth. It can be funny, sharp, and brutally honest about bad lobby behavior. The trick is making the receipts stronger than the salt.
If the evidence is clear, people can judge the behavior without needing a wall of rage. If the evidence is sloppy, even a real troll can hide behind confusion. The goal is simple. Make the nonsense easy to understand and hard to wiggle out of.
Start With The Match Story
Before posting, write the match story in plain language. What mode was it? What role did the player pick? When did the behavior begin? Was it one angry message after a lost fight, or a full match pattern of feeding, refusing to group, griefing objectives, or turning chat into a sewer?
Context matters because not every bad game is a troll game. Everyone has missed abilities. Everyone has made a terrible rotation and instantly regretted it. A useful report separates normal bad play from behavior that looks intentional, abusive, or destructive.
Try this format in your head before writing the public report.
1. The match started normally. 2. The player began causing problems after a specific moment. 3. The behavior repeated more than once. 4. The screenshots or clips show the pattern. 5. The report focuses on what they did, not on private details or real world identity.
That structure keeps the report readable. It also keeps the roast aimed at the behavior. Clown shoes in the lobby are fair game. Real life hunting is not.
Show The Pattern, Not Just One Explosion
One screenshot can be useful, but a pattern is stronger. If someone types one rude line after a bad fight, that might be tilt. If they spend the next twenty minutes feeding, blocking surrender discussion with spam, blaming everyone else, and refusing to play the objective, now there is a story.
The best receipts show sequence. A chat screenshot, then a scoreboard moment, then another chat line, then the final damage or objective screen can explain more than a giant angry paragraph. You are not trying to win a courtroom drama. You are trying to show other players why the behavior made the match worse.
Keep the proof focused. Crop out private messages that do not matter. Do not include personal information. Do not post anything that pushes people toward harassment. A strong report does not need that garbage. The game behavior is the evidence.
Write Like A Witness With Jokes
The tone can be spicy without becoming useless. Good lines make people read. Clear facts make people believe.
Instead of writing that a player is the worst human alive, write that they spent the final ten minutes orbiting fountain like a decorative statue while the rest of the team tried to defend Fire Giant pressure. That is funny, specific, and tied to match behavior.
Instead of saying they ruined everything because they are trash, say that after the first lost team fight they stopped rotating, typed blame messages, and ignored every objective call. That gives readers something real to evaluate.
Comedy works best when it points at the obvious absurdity. The player who rage pings after diving alone into four enemies is already writing the joke for you. You just have to document it.
Keep Names And Claims Clean
A report should use the public gamer tag or in match name that is relevant to the behavior. It should not hunt for social profiles, phone numbers, addresses, workplaces, family details, or anything outside the game. That crosses from accountability into creep behavior, and nobody needs that.
Also be careful with claims you cannot prove. If you do not know someone was cheating, do not label it as proven cheating. If the proof shows griefing or abusive chat, say that. If it only looks suspicious, say what looked suspicious and let the evidence speak.
This keeps the site useful. It also keeps the focus where it belongs, on lobby conduct and match quality.
End With What Other Players Can Learn
The best reports do more than dunk on one troll. They teach the community what to watch for. Maybe the lesson is to save screenshots before chat scrolls away. Maybe it is to record a short clip when a player begins repeated fountain idling. Maybe it is to avoid feeding the drama in chat because the troll wants attention more than victory.
A useful report can end with one practical note. Report through the game tools. Mute when the chat becomes a sewage pipe. Keep playing if the match is still winnable. Save proof if the behavior becomes a pattern. Do not let one lobby goblin turn five players into five more problems.
That is how receipts survive the salt. Not by pretending the match was pleasant. Not by writing a fake polite essay. By showing the mess clearly, laughing at the nonsense, and keeping the proof clean enough that the troll cannot hide behind chaos.
Bad games happen. Bad behavior gets documented.