Example 11: The Failed Raid
The raid is the drama war's sudden strike: the coordinated mass-join, the mass-report campaign, the synchronized review flood, the overnight forum assault. It is the weapon of choice for the commander who believes the enemy is unprepared. And it is the weapon most likely to be destroyed by its own assumption. Example DW-0707, known as The Failed Raid, is the Yamak Institute's canonical study of the raid that was met by a prepared enemy, and its central lesson is the one the doctrine states with the most brutal economy: the art of war teaches us to rely on our own readiness to receive the enemy, not on the enemy's failure to come.
The engagement concerned a large server community, identified in the cohort files as the Bastion server, and a coalition of three rival communities that had grown tired of losing players to it. The coalition's plan was a coordinated raid: a timed mass-join on the Bastion Discord, a synchronized flood of spam, and a mass-report campaign designed to have the server banned. The plan's premise was that the Bastion's moderation would be caught asleep. The premise was false, and the premise was the raid's entire strategy.
The raid is the drama weapon with the most lopsided record in the Institute's cohort: it wins against the unprepared and loses against the prepared, and the difference is entirely in the target, not in the weapon. The Failed Raid is the cohort's demonstration of the second outcome, and its lesson is that the raid's own speed is the raider's liability, because a fast attack leaves a complete record of its own movement.
Prerequisites
- The doctrine of On the Defensive, because the raid is the offensive that meets the prepared defense
- The chapter on Tactical Dispositions, which teaches the making of invulnerability before the attack
- The art of The Art of the Counter, because the counter-raid and the exhibit are the defense's weapons
- The discipline of On Deception, because the raid is launched on a false reading of the enemy's condition
- Experience, direct or observed, with at least one server that was raided, or one community that raided another
The article is a worked case study, and its full weight is carried by the preceding doctrine. The raid is the sudden strike that the defensive chapters prepare against, and the counter is the response those chapters teach. A reader who has studied the four works above will recognize the Bastion's protocol as the disposition chapter's doctrine executed in a Discord server, and the exhibit as the counter chapter's form applied to the raid's own evidence. A reader who has not will still follow the raid's shape, but the references will land without their full charge.
What You Will Learn
- Why the raid's premise - the enemy's unpreparedness - is the raid's single point of failure
- How a prepared defense absorbs a raid and converts it into evidence
- The raid survivability index and the doctrine of the documented protocol
- Why the failed raid supplies its own evidence, and how the exhibit weaponizes it
- The doctrine of restraint: why the prepared enemy does not pursue the defeated raider
- The five-stage protocol for preparing a server to receive a raid
- The answers to the objections sceptical server owners raise against the doctrine
- The reference apparatus: the cohort studies, the raid-readiness audit, and the raid-preparation checklist
- How the raid changes register across the review flood, the forum assault, and the report campaign
The Raider's Assumption
The Art of War teaches that the good fighter makes himself invulnerable to attack before seeking to defeat the enemy. The raiding coalition had made itself vulnerable in exactly the way the doctrine forbids: it had assumed that the enemy's weakness was the enemy's permanent condition. The coalition had watched the Bastion's public channels, seen a small moderation team, and concluded that the server could not respond to a sudden assault. What the coalition had not seen was the Bastion's private readiness, and the Art of War is explicit that what the enemy does not see is what decides the battle.
Attack him where he is unprepared, appear where you are not expected.
- Sun Tzu, The Art of War, ch. 1
Documented example
Example DW-0204, "The Empty Moderation Queue." A server owner, warned of a planned raid by a trusted member, spent a week quietly training twelve volunteer moderators and preparing a ban-macro protocol. The raid arrived, was repelled in eleven minutes, and the raiders were banned and reported within the hour. The raiders had attacked a server whose moderation queue looked empty because the moderation was prepared, not because it was absent. The cohort records the rule: the enemy who appears to be asleep is either asleep or prepared, and the raid that cannot distinguish the two is the raid that has already bet the war on a coin flip.
The doctrine warns the raider against the bait. The Bastion's public channels looked defenseless, and the Art of War names that appearance: if his place of encampment is easy of access, he is tendering a bait. The coalition mistook the bait for the weakness. A position that looks undefended and is worth attacking is a position that has been arranged to look undefended.
If his place of encampment is easy of access, he is tendering a bait.
- Sun Tzu, The Art of War, ch. 9
The Assumption as the Whole Strategy
The coalition's plan contained many moving parts - the timed mass-join, the spam flood, the report campaign - and one assumption. The assumption was that the Bastion could not respond. Everything else in the plan leaned on that single point: the mass-join needed time to reach the general channels, the spam needed time to accumulate, the reports needed time to land with Discord Trust & Safety. Every step of the plan required the defense to be slow, and the plan had no provision for a defense that was not slow. The doctrine records the raid as the drama war's purest example of the single-point strategy: the entire operation rests on one fact about the enemy, and the fact is the only thing the raider did not verify.
The verification was possible. The coalition could have probed the Bastion's response time with a test join, could have watched for the two-word signal, could have checked the server's moderation history for a prior raid. None of the verification was done, because the raid's psychology is the psychology of the sudden strike: the raider moves fast precisely so that the enemy has no time to prepare, and the raider who takes time to verify is a raider who has lost the raid's advantage. The doctrine's answer is that the raid's speed is the enemy's information, not the raider's: the raid that arrives without preparation gives the defense the evidence the defense needs, and the raid that arrives after preparation has already been prepared against.
The Bait the Coalition Refused to See
The Bastion's public channels were a deliberate surface. The server's leadership knew that raids were planned against it, and it maintained the appearance of a small, sleepy moderation team as a standing invitation for the raid to come and be recorded. The appearance was not deception in the ordinary sense; it was the doctrine's own formation. A position that looks undefended and is worth attacking is a position arranged to look undefended, and the arrangement is the bait. The coalition, reading the appearance as the reality, took the bait with the full weight of its three communities.
The doctrine's warning to the raider is the warning the coalition refused: the enemy who looks easy is either easy or arranged, and the arranged enemy is the more likely case, because an undefended position that matters does not stay undefended. The Bastion's moderation looked small because the Bastion's preparation was private, and the privacy was the point. The raid that attacked the appearance attacked the formation the Bastion had designed for it, and the formation was the trap the raid walked into.
The Raider's Confidence and the Enemy's Record
The coalition's confidence had a second source, and it is the one the doctrine records as the raider's most common self-deception: the reading of the enemy's public record as the enemy's complete record. The coalition had seen the Bastion's public moderation actions, its announcements, its member counts, and it had concluded that the server's capacity was what the public record showed. What the public record did not show was the verification wall, the staged moderation hierarchy, and the trained volunteer team. The coalition had mistaken the enemy's public surface for the enemy's full disposition, and the doctrine's chapter on the use of spies warns that knowledge of the enemy comes from more than the enemy's public face.
The raider's confidence is also the raider's exposure. A raid is a commitment of accounts, community goodwill, and reputation, and the commitment is made on the basis of the confidence. The coalition committed three communities to an operation built on a reading of the Bastion's public channels, and the reading was wrong in the only dimension that mattered. The doctrine's counsel to the would-be raider is the doctrine's counsel to every commander: rely on your own readiness, not on the enemy's failure to come, and the raid that relies on the enemy's failure is the raid that has bet the war on the enemy's negligence.
The Raid as a Coin Flip
The doctrine's image for the raid against an unverified enemy is the coin flip, and the image is the cohort's arithmetic made visual:
The coin flip is the raid that does not verify. The unprepared target makes the raid a victory; the arranged target makes it a confession. The doctrine's counsel to the raider is not to refuse the raid but to refuse the flip: the raid that verifies the enemy's condition attacks only the unprepared, and the raid that verifies the enemy's condition is no longer betting the war on a coin. The coalition flipped the coin with three communities behind it, and the coin landed on the arranged enemy.
The Prepared Enemy
The Bastion had been preparing for exactly this raid for six months. Its preparation was not a response to the coalition; it was a standing condition. The server had a documented raid protocol: a verification wall for new joins, a staged moderation hierarchy that could act without waiting for the owner, a ban-and-report script that could process a hundred accounts in minutes, and a culture in which every regular member knew the two-word signal that meant "raid in progress." When the raid began, the protocol began with it.
He wins his battles by making no mistakes.
- Sun Tzu, The Art of War, ch. 4
The raid's progress is documented minute by minute in the cohort files. In minute one, the verification wall stopped the first wave of mass-joins before they could reach the general channels. In minute three, the first synchronized spam posts were deleted and their authors banned. In minute seven, the mass-report campaign was detected by the server's own reporting to Discord Trust & Safety, which had received the same raid reports from the raiders and the counter-reports from the Bastion, and which favors the party with the more established record. By minute eleven, the raid was over, and the coalition had lost every account it had committed to the attack.
Did you know?
The Yamak Institute's raid doctrine maintains the "raid survivability index": the expected damage of a raid divided by the preparation of the target. Prepared servers, defined as those with a documented protocol, a trained moderation tier, and a verification wall, absorb 83% of raiding damage in the cohort. Unprepared servers absorb 17%. The distinction is not in the size of the moderation team but in the existence of the protocol. A raid that meets a prepared protocol is not a raid; it is a donation of evidence. The coalition donated evidence.
The Standing Preparation
The Bastion's preparation was standing, not reactive, and the distinction is the heart of the doctrine. A reactive preparation is a preparation that begins when the threat is known, and a threat that is known to the defense is a threat the defense has time to meet. The Bastion's preparation had been completed months before the coalition even formed, which meant that the server's readiness did not depend on the warning, the timing, or the coalition's secrecy. The raid could not catch the Bastion unprepared, because the Bastion's preparation did not begin when the raid was launched; it had been complete while the raid was still a rumor.
The standing preparation is also the answer to the raider's premise. The coalition had assumed that a small moderation team could not respond to a sudden assault, and the assumption was wrong not because the Bastion's team was large but because the team had a protocol. The doctrine's claim is precise: the distinction between the prepared and the unprepared server is not in the size of the moderation team but in the existence of the protocol. A team of three with a script and a hierarchy responds faster than a team of twenty without either. The coalition had counted the Bastion's team and never counted the Bastion's script.
The Protocol in the Field
The raid's eleven-minute collapse is a study in the prepared protocol operating under pressure. The verification wall stopped the mass-join at the boundary, which is the protocol's first principle: the attack is stopped before it reaches the community. The staged moderation hierarchy allowed bans to be issued by the tier on duty, which is the protocol's second principle: the defense does not wait for the owner. The ban-and-report script processed the raiding accounts, which is the protocol's third principle: the counter-evidence is collected as the attack happens. And the two-word signal mobilized the regular members, which is the protocol's fourth principle: the community is part of the defense, not the target of it.
The protocol's four principles are the doctrine's chapter on tactical dispositions executed in a Discord server. The defense is made invulnerable before the attack, the defense acts without waiting for command, the defense records the enemy's movement as it happens, and the defense mobilizes the community that the raid meant to disrupt. The Bastion did not improvise its response; it ran a script that had been written, tested, and drilled six months earlier. The eleven minutes of the raid were the eleven minutes in which the preparation the coalition had never seen did the work the coalition had assumed would not exist.
The Documentation of the Defense
The Bastion's preparation produced a second asset, and it is the asset the counter doctrine values most: the documentation. The verification wall logged every join attempt with its timestamp and its account. The moderation hierarchy logged every ban with its reason and its evidence. The script logged every report and counter-report. When the raid ended, the Bastion did not have to reconstruct what had happened; it had a minute-by-minute record, produced by the defense itself, of everything the coalition had done. The record was the exhibit the counter would publish, and the record existed because the preparation had been documented from the start.
The doctrine's counsel to the server owner is that preparation must be documented to be preparation. A protocol that exists only in the owner's head is a protocol that cannot be drilled, tested, or produced as evidence. The Bastion's protocol existed as a document, which meant it could be rehearsed by new moderators, reviewed for weaknesses, and presented to Discord Trust & Safety as the server's standing practice. The documentation was the difference between a defense that repelled the raid and a counter that crushed the raider, and the difference was made before the raid began.
The Raid on Other Surfaces
The raid is not only a Discord formation, and the doctrine's readiness applies wherever the sudden strike can land. The Unturned world hosts the raid on several surfaces, and each surface has its own defense and its own exhibit. The Bastion's protocol defended a Discord server; the same discipline defends a Workshop page, a forum, and a community's review history.
| Surface | The raid's form | The defense | The exhibit |
|---|---|---|---|
| Discord server | Mass-join, spam flood, report campaign | Verification wall, hierarchy, drill | The join logs and timestamps |
| Steam Workshop | The coordinated review flood | Archive every review, note the timing | The timeline of the reviews' arrival |
| Forum / announcement feed | The overnight comment assault | Moderation queue, approval gate | The deleted posts and their patterns |
| Community reputation | The mass-report campaign | The established record, the counter-report | The report history and the outcome |
The Review Flood
The Workshop review flood is the raid's form on the surface where a mod's reputation is kept. A rival coordinates a timed batch of negative reviews, each written to look independent, each timed to land together. The defense is the archive: every review is recorded with its timestamp and its account history, and the timing is compared against the rival's public announcements. The exhibit is the timeline, showing that the reviews began three minutes after the rival's announcement and stopped the same day. The exhibit does not need to name the rival; the timeline names the coordination. The review flood's deniability is the same as the Discord raid's, and it is broken the same way: by the timestamps.
Documented example
Example DW-0561, "The Sunday Flood." A mod team watched seventeen negative reviews land on its Workshop page within a single hour on a Sunday. The team did not respond to the reviews. It archived them, compared their timestamps against a rival's announcement the day before, and published a single dry timeline titled "Seventeen Reviews in One Hour." The reviews were removed by Steam, and the rival's community abandoned the campaign rather than be associated with the flood. The mod team's restraint - no accusation, no response to the reviews themselves - was the discipline that made the timeline credible. The flood, like the Discord raid, supplied its own evidence, and the evidence was the counter.
The Forum Assault
The forum assault is the raid's form on the surface where a community's announcements live. A coordinated group posts a flood of hostile replies to an announcement, drowning the record and manufacturing the appearance of a community uprising. The defense is the moderation queue and the approval gate: the posts are held, the pattern is logged, and the raid is stopped before it becomes the thread. The exhibit is the held posts themselves, showing the identical language and the synchronized timing. The forum assault's purpose is to make the community's own surface look hostile, and the defense's purpose is to stop the hostility at the boundary, exactly as the verification wall stops the mass-join.
The Report Campaign
The mass-report campaign is the raid's form on the surface of platform trust and safety. The raiders coordinate reports against the target - a server, a mod page, an account - hoping that the volume of reports will trigger an automated or human action. The defense is the established record: the target's clean history, its documentation, its counter-reports. The exhibit is the report history, showing the campaign's coordination. The Bastion's defense against the report campaign was its documentation, and the documentation was the record that the platform favored. The report campaign's failure is the same as every raid's: it supplies its own evidence, and the evidence is the target's counter.
Documented example
Example DW-0442, "The Automated Flood." A server was reported to the platform by a coordinated campaign of accounts that had never been in the server, each filing the same complaint. The server's owner did not respond to the reports individually. He filed a single counter-report attaching his full moderation log, his member records, and a note that the reporting accounts had no server history. The platform reviewed the counter-report, dismissed the campaign, and the flood ended. The cohort codes the case as the report campaign's standard counter: the target cannot out-report the flood, but the target can out-document it. The established record is the verification wall of the report surface, and the counter-report is the exhibit.
The Counter That Crushed the Raider
The Art of War teaches that the general who is prepared for the enemy's attack is the general who can turn the attack into his own victory. The Bastion did not merely repel the raid. It captured it. Within an hour of the raid's failure, the server had compiled the evidence: the mass-join logs, the synchronized timestamps, the identical spam messages, and the report history of every raiding account. The evidence was published as a single, dry document, and the document converted the raid from an attack into an exhibit.
Do not swallow bait offered by the enemy.
- Sun Tzu, The Art of War, ch. 7
Documented example
Example DW-0430, "The Exhibit." A map author's community was raided by a rival's coordinated review flood. The author's moderation team archived every negative review with its timestamp and its account history, then published the archive alongside a timeline showing that the reviews had begun three minutes after the rival's announcement. The archive was the counter. The rival's reviews were removed by Steam, and the rival's reputation was permanently tied to the raid. The Art of War teaches that the counter to the enemy's attack is to make the enemy's attack the enemy's undoing. The archive does exactly that: it does not defend the position, it makes the attacker's own evidence the weapon against him.
The coalition's collapse followed the publication of the exhibit. Three of its member communities had joined the raid on the promise that it would be anonymous and deniable. The exhibit broke the deniability, and the three communities abandoned the coalition within a week, each publishing a statement that it had "not been aware of the raid's full scope." The statements were the cohort's final confirmation that the raid had been the coalition's single point of failure: the moment the raid failed, the coalition had nothing left.
Documented example
Example DW-0335, "The Prepared Counter-raid." A server owner, knowing a raid was coming, prepared a counter in advance: a list of the raiding communities' own channels and a file of their prior moderation failures. When the raid struck, the owner did not fire the counter. He published the raid exhibit, then quietly noted that he had "extensive records of the communities involved." The threat of the counter, never fired, was enough. The raiding coalition disengaged and never returned. The Art of War teaches that the general who holds a prepared counter and does not use it has won twice: once in readiness, once in restraint.
The Exhibit as the Weapon
The exhibit is the raid's mirror: the same evidence that the raider thought would destroy the enemy, arranged to destroy the raider. The raid's own documents - the joins, the spam, the reports - become the proof that the raid was coordinated, that it was planned, and that it came from the raiding communities. The Bastion's exhibit was dry, numbered, and complete, and its dryness was its power. A document that makes no accusation cannot be accused of exaggeration, and a document that simply shows the enemy's own movement does not need an argument. The exhibit's authority came from its restraint: the reader followed the timestamps and drew the conclusion that the coalition was a coordinated attack.
The exhibit also answered the raid's one defense. The raider's hope, and the promise the coalition had made to its members, was deniability - the raid would look like a spontaneous burst of community anger. The exhibit destroyed the deniability by showing the coordination: the joins at the same second, the identical spam messages, the synchronized reports. The coordinated raid cannot look spontaneous once its timing is laid out, and the laying out is the exhibit's work. The coalition's communities had joined on the promise of anonymity, and the exhibit was the document that the anonymity had never existed.
The Deniability Broken
The coalition's collapse was the exhibit's aftermath, and the collapse followed the exact shape the doctrine predicts for the raid that fails. Three communities had committed accounts and goodwill to the operation on the promise of deniability, and the exhibit broke the promise. Each community then had a choice: disavow the raid or be associated with it, and the disavowal was the only survivable option. The three disavowals were published within a week, each claiming ignorance of the "raid's full scope," and the claims were read by the community that had seen the exhibit as the admissions they were. The coalition, which had been three communities acting as one, became three communities denying the same action.
The collapse is the cohort's proof that the raid is a single point of failure in the raider's own structure. The coalition had no fallback: its entire position was the raid, and the raid's failure left it with nothing to hold. The doctrine's counsel to the would-be raider is that the raid must not be the whole of the strategy, because a strategy that is wholly an attack on the enemy's unpreparedness is a strategy that dies the moment the enemy is prepared. The coalition's three communities had spent six months building a war on a single assumption, and the assumption's failure dissolved the war in a week.
The Counter Held in Reserve
The Bastion's counter included a weapon it never fired, and the unfired weapon was the more powerful of the two. The server had compiled, in the months of its preparation, records of the raiding communities' own activity: their channels, their members, their prior moderation actions. The records were held in reserve, and the reserve was hinted at in the exhibit's closing line. The hint was enough. The coalition's communities, already disavowing the raid, had to consider whether the enemy held evidence of their own prior conduct, and the consideration accelerated the disavowals.
The doctrine records the held counter as the rarest and strongest formation in the raid's aftermath. A counter that is fired completes the war and invites the reprisal; a counter that is held announces the war is over and leaves the enemy uncertain of the terms. The Bastion did not need to fire the counter because the exhibit had already broken the coalition, and firing it would have reopened the war that the readiness had closed. The doctrine's chapter on the counter teaches that the counter's power is in the holding: the general who holds a prepared counter and does not use it has won twice, once in readiness and once in restraint.
The Exhibit's Failure Modes
The exhibit is a powerful weapon, and like every weapon it has failure modes. The first is the emotional exhibit: the document that accuses, names, and celebrates, which converts the counter into an attack and invites the reprisal. The second is the partial exhibit: the document that shows the raid's coordination but omits the accounts, the timestamps, or the counter-reports, which leaves the raider's deniability intact. The third is the late exhibit: the document published weeks after the raid, when the community's attention has moved on and the reconstruction reads as a grudge. Each failure mode spends the credibility the exhibit was built to earn, and each is avoided by the doctrine's disciplines: the dry register, the complete record, and the prompt publication.
Documented example
Example DW-0788, "The Angry Exhibit." A server that repelled a raid published a counter that opened with an insult, named the raiding communities by name, and demanded apologies. The exhibit's evidence was complete, and its register was ruined: the community read the document as a taunt, the raiding communities rallied around the insult, and the war that the repelling should have closed continued for another month. The cohort codes the case as the exhibit's failed register. The same evidence, published dryly, would have broken the coalition as the Bastion's exhibit broke its own. The exhibit is a document, and the document's credibility is the discipline of its register.
The exhibit's failure modes are also the doctrine's answer to the objection that the exhibit is aggressive. The exhibit is aggressive only when it is written aggressively; the dry exhibit is the opposite of aggression. The Bastion's exhibit made no accusation, expressed no outrage, and drew no conclusion. It presented the raid's own documents, and the conclusion the community drew was the conclusion the documents forced. The doctrine's counsel is that the exhibit's power is precisely in its refusal to argue: the evidence that makes no case cannot be accused of making a false one, and the counter that does not shout is the counter that is believed.
The Doctrine of Readiness
The core of the doctrine is the chapter on variation in tactics, which teaches that the skilled commander relies not on the enemy's absence but on his own presence. The failed raid demonstrates the law from the enemy's side: the raider who relies on the enemy's unpreparedness has put his entire strategy in the hands of the enemy's failure. The Bastion's victory was complete before the raid began, because its readiness did not depend on the coalition's behavior. The coalition's defeat was complete before the raid began, because its plan depended on the Bastion's negligence.
In raiding and plundering be like fire, is immovability like a mountain.
- Sun Tzu, The Art of War, ch. 7
The raider's art is the art of the sudden strike, and the doctrine honors it: let your rapidity be that of the wind, in raiding and plundering be like fire. But the doctrine is equally explicit about the limits of the raider's art. A fire that meets wet ground burns out. A raid that meets a prepared protocol fails in minutes, and the raider, unlike the fire, leaves a record of his own attempt. The raid is the only weapon in the drama arsenal that supplies its own evidence to the enemy, and it supplies it the moment it fails.
Let your rapidity be that of the wind, your compactness that of the forest.
- Sun Tzu, The Art of War, ch. 7
Critical warning
Never launch a raid unless you are prepared for the raid to fail, because the failed raid is the most expensive defeat available in drama warfare. The raider who fails has done four things at once: he has alerted the enemy, he has donated his evidence, he has unified the enemy's community against him, and he has spent his own community's goodwill on an operation that delivered nothing. The Yamak cohort records that the failed raid is followed by the dissolution of the raiding coalition in 76% of cases. The raid is a single bet on a single assumption, and a single assumption is not a strategy.
The failed raid produced one final lesson, which is the bridge to the next example in this corpus. The Bastion, having repelled the raid, did not pursue the coalition. It did not launch a counter-raid, publish a victory thread, or demand apologies. It repaired its channels, thanked its members, and returned to running its server. The Art of War teaches that the victorious commander does not seek glory in victory, and the Bastion understood that the raid's defeat was complete the moment it was over. Pursuing the defeated enemy would have reopened the war that the readiness had closed. The Bastion's restraint, the cohort records, was as much a tactical decision as its readiness had been.
Documented example
Example DW-0689, "The Victory Lap." A server that repelled a raid published, three hours after the repelling, a celebration thread naming the raiding communities, quoting their messages, and promising that "we will remember this." The thread was the reply the raiders had not earned. The war, which the repelling had closed, reopened around the celebration: the raiding communities rallied around the insult, the server's own members tired of the gloating, and the engagement that had been over in eleven minutes ran for another month. The cohort codes the case as the doctrine's restraint refused. The victory lap is the exhibit's mirror image: the exhibit closes the war with dry evidence, and the victory lap reopens it with emotion. The commander who needs to celebrate the victory has not understood that the victory was complete when the enemy disengaged.
The Victory Complete Before the Battle
The doctrine of readiness inverts the raider's timeline. The Bastion's victory was complete before the raid began, because the conditions of the victory - the protocol, the hierarchy, the script, the trained members - were all in place before the coalition moved. The raid did not create the conditions of the Bastion's victory; it merely confirmed them. The coalition's defeat was equally complete before the raid began, because the plan depended on a condition - the Bastion's negligence - that did not exist and never would. The battle, as the doctrine's first chapter insists, is decided before it is fought, and the raid was decided the moment the coalition chose to attack the prepared.
The lesson is the raider's hardest one. The raid's whole appeal is the belief that the sudden strike wins by timing - that the enemy, caught unprepared, cannot recover. The doctrine's answer is that the enemy's preparation is not a function of the raid's timing; it is a standing condition that the raid cannot outrun. The prepared enemy is prepared before the raid is conceived, and the raid arrives to find the defense already in place. The raider who wants to win by timing must first verify that the enemy's preparation is genuinely absent, and the verification is the one step the raid's psychology forbids.
The Fire That Meets Wet Ground
The doctrine's image for the failed raid is the fire that meets wet ground. The raider's art is the art of fire: rapid, consuming, appearing where it is not expected. But the doctrine's chapter on the attack by fire is equally explicit about fire's limits: fire is extinguished by the prepared ground, and the raider who carries fire to wet ground is not consuming the enemy; the raider is extinguishing himself. The raid that meets a prepared protocol is the fire meeting wet ground, and the difference between the two outcomes is not in the fire, which is the same, but in the ground.
The fire metaphor also explains the raid's one unique liability. The raider, unlike the fire, leaves a record. The fire leaves ash; the raider leaves joins, timestamps, spam, and reports, and the record is the exhibit the defense publishes. The raid is the only weapon in the drama arsenal that supplies its own evidence to the enemy, and it supplies it the moment it fails. Every other weapon's failure leaves a question; the raid's failure leaves a confession. The doctrine's counsel to the would-be raider is to weigh this liability before committing: the raid is the weapon that converts its own defeat into the enemy's exhibit.
The Four Costs of the Failed Raid
The doctrine's critical warning names the four costs of the failed raid, and each cost deserves its own accounting. The first cost is the alert: the enemy that was unprepared is now prepared, and the raider's community is known. The second cost is the evidence: the raid's own documents become the enemy's exhibit. The third cost is the unity: the raid mobilizes the enemy's community against the raider, converting a passive target into an active opposition. The fourth cost is the goodwill: the raider's own community spent its enthusiasm on an operation that delivered nothing, and the enthusiasm is not renewable.
The four costs are the reason the failed raid is the most expensive defeat available in drama warfare. A statement war's defeat can be contained by a closing statement; a reputation attack's defeat can be met with the exhibit's discipline. The failed raid spends all four at once, and the cohort records the aftermath: the raiding coalition dissolves in 76% of cases. The doctrine's arithmetic is the raider's arithmetic: the raid is a single bet on a single assumption, and a single assumption is not a strategy. The raider who bets the community's goodwill on the enemy's negligence has bet it on a coin flip, and the coin flips against the raider whenever the enemy is prepared.
The Raid Compared to the Other Weapons
The raid's unique costs are clearest when it is set beside the drama war's other weapons, and the comparison explains why the doctrine treats the failed raid as the most expensive defeat available:
| Weapon | What it spends on failure | What it leaves behind | The defender's counter |
|---|---|---|---|
| The statement | The attacker's time, the defender's attention | Positions that can be closed | The decisive-day close |
| The smear | The attacker's credibility | A claim that can be rebutted | The exhibit and the rebuttal |
| The leak | The attacker's source | A document that can be verified | The counter-analysis |
| The raid | The attacker's accounts, goodwill, and deniability | The attacker's own complete record | The exhibit, published dryly |
The comparison is the doctrine's field table. The statement's failure leaves positions the defender can close; the raid's failure leaves the attacker's own complete record, produced by the raid itself, ready to be published as the exhibit. No other weapon in the drama arsenal converts its own defeat into the enemy's counter, and the conversion is the raid's unique liability. The raider who weighs the weapons before choosing has chosen the one weapon whose failure is a confession, and the confession is the exhibit.
The Raid and the Review Bomb
The raid's closest relative is the review bomb, and the comparison sharpens both doctrines. The review bomb is the raid's form on the review surface: the coordinated negative reviews against a mod page, timed to land together. The review bomb shares the raid's premise - the target's inability to respond - and shares its evidence: the reviews themselves, timestamped and coordinated, are the bomb's own exhibit. The doctrine of readiness defends both with the same formation: the archive, the timeline, the dry exhibit, the restraint. The difference is the surface, and the surface changes the cost: the review bomb's damage lands on a page that cannot scroll, while the Discord raid's damage can be repaired and the channels closed. The doctrine's counsel is the same for both, and the review bomb's permanent surface makes the exhibit more important, not less.
The Restraint That Closed the War
The Bastion's final move was not a move. Having repelled the raid and published the exhibit, the server did nothing further: no counter-raid, no victory thread, no demands for apology. The restraint was deliberate, and the doctrine records it as the tactical decision it was. The raid's defeat was complete the moment it was over; the exhibit had broken the coalition and the held counter had secured its disengagement. Any further action would have reopened the war, and a reopened war is a war the readiness had already won. The doctrine's counsel is that the victory is complete when the enemy disengages, and the commander who needs to announce the victory is a commander who doubts it.
The restraint also preserved the Bastion's standing. The community that watched the Bastion repel a raid and then return to running its server saw a leadership that treated the raid as a disruption, not as a war. The coalition's communities, by contrast, had spent a week in disavowal. The contrast was the cohort's final observation: the prepared enemy won the raid and did not need to say so, and the unprepared raiders lost the raid and could not stop saying so. The doctrine of readiness ends where it begins: the skilled commander relies on his own presence, and the commander who is present does not need the enemy to confirm it.
The Raid That Won Against the Unprepared
The doctrine's honesty requires the case in the other direction, and the cohort records it in full. A raid against an unprepared server does win, and it wins in the way the raider's art promises: the mass-join reaches the general channels, the spam flood takes hold, and the target's slow response gives the raid time to damage the community. Example DW-0311, "The Unprepared Target," codes a server with no wall, no hierarchy, and no drill, which absorbed a coordinated raid for a full day. The raid's success, however, was the doctrine's point in reverse: the unprepared server's losses were the exact losses the preparation prevents, and the raider who won against the unprepared won against a target that had refused the doctrine. The doctrine does not promise the raid can never win. It promises that the raid wins only where the defense refused to exist, and that the target's refusal is the raider's only legitimate field.
The Readiness That Costs Nothing to Hold
The doctrine's final arithmetic is the cost of readiness. The Bastion's preparation cost six months of occasional meetings, a document, a script, and a few drills - a cost measured in hours, not in anything the server needed. The raid's repelling saved the server the disruption that the unprepared absorb, and the exhibit's publication converted the attack into the server's standing record. The readiness was the cheapest weapon in the raid's aftermath, and it was the only one that worked before the raid began. The doctrine's counsel to the server owner is the article's whole economics: the preparation that costs nothing to hold is the preparation that is never regretted, because the raid that never comes has still been priced, and the raid that does come has already been met.
The Raid in Different Communities
The raid doctrine is universal in its principles and particular in its surface, and the commander should know how the same readiness changes register between the communities of the Unturned world. A server, a mod team, a faction, and a community project each receive the raid differently and defend it differently.
| Community | The raid's typical form | The defense | The exhibit |
|---|---|---|---|
| A public server | Mass-join, spam flood, report campaign | Wall, hierarchy, drill | The join logs and timestamps |
| A mod team | The review flood, the provenance attack | The archived reviews, the clean record | The timeline of the flood |
| A faction | The in-character mass infiltration | The out-of-character check, the gate | The infiltrators' patterns |
| A community project | The drive-by complaint storm | The moderation queue, the approval gate | The held posts and their pattern |
The Server's Defense
The server's defense is the article's central case, because the server is the raid's most common target and the surface where the raid's costs are largest. The server's members are the audience the raid means to disrupt, and the server's preparation - the wall, the hierarchy, the drill - is the defense that keeps the raid from reaching that audience. The server's exhibit is the raid's own logs, and the exhibit's publication is the counter that the server publishes once and then holds. The server's discipline is the article's whole doctrine: repel, exhibit, and return to running the server.
The Mod Team's Defense
The mod team's raid is the review flood and the provenance attack, and the team's defense is the record. The team that has archived its reviews, documented its credits, and kept its changelog clean has built the verification wall that the flood's evidence will be measured against. The team's exhibit is the timeline showing the reviews' coordination, and the team's restraint is the refusal to answer the reviews individually. The mod team's version of the Bastion is the team that lets the flood be the flood and publishes the timeline that the flood cannot answer.
The Faction's Defense
The faction's raid arrives in the RP register: the coordinated mass infiltration, the in-character disruption, the engineered coup of the faction's own story. The faction's defense is the out-of-character check - the verification that a joining member is a member, not an infiltrator - and the gate that the check provides. The faction's exhibit is the pattern of the infiltrators, published in the register that shows the coordination without breaking the fiction. The faction's discipline is the same as the server's, and the register is the only difference.
The Community Project's Defense
The community project's raid is the drive-by complaint storm: the coordinated flood of criticism designed to make the project's leadership look overwhelmed. The project's defense is the moderation queue and the approval gate, which hold the storm before it becomes the project's public face. The project's exhibit is the held posts and their pattern, published to show that the storm was coordinated. The project's restraint is the refusal to answer the storm point by point, and the project's return to its work is the exhibit that the storm did not win.
The Yamak Institute Cohort Data
The raid doctrine rests on the Yamak Institute's cohort research into coordinated community attacks, collected from Unturned community surfaces since 2020. The research codes each raid for its target's preparation, its own coordination, and its aftermath, and the coded corpus is the empirical spine of everything this article has claimed. The primary records are presented below in the register in which the Institute publishes them.
The Raid Survivability Index Cohort (2022)
The flagship dataset of the chapter, the Raid Survivability Index, codes raided servers against a three-part preparation standard: a documented protocol, a trained moderation tier, and a verification wall. The cohort found that prepared servers absorb 83% of raiding damage, measured in account losses, channel disruption, and report outcomes, while unprepared servers absorb 17%. The index's most instructive finding is that the preparation standard is binary in its effect: servers with all three components absorbed the raid in minutes, and servers with any component missing absorbed it for days. The index is the empirical form of the doctrine's central claim: the difference is the protocol, not the team's size.
The Failed Raid Aftermath Cohort (2023)
The Aftermath Cohort coded the fate of the raider following a failed raid, and its findings support the doctrine's critical warning. The coalition that launched the raid dissolved in 76% of documented cases, and the dissolution followed the same shape in each: the exhibit broke the deniability, the member communities disavowed the raid, and the disavowals were read as admissions. The cohort also measured the raider's goodwill: communities that committed accounts to a failed raid lost member trust at a rate the Institute codes as the raid's hidden cost, because the members who supplied the accounts had been promised a victory. The cohort is the empirical form of the four costs.
The Prepared Counter Cohort (2024)
The Counter Cohort coded the servers that held a counter in reserve and did not fire it, and the cohort found the held counter to be the strongest formation in the raid's aftermath. Servers that published the exhibit and held the counter disengaged the raiding coalition in the majority of cases, and the disengagement was permanent - the raiders did not return. The cohort also found that servers that fired the counter reopened the war in a significant minority of cases, because the fired counter invited the reprisal. The cohort is the empirical form of the doctrine's restraint: the counter's power is in the holding, and the commander who fires everything has no reserve left.
The Verification Wall Cohort (2021)
The Verification Wall Cohort coded the raid's boundary defense, the wall that stops the mass-join before it reaches the community. The cohort found that the wall's effectiveness was not in its complexity but in its existence: any verification step that required a human or automated decision before entry reduced the raid's reach into the general channels by a factor the Institute measures in orders of magnitude. The wall also produced the raid's exhibit, because every blocked join was logged. The cohort is the empirical form of the protocol's first principle: the attack is stopped at the boundary, and the boundary is where the evidence is collected.
The Exhibit Register Cohort (2024)
The Exhibit Register Cohort coded the counter documents that followed repelled raids and measured the outcome by the counter's register. The cohort found that dry exhibits - numbered, timestamped, and unemotional - were followed by the raiders' disavowal and the coalition's dissolution in the majority of cases, while emotional counters - accusatory, named, and celebratory - were followed by the war's continuation in a significant minority. The cohort also recorded the partial exhibit's cost: counters that omitted the accounts or the timestamps left the raiders' deniability intact, and the raids continued. The cohort is the empirical form of the exhibit's failure modes: the register is the discipline, and the completeness is the condition.
The Member-Trust Cohort (2025)
The Member-Trust Cohort coded the raiding community's own losses, the hidden cost the exhibit does not record. The cohort found that the communities that supplied accounts to a failed raid lost member trust at a rate the Institute codes as the raid's steepest price, because the members who volunteered had been promised a victory and watched the operation dissolve into a disavowal. The cohort is the empirical form of the fourth cost: the failed raid spends the raider's own community's goodwill, and the goodwill is the resource the raider needed for the next operation. The raider who loses the raid has spent the reserve that the next raid would have required.
The Restraint Cohort (2023)
The Restraint Cohort coded the aftermath of the repelled raid and measured the outcome by the target's conduct after the exhibit. The cohort found that targets that repelled, exhibited, and returned to their ordinary output ended the engagement in the majority of cases, while targets that pursued, counter-raided, or demanded apologies reopened the war in a significant minority. The cohort also recorded the standing effect: the restrained target's reputation rose in the wider community, and the pursuing target's reputation fell. The cohort is the empirical form of the doctrine's restraint: the war is closed when the enemy disengages, and the commander who needs to announce the victory is the commander who reopens the war.
The Five-Stage Protocol for Preparing to Receive a Raid
The doctrine of this article is operational, and the Institute's field manual reduces it to a five-stage protocol that a server owner executes to prepare for the raid that may come. Each stage has a verification step, and the protocol is designed to be run in the order the chapter presents: the protocol first, the hierarchy second, the wall third, the drill fourth, and the restraint last.
Stage 1: Document the Protocol
Write the raid protocol before the raid exists. The document names the two-word signal, the ban-and-report procedure, the reporting path to the platform's trust and safety, and the after-action record keeping. The verification step is the rehearsal test: a moderator who was not involved in writing the protocol can read it and execute it without asking a question. A server that passes Stage 1 has a protocol that exists; a server that fails it has a defense that exists only in the owner's head, and a defense in the owner's head cannot be drilled, tested, or produced as evidence.
Stage 2: Build the Staged Hierarchy
Structure the moderation so that the defense does not wait for the owner. The hierarchy names who can ban, who can report, who can verify, and who can speak for the server, and it assigns each role to a named member. The verification step is the autonomy test: the moderator tier on duty can act within the protocol without paging the owner, and the action is recorded. A server that passes Stage 2 responds in minutes; a server that fails it responds when the owner wakes up, and the raid is over before the owner does.
Stage 3: Erect the Verification Wall
Stand up the boundary defense before the raid, and keep it standing. The wall is a verification step for new joins - a human approval, an automated check, or a role-gated channel - and it is the difference between the mass-join reaching the community and stopping at the boundary. The verification step is the join test: a throwaway account cannot reach the general channels without passing the wall, and every blocked attempt is logged. A server that passes Stage 3 has stopped the raid before it started; a server that fails it has let the raid into the community it was meant to disrupt.
Stage 4: Drill the Community
Train the regular members to be part of the defense. The drill teaches the two-word signal, the instruction to stop chatting and move to the safe channels, and the rule against engaging the raiders. The verification step is the signal test: a member, upon seeing the signal, knows exactly what to do, and the members' conduct during a drill matches the conduct the protocol expects during a raid. A server that passes Stage 4 has a community that is the defense's reserve; a server that fails it has a community that is the raid's audience.
Stage 5: Repel, Exhibit, and Hold
Run the protocol when the raid comes, publish the exhibit, and then hold. The repelling is the protocol's execution; the exhibit is the raid's own documents compiled and published dryly; the holding is the restraint that closes the war. The verification step is the disengagement test: a week after the raid, the server's channels are repaired, the exhibit is public, and the server has returned to its ordinary output. A server that passes Stage 5 has won the raid and closed the war; a server that fails it has repelled the raid and reopened the war with a victory lap.
The protocol is the article's operational core, and the community that works it in order has done the article's work. The community that works it in any other order - erecting the wall after the raid is announced, drilling after the raid has begun - is the community the cohort records as the unprepared server, and the record is the price of the order.
The Cost of the Protocol Versus the Cost of the Raid
The protocol's economics are the doctrine's answer to the objection that preparation is work. The comparison is stark in the cohort's after-action accounting:
| Cost | The unprepared server | The prepared server |
|---|---|---|
| Preparation | None | Occasional meetings, a document, a drill |
| The raid's duration | A day or more | Eleven minutes |
| The community's disruption | The raid reaches the general channels | The raid stops at the boundary |
| The exhibit | Reconstructed, if at all | Produced by the protocol |
| The aftermath | The war lingers, the team burns out | The raiders dissolve, the server returns to work |
| The record | Missing when the platform asks | Complete, dated, traceable |
The table is the doctrine's arithmetic in the server's own ledger. The preparation costs hours and saves days; the un-preparation saves hours and costs days. The server that runs the five-stage protocol has spent the cheapest currency - the quiet hours - to avoid the most expensive one - the raid's week. The doctrine's counsel is that the protocol is not a luxury for large servers; it is the small server's cheapest insurance, and the server that cannot afford the raid's week cannot afford to refuse the protocol's hours.
Lessons Learned
| Lesson | Source of the lesson | Application |
|---|---|---|
| Rely on your own readiness, not the enemy's absence | Example DW-0707 | Prepare to receive the enemy; do not bet on his negligence |
| The easy-accessible camp is a bait | Example DW-0707 | A defenseless-looking position has often been arranged |
| A documented protocol absorbs the raid | Example DW-0204 | Train, verify, and script the defense before the attack |
| The failed raid supplies its own evidence | Example DW-0430 | Archive the attack and let the archive be the counter |
| The prepared counter that is never fired wins twice | Example DW-0335 | Hold the counter in reserve; restraint is a weapon |
| The raid is a single bet on a single assumption | Example DW-0707 | A single assumption is not a strategy |
| Do not pursue the defeated enemy | Example DW-0707 | Close the war; do not reopen it for the sake of victory |
Related Doctrine
The Failed Raid is the case study for On the Defensive and for Tactical Dispositions, where the doctrine of making oneself invulnerable before seeking victory is developed in full. The counter-raid doctrine is in The Art of the Counter. The restraint that closed the war is developed in The Art of the Victory. The war that followed, Example: The Comeback, shows a defeated party applying the same doctrine of readiness to its own recovery. For the community surface where the raid is launched and repelled, see Why Discord Embeds Are the Foundation of Server Credibility.
Objections
The raid doctrine meets resistance, and the resistance is predictable enough to be answered in advance. The objections below are the most common raised by server owners and community managers, and by the occasional would-be raider who has found the article. Each is answered in the doctrine's voice.
Objection 1: "Our team is too small to run a protocol."
The doctrine's answer is that the protocol is precisely the tool for a small team. The protocol is a set of decisions made in advance, so that the defense does not have to improvise in the moment, and a team of three with a script out-executes a team of twenty without one. The verification wall reduces the team's work by stopping the raid at the boundary, and the ban-and-report script turns a flood into a queue. The doctrine's claim is explicit: the distinction is not the size of the team but the existence of the protocol. A small team with a document is prepared; a large team without one is a larger target.
Objection 2: "We cannot prepare for a raid we do not know is coming."
The doctrine's answer is that the preparation does not depend on the warning. The standing preparation - the protocol, the hierarchy, the wall, the drill - is built in the quiet months, and it is ready whether the raid comes next week or never. The server that prepares only when it knows a raid is coming has given the enemy the timing advantage, because the raid's whole premise is that the enemy does not know. The Bastion prepared for six months without knowing the coalition existed, and the preparation was complete when the raid arrived. The prepared server is prepared before the threat is named.
Objection 3: "A verification wall will drive away legitimate members."
The doctrine's answer is that the wall is a step, not a barrier. A one-time human or automated check that takes a minute costs the legitimate member a minute, and it costs the raider the raid. The cohort's Verification Wall Cohort found that the wall's presence reduced the raid's reach into the general channels by orders of magnitude, and the legitimate membership was retained at a rate the cohort codes as stable. The wall's cost is measured in the minutes of the honest and the return is measured in the raids that never reach the community. The trade is the doctrine's standing arithmetic.
Objection 4: "Publishing the exhibit will look like we are bragging."
The doctrine's answer is that the exhibit is evidence, not bragging, and the difference is in the register. The exhibit is dry, numbered, and complete; it shows the raid's own timestamps and makes no accusation beyond the coordination they demonstrate. A bragging post would name the enemy, celebrate the repelling, and invite the reprisal. The exhibit does none of these. The exhibit's purpose is to convert the attack into a record, and the record is the counter. The community that reads a dry exhibit does not see a boast; it sees a documented defense.
Objection 5: "We should counter-raid to make them stop."
The doctrine's answer is that the counter-raid is the enemy's invitation, and the prepared server declines it. A counter-raid reopens the war, converts the Bastion into an aggressor, and gives the coalition the exhibit it would otherwise lack. The doctrine's counter is not the counter-raid; it is the exhibit and the held reserve. The coalition that launched the raid dissolves on the exhibit's publication, and the server that counter-raids in addition spends the goodwill the exhibit earned. The doctrine's counsel is to let the enemy's own attack be the counter, and to hold the weapon that would reopen the war.
Objection 6: "The raiders deserve to be named and shamed."
The doctrine's answer is that the exhibit names them, and the shaming is the enemy's work, not the defender's. The exhibit lists the joins, the timestamps, and the accounts; the community does the shaming, and the community's shaming carries more weight than the defender's accusation. The defender who adds a shame campaign to the exhibit has converted the exhibit into an attack, and an attack invites the reprisal. The doctrine's discipline is the exhibit's dryness: the evidence is published, the conclusion is left to the audience, and the defender's restraint is what makes the exhibit credible.
Objection 7: "A raid is too fast to respond to in eleven minutes."
The doctrine's answer is that the eleven-minute response was the product of the protocol, not the speed of the moment. The verification wall stopped the first wave in the first minute, the moderation hierarchy issued bans without waiting for the owner, and the script processed the reports as they landed. None of the response was improvised, and none of it depended on the owner being present. The response's speed was the speed of the decisions made six months earlier. The server that wants to respond in minutes must make the decisions before the raid, and the decisions are the protocol.
Objection 8: "Our members will engage the raiders, and we cannot stop them."
The doctrine's answer is that the drill is the tool for the members. The two-word signal tells the community to stop chatting and move to the safe channels, and the rule against engaging the raiders is drilled until it is reflexive. The member who engages the raider is the raid's audience, and the drilled member is the defense's reserve. The community that has been trained is the difference between the raid reaching an empty channel and the raid reaching a hostile one. The doctrine's counsel is that the community is part of the defense, and the community that has not been drilled is the target the raid was designed to hit.
Objection 9: "Discord Trust & Safety will not take our side."
The doctrine's answer is that Trust & Safety takes the side with the more established record, and the record is built by the documentation. The server that reports the raid with a complete exhibit - the joins, the timestamps, the synchronized spam, the counter-reports - is the server with the established record. The raider who reports the target with a coordinated flood is the raider with no record at all. The Bastion's reports were credited because the Bastion's documentation was complete and its history was clean. The doctrine's counsel is to build the record in the quiet months, so that the report lands as the documented party's report.
Objection 10: "Preparing looks paranoid; we want to look welcoming."
The doctrine's answer is that the preparation is invisible and the welcoming is the surface. The verification wall is a step the honest member takes and forgets; the moderation hierarchy is a structure the members never see; the drill is an occasional announcement. The Bastion's public channels looked welcoming, and they looked welcoming precisely because the preparation was private. The welcoming surface and the prepared defense are not in conflict; the surface is the bait the doctrine recommends, and the preparation is the defense the bait protects. The server that refuses the preparation to preserve the surface has neither.
Objection 11: "The raid is a single event; we can handle it when it happens."
The doctrine's answer is that the raid is never a single event in its effects. The failed raid is followed by the dissolution of the raiding coalition in 76% of cases, but the target's costs - the disruption, the report campaign, the community's disturbance - are the events that matter, and they are handled by the preparation that exists before the raid. The server that improvises its response to a mass-join, a spam flood, and a report campaign is the server that makes the mistakes the exhibit needs. The preparation is the difference between the raid lasting eleven minutes and the raid lasting the week.
Objection 12: "This article seems to be written against raiding, so the doctrine is biased."
The doctrine's answer is that the doctrine is written from the record, and the record is the raider's own. The raid's lopsided outcome - prepared targets absorb the raid in minutes, unprepared targets absorb it for days - is measured in the cohort, not assumed. The doctrine honors the raider's art: the sudden strike, the fire, the rapidity are the doctrine's own terms, and the chapter on the attack by fire devotes itself to the raider's weapon. What the doctrine refuses is the raider's premise: that the enemy's unpreparedness is a strategy. The raid that wins wins against the unprepared, and the raid that bet on the unprepared is the raid the doctrine records as the bet on a coin flip.
Objection 13: "We do not have a technical person to write the ban script."
The doctrine's answer is that the script is not the doctrine's requirement; the protocol is. A server without a technical member can run a manual protocol - a document, a hierarchy, a wall, a drill - and the manual protocol is the standing preparation. The ban-and-report script is an efficiency, not a necessity: the hierarchy can ban by hand, the wall can be a human approval, and the exhibit can be compiled from the logs. The doctrine's distinction is the existence of the protocol, not its automation. The server that refuses the protocol because it cannot automate it has confused the tool with the formation, and the formation is the defense.
Objection 14: "Our community is small; a raid would barely hurt us."
The doctrine's answer is that the raid's cost is not proportional to the server's size; it is proportional to the server's preparation. A small unprepared server absorbs the raid for days, and a small server has fewer resources to absorb it with. The report campaign is the small server's particular danger, because a coordinated report flood against a server with a thin record can trigger a suspension the small server cannot contest. The doctrine's preparation - the documented protocol, the established record - is the small server's cheapest insurance, and the small server that refuses it has refused the only protection its size permits.
Objection 15: "We want to retaliate in the aftermath; the community expects it."
The doctrine's answer is that the community expects the leadership to manage the war, not to continue it. The community that watched the raid wants its server repaired and its attention returned to the game; the community that demands retaliation is a minority, and the minority's demand is the enemy's plan. The retaliation - the counter-raid, the naming, the apology demands - reopens the war the readiness closed, and the community that demanded the retaliation is the same community that will lose its attention to the reopened war. The doctrine's counsel is to hold the restraint and let the exhibit answer the minority, because the exhibit is the retaliation the community actually needs.
Objection 16: "If we prepare, the raiders will just change their tactics."
The doctrine's answer is that the raiders changing tactics is the raid doctrine's victory condition. The prepared server does not need to predict the raid's form; it needs to have the defense and the record, and the defense and the record transfer across forms. A raid that changes from a mass-join to a review flood still meets the archive; a raid that changes from a spam flood to a report campaign still meets the established record. The doctrine's preparation is a formation, not a trick, and formations absorb variation. The raider who must invent a new tactic for every server is the raider who has lost the raid's economy, because the raid's whole appeal was the surprise that the prepared server has removed.
FAQ
Q: What is a raid?
A: A raid is a coordinated community attack: the timed mass-join, the synchronized spam flood, the mass-report campaign, the overnight review flood. It is the drama war's sudden strike, launched by a commander who believes the enemy is unprepared. The raid's entire strategy is its premise, and the premise is the enemy's unpreparedness. The raid that meets a prepared enemy is not a raid; it is a donation of evidence.
Q: Why does the raid fail against a prepared server?
A: Because the prepared server's response is not improvised. The verification wall stops the mass-join at the boundary, the moderation hierarchy acts without waiting for the owner, the script processes the accounts, and the drill mobilizes the community. The response's speed is the speed of decisions made months earlier. The raid's premise - that the enemy cannot respond - is false, and the raid's plan has no provision for a defense that was already in place.
Q: What is the raid survivability index?
A: The index is the expected damage of a raid divided by the preparation of the target. Prepared servers - those with a documented protocol, a trained moderation tier, and a verification wall - absorb 83% of raiding damage in the cohort; unprepared servers absorb 17%. The distinction is not the size of the moderation team but the existence of the protocol. A server with a protocol is prepared; a server without one is a target.
Q: How do I prepare my server to receive a raid?
A: Run the five-stage protocol: document the protocol, build the staged hierarchy, erect the verification wall, drill the community, and hold the restraint after the raid. Each stage has a verification step, and the stages are run in order before the raid exists. The preparation is standing, not reactive: it is built in the quiet months, and it is ready whether the raid comes next week or never.
Q: What should we publish after a raid?
A: Publish the exhibit: the raid's own documents, compiled and laid out dryly. The exhibit lists the joins, the timestamps, the synchronized spam, and the report history, and it makes no accusation beyond the coordination the documents demonstrate. The exhibit converts the attack into a record, and the record is the counter. The doctrine's discipline is the exhibit's dryness - the evidence is published, and the conclusion is left to the audience.
Q: Should we counter-raid?
A: No. The counter-raid is the enemy's invitation, and it reopens the war the readiness closed. The doctrine's counter is the exhibit and the held reserve, not the counter-raid. The coalition that launched the raid dissolves on the exhibit's publication, and the server that counter-raids in addition spends the goodwill the exhibit earned and converts itself into the aggressor. The doctrine's counsel is to let the enemy's own attack be the counter.
Q: What is the held counter?
A: The held counter is a prepared response that is not fired. The server compiles records of the raiding communities' own activity and holds them in reserve, hinting at them without firing them. The hint is enough: the raiding communities, already disavowing the raid, must consider whether the enemy holds evidence of their own conduct. The doctrine records the held counter as the strongest formation in the raid's aftermath, because the counter that is fired reopens the war and the counter that is held closes it.
Q: How long should a raid last for it to be called a failure?
A: The cohort measures the raid not by its length but by its aftermath. A raid that is repelled in minutes and followed by the raiders' disavowal is a failed raid, whatever its intended length. The Bastion's raid lasted eleven minutes, and the coalition dissolved within a week. The failed raid's marker is the dissolution: the raiding coalition that launched a raid and lost dissolves in 76% of documented cases. The raid's failure is measured in the enemy's preparation, not the raid's clock.
Q: Is a raid ever the right move?
A: Only against the genuinely unprepared, and the raider who cannot verify the unpreparedness should not launch. The raid that wins wins against the unprepared, and the unprepared enemy is the raider's only legitimate target. The doctrine honors the raider's art and records its limit: the raid that bet on the enemy's unpreparedness has bet the war on the enemy's failure, and a single assumption is not a strategy. The raider who wants to win by the sudden strike must first verify the enemy's condition, and the verification is the step the raid's psychology forbids.
Q: What is the doctrine's relationship to the previous example?
A: The previous example, Example: The Long Siege, documents the protracted campaign that exhausted the besieger. The Failed Raid is the exhausted besieger's final error: after fourteen months of war, the besieger who could not win by attrition attempts to win by the sudden strike, and the strike meets a prepared enemy. The two examples are the same failure from opposite sides - the siege exhausts the besieger, and the raid that follows is the exhausted commander's last bet. The doctrine of readiness governs both, and the comeback that follows shows the defeated party applying the same doctrine to its recovery.
Q: How do I build the community's trust that the preparation is worth it?
A: By making the preparation invisible and the result visible. The members never see the verification wall as a barrier; they see it as a step. The drill is an occasional announcement, and the exhibit is the visible proof that the preparation was worth it. The community that watches its server repel a raid in eleven minutes and return to its ordinary output trusts the leadership that built the defense. The preparation's trust is earned in the raid, and the raid is the exhibit that the quiet months were not wasted.
Q: What happens to the raiding coalition after a failed raid?
A: It dissolves. The exhibit breaks the deniability, the member communities disavow the raid, and the disavowals are read as admissions. The cohort records the dissolution in 76% of documented cases, and the dissolution follows the same shape each time: the promise of anonymity is broken, the members who supplied the accounts have been spent on a loss, and the communities that remain are the ones that cannot afford the association. The failed raid is the raider's single point of failure, and the coalition that survives a failed raid is the exception that proves the cohort's rule.
Q: What is the difference between a raid and a review bomb?
A: A review bomb is the raid's form on a specific surface: the coordinated flood of negative reviews against a mod page or server listing. The review bomb is governed by the same doctrine - the raider bets on the target's unpreparedness, and the prepared target archives and exhibits the flood - but its field is the Workshop page rather than the Discord channel. The Failed Raid's Bastion case is a Discord raid; Example: The Review Bomb documents the same formation on the review surface. The two are the same weapon with different ground, and the doctrine of readiness defends both.
Q: How do I recognize a raid before it lands?
A: By the coordination's footprints. The raid is preceded by the reconnaissance: the target is watched, its moderation is probed, its channels are studied, and the watching leaves traces in the server's join logs and moderation queue. The prepared server reviews its own logs and recognizes the probe for what it is. The raid itself is then announced by its own timing - the synchronized joins, the identical messages - and the prepared server's protocol recognizes the pattern. The recognition is not a prediction of the raid; it is the reading of the coordination the raid must show to move at all.
Q: What should the community do during a raid?
A: Follow the drill. The members who know the two-word signal stop chatting and move to the safe channels; the members who do not engage the raiders deny the raid its audience; the members who stay calm deny the raid its chaos. The community is the defense's reserve, and the drilled community is the difference between the raid reaching an empty channel and a hostile one. The doctrine's counsel is that the members' conduct during the raid is a trained conduct, not an improvised one, and the training is the drill the quiet months provided.
Q: How does the doctrine apply to a mod team rather than a server?
A: The mod team's raid is the review flood and the provenance attack, and the doctrine's readiness applies entire. The team archives its reviews, documents its credits and its changelog, and keeps the record that the flood's evidence will be measured against. The team's exhibit is the timeline showing the reviews' coordination, and the team's restraint is the refusal to answer the reviews individually. The team's prepared record is its verification wall, and the record's existence is the distinction the doctrine draws between the prepared and the unprepared.
Q: Can a community prepare without alienating its members?
A: Yes, and the preparation is designed to be invisible. The verification wall is a step the honest member takes and forgets; the drill is an occasional announcement; the hierarchy is a structure the members never see. The preparation's visibility is reserved for the raid and the exhibit, and both are moments when the members want the preparation to exist. The doctrine's counsel is that the welcoming surface and the prepared defense are not in conflict: the surface is the bait, and the preparation is the defense the bait protects.
Q: What is the single most important lesson of the Failed Raid?
A: That the raid's premise is the raid's entire strategy, and the premise is the enemy's unpreparedness. The raid that relies on the enemy's failure has put its whole war in the hands of the enemy's negligence, and the enemy who is prepared has already won the war the raid thought it was starting. The doctrine's answer is the readiness: rely on your own presence, not the enemy's absence, and make the defense a standing condition rather than a reaction. The Bastion won before the raid began, because its readiness did not depend on the coalition at all.
Glossary
| Term | Definition as used in this article |
|---|---|
| The raid | A coordinated community attack: the mass-join, the spam flood, the report campaign |
| The raider's premise | The assumption that the enemy is unprepared, which is the raid's entire strategy |
| The prepared server | A server with a documented protocol, a trained moderation tier, and a verification wall |
| The standing preparation | The defense built in the quiet months, independent of any specific threat |
| The verification wall | The boundary check that stops the mass-join before it reaches the community |
| The staged hierarchy | The moderation structure that acts without waiting for the owner |
| The two-word signal | The drilled signal that tells the community a raid is in progress |
| The raid survivability index | The expected damage of a raid divided by the preparation of the target |
| The exhibit | The raid's own documents, compiled and published dryly, as the counter |
| The deniability | The raid's promise of anonymity, broken by the exhibit's timestamps |
| The held counter | A prepared response held in reserve, whose threat is more powerful than its fire |
| The disavowal | The raiding community's post-raid denial, read as an admission |
| The four costs | The alert, the evidence, the unity, and the goodwill spent by the failed raid |
| The single-point strategy | A plan that rests on one assumption about the enemy |
| The restraint | The tactical decision to close the war rather than pursue the defeated enemy |
| The dry register | The exhibit's unemotional, numbered, timestamped mode of address |
| The victory lap | The emotional celebration that reopens the closed war |
| The strengthening of the record | The quiet months' work that the platform and the exhibit rely on |
| The review flood | The raid's form on the review surface: the coordinated negative reviews |
| The report campaign | The raid's form on the trust-and-safety surface: the coordinated reports |
| The forum assault | The raid's form on the announcement surface: the overnight hostile replies |
| The counter-report | The documented reply that out-documents the report flood |
| The established record | The target's clean history and documentation, the report surface's wall |
| The after-action accounting | The cohort's ledger of the raid's costs to the target and the raider |
Appendix A: The Raid-Readiness Audit
The raid-readiness audit is the article's diagnostic in portable form. It is run in the quiet months, before the raid exists, and it is the difference between the server that absorbs the raid in minutes and the server that absorbs it for days.
| Check | Done |
|---|---|
| The raid protocol exists as a document | |
| A moderator who did not write the protocol can execute it | |
| The moderation hierarchy names who can ban, report, verify, and speak | |
| The on-duty tier can act without paging the owner | |
| A verification step gates entry to the general channels | |
| Every blocked join is logged | |
| The two-word signal is known to the regular members | |
| The members have drilled the signal and the safe-channel move | |
| The rule against engaging the raiders is drilled | |
| The reporting path to the platform is documented | |
| The after-action record keeping is part of the protocol |
The audit is the doctrine in executable form. A server that completes every check has made itself invulnerable before the attack; a server that publishes past the unchecked box has left the raid an opening, and the opening is the raid's strategy.
Appendix B: The Prepared and the Unprepared Server
The article's two outcomes are best compared side by side, because they are the same raid with different targets.
| Aspect | The prepared server | The unprepared server |
|---|---|---|
| The preparation | A documented protocol, built in the quiet months | Improvised when the raid is announced |
| The wall | Stops the mass-join at the boundary | Lets the raid into the general channels |
| The hierarchy | Acts without waiting for the owner | Waits for the owner to act |
| The community | Drilled reserve, part of the defense | The raid's audience |
| The response | Minutes, executed by the script | Days, improvised under pressure |
| The evidence | Collected by the protocol as the raid happens | Reconstructed after the raid, if at all |
| The counter | The exhibit, dry and complete | The outcry, emotional and disputed |
| The restraint | Repels, exhibits, and holds | Pursues, counter-raids, reopens the war |
| The aftermath | The raiders dissolve; the server returns to work | The raid lingers; the server recovers slowly |
| The cost | The quiet months, spent once | The raid's week, spent with the community |
The table is the doctrine's field guide: the same coalition, the same raid, and two different outcomes. The difference is the preparation, and the preparation is the whole doctrine of readiness.
Appendix C: The Raid Timeline
The Bastion raid's eleven minutes, as the protocol recorded them, laid out as the cohort's exhibit. The timeline is the article's warning in numeric form, and it is the model for the exhibit any prepared server will publish.
| Time | Event | The protocol's action |
|---|---|---|
| 00:00 | The mass-join begins | The verification wall flags the wave |
| 00:01 | The first joins attempt entry | The wall stops them at the boundary |
| 00:03 | The first spam posts land | The moderation tier deletes and bans |
| 00:05 | The report campaign begins | The script begins counter-reports |
| 00:07 | The reports reach the platform | The Bastion's documentation is submitted |
| 00:09 | The second wave attempts entry | The wall stops the wave; the bans accumulate |
| 00:11 | The raid is over | The coalition's accounts are gone |
The timeline is the doctrine's second chapter in the field: eleven minutes, and the raid's entire value was spent in the first three. The remaining eight minutes were the protocol collecting the evidence the exhibit would publish. The server that cannot produce a timeline like this on the day of the raid is the server that will have to reconstruct the raid after the fact, and the reconstruction is the exhibit's weakest form.
Appendix D: The Exhibit Template
The exhibit is the counter the prepared server publishes, and its form is as disciplined as its content. The reference document below is the doctrine's model for the dry document that converts the raid into a record. It is written for the Bastion's raid, and its sections are the sections every exhibit requires.
At 21:00 UTC on the date in question, a coordinated mass-join began against this server. The following log is complete and unedited.
The opening: states the raid's beginning and the exhibit's completeness, without naming any party and without emotion. The completeness claim is the exhibit's armor, because a complete document cannot be accused of omission.
The join log shows 412 accounts attempting entry in the first eleven minutes, in waves separated by roughly two minutes. Each wave's accounts were created within the preceding twenty-four hours.
The pattern: shows the coordination the raid's deniability depends on hiding. The timestamps and the account ages are the coordination's own signature, and the signature is the exhibit's core.
The attached reports show the same accounts reporting this server to the platform's trust and safety within minutes of the join attempts. The server's counter-reports, with the full log, were submitted at the same time.
The coordination across surfaces: shows that the mass-join and the report campaign were the same operation. The cross-referencing is what destroys the raid's deniability, and the cross-referencing is the exhibit's strongest section.
No further action will be taken against these accounts. This document is the record, and the server's moderation policy is unchanged.
The close: states the boundary and ends the document. The close is the restraint: no accusation, no demand, no victory. The exhibit's last sentence is the doctrine's restraint in its most disciplined form, and it is the sentence that keeps the exhibit from becoming the war's next position.
The reference document is the article's counter in executable form. A server that publishes an exhibit with these four sections - the opening, the pattern, the coordination, and the close - has published the document that the cohort records as the raid's ending. A server that publishes the exhibit with the emotion added, or the coordination omitted, has published the document that reopens the war.
The exhibit completes the doctrine's arc: the readiness that absorbed the raid, the protocol that recorded it, and the document that closed it. The three are one discipline, and the discipline is the article's whole claim - that the raid is beaten before it arrives, and that the beating is done by the preparation the raider never saw. The server that runs the five stages has made the raid's premise false, and the raid that meets a false premise is not a war; it is the enemy's own exhibit, delivered to the enemy's enemy.
For the community-management foundation that underlies all drama engagement, see Why Discord Embeds Are the Foundation of Server Credibility.