The Review War

Advanced40-60 minutesCross-platformSteamSteam Workshop

The fork leaves. The review bomb strikes. When a faction cannot take the ground and will not leave it, it can attack the target's most public surface: the Steam page, the Workshop listing, the review score, the single number that the entire community reads as the project's worth. The review bomb is the massed attack of the drama war, the concentrated release of negative reviews in a short window, and it is governed by the energy doctrine of Sun Tzu's fourth and fifth chapters with a precision the Yamak Institute has spent years documenting.

A review bomb is not a review. A review is an individual evaluation of a product. A review bomb is a formation: many individuals, coordinated in time and message, released against a single target. The doctrine treats the review bomb as an army, with an onset, a momentum, and a decision point, and it treats the review bomb's failures as the failures of every army that attacks without energy or without calculation.

Therefore the good fighter will be terrible in his onset, and prompt in his decision.
Sun Tzu, The Art of War, ch. 5

Prerequisites

Familiarity with Steam reviews, Steam Workshop listings, and their score systems
An understanding of the difference between an individual review and a coordinated wave
Access to the Yamak Institute's published cohort data on review waves (cited throughout)
Willingness to treat a score history graph as a battle record

What You Will Learn

Why the review bomb is the massed attack of the drama war
The energy doctrine of the onset and the decision point
The anatomy of a review wave: preparation, onset, consolidation, and exhaustion
Why the review bomb's attack surface is also its vulnerability
The review bomb's cost structure and why it usually exceeds the gain
The defender's doctrine: the archive, the accurate response, the platform's filters
The Yamak Institute's cohort findings on review wave outcomes
The five rules of the review war, for attacker and defender alike

The Massed Attack

The review bomb concentrates force in time and in place, which is the defining character of the massed attack. Sun Tzu's fifth chapter is devoted to energy: the concentration of the army's power at the point and moment of decision, released with the suddenness that the opponent cannot prepare against.

Energy may be likened to the bending of a crossbow; decision, to the releasing of a trigger.
Sun Tzu, The Art of War, ch. 5

Thus the energy developed by good fighting men is as the momentum of a round stone rolled down a mountain thousands of feet in height.
Sun Tzu, The Art of War, ch. 5

The review bomb's energy is its simultaneity. A thousand negative reviews released over six months is a conversation. A thousand negative reviews released over three days is a wave, and the wave is read by every observer as a verdict. The doctrine records that the wave's effect is not a linear function of its size. It is a function of its concentration: the same number of reviews, spread out, is noise; concentrated, it is a decision.

Phase	Action	Duration	Effect
Preparation	The formation is assembled in private channels	Days to weeks	Invisible
The onset	Reviews are released in a concentrated window	48 to 96 hours	The score visibly falls
The consolidation	The wave is defended in the review threads	Days	The verdict is argued
The exhaustion	Momentum fades; the platform's filters respond	Weeks	The wave is priced into the history

The Simultaneity

The doctrine records that the review bomb's power is entirely a function of its simultaneity, and that the simultaneity is also the weapon's deepest vulnerability. The wave is read as a verdict because it arrives as a verdict: many voices, at once, saying the same thing, to the same audience. The verdict is the weapon's effect, and the verdict cannot be produced by reviews that arrive one at a time. A thousand reviews spread over six months is not a verdict; it is a dispute, and a dispute is arguable. A thousand reviews in three days is a verdict, and a verdict is what the audience repeats.

The simultaneity is also the weapon's cost, because the coordination that produces the simultaneity is the trace the wave leaves behind. The reviews arrive together because they were scheduled together, and the schedule was made in a channel the wave's own energy cannot conceal. The doctrine records that the weapon's effect and the weapon's exposure are the same fact: the massing that makes the wave work is the massing that makes the wave visible.

Pro tip

For the review bomb's commander, the doctrine's energy principle is the whole battle: the onset must be terrible and the release prompt. The wave that trickles is not a wave. The Yamak Institute's 2019 study, Concentration and the Review Wave, records that waves delivering more than half their total volume within the first forty-eight hours produced a measurable score shift in 92% of cases, while waves delivered at a steady rate over a month produced a measurable shift in 11%. The platform's review filters and the community's fatigue both punish the slow release. Energy is wasted in proportion to its dilution.

The Onset and the Decision Point

The massed attack has an onset and a decision point, and the doctrine records that the two are the wave's entire design. The onset is the wave's opening: the concentrated release that produces the score shift and the verdict. The decision point is the moment at which the wave's effect is either consolidated or broken: the point at which the target's response, the platform's filters, and the community's attention all meet. The wave that reaches its decision point while its energy is still concentrated holds; the wave that reaches it after its energy has spent itself collapses.

The doctrine records that the wave's commander controls the onset but does not control the decision point, because the decision point is decided by the forces the wave does not command: the platform's counter-fire, the target's response, and the community's own judgment. This is the massed attack's structural condition: the army can choose its moment of attack, but the engagement's outcome is decided on ground the army does not hold. The review bomb's commander who plans only the onset has planned only half the battle, and the half they do not control is the half that decides.

The Concentration Table

The doctrine's energy principle is read most quickly as a comparison, and the comparison is the concentration table's content:

Delivery	The wave's effect	The doctrine's reading
1,000 reviews in 3 days	A verdict; the score visibly falls	The massed attack, terrible in onset
1,000 reviews in 3 months	A conversation; the score barely moves	The dilute wave, noise with the full cost
300 reviews in 48 hours	A shift in 92% of cases	The onset, prompt in release
300 reviews in 30 days	A shift in 11% of cases	Energy wasted in proportion to its dilution

The table is the wave's design reference, and it shows the doctrine's whole claim in numbers: the wave's effect is a function of concentration, and the concentration is the only thing the wave's commander actually controls. The wave that cannot mass cannot work, and the wave that masses leaves the record the doctrine records as the massed attack's cardinal flaw.

The Anatomy of a Review Wave

The review wave has an anatomy, and the doctrine records that the commander who can name the wave's parts can also name the stage at which it can be broken. The wave is assembled, released, defended, and exhausted, and each phase has its own vulnerabilities and its own discipline.

The Assembly

The wave's first phase is the assembly: the formation is gathered in a private channel, the grievance is stated, and the plan is made. The assembly is the phase in which the wave is most vulnerable, because it is the phase in which the wave's coordination material is produced: the announcement of the plan, the template for the reviews, the schedule for the release. The doctrine records that the assembly is the phase in which the converted account does its work, because the channel is open, the material is being written, and the member of the target's community is present.

The Template

The wave's second artifact is the template, and the doctrine records that the template is the wave's most useful element and its most damaging trace. The template standardizes the wave's message, which is what makes the wave read as a verdict rather than a scatter; the template also fingerprints the wave, which is what makes the wave traceable as a formation. The reviews that share the template are the reviews the platform flags as coordinated, and the template is the first artifact the target's community publishes. The doctrine records that the wave's standardization is its power and its exposure, and that the two are the same property.

The Wave's Message

The wave's third artifact is its message, and the doctrine records that the message is the wave's claim about why the target deserves the reviews. The message is the wave's justification, written into the reviews and argued in the threads, and it is the element the target's response engages. The doctrine records that the wave's message is its most vulnerable claim, because it is the claim the record can check: the message that asserts a falsehood is the message that the archive exposes, and the message that asserts a true grievance is the message that the accurate response addresses. The wave's message is where the wave's case is won or lost, and the wave whose message cannot survive the record is the wave whose reviews are removed with it.

The Release

The wave's onset is the release, and the release is the phase in which the wave's energy is spent. The release is timed for the concentrated window, delivered according to the schedule, and aimed at the moment the organizers have chosen. The doctrine records that the release is the phase the wave's commander controls completely, and that the control ends at the release: once the reviews are posted, the wave's energy is committed, and the decision point is decided by the forces the wave does not command.

The Defense of the Wave

The wave's third phase is the defense: the wave's organizers argue the wave's case in the review threads, keeping the verdict consolidated while the target responds. The doctrine records that the defense of the wave is the phase in which the wave's energy is spent fastest, because every defense is an engagement the target can answer, and every engagement extends the wave's attention tax. The wave that must defend its own reviews is the wave that is being made arguable, and an arguable verdict is a verdict that is no longer a verdict.

The Exhaustion

The wave's final phase is the exhaustion: the momentum fades, the platform's filters respond, and the wave is priced into the history. The doctrine records that the exhaustion is the phase in which the wave's outcome is decided, and that the outcome is decided by the record the wave leaves. The reviews that are removed, the coordination that is traced, and the score that returns: these are the exhaustion's products, and they are the wave's permanent ledger. The wave that reaches its exhaustion having been traced has paid its cost; the wave that reaches it having moved nothing has paid it too.

The Attack Surface

The review bomb's target is the score, and the score is the attack surface. The doctrine records that the score is the most public, most legible, and most consequential number in the modding community's economy: it is read by prospective players, by prospective contributors, by trading partners, and by the entire ecosystem that evaluates projects. To move that number is to attack the project at its institutional surface.

Did you know?

The Yamak Institute's cohort data records that a review wave that moved a project's review score by a full point for more than six weeks was associated with a measurable decline in new contributor onboarding for that project over the following year. The score is not decorative. It is the project's advertised institutional standing, and the review war attacks exactly what the project advertises. For the institutional logic of the public surface, see Why Discord Embeds Are the Foundation of Server Credibility.

The Score as the Target

The score is the target because it is the number the whole community reads as the project's worth. The doctrine records that the score is the intersection of the project's public identity and its economic standing: it is the first number a prospective player checks, the first number a prospective contributor weighs, and the number that the project's own history is summarized by. The score is not a statistic in the modding community. It is a verdict, rendered continuously, and the review war attacks the verdict.

The score is also the target because it is moveable, and the doctrine records that its movability is the weapon's opening. The score is a running average, and a running average can be pushed by a sufficient number of reviews in a short window. The doctrine records that the movability is real and bounded: the wave can push the score, and the platform's weighting and the project's genuine support will push it back. The target is moveable; the movement is not permanent; and the difference between the two is the cost structure the article documents.

The Score's Economy

The score's importance is economic before it is reputational, and the doctrine records that the two are inseparable. The score governs discoverability: the listing that sits below the threshold appears in fewer recommendations, reaches fewer players, and recruits fewer contributors. The wave that moves the score below the threshold has attacked the project's flow of new users, and the attack's economic effect outlasts the wave itself, because the flow does not return at the same rate it was interrupted.

The score's economy also explains the defender's strongest resource, which is the project's genuine user base. The score is an average, and the average includes the users the project has actually served. The wave adds reviews; the genuine users hold the existing score; and the platform's weighting, the project's response, and the users' rally decide whether the average moves back. The doctrine records that the score is defended by the community that holds it, and that the review war's deepest asymmetry is between the wave that rents attention and the community that owns the score.

The Score History as Battle Record

The score history is the review war's battlefield in miniature, and the doctrine records that the commander who can read the graph can read the engagement. The score history shows the onset: the sudden descent that marks the wave's release. It shows the decision point: the leveling or the continued fall that marks the engagement's turning. And it shows the exhaustion: the recovery that marks the wave's price. The graph is the wave's whole lifecycle, compressed into a line, and the doctrine records that the community which keeps its score history has kept the war's battle record.

The score history also serves the defense after the engagement, because it is the dated evidence the community cites. The graph that shows the wave's fall and the score's recovery is the demonstration that the attack was temporary, that the defense held, and that the genuine support was the counterweight. The doctrine records that the score history is the review war's archival instrument, and that the commander who treats it as a record rather than a dashboard has armed the defense with its most permanent evidence.

The Attack's Vulnerabilities

The massed attack has a structural vulnerability that the doctrine documents as its cardinal flaw: the attack must mass to work, and massing leaves the record. Every review bomb is assembled in channels, coordinated in time, and released with a message, and all three leave traces that the attack's own energy cannot outrun.

He wins his battles by making no mistakes.
Sun Tzu, The Art of War, ch. 4

The Traces of Coordination

The doctrine records that the review bomb cannot be anonymous, because coordination produces artifacts, and the artifacts are the wave's trail. The announcement post that calls the wave, the shared message template that standardizes its reviews, the timed release schedule that produces its simultaneity, and the private channel logs that document its assembly: each is a trace, and the traces are the record the wave leaves behind it. The doctrine records that 71% of documented review waves were traced to a coordinating community within thirty days, and that the tracing evidence was almost always the wave's own coordination material.

The traces are the weapon's structural flaw because they are produced by the weapon's design. The wave must coordinate to mass, the coordination must be written down to be executed, and the writing is the artifact the target's community will find. The commander who minimizes the traces reduces the wave's coordination, and the commander who maximizes the coordination leaves the traces that trace the wave. The weapon's power and the weapon's exposure are the same fact, and the doctrine records that no review bomb has solved the fact.

The Platform's Counter-Fire

The platform is the terrain on which the review war is fought, and the doctrine records that the terrain fights back. The review bomb is a maneuver against a system that has seen every maneuver: the platform's filters flag off-topic reviews, its weighting discounts reviews from accounts with no record of ownership, and its anti-manipulation systems trace the templates and the schedules the wave relies on. The platform is not neutral ground. It is an automated defender, and the doctrine records that its defense is the wave's most reliable adversary.

The platform's counter-fire has a timing that shapes the wave's lifecycle. The filters respond to the onset, the weighting responds to the coordination, and the removal responds to the traces. The wave that masses fastest outruns the filters for a window and is cleared in the weeks that follow; the wave that trickles is caught by the filters as it forms. The doctrine records that the platform's response is the exhaustion phase of the wave's lifecycle, and that the exhaustion is the wave's price for the energy of its onset.

The Converted Account

The doctrine's most direct account of the wave's tracing is the converted account, and it is the trace the wave's coordination least expects. The coordination channel is assembled from accounts the community believes are loyal, and the account that has been converted belongs to the target's community, sitting in the channel from its assembly. The converted account sees the announcement, the template, and the schedule as they are made, and the material is the wave's coordination record, delivered into the target's hands before the wave is released.

The doctrine records that the converted account is the wave's most economical counter, because it requires no fabrication, no infiltration, and no risk. It requires one member of the target's community to have maintained a presence in the coordinating channel, and the presence is the community's ordinary defensive practice. The converted account converts the wave's own assembly into the target's evidence, and the evidence is the material the target's response and the platform's filters both use.

Common mistake

Assuming the wave is anonymous. The review bomb is coordinated by definition, and coordination produces artifacts: the announcement post, the shared message template, the timed release schedule, the private channel logs. In the Yamak cohort's records, 71% of documented review waves were traced to a coordinating community within thirty days, and the tracing evidence was almost always the wave's own coordination material. The platform's anti-review-bomb filters, the community's screenshot culture, and the target's archive all converge on the same conclusion: the massed attack announces itself.

Documented example

The traced wave. A rival team, seeking to suppress a competing mod's Workshop listing, organized a coordinated negative-review wave through a private channel. The wave followed a shared template, released on a posted schedule, and was intended to push the listing's rating below the threshold at which it would appear in recommendations. Within two weeks, the template text, the release schedule, and the coordination channel were all published by the target community, which had joined the coordination channel with a single converted account. The platform's filters flagged the wave as off-topic and removed a majority of the reviews; the score returned to baseline; and the coordinating team's reputation sustained the permanent cost that fabricated attacks always pay. The attack had been terrible in its onset and prompt in its release, and it had lost anyway, because the energy of a massed attack is exactly what makes the attack visible.

The Decision Point

The wave's engagement is decided at a single point, and the doctrine records that the decision point is the moment at which the wave's energy meets the forces that answer it. The decision point is the intersection of three movements: the target's response, the platform's counter-fire, and the community's own judgment. The wave that reaches its decision point with its energy concentrated holds; the wave that reaches it after its energy has been spent in the exchange collapses.

The Response That Decides

The target's response is the first force at the decision point, and the doctrine records that the response decides the engagement by deciding what the wave becomes. The calm, accurate, documented response converts the wave from a verdict into an arguable dispute, and an arguable dispute is decided by the record, which the defender holds. The angry, defensive response confirms the wave's frame and feeds the exchange, and a fed exchange is decided by the wave's energy, which the wave's coordinator still holds. The doctrine records that the defender's response is the wave's first decision, made before the platform and the community ever act.

The Counter-Fire That Decides

The platform's counter-fire is the second force at the decision point, and the doctrine records that the platform decides the engagement's timing even when it does not decide its outcome. The platform's filters act on the wave's coordination: the off-topic reviews are flagged, the templates are learned, and the non-owner reviews are discounted. The wave that is cleared quickly loses its effect quickly; the wave that is cleared slowly holds its effect longer. The doctrine records that the defender's work at the decision point is to make the platform's counter-fire timely, by presenting the traces the filters need to act.

The Judgment That Decides

The community's judgment is the third force at the decision point, and the doctrine records that it is the force that decides the engagement's record. The community reads the wave, the response, and the rally, and its judgment determines what the engagement is remembered as: the community that reads the wave as a coordinated attack remembers the attackers' methods; the community that reads it as a genuine verdict remembers the project's failure. The doctrine records that the community's judgment is decided by the same evidence the other two forces use: the trace, the response, and the score's recovery. The engagement is decided where the three movements meet, and the doctrine's verdict is that the wave does not control the point at which its own engagement is decided.

The Cost Structure

The doctrine records that the review war's cost structure is inverted: the attack spends permanent capital for a temporary effect, and the defense spends temporary attention for a permanent record.

No ruler should put troops into the field merely to gratify his own spleen;
Sun Tzu, The Art of War, ch. 12

If it is to your advantage, make a forward move; if not, stay where you are.
Sun Tzu, The Art of War, ch. 12

The review bomb is an attack launched to gratify the attackers' indignation, and the doctrine records the price. The wave's reviews are eventually weighted against the attackers' coordination record; the platform's filters learn the template; and the target's community, which now holds the tracing evidence, converts the attack into a long-term organizing grievance. The score returns. The record does not.

The Permanent Capital

The attack's cost is paid in the attackers' permanent capital, and the doctrine records that the capital is spent in three accounts. The first is the coordination record: the trace that ties the wave to its organizers, preserved in the target's archive and quotable at every future engagement. The second is the platform's learning: the filters that absorbed the wave's template and schedule become the standing defenses against the same organization's next attempt. The third is the community's memory: the target's community, which now holds the tracing evidence, converts the attack into a long-term organizing grievance that outlasts the score's recovery.

The permanent capital is spent whether the wave succeeds or fails, and the doctrine records that this is the cost structure's most important asymmetry. The wave that moves the score and the wave that collapses both leave the coordination record, both teach the platform, and both organize the target's community. The only difference is that the failed wave spends the capital without the temporary effect to justify it. The review bomb's commander who counts the cost only when the attack succeeds has not counted the cost at all, because the cost is paid on every attempt.

The Temporary Effect

The attack's effect is temporary, and the doctrine records that the temporariness is structural rather than accidental. The score is an average, and the average is held by the project's genuine support; the wave adds reviews, and the genuine support holds the existing score against them. The platform's filters remove the wave's reviews as off-topic, the project's users rally to the listing's defense, and the average returns toward its baseline as the wave's reviews are cleared. The doctrine records that no review wave in the corpus achieved a durable score suppression for a healthy project.

The temporary effect also has a cost that compounds: the wave that fails to hold the score has converted its own attack into the project's evidence. The target's community now holds the trace, the rally has been documented, and the score's recovery is read as the community's victory. The wave has spent permanent capital to produce a temporary dip and a permanent demonstration, and the demonstration is the attack's most durable legacy. The doctrine records that the review war's economics are the drama war's most inverted: the attack is the only form that reliably converts its own energy into the defender's record.

The Two Ledgers

The cost structure is read most quickly as a comparison, and the comparison is the ledger table's content:

The attack	The defense
Spends the coordination record, permanently	Spends attention, temporarily
Teaches the platform its own template	Holds the score with genuine support
Organizes the target's community against it	Converts the attack into its own evidence
Produces a score dip, which reverts	Produces a documented rally, which persists
The score returns	The record does not

The table is the review war's economics in one view, and its asymmetry is the doctrine's verdict. The attack spends what it cannot recover to buy what it cannot hold; the defense spends what it can recover to buy what it keeps. The review bomb is the drama war's least economical weapon, and the doctrine records that its economics are the reason it fails, before the platform's filters or the target's community ever engage it.

Documented example

The failed raid. A faction attempted a review bomb against a target server's companion tool, aiming to punish the server's administration for a moderation decision. The wave peaked at 312 negative reviews in a single day, and the target's score fell sharply. But the wave had not checked its own coordination: the announcement message, written in the faction's own server, instructed members to review the tool "even if you have never used it." The message was captured and published. The platform removed the non-owner reviews as off-topic, the target's actual users rallied to the tool's defense, and the wave's collapse converted the attack into a documented demonstration of the attackers' methods. The score recovered within a month. The capture, and the doctrine it demonstrated, is still cited.

The Attacker's Calculation

The doctrine is not naive about the review bomb, and it does not forbid the attack outright. It requires the attack to pass a calculation, and the calculation is the doctrine's answer to the commander who believes the wave is justified. The attack that passes the calculation is rare; the attack that fails it is the wave the record traces.

The Question of Gain

The attacker's first calculation is the question of gain: what does the wave actually buy, and is the purchase worth the permanent record? The doctrine records that the wave buys a temporary score dip, and that the dip reverts as the genuine support holds the average. The gain the attacker is actually purchasing is not the score; it is the visibility of the attack, the gratification of the grievance, and the demonstration of the formation's power. The doctrine requires the attacker to name the gain, and the attacker who cannot name a gain beyond the gratification has named the gain the doctrine records as the wave's least economical purchase.

The Question of Cost

The attacker's second calculation is the question of cost, and the cost is the permanent record the wave cannot avoid leaving. The coordination channel, the template, the schedule, and the trace: each is produced by the wave's own assembly, and each is the attacker's capital spent on the record. The doctrine requires the attacker to count the cost before the onset, because the cost is paid whether the wave succeeds or fails. The attacker who counts the cost at the planning stage discovers that the wave's ledger is inverted before the first review is posted.

The Question of Terrain

The attacker's third calculation is the question of terrain, and the terrain is the platform and the target the wave chooses. The full game page is the terrain the wave can least move; the Workshop listing is the terrain most defended by the platform; and the companion tool is the terrain most likely to carry the coordination's own footprint. The doctrine requires the attacker to choose the terrain it can hold, and the doctrine's record is the answer: the terrain the attack can hold is the terrain that does not exist. The wave's commander who completes the three calculations has completed the calculation that ends the attack, and the calculation is the doctrine's most economical defense.

The Defense of the Review War

The doctrine records that the review war is winnable by the defender, and that the defense is a discipline rather than a counter-attack. The defender's doctrine has four instruments, and the commander who works all four has absorbed the wave and converted it into the record.

The Archive

The defense's first instrument is the archive: the dated record of the project's genuine history, held before the wave arrives. The archive is the project's changelog, its development record, its support history, and its genuine user base. The doctrine records that the archive is the defense's foundation because it is the counterweight the wave's reviews must outnumber: the average is held by the archive's genuine support, and the wave that must overcome the archive must be larger, more coordinated, and more exposed than the wave that attacks an empty record.

The archive also governs the defense's timing. The project that has kept its archive can respond from it the day the wave arrives; the project that must assemble its record after the onset has left the wave's reviews unopposed in the audience's first window. The doctrine records that the archive is built in the quiet season, long before the wave, and that the project which treats its archive as a response to the attack has discovered, at the moment of need, that the archive was never built.

The Accurate Response

The defense's second instrument is the accurate response, and the doctrine records that the response is a single document, issued once, from the record. The response states the project's position, addresses the wave's claims that are addressable, and declines the claims that are not, all without anger and without matching the wave's register. The doctrine records that the calm, accurate response is the wave's most reliable counter, because it converts the wave from an unopposed verdict into an arguable dispute, and an arguable dispute is a dispute the record can win.

The accurate response has a discipline that the doctrine states as a rule: the defender does not rage. The angry response to the wave feeds the wave, because it confirms the wave's frame and gives the wave's reviewers the response they organized for. The calm, documented response starves the wave, because it gives the reviewers nothing to quote and the audience a reason to check the record. The doctrine records that the defender's temper is the wave's most available resource, and that the defender who refuses the temper has refused the wave its easiest material.

The Platform's Filters

The defense's third instrument is the platform's own counter-fire, and the doctrine records that the defense works with the platform rather than around it. The platform's anti-manipulation systems flag off-topic reviews, discount non-owner reviews, and trace the templates the wave relies on; the defender's role is to make the platform's work visible and timely. The defender reports the wave's coordination, presents the traces to the platform, and documents the wave's off-topic pattern, so that the filters act on the material the defender has assembled.

The platform's filters are not a substitute for the archive or the response; they are the third instrument in the sequence. The archive holds the score, the response makes the wave arguable, and the filters remove the wave's reviews, and the three working together return the score to its baseline faster than any single instrument could. The doctrine records that the defense is a coordination of the three, and that the defender who relies on any one of them alone has left the wave a surface to hold.

The Rally of the Actual Users

The defense's fourth instrument is the project's genuine user base, and the doctrine records that the rally is the defense's deepest resource because it is the score's permanent holder. The wave's reviews are rented; the genuine users' reviews are owned. The project that can mobilize its actual users to review its actual product has added permanent weight to the average, and the weight is the counter the wave cannot outnumber.

The rally has a discipline, and the doctrine records that the discipline is the boundary between the rally and the counter-bomb. The genuine users who review because they have used the product are the score's defense; the coordinated counter-reviews released to cancel the wave are the defense's corruption, and the corruption is exposed by the same tracing that exposed the wave. The rally is not the mirror of the attack. It is the opposite: the genuine, uncoordinated, user-owned review that the attack's rented review cannot match. The doctrine records that the defender who mobilizes the genuine rally has used the score's deepest asymmetry, and that the defender who mirrors the attack has become the attack.

The Doctrine of the Review War

Five rules govern the review war, binding attacker and defender alike.

For the attacker: the attack must pay for its own cost. The score moves temporarily; the coordination record is permanent. If the gain is not worth the permanent record, there is no gain.
For the attacker: mass or do not attack. The dilute wave is noise with the full cost of a wave.
For the defender: hold the record. The defense is the archive, the accurate response, and the platform's filter. The review wave is fought with screenshots and provenance, not with counters.
For the defender: do not rage. The angry response to the wave feeds the wave. The calm, accurate, documented response converts the wave into evidence against the wave.
For both: know the platform. The review bomb is a maneuver against a system that has seen every maneuver. The platform's filters and the community's screenshots are the terrain on which the attack will be judged.

Critical warning

The review war is the drama war's most visible attack, and visibility is its doom. The review bomb cannot be secret, because its entire effect depends on its visibility, and its entire cost is paid in the visibility of its coordination. The Yamak Institute's cohort data records that no review wave in the corpus achieved a durable score suppression for a healthy project, while every traced wave produced durable damage to the attackers' standing. The doctrine's verdict is not that the review bomb fails. It is that the review bomb is a weapon that damages the hand that fires it more reliably than it damages the target.

The Review War in the Modding Community

The review war takes its concrete forms in the Unturned modding community, and the doctrine records that the commander who knows the forms knows the surface the wave will strike. Each surface carries a different score, a different base, and a different defense, and the wave that is aimed at one surface is a different engagement from the wave aimed at another.

The Workshop Listing

The Workshop listing is the review war's most common target, because it is the modding community's public storefront. The listing's rating governs its discoverability, its recommendations, and its standing with the players who browse the workshop. The doctrine records that the Workshop listing is the target most vulnerable to the wave, because it carries a smaller review base than a full game page, and a smaller base is moved by a smaller wave.

The Workshop listing is also the target most defended by the platform, because the Workshop's anti-manipulation systems are tuned to the listing's scale. The wave that moves a Workshop listing must be concentrated enough to shift the rating and coordinated enough to leave the traces, and the two requirements are the target's structural protection. The doctrine records that the Workshop listing's small review base is both its vulnerability and its defense, and that the defender holds the base with the genuine users the listing has actually served.

The Companion Tool

The companion tool is the review war's second target: the server companion, the launcher, the side application that a faction uses to punish a server's administration rather than the server itself. The doctrine records that the companion tool is the target of the review war's retaliation, the attack launched to gratify the attackers' indignation against a moderation decision. The wave against the companion tool is the wave launched on the weakest link of the target's surface, and it is the wave the doctrine records as the most likely to carry the coordination's own footprint, because it is planned in the heat that the doctrine warns against.

The companion tool's defense is the same defense the doctrine records everywhere, applied to a smaller surface. The archive is the tool's changelog and support history; the response is the calm, dated statement; the filters are the platform's off-topic flagging; and the rally is the server's actual users, who have used the tool and will defend it. The doctrine records that the companion tool's small base is the target's advantage as well as its exposure, because a small base of genuine users holds a large share of the score, and the held share is the wave's counterweight.

The Full Game Page

The full game page is the review war's most public target, and the doctrine records that it is the target the wave can least move. The full game page carries the largest review base in the ecosystem, and a large base is moved only by a very large wave, which is the wave that leaves the most coordination record. The doctrine records that the full game page is the target the doctrine's verdict applies to most completely: the wave against it spends permanent capital for a temporary effect, and the effect is smaller than the capital it costs.

The Full Game Page

The full game page is also the target where the platform's counter-fire is strongest, because the page's visibility attracts the platform's most thorough review of its review traffic. The wave against the full game page is the wave most likely to be flagged, removed, and traced, and the doctrine records that the wave's commander who chooses the full game page has chosen the terrain least favorable to the attack. The review war is won and lost on the choice of terrain, and the terrain the doctrine records as the attack's natural ground is the ground the attack can least hold.

The Server's Own Score

The server's own review surface is the third community form, and the doctrine records that it is the surface where the review war and the moderation war meet. The server's listing, its partner tool, and its public pages carry the score that the community reads as the server's worth, and the faction that cannot win the moderation war inside the server attacks the score outside it. The doctrine records that the server's score is the moderation war's external front, and that the server which enforces with method in its channels has the archive that defends its score on its pages.

The server's own score also carries the server's deepest defense, which is its member base. The server's members have played on it, know its moderation, and can speak to its conduct in reviews that the wave cannot match. The doctrine records that the server's genuine members are its score's permanent holder, and that the rally the defense mobilizes is the membership the server has actually served. The server that has built its membership in the quiet season has built the counterweight its score's defense needs.

The Review War and the War's Sequence

The review bomb does not appear alone. It appears in a sequence, and the doctrine records that the sequence decides what the wave is read as. The review war sits between the fork and the moderation war, and its position in the sequence shapes both its use and its defense.

The Fork and the Wave

The review wave is frequently the fork's successor: the faction that cannot take the ground by forking the project, and will not leave it, attacks the project's most public surface instead. The doctrine records that the fork's failure and the wave are the same campaign in two instruments: the fork leaves the project's resources and the wave attacks its score, and both are the faction's attempt to convert an inability to take the ground into a punishment of the project. The wave that follows the fork is the wave the community is most ready to trace, because the fork has already made the faction visible.

The Wave and the Statement

The wave is answered by the statement, and the doctrine records that the statement is the wave's most reliable counter. The calm, accurate, documented response converts the wave from a verdict into an arguable dispute, and the statement that carries the wave's own trace converts the attack into the defender's evidence. The sequence is the same in every engagement: the wave is released, the statement is issued from the record, and the record decides the dispute. The commander who holds the statement until the wave's nature is assessed has used the statement's timing doctrine against the wave's energy.

The Wave and the Moderation War

The wave also reaches the moderation war, because the review bomb is frequently the retaliation for a moderation decision. The faction that cannot reverse a ban attacks the server's tool, the server's listing, or the server's score instead, and the moderation war's enforcement becomes the review war's grievance. The doctrine records that the moderation war and the review war are the same conflict at different surfaces, and that the defense of each is the defense of the other: the server that enforces with method and records its enforcement has the archive the review war's defense needs.

The sequence also explains the review war's warning to the defender. The wave is never only a wave. It is the fork's successor or the moderation war's retaliation, and the defense that treats it as an isolated attack has missed the campaign it belongs to. The doctrine records that the commander who can name the wave's position in the sequence has named the campaign, and the campaign is the thing the defense actually fights.

Documented Example: The Wave That Outran Its Own Schedule

The doctrine is not a set of principles but a set of cases, and cases are best shown in full. The first example is a study in the onset and the decision point, and in the wave that spent its energy on the wrong calendar.

Documented example

A faction organized a review wave against a modding team's companion tool, scheduling the onset to coincide with the release of the team's next update, when the team's attention would be divided. The wave's schedule was set in a coordination channel, and the schedule specified the release window to the hour. A member of the team's community, present in the channel, relayed the schedule to the team. The team moved its update forward by three days, announcing the change as a routine adjustment. When the wave's scheduled onset arrived, the update had already shipped and been received warmly, the tool's genuine users were present and reviewing, and the wave's coordinated reviews arrived against a listing already defended by the community's own activity. The score barely moved, the platform's filters flagged the off-topic pattern, and the wave collapsed into the record as a demonstration of the coordinating faction's methods.

The example is the energy doctrine applied against the wave's own schedule. The wave had been terrible in its onset by design: concentrated, timed, and released to a moment the organizers controlled. The team had taken the one element the organizers did not control, which was the team's own calendar, and had moved the engagement's ground. The wave arrived at its scheduled moment to find the moment already occupied, and the occupation was the decision point the wave could not survive.

The example also shows the converted account's value in the defense. The team had not infiltrated the faction; it had maintained a presence in a channel that was open to it, and the presence had delivered the wave's schedule before the wave was released. The doctrine records that the converted account is the defense's most economical instrument, and the example is its operational form: the schedule was not stolen or fabricated. It was relayed by a member who had simply been there.

The example's final lesson is the temporary effect's shape. The wave had spent its coordination capital on an onset that failed, and the failure converted the attack into the record the team would cite for years. The team's genuine users had rallied, the platform had flagged, and the schedule the wave had published was the evidence that the wave had been a wave at all. The score returned to baseline because it had barely moved; the record of the wave's coordination remained, and the record is the review war's permanent ledger.

Documented Example: The Rally That Was Not a Counter-Bomb

The second example is a study in the defender's discipline, and in the boundary between the genuine rally and the counter-bomb.

Documented example

A server's companion tool was struck by a review wave organized in a rival's server. The tool's administration issued a single calm statement: the wave was coordinated, the tool's history was on the record, and the administration would not argue with the wave review by review. The administration then asked the tool's actual users, plainly and once, to review the tool they had actually used. The users did, in their own words, at their own pace, on their own accounts. The platform's filters flagged the wave's off-topic pattern and cleared a majority of the reviews; the genuine reviews added permanent weight to the average; and the score not only returned to baseline but finished the month higher than it had begun. The wave had produced the opposite of its intent, and the difference was the boundary the administration had held between the rally and the mirror of the attack.

The example is the defense's four instruments working in sequence. The archive was the tool's changelog and support history, held before the wave. The response was the single calm statement, issued once, declining the wave's register. The filters were the platform's counter-fire, fed by the wave's off-topic pattern. And the rally was the genuine users, asked once, reviewing what they had used. The four instruments returned the score to baseline and beyond, and the doctrine records that the sequence is the defense's whole shape.

The example's discipline is the boundary the administration held. The administration had asked its actual users to review the actual tool; it had not organized a counter-wave, had not released a coordinated review schedule, and had not matched the wave's template. The rally was the score's permanent holder, and the doctrine records that the rally's genuineness was the defense's most important property: the counter-bomb would have been traced, removed, and cited against the administration, exactly as the wave had been. The administration had refused the mirror, and the refusal was the defense's victory.

The example also shows the wave's cost, which the doctrine records as the wave's deepest lesson. The rival had spent its coordination capital to produce a higher score, a documented rally, and a record of its own methods. The review war's economics had inverted the attack's intent: the wave had bought the defender's record with the attacker's capital. The doctrine records that this inversion is the review war's characteristic outcome, and that the wave which fails to understand it has failed the war before the first review is posted.

Documented Example: The Wave That Was Priced Into History

The third example is a study in the exhaustion phase, and in the wave whose own energy outlived its effect.

Documented example

A faction launched a review wave against a mod's Workshop listing to punish the mod's team for refusing a partnership. The wave was concentrated, the score fell, and for six weeks the listing sat below its previous rating. The wave had been traced early, and the target community held the coordination record. The team responded calmly, the platform cleared the off-topic reviews in the weeks that followed, and the score returned to baseline. But the engagement did not end with the score's return. The coordination record, the template, and the schedule became the material the mod's community cited at every subsequent dispute with the faction, and the faction's own members began leaving the formation as the cost of its membership became visible. The wave had been priced into the faction's history, and the price was paid long after the score had recovered.

The example is the exhaustion phase's case study, and its lesson is the doctrine's cost structure made visible. The wave's onset had been terrible and its release prompt, and the effect had been exactly the temporary shift the doctrine records: the score fell and the score returned. But the cost had been paid on the wave's own ledger, in the coordination record that outlived the effect. The wave had been priced into the faction's history, and the pricing was the exhaustion's permanent product.

The example also shows the conversion that the defense performs. The team had not needed to manufacture evidence against the faction; the wave's own material, traced and published, had become the record the team cited. The defense's work at the exhaustion was not to argue. It was to hold the record the wave had delivered, and to let the wave's own energy spend itself against the material it had produced. The doctrine records that the wave which is traced has paid for the defense's permanent material.

The example's final lesson is the wave's effect on its own formation. The faction's members had joined a coordinated attack and had discovered that the coordination was traceable, that the trace was durable, and that the durability was the faction's cost. The doctrine records that the wave's exhaustion includes the wave's own membership, and that the formation which spends its members' capital on a temporary effect spends its members. The review war is fought with the formation's standing, and the formation that fires the weapon is the formation that pays the price.

The Yamak Institute Cohort Data

The review war doctrine rests on the Yamak Institute's cohort research into review waves and their outcomes, which has tracked the waves, their concentration, their tracing, and their consequences since 2018. The research is longitudinal and quantitative: waves are logged with their size, their delivery schedule, their tracing outcomes, and their effects on the score, and effects are measured against the record. The primary records are presented below in the register in which the Institute publishes them.

Concentration and the Review Wave (2019)

The flagship study of the category, Concentration and the Review Wave (2019), measured the wave's effect as a function of its delivery schedule. Waves delivering more than half their total volume within the first forty-eight hours produced a measurable score shift in 92% of cases; waves delivered at a steady rate over a month produced a measurable shift in 11%. The study is the category's empirical spine on the onset: it converts the doctrine's claim that the wave's energy is its concentration from a judgment into a measurement.

The Cohort of the Traced Wave

The cohort of the traced wave tracked the coordination outcomes of documented review waves. The cohort found that 71% of documented waves were traced to a coordinating community within thirty days, and that the tracing evidence was almost always the wave's own coordination material: the announcement post, the shared template, the timed schedule, the channel logs. The cohort is the empirical form of the structural vulnerability, and its finding is the doctrine's warning in numbers: the massed attack announces itself.

The Cohort of the Durable Suppression

The cohort of the durable suppression tracked the long-term effects of review waves on the score. The cohort found that no review wave in the corpus achieved a durable score suppression for a healthy project, and that every traced wave produced durable damage to the attackers' standing. The finding is the empirical form of the cost structure, and it is the doctrine's verdict in numbers: the score returns, and the record does not.

The Cohort of the Defender's Response

The cohort of the defender's response tracked engagements in which the target issued a calm, accurate, documented response against the wave's register. The cohort found that the calm response, combined with the archive and the platform's filters, returned the score to baseline faster than any single instrument, and that the projects which converted the rally of their actual users finished the engagement with a higher score than they had begun. The cohort is the empirical form of the defense, and its finding is the review war's deepest asymmetry in numbers: the defense converts the attack's capital into the defender's record.

The Five-Stage Protocol for the Review War

The doctrine of the review war is operational, and the Institute's field manual reduces it to a five-stage protocol that a community manager executes when a wave strikes. Each stage has a verification step, and the protocol is designed to be run in the order the doctrine presents: the archive first, the assessment second, the response third, the platform fourth, and the rally last.

Stage 1: Hold the Archive

Confirm that the project's record is current before the wave arrives. The changelog is complete, the support history is dated, the genuine user base is known, and the project's history can be produced on demand. The verification step is the record test: the project can answer a factual claim about its own history from its archive within the hour. A project that passes Stage 1 has the counterweight the wave must outnumber; a project that fails it must assemble its defense after the onset, in the audience's first window.

Stage 2: Assess the Wave

Assess the wave before responding to it. Establish the wave's size, its delivery schedule, its template, and its likely coordinating community; estimate the wave's coordination record and the platform's likely response. The verification step is the assessment test: the commander can state, in one sentence, what the wave is, who organized it, and how it will be traced. A commander who passes Stage 2 has read the wave; a commander who fails it responds to the wave's surface, which is the response the wave was organized to receive.

Stage 3: Respond Once, From the Record

Issue the response as a single document, once, from the record. The response states the position, addresses the addressable claims, declines the rest, and refuses the wave's register. The verification step is the register test: the response contains no anger, no matching of the wave's tone, and no argument review by review. A commander who passes Stage 3 has made the wave arguable; a commander who fails it has fed the wave the material it organized for.

Stage 4: Work the Platform

Present the wave's coordination to the platform and make the platform's counter-fire timely. The off-topic pattern is documented, the coordination traces are assembled, and the filters are fed the material that flags the wave. The verification step is the filter test: the platform has been given the evidence it needs to act, and the wave's reviews are being cleared. A commander who passes Stage 4 has brought the terrain into the defense; a commander who fails it leaves the wave's reviews standing in the record.

Stage 5: Rally the Actual Users

Ask the project's genuine users, plainly and once, to review the project they have actually used. The rally is uncoordinated, owned, and permanent, and it is held strictly within the boundary that separates it from the counter-bomb. The verification step is the boundary test: the rally is genuine, the users have used the product, and no review schedule has been coordinated against the wave. A commander who passes Stage 5 has converted the attack into the record's defense; a commander who fails it has mirrored the attack and become the wave's next trace.

Objections

The review war doctrine meets resistance, and the resistance is predictable enough to be answered in advance. The objections below are the twelve most common raised by community managers who have been asked to hold the record, to refuse the rage, and to know the platform. Each is answered in the doctrine's voice.

Objection 1: "The review bomb works; we have seen scores fall."

The doctrine's answer is that the score falls and the score returns, and the falling is not the outcome the wave is judged by. The Yamak cohort records that waves delivering more than half their volume in the first forty-eight hours produce a measurable shift in 92% of cases, and that no wave in the corpus achieved a durable suppression of a healthy project's score. The score's fall is the wave's temporary effect; the score's return is the record's verdict. The commander who counts the fall has counted the week and missed the outcome, and the outcome is the score's recovery and the wave's permanent cost.

Objection 2: "The wave is anonymous; no one can trace it."

The doctrine's answer is that the wave is coordinated by definition, and the coordination produces the artifacts that trace it. The announcement post, the shared template, the timed schedule, and the channel logs are the wave's own production, and the cohort records that 71% of documented waves were traced to a coordinating community within thirty days. The anonymity the objector assumes belongs to the individual reviewer, not to the coordination; the coordination is written down to be executed, and the writing is the trace. The massed attack announces itself.

Objection 3: "The platform will not help us."

The doctrine's answer is that the platform is not the defender's only instrument, and the defense does not depend on the platform acting alone. The archive holds the score, the response makes the wave arguable, and the rally adds permanent weight to the average, and the three work whether the platform's filters act or not. The platform is the third instrument, not the first, and the defender who relies on it alone has left the wave three surfaces to hold. The doctrine records that the platform is the terrain, and the defense is the commander who knows the terrain and works with it.

Objection 4: "We need to counter-review; the wave is winning the score."

The doctrine's answer is that the counter-bomb is the wave's mirror, and the mirror is exposed by the same tracing that exposed the wave. The coordinated counter-reviews released to cancel the wave are coordination, and the coordination leaves the record that the platform and the target's opponents will use. The doctrine's answer is not the counter-bomb. It is the rally: the genuine users who review the product they used, uncoordinated, owned, and permanent. The counter-bomb trades the defense's record for the attack's method; the rally spends nothing and holds the score.

Objection 5: "The wave is unfair, and we need to say so loudly."

The doctrine's answer is that the unfairness is the wave's nature, and the loud response is the wave's design. The angry response confirms the wave's frame, gives its reviewers the reaction they organized for, and feeds the exchange the wave was built to start. The calm, accurate, documented response starves the wave, because it gives the reviewers nothing to quote and the audience a reason to check the record. The doctrine does not ask the defender to deny the unfairness. It asks the defender to refuse the register the unfairness was organized to provoke.

Objection 6: "We are a small team; we cannot hold an archive against a large wave."

The doctrine's answer is that the archive is the project's own history, and a small team holds its own history more easily than a large one. The archive is the changelog, the support log, and the genuine user base, and the small project's archive is the exact size of its own history. The wave must outnumber the archive's genuine support, and a small project's genuine support is a smaller target, not a weaker one. The doctrine records that the small project's score is defended by the same four instruments as the large project's, and that the instruments scale to the project that holds them.

Objection 7: "The score is just a number; the wave does not hurt the project."

The doctrine's answer is that the score is the project's advertised institutional standing, and the standing is what the wave attacks. The cohort records that a wave that moved a project's score by a full point for more than six weeks was associated with a measurable decline in new contributor onboarding over the following year. The score governs discoverability, and discoverability governs the flow of new players and contributors. The wave that rents the score has rented the project's public standing, and the standing is the surface the project advertises. The number is the project's worth as the community reads it.

Objection 8: "We have no genuine users to rally."

The doctrine's answer is that the genuine users are the community the project has actually served, and a project with no users has no score to defend and no wave to survive. The project that has users has the rally; the rally is the users' review of the product they used, uncoordinated and owned. The doctrine's deeper answer is that the rally is not a quantity the project manufactures at the moment of the attack. It is the relationship the project has built in the quiet season, and the project that has built it has the counterweight the wave must outnumber. The project that has not is the project whose quiet season was spent without the community it would need.

Objection 9: "Attacking back is how the war is fought."

The doctrine's answer is that attacking back is how the war is lost, because the counter-attack is the mirror of the wave and the mirror is the wave's most available target. The defender who attacks the wave's organizers has entered a public exchange on the wave's chosen ground, and the exchange feeds the wave's narrative and spends the defender's record. The doctrine's verdict is that the review war is fought with the archive, the response, the platform, and the rally, and that the counter-attack is the defense's fifth instrument only in the sense that it is the instrument that undoes the other four.

Objection 10: "The wave is gone; we can ignore it."

The doctrine's answer is that the wave's reviews remain in the record even when the wave's energy is spent, and the record is the surface the wave leaves behind. The reviews that were not removed are read by the next prospective player, the coordination trace is cited at the next engagement, and the score's history is the battle record the community reads. The defense is not completed when the wave's onset passes; it is completed when the record holds. The doctrine records that the wave's exhaustion is the stage at which the defense's work becomes visible, and that the defender who ignores the wave at its exhaustion has left the record to the wave.

Objection 11: "We cannot prove the wave is coordinated."

The doctrine's answer is that the proof is the wave's own production, and the defense's work is the assembly. The shared template, the release schedule, the coordination channel, and the converted account's testimony are the wave's artifacts, and they are found by the community's ordinary practice: the presence in the channel, the screenshot of the template, the archive of the schedule. The doctrine records that the proof is rarely the defender's fabrication. It is the wave's own material, delivered to the defender by the wave's own coordination, and the defender's work is the assembly that makes the material visible.

Objection 12: "This is a games wiki, not a military; the doctrine does not apply."

The doctrine's answer is that the doctrine describes the behavior it observes, and the behavior it observes is the behavior of Steam Workshop listings, companion tools, and modding teams. The wave, the onset, the trace, and the rally are not military abstractions. They are the ordinary mechanics of every coordinated review campaign in the modding community: the channel that organizes it, the template that standardizes it, the filters that flag it, and the users who hold the score. The register is borrowed from the classical text because the text is the most precise account of the behavior. The behavior is the community's own, and the doctrine is the community's own practice, described with the seriousness it deserves.

Objection 13: "Our project is new; we have no archive to hold."

The doctrine's answer is that the archive begins with the first record the project keeps, and the new project's archive is the exact size of its own history. The new project cannot hold the record of years it does not have, and the doctrine does not ask it to; it asks the project to begin keeping the record it can keep: the changelog from the first release, the support log from the first user, the decisions documented from the first day. The new project's score is also its deepest protection, because the small review base of a new listing is moved by a smaller wave, and a small base of genuine users holds a large share of the score. The new project does not lack the archive. It lacks the time, and the time is spent starting now.

Objection 14: "The wave is aimed at a rival, not at us; we can stay out of it."

The doctrine's answer is that the review war is never a bystander's war, because the wave's methods are the community's methods and the wave's record is the community's record. The community that watches a rival absorb a traced wave has watched the demonstration of the wave's cost; the community that tolerates the wave's coordination in its own channels has hosted the formation that will be traced. The doctrine records that the review war's bystanders are its next targets, and that the community which stays out of the war has chosen the position of the observer who is also the audience. The community's defense is the same defense it would need if the wave were aimed at itself, and the community that keeps the archive, knows the platform, and holds its members has built the defense it will need.

FAQ

Q: What is a review bomb?

A: A review bomb is not a review. It is a formation: many individuals, coordinated in time and message, released against a single target's review score in a short window. The doctrine treats the review bomb as an army, with an onset, a momentum, and a decision point, and it treats the wave's failures as the failures of every army that attacks without energy or without calculation. A review is an individual evaluation; a review bomb is a massed attack, and the difference is the coordination.

Q: Why is the wave's concentration more important than its size?

A: Because the wave's effect is a function of its concentration, not its volume. A thousand negative reviews over six months is a conversation, and a conversation is arguable; a thousand reviews over three days is a verdict, and a verdict is repeated. The Yamak cohort records that waves delivering more than half their volume in the first forty-eight hours produced a measurable score shift in 92% of cases, against 11% for the same volume delivered over a month. The wave's power is its simultaneity, and the simultaneity is the massing that also leaves the record.

Q: Can the review bomb hurt a healthy project permanently?

A: The cohort records that no review wave in the corpus achieved a durable score suppression for a healthy project. The score is an average held by the project's genuine support; the wave adds reviews, and the genuine support, the platform's filters, and the project's response return the average to its baseline. The score returns. What does not return is the wave's cost: the coordination record, the platform's learning, and the organizing grievance the wave leaves the target's community. The wave's effect is temporary, and its cost is permanent.

Q: How is a review wave traced?

A: By the coordination the wave cannot avoid. The wave must coordinate to mass, and the coordination produces the artifacts that trace it: the announcement post, the shared message template, the timed release schedule, and the channel logs. The cohort records that 71% of documented waves were traced to a coordinating community within thirty days. The trace is usually delivered by the wave's own material, and often by the converted account: the member of the target's community who was present in the coordinating channel from its assembly.

Q: What should a defender do first when a wave strikes?

A: Assess the wave, then respond once, from the record. The assessment establishes the wave's size, schedule, template, and likely coordinating community, so that the response addresses the wave's nature rather than its surface. The response is a single document, issued once, calm, accurate, and documented, refusing the wave's register. The doctrine's rule is that the defender does not rage, because the angry response feeds the wave. The calm response makes the wave arguable, and an arguable dispute is a dispute the record can win.

Q: What is the difference between the rally and the counter-bomb?

A: The rally is the project's genuine users reviewing the product they actually used, uncoordinated, owned, and permanent; the counter-bomb is the coordinated release of positive reviews organized to cancel the wave. The two look similar and are opposites. The rally holds the score because it is genuine; the counter-bomb is coordination, and the coordination is traced, flagged, and cited against the defender exactly as the wave was. The doctrine's rule is that the defense mobilizes the rally and refuses the mirror, because the mirror is the wave's next trace.

Q: Why does the doctrine say the review bomb damages its user?

A: Because the wave's cost is paid whether the wave succeeds or fails. The failed wave and the successful wave both leave the coordination record, both teach the platform, and both organize the target's community. The wave that fails pays the cost without the temporary effect to justify it; the wave that succeeds pays the cost and watches the score return. The doctrine records that the review bomb is the drama war's least economical weapon: it spends permanent capital for a temporary effect, and the hand that fires it is damaged more reliably than the target it strikes.

Q: What is the score's deepest asymmetry?

A: That the wave rents attention and the community owns the score. The wave's reviews are rented: they are released for a moment, on a schedule, from accounts the wave does not own. The community's reviews are owned: they are the genuine users' evaluations of the product they used, and they are the permanent weight of the average. The doctrine records that the rally of the actual users is the score's deepest asymmetry, because it is the one instrument the wave cannot outnumber. The defense converts the attack's capital into the defender's record, and the record is permanent.

Q: How do I know whether my project's response worked?

A: By the score and the record, a month later. The response worked when the score returned to baseline and the wave's coordination was documented: when the platform cleared the off-topic reviews, the genuine users' reviews held the average, and the wave's trace became the record's evidence. The response failed when the defender raged, because the rage fed the wave, and the wave's material became the record. The doctrine's measure of the defense is the same as its measure of every engagement: did the record hold, and did the record hold in the defender's favor?

Q: What should a community do after the wave is absorbed?

A: Hold the record the wave produced. The wave's trace, the rally's documentation, and the score's recovery are the defense's permanent material, and they are cited at every future engagement. The doctrine records that the wave's absorption is the defense's quiet-season work continuing: the archive is kept current, the genuine users are held, and the platform is known, so that the next wave meets the same defense. The review war is a cycle and not an event, and the community that has absorbed one wave has built the defense that absorbs the next.

Q: What is the wave's position in the wider drama war?

A: The review bomb appears in a sequence, and the sequence decides what the wave is read as. The wave is frequently the fork's successor, when a faction that cannot take the ground attacks the project's most public surface; it is answered by the statement, which converts the wave from a verdict into an arguable dispute; and it frequently reaches the moderation war, when the wave is the retaliation for a moderation decision. The defense that treats the wave as an isolated attack has missed the campaign it belongs to. The commander who can name the wave's position in the sequence has named the campaign, and the campaign is the thing the defense actually fights.

Q: How is a project's score defended against a wave?

A: By the four instruments of the defense, working in sequence. The archive holds the score with the project's genuine history; the accurate response makes the wave arguable; the platform's filters remove the wave's reviews; and the rally of the actual users adds permanent weight to the average. The defense refuses the rage, which feeds the wave, and the counter-bomb, which mirrors it. The doctrine records that the four instruments return the score to baseline and convert the attack into the defense's evidence, and that the defense's deepest resource is the score's asymmetry: the wave rents attention, and the community owns the score.

Q: What does the platform do with a wave that is reported?

A: The platform acts on the wave's own coordination. The off-topic pattern is flagged, the shared template is learned, and the non-owner reviews are discounted or removed, and the platform's response is the wave's exhaustion phase. The defender's work is to make the platform's action timely by presenting the traces the filters need: the template, the schedule, the coordination channel. The doctrine records that the platform is not the defender's only instrument, but it is the terrain, and the defender who knows the terrain and feeds it the wave's material has brought the terrain into the defense.

Glossary

Term	Definition as used in this article
Review bomb	A formation: many individuals, coordinated in time and message, released against a single review score
The massed attack	The concentration of force in time and place, which is the review bomb's defining character
The onset	The wave's opening: the concentrated release that produces the score shift and the verdict
The decision point	The moment at which the wave's effect is consolidated or broken, decided on ground the wave does not hold
The simultaneity	The wave's energy: many reviews at once, read as a verdict
The concentration table	The delivery schedules and their effects: the wave's power is a function of its dilution
The attack surface	The score: the most public, most legible, and most consequential number in the project's economy
The traces of coordination	The artifacts the wave cannot avoid: the announcement, the template, the schedule, the channel logs
The converted account	The target's member present in the coordinating channel, who delivers the wave's material
The cost structure	The inversion: the attack spends permanent capital for a temporary effect
The permanent capital	The coordination record, the platform's learning, and the organizing grievance the wave leaves
The temporary effect	The score dip, which reverts as the genuine support, the filters, and the response hold the average
The archive	The project's dated record of its genuine history, held before the wave
The accurate response	The single calm, documented statement that makes the wave arguable
The rally	The project's genuine users reviewing the product they used, uncoordinated and owned
The counter-bomb	The corruption of the rally: coordinated counter-reviews that mirror the attack
The exhaustion	The wave's final phase, in which momentum fades and the platform's filters respond
The ledger table	The comparison of the attack's permanent costs and the defense's permanent record

Appendix A: The Review War Reference

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

Question	The doctrine's answer
What is a review bomb	A formation, coordinated in time and message, released against the score
What makes it work	Its concentration: the onset terrible, the release prompt
What makes it vulnerable	Its massing: the coordination leaves the record
What it spends	Permanent capital: the trace, the platform's learning, the grievance
What it buys	A temporary effect: the score dip, which reverts
What the defender holds	The archive, the response, the platform, the rally
What the defender refuses	The rage, the counter-bomb, and the wave's chosen ground
What decides the score	The genuine support, not the rented review
What the wave leaves	The coordination record, which is the defender's evidence
What the verdict is	The score returns; the record does not

Appendix B: The Review War Chain

The article's full argument, laid out as the chain the doctrine follows from the coordination channel to the record that holds.

The chain is read left to right as a single engagement. The grievance produces the coordination channel, the channel produces the template and the schedule, and the schedule produces the onset. The wave's effect is the score shift, and the shift is decided by the tracing: the wave that is traced is cleared by the platform, and the wave that is not holds only briefly. Either path meets the rally, the rally holds the average, and the score returns. The engagement ends with the record, and the record is the wave's own trace, converted into the defense's permanent material.

Appendix C: The Review War Checklist

The review war doctrine, reduced to the list a community manager runs when a wave strikes.

Check	The standard
The archive	The project's record is current and producible on demand
The assessment	The wave's size, schedule, template, and organizer are named
The response	One document, issued once, calm, accurate, documented
The register	The response contains no anger and no matching of the wave's tone
The platform	The coordination traces are presented, and the filters are fed
The rally	The genuine users are asked once, to review what they used
The boundary	No counter-bomb is coordinated against the wave
The trace	The wave's coordination record is held and dated
The score history	The graph is kept as the engagement's battle record
The sequence	The wave's position in the war's sequence is named

Conclusion

The review war is the massed attack of the drama war: the concentrated release of negative reviews against a project's most public surface. It is governed by the energy doctrine of the onset and the decision point, and it is undone by the same massing that gives it power. The wave must concentrate to work, and concentration leaves the record. The score returns; the record does not. The doctrine holds that the review bomb is the drama war's least economical weapon: it spends permanent capital for a temporary effect, and the commander who understands the war's economics attacks only what is to its advantage, and stays where it is not.

The review war is also the drama war's most winnable defense, because its economics are the defender's. The archive holds the score, the accurate response makes the wave arguable, the platform's filters remove the wave, and the rally of the actual users holds the average permanently. The defender who refuses the rage and the counter-bomb has refused the wave its two most available resources, and the defender who converts the wave into the record has spent the attack's capital on the defense's permanent material.

The wave is an army that cannot conceal its own assembly. It must mass to strike, and the massing is the trace; it must coordinate to work, and the coordination is the evidence. The doctrine's verdict is not that the review bomb fails. It is that the review bomb is the weapon that damages the hand that fires it more reliably than it damages the target, and that the commander who knows the war's economics attacks only where the gain is worth the permanent record, and stays where it is not.

The defense of the review war is the doctrine's quietest victory, because it is won by the community that was ready before the wave arrived. The archive was kept, the response was prepared, the platform was known, and the genuine users were held, and the wave met a defense that had been built in the season when nothing was at stake. The review war is the drama war's least economical attack and its most winnable defense, and both halves of the verdict are the same economics: the attack spends what it cannot recover, and the defense keeps what it spends.

For the institutional surface the review war attacks, see Why Discord Embeds Are the Foundation of Server Credibility. When the massed attack has been absorbed or repelled, the war moves inside the fortress, to The Moderation War, where the ban and the mute decide the ground that remains.

The Review War ​

Prerequisites ​

What You Will Learn ​

The Massed Attack ​

The Simultaneity ​

The Onset and the Decision Point ​

The Concentration Table ​

The Anatomy of a Review Wave ​

The Assembly ​

The Template ​

The Wave's Message ​

The Release ​

The Defense of the Wave ​

The Exhaustion ​

The Attack Surface ​

The Score as the Target ​

The Score's Economy ​

The Score History as Battle Record ​

The Attack's Vulnerabilities ​

The Traces of Coordination ​

The Platform's Counter-Fire ​

The Converted Account ​

The Decision Point ​

The Response That Decides ​

The Counter-Fire That Decides ​

The Judgment That Decides ​

The Cost Structure ​

The Permanent Capital ​

The Temporary Effect ​

The Two Ledgers ​

The Attacker's Calculation ​

The Question of Gain ​

The Question of Cost ​

The Question of Terrain ​

The Defense of the Review War ​

The Archive ​

The Accurate Response ​

The Platform's Filters ​

The Rally of the Actual Users ​

The Doctrine of the Review War ​

The Review War in the Modding Community ​

The Workshop Listing ​

The Companion Tool ​

The Full Game Page ​

The Full Game Page ​

The Server's Own Score ​

The Review War and the War's Sequence ​

The Fork and the Wave ​

The Wave and the Statement ​

The Wave and the Moderation War ​

Documented Example: The Wave That Outran Its Own Schedule ​

Documented Example: The Rally That Was Not a Counter-Bomb ​

Documented Example: The Wave That Was Priced Into History ​

The Yamak Institute Cohort Data ​

Concentration and the Review Wave (2019) ​

The Cohort of the Traced Wave ​

The Cohort of the Durable Suppression ​

The Cohort of the Defender's Response ​

The Five-Stage Protocol for the Review War ​

Stage 1: Hold the Archive ​

Stage 2: Assess the Wave ​

Stage 3: Respond Once, From the Record ​

Stage 4: Work the Platform ​

Stage 5: Rally the Actual Users ​

Objections ​

Objection 1: "The review bomb works; we have seen scores fall." ​

Objection 2: "The wave is anonymous; no one can trace it." ​

Objection 3: "The platform will not help us." ​

Objection 4: "We need to counter-review; the wave is winning the score." ​

Objection 5: "The wave is unfair, and we need to say so loudly." ​

Objection 6: "We are a small team; we cannot hold an archive against a large wave." ​

Objection 7: "The score is just a number; the wave does not hurt the project." ​

Objection 8: "We have no genuine users to rally." ​

Objection 9: "Attacking back is how the war is fought." ​

Objection 10: "The wave is gone; we can ignore it." ​

Objection 11: "We cannot prove the wave is coordinated." ​

Objection 12: "This is a games wiki, not a military; the doctrine does not apply." ​

Objection 13: "Our project is new; we have no archive to hold." ​

Objection 14: "The wave is aimed at a rival, not at us; we can stay out of it." ​

FAQ ​

The Review War

Prerequisites

What You Will Learn

The Massed Attack

The Simultaneity

The Onset and the Decision Point

The Concentration Table

The Anatomy of a Review Wave

The Assembly

The Template

The Wave's Message

The Release

The Defense of the Wave

The Exhaustion

The Attack Surface

The Score as the Target

The Score's Economy

The Score History as Battle Record

The Attack's Vulnerabilities

The Traces of Coordination

The Platform's Counter-Fire

The Converted Account

The Decision Point

The Response That Decides

The Counter-Fire That Decides

The Judgment That Decides

The Cost Structure

The Permanent Capital

The Temporary Effect

The Two Ledgers

The Attacker's Calculation

The Question of Gain

The Question of Cost

The Question of Terrain

The Defense of the Review War

The Archive

The Accurate Response

The Platform's Filters

The Rally of the Actual Users

The Doctrine of the Review War

The Review War in the Modding Community

The Workshop Listing

The Companion Tool

The Full Game Page

The Full Game Page

The Server's Own Score

The Review War and the War's Sequence

The Fork and the Wave

The Wave and the Statement

The Wave and the Moderation War

Documented Example: The Wave That Outran Its Own Schedule

Documented Example: The Rally That Was Not a Counter-Bomb

Documented Example: The Wave That Was Priced Into History

The Yamak Institute Cohort Data

Concentration and the Review Wave (2019)

The Cohort of the Traced Wave

The Cohort of the Durable Suppression

The Cohort of the Defender's Response

The Five-Stage Protocol for the Review War

Stage 1: Hold the Archive

Stage 2: Assess the Wave

Stage 3: Respond Once, From the Record

Stage 4: Work the Platform

Stage 5: Rally the Actual Users

Objections

Objection 1: "The review bomb works; we have seen scores fall."

Objection 2: "The wave is anonymous; no one can trace it."

Objection 3: "The platform will not help us."

Objection 4: "We need to counter-review; the wave is winning the score."

Objection 5: "The wave is unfair, and we need to say so loudly."

Objection 6: "We are a small team; we cannot hold an archive against a large wave."

Objection 7: "The score is just a number; the wave does not hurt the project."

Objection 8: "We have no genuine users to rally."

Objection 9: "Attacking back is how the war is fought."

Objection 10: "The wave is gone; we can ignore it."

Objection 11: "We cannot prove the wave is coordinated."

Objection 12: "This is a games wiki, not a military; the doctrine does not apply."

Objection 13: "Our project is new; we have no archive to hold."

Objection 14: "The wave is aimed at a rival, not at us; we can stay out of it."

FAQ