A review bomb is a race between your response and the review score math, and most developers lose the first 24 hours because nobody was watching. By the time a friend texts you a screenshot, the reviews have been stacking for half a day and the story is being written by everyone except you.
Here is the incident-response playbook for the first 48 hours.
What Actually Counts as a Review Bomb?
Valve's working definition, from its March 2019 announcement, is "anomalous review activity": a large volume of reviews landing in a short window, far off the game's normal pattern.
Your working definition is baseline. 2-3 reviews on a normal day and 40 negatives in 6 hours is a bomb; a patch that corrupts saves drawing 15 accurate, furious reviews overnight is feedback arriving at volume.
The branch that decides everything: off-topic bombs (publisher drama, store exclusivity, a developer's tweet) Valve can neutralize; on-topic bombs (a broken patch, a price change, an account requirement) count in your score, and nobody is coming to save you.
What Valve's Off-Topic System Does (and Does Not) Fix
Since March 2019, Valve runs a tool that watches review activity across Steam in close to real time. When it flags an anomaly, a human team investigates. If they judge the incident off-topic, they mark the time period, notify the developer, and reviews inside that window stop counting toward the score by default.
3 things developers get wrong about this system:
- The reviews do not disappear. They stay visible on your page and in the review graph, marked as excluded. The tool protects the number, not the vibe.
- Players can opt out. A checkbox in Steam's store options lets any user include off-topic periods in the scores they see.
- "Off-topic" is Valve's call, not yours. Controversially, the 2019 announcement classed even DRM and EULA changes as off-topic. Anger about gameplay, pricing, bugs, or account requirements counts in full.
The takeaway: mad at your publisher, the system may bail you out; mad at your game, the rest of this post is your only tool.
3 Review Bombs and What They Teach
GTA 5 and OpenIV (June 2017): reverse the trigger, end the bomb
Take-Two hit the OpenIV modding tool with a cease-and-desist on June 5, 2017. When the tool announced its shutdown on June 14, GTA 5's Steam reviews collapsed into negative territory and a restore-the-tool petition passed 77,000 signatures. Within days, Rockstar said single-player, non-commercial mods would generally be left alone, and OpenIV returned.
The lesson: when the trigger is a business decision players read as hostile, the cheapest fix is reversing it. The policy changed, so the bombing stopped.
Borderlands 2 (April 2019): when Valve steps in
After Borderlands 3 went Epic-exclusive for 6 months, players bombed the older games instead: nearly 1,600 negative reviews hit Borderlands 2 in about 2 days, per Kotaku. Roughly 2 days in, Valve's then-new system marked the period off-topic and neutralized the score impact.
The lesson: when the anger is not about your game, Valve handles the number. But the angry reviews stayed visible and highly upvoted, so "Valve fixed it" is never the whole story.
Helldivers 2 (May 2024): the fastest recovery arc on record
Sony announced on a Friday that all Steam players would soon be required to link a PlayStation Network account. The weekend response was historic: negative review counts ran past 100,000 within days, most tallies eventually topping 200,000, and the game plunged to Mostly Negative recent reviews. On Monday, May 6, 2024, Sony reversed the requirement.
Then the rare part happened. The community organized "Operation: Clean-up," treating review restoration like an in-game mission: more than 70,000 positive reviews landed within days, and the overall score climbed from Mixed back to Mostly Positive the same week.
The lesson cuts both ways: shipping a controversial policy on a Friday with no communication plan donates a weekend to the mob; Arrowhead visibly siding with its players is why the same community came back to repair the score.
The 48-Hour Playbook
Hour 0 to 2: Confirm it is real
Pull your baseline: average daily review count over the last 30 days. A bomb is a multiple of baseline (think 5-10x) with 1-sided sentiment; 2 bad days in a row is not, and treating normal negativity like an incident makes you look thin-skinned.
Check the blast radius: reviews only usually means 1 community; reviews plus Reddit plus YouTube means the story has spread. Screenshot the review graph with timestamps in case you ask Valve to assess the period later.
Hour 2 to 6: Diagnose the trigger
Read 20-30 of the new reviews, sorted by most recent. They will tell you what happened, usually in the first sentence. Nearly every bomb traces to 1 of 4 triggers:
- A patch broke something players loved or relied on
- Pricing or monetization changed in a way that feels like a bait and switch
- A policy decision landed badly: DRM, account linking, regional delisting
- External drama: something said online, an exclusivity deal, publisher behavior
Hour 6 to 12: Decide - respond or wait
Respond publicly if the trigger is real and fixable, or a misunderstanding you can correct with receipts. Wait if you genuinely do not know the cause yet, or if lawyers are involved. But "wait" means actively drafting and watching the spread, never silence past 72 hours.
Your Discord is your early-warning system and pressure valve; a community that hears from you directly bombs less and defends more. The free Discord health check takes 2 minutes.
Hour 12 to 24: Ship the public response
The formats with a track record:
- A Steam announcement (event). Highest reach: followers, store page, and news hub at once.
- A pinned discussion thread. 1 place to answer players instead of 400 review threads.
- The 3-part structure. Acknowledge the specific complaint ("the 1.3 patch broke controller rebinding," not "we hear your concerns"), explain without excusing, commit to a fix with a date.
- If you are reversing a decision, reverse it plainly. Sony's Helldivers walk-back was a few short paragraphs.
Push the same statement everywhere at once: Steam, Discord, X, Reddit, Bluesky. Gamosy's Social Publisher exists for exactly this kind of morning, 1 write-up scheduled across every channel before your coffee goes cold.
Hour 24 to 48: Follow through
If you promised a patch, ship a visible hotfix or a dated roadmap inside this window, even if the full fix takes longer. Update your original announcement with progress; edits read as good faith. And ask nothing of the reviewers: no requested review edits, no hints. Operation Clean-up worked because players started it themselves after the fix shipped.
What Not to Do
- Do not argue in individual review comments. Every heated developer reply becomes a screenshot with more reach than your announcement.
- Do not mass-report the reviews. Reviews that break no rules stay up, and a developer caught trying to silence customers turns a bad week into a news cycle.
- Do not go quiet past 72 hours. The window where "we are investigating" reads as honest closes fast.
- Do not incentivize positive reviews. It violates Steamworks rules on a normal day and is radioactive during a bomb.
The Aftermath: Recent Window Math and the Recovery Arc
Steam shows 2 scores: Overall (lifetime) and Recent, calculated from the trailing 30 days. That window is your recovery clock: if the bombing stops today, every bomb review ages out of Recent within 30 days, and Recent recovers first, as Helldivers 2's did.
Overall is slower, and the math is unforgiving. Start at 500 reviews and 92% positive, add 150 bomb negatives: you are at roughly 71%, Mixed territory. Getting back above 80% takes about 300 new positive reviews, and at typical rates of 30-60 sales per counted review (full math in our first 10 Steam reviews breakdown), that is 9,000-18,000 sales of recovery work. Contain the same bomb at 50 negatives and you never lose the Positive label. That is what the first 48 hours are worth. Run your own scenarios in the free Review Milestone Calculator.
One more lever: if the bombing was genuinely off-topic, ask Valve to assess the period via Steamworks partner support; timestamps and context speed up the review. Do not bother for on-topic bombs, since anger about the product counts, full stop.
Your Clock Starts at Detection
Everything above assumes you noticed the spike early, and that assumption fails constantly. Gamosy's Media Monitoring module went live this week: for your licensed game under Gamosy PRO it watches your review flow and mentions, learns your normal week, and alerts you when the curve breaks. Hour 0 versus hour 14 is a contained incident versus a Mixed label, so let Media Monitoring start the clock instead of a friend's screenshot.
TL;DR
- Confirm against baseline. 5-10x your normal daily review volume with 1-sided sentiment is a bomb; 2 bad days is not.
- Diagnose from the reviews themselves. Patch, pricing, policy, or drama; then branch on-topic vs off-topic.
- Off-topic: document and let Valve's system work. It excludes the period from your score but leaves reviews visible.
- On-topic: respond within 24 hours. Steam announcement plus pinned thread, acknowledge specifics, date the fix, push it everywhere at once.
- Never argue, mass-report, incentivize, or go silent past 72 hours. Then let the 30-day Recent window and steady sales repair the score.
The score recovers when the trigger is fixed and the players believe you. Every case that ended well, from OpenIV to Helldivers 2, followed that order. GG.
More reading: Your first 10 Steam reviews | Discord community building | Steam wishlist strategy
Frequently Asked Questions
What counts as a review bomb on Steam?
A large volume of reviews landing in a short window, far outside the game's normal pattern; Valve calls it "anomalous review activity." A practical test: 5-10x your average daily review count arriving with 1-sided sentiment. A slow decline after a disliked patch is negative feedback, not a bomb.
Does Valve remove review bombs from your score?
Only off-topic ones. Since March 2019, Valve's tool flags anomalous activity, a human team investigates, and periods judged unrelated to the game itself drop out of the score by default. Reviews stay visible, users can opt back in, and on-topic bombs count in full.
How long does a review bomb affect your Steam rating?
The Recent score covers the trailing 30 days, so once the bombing stops, it typically recovers within a month. The Overall score is slower: 150 bomb negatives on a 500-review game can take roughly 300 new positive reviews to undo. Fast containment beats any recovery tactic.
Should you respond publicly to a review bomb?
If the trigger is real and fixable, yes, within 24 hours: a Steam announcement plus a pinned discussion, acknowledging the specific complaint and dating the fix. For off-topic publisher drama, a calm holding statement is usually enough. Arguing in reviews, mass-reporting, and silence never work.
