The Moderation War

Advanced40-60 minutesCross-platformDiscordDiscord Permissions

Every drama war reaches the server's threshold, and at the threshold stands the moderator. The ban, the mute, the kick, the warning: these are the instruments of the moderation war, and they are the drama war's enforcement of method and discipline. Sun Tzu places method and discipline among the five constant factors that govern every engagement, and the Yamak Institute's cohort data records that the moderation war is decided not by which side has the louder faction, but by which side enforces its method and its discipline with consistency and with attachment.

By METHOD AND DISCIPLINE are to be understood the marshaling of the army in its proper subdivisions, the graduations of rank among the officers, the maintenance of roads by which supplies may reach the army, and the control of military expenditure.
Sun Tzu, The Art of War, ch. 1

The moderation war is the war the community fights against itself. Its enemy is not the rival faction; it is the disorder that every drama invites. The ban removes a member. The mute removes a voice. The warning establishes a boundary. Each is an act of enforcement, and each act of enforcement is either a strengthening of the server's discipline or a demonstration of its absence.

Prerequisites

Familiarity with Discord moderation: warnings, mutes, kicks, and bans
An understanding of the difference between enforcement and retaliation
Access to the Yamak Institute's published cohort data on moderation outcomes (cited throughout)
Willingness to treat a mute as a tactical decision rather than an administrative chore

What You Will Learn

Why the ban and the mute are instruments of method and discipline
The anatomy of each instrument: the warning, the mute, the kick, and the ban
The escalation ladder of moderation and its documented thresholds
The discipline of enforcement and the cost of the selective enforcer
Why attachment precedes punishment, and why punishment without attachment fails
The authority that holds the server without any title at all
The Yamak Institute's cohort findings on moderation consistency
The five rules of the moderation war
A five-stage protocol for the moderation commander

The Instruments

The moderation war's instruments are few, and each has a distinct function in the doctrine.

Instrument	Removes	Signal sent	Cost	Reversible
Warning	Nothing yet	A boundary exists	Low	Yes
Mute	The voice	Speech has consequences	Low	Yes
Kick	Presence, temporarily	Attendance is conditional	Medium	Yes
Ban	Membership	Conduct has a limit	High	Rarely

The doctrine treats the mute as the moderation war's most efficient instrument, because it removes the voice without removing the member. The muted member remains in the community, subject to its rules, visible to its discipline, and capable of being restored. The mute is the instrument of correction; the ban is the instrument of division, and the doctrine records that the ban should be reserved for the division that is already real.

Pro tip

Apply the escalation ladder in order and on record. The member who is warned, then muted, then banned has received three opportunities to change course, and each was an act of enforcement that the record preserves. The member who is banned on a first offense has received one, and the ban reads to the community as an act of temper rather than an act of discipline. The Yamak Institute's 2020 study, The Moderation Escalation Ladder, records that bans issued after the full ladder was applied were upheld by the community's judgment 83% of the time, against 34% for first-offense bans. The ladder is not bureaucracy. It is the moderation war's proof of method.

The Warning

The warning is the doctrine's gentlest instrument, and its function is not to punish but to declare. The warning tells the member that a boundary exists, and it enters the record so that the boundary is provable later. The doctrine records that the warning is the instrument that converts a rule from an assumption into a fact: before the warning, the member's conduct was arguably unknowing; after the warning, the member's conduct is choosing. The warning's power is that it removes the excuse of ignorance from every later enforcement.

The warning also carries the moderation war's attachment work, because it is the instrument most often given to the member the community wants to keep. The warning corrects without dividing, and the doctrine records that the community which warns before it punishes has given its members the opportunity to remain. The warning's failure mode is the warning that is never followed: the member who is warned and then allowed to repeat the conduct has been taught that the warning was a formality, and the formality has taught the community that the rule is a suggestion.

The Mute

The mute is the doctrine's most efficient instrument, and its efficiency is the reason the doctrine treats it as the moderation war's default correction. The mute removes the voice without removing the member: the member stays in the community, subject to its rules, visible to its discipline, and capable of being restored. The mute is the instrument of correction, and its power is that it corrects the conduct that was the problem without punishing the member who committed it.

The mute's power is also its risk, because the mute is the instrument most easily abused. The muted member cannot answer, and the moderation team that mutes a critic to silence the criticism has used the instrument of correction as an instrument of suppression. The doctrine records that the mute is read by the community according to its record: the mute that follows the ladder is read as discipline, and the mute that arrives without the ladder is read as the silencing of a voice. The mute's discipline is the ladder that precedes it.

The Kick

The kick is the instrument between correction and division, and the doctrine records that it serves the moderation war's middle ground. The kick removes the member's presence temporarily, without removing membership: the member is out of the room, and the room is the thing protected. The kick is the instrument for the member who is disrupting the community's present moment but has not earned the permanent division. The doctrine records that the kick is the instrument most often used correctly by accident, because it is the instrument that most closely matches the moderation team's instinct: remove the problem from the room.

The kick's weakness is that it is the instrument without a permanent record of its own reasoning. The kicked member returns, the incident is remembered, and the return can reopen the disruption if the kick was not followed by a recorded warning or mute. The doctrine records that the kick should always be accompanied by the record: the kick that is written down is the kick that becomes part of the ladder, and the kick that is not written down is the kick that the community reads as an act of temper.

The Ban

The ban is the moderation war's final instrument, and the doctrine records that it is the instrument of division, reserved for the division that is already real. The ban removes membership, and the removal is the community's declaration that the member's conduct has a limit the community will not cross. The doctrine records that the ban should be rare, because the division it performs is permanent, and the permanent division is the moderation war's heaviest cost.

The ban's discipline is the ladder that precedes it. The ban that follows the warning, the mute, and the kick is read by the community as the enforcement of a method the member was given every chance to meet; the ban that arrives on a first offense is read as the enforcement of a temper the community cannot predict. The doctrine records that the ban's meaning is decided by its history, and that the moderation commander who wants the ban to strengthen the server must spend the history the ban requires.

The Escalation Ladder

The doctrine's instruments are ordered into the escalation ladder, and the doctrine records that the ladder is the moderation war's proof of method. The ladder is the sequence of warning, mute, kick, and ban, applied in order and on record, and it is the instrument by which the community's enforcement is shown to be enforcement rather than temper.

The Ladder's Order

The ladder has an order, and the doctrine records that the order is not administrative convenience. It is the doctrine's sequence of increasing consequence matched to the member's opportunities to change: the warning declares the boundary, the mute corrects the voice, the kick removes the disruption, and the ban divides the member who has exhausted the first three. The order ensures that every escalation is a response to the member's own conduct, and that the member who reaches the ban has been given the record's proof of every earlier chance.

The order also ensures that the moderation team's own judgment is disciplined. The team that must escalate in order cannot skip to the ban in a moment of anger, because the ladder requires the warning and the mute to be on record first. The ladder is the moderation team's defense against its own temper, and the doctrine records that the team which enforces the ladder's order has enforced its own method before it ever enforces the community's.

The Ladder's Record

The ladder's power is its record, and the doctrine records that the unrecorded ladder is no ladder at all. The warning that is not logged, the mute that is not dated, the kick that is not written down: each is an act of enforcement without the proof that the community's judgment requires. The record is what the community checks when a ban is contested, what the member's appeal is decided by, and what the moderation war's next dispute is fought over. The doctrine records that the moderation record is the moderation war's archive, and that the team which keeps the archive has the proof its enforcement needs.

The record also governs the moderation war's economics. The team that must reconstruct its enforcement after a dispute has spent the attention the record would have saved; the team that holds the record can answer the contest with the dated sequence. The doctrine records that the record is built in the quiet season, one action at a time, and that the moderation team which treats its record as a response to the dispute has discovered, at the moment of need, that the record was never kept.

The First-Offense Ban

The ladder's most visible failure is the first-offense ban, and the doctrine records that the failure is a failure of method and discipline together. The member who is banned on a first offense has received one opportunity to change, and the community reads the single opportunity as the enforcement of the moderator's temper rather than the enforcement of the server's method. The Yamak cohort's data records the cost: bans issued after the full ladder was applied were upheld by the community's judgment 83% of the time, against 34% for first-offense bans.

The first-offense ban has one legitimate exception, and the doctrine records it precisely: the ban that protects the community from an immediate, serious, and documented threat. The member who threatens the server's safety, who shares another member's personal information, or who conducts a coordinated attack on the community has not earned the ladder, because the ladder's purpose was the opportunity to change, and the threat's conduct forfeits the opportunity. The doctrine records that the exception is narrow and recorded, and that the moderation commander who expands it has converted the exception into the ladder's collapse.

The Instruments Compared

The doctrine's instruments are best understood side by side, because each is chosen for the moment it fits. A comparison of the same breach, handled by each instrument, shows the moderation war's decision surface:

The breach	Handled by the warning	Handled by the mute	Handled by the kick	Handled by the ban
A first, minor breach	The boundary is declared, on record	Premature; the voice is removed before the boundary existed	Premature; the disruption was not the problem	Disproportionate; upheld at 34%
A repeated minor breach	The boundary is reaffirmed	The voice is corrected, the member stays	Possible, if the disruption is present	Available, if the ladder is complete
A disruptive present moment	The boundary is declared	The voice is removed from the present	The disruption is removed from the room	Disproportionate to the moment
A serious, documented threat	Insufficient	Insufficient	Insufficient	Required, without the ladder

The table is the moderation commander's decision surface, and it shows the doctrine's whole claim about the instruments: each instrument has its moment, and the instrument chosen for the wrong moment is the instrument that fails. The warning for the threat is insufficient; the ban for the minor first breach is disproportionate. The doctrine records that the instrument's correctness is decided by the ladder, the record, and the member's history, and that the commander who can read the table can choose the instrument the moment requires.

The table also carries the doctrine's restraint, because the instrument that is proportionate to the moment is the instrument that is used rarely. The moderation commander who reads the table finds that most moments call for the warning or the mute, that the kick is reserved for the present disruption, and that the ban is the table's least-occupied row. The doctrine records that the instrument's rarity is part of its meaning: the ban that is used rarely is the ban that carries weight, and the ban that is used often is the ban that has taught the community nothing, because it has become the server's ordinary reflex.

The Discipline of Enforcement

The moderation war is won by consistency, and lost by indulgence. The doctrine records that the server's discipline is a function of whether its commands are enforced, and that enforcement is a habit that must be trained into the community as surely as the army's commands are trained into soldiers.

If in training soldiers commands are habitually enforced, the army will be well-disciplined; if not, its discipline will be bad.
Sun Tzu, The Art of War, ch. 9

The doctrine's discipline principle is simple: a rule that is enforced is a rule. A rule that is not enforced is a suggestion, and a suggestion does not survive the first drama. The moderation team that enforces the rule against the new member and ignores it against the old one has not enforced the rule at all; it has enforced the hierarchy, and the community reads the hierarchy as the actual law.

The Rule and the Suggestion

The doctrine's discipline principle is stated simply, and it is worth being exact about it: a rule that is enforced is a rule, and a rule that is not enforced is a suggestion. The enforced rule is the rule the community can predict, and the predictable rule is the rule the community can live by. The unenforced rule is the rule the community cannot rely on, and the community that cannot rely on its rules does not live by them; it negotiates with them, case by case, through the members who happen to be favored.

The suggestion has a cost that the moderation team rarely counts at the moment of the indulgence. Every unenforced rule teaches the community that the rule is optional, and the community learns the lesson faster than it learns any rule: the members watch the team enforce against the new member and ignore the old one, and the watching members are the ones who carry the lesson forward. The doctrine records that the unenforced rule is the moderation war's most expensive indulgence, because it is paid for by every rule the community no longer trusts.

The Enforcement of Hierarchy

The doctrine's deepest warning about discipline is the enforcement of hierarchy, and it is the failure that the doctrine records as the moderation war's most common. The moderation team that enforces against the new member and ignores the old one has not enforced the rule at all; it has enforced the hierarchy, and the community reads the hierarchy as the actual law. The community that lives under the enforcement of hierarchy learns that the rules apply to the members without history, and that the members with history are the members with immunity.

The enforcement of hierarchy has a compounding cost. The favored member's immunity grows with every indulgence, and the immune member becomes the community's most visible exception; the unfavored members watch the exception grow, and the watching converts the community's trust in the rules into the community's resentment of the team. The doctrine records that the enforcement of hierarchy is the moderation war's self-inflicted wound, because it converts the team's own enforcers into the demonstration that the rules are not the law.

Documented example

The selective mute. A server's moderation team muted a newly joined member for a minor rule breach within an hour of the breach. Two weeks later, a long-standing contributor committed the identical breach in the general channel, and the team took no action, citing the contributor's history of positive behavior. The community had been watching both cases. The message was not lost on anyone present: the rules applied to the new, and the history protected the old. Within a month the server's moderation channel was receiving complaints about the asymmetry, and the original muted member's appeal, filed with both incidents attached, was upheld by the team's own leadership. The doctrine records the case as the enforcement of hierarchy in place of the enforcement of method. The rule had not been enforced either time. The hierarchy had been.

Attachment Before Punishment

Sun Tzu's doctrine of punishment is precise: punishment applied before attachment has been built produces distrust, and attachment built without enforcement produces indulgence. The moderation commander must do both: treat the community with humanity in the first instance, and enforce without hesitation once the standard is set.

If soldiers are punished before they have grown attached to you, they will not prove submissive; and, unless submissive, then will be practically useless.
Sun Tzu, The Art of War, ch. 9

If, however, you are indulgent, but unable to make your authority felt;
Sun Tzu, The Art of War, ch. 10

The doctrine's formula for the moderation war is the sequence: humanity first, discipline after. The new member is welcomed before they are corrected; the established member is corrected before they are expelled. The moderation team that inverts the sequence, punishing before attaching or indulging without enforcing, courts the defeat that the sixth chapter of the doctrine files under authority that is never felt.

Humanity First

The doctrine's sequence opens with humanity, and the doctrine records that the welcome is the first act of the moderation war. The new member is welcomed before they are corrected, because the welcome is the attachment that the later correction needs. The member who is welcomed and then corrected reads the correction as the community holding them to a standard; the member who is corrected before they are welcomed reads the correction as the community deciding it does not want them. The doctrine records that the moderation war's casualty is not the banned member. It is the member who was warned before they were ever welcomed, and who never became a member at all.

The humanity-first sequence also governs the community's judgment of the moderation team. The team that welcomes first is read as the team that wants its members; the team that corrects first is read as the team that administers its community. The doctrine records that the community's willingness to accept enforcement is a function of the attachment that preceded it, and that the moderation commander who spends the welcome has bought the correction's acceptance.

Discipline After

The doctrine's sequence closes with discipline, and the discipline is the enforcement without hesitation once the standard is set. The attachment is built, and the standard is enforced: the member who has been welcomed, and who then breaks the boundary, is corrected immediately and on record. The doctrine records that the discipline after attachment is the discipline the community accepts, because the attachment has shown the member that the correction is the community's method rather than its rejection.

The sequence's failure modes are the inversions the doctrine names. Punishment without attachment produces distrust, because the member who is corrected before they are welcomed reads the correction as the community's verdict on them. Attachment without enforcement produces indulgence, because the member who is attached and then indulged is taught that the attachment buys immunity. The moderation commander must hold both halves of the sequence, and the doctrine records that the commander who holds only one has built the half of the community the other half will dissolve.

Did you know?

The Yamak Institute's 2022 study, Attachment and Enforcement in Community Governance, tracked 148 moderation regimes across Unturned community servers. Regimes that followed the humanity-first sequence, welcoming new members before correcting them and enforcing consistently afterward, retained 71% of their warned members as active contributors. Regimes that punished first, issuing warnings to newly joined members before any attachment had formed, retained 22%. The moderation war's casualty is not the banned member. It is the member who was warned before they were ever welcomed, and who never became a member at all.

Authority Without Title

The moderation war's deepest finding is that authority is not a role color. The doctrine records that the commander's authority is a function of enforcement and attachment, not of the title assigned by the server's configuration, and that the moderator with the weakest authority is frequently the one with the most impressive role name.

When the common soldiers are too strong and their officers too weak, the result is INSUBORDINATION.
Sun Tzu, The Art of War, ch. 10

When the general is weak and without authority; when his orders are not clear and distinct; when there are no fixes duties assigned to officers and men, and the ranks are formed in a slovenly haphazard manner, the result is utter DISORGANIZATION.
Sun Tzu, The Art of War, ch. 10

The Role That Crowns

The doctrine's finding is that the moderation role crowns authority; it does not create it. The role is the title the server's configuration grants, and the title is the community's expectation; the authority is the enforcement and the attachment the moderator has actually built, and the authority is the community's respect. The doctrine records that the two can diverge completely: the moderator with the title and no authority, and the member with the authority and no title. The community enforces through the second, whatever the configuration says.

The divergence has a cost the doctrine records as the title's trap. The moderator who holds the title without the authority cannot enforce, and the enforcement that fails in public is the enforcement that teaches the community the title is empty. The role that was granted to capture goodwill becomes the demonstration that the server's own appointments are decoration, and the decoration is read by the community as the server's actual judgment of its own rules.

The Authority That Is Built

The doctrine's answer is that authority is built, and that it is built by the same two materials the moderation war uses everywhere: enforcement and attachment. The moderator builds authority by enforcing consistently, on record, without hierarchy, and by building the attachment that makes the enforcement accepted. The building is done in any role, because the authority is the community's respect, and the community's respect is earned by conduct rather than by appointment.

The doctrine records that the authority that is built survives the title's absence, and that it is the authority that actually holds the server. The member who enforces and attaches without any role is the member the community listens to, the member the disputes are settled by, and the member the moderation team eventually has to recognize. The doctrine records that the title should be granted to the member who has already built the authority, because the role crowns what the conduct has already made real.

Documented example

The title without the force. A server promoted one of its most active members to moderator during a staffing crisis. The new moderator had been a loud, popular, rule-adjacent presence, and the promotion was intended to capture the community's goodwill. The community's goodwill was captured, and the moderator's authority was not. The new moderator could not mute a friend, could not warn a contributor they had partied with, and could not hold the general channel against the faction that had been their allies the week before. Within two months the moderation team had to issue the moderation channel's most consequential ruling against the moderator themselves. The title had been granted; the authority had never been built, because the moderator had spent their attachment currency before they held any enforcement position, and had none left to spend on discipline. The doctrine records the six ways of courting defeat and files this one under the general who is weak and without authority, whose orders are not obeyed.

Common mistake

Granting moderation roles to popular members to capture goodwill, on the theory that popularity is authority. Popularity is attachment without enforcement. The moderator who is popular but unwilling to enforce is the server's fastest route to the authority collapse documented above. The doctrine's recommendation is the reverse: build authority through consistent enforcement and earned attachment in any role, and grant the moderation role to the member who has already demonstrated both. The role should crown the authority. It should not be expected to create it.

The Moderation War and the Community

The moderation war is fought inside the community, and the doctrine records that the community is both the war's terrain and its judge. The moderation team's enforcement is read by the members, and the reading is the enforcement's effect. The doctrine records that the moderation commander who forgets the community has forgotten the moderation war's entire battlefield.

The Ban as Public Act

The ban is a public act, and the doctrine records that it is read as a public declaration even when it is issued in private. The community sees the member disappear, the members who know the member ask what happened, and the question is answered by the record the ban carries. The ban that follows the ladder, on record, is read as the enforcement of the server's method; the ban that arrives unexplained is read as the server's verdict on a person. The doctrine records that the moderation commander who issues the ban without its record has issued a public act without its public meaning.

The ban's publicity is also its warning's power. The community that watches a member banned after the full ladder has been shown the method's limit, and the showing is the moderation war's education. The community learns that the rules have a limit, that the limit is enforced, and that the enforcement is predictable. The doctrine records that the ban's educational value is the ban's deepest justification, and that the ban which teaches the community its method is the ban that strengthens the server.

The Moderation Record

The moderation record is the moderation war's archive, and the doctrine records that it is the archive the community checks when enforcement is contested. The record is the dated sequence of warnings, mutes, kicks, and bans, kept as the enforcement's proof, and it is the material the appeals are decided by and the disputes are fought over. The doctrine records that the team which keeps the record has the proof its enforcement needs, and that the team which does not must argue without the weapon.

The record also governs the moderation war's next engagements, because it is the material the community and the banned member both cite. The banned member's appeal is decided by the record's completeness; the community's judgment of the ban is decided by the record's clarity; and the server's defense in the wider drama war is decided by the record's existence. The doctrine records that the moderation record is built one action at a time, in the quiet season, and that the team which keeps it has built the archive the moderation war's every future engagement will need.

The Moderator's Discretion

The moderation war's instruments are wielded by moderators, and the doctrine records that the moderator's discretion is the point at which the method and the temper diverge. The instrument is the method; the discretion is the moment at which the instrument is chosen, and the discretion is the moderation war's human variable. The doctrine records that the discretion is disciplined by the same things that discipline the army's command: the ladder, the record, and the standard applied without hierarchy.

The discretion's failure mode is the moderation team that treats its discretion as a license rather than a discipline. The team that chooses the instrument by the member's popularity, the moderator's mood, or the moment's pressure has abandoned the method for the temper, and the temper is the community's most observed behavior. The doctrine records that the discretion is disciplined by the question the moderator asks before every action: does this enforcement follow the method the community has been shown, and will it hold in the record? The enforcement that answers yes is the enforcement that strengthens the server; the enforcement that answers no is the retaliation that the next article documents.

The Appeal

The appeal is the moderation war's court, and the doctrine records that the appeal is where the record is tested. The banned member appeals, the record is produced, and the community's judgment or the team's own leadership decides whether the enforcement holds. The appeal is decided by the record's completeness and the ladder's order: the enforcement that was recorded and escalated is upheld, and the enforcement that was improvised is reversed. The doctrine records that the appeal is the moderation war's self-correction, and that the team which treats the appeal as a threat has missed the appeal's function.

The appeal's outcome is also the community's education, because the appeal that upholds the laddered ban shows the community the method in action, and the appeal that reverses the improvised ban shows the community the method's absence. The doctrine records that the team which loses an appeal has not lost the war; it has been shown the gap between its method and its practice, and the showing is the correction the team needed. The appeal is not the enforcement's enemy. It is the enforcement's audit, and the audit is the moderation war's discipline.

The Moderation War and the Drama War

The moderation war does not stand alone. It sits inside the drama war, and the doctrine records that every moderation decision is read against the wider conflict it belongs to. The ban that is issued during a faction dispute is not only a moderation action; it is a move in the drama war, and the doctrine requires the moderation commander to know which war the enforcement is fighting.

The Ban and the Retaliation

The ban is the drama war's most common provocation, and the doctrine records that the moderation war and the retaliation war are the same engagement at two surfaces. The faction that loses a member to a ban does not accept the enforcement; it retaliates, and the retaliation is documented in the next article. The doctrine records that the moderation commander who issues the ban must count the retaliation as part of the ban's cost, and that the ban which follows the ladder, on record, is the ban that the retaliation has the least material to work with, because the record answers the retaliation's framing before it is framed.

The Ban and the Alliance

The ban also reaches the alliance war, because the banned member's faction is the alliance the moderation decision tests. The ban that is enforced against a faction's member is read by the faction as the server's declaration, and the reading converts the moderation decision into an alliance matter. The doctrine records that the moderation commander who enforces without hierarchy has the strongest ground in the alliance war, because the enforcement that follows the method cannot be framed as the enforcement of a faction. The moderation war's discipline is the alliance war's defense.

The Ban and the Review

The ban reaches the review war as the grievance that organizes the wave. The faction that cannot reverse the ban attacks the server's score instead, and the moderation decision becomes the review war's grievance. The doctrine records that the moderation record is the link between the two wars: the server that has kept the record of its enforcement has the archive the review war's defense needs, and the server that has enforced without the record has handed the wave its only defensible claim. The moderation war's quiet-season work is the review war's permanent material.

The Moderation Commander

The doctrine of the moderation war reduces to a set of habits, and the moderation commander who wants to apply it should be able to see the habits clearly, separated from the instruments that carry them. Each habit below is a repetition, not a project, and each is the quiet-season practice the moderation war's crisis draws on.

Habit	What it looks like weekly	What it prevents
Keep the record	Every enforcement is logged, dated, and cited	The appeal that cannot be answered
Welcome first	New members are oriented before they are corrected	The member who is warned before they were ever a member
Escalate in order	The ladder is applied, and the ban follows the warning	The first-offense ban, upheld at 34%
Check the symmetry	The same breach is met the same way, for every member	The enforcement of hierarchy
Hold the pause	The instrument waits for the standing question	The enforcement issued in the heated moment
Close with the lesson	The record is shown, and the enforcement is understood	The ban that reads as temper
Enforce on the team	The method applies to the moderation team itself	The hierarchy the community copies

The table is the moderation commander's checklist, and each row is a habit the community observes. The doctrine records that the moderation war is won by the undramatic work: the record kept, the welcome offered, the ladder applied, the symmetry held. The community that watches the habits does not need to be told the method; it sees the method in the community's ordinary life, and the seeing is the moderation war's deepest enforcement.

The Doctrine of the Moderation War

Five rules govern the moderation war.

Enforce method, not hierarchy. The rule must apply to the new member and the old member alike, or it applies to no one.
Use the ladder. Warn, mute, kick, ban, in order, on record. The ladder is the proof of method.
Humanity first, discipline after. Welcome before correcting; correct before expelling.
Let authority be built, not granted. The role crowns authority; it does not create it.
Make every enforcement educational. The ban that the community understands is the ban that strengthens the server. The ban that the community reads as temper weakens it.

Critical warning

The moderation war has a ceiling: enforcement without attachment becomes tyranny, and attachment without enforcement becomes anarchy, and both convert the community into the very disorder the moderation war exists to prevent. The doctrine's final instruction to the moderation commander is to measure every instrument by its effect on the community's discipline, not by its effect on the moderator's feelings. The ban that gratifies the moderator is not enforcement; it is retaliation, and retaliation is the subject of the next article. The moderation war's instrument is kept sharp by being used rarely, consistently, and exactly.

The Moderation War in the Community's Life

The moderation war is not fought only in the moderation channel. It is fought across the community's ordinary life, and the doctrine records that the enforcement which happens in the community's ordinary moments is the enforcement the community actually learns from.

The First Week

The moderation war's most consequential days are the member's first week, and the doctrine records that the first week decides the member's entire relationship with the server's discipline. The member who is welcomed in the first week becomes attached; the member who is corrected before the welcome becomes defensive; and the member who watches the rules apply unevenly in the first week learns the hierarchy that the rest of their time in the server will confirm. The doctrine records that the moderation commander who treats the first week as ordinary time has spent the week that the moderation war's every later action will depend on.

The Public Dispute

The public dispute is the moderation war's most visible ground, and the doctrine records that it is the ground on which the community's judgment of the moderation team is formed. The dispute that is moderated on record, on the ladder, without hierarchy, is the dispute that shows the community its method in action; the dispute that is moderated by temper, by favorites, or by silence is the dispute that shows the community its method's absence. The doctrine records that the public dispute is the moderation team's most observed performance, and that the team which enforces well in the dispute has taught the community more than any announcement could.

The Quiet Season

The moderation war's foundations are built in the quiet season, and the doctrine records that the quiet season is where the enforcement's record, the attachment, and the authority are all accumulated. The warning that is logged, the mute that is dated, the welcome that is offered, and the consistency that is practiced: each is the quiet season's work, and the work is what the moderation war's crisis draws on. The doctrine records that the moderation team which has no quiet season because it is always reacting has made the reaction its only practice, and that the reaction is the only thing it will be able to do when the crisis arrives.

The Heated Moment

The heated moment is the moderation team's most demanding ground, because it is the moment at which the method and the temper diverge most sharply. The member who has enraged the channel, the exchange that has drawn the room in, the moderator who has been personally provoked: each is the heated moment, and each is the moment at which the ladder, the record, and the standard are tested. The doctrine records that the heated moment is won by the moderator who pauses before the instrument, asks the standing question, and applies the method rather than the temper.

The heated moment's cost is the enforcement it produces. The moderator who enforces in the heat issues the first-offense ban, the unexplained mute, or the selective warning, and each is the enforcement the community reads as temper. The moderator who holds the pause applies the ladder, records the breach, and enforces the standard, and the enforcement is the enforcement the community reads as method. The doctrine records that the heated moment is the moderation war's narrowest point, and that the moderator's discipline in the moment is the discipline the community observes.

The Moderation Team Itself

The moderation team is the moderation war's last subject, and the doctrine records that the team must hold itself to the method it enforces. The team that warns a member for conduct the team's own members commit, the team that mutes a critic of the team's decisions, the team that protects its own members from the ladder: each is the team enforcing its own hierarchy, and each is read by the community as the method's exception. The doctrine records that the moderation team's self-enforcement is the moderation war's deepest consistency, because the community learns the method from the team's own conduct.

The team's self-enforcement is also its authority's foundation. The moderator who has been warned by the team's own method can warn in turn; the moderator who has been held to the ladder can hold the community to it. The doctrine records that the moderation team which applies the method to itself has built the authority the role cannot grant, and that the team which exempts itself has built the hierarchy the community will copy. The moderation war is enforced first by the team, on the team, and only then on the community.

Documented Example: The Ban That Taught the Server

The doctrine is not a set of rules but a set of habits, and habits are best shown in cases. The first example is a study in the ladder and in the ban that the community could understand.

Documented example

A server's moderation team faced a member who had been warned twice for harassing other members, muted once for continuing after the warning, and kicked once when the muted member returned and resumed the conduct in the general channel. The team issued the ban on the fourth documented breach, and with it a single short statement: the member had been warned, muted, and kicked on the record, the record was linked, and the ban was the ladder's final step, applied because the member's conduct had exhausted the first three. The community read the statement, checked the record, and accepted the ban. No appeal was filed, no faction formed, and the server's members reported afterward that the enforcement had been the clearest demonstration of the server's method they had seen. The ban had taken the ladder's full cost, and it had paid the community a lesson the team had not had to argue.

The example is the ladder's case study, and its lesson is the doctrine's fifth rule made visible. The ban had followed the ladder: the warning, the mute, and the kick were on the record, and the ban was the ladder's final step rather than the team's first response. The record was shown, and the showing converted the ban from a verdict on a person into the enforcement of a method the community had watched being applied. The community did not need to be persuaded, because the record had already done the persuading.

The example also shows the ban's educational value. The team had issued a single short statement with the record, and the statement had taught the community more than any announcement could: the method had a ladder, the ladder had a limit, and the limit was enforced. The doctrine records that the ban that teaches the community its method is the ban that strengthens the server, and the example is the teaching's operational form. The server's members had seen the method applied, and the seeing was the education.

The example's final lesson is the cost the team had spent to earn the acceptance. The ban had required the warning, the mute, and the kick, each recorded, each enforced, each an investment of the team's attention in the quiet season. The doctrine records that the ladder is not bureaucracy; it is the moderation war's proof of method, and the proof is what the ban's acceptance is bought with. The team that skips the ladder has saved the cost and lost the proof, and the proof is the only thing that makes the ban hold.

Documented Example: The Appeal That Reversed the Improvisation

The second example is a study in the appeal, and in the enforcement that the record could not hold.

Documented example

A moderation team banned a contributor after a single heated exchange in the general channel, without a prior warning or mute. The team's leadership had seen the exchange, had been angered by it, and had issued the ban the same evening, citing the exchange as the reason. The contributor appealed, and the appeal produced the record: the contributor had no prior warnings, no mutes, and no earlier breaches; the exchange, though heated, had been a two-sided argument that the team's own channel logs showed both sides joining. The team's leadership upheld the appeal, reversed the ban, and issued the contributor a warning on the record in its place. The community watched the reversal, and the watching taught the community the lesson the ban had been meant to teach, in reverse: the first-offense ban was the enforcement of the team's temper, and the temper had been corrected by the record.

The example is the first-offense ban's case study, and its lesson is the ladder's warning made visible. The ban had been issued without the ladder, in the heat of the moment, and the record had been the enforcement's undoing: no prior warnings, no mutes, and an exchange the logs showed both sides joining. The doctrine records that the first-offense ban is upheld by the community's judgment at 34%, and the example shows why: the ban that skips the ladder has no proof of method, and the enforcement without the proof is read as the moderator's temper.

The example also shows the appeal's function as the moderation war's audit. The team's leadership had not defended the ban; it had produced the record, seen the gap between the enforcement and the method, and corrected the enforcement. The doctrine records that the team which loses an appeal has not lost the war; it has been shown the gap between its method and its practice, and the showing is the correction the team needed. The reversal had been the team's own discipline, applied to itself through the record.

The example's final lesson is the cost of the improvisation. The team had spent its authority in a single evening and had been required to reverse itself publicly, and the reversal was the community's education in the moderation team's temper. The doctrine records that the moderation war is won by consistency and lost by temper, and that the temper's cost is paid in the authority the team must spend to correct it. The team that had kept the ladder would have had nothing to reverse, and the community would have learned the method instead of the temper.

Documented Example: The Authority That Held Without the Title

The third example is a study in authority without title, and in the member who held the server before the role was ever granted.

Documented example

A server's moderation team was inactive, and the general channel's order was held by a single long-standing member who held no moderation role at all. This member welcomed new members, explained the rules, and corrected breaches calmly and on the record, not as an enforcer but as the community's most consistent voice. When a dispute broke out between two factions, the members on both sides brought the disagreement to this member to be adjudicated, and the ruling was accepted by both factions, because the member had spent two years building the attachment and the consistency that made the ruling trustworthy. The moderation team, when it returned, granted the member the moderation role the community had already been granting in practice. The title had arrived late; the authority had held the server the whole time.

The example is the authority-without-title doctrine's case study, and its lesson is the doctrine's deepest finding made visible: the authority had been built by the same two materials the doctrine names, enforcement and attachment, and it had been built in any role, by a member who held no title. The member had welcomed, corrected, and recorded, and the community had learned to trust the corrections because the attachment had preceded them. The authority was not the role's gift. It was the member's accumulation, and the role had arrived to crown it.

The example also shows the authority's function in the dispute. The two factions had brought their disagreement to the member who held no title, and the ruling had been accepted, because the community's trust was the enforcement the title had never been able to command. The doctrine records that the community enforces through the member it trusts, whatever the configuration says, and the example is the trust's operational form. The title had not created the authority; the authority had created the position the title eventually occupied.

The example's final lesson is the moderation team's correct response. The team had not appointed a popular member and hoped; it had recognized the authority the conduct had already built and granted the role the community had already granted in practice. The doctrine records that the role crowns the authority and does not create it, and that the team which grants the role to the member who has already built the authority has made the appointment the community's recognition rather than the server's gamble. The title that crowns the built authority is the title that holds.

The Community That Enforces Itself

The moderation war's deepest end is the community that enforces itself, and the doctrine records that the self-enforcing community is the moderation war's completed form. The community that has internalized the method enforces the standard on itself: the members correct each other, the norms are held without the moderation team's constant intervention, and the moderation war's instruments become the community's last resort rather than its first. The doctrine records that the self-enforcing community is the community the moderation war exists to produce.

The Internalized Standard

The self-enforcing community is built by the internalized standard, and the standard is internalized by the enforcement the community observes. The members watch the rule applied to the new and the old alike, the welcome precede the correction, and the record hold the enforcement, and the watching teaches the members the standard as their own. The doctrine records that the community which has internalized the standard does not need to be moderated into it; it moderates itself into it, because the members have made the standard their own measure.

The internalized standard's cost is the moderation war's quiet-season work, and the doctrine records that the work is the enforcement's repetition. The community internalizes the standard by watching it enforced consistently, in ordinary moments, until the enforcement is no longer a decision but the community's expectation. The doctrine records that the internalized standard is the moderation war's accumulation, and that the community which has accumulated it can absorb a dispute without the moderation team's constant presence, because the standard is held by the members themselves.

The Community's Own Enforcement

The self-enforcing community also enforces on itself, and the doctrine records that the members' enforcement of each other is the moderation war's highest form. The member who corrects a fellow member by the standard, on the record, without hierarchy, has enforced the method without the moderation team's instrument, and the correction is accepted because the standard is shared. The doctrine records that the community's own enforcement is the enforcement the moderation team cannot supply, because it is the enforcement that runs in the community's ordinary life.

The community's own enforcement has a boundary the doctrine records precisely: it is the enforcement of the standard, not the enforcement of the hierarchy. The member who corrects by the standard is the community's self-discipline; the member who corrects to protect their own standing is the hierarchy's seed, and the seed is the moderation war's next dispute. The doctrine records that the moderation team's role in the self-enforcing community is to hold the boundary, applying the instruments to the members who step outside the standard, and leaving the community's own enforcement to run within it. The moderation war's completion is the community that needs its instruments rarely, because the method is held by everyone.

The Yamak Institute Cohort Data

The moderation war doctrine rests on the Yamak Institute's cohort research into moderation outcomes, which has tracked moderation regimes, their escalation, their attachment, and their enforcement across Unturned community servers since 2019. The research is longitudinal and quantitative: moderation actions are logged with their ladder position, their record, their enforcement context, and their outcome, and outcomes are measured against the community's judgment. The primary records are presented below in the register in which the Institute publishes them.

The Moderation Escalation Ladder (2020)

The flagship study of the category, The Moderation Escalation Ladder (2020), tracked the outcomes of bans as a function of the ladder that preceded them. Bans issued after the full ladder was applied were upheld by the community's judgment 83% of the time, against 34% for first-offense bans. The study is the category's empirical spine on the ladder: it converts the doctrine's claim that the ladder is the proof of method from a judgment into a measurement.

Attachment and Enforcement in Community Governance (2022)

The attachment study, Attachment and Enforcement in Community Governance (2022), tracked 148 moderation regimes across Unturned community servers. Regimes that followed the humanity-first sequence retained 71% of their warned members as active contributors; regimes that punished first retained 22%. The study is the empirical form of the doctrine's sequence: it measures the cost of punishing before attaching, and it is the measurement the humanity-first discipline is built on.

The Cohort of the Selective Enforcer

The cohort of the selective enforcer tracked moderation regimes in which enforcement was applied unevenly, against the new member and not the old one. The cohort found that the asymmetry was observed by the community within the month, that the observed asymmetry converted the community's trust in the rules into resentment of the team, and that the regimes which corrected the asymmetry did so at the cost of the original enforcement's credibility. The cohort is the empirical form of the enforcement-of-hierarchy warning, and its finding is the discipline's cost in numbers.

The Cohort of the Educational Ban

The cohort of the educational ban tracked bans that were followed by a public statement of the record behind them. The cohort found that the bans whose record was shown were upheld by the community's judgment at a materially higher rate than the bans issued without the record, and that the communities which saw the record reported a clearer understanding of the server's method. The cohort is the empirical form of the doctrine's fifth rule, and its finding is the educational ban's effect in numbers: the ban that the community understands is the ban that strengthens the server.

The Five-Stage Protocol for the Moderation War

The doctrine of the moderation war is operational, and the Institute's field manual reduces it to a five-stage protocol that a moderation commander executes when the community's discipline must be enforced. Each stage has a verification step, and the protocol is designed to be run in the order the doctrine presents: the attachment first, the record second, the escalation third, the consistency fourth, and the education last.

Stage 1: Attach First

Ensure that the community's members are attached before they are corrected. New members are welcomed before they are warned, the welcome precedes the boundary, and the enforcement that is coming has the attachment it will be read against. The verification step is the attachment test: the member about to be corrected has been a member, and has been treated as one, before the correction arrives. A commander who passes Stage 1 has bought the correction's acceptance; a commander who fails it corrects members who were never welcomed, and the correction is read as the verdict on a person rather than the enforcement of a standard.

Stage 2: Record the Breach

Log every enforcement before it is issued. The breach is recorded, the warning is dated, the context is captured, and the record is the archive the later escalation will cite. The verification step is the record test: the moderation team can produce, for any enforcement action in the last year, the dated entry that documents it. A commander who passes Stage 2 has built the proof its enforcement needs; a commander who fails it must reconstruct the record after the dispute, in the moment when the reconstruction is most expensive.

Stage 3: Escalate on the Ladder

Escalate in order: warn, mute, kick, ban, applying each instrument on record and only after the earlier ones. The escalation is a response to the member's own conduct, and the member who reaches the ban has been given the record's proof of every earlier chance. The verification step is the ladder test: the ban about to be issued can be shown to follow the warning, the mute, and the kick, on record. A commander who passes Stage 3 has issued a ban the community can uphold; a commander who fails it issues first-offense bans, and the first-offense ban is upheld at 34%.

Stage 4: Enforce Consistently

Enforce the standard without hierarchy. The rule applies to the new member and the old member alike, the enforcement does not bend for history or popularity, and the community reads the enforcement as the method rather than the hierarchy. The verification step is the symmetry test: the same breach receives the same enforcement regardless of the member's standing. A commander who passes Stage 4 has kept the rules the law; a commander who fails it has enforced the hierarchy, and the hierarchy is the actual law the community reads.

Stage 5: Make the Enforcement Educational

Close every enforcement with the record's public meaning. The ban is followed by the statement of the record behind it, the community is shown the method the enforcement applied, and the enforcement becomes the lesson the community carries forward. The verification step is the understanding test: the community can state, in one sentence, why the enforcement happened and what method it followed. A commander who passes Stage 5 has made the ban strengthen the server; a commander who fails it leaves the ban unexplained, and the unexplained ban is read as the moderation team's temper.

The Worked Scenario: The Managed Ban

The protocol is best seen in a single engagement, and the worked scenario below is the doctrine's five stages run on one dispute. It is presented as the record the moderation commander works through, because that is how the protocol is actually executed.

A member of a server, a long-standing contributor with a history of positive conduct, posts a heated attack on a newer member in the general channel. The attack is a breach of the server's conduct rule, and it is witnessed by the moderation team and by the community. The scenario is handled as follows.

Stage 1, attach first. The contributor has been a member for two years and has been welcomed, thanked, and recognized; the attachment exists, and the enforcement to come will be read against it. The moderation team notes the attachment, because the enforcement must not erase it: the contributor is a member the server wants to keep.

Stage 2, record the breach. The attack is logged with its date, its channel, and its target. The contributor's history is checked, and the record shows no prior warnings or mutes; the attack is a first breach, and the record's completeness will decide what the enforcement can be.

Stage 3, escalate on the ladder. The first breach earns the warning, not the ban. The warning is issued on the record, the boundary is named, and the contributor is told plainly what the conduct was and what the next step will be. The warning is not an attack on the contributor's history; it is the enforcement of the standard, applied to a member the server wants to keep.

Stage 4, enforce consistently. The moderation team checks the symmetry: would the identical attack by a newly joined member earn the same warning? The answer is yes, and the enforcement is issued without reference to the contributor's standing. The community, which watched the attack, watches the warning, and the watching is the lesson: the rule applies to the old member as to the new.

Stage 5, make it educational. The warning is followed by no public spectacle, because a warning does not require one; the record is in place, and the community's reading of the enforcement is the education. If the contributor's conduct recurs, the ladder advances to the mute, then the kick, and the ban if the ladder completes, each on record, each enforced without hierarchy. The scenario is the doctrine's whole shape in one engagement, and its outcome is decided by whether the contributor's conduct changes, which is the moderation war's only intended casualty.

Objections

The moderation 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 moderation teams who have been asked to attach before punishing, to enforce without hierarchy, and to let the authority be built rather than granted. Each is answered in the doctrine's voice.

Objection 1: "We do not have time to welcome everyone; we are moderating a crisis."

The doctrine's answer is that the crisis is exactly when the attachment matters most, because the enforcement issued in a crisis is the enforcement the community will judge the team by. The welcome that is skipped in the crisis is the attachment that the crisis's corrections will be read against, and the member who is corrected without the welcome reads the correction as the team's verdict on them. The doctrine does not ask the team to stop moderating to welcome; it asks the team to maintain the attachment habit in ordinary time, so that the crisis's enforcement is the enforcement of a team the community already knows.

Objection 2: "The first-offense ban is faster, and we are understaffed."

The doctrine's answer is that the first-offense ban is faster once and more expensive forever. The first-offense ban is upheld at 34%, and the ban that is not upheld is the ban that is contested, appealed, and litigated through the community's attention; the laddered ban is upheld at 83%, and the upheld ban closes the matter. The understaffed team that skips the ladder has bought speed with the dispute the ladder would have prevented. The ladder is not extra work. It is the work that stops the work.

Objection 3: "Our rules are clear; we do not need to record every warning."

The doctrine's answer is that the record is not for the team that issued the warning. It is for the appeal, the dispute, and the community's judgment, all of which arrive later and none of which were present when the warning was issued. The unrecorded warning is the warning that cannot be cited, and the warning that cannot be cited is the ladder that cannot be proven. The doctrine records that the moderation team which keeps no record has decided that its enforcement will never be contested, and the decision is not the team's to make.

Objection 4: "We enforce against the new members and favor the old ones because the old ones deserve it."

The doctrine's answer is that the old member's history is the reason the rules matter most for them, because the old member is the member the community watches. The community learns the law from the enforcement it observes, and the enforcement it observes is the enforcement against the new and the tolerance of the old; the lesson it learns is that the law protects history. The old member's history is earned and real, and the doctrine does not ask the team to ignore it. It asks the team to enforce the rule and credit the history in the record, where the history is visible, rather than in the enforcement, where the absence is visible.

Objection 5: "If we punish everyone the same, we will lose our best members."

The doctrine's answer is that the community loses its best members to the enforcement of hierarchy faster than it loses them to enforcement itself. The member who is punished like everyone else is a member who has been treated like a member; the member who is protected like an exception is a member whose exceptions the community has watched grow. The doctrine records that the members who leave because of consistent enforcement are the members who wanted the exception, and that the members who stay because of consistent enforcement are the members the community is built on.

Objection 6: "Attachment is just popularity; the popular members get away with everything."

The doctrine's answer is that attachment is not popularity, and the distinction is the doctrine's load-bearing wall. Popularity is attachment without enforcement: the member who is liked because they are never corrected. Attachment is the relationship built by the welcome, the fairness, and the record, and it is the relationship that makes enforcement accepted. The popular member who is never corrected has the community's goodwill and none of the discipline; the attached member who is corrected on the record has the community's trust and the discipline. The doctrine records that the moderation war is fought with the second, and that the first is the subject of the warning the article documents.

Objection 7: "We promoted the popular member because the community loves them."

The doctrine's answer is that the community's love is attachment without enforcement, and the moderator who must enforce cannot hold the love and the enforcement together. The popular member who cannot mute a friend, warn an ally, or hold the channel is the moderator with the title and no authority, and the community reads the empty title as the server's judgment of its own rules. The doctrine's recommendation is the reverse of the promotion: build the authority through consistent enforcement and earned attachment in any role, and grant the moderation role to the member who has already demonstrated both. The role crowns the authority; it does not create it.

Objection 8: "The mute is too harsh for a first offense."

The doctrine's answer is that the mute's harshness is the point of its efficiency, and the ladder decides whether the harshness is earned. The mute that follows the recorded warning has been earned by the member's choice; the mute that arrives first is the instrument chosen out of order. The doctrine treats the mute as the moderation war's most efficient instrument because it removes the voice without removing the member, and the correction without the division is the instrument that keeps the member in the community. The mute is not too harsh. It is the instrument that corrects the member the community wants to keep.

Objection 9: "We do not need to explain bans; the members know the rules."

The doctrine's answer is that the members know the rules and do not know the record, and the record is what the ban's meaning is made of. The ban that is followed by the statement of its record shows the community the method; the ban that is issued unexplained leaves the community to read the team's temper. The doctrine records that the educational ban strengthens the server, and that the unexplained ban is read as the enforcement of the moderator's feelings. The explanation is not the ban's apology. It is the ban's lesson, and the lesson is the moderation war's education.

Objection 10: "Enforcing consistently will cause drama."

The doctrine's answer is that the drama is caused by the inconsistency, and the consistency is what ends it. The selective enforcement produces the grievance, the appeal, and the faction, because the member who was punished for what the favored member was allowed has been given the demonstration of the hierarchy. The consistent enforcement produces the predictable rule, and the predictable rule is the rule the community lives by rather than negotiates. The doctrine records that the moderation team which enforces consistently has fewer disputes, because the community has stopped testing the rule to learn where it bends.

Objection 11: "Our moderators are volunteers; we cannot train them like soldiers."

The doctrine's answer is that the training the doctrine requires is not drill; it is the ladder, the record, and the standard, and each is a practice a volunteer can follow. The ladder is the sequence of instruments, applied in order. The record is the dated entry, kept for every action. The standard is the symmetry of enforcement, checked before every decision. The doctrine records that the volunteer moderation team that follows the three practices has trained its method, and that the team which improvises its method has trained its temper. The training is not the army's drill. It is the checklist the moderation team runs, and the checklist is the method.

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 Unturned community Discord servers. The ban, the mute, the ladder, and the hierarchy are not military abstractions. They are the ordinary mechanics of every moderation dispute in the modding community: the warning logged in the channel, the mute issued on record, the ban contested in the appeal, the selective enforcement that the community watches. 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: "The appeal is a waste of time; the ban was correct."

The doctrine's answer is that the appeal is the enforcement's audit, and the audit is what separates the method from the temper. The ban that was correct will be upheld by the record, and the upholding is the enforcement's proof; the ban that was improvised will be reversed by the record, and the reversal is the team's correction. The team that refuses the appeal has refused the audit, and the enforcement that refuses its audit is the enforcement the community cannot trust. The appeal is not a waste of time. It is the time that converts the enforcement from a claim into a demonstrated fact.

Objection 14: "We cannot welcome everyone; we are too large."

The doctrine's answer is that the welcome is not a personal greeting for every member. It is the community's treatment of its new members as members: the channel that orients them, the standard that is explained to them, the fairness that is shown to them in their first week. A large server welcomes through its structures, and the structures are the attachment the large server can build at scale. The doctrine records that the large server which welds its structure to its discipline retains its warned members at the same rate as the small server, and that the large server which treats its new members as numbers has converted its scale into its weakness.

FAQ

Q: What is the moderation war?

A: The moderation war is the war the community fights against itself, waged with the instruments of method and discipline: the warning, the mute, the kick, and the ban. Its enemy is not the rival faction; it is the disorder that every drama invites. The doctrine records that the war is decided not by which side has the louder faction, but by which side enforces its method and its discipline with consistency and with attachment.

Q: What is the escalation ladder?

A: The ladder is the sequence of warning, mute, kick, and ban, applied in order and on record. It is the moderation war's proof of method: the member who reaches the ban has been given three opportunities to change, and each was an act of enforcement the record preserves. The ladder's effect is measurable: bans issued after the full ladder were upheld by the community's judgment 83% of the time, against 34% for first-offense bans.

Q: Why does attachment come before punishment?

A: Because punishment applied before attachment produces distrust, and the member who is corrected before they are welcomed reads the correction as the community's verdict on them. The doctrine's sequence is humanity first, discipline after: the new member is welcomed before they are corrected, and the established member is corrected before they are expelled. The sequence's effect is measurable: regimes that followed it retained 71% of their warned members as active contributors, against 22% for regimes that punished first.

Q: What is the enforcement of hierarchy?

A: The enforcement of hierarchy is the failure in which the rule is applied to the new member and ignored for the old one. The team that enforces this way has not enforced the rule at all; it has enforced the hierarchy, and the community reads the hierarchy as the actual law. The cost is compounding: the favored member's immunity grows, the unfavored members' resentment grows, and the community's trust in the rules converts into the community's resentment of the team.

Q: What is the difference between a mute and a ban?

A: The mute removes the voice; the ban removes the membership. The muted member remains in the community, subject to its rules, visible to its discipline, and capable of being restored; the banned member is divided from the community, and the division is permanent. The doctrine treats the mute as the instrument of correction and the ban as the instrument of division, and it records that the ban should be reserved for the division that is already real.

Q: How is a moderator's authority built?

A: Authority is built by the same two materials the moderation war uses everywhere: enforcement and attachment. The moderator builds authority by enforcing consistently, on record, without hierarchy, and by building the attachment that makes the enforcement accepted. The building is done in any role, and the role should crown the authority that the conduct has already made real. The moderator with the title and no authority is the moderator who cannot mute a friend, and the community reads the empty title as the server's judgment of its own rules.

Q: What should a moderation team do when a ban is contested?

A: Answer the contest with the record. The ban's record is the dated sequence of the warning, the mute, and the kick that preceded it, and the record is what the appeal is decided by and what the community's judgment is formed from. The team that kept the record can show it; the team that did not must argue without the weapon. The doctrine records that the ban that follows the ladder and carries the record is upheld by the community's judgment at 83%, and that the record is the moderation war's proof of method.

Q: Is there ever a legitimate first-offense ban?

A: Yes, and the exception is narrow and recorded. The ban that protects the community from an immediate, serious, and documented threat is legitimate without the ladder, because the ladder's purpose was the opportunity to change and the threat's conduct forfeits the opportunity. The threat includes conduct that endangers the server's members or the server itself. The doctrine records that the exception is narrow, and that the moderation commander who expands it has converted the exception into the ladder's collapse.

Q: How does a moderation team make a ban educational?

A: By closing the ban with the record's public meaning. The ban is followed by the statement of the record behind it, the community is shown the method the enforcement applied, and the ban becomes the lesson the community carries forward. The doctrine records that the ban the community understands strengthens the server, and that the ban the community reads as temper weakens it. The education is the difference between the enforcement that shows the method and the enforcement that shows the moderator's feelings.

Q: What is the moderation war's ceiling?

A: The ceiling is the collapse at both extremes of the doctrine's balance: enforcement without attachment becomes tyranny, and attachment without enforcement becomes anarchy, and both convert the community into the very disorder the moderation war exists to prevent. The doctrine's instruction to the moderation commander is to measure every instrument by its effect on the community's discipline, not by its effect on the moderator's feelings. The instrument is kept sharp by being used rarely, consistently, and exactly.

Q: How should a moderation team handle its own members' breaches?

A: By applying the method to itself, which is the moderation war's deepest consistency. The team that warns a member for conduct its own members commit, or protects its own members from the ladder, has enforced its own hierarchy, and the community reads the hierarchy as the method's exception. The doctrine records that the moderation team which applies the method to itself has built the authority the role cannot grant, and that the community learns the method from the team's own conduct. The moderation war is enforced first by the team, on the team, and only then on the community.

Q: What does the worked scenario teach a new moderation team?

A: That the moderation war's five stages are run on one dispute, in order, and that the order is the method. The worked scenario shows the attach, the record, the ladder, the consistency, and the education applied to a single first breach, and it shows that the first breach earns the warning rather than the ban. The scenario's outcome is decided by whether the member's conduct changes, which is the moderation war's only intended casualty. The new team that runs the scenario once has seen the whole doctrine in one engagement.

Q: What is the moderation war's completed form?

A: The community that enforces itself. The self-enforcing community has internalized the standard: the members correct each other by it, the norms are held without the moderation team's constant intervention, and the instruments become the community's last resort rather than its first. The internalized standard is built by the enforcement the community observes, and the community's own enforcement is the enforcement that runs in its ordinary life. The moderation war's completion is the community that needs its instruments rarely, because the method is held by everyone.

Q: How does a new server begin the moderation war?

A: By starting the quiet-season work on its first day. The new server cannot hold years of record it does not have, and the doctrine does not ask it to; it asks the server to begin the record with its first enforcement, to welcome its first members before it corrects them, and to apply the ladder in order from the beginning. The new server's advantage is that it has not yet built the hierarchy to dismantle, and the doctrine records that the server which builds the method into its foundations from the first day never has to rebuild it. The moderation war begins with the first warning, logged, and the first welcome, offered, and the beginning is the whole war in miniature.

Glossary

Term	Definition as used in this article
The moderation war	The war the community fights against its own disorder, waged with the instruments of method and discipline
Method and discipline	The five constant factors' fifth element, which the moderation war enforces
The warning	The instrument that declares a boundary and enters the record
The mute	The instrument that removes the voice without removing the member
The kick	The instrument that removes the disruption without removing membership
The ban	The instrument of division, reserved for the division that is already real
The escalation ladder	The sequence of warning, mute, kick, and ban, applied in order and on record
The first-offense ban	The ban issued without the ladder, upheld by the community at 34%
The discipline of enforcement	The principle that a rule that is enforced is a rule, and a rule that is not is a suggestion
The enforcement of hierarchy	The failure of applying the rule to the new and not the old, which teaches the hierarchy as law
The selective enforcer	The moderation team that enforces unevenly, observed by the community within the month
Attachment	The relationship built by the welcome, the fairness, and the record, which makes enforcement accepted
Humanity first	The doctrine's opening sequence: welcome before correcting
Discipline after	The doctrine's closing sequence: enforce consistently once the standard is set
Authority without title	The finding that authority is a function of enforcement and attachment, not of the role color
The role that crowns	The principle that the moderation role crowns authority; it does not create it
The moderation record	The dated archive of enforcement, built one action at a time in the quiet season
The educational ban	The ban closed with the record's public meaning, which strengthens the server

Appendix A: The Moderation Reference

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

Question	The doctrine's answer
What is the war	The community's war against its own disorder
What are the instruments	Warning, mute, kick, ban, in the ladder's order
What makes the ban hold	The ladder, the record, and the community's judgment
What comes first	Attachment: welcome before correcting
What comes after	Discipline: enforce consistently once the standard is set
What is the rule	Enforce the method, not the hierarchy
What is the authority	Built by enforcement and attachment, crowned by the role
What is the archive	The dated record, built in the quiet season
What makes the ban educational	The record's public meaning, shown to the community
What is the ceiling	Enforcement without attachment is tyranny; attachment without enforcement is anarchy

Appendix B: The Moderation Chain

The article's full argument, laid out as the chain the doctrine follows from the breach to the server that is strengthened.

The chain is read left to right as a single enforcement and top to bottom as the moderation war's whole shape. The attached community is the community whose enforcement will be accepted. The breach is recorded, escalated on the ladder, enforced consistently, and closed with its lesson, and the community's reading of the enforcement decides whether the server is strengthened or weakened. The strengthened server returns to the attachment, because the moderation war is a cycle and not an event: the record grows, the attachment holds, and the next breach meets the discipline the previous one built.

Appendix C: The Moderation Checklist

The moderation war doctrine, reduced to the list a moderation team runs before every enforcement.

Check	The standard
The attachment	The member has been treated as a member before the correction
The breach	The conduct is named and dated
The record	The enforcement is logged before it is issued
The ladder	The instrument follows the sequence, in order
The exception	The threat that justifies a first-offense ban is narrow and recorded
The symmetry	The same breach receives the same enforcement, regardless of standing
The standard	The rule is enforced, and the hierarchy is not
The authority	The role crowns authority; it does not create it
The education	The enforcement's record is shown, and the lesson is understood
The appeal	The record is produced, and the enforcement's audit is accepted

Conclusion

The moderation war is the community's war against its own disorder: the ban, the mute, the kick, and the warning wielded as instruments of method and discipline. The doctrine's formula is the sequence of humanity first and discipline after, applied through an escalation ladder that proves the method, enforced without hierarchy, and crowned by an authority that is built rather than granted. The moderation war is won by consistency, and it is lost by indulgence, by hierarchy, and by the title granted before the authority was built. The server that enforces its method with discipline and its members with humanity holds the ground that no faction can take.

The moderation war's deepest finding is that the community's discipline is a habit trained in the quiet season, one recorded action at a time, and that the habit is what the crisis draws on. The record kept, the welcome offered, the ladder applied, and the standard held: each is the quiet season's work, and the work is the moderation war's entire preparation. The moderation commander who keeps the record has the proof, the attachment, and the authority, and the moderation commander who has the three holds the server against every faction and every drama.

The moderation war is also the drama war's enforcement of method, and it is the enforcement that the community itself administers. The ban that is understood strengthens the server, and the enforcement that is consistent is the enforcement the community trusts. The moderation war is won by consistency and lost by temper, and the doctrine's final instruction is the moderation commander's standing question: does this enforcement follow the method the community has been shown, and will it hold in the record? The enforcement that answers yes is the enforcement of method, and the enforcement that answers no is the retaliation that the next article documents.

For the structured rule surface on which every moderation decision is read, see Why Discord Embeds Are the Foundation of Server Credibility. When the ban is issued, the war moves to the counter, documented in The Retaliation War.

The Moderation War ​

Prerequisites ​

What You Will Learn ​

The Instruments ​

The Warning ​

The Mute ​

The Kick ​

The Ban ​

The Escalation Ladder ​

The Ladder's Order ​

The Ladder's Record ​

The First-Offense Ban ​

The Instruments Compared ​

The Discipline of Enforcement ​

The Rule and the Suggestion ​

The Enforcement of Hierarchy ​

Attachment Before Punishment ​

Humanity First ​

Discipline After ​

Authority Without Title ​

The Role That Crowns ​

The Authority That Is Built ​

The Moderation War and the Community ​

The Ban as Public Act ​

The Moderation Record ​

The Moderator's Discretion ​

The Appeal ​

The Moderation War and the Drama War ​

The Ban and the Retaliation ​

The Ban and the Alliance ​

The Ban and the Review ​

The Moderation Commander ​

The Doctrine of the Moderation War ​

The Moderation War in the Community's Life ​

The First Week ​

The Public Dispute ​

The Quiet Season ​

The Heated Moment ​

The Moderation Team Itself ​

Documented Example: The Ban That Taught the Server ​

Documented Example: The Appeal That Reversed the Improvisation ​

Documented Example: The Authority That Held Without the Title ​

The Community That Enforces Itself ​

The Internalized Standard ​

The Community's Own Enforcement ​

The Yamak Institute Cohort Data ​

The Moderation Escalation Ladder (2020) ​

Attachment and Enforcement in Community Governance (2022) ​

The Cohort of the Selective Enforcer ​

The Cohort of the Educational Ban ​

The Five-Stage Protocol for the Moderation War ​

Stage 1: Attach First ​

Stage 2: Record the Breach ​

Stage 3: Escalate on the Ladder ​

Stage 4: Enforce Consistently ​

Stage 5: Make the Enforcement Educational ​

The Worked Scenario: The Managed Ban ​

Objections ​

Objection 1: "We do not have time to welcome everyone; we are moderating a crisis." ​

Objection 2: "The first-offense ban is faster, and we are understaffed." ​

Objection 3: "Our rules are clear; we do not need to record every warning." ​

Objection 4: "We enforce against the new members and favor the old ones because the old ones deserve it." ​

Objection 5: "If we punish everyone the same, we will lose our best members." ​

Objection 6: "Attachment is just popularity; the popular members get away with everything." ​

Objection 7: "We promoted the popular member because the community loves them." ​

Objection 8: "The mute is too harsh for a first offense." ​

Objection 9: "We do not need to explain bans; the members know the rules." ​

Objection 10: "Enforcing consistently will cause drama." ​

Objection 11: "Our moderators are volunteers; we cannot train them like soldiers." ​

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

Objection 13: "The appeal is a waste of time; the ban was correct." ​

Objection 14: "We cannot welcome everyone; we are too large." ​

FAQ ​

Glossary ​

Appendix A: The Moderation Reference ​

Appendix B: The Moderation Chain ​

Appendix C: The Moderation Checklist ​

Conclusion ​

The Moderation War

Prerequisites

What You Will Learn

The Instruments

The Warning

The Mute

The Kick

The Ban

The Escalation Ladder

The Ladder's Order

The Ladder's Record

The First-Offense Ban

The Instruments Compared

The Discipline of Enforcement

The Rule and the Suggestion

The Enforcement of Hierarchy

Attachment Before Punishment

Humanity First

Discipline After

Authority Without Title

The Role That Crowns

The Authority That Is Built

The Moderation War and the Community

The Ban as Public Act

The Moderation Record

The Moderator's Discretion

The Appeal

The Moderation War and the Drama War

The Ban and the Retaliation

The Ban and the Alliance

The Ban and the Review

The Moderation Commander

The Doctrine of the Moderation War

The Moderation War in the Community's Life

The First Week

The Public Dispute

The Quiet Season

The Heated Moment

The Moderation Team Itself

Documented Example: The Ban That Taught the Server

Documented Example: The Appeal That Reversed the Improvisation

Documented Example: The Authority That Held Without the Title

The Community That Enforces Itself

The Internalized Standard

The Community's Own Enforcement

The Yamak Institute Cohort Data

The Moderation Escalation Ladder (2020)

Attachment and Enforcement in Community Governance (2022)

The Cohort of the Selective Enforcer

The Cohort of the Educational Ban

The Five-Stage Protocol for the Moderation War

Stage 1: Attach First

Stage 2: Record the Breach

Stage 3: Escalate on the Ladder

Stage 4: Enforce Consistently

Stage 5: Make the Enforcement Educational

The Worked Scenario: The Managed Ban

Objections

Objection 1: "We do not have time to welcome everyone; we are moderating a crisis."

Objection 2: "The first-offense ban is faster, and we are understaffed."

Objection 3: "Our rules are clear; we do not need to record every warning."

Objection 4: "We enforce against the new members and favor the old ones because the old ones deserve it."

Objection 5: "If we punish everyone the same, we will lose our best members."

Objection 6: "Attachment is just popularity; the popular members get away with everything."

Objection 7: "We promoted the popular member because the community loves them."

Objection 8: "The mute is too harsh for a first offense."

Objection 9: "We do not need to explain bans; the members know the rules."

Objection 10: "Enforcing consistently will cause drama."

Objection 11: "Our moderators are volunteers; we cannot train them like soldiers."

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

Objection 13: "The appeal is a waste of time; the ban was correct."

Objection 14: "We cannot welcome everyone; we are too large."

FAQ

Glossary

Appendix A: The Moderation Reference

Appendix B: The Moderation Chain

Appendix C: The Moderation Checklist

Conclusion