Procedure for Enforcing the Server Rules.
Boundary→consequence→action→disengage.
Step 0: Identify the rule.
Before intervening as staff, know what behaviour you're addressing and why staff intervention is necessary.
If you're uncertain whether something violates a rule, ask another staff member.
Unless immediate action is necessary to prevent harm or disruption, uncertainty is a reason to investigate rather than enforce.
Good judgment includes stopping and questioning your own interpretation before exercising authority.
Step 1: State the boundary (once).
Short. Factual. No debate.
"Public chat must stay appropriate. Stop."
No explanations. No history lesson. One sentence.
A verbal instruction is usually sufficient at this step. Use
/warnwhen the violation warrants being formally recorded, or when an ordinary instruction has already failed.
Staff should never repeat Step 1 more than once.
Step 2: State the consequence (once).
Only if the behavior continues.
This is not a conversation, this is not a threat; it's a notification of a closing bracket.
If players try to drag staff into explanations, excuses, or justifications, use this verbatim:
That sentence does three things simultaneously:
- Asserts clarity
- Asserts finality
- Removes the social oxygen from the conflict
If they keep arguing after that, you skip straight to action.
Step 3: Act, then disengage.
Mute, kick, revoke privs; whatever may be necessary. For Guardians, issue /report PlayerName ....
Never explain enforcement while enforcing.
Explanations come before problems (rules) or after emotions cool (appeals), never during.
Silence after action is part of the consequence.
No public autopsy or follow-up discussion in public chat.
No moralizing or justification after the fact.
You have accomplished your responsibility, normal chat resumes as if nothing happened.
Good-faith players self-correct at Step 1 Border-pushers reveal themselves at Step 2 Bad-faith actors remove themselves at Step 3