Steam Review Bombing: How It Works, How to Survive

Since March 2019, Valve detects review bombs automatically and excludes off-topic ones from your review score by default: the bombed date range is marked, every review inside it stops counting, and the reviews stay visible but the label on your store page ignores them. The catch is the word off-topic. If players are angry about something in the actual product — a bad patch, a new account requirement, removed features — those reviews count in full, and no exclusion is coming.

That one distinction decides everything about how a bomb plays out, so this guide is built around it: what Valve counts as off-topic, how the exclusion works, three documented bombs including Helldivers 2’s 2024 PSN blowup, and the recovery math for scores that took real counted damage. If you just need the label boundaries, our review score thresholds table has all nine.

Valve’s working definition, from the 2019 announcement that introduced the system, is an anomalous spike in review volume and sentiment over a short period. Not “your game got a bad week of reviews” — a coordinated or event-driven surge that looks nothing like your baseline.

Within that, Valve splits bombs into two kinds, and the split is the whole ballgame:

Valve decided by default that some categories are always off-topic, DRM and EULA changes being the named examples, on the logic that they apply to a large fraction of the catalog and rarely change whether a future buyer enjoys the game itself. Everything else gets judged case by case by actual Valve staff.

The uncomfortable implication for developers: the system is not review-bomb protection. It is off-topic-review-bomb protection. If 10,000 players thumbs-down your game because your publisher added an account linking requirement, Valve’s position is that future purchasers deserve to know, and your score eats every one of those reviews.

The mechanics, per Valve’s announcement and the Steamworks review documentation:

1. 01A tool watches every game’s review activity in close to real time and flags anomalous changes in volume and sentiment.
2. 02Humans investigate. The flag goes to a team at Valve that looks at what the reviews in the spike are actually about.
3. 03If the bomb is ruled off-topic, Valve marks the date range. Every review posted inside that window — positive and negative, on-topic and off — is removed from the score calculation. Valve chose blanket date-range exclusion over judging reviews one by one because individual sorting does not scale and invites accusations of cherry-picking.
4. 04Nothing is deleted. The reviews remain readable on your page, the histogram shows the marked period, and the store page discloses that some reviews were excluded.
5. 05Users can opt out of the protection. A Steam store setting lets any user include off-topic review periods in the scores they personally see. The default, which is what the overwhelming majority of shoppers see, excludes them.
6. 06Developers can opt out too, keeping bombed reviews in their score. In practice almost nobody does.

You do not have to wait for the tool. If your histogram shows a cliff and Valve has not reacted, the Steamworks docs tell you to contact Valve through partner support and flag the anomalous period yourself. Response is not instant. Borderlands 2 sat with a cratered score for around five days in 2019 before the exclusion landed. But the process exists and it works.

Three cases, three different endings.

GTA V, June 2017. After Take-Two sent a cease-and-desist to OpenIV, the tool behind most of GTA V’s single-player modding scene, players flooded the page with negative reviews and the game’s overall rating dropped to Mixed. There was no exclusion system yet, so every review counted. Take-Two reversed course within about ten days, stating it would generally not pursue single-player, non-commercial mod projects, and OpenIV resumed development. The score climbed back the slow way, positive volume diluting the spike, until the label read Very Positive again. This bomb and the Firewatch one that autumn are a large part of why the 2019 system exists.

Borderlands, April 2019. One month after Valve announced the off-topic tool, 2K announced Borderlands 3 as a six-month Epic exclusive, and angry players bombed the older Borderlands games on Steam — titles that had nothing to do with the decision. Roughly 1,100 negative reviews hit Borderlands 2 in a single day against a baseline of a handful. Valve ruled it off-topic (the reviews were about a storefront decision for a different game), marked the April 3-8 window, and excluded more than 4,000 reviews from Borderlands 2 alone. The scores snapped back to their pre-bomb labels. Total lasting score damage: effectively zero.

Helldivers 2, May 2024. The big one, covered next.

On May 3, 2024, Sony announced that Helldivers 2 PC players would be required to link a PlayStation Network account, a rule that had been waived at launch for technical reasons, now returning with a June 4 deadline for existing players. PSN does not officially operate in most of the countries where the game had been sold, which turned a login requirement into a lockout.

The response was one of the largest review bombs in Steam history. More than 200,000 negative reviews landed in about three days; SteamDB tallies reported by Game World Observer put the count past 330,000. The game, sitting comfortably in Very Positive territory since its February launch, fell to Mostly Negative on recent reviews and the lifetime score slid toward Mixed. Arrowhead’s own leadership publicly treated the bomb as legitimate feedback rather than fighting it, with the CEO acknowledging players were using the tools available to them.

Three things about Valve’s role are worth studying:

• —No off-topic exclusion. The complaints were about a requirement attached to the product itself, squarely on-topic under Valve’s definition. Every one of those reviews counted, and they still count today.
• —Valve broke its own refund policy. Refunds went through for players with dozens or even 100+ hours of playtime, far past the standard 2-hour window. When the platform holder starts eating refunds on your behalf, the message to the publisher is not subtle.
• —The game was pulled from sale in roughly 170 countries where PSN was unavailable, a restriction that outlived the controversy itself.

Sony reversed the requirement on May 6, 2024, three days after announcing it. Players then did something rare: they organized to flip their reviews back, and over 200,000 positive reviews landed in the days after the backtrack, many explicitly praising the reversal.

The aftermath is the instructive part, and it cuts both ways. The PSN bomb itself proved recoverable: recent reviews even hit Overwhelmingly Positive in mid-2025 after a long repair arc. But fresh bombs over monetization and balance hit through 2026, and as I write this the game sits at Mostly Positive overall, roughly 77% across more than a million reviews, with the recent label swinging as low as Mostly Negative. Every one of those counted reviews stays in the lifetime math. And look at what even the partial recovery required: a same-week reversal from the publisher, hundreds of thousands of players revising or replacing reviews, and ongoing sales volume most games never see. Those are not levers an indie with 800 reviews can pull.

The honest version of the playbook is short, because most of the levers are not yours.

You can

• —Report the anomalous period to Valve through Steamworks partner support if it has not already been flagged. If the bomb is off-topic, this is the single highest-value action available to you, and everything else is secondary.
• —Fix the actual cause fast if it is on-topic. Sony reversed in 3 days and the recent score flipped back within a week. Take-Two reversed in about ten days and recovered fully over time. Every documented recovery starts with the grievance being resolved, not messaged around.
• —Communicate once, clearly, in the right places. A pinned discussion post and a Steam event update stating what happened and what you are doing. Our review management playbook covers the first-48-hours sequence in detail, including when a developer response on a top review helps and when it pours fuel.
• —Ship the fix as a visible update. A patch with notes and a visibility round tells both the algorithm and returning players that the situation changed.
• —Ask players to reconsider after the fix, neutrally. “We’ve reverted the change, and if it changed your review, we’d appreciate a second look” is fine. Helldivers 2 players reversed tens of thousands of reviews voluntarily once the reversal shipped.

You cannot

• —Get on-topic reviews excluded. Valve staff read the reviews. If they are about your game, they stay in the score, full stop.
• —Ask for positive reviews, pay for reviews, or gate rewards on reviews. Valve treats all of these as manipulation regardless of the circumstances, bomb or no bomb, and the penalty is a warning banner or removal.
• —Delete or hide reviews. Developers have no removal power beyond reporting individual reviews that break Steam’s content rules (doxxing, slurs, spam). Mass-reporting angry-but-legitimate reviews does nothing except waste your crisis hours.
• —Wait it out silently and expect the recent score to save you. The 30-day recent window does eventually roll the bomb out of the recent label, but the lifetime score keeps every counted review forever. Silence also reads as contempt to the people deciding whether to revise their thumbs.

How recovery works depends entirely on which kind of bomb you took.

Off-topic bomb, excluded: recovery is instant and complete. The marked window drops out of the calculation and your score reverts to what it was. Borderlands 2 went back to its pre-bomb label the day the exclusion landed. There is no climb.

On-topic bomb, counted: now it is arithmetic, and the arithmetic is brutal. Steam’s score is positive reviews divided by total counted reviews, nothing more. Take a healthy indie game at 85% positive with 500 reviews (425 positive, 75 negative). An on-topic bomb adds 300 negatives: you are now at 425 / 800 = 53%, deep in Mixed. To climb back to 70% (Mostly Positive), you need (425 + x) / (800 + x) = 0.70 if every single new review is positive — that is 450 consecutive positive reviews. Real post-crisis reviews will not run 100% positive, and the required volume explodes as your incoming positive rate falls:

At a typical healthy 85% incoming rate, that is 900 new reviews, which at the ~30x reviews-to-sales multiplier implies roughly 27,000 additional sales, for a game that had 500 reviews before the bomb. And if your post-bomb reviews run at 70% positive or below, you never cross the line at all; the math has an asymptote. This is why resolving the grievance quickly matters more than any messaging: every day the cause stands, the pile of counted negatives grows and the required climb gets longer.

You can run your own numbers instead of trusting my scenario: put your current positive and negative counts into the review score calculator and it will tell you exactly how many net-positive reviews you need to cross the next label boundary, using the same threshold table Steam’s labels are built on.

Two softeners in your favor. The recent score (last 30 days) sheds the bomb automatically once it stops, so shoppers see “Recent: Very Positive” over a wounded lifetime score within about a month of resolution. That pairing tells the story honestly. And revised reviews move the math one-for-one: a negative flipped to positive both removes a negative and adds a positive, which is why the post-fix “second look” ask is worth making.

If your histogram just fell off a cliff, run this in order:

1. 01Read 30 of the new reviews and classify the bomb. About the game or its terms (on-topic), or about something external (off-topic)? Be honest — Valve will be.
2. 02Off-topic: contact Valve through Steamworks partner support today and flag the date range. Then hold; the exclusion restores your score in full.
3. 03On-topic: identify the specific decision players are punishing and get a reversal or fix decision made within days, not weeks. Speed is the difference between the Helldivers 2 outcome and a permanent Mixed label.
4. 04Post one clear statement on your community hub and as a Steam event. No defensiveness, no arguing in review responses.
5. 05Ship the fix visibly, then neutrally invite players to re-review.
6. 06Model the damage. Current positive and negative counts into the review score calculator, so you know whether you are 40 reviews or 900 reviews from your old label, and plan marketing accordingly.
7. 07Afterwards, audit what made you bombable. Account requirements, monetization changes, and EULA surprises are the recurring triggers in every documented case. If a decision like that is on your roadmap, announce it before launch, not after players have paid.

The system Valve built in 2019 means an off-topic bomb is survivable by design. An on-topic bomb is survivable too, but only through the boring mechanism of fixing the thing. The store page keeps the receipts either way.