Review bombing works through coordination, not volume alone. A group agrees on a trigger, posts negative reviews as close to simultaneously as it can manage, and lets the arithmetic of a rating average do the rest. The detail most people miss: on Steam, whether those reviews actually count depends entirely on whether they are about the game.
This guide explains how review bombing works from a player’s perspective, where a coordinated campaign ends and ordinary organised criticism begins, and what developers and players can realistically do about it.
Table of Contents
- 1How Review Bombing Works
- 2What Counts as Review Bombing?
- 3Why Gamers Use Review Bombing
- 4How Coordinated Ratings Affect a Game
- 5How Platforms Detect and Respond to Review Bombing
- 6Review Bombing vs. Ordinary Negative Reviews
- 7The Difference Between Review Bombing, Brigading, and Astroturfing
- 8What Developers and Publishers Should Do
- 9What Players Can Do About Review Bombing
- 10Frequently Asked Questions
- 11Is review bombing legal?
- 12What happens when a game gets review bombed?
- 13Can developers remove negative reviews?
- 14Does one person posting several ratings count as review bombing?
- 15How can I report coordinated or fake reviews?
- 16Why do platforms sometimes delay changing a review score?
- 17What to Do First
How Review Bombing Works
The basic sequence takes hours, not days. Organisers pick a channel first, usually a Discord server, a subreddit, or a Steam Community discussion thread, and settle on a target and a deadline. In the Steam Community threads around Team Fortress 2 and Warhammer 40,000, campaigns were not covert at all. People posted progress trackers like “nearly down to 60 percent, let’s keep it going” while the campaign ran.
Once the trigger lands, participants buy, activate, and post within the same narrow window. The window matters more than the headcount, because a rating average is weighted by how many reviews land and when. A thousand negative reviews spread across a year barely register. A thousand inside forty-eight hours can flip a store page from Mostly Positive to Mixed.
Campaigns also time themselves against how the platform calculates a score. On r/TheBazaar, organisers openly advised timing around the fact that Steam’s “Recent reviews” label only covers roughly the last 30 days. Aim at that window and you damage the number buyers actually see.
Nobody has to have played the game. Accounts that never activated a key can still leave a review, which is why playtime is one of the strongest tells when you are reading a histogram yourself.
What Counts as Review Bombing?
Review bombing is a coordinated flood of negative ratings posted by people who agreed to do it, aimed at a specific target, within a short window, for a reason that is usually not the quality of the product. Coordination is the whole test. Thousands of players independently disliking a bad launch is not review bombing, however ugly the chart looks that week.
Not everything that looks like a bomb is one. A game with genuine bugs, poor performance, and a rough first week can post several hundred negative reviews with no organiser anywhere in sight. The clearest counter-example is the r/IndieDev AMA where the SEDAP! studio described launching to 60% Mixed, absorbing real bug and balance complaints mixed with personal attacks, then climbing to about 69% after a year of patches and a 1.1 update. The developer later corrected himself for using the term too loosely. That was an organic launch failure, not a campaign.
Why Gamers Use Review Bombing
Outrage is the most common driver. Players are angry about something that is not the game itself: an account-linking requirement, exclusivity on another store, a pricing change, a sequel, or a corporate decision that has nothing to do with the build in front of them. The rating box is the only lever most of them have.
Other motives show up regularly. Some campaigns are punishment for perceived misconduct. Some want visibility for an issue the developer has ignored. Some are culture-war or identity-based harassment aimed at a person rather than a product. A few are financial pressure dressed up as outrage, where the real goal is a public reversal.
Players defending the practice argue that the review score is the only channel that reaches decision-makers, and that coordinated ratings are the closest thing a community has to a vote. Critics answer that punishing an entire player base for one executive decision teaches companies that the cost of ignoring players is a cratered storefront, and that the people who never buy the game pay the price for those who do.
How Coordinated Ratings Affect a Game
A Steam score is a percentage of positive reviews, and every review moves that percentage by one review’s worth of weight. A game sitting at 4,000 reviews and 80% positive has 800 negative reviews. Swallow 2,000 more negative ones and the same game lands near 57%, which reads as Mixed. No change to the product, no change to the players who already liked it, entirely different impression.
Steam shows two figures, and people confuse them constantly. The recent label covers a rolling window of roughly 30 days, so a bomb damages it fast and it recovers fast once the flow stops. The lifetime score keeps every review that was not excluded, which means an on-topic bomb stays in the number for good. Players watching a scoreboard see a crash and a slow, grinding repair. Shoppers reading a store page see a wrecked average that never resets.
Visibility effects sit on top of that, and how big they are depends on the platform’s own weighting. Store search and recommendation systems lean on review score heavily, so a cratered page gets less traffic, which means fewer organic reviews arrive to replace the bomb, which drags the score further. Community threads on r/newworldgame and r/Steam put it more bluntly: people who have worked with studios say an organic wave does the real damage, because a bomb mostly produces noise that filters out and a bad launch produces customers who refund.
How Platforms Detect and Respond to Review Bombing
Platforms do not publish a complete detection method, and the ones that do change their behaviour over time. What is consistent across the major storefronts is the set of signals they look for: a sudden spike in ratings far above a title’s normal volume, clusters of accounts sharing devices or payment details, identical or lightly edited wording across many reviews, links or campaign language repeated in the same window, and traffic patterns that arrive in one block rather than trickling in.
Steam is the most documented case. In 2017 Valve added the review histogram, showing the pattern of daily positive and negative reviews, so the shape of a bomb became visible instead of inferred. In March 2019 Valve added off-topic exclusion: when staff or the automatic system identifies a burst of reviews that are not about the game, that date range is marked, the reviews stay visible but stop counting toward the score, and players and developers can opt in or out of exclusion for that window.
The off-topic test is the entire ballgame. A campaign triggered by an account-linking requirement, a store exclusivity, or a political grievance is off-topic and gets excluded. A campaign triggered by what is actually in the build is on-topic and keeps counting, no matter how coordinated or how angry it is. Players on r/Steam describe the frustration clearly: the system reads as a loophole precisely when the complaints are legitimate.
Later changes adjusted how much individual reviews count, weighting language and filtering spam-like text, though how much that affects bombing specifically is still argued over in community discussion. Elsewhere, the response set includes filtering, individual review removal, account or device restrictions, and appeals through developer support channels. Amazon, Goodreads, IMDb, Rotten Tomatoes and the mobile app stores all run variations of this, with reporting handled through their own violation forms.
Review Bombing vs. Ordinary Negative Reviews
The distinction is easy to state and easy to get wrong, because a bad launch and a bomb can land on the same week.
| Signal | Review bombing | Ordinary negative reviews |
|---|---|---|
| Coordination | Organised in advance on a forum, Discord or thread | No organiser; players react independently |
| Timing | Clustered into hours or a couple of days | Spread across the weeks after launch |
| Repetition | Repeated phrasing, links, or near-identical text | Distinct accounts, distinct writing |
| Intent | Targets a decision or a person, not the build | Targets the build |
| Evidence | Little or no playtime, no key activation, single-day cliff in the histogram | Hours logged, specifics about bugs or balance |
| Right response | Report for coordination, do not argue in the thread | Take it at face value and fix what it describes |
A single critic reviewing a game they own, with forty hours logged and three specific complaints, is doing the opposite of bombing. A hundred accounts with zero playtime, all filing negative reviews within the same afternoon over a corporate announcement, is bombing. Nothing about the volume matters; the coordination does.
The Difference Between Review Bombing, Brigading, and Astroturfing
The three terms get used interchangeably and they are not the same thing. Review bombing is the act and the method: a flood of negative reviews aimed at one target. Brigading is the mobilisation itself, organised outside a platform’s own systems, and brigading is how most review bombs are delivered. You can brigade something without writing reviews, and you can review bomb through accounts you own personally without anyone calling it a brigade.
Astroturfing is broader again. It describes public opinion that looks organic but was manufactured, paid for, or coordinated to look spontaneous. A campaign where participants are told exactly what to say is astroturfing whether or not anyone is technically organising it on a Discord server.
The overlap is real: a review bomb can be a brigade, it can be astroturf, and it can be a legitimate protest at the same time. That last case is the hard one, and it is why the argument about review bombing rarely ends with agreement.
What Developers and Publishers Should Do
Start with evidence, because reporting without it stalls. Screenshot the histogram, note the dates and the volume spike, save the threads where the campaign is being organised, and record review text that repeats across accounts.
Then report through the platform’s own process rather than arguing in the thread. Steam developers go through Steamworks partner support, and reviewers go through the report button. Expect it to take days. Borderlands 2 sat cratered for roughly five days before the exclusion landed, which is a normal timeline, not a failure.
Do not retaliate in the review threads. The near-universal advice from developers in forum threads is that arguing back attracts more attention to the page without changing any score. Buying reviews is also a non-starter: it breaks platform terms, it corrupts the same average you are trying to protect, and it is exactly the behaviour that makes off-topic exclusion harder to argue for.
Separate the signal from the noise. Personal attacks go to the harassment report. Bug reports, balance complaints and performance issues are not part of the bomb, and treating them as such is the mistake that costs studios a year of goodwill. Document every platform decision, keep responding to valid criticism in your own channels, and correct misinformation with facts instead of counter-attacks.
What Players Can Do About Review Bombing
Review what you actually played, in your own words, with the detail that makes a review useful. Playtime and specifics are the cheapest defence against manipulation, because a campaign cannot fake them in bulk.
Report coordination rather than arguing about it. If you are watching accounts with no playtime file near-identical reviews inside an hour of a public announcement, that is the thing to report, and the evidence helps.
Do not amplify the campaign by reposting the thread or the screenshots. A bomb needs attention to become a headline, and a headline pulls in people who have never played the game. Equally, do not treat every angry review as an attack: on-topic criticism from someone who bought the game is the system working, and it is usually the most useful thing on the page.
Frequently Asked Questions
Is review bombing legal?
Posting a negative opinion is generally protected, so a review bomb is rarely illegal on its own. It becomes a different matter when it breaks a platform’s terms of service, when it misrepresents your experience with a product in a way that violates the FTC’s Endorsement Guides, or when the campaign’s real goal is a public reversal, which can read as extortion or harassment. Rules differ by country, so treat this as general information rather than legal advice.
What happens when a game gets review bombed?
Its review percentage drops sharply, usually within hours, and the recent label flips from Mostly Positive toward Mixed or lower. If the campaign is off-topic, Steam can exclude that date range and the score recovers. If it is on-topic, the reviews keep counting against the lifetime score permanently. Store visibility falls with the score, and the developers spend weeks answering the same thread.
Can developers remove negative reviews?
No. Developers cannot delete, hide or cap incoming reviews, which is the single most common complaint in developer threads. What they can do is report suspected coordination through Steamworks partner support, appeal a decision, and respond in their own channels. Individual reviews can be removed by the platform when they break content rules, but that is a review-by-review decision rather than a developer tool.
Does one person posting several ratings count as review bombing?
Rarely, on its own. Review bombing is defined by coordination between multiple people agreeing to act together, so one account posting repeatedly is more likely a spam or ban-evasion issue and belongs under platform anti-spam rules. That said, a ring of accounts run by one person can be treated as a coordinated campaign, and the detection signals, shared devices and identical wording, look much the same.
How can I report coordinated or fake reviews?
On Steam, use the report option on the review itself and flag it as coordinated activity, then include screenshots of the repeated wording and timing in any developer-side report. Other platforms have their own violation forms, and mobile app stores and Amazon both run separate fake-review reporting flows. Screenshots of the histogram plus a saved thread are the two pieces of evidence that move a report forward fastest.
Why do platforms sometimes delay changing a review score?
Because deciding whether a window of reviews is off-topic is a judgement call, not a formula. Steam’s March 2019 system combines automatic detection with staff review, and staff have to read the reviews to decide whether they are about the game or about a corporate decision outside it. Developers report waiting several days for that decision, which is why a cratered page often sits there before anything changes.
What to Do First
Before anything else, decide honestly whether you are looking at a coordinated campaign or a genuinely angry player base. The histogram shape, the playtime on the accounts and whether anyone is organising in public will usually answer that in a few minutes.
If it is a bomb, screenshot everything, report it through the platform’s process, and say nothing in the thread. If it is real criticism, then it is not a bomb, and the only useful response is to fix what people are describing. That single distinction explains how review bombing works, when the platforms catch it, and why so many launches that looked like bombs turned out to be something else entirely.
