3-Step Procedure for Enforcing the Server Sules.

Step 1: State the boundary (once).

Short. Factual. No debate.

"Public chat must stay appropriate. Stop."

No explanations. No history lesson. One sentence.

It is appropriate to use the /warn command at this step

Staff should never repeat Step 1 more than once.

Repetition trains players to treat warnings as gameplay.

Step 2: State the consequence (once).

Only if the behavior continues.

"If this continues, there will be consequences."

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:

"The rules are clear, they were already explained, and this is not open for debate."

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
TOP Updated 2026-06-22 15:19:41