At 2am on a Saturday, 47 negative reviews hit your game in three hours. By the time you wake up, your score has dropped from 78% to 71%, right at the edge of losing "Mostly Positive." Two more hours pass. It hits 69%. You are now "Mixed."
Your store visibility just tanked. Your conversion rate may have halved.
This is not hypothetical. In May 2024, Helldivers 2 received over 200,000 negative reviews in three days after Sony announced mandatory PSN account linking. In May 2023, War Thunder hit "Overwhelmingly Negative" with 98,000 negative reviews after economy changes. In June 2017, GTA V dropped to "Mixed" after nearly 50,000 negative reviews over the OpenIV modding tool shutdown.
What separates a game that recovers in days from one that takes months? What the developer does in the first 60 minutes.
What qualifies as a review bomb
A review bomb is an abnormal spike in negative reviews over a short period, where the negativity is coordinated or collective rather than individual players reacting on their own.
What is not a review bomb:
- A bad patch that genuinely upsets individual players over several days. That is feedback.
- A gradual decline in reviews after the honeymoon period. That is natural entropy.
- A handful of angry reviews clustered around a controversial update. That is a spike, not a bomb.
The distinction matters because how you respond depends on the type. Treating legitimate player frustration as a "review bomb" makes you look dismissive. Treating an actual coordinated attack like normal feedback wastes your time on bad-faith actors.
The three types of review bombs
Type A: Controversy-Driven
Something external to the game triggers a wave of negativity. A developer makes a controversial public statement. A publisher makes a business decision players disagree with. An industry controversy pulls your game into the crossfire.
You can spot these because many reviewers have low playtime or have not played recently. Reviews rarely mention specific gameplay, and the language is all about the controversy, not the game.
- Firewatch (September 2017): Developer Campo Santo issued a DMCA takedown against PewDiePie's videos after he used a racial slur on stream. PewDiePie's fanbase retaliated by review bombing Firewatch. The reviews had nothing to do with the game itself.
- Borderlands series (April 2019): After 2K announced Borderlands 3 as an Epic Games Store exclusive, players bombed Borderlands 2 and The Pre-Sequel on Steam, even though those games had nothing to do with the exclusivity decision. Borderlands 2 received roughly 1,600 negative reviews in two days.
Type B: Update Backlash
The developer ships an unpopular change: a bad patch, a monetization increase, a removed feature, a mandatory third-party account link. Players respond en masse.
These look different from controversy bombs. Reviewers have significant playtime. Reviews cite specific changes. The anger is about a concrete decision, not an abstract controversy. This is real feedback, just a lot of it at once.
- Helldivers 2 (May 2024): Sony mandated PSN account linking for PC players, which would have locked out players in 177 countries where PSN is unavailable. Over 200,000 negative reviews in three days. The game dropped from Very Positive to Mixed.
- War Thunder (May 2023): Gaijin Entertainment released economy changes that increased premium prices, repair costs, and ammo costs. The game hit Overwhelmingly Negative with 98,000+ negative reviews in one week, with only 7% of recent reviews positive.
- GTA V (June 2017): Take-Two issued a cease-and-desist against OpenIV, the primary single-player modding tool. Nearly 50,000 negative reviews poured in. The game dropped from Positive to Mixed.
Type C: Brigading
An external community (a rival game's fanbase, a forum, a streamer's audience) coordinates an attack on your game's reviews. The motivation may be personal, competitive, or purely for entertainment.
These are tricky. You will see a mix of real players and accounts with minimal game libraries. Reviews often share similar language or meme references. Accounts may be recently created. These are harder to identify and harder to fix than Types A or B.
The first 60 minutes
Minutes 0-15: Detect
You need to know something is happening. Monitor your review velocity, which is just the number of new reviews per hour compared to your baseline.
- Normal day: 5-15 reviews, spread across 24 hours.
- Something is off: 20-30 reviews in a single hour.
- Review bomb: 50+ reviews in an hour, or 3-5x your daily total in a few hours.
If you do not have automated monitoring, you are finding out about this when you check Steam manually, which might be hours or days after the bomb starts. By then, the damage is done and you are playing catch-up.
Minutes 15-30: Assess
Read 10-15 of the new reviews. You are trying to answer three questions:
- What are they about? Specific gameplay complaint? External controversy? Coordinated memes?
- Who is writing them? Check reviewer profiles. High playtime = real players. Low playtime or minimal game libraries = potential brigading.
- What type is this? Type A (controversy), Type B (update backlash), or Type C (brigading)?
Also check your exposure. Where is your score now versus 6 hours ago? How close are you to a tier cliff? If you are at 72% and dropping, you have a narrow window before you hit 70% and lose Mostly Positive.
Minutes 30-60: Pick your response
Your response has to match the type. Do not skip this step. Responding to a Type A bomb like a Type B (or vice versa) will make things worse.
How to respond, by type
If Type A (controversy): hold back
- DO NOT respond to individual reviews. It only feeds the outrage cycle.
- DO NOT engage with the controversy directly on Steam.
- DO post ONE measured community announcement that addresses the situation with facts. Keep it short and honest.
- DO report reviews that clearly violate Steam's guidelines (spam, hate speech, reviews from non-owners).
- WAIT for Steam's off-topic review filter. Since March 2019, Valve has a system that detects anomalous review activity and flags it for human review. If the bomb is determined to be off-topic, those reviews will be excluded from your score.
Controversy bombs typically peak and fade within 48-72 hours. Time is on your side here. The Borderlands 2 bomb was caught by Valve's off-topic filter within days, and the game's score reverted to pre-bomb levels.
If Type B (update backlash): engage directly
This is legitimate feedback. Treat it that way. The worst thing you can do is dismiss real players as "review bombers."
- Post a community announcement that names the specific complaints. Be concrete about what you heard.
- If the update was a mistake, say so. Commit to a rollback or fix with a specific timeline. Gaijin reverted War Thunder's economy changes within 3 days and followed up with a detailed roadmap. That combination of fast action and a clear plan worked.
- If you stand behind the change, explain why. Why did you make this decision? What problem were you solving? Respect the players enough to give them the real answer.
- Respond to individual reviews. This is where the 21.6% flip rate is your main tool for recovery. Acknowledge each player's specific complaint, reference what you are doing about it, and give them a reason to come back.
The best example of this done right: Arrowhead's CEO responded to the Helldivers 2 bomb by saying "I guess it's warranted. Sorry everyone for how this all transpired. I hope we will make it up and regain the trust." No blame. No defensiveness. Sony reversed the PSN requirement within 3 days. Players then flooded the game with over 200,000 positive reviews in a counter-campaign they called "Operation Clean-Up."
If Type C (brigading): document and report
- Document everything. Screenshot patterns in reviews, note account characteristics, record timing.
- Report to Steam Support with your evidence of coordinated inauthentic behavior.
- Post a brief community message: "We are aware of a pattern of reviews that appear to be coordinated from outside our player community. We are working with Steam to investigate."
- DO NOT engage with individual brigade reviews. That is what they want.
- DO respond to legitimate player reviews that may be mixed in with the brigade.
Writing the community post
Your community announcement is the single most important thing you will write during a bomb. Get it right.
For a controversy bomb, keep it short and factual:
"We are aware of the recent wave of reviews related to [situation]. We want to address this directly: [factual statement, 2-3 sentences]. Our focus remains on building the best game we can for our community. We value every player who engages with [Game Name] based on the game itself."
For an update backlash, lean in:
"We hear you. The response to [update/change] has been loud and clear. Here is what happened: [explain the reasoning, briefly]. Here is what we are doing about it: [specific actions with timeline]. We are reading every review and will be responding individually over the coming days."
The difference matters. Type A keeps distance from the controversy. Type B leans into the feedback and shows concrete action. Mix them up and you will make things worse.
What not to say during a review bomb
Some things make any bomb worse, no matter the type:
- "This is just a review bomb". Even if true, this sounds dismissive. It tells players their feedback is illegitimate.
- "You only have 2 hours played". Gatekeeping who gets to have an opinion always backfires publicly.
- "We'll just ignore the haters". Alienates everyone, including moderate critics who had legitimate points.
- Anything passive-aggressive or sarcastic. You are not writing for the person who bombed you. You are writing for the thousands of potential buyers who will read your response later.
- "This makes me kind of happy". Gearbox CEO Randy Pitchford's response to the Borderlands review bomb is a textbook example of what not to say. It came across as contemptuous and dismissive of the entire playerbase.
Recovery after the bomb
Week 1: Stabilize
- Continue responding to all legitimate reviews using the ARAK framework.
- Ship the hotfix or rollback if applicable.
- Post daily community updates on progress. Silence after the first announcement erodes trust fast.
Weeks 2-4: Rebuild
- The 21.6% flip rate is your best weapon now. Respond to every negative review from the bomb that contained legitimate feedback.
- Reference specific fixes or changes in each response.
- Ask (but do not demand) reviewers to reconsider after trying the fix. "We shipped a fix for [their complaint] in patch [X]. Would love to hear if it works better now."
Months 2-3: Let organic reviews do the work
- New positive reviews from organic players begin outweighing the bomb reviews.
- Continue the daily response routine to keep the score climbing.
- Track weekly: is your score closing the gap to your pre-bomb tier?
The Helldivers 2 recovery shows what good looks like: the developer acknowledged the problem immediately, the publisher reversed the controversial decision within 3 days, and the community launched a counter-campaign of positive reviews. Total recovery time: roughly 2 weeks to return to Mostly Positive overall.
Set up monitoring before it happens
You cannot prevent review bombs. You can only detect them early and respond fast. The studios that survive them had monitoring running before anything went wrong.
At minimum, you want four things running before a bomb hits:
- Review velocity alerts that fire when review volume exceeds 2-3x your normal daily rate.
- Sentiment tracking that tells you whether incoming reviews are running positive or negative.
- Tier proximity tracking so you know exactly how many negative reviews you can absorb before dropping. If you are at 72% with 1,000 reviews, you can calculate that buffer precisely.
- Alerts that work outside business hours. Review bombs do not happen 9-to-5. The Helldivers 2 bomb started on a Friday. If your monitoring goes dark on weekends, you are exposed.
The studios that get blindsided are the ones checking reviews manually, once a day, during work hours. By the time they notice, the damage is already baked into their score.
Run a free review audit to see your current tier, how much buffer you have before the next threshold, and which way your sentiment is trending.