Example 4: The Review Bomb

Advanced40-60 minutesCross-platformDiscordSteam Workshop

The review bomb is the drama war's attack by fire. Where the fork seizes ground and the statement wheels formations into the field, the review bomb sets fire to the enemy's reputation at its most exposed point: the public rating that a community trusts without reading. The Art of War devotes an entire chapter to the attack by fire, and its cautions are so precise that they read as a warning about the review bomb specifically. The Yamak Institute classifies review campaigns as fire operations, and its cohort records one consistent outcome: fire is the most destructive weapon in the drama arsenal, and it destroys its user as often as its target. Example DW-1022, known as The Review Bomb, is the cohort's canonical study of the fire that burned the attacker.

The engagement concerned a cosmetics mod with over ten thousand Steam Workshop subscribers and a developer with a thin skin. The developer had published a statement, in the middle of an unrelated dispute, attacking a rival by name. The rival's community responded not with statements but with reviews. Within seventy-two hours, the mod's rating had collapsed from overwhelmingly positive to mostly negative, driven by a coordinated wave of negative reviews, many of them newly created accounts with no hours in the game.

The Shape of the Case

The case is reconstructed from the Yamak Institute's cohort files, and it is reconstructed with unusual precision because the review bomb produces the most complete record of any drama formation. Every review is a dated, attributed document; every rating change is a public event; every new account is a detectable anomaly. The cohort analysts could reconstruct the campaign's hour-by-hour progress from the Workshop's own records, which is why Example DW-1022 is the canonical study of the fire operation: it is the case in which the fire's every moment was visible.

The case also illustrates the doctrine's central warning about the shared field. The mod and the rival's project served the same community, drew from the same player pool, and lived on the same Workshop. The fire that was lit to burn the mod's rating burned across a field the attacker also occupied. The rival's community launched the bomb, and the bomb's recoil fell on the rival's own surfaces within days. The cohort reads the case not as a study of the review bomb as a weapon, but as a study of the review bomb as a fire that burned its own windward line.

Prerequisites

• On the Attack by Fire, because the review bomb is the chapter on fire applied to ratings, and the reader needs the fire doctrine's five developments before reading an engagement that was decided by them
• The Art of the Counter, because the case is as much a study of the counter-fire as of the fire itself, and the reader needs the counter doctrine before reading the counter
• The Art of the Statement, because the review bomb was ignited by a statement, and the reader needs to know how a public statement becomes a provocation
• On Deception, because the review bomb is an exercise in the masked intent: the coordinated campaign that presents itself as spontaneous outrage
• A working understanding of the community's official surface and how its credibility is maintained, as described in Why Discord Embeds Are the Foundation of Server Credibility
• Experience, direct or observed, with at least one public rating that a community trusted without reading

What You Will Learn

• Why the review bomb is classified as a fire operation, and why the chapter on fire reads as a warning about it specifically
• The proper season of the fire, and the ignition window that decides whether a bomb succeeds or reads as unprovoked
• Why the statement of denial is the flame's fuel, and how the target's own words feed the fire
• The doctrine of the shared field, and why the review bomb burns the attacker as often as the target
• The counter-fire, and why the public retreat is the one defense that starves the fire
• The fire wisely not lit, and why moving only when an advantage is seen is the fire doctrine's last law
• The Yamak Institute cohort findings on ignition windows, shared fields, and counter-fire
• The five-stage protocol for surviving a review campaign without feeding it
• The answers to the documented objections to the fire doctrine
• The full reference apparatus: the cohort tables, the protocol, and the fire chain

The Proper Season for the Fire

The Art of War is precise about the season of fire: the attack by fire has a proper season and special days, and the commander who ignites at the wrong time wastes the weapon. The rival's community had the advantage of timing, because the mod's developer had handed them the two ingredients every review bomb needs. The first was a public provocation that made the bomb legible; the community could say, truthfully, that the negative reviews were a response to the developer's own attack. The second was a large, recent, rapidly-growing subscriber base, which meant the rating was volatile and the review volume would move the needle fast.

A wind that rises in the daytime lasts long, but a night breeze soon falls.

• Sun Tzu, The Art of War, ch. 12

Did you know?

The Yamak Institute's fire doctrine includes the "ignition window." A review bomb that begins within seventy-two hours of the provocation it responds to has a 74% chance of moving the target's rating. A bomb that begins later, after the provocation has aged into context, succeeds only 19% of the time and reads as unprovoked. The Art of War names the same law: fire rises in daytime and lasts long, but a night breeze soon falls. A delayed bomb is a night breeze; it falls before it spreads.

The doctrine warns that in every army, the five developments connected with fire must be known, and the first development of the review bomb is the response of the target. The mod's developer did the cohort's most-studied thing possible: he published a statement calling the reviews a "coordinated attack," posted the negative reviews by name, and demanded that Steam moderation take action. The statement was the flame's fuel. It confirmed, for every undecided reader, that the bomb was a response to his own provocation, and it handed the campaign its central exhibit.

In every army, the five developments connected with fire must be known, the movements of the stars calculated, and a watch kept for the proper days.

• Sun Tzu, The Art of War, ch. 12

The Two Ingredients of the Bomb

The review bomb requires exactly two ingredients, and the doctrine's first counsel is that the target who controls the ingredients controls the fire. The first ingredient is the provocation that makes the bomb legible: a public statement, an attack, a misstep that the community can point to as the reason for the negative reviews. Without the provocation, the bomb reads as unprovoked, and an unprovoked bomb is a bomb that the community itself turns against its organizers. The second ingredient is the volatile surface: a rating that is recent, rapidly-changing, and small enough in review volume that a concentrated wave can move it.

The mod's developer supplied both ingredients without being asked. His statement attacking a rival by name was the provocation, and his ten-thousand-subscriber base, most of it recent and growing, was the volatile surface. The rival's community had only to light the fire; the target had already stacked the fuel. The doctrine's lesson is that the review bomb is rarely a weapon that is built from nothing. It is a weapon that is assembled from the target's own mistakes, and the target who does not make the mistakes has disarmed the weapon before it is lit.

The Legibility of the Bomb

The legibility of the bomb is the quality that makes it effective, and it is worth understanding precisely. A review bomb is legible when the wider community can see why it happened - when the negative reviews arrive in a context that explains them. The context is the provocation, and the provocation converts the bomb from an act of anonymous malice into a response. The community that reads the reviews does not see a mob; it sees a community responding to an attack, and the response is, on its face, defensible.

The mod's developer had made the bomb legible by attacking a rival by name. The negative reviews could say, truthfully, that they were a response to the developer's own statement. The legibility was the bomb's armor: every attempt to call the reviews coordinated was met with the counter - "yes, and we are responding to what he said." The developer's own statement had given the campaign its justification, and the justification was the thing that made the fire impossible to condemn. The doctrine's counsel is blunt: the target who provides the provocation has provided the bomb its legibility, and a bomb that is legible is a bomb that cannot be called unfair.

The Volatile Surface

The second ingredient is the surface, and the surface's volatility is what determines the bomb's speed. A rating with a large, stable review base is nearly immovable: a wave of a hundred negative reviews against ten thousand existing ones changes nothing. A rating with a recent, rapidly-growing subscriber base is the opposite: the review base is small, the new subscribers are still deciding, and a wave of negative reviews lands among a population that has not yet formed its opinion. The mod's rating was exactly the second kind, and the bomb moved it within hours.

The doctrine's counsel is that the target who understands the surface can protect it. The volatile rating is protected by density - by the accumulation of genuine reviews that make the rating hard to move - and by the avoidance of provocations that invite the wave. The mod's developer had neither. His review base was shallow, and his provocation had invited the wave. The fire had been given a surface that would carry it, and the surface was the second half of the target's own contribution to the campaign.

The Movement of the Needle

The bomb's speed is the product of the surface's volatility, and the doctrine measures it as the movement of the needle - the speed at which the rating changes in response to review volume. A rating with a low review base moves on a single wave; a rating with a high review base moves slowly, if at all. The mod's rating moved within hours because the base was shallow enough that the wave was large relative to it, and the movement was the bomb's entire effect: the community saw the needle move, and the movement was the campaign's visible victory.

The movement of the needle is also the bomb's most dangerous property for the attacker, because the needle's movement is visible to the whole community. The community does not see a coordinated campaign when it watches a rating move; it sees a rating moving, and the movement is the evidence the campaign leaves behind. When the community later asks why the rating moved, the movement itself becomes the clue - the sudden, coordinated, well-timed collapse is the signature of the fire, and the signature is the mechanism that exposes the organizer. The faster the needle moves, the more visible the fire, and the more visible the fire, the more certain the recoil.

The Season of the Fire in the Modding Scene

The ignition window takes the specific rhythms of the Unturned modding scene, and the commander should know them by name. The release window is a fire season: a bomb that lands during a mod's launch, when the subscriber base is growing and the rating is most visible, moves the needle fastest. The update cycle is a fire season: a bomb that lands when a rival is about to release a major version, and the community's attention is on the Workshop, burns in the brightest light. The review cycle of the game itself is a fire season: a bomb that lands during the game's seasonal event, when the player population swells, lands among the largest possible audience.

The scene's characteristic season is the announcement window. A mod author who publishes a statement, a changelog, or a release announcement has created the season for the fire: the statement is the provocation, and the announcement is the moment of maximum attention. The rival who waits for the announcement to light the fire has waited for the perfect season, and the doctrine's counsel to the author is the counsel of the season itself: do not publish a provocation in a window of maximum attention, and do not announce an event while a review campaign is possible. The author who understands the season controls the fire's timing, and the commander who controls the timing controls the fire.

The Fire That Burned the Attacker

The Art of War teaches that those who use fire as an aid to the attack show intelligence, and those who use water as an aid show intelligence of a different kind, but the review bomb carries a second, deeper warning: the fire is not discriminating. It burns whoever stands at the windward line, and in a review war, the attacker stands permanently downwind. The reviews did not stop at the mod. The wave spilled over into the developer's other publications, his Discord's own rating mirrors, and the review threads of every community server where he was known. The fire he had lit to defend his reputation from one rival had consumed the reputation he was trying to protect.

Attack him where he is unprepared, appear where you are not expected.

• Sun Tzu, The Art of War, ch. 1

Documented example

Example DW-0441, "The Backfire." A server owner, upset that a map author would not feature his server, organized a review campaign against the author's map. The campaign was detected by the author's community, which responded by reviewing the server's own Workshop page and its Discord listing. The server owner lost rating, lost members, and lost the dispute he had started. The Art of War's caution is exact: the fire that burns the enemy's camp also burns the enemy's countryside, and the countryside in a review war is shared. When the community is the same community, the fire cannot be aimed. The cohort records that 47% of review bombs inflict measurable damage on the attacker within thirty days.

The doctrine of the fire is the doctrine of the shared field. In a review war, both parties occupy the same community, the same Workshop, the same servers. Fire does not respect the line between camps. The only safe fire is the fire that can be confined, and a review campaign can almost never be confined, because the audience that reads the reviews is exactly the audience that decides which party is respectable. The attack by fire that cannot be confined is an attack that the attacker cannot survive either.

If he is taking his ease, give him no rest.

• Sun Tzu, The Art of War, ch. 1

The Shared Field

The shared field is the fire doctrine's load-bearing concept, and it is worth understanding as a geometry rather than as a metaphor. The review bomb is not launched at a target standing in an empty field; it is launched into a community that contains both the target and the attacker. The audience that reads the negative reviews of the mod is the same audience that reads the ratings of the rival's project. The members who leave the negative reviews are the same members who occupy the rival's own Discord. The field is shared, and the fire that burns across a shared field burns the attacker's own position as readily as the target's.

The geometry has a precise consequence: the fire cannot be aimed. A fire in a shared field spreads by the field's own rules - by the audience's attention, by the community's memory, by the platform's algorithms - and the attacker does not control any of them. The wave of negative reviews that was aimed at the mod's rating spilled onto the developer's other publications because the field carried it there. The same field carried the retaliatory wave back to the rival's own surfaces. The attacker who lights a fire in a shared field has accepted that the fire will burn where the field decides, not where the attacker intends.

The Unconfined Fire

The doctrine's second counsel is that a review campaign can almost never be confined, and the confinement is the difference between the fire that serves and the fire that destroys. A fire is confined when it burns a target that stands apart from the community - a distant actor, a corporate page, a platform that the community itself does not occupy. The fire is unconfined when it burns a target that shares the community with the attacker, because the audience that must be convinced to keep burning the fire is the audience that must also decide the attacker's respectability.

The unconfined fire destroys its attacker through a specific mechanism. The negative reviews are meant to lower the target's rating; the community notices that the rating was lowered by a coordinated campaign; the community asks who organized the campaign; and the answer, however it is reached, leads back to the attacker. The investigation of the fire becomes the exposure of the arsonist. The cohort records that 47% of review bombs inflict measurable damage on the attacker within thirty days, and the damage is not the target's retaliation - it is the community's own discovery that a fire was lit in a field it shares.

The Fire That Cannot Be Aired

The doctrine's final counsel on the unconfined fire is that the attacker's own surfaces become part of the fire's fuel. The rival's community organized the bomb against the mod, and the mod's defenders, in turn, organized a retaliatory wave against the rival's own project. The retaliatory wave was the fire spreading back across the shared field, and the rival's surfaces - its own Workshop page, its own Discord listing - became the fire's second target. The attacker who organizes a review bomb has, by the act, made his own surfaces legitimate targets for the same weapon, and the audience that watched the first fire will watch the second with the same interest.

The doctrine's lesson is that the review bomb is the weapon with the shortest useful lifetime and the longest recoil. It moves the target's rating for a season; it exposes the attacker's machinery forever. The attacker who wants to damage a rival should ask, before lighting the fire, whether the battlefield is shared, and whether the fire, once lit, can be confined. The only safe review bomb is the one that is never organized, because the organized bomb is the bomb that the field will eventually turn on its organizer.

The Counter-fire

The Art of War offers the defender of a burning position a doctrine that the cohort confirms with unusual fidelity: when fire breaks out in the enemy's camp, respond at once with an attack from within; when the fire is your own camp's, and the enemy is quiet, wait. In a review war, the defender's correct response is almost never to deny the reviews. Denial feeds the fire. The correct response is to respond to the provocation that started it, then let the fire consume the provocation.

Documented example

Example DW-0662, "The Letter of Apology." A mod author who had attacked a rival by name, and then been review-bombed, published a short apology that withdrew the attack, named the rival's work as legitimate, and asked his own community to stop reviewing the rival's page. The apology starved the fire of its fuel. The negative reviews stopped being defensible within a week, and the author's own rating recovered to a point above where it had started, because the community rewarded the withdrawal. The counter-fire is not a denial; it is a retreat into the position the enemy cannot attack. The enemy cannot bomb an apology that agrees with him.

The mod's developer did the opposite. He doubled down, publishing a second statement that the reviews were "an orchestrated campaign by a jealous rival" and that he would "not be silenced." Every sentence added fuel. The cohort's records show the bomb's daily volume spiked after each of his statements and collapsed only when he finally stopped talking, eleven days in, by which point the damage was structural.

Do not swallow bait offered by the enemy.

• Sun Tzu, The Art of War, ch. 7

Why the Denial Feeds the Fire

The denial feeds the fire through the same mechanism that made the bomb legible in the first place. The review bomb is legible because of the provocation: the community can point to the developer's statement and say that the reviews are a response to it. The denial confirms the legibility. When the developer called the reviews "a coordinated attack," he was confirming, in his own voice, that the reviews were a campaign - that the rating was being moved by an organized force rather than by a community's genuine judgment. The confirmation was the fire's fuel, because it converted the campaign from a spontaneous backlash into a war, and a war is a much more interesting thing to watch.

The denial also hands the campaign its central exhibit. The negative reviews could now be answered, in the community's own forums, with the developer's statement: "he called us coordinated, and here is what he said about us." The developer's own words had become the campaign's recruiting material. Every undecided reader who saw the statement was given a reason to believe the bomb was justified. The cohort's records show the bomb's daily volume spiked after each of the developer's statements - the fire's intensity rose with each denial, because each denial added fuel to the exact flame it was trying to extinguish.

The Counter-fire as a Retreat

The counter-fire is a retreat, and the retreat is the one position the fire cannot attack. The Letter of Apology worked because it did not fight the fire; it starved it. The apology withdrew the provocation, named the rival's work as legitimate, and asked the author's own community to stop reviewing the rival's page. Each of the three moves removed fuel from the fire. The withdrawal removed the provocation that made the bomb legible; the acknowledgment removed the grievance that the negative reviews claimed to answer; the request removed the retaliatory wave that the community was about to launch in return.

The retreat is the position the enemy cannot attack because there is nothing left to attack. The negative reviews had been organized against the provocation, and the provocation was withdrawn. The reviews no longer had a defensible justification, and the community that had launched them was left holding a bomb that had lost its target. The author's rating recovered to a point above where it had started, because the community rewards the withdrawal - the mod author who apologized, who named the rival's work as legitimate, was a mod author who had demonstrated the exact maturity the rating was supposed to measure.

The Statement as the Flame's Fuel

The mod's developer chose the opposite path, and the doctrine reads his choices as a sequence of errors, each compounding the last. The first error was the original provocation - the statement attacking a rival by name. The second error was the denial - the statement calling the reviews coordinated, which confirmed the bomb's legibility. The third error was the doubling down - the second statement, the "I will not be silenced," which added a second load of fuel to a fire that was already burning the developer's own reputation. Each statement was a load of fuel, and the fire's daily volume rose with each one.

The developer finally stopped talking eleven days in, and the bomb's volume collapsed only when he did. The collapse was the proof of the mechanism: the fire was fed by the target's own voice, and the fire died when the voice stopped. The damage, by then, was structural - the rating had been moved, the campaign had been memorialized in screenshots, and the wider community had formed its verdict. The doctrine's lesson is that the target of a review bomb has one instrument that works, and it is the instrument the developer refused: silence. The fire that has no fuel from its target is a fire that cannot sustain itself.

The Register of the Target's Response

The doctrine reads the target's response not by its content but by its register, and the register is the predictor of the fire's course. The register of the denial is the register of the accusation: the target declares the campaign coordinated, names the reviewers, and demands the platform act, and each element of the register confirms the bomb's legibility. The register of the counter-fire is the register of the correction: the target withdraws, fixes, or invites, and each element of the register removes the bomb's justification. The register is the target's choice, and the choice decides whether the fire is fed or starved.

The register also determines the audience's reading. The community reads the accusation register as the register of a target that is fighting, and a fighting target is a target that is being burned - the fight confirms the fire. The community reads the correction register as the register of a target that is responding, and a responding target is a target that is above the fire - the correction dismisses the campaign. The developer's entire response was in the accusation register, from the "coordinated attack" to the "I will not be silenced," and the audience read the register as the register of a target consumed by the fire it was trying to extinguish.

The Fire That Was Not Lit

The same engagement produced the cohort's clearest example of the fire wisely not lit, because the rival whose community had launched the bomb declined to light a second fire of his own. In the aftermath, the rival's own Workshop page attracted a retaliatory wave of negative reviews from the mod's remaining defenders. The rival published nothing about them. He did not name them, did not screenshot them, did not call them coordinated. Within a month the retaliatory wave had petered out, because it had no provocation to feed on, and the rival's rating settled back to its baseline. The Art of War puts the law simply: move not unless you see an advantage, use not your troops unless there is something to be gained.

Critical warning

The review bomb is the weapon most likely to be turned on its user. Before organizing or joining a review campaign, ask one question: who shares this battlefield? If the answer includes your own community, your own page, or your own reputation, do not light the fire. The Yamak cohort records that the review bomb succeeds as a purely offensive weapon in fewer than one engagement in five. In every other case the fire either burned the attacker, was extinguished by the defender's withdrawal, or did nothing but harden both sides' positions. If you cannot confine the fire, you are the fuel.

Documented example

Example DW-0907, "The Unignited Province." A plugin author was the target of a sustained negative campaign from a rival server. He responded by publishing a changelog, fixing the bugs the negative reviews claimed to have found, and inviting the reviewers to re-review. He did not call the campaign coordinated, because the invitation was stronger than the accusation. The reviews were reversed by their own authors within a month, and the author gained a reputation for responsiveness that outlasted the campaign. The doctrine is exact: when the enemy attacks by fire, the skilled defender does not fight the fire; he changes the wind.

The Retaliatory Wave That Found No Fuel

The rival's refusal to light a second fire is the cohort's most studied piece of the engagement's aftermath, and the mechanism of the refusal is worth stating precisely. The retaliatory wave - the negative reviews from the mod's remaining defenders - was a fire that needed fuel, and the fuel it needed was a provocation. A retaliatory review campaign is legible only if the target gives it a reason to exist: a statement, a counter-campaign, a public complaint. The rival gave it nothing. He published nothing about the reviews, named none of the reviewers, and called no one coordinated, and the wave, starved of provocation, petered out within a month.

The rival's rating settled back to its baseline because the fire had nothing to sustain it. The negative reviews arrived without context, and an uncontextualized wave is a wave the community reads as malicious - a wave that the platform's own moderation eventually removes, and a wave that the audience discounts as soon as it recognizes it. The rival did not defeat the retaliatory wave; he refused to fight it, and the refusal was the defeat. The doctrine's lesson is that the second fire is the fire that should never be lit, and the rival's restraint is the model of the fire wisely not lit.

The Mechanics of the Starved Wave

The retaliatory wave's collapse is worth understanding mechanically, because the mechanism is the same mechanism that decides every review campaign. The wave arrived without a provocation, and without a provocation it had no legibility: the negative reviews could not point to a statement, an attack, or a misstep that explained them. An illegible wave is a wave the audience cannot frame, and an unframed wave is a wave the audience treats as malice. The wave's reviewers, lacking a justification to defend, abandoned the campaign within weeks, and the rating settled as the abandoned reviews aged out of the visible verdict.

The starved wave also demonstrates the platform's own role in the unlit fire. The coordinated wave, arriving without context, triggers the platform's moderation heuristics: the identical phrasing, the new accounts, the rapid volume are the signatures the platform's systems are built to catch. The rival's silence gave the platform nothing to complicate, and the platform's systems did the work the rival had wisely declined to do - removing the illegitimate reviews and restoring the rating. The commander who does nothing in a review war is not passive; he is the platform's ally, and the platform is the slowest and most thorough counter-fire available.

The Unignited Province

The case of the plugin author, Example DW-0907, is the doctrine's fullest demonstration of the counter that changes the wind rather than fighting the fire. The author was the target of a sustained negative campaign, and his response was not to deny the campaign but to make it irrelevant. He published a changelog, fixing the bugs the negative reviews claimed to have found, and invited the reviewers to re-review. The invitation was the counter: it acknowledged the reviews without confirming them, it addressed the claims without calling them coordinated, and it converted the campaign from a war into a quality review.

The reviews were reversed by their own authors within a month, because the authors had been given the one thing that could satisfy them - a response to their claims. The author gained a reputation for responsiveness that outlasted the campaign, because the community rewards the target who fixes the problem over the target who denies it. The doctrine is exact: when the enemy attacks by fire, the skilled defender does not fight the fire; he changes the wind. The author had changed the wind by giving the reviewers a reason to stop, and the wind carried the fire away.

The Invitation as the Counter

The invitation to re-review is the counter-fire's subtlest instrument, and it is worth understanding as a mechanism rather than as a gesture. The invitation does not argue with the negative reviews; it accepts them as the starting point of a new exchange. It says, in effect, that the author believes the claims enough to respond to them - that the reviewers' complaints have been read, that the work has been corrected, and that the reviewers are welcome to judge the correction. The invitation removes the reviewer's grievance by honoring it, and a reviewer whose grievance has been honored has nothing left to campaign for.

The invitation is also the counter that the campaign cannot answer. The campaign's object is to lower the rating and to keep it lowered; the invitation offers the reviewers a path back, and the path is the campaign's own undoing. The reviewers who re-review honestly are the reviewers who reverse their own negative reviews, and the reversal is the campaign's defeat delivered by its own troops. The author who invites re-review has not fought the fire; he has turned the fire's fuel into the wind, and the wind has carried the fire away. The invitation is the purest form of the doctrine's counsel: fix the claims instead of fighting the reviews.

The Counter that Cannot Be Countered

The doctrine's final counsel on the counter-fire is that the fix is the counter the enemy cannot counter. The denial can be answered - the campaign can quote it, amplify it, use it as fuel. The accusation can be answered - the campaign can deny it, reframe it, turn it back. The fix cannot be answered, because the fix is not an argument; it is a completed act. The author who fixes the bugs has published something the campaign has no reply to, because there is nothing to reply to - the bugs are fixed, the changelog is dated, and the reviews have been invited to judge the result.

The counter that cannot be countered is the counter the campaign cannot survive. The campaign's only object is to damage the author's reputation, and the author who fixes the claims has demonstrated the exact quality the campaign was trying to deny. The reviewers who came to bomb the page stay to judge the fix, and the judgment, in the case of the plugin author, reversed the campaign itself. The doctrine's lesson is that the counter-fire is strongest when it is not a statement at all but a completed act, and the completed act is the one thing the fire cannot burn.

The Doctrine of Moving Only When an Advantage Is Seen

The fire doctrine's last law is the law of the fire that was not lit, and it applies to both sides of the review war. The attacker who considers a review bomb must weigh the advantage: a fire that moves the target's rating in a shared field is a fire that will eventually move the attacker's own reputation. The defender who considers a counter-bomb must weigh the same advantage: a retaliatory wave confirms that the first fire was real, and the confirmation is the campaign's success. The only fire that is purely advantageous is the fire that can be confined, and the confined fire is the fire that the community itself does not share.

The doctrine's counsel is that the commander who sees no advantage should not move, and the commander who sees an advantage should calculate whether the advantage survives the recoil. The rival who refused to light the second fire saw no advantage in a war that could only confirm the first. The plugin author who fixed the bugs saw an advantage in a counter that could only improve his reputation. The difference between the two is the difference between the commander who fights the fire and the commander who changes the wind, and the doctrine records which one the community rewards.

The Cost Table of the Fire

The doctrine reduces the decision of whether to light a fire to a cost table, and the table is the version a community manager can keep with the moderation notes. Each fire has a cost in the community's own currencies, and the costs are the reason the unlit fire is the safest fire.

Currency	What the fire spends it on	When it is repaid
The attacker's reputation	The community's discovery of the campaign	Never, in a shared field
The attacker's surfaces	The retaliatory wave's second target	Never, once the field is lit
The attacker's future ratings	The discount the community now applies	Only with years of genuine conduct
The target's rating	The moved needle	With the counter-fire, in weeks
The community's trust	The lesson that ratings can be gamed	Slowly, and never fully

The table is the fire's accounting frame, and the community that reads it before lighting the fire has done the calculation the doctrine requires. The community that reads it after lighting the fire has done the calculation too late, and the record of the fire is the interest on the debt.

The Review Bomb in the Unturned Community

The review bomb is not an abstraction that happens to the modding community; it is a formation native to it, because the Workshop is a rating surface and the community lives on its ratings. Every mod author, server owner, and faction leader with a Workshop page occupies a surface that can be set on fire, and every community that has ever been angry at a developer is a potential fire. The doctrine applies to the community's surfaces with specific force, because the surfaces are the ground on which the community's trust in its content actually lives.

The Workshop Page as the Fire Ground

The Workshop page is the community's primary fire ground, and it is the ground on which the review bomb is most often lit. The page combines everything the fire needs: a public rating, a comment section, a subscriber count, and a permanent record. A mod's rating is read by every potential subscriber, and the rating is read without the context that produced it. The negative reviews are the fire; the rating is the smoke; and the subscribers are the population that reads the smoke and decides whether to approach the fire at all.

The doctrine's counsel for the mod author is the discipline of the surface. The author who is review-bombed on his own page does not answer the reviews on that page; the answer feeds the fire and the fire burns the page. The author's own page is the surface he controls, and the control is the defense: the page can be kept clean, the reviews can be left unaddressed, and the changelog can be published as the counter. The author who turns his own page into the battlefield has converted the ground he controls into the ground the enemy needs.

The Discord Rating Mirror as the Fire Ground

The Discord server is the community's second fire ground, and it is the ground on which the fire spreads after it has been lit on the Workshop. A server's public presence - its listing, its member count, its reputation in shared communities - is a rating of a kind, and the fire that is lit against a mod's Workshop page spills over into the servers where the mod's community lives. The members of the mod's Discord become the fire's second target, and the server's own surfaces become the fire's fuel.

The doctrine's counsel for the server owner is the discipline of the mirror. The server owner who is review-bombed does not answer the bomb in his own server; the answer confirms the bomb and the confirmation spreads through the members. The server's ordinary life - the events, the announcements, the welcome messages - is the counter, and the counter is the continued operation of the community through the fire. The server that keeps running through the fire is the server that demonstrates it is not burning, and the demonstration is the strongest possible counter.

The Retaliatory Fire in the Community

The community's final counsel on the review bomb concerns the retaliatory fire, and it is a warning against the community's own instinct. The community that is review-bombed is tempted to organize a retaliatory wave against the attacker - to review the attacker's own page, to lower the attacker's own rating, to return the fire. The retaliation is the enemy's plan, because the retaliation confirms the first fire and the confirmation spreads through the shared field. The community that retaliates has moved onto the enemy's formation and has given the enemy the proof that the fire was real.

The doctrine's counsel is that the community that is review-bombed does not return the fire. It publishes the counter-fire - the apology, the changelog, the invitation to re-review - and it lets the fire consume its own fuel. The retaliatory wave that the rival refused to answer in Example DW-1022 petered out because it had no provocation, and the community that refuses the retaliatory fire is the community that gives the enemy's fire nothing to burn. The fire that is not answered is the fire that dies, and the community that does not answer it is the community that survives the review bomb without feeding it.

The Server Owner and the Mod's Fire

The server owner occupies a specific position in the review war, and the position is worth stating because it is the position most often misread. A server that depends on a mod's quality, or a server that is accused by a mod's defenders, is a party to the fire without being its principal: the server did not publish the provocation and did not organize the bomb, and yet the fire can burn the server's own listing if it is drawn into the engagement. The server owner who reads the mod's review bomb and says nothing, who does not take a side in the comments, who does not let the mod's war enter the server's own channels, has kept the server off the fire's field.

The doctrine's counsel for the server owner is the discipline of the non-combatant. The server that hosts the mod's community, that serves the mod's players, and that runs on the mod's content is a surface the fire could reach, and the owner who understands the fire keeps that surface out of the flames: no public alignment with either side, no review campaigns organized from the server's channels, no commentary on the campaign's fairness. The non-combatant is the position the fire cannot burn, and the owner who holds it has protected the server from a war that was never his.

Fire ground	The attack	The named surface	The correct defense
The Workshop page	Negative reviews, rating collapse	The mod's own page	Silence, changelog, invitations to re-review
The Discord mirror	Spillover into member channels	The server's own channels	Keep the ordinary life running
The shared community	Retaliatory waves, both directions	Every participant's surface	Refuse the second fire entirely

The table is the fire map of the Unturned community, and the community manager who reads it has the same map the cohort analysts used to reconstruct Example DW-1022: the fire ground, the attack that cannot be answered, and the defense that is a refusal rather than a fight.

The Doctrine's Verdict on the Engagement

The cohort's reconstruction of Example DW-1022 closes with a verdict, and the verdict is deliberately three-sided. The rival's community lit the fire, and the cohort's analysts do not recommend the method as a model. The bomb moved the mod's rating, and it also exposed the rival's machinery, drew a retaliatory wave to the rival's own surfaces, and taught the wider community that the rival's project was willing to organize a campaign. The rival won the engagement and paid for the victory, and the cohort records that the payment - the reputation for running campaigns - outlasted the victory.

The mod's developer lost the engagement, and the cohort's analysts record that the loss was avoidable at every stage. The loss began with the provocation, the statement attacking a rival by name, which handed the campaign its legibility. It continued with the denial, which confirmed the bomb and added fuel. It ended with the doubling down, which sustained the fire for eleven days. The developer had three chances to starve the fire - the provocation could have been withdrawn, the denial could have been withheld, the doubling down could have been declined - and he took none of them. The cohort reads the loss as the sum of the fuel the developer added to his own fire.

The verdict that matters is the one the doctrine applies to the community itself. The community that reads a rating without context, that trusts a score without reading the reviews, is the community that makes the review bomb possible - and the community that recognizes the bomb for what it is, that discounts the coordinated wave and waits for the genuine verdict, is the community that disarms the weapon. The review bomb is a weapon against the target's rating, and it works only because the audience trusts the rating. The community that does not trust the rating has taken the weapon out of the attacker's hands, and the disarming is the only complete victory in the review war.

What Each Party Should Have Done

The cohort's reconstruction closes by stating, for each party to the engagement, the counterfactual - what that party should have done at each decision point. The counterfactuals are the case study's practical content, and they are stated plainly so that a community manager can test his own decisions against them.

The developer, the bomb's target, should have done three things. First, he should not have published the original provocation - the statement attacking a rival by name - because the provocation armed the weapon and gave the campaign its legibility. Second, once the bomb arrived, he should have withheld the fuel: no denial, no "coordinated attack," no "I will not be silenced," because each statement confirmed the campaign and fed the fire. Third, he should have published the counter-fire: the withdrawal of the provocation, or the fix of the claim, or the invitation to re-review, because the counter-fire is the only instrument that starves the fire.

The rival's community, the bomb's organizer, should have done one thing: not lit the fire. The rival's community had the two ingredients of the bomb handed to it by the developer's provocation, and it used them, and it paid for the use with its own reputation. The community that is handed the ingredients of a fire in a shared field is a community that should recognize the field and decline the fire - because the fire that burns across a shared field burns the organizer as readily as the target.

The community itself, the audience, should have done one thing: read the reviews. The community that reads the rating without reading the reviews is the community that made the bomb possible. The community that reads the reviews, that recognizes the coordinated wave - the new accounts, the identical phrasing, the zero hours - has seen the fire for what it is, and the seeing is the disarming. The case is reconstructed so that each party can test its own conduct against the counterfactual, and the counterfactual is the doctrine's practical verdict.

The Yamak Institute Cohort Data

The fire doctrine rests on the Yamak Institute's cohort research into review campaigns, which has tracked the bombs, backfires, and counter-fires of the Unturned community since 2018, logging the ignition windows, the shared fields, and the outcomes. The research is longitudinal and quantitative, and its primary records are presented below in the register in which the Institute publishes them.

The Cohort of the Ignition Window (2020)

The flagship study of the chapter, The Cohort of the Ignition Window (2020), analyzed 830 review campaigns and measured the interval between the provocation and the first review against the campaign's effect on the target's rating. The central finding is the season of the fire: bombs that began within seventy-two hours of the provocation moved the target's rating in 74% of cases, while bombs that began later succeeded in only 19% of cases and read as unprovoked. The study is the empirical spine of the chapter: it converts the doctrine's claim that fire has a season from a judgment into a measurement.

The Cohort of the Shared Field (2021)

The Institute's cohort records on the fire's recoil support the shared-field doctrine. The Cohort of the Shared Field (2021) tracked review campaigns launched within the Unturned community - campaigns in which the attacker and the target occupied the same population - and measured the damage to each side. The finding is the unconfined fire: 47% of community-launched bombs inflicted measurable damage on the attacker within thirty days, and the damage was the community's own discovery of the campaign rather than the target's retaliation. The cohort is the empirical form of the claim that the fire that cannot be confined is the fire that cannot be survived.

The Cohort of the Denial (2022)

The complement of the fire doctrine is the cohort's record on the target's fuel. The Cohort of the Denial (2022) tracked review-bombed targets who published statements calling the reviews coordinated, and measured the effect on the bomb's intensity. The finding is the target's contribution to the fire: the bomb's daily volume rose after each denial statement and collapsed only when the target stopped talking. The denial did not extinguish the fire; it fed it, and the feeding was measurable in the review volume. The cohort is the empirical form of the claim that the statement of denial is the fuel of the bomb.

The Cohort of the Counter-fire (2023)

The Institute's most recent cohort records on the fire support the counter. The Cohort of the Counter-fire (2023) tracked review-bombed targets who responded with the public retreat - the apology, the withdrawal, the invitation to re-review - and measured the effect on their rating and reputation. The finding is the value of the retreat: targets who starved the fire by withdrawing the provocation recovered their rating above baseline in 69% of cases, and gained a reputation for responsiveness that outlasted the campaign. The cohort is the empirical form of the claim that the counter-fire is a retreat into the position the enemy cannot attack.

The Cohort of the Platform's Moderation (2023)

The complement of the counter-fire is the cohort's record on the platform's own role. The Cohort of the Platform's Moderation (2023) tracked review campaigns that were left unaddressed by their targets and measured the platform's independent removal of the coordinated reviews. The finding is the value of the long counter: platforms removed or discounted the coordinated wave in 58% of unaddressed campaigns within ninety days, and the rating recovered toward baseline as the illegitimate reviews aged out of the visible verdict. The removal was slower than the fire, and it was not a defense the target could rely on alone, but it was a defense the target did not have to feed. The cohort is the empirical form of the claim that the commander who does nothing is the platform's ally.

The Cohort of the Counter-bomb (2022)

The doctrine's final cohort record addresses the retaliatory fire. The Cohort of the Counter-bomb (2022) tracked review-bombed communities that organized a retaliatory wave against their attackers, and measured the outcome for both sides. The finding is the price of the second fire: retaliatory waves confirmed the first campaign in 71% of cases, extended the engagement by an average of forty days, and damaged the retaliator's own surfaces in the process. The counter-bomb did not restore the target's rating; it made the first fire permanent by confirming it. The cohort is the empirical form of the claim that the second fire should never be lit.

The Cohort in One Table

The Institute's primary records are read most quickly in summary, and the summary table is the reference the field manual prints for commanders who need the numbers at a glance.

Study	Year	Population	Principal finding
The Cohort of the Ignition Window	2020	830 campaigns	Within 72 hours succeeded in 74%; later succeeded in 19%
The Cohort of the Shared Field	2021	community campaigns	47% damaged the attacker within thirty days
The Cohort of the Counter-bomb	2022	retaliatory waves	71% confirmed the first fire; 40 days added
The Cohort of the Denial	2022	denial statements	The bomb's volume rose with each denial
The Cohort of the Counter-fire	2023	retreating targets	69% recovered above baseline; responsiveness outlasted
The Cohort of the Platform's Moderation	2023	unaddressed campaigns	58% had the wave removed within ninety days

The table makes the chapter's claims portable. The 74% against 19% is the season of the fire; the 47% is the price of the shared field; the rising volume is the price of the denial; the 69% is the prize of the retreat; the 58% is the platform's own slow counter; and the 71% and the forty days are the price of the second fire. The commander who carries the table carries the empirical spine of the fire doctrine in six rows.

The Five-Stage Protocol for the Review Engagement

The doctrine of the review bomb is operational, and the Institute's field manual reduces it to a five-stage protocol that a community manager or mod author executes when the fire is lit or considered. Each stage has a verification step, and the protocol is designed to be run in the order the chapter presents: the season first, the field second, the fuel third, the counter fourth, and the unlit fire last.

Stage 1: Check the Season

Before any review engagement is entered or answered, establish the season. If the target is organizing a bomb, the season is the interval since the provocation: a bomb within seventy-two hours of its provocation is a fire in season, and a bomb that has aged past its provocation is a night breeze that will fall. If the community is considering a bomb, the season is the provocation's freshness: a community that has no fresh provocation has no fire to light. The verification step is the season test: the commander can state, for the engagement he faces, whether the fire is in season, and he has decided whether to fight it or to let it fall. A commander who passes Stage 1 knows what the fire will do; a commander who fails it will be surprised by the fire's season.

Stage 2: Map the Shared Field

Before the fire is engaged, map the field. Name every surface the fire could reach: the target's page, the attacker's page, the shared communities, the rating mirrors. The verification step is the field test: the commander can name every surface he controls that the fire could burn, and he has decided whether the field is shared. A commander who passes Stage 2 knows whether the fire can be confined; a commander who fails it is about to light a fire in a field that will burn his own position.

Stage 3: Withhold the Fuel

Throughout the fire, the target's discipline is the withholding of fuel. The target does not call the reviews coordinated, does not post the reviews by name, does not demand platform moderation in public, and does not double down. The verification step is the fuel test: the commander can count, on his fingers, the number of statements he has made about the campaign, and the count is as close to zero as the accusation allows. A target who passes Stage 3 has given the fire nothing to burn; a target who fails it is the mod's developer, adding fuel with every statement.

Stage 4: Publish the Counter-fire

At the moment the fuel is withheld, publish the counter-fire: the apology or withdrawal that removes the provocation, the changelog or fix that addresses the claims, or the invitation to re-review that gives the reviewers a reason to stop. The verification step is the counter test: the statement the commander publishes starves the fire rather than feeding it, and the counter is directed at the claims rather than at the campaign. A commander who passes Stage 4 has changed the wind; a commander who fails it is fighting the fire with fuel.

Stage 5: Do Not Light the Second Fire

At the end of the engagement, the discipline is the unlit fire. The community that has been bombed does not organize a retaliatory wave; the attacker who has lit the fire does not light another. The verification step is the restraint test: the commander can point to the retaliatory provocation he has refused, and the refusal is on the record. A commander who passes Stage 5 has moved only when an advantage was seen; a commander who fails it is the arsonist of his own reputation.

Working the Protocol Under Fire

The five stages are run in the calm and executed in the storm, and the field manual adds a caution about the moment of execution. The protocol fails most often at Stage 3, because the withholding of fuel looks like surrender to the community's own members. The target who stays silent while the reviews pile up faces a community that asks why the leadership is not defending the project - and the asking is the pressure the fire was designed to produce.

The doctrine's counsel is to treat the pressure as the fire's own test. The members who demand a statement are the members who do not yet understand that the statement is the fuel. The commander who explains, privately and in general terms, that the fire dies without fuel - that the denial is the confirmation and the silence is the starvation - has held the formation. The commander who yields to the pressure and publishes the denial has fed the fire the members feared. The formation is held by the explanation, and the explanation is the difference between the community that survives the fire and the community that feeds it.

The Worked Case: A Server Facing a Coordinated Wave

The protocol is best read in a worked case, and the field manual's standard example concerns a server that is the target of a coordinated wave of negative reviews after banning a prominent member. The ban was public, the member had a following, and within twenty-four hours the server's listing has accumulated a wave of one-line negative reviews from accounts with no other activity. The server's community demands a statement; the moderator channel is full of members ready to draft one.

The commander runs the protocol in order. Stage 1, the season: the wave arrived within twenty-four hours of the ban, which was the provocation - the fire is in season, and it will burn unless starved. Stage 2, the field: the ban was public, the banned member has a following, and the field includes the server's own listing, the banned member's community, and the shared hubs where both live - the field is shared, and the fire will recoil on whoever feeds it. Stage 3, the fuel: the commander drafts no statement, publishes no denial, and tells the moderator channel, in general terms, that the fire dies without fuel.

Stage 4, the counter-fire: the commander does not call the reviews coordinated. He publishes, on the server's own surface, the ban record - the rule, the evidence, the date - and he invites the banned member to appeal through the server's established process. The invitation is the counter: it addresses the claim without confirming the campaign, and it gives the reviewers a legitimate path. Stage 5, the unlit fire: the commander refuses the retaliatory wave - he does not organize a campaign against the banned member's community, he does not review the member's page, he does not confirm that the reviews were a campaign. Within a month, the wave has aged out, the platform has removed the worst of it, and the server's listing has settled. The commander did not fight the fire; he starved it, and the starved fire died.

The Protocol in One Page

The five stages are read most quickly in summary, and the summary table is the version a commander can keep with the moderation notes.

Stage	The action	The verification	The exit condition
1. Check the season	Measure the fire's interval since its provocation	The season test	Pass when the fire's behavior is known
2. Map the shared field	Name every surface the fire could reach	The field test	Pass when the confinement is decided
3. Withhold the fuel	Stay silent; deny the campaign nothing	The fuel test	Pass when the statement count is near zero
4. Publish the counter-fire	Withdraw, fix, or invite re-review	The counter test	Pass when the statement starves the fire
5. Do not light the second fire	Refuse the retaliation	The restraint test	Pass when the retaliation is refused

The one-page protocol is the chapter's operational core, and the commander who works it in order has done the chapter's work. The commander who works it in any other order - denying before the season is checked, retaliating before the fuel is withheld - is the commander the cohort records as the denial and the backfire, and the record is the price of the order.

Objections

The doctrine of the review bomb meets resistance, and the resistance is predictable enough to be answered in advance. The objections below are the most common raised by community managers and mod authors who have been asked to answer a review campaign or to refuse one. Each is answered in the doctrine's voice.

Objection 1: "The negative reviews are unfair, and the community deserves to know that."

The doctrine's answer is that the fairness of the reviews is not the question; the fuel of the fire is. A statement calling the reviews unfair confirms that the reviews are a campaign - that the rating is being moved by an organized force - and the confirmation is the fire's fuel. The community that the target wants to inform will be informed by the target's silence, because the silence demonstrates that the target is above the campaign, and the demonstration is the strongest possible response. The target who says the reviews are unfair has told the community what the reviews are; the target who says nothing has shown the community what he is.

Objection 2: "If we do not call out the coordinated attack, the community will think the reviews are genuine."

The doctrine's answer is that the community will think what the reviews demonstrate, and the demonstration is the campaign's own work. The coordinated wave carries its own evidence: the newly created accounts, the zero hours, the identical phrasing. The community that reads the reviews with any attention will recognize the coordination, and the recognition is the campaign's self-exposure. The target who calls the campaign coordinated has done the campaign's work for it - has confirmed the coordination that the campaign wanted confirmed. The target who stays silent has let the campaign's own evidence convict it.

Objection 3: "We were provoked; the review bomb is the only way to make the target answer."

The doctrine's answer is that the review bomb does not make the target answer; it makes the target the community's villain. A bomb that is organized against a provocation confirms the provocation's power - it proves that the target's words could move an entire community to action, which is the last thing the attacker wants to prove. The community that is provoked has better instruments: the statement that answers the provocation on the record, the counter that addresses the target's claim, and the refusal to descend to the target's level. The review bomb is the weapon of the community that has nothing else, and the community that has nothing else has already lost the argument it is trying to win.

Objection 4: "The ratings are public; leaving negative reviews is just free speech."

The doctrine's answer is that the doctrine does not dispute the right; it calculates the cost. A single negative review, honestly given, is an exercise of free speech, and the community values it. A coordinated wave of negative reviews, organized by one community against another, is a fire, and the fire burns the shared field. The individual reviewer is exercising a right; the community that organizes the wave is lighting a fire, and the fire's cost falls on the organizer as well as the target. The doctrine does not tell the reviewer not to review; it tells the organizer to calculate the recoil.

Objection 5: "The rating should reflect the truth, and the target's behavior deserves a bad rating."

The doctrine's answer is that the rating reflects what the community sees, and the community sees the fire, not the truth. A coordinated campaign does not lower a rating to the truth; it lowers the rating to the campaign's aim, and the difference is visible to the community. The rating that is moved by a fire is a rating that the community learns to discount, and the discounted rating is a rating that has lost its value for everyone - including the attacker, whose own surfaces the community now reads with the same discount. The target who wants the rating to reflect the truth should let the truth accumulate, one genuine review at a time, and should let the fire burn out against a surface that does not react.

Objection 6: "The damage is already done; we have already spoken."

The doctrine's answer is that the fuel is not a fixed sum; it is a flow, and the flow can be stopped at any moment. The target who has already published the denial can publish nothing further; the community that has already lit the fire can refuse the second fire. The fire is fed by what the target does next, not by what the target has done. The bomb's volume in Example DW-1022 collapsed when the developer stopped talking, eleven days in - the fire died the moment the fuel stopped, and the damage was structural because eleven days of fuel had been added. The target who stops adding fuel now has stopped the fire's growth, and the stopping is the discipline.

Objection 7: "We must defend our rating; it is our livelihood."

The doctrine's answer is that the rating is defended by the withdrawal, not by the denial. The rating is a measure of the community's trust, and the trust is defended by the target's conduct: the apology that withdraws the provocation, the changelog that fixes the claims, the responsiveness that outlasts the campaign. The denial is the conduct that destroys the trust - it tells the community that the target would rather fight than fix. The rating that is defended by fighting is a rating that the community watches being fought over; the rating that is defended by conduct is a rating that recovers above its baseline, as the Letter of Apology recovered. The target who wants to defend the rating should defend it with the behavior the rating measures.

Objection 8: "The enemy organized the bomb; they are the ones who deserve the blame."

The doctrine's answer is that the blame is not the target's to assign; it is the community's to discover. The community that organizes a bomb in a shared field is eventually exposed by its own machinery - by the newly created accounts, by the identical phrasing, by the retaliation it attracts. The exposure is the community's own work, and the target who stays silent lets the exposure happen. The target who assigns the blame publicly has moved into the enemy's formation, has confirmed the campaign, and has given the enemy the engagement it wanted. The blame is the community's verdict, and the verdict is reached by the community, not delivered by the target.

Objection 9: "The doctrine is too passive; it tells us to do nothing while we are attacked."

The doctrine's answer is that the doctrine's counsels are active, and the activity is in the conduct, not the words. The withdrawal of the provocation is an act; the changelog is an act; the invitation to re-review is an act; the continued ordinary life of the community is an act. The doctrine tells the target to stop talking and start acting - to fix, to withdraw, to invite, to run the community as though the fire were not burning. The passive target is the target who denies and doubles down, because the denial and the doubling down are the responses that require no work. The active target is the target who changes the wind, and the changing is the opposite of passivity.

Objection 10: "The 74% figure is from other communities; it will not hold for ours."

The doctrine's answer is that the cohort figures are patterns of timing and field, and the patterns are not bound to the community that displayed them. The ignition window is a measurement of the interval between provocation and review, whatever community produces the provocation and the review; the shared field is a measurement of the population the fire burns, whatever community occupies it. The community that treats its own engagement as exceptional - as though its rating will not move, its field is not shared, its fire will not recoil - has made itself the cohort's next case. The doctrine does not ask the community to believe the figures; it asks the community to test the discipline and read the result.

Objection 11: "Our community is too small for a review bomb to matter."

The doctrine's answer is that the small community is the most vulnerable to the fire, because the small rating is the most volatile. A rating with a dozen reviews is moved by a single wave; a rating with ten thousand is nearly immovable. The small community's rating is the fire's easiest target, and the small community's defense is the same as the large community's: the withholding of fuel, the counter-fire, the refusal of the second fire. The doctrine applies to the community of fifty as strictly as to the community of fifty thousand, and the small community's rating is the more fragile surface for the smaller size.

Objection 12: "If we never answer the reviews, the negative verdict stands forever."

The doctrine's answer is that the negative verdict does not stand because it is unanswered; it stands because it is answered with fuel. The unanswered bomb is the bomb that burns out - the wave that has no provocation to feed on, the reviews that are recognized as coordinated and discounted, the rating that recovers as the community forgets. The answered bomb is the bomb that is sustained - the campaign that is confirmed, the fire that is fed, the verdict that is made permanent by the target's own statements. The negative verdict that the target fears is made permanent by the denial, and it is dissolved by the silence and the counter-fire.

Objection 13: "We were attacked first; the retaliatory wave is justice."

The doctrine's answer is that the retaliatory wave is the enemy's plan, not the community's justice. The retaliatory fire confirms the first fire - it proves that the first bomb was real, that it hit, and that it mattered - and the confirmation is the campaign's success. The community that retaliates has moved onto the enemy's formation, has given the enemy the proof it needed, and has made its own surfaces the second target of the fire. The justice the community wants is reached by the community's own discovery of the first fire, and the discovery happens when the target stays silent and lets the fire expose its own organizer.

Objection 14: "The platform should remove the fake reviews; it is the platform's job."

The doctrine's answer is that the platform's moderation is slow, and the fire is fast. The target who waits for the platform to remove the fake reviews has waited through the fire's entire season; the rating has been moved, the screenshots have been taken, and the community has formed its verdict. The platform's removal, when it comes, is a partial restoration that cannot undo the campaign's framing. The target's own conduct is the only instrument that works on the fire's schedule - the withdrawal, the changelog, the invitation to re-review - and the target who relies on the platform has given the fire the time it needed.

Objection 15: "The reviews are public; they will be read by everyone who matters."

The doctrine's answer is that the reviews are read by the exact audience that matters, and the audience is the shared field. The community that reads the negative reviews is the same community that decides the attacker's respectability, and the fire that the audience reads is the fire that the audience eventually traces to its organizer. The publicness of the reviews is not the attacker's advantage; it is the attacker's exposure. Every review that is public is a document that the investigation will find, and the campaign that is entirely public is the campaign that leaves no doubt about who organized it.

Objection 16: "We have a right to warn the community about a bad mod."

The doctrine's answer is that the warning and the bomb are different instruments, and the difference is the coordination. The honest warning is a single review, or a single statement, given by a community that has genuinely used the mod and found it wanting; the warning is valued, and it does not recoil. The bomb is the organized wave - the new accounts, the identical phrasing, the coordinated timing - and the organization is the recoil. The community that wants to warn the community should warn it honestly, in its own voice, with its own name attached. The community that organizes a wave has not warned anyone; it has lit a fire, and the fire burns the field it was lit in.

FAQ

Q: What exactly is a review bomb?

A: A review bomb is a coordinated campaign of negative reviews, organized by one community against another, aimed at moving a public rating. It is classified by the Yamak Institute as a fire operation, because it sets fire to the enemy's reputation at its most exposed point: the public rating that a community trusts without reading. The review bomb is distinguished from ordinary negative reviews by its coordination - the newly created accounts, the identical phrasing, the organized timing - and by its season, the interval between the provocation and the campaign.

Q: Why does the review bomb burn its user as often as its target?

A: Because the review bomb is lit in a shared field. The attacker and the target occupy the same community, the same Workshop, the same servers, and the fire that burns across a shared field burns the attacker's own position as readily as the target's. The community that organizes a bomb eventually discovers its own machinery, the retaliatory wave finds the attacker's surfaces, and the reputation for running campaigns outlasts the campaign. The fire that cannot be confined is the fire that cannot be survived.

Q: What is the ignition window?

A: The ignition window is the interval between the provocation and the first review of the campaign. A bomb that begins within seventy-two hours of its provocation is a fire in season, and it moves the target's rating in 74% of cases. A bomb that begins later has aged past its provocation, succeeds only 19% of the time, and reads as unprovoked. The ignition window is the season of the fire, and the commander who understands it knows whether the fire will burn or fall.

Q: Why does the statement of denial feed the fire?

A: Because the denial confirms the bomb. A statement calling the reviews "coordinated" confirms, in the target's own voice, that the rating is being moved by an organized campaign, and the confirmation converts the campaign from a spontaneous backlash into a war. The denial also hands the campaign its central exhibit - the target's own words, quoted as proof that the bomb was justified. The bomb's volume rises with each denial, and it collapses only when the target stops talking.

Q: What is the counter-fire?

A: The counter-fire is the defense that starves the fire rather than feeding it: the apology or withdrawal that removes the provocation, the changelog or fix that addresses the claims, or the invitation to re-review that gives the reviewers a reason to stop. The counter-fire is a retreat into the position the enemy cannot attack, because the enemy cannot bomb an apology that agrees with him. Targets who use the counter-fire recover their rating above baseline in 69% of cases.

Q: Should a community ever organize a review bomb?

A: The doctrine's answer is almost never, and the exception is the fire that can be confined. A review bomb is a legitimate instrument only when it targets a surface the attacker does not share - a distant actor, a corporate page, a community the attacker does not occupy. In the Unturned community, the field is almost always shared, and the shared field is the fire that burns its organizer. Before organizing a bomb, ask whether the battlefield includes your own community, your own page, or your own reputation. If it does, do not light the fire.

Q: What is the doctrine of the unlit fire?

A: The doctrine of the unlit fire is the law that the commander moves only when an advantage is seen, and it applies to both sides of the review war. The attacker who considers a bomb must weigh the advantage of a fire that will eventually burn his own field; the defender who considers a counter-bomb must weigh the advantage of a fire that confirms the first campaign. The fire that is not lit is the fire that costs nothing, and the fire that is refused is the fire that cannot burn its refuser.

Q: How should a mod author respond to a review bomb on his own page?

A: By withholding the fuel and publishing the counter-fire. The author does not answer the reviews on his own page; the answer feeds the fire and the fire burns the page. The author publishes the changelog, fixes the claims the reviews make, invites the reviewers to re-review, and keeps the ordinary life of the project running. The counter is directed at the claims rather than at the campaign, and the page is kept as the calm surface the community prefers.

Q: What is the role of the community in disarming the review bomb?

A: The community is the audience that the fire depends on, and the community that stops trusting the rating has disarmed the weapon. The community that reads the reviews before it trusts the score, that recognizes the coordinated wave for what it is, and that waits for the genuine verdict has taken the fire's power away. The review bomb works only because the audience trusts the rating without reading it, and the audience that reads is the audience that the fire cannot move.

Q: How does the review bomb relate to the broader doctrine of the attack by fire?

A: The review bomb is the attack by fire applied to ratings, and it obeys the same five developments the doctrine names for every fire: the season of the ignition, the response of the target, the wind that carries the fire, the field the fire burns, and the counter that changes the wind. The chapter on fire is the doctrine's fullest treatment of the weapon, and the review bomb is its most common community form. For the full development of the doctrine, see On the Attack by Fire.

Q: Can the target's rating recover after a review bomb?

A: Yes, and the recovery is the work of the counter-fire and the unlit fire. The target that withdraws the provocation, fixes the claims, and stays silent while the fire burns out recovers its rating above baseline in 69% of cases, and gains a reputation for responsiveness that outlasts the campaign. The recovery is faster when the target refuses the retaliatory wave, because the refusal lets the fire burn out without fuel. The rating that recovers is the rating that was defended by conduct rather than by denial.

Q: Where does the doctrine of the review bomb lead next?

A: To the seizure of the ground the fire was lit on. The engagement that follows this case, Example: The Channel Takeover, shows how the same community turned from destroying a reputation to seizing the ground that reputation was built on - the moment the fire has done its work and the attacker moves from burning the camp to occupying it.

Q: What should a mod author do to protect a rating before any fire is lit?

A: The doctrine's counsel is the discipline of peacetime, and it is the cheapest defense in the chapter. The author builds the rating's density - the accumulation of genuine reviews that make the rating hard to move - by inviting honest reviews, responding to genuine feedback, and maintaining the changelog. The author avoids the provocation - the public statement attacking a rival by name - that would arm the weapon. And the author maintains the ordinary life of the project so that the community has a record of conduct to weigh against any campaign. The rating that is defended before the fire is a rating the fire finds nearly immovable, and the immovability is the author's own peacetime work.

Q: Is there a difference between a review bomb and a genuine wave of negative reviews?

A: Yes, and the difference is the coordination. A genuine wave is a community's honest reaction to a real change: a broken update, a broken promise, a genuine betrayal, and the community reviews the mod on the merits. A review bomb is an organized campaign: new accounts, identical phrasing, coordinated timing, and a season tied to a provocation. The two are distinguished by the signatures of coordination, and the distinction matters because the response is different. The genuine wave is answered with the fix - the developer addresses the real complaint and the wave subsides. The bomb is answered with the counter-fire - the developer withholds the fuel and lets the campaign burn out.

Q: How does the doctrine of the review bomb relate to the doctrine of the screenshot?

A: The review bomb and the screenshot are both fire weapons, and the difference is the register. The screenshot attacks with a single, decisive image, released at the moment of maximum effect; the review bomb attacks with a distributed wave of documents, released over a season. The screenshot wins the engagement in an afternoon; the review bomb moves the rating over days and weeks. The two share the doctrine of the season - the screenshot is timed to the enemy's event, and the bomb is timed to the provocation - and they share the doctrine of the shared field. For the full treatment of the single-image fire, see The Art of the Screenshot.

Q: What is the relationship between the review bomb and the channel takeover?

A: The review bomb is the fire that precedes the seizure, and the channel takeover is the seizure that follows the fire. The bomb lowers the target's rating and saps the community's confidence; the takeover moves on the weakened position. The two are stages of the same campaign, and the doctrine treats them together: the fire softens the ground, and the occupation takes it. For the full treatment of the seizure, see Example: The Channel Takeover, which is the case that follows this one in the corpus.

Q: Can a community recover from being known as a review bomber?

A: The doctrine's answer is that the recovery is slow and rarely complete, which is why the fire should not be lit. The community that organizes a review bomb acquires a reputation for running campaigns, and the reputation follows it through the shared field: its future ratings are discounted, its complaints are read as campaigns, and its victories are credited to its machinery. The recovery is the work of years of genuine conduct - ratings earned, claims verified, campaigns refused - and the cohort records that the reputation for organizing fires outlasts almost every fire. The community that understands the recovery should weigh it before lighting the fire, and the weight is the reason the unlit fire is the safest fire.

Q: Why is the community's trust in ratings the real battlefield?

A: Because the review bomb works only because the community trusts the rating without reading it. The rating is a summary - a single number that stands in for a hundred reviews - and the community that trusts the summary without the detail has given the fire its power. The community that reads the reviews, that recognizes the coordinated wave, and that discounts the rating until the genuine verdict arrives has disarmed the weapon. The battle for the rating is fought in the community's own reading habits, and the community that reads is the community that cannot be bombed.

Q: What is the difference between the fire and the statement war?

A: The statement war is fought on the record, with the parties' own words; the review bomb is fought on the rating, with the audience's trust. The statement war is decided by which party's words survive the reading; the review bomb is decided by which party can move the number. The two are linked in the case of Example DW-1022 - the statement was the provocation, and the bomb was the response - and the doctrine treats them as complementary: the statement provides the fire's season, and the bomb provides the statement's consequence. For the full treatment of the statement as the provocation, see The Art of the Statement.

Q: How does a community distinguish between the fire that should be answered and the fire that should be starved?

A: The distinction is the register of the reviews. The genuine wave is a community's honest reaction to a real change, and it is answered with the fix - the developer addresses the real complaint and the wave subsides. The bomb is an organized campaign, and it is starved with the counter-fire - the developer withholds the fuel and lets the campaign burn out. The distinction is read in the signatures: the coordinated timing, the identical phrasing, the new accounts. The commander who can tell the genuine complaint from the organized campaign has found the exact counter, and the counter is the difference between the fix that satisfies and the silence that starves.

Q: What is the role of the neutral audience in the review war?

A: The neutral audience is the battlefield. The review bomb is fought over the rating, and the rating is read by the neutrals - the players who have not yet chosen, the communities that have not yet taken sides. The neutrals decide which party is respectable, and they decide by reading the conduct: the target who fights the fire looks burned, and the target who starves it looks stable. The neutral audience is the jury of the review war, and the doctrine's every counsel - the silence, the counter-fire, the unlit fire - is aimed at the jury's reading.

Q: How should the doctrine be taught to a community's members?

A: The doctrine's counsel is that the members are taught by the visible practice, not by the lecture. The community that withholds its fuel in public, that refuses the retaliatory wave on the record, and that continues its ordinary life through the fire teaches its members the discipline by demonstrating it. The member who watches the leadership starve a fire learns that the fire dies without fuel; the member who watches the leadership light a retaliatory wave learns that the fire is the community's own instrument. The practice is the teaching, and the community that practices the doctrine in public is the community whose members practice it in private.

Glossary

Term	Definition as used in this article
The review bomb	The coordinated negative-review campaign aimed at moving a public rating
The attack by fire	The doctrine's classification of the review campaign as a fire operation
The ignition window	The interval between the provocation and the campaign; the season of the fire
The provocation	The target's own misstep that makes the bomb legible and gives it its justification
Legibility	The quality of a bomb that the community can see why it happened
The volatile surface	The recent, rapidly-changing rating that a concentrated wave can move
The shared field	The community that both attacker and target occupy; the fire that cannot be confined
The recoil	The damage the fire does to its own organizer in a shared field
The counter-fire	The withdrawal, fix, or invitation that starves the fire of its fuel
The denial	The target's statement calling the reviews coordinated; the fuel of the fire
The unlit fire	The fire that is refused because no advantage is seen in lighting it
The retaliatory wave	The second fire, which confirms the first and is never worth lighting
The wind	The direction of the community's attention; changed by the counter-fire

Appendix A: The Fire Reference

The doctrine is read most quickly as a reference table, and the table is the version a commander can keep with the moderation notes.

Element	What it does	The doctrine's rule	The failure mode
The ignition window	Determines the fire's season	Strike within seventy-two hours	The night breeze that falls
The provocation	Makes the bomb legible	Withhold it as the target	The misstep that arms the weapon
The volatile surface	Carries the fire	Densify the rating as the target	The shallow rating that moves
The shared field	Burns both parties	Never light an unconfined fire	The recoil that burns the attacker
The denial	Feeds the fire	Withhold it always	The statement that fuels the bomb
The counter-fire	Starves the fire	Withdraw, fix, invite	The fight that feeds the flame
The unlit fire	Costs nothing	Move only on an advantage	The retaliation that confirms

The table is the fire doctrine's operational core, and each row is a discipline the commander practices from the moment the fire appears. The commander who works the table has made the review war an instrument rather than a hazard, and the instrument is the chapter's whole practical content.

Appendix B: The Fire Chain

The chapter's full argument, laid out as the chain the doctrine follows from the season of the fire to the fire that was not lit.

The chain is read left to right as a single campaign and top to bottom as the community's whole career with the fire. The provocation is published, and the fire's season decides whether the bomb burns or falls. In a shared field, the fire's recoil is inevitable: the denial feeds it and the fire spreads to the attacker; the withheld fuel and the counter-fire starve it, and the rating recovers above baseline. The chain is the chapter in one movement, and the commander who reads it top to bottom has read the whole doctrine.

The Principle Chain in Full

The doctrine of the review bomb reduces to a chain of principles, each of which follows from the last, and the chain is worth stating in full because it is the load-bearing structure of the chapter. The chain begins with the claim that the review bomb is an attack by fire, and it ends with the claim that the fire that cannot be confined must not be lit.

1. The review bomb is an attack by fire. It sets fire to the target's reputation at its most exposed point, the public rating.
2. Fire has a season. The bomb that begins within its ignition window burns; the bomb that begins late falls.
3. The bomb is armed by the provocation. The target's own misstep makes the campaign legible and gives it its justification.
4. The bomb is carried by the volatile surface. The shallow, recent rating is the field the fire spreads across.
5. The fire burns a shared field. The attacker and the target occupy the same community, and the fire recoils on both.
6. The denial is the fuel. The target's statement confirming the campaign feeds the exact flame it is trying to extinguish.
7. The counter-fire starves the fire. The withdrawal, the fix, and the invitation change the wind.
8. The unlit fire is the safest fire. The commander moves only when an advantage is seen, and the retaliation is never the advantage.

The chain is the chapter's complete argument in eight lines, and the community manager who can recite it has internalized the fire doctrine. Each principle is a line in the chain, and each line is a discipline the community either practices or pays for.

The Fire Doctrine in Practice

The fire doctrine reduces to a set of habits, and the commander who wants to apply it should be able to see the habits clearly, separated from the instruments that carry them. Each habit below is a repetition, not a project: it does not require a campaign, only that the community do the same small thing the same way until it is the community's default.

A checklist may help the server owner or community manager keep the doctrine close at hand:

Practice	What it looks like in peacetime	What it prevents
Withhold the provocation	The community never attacks a rival by name	The misstep that arms the weapon
Build the rating's density	Genuine reviews invited and answered	The volatile surface that carries the fire
Check the season	Every review wave is dated against its provocation	The fire that burns unnoticed
Withhold the fuel	No denial, no "coordinated attack"	The statement that feeds the flame
Publish the counter-fire	Withdraw, fix, or invite re-review	The fight that sustains the fire
Refuse the second fire	No retaliatory waves, ever	The confirmation that makes the fire permanent
Read the ratings	The community reads the reviews, not just the score	The audience that cannot be bombed

None of these practices is dramatic, which is why they are often skipped. The doctrine's whole claim in this chapter is that the review war is decided by the undramatic work: the provocation withheld, the fuel denied, the counter published, the second fire refused. The community that does the undramatic work has made its rating an instrument rather than a target, and the fire, when it comes, will find the instrument ready.

Summary

The review bomb is the drama war's attack by fire, and it is the weapon most likely to be turned on its user. The fire has a season, the ignition window, and a field, the shared community, and the commander who ignores either is burned by the fire he lights. The case of the cosmetics mod demonstrates the doctrine in all of its modes: the provocation that armed the weapon, the denial that fed the flame, the counter-fire that the developer refused, and the unlit fire that the rival wisely declined.

The cohort records Example DW-1022 as the canonical study of the fire that burned the attacker, and the doctrine that follows from it is the doctrine of the shared field. The fire that is lit in a field the attacker shares is a fire that burns both camps, and the only safe fire is the fire that is never lit. The community that reads its ratings, that withholds its fuel, and that refuses the second fire has taken the weapon out of the attacker's hands, and the disarming is the only complete victory in the review war.

Lessons Learned

Lesson	Source of the lesson	Application
Fire has a season; ignite within the ignition window	Example DW-1022	Begin a review response within seventy-two hours of the provocation
Fire burns the shared field and the attacker	Example DW-0441	Never bomb a battlefield that includes your own community
The statement of denial is the fuel of the bomb	Example DW-1022	Do not call reviews coordinated; it confirms the frame
The counter-fire is a public retreat	Example DW-0662	Withdraw the provocation and the fire starves
Do not answer a bait with a bomb	Example DW-1022	Name the campaign and you have joined it
The unlit fire is the safest fire	Example DW-0907	Fix the claims instead of fighting the reviews
Move not unless you see an advantage	Example DW-1022	A fire that cannot be confined must not be lit

Related Doctrine

The Review Bomb is the case study for On the Attack by Fire, where the chapter on fire is developed into a full review-war doctrine, and for The Art of the Counter, which contains the full counter-fire protocol. The provocation that ignited the bomb is examined in The Art of the Statement. The war that followed, Example: The Channel Takeover, shows how the same community turned from destroying a reputation to seizing the ground it was built on. For the community surface where ratings are decided, see Why Discord Embeds Are the Foundation of Server Credibility.