Skip to main content

Resolve a disagreement between your Rust moderation leads

Keep one decision in force while you resolve the disagreement. Name the person who owns that decision and give the other lead a private place to explain what they see differently.

Keep the immediate duty separate from the policy question

Say Mat wants to permanently ban a player from Amber Bay after repeated event disruptions. Iona thinks the last warning never reached the player and wants a temporary action while they review. Players are waiting at the event gate. The owner assigns Iona the event response under the existing rules and schedules a separate private review of any ongoing restriction.

Have both describe the case using the same facts. Ask which part they agree on and which missing fact would change the response. Keep player replies with the named reviewer so two staff messages cannot give two outcomes.

Hear the leads before writing a wider rule

Iona reads the warning record and Mat describes prior incidents. They find that the rule says ‘after a warning’ but does not say how the warning reaches the player. The owner asks what evidence of delivery they can realistically check. They agree the event lead can end immediate disruption and the reviewer can consider a longer restriction once the documented warning is confirmed.

In the staff note, replace the vague instruction with the agreed action, who has it and the boundary between event response and case review. If the wider lead remit was part of the conflict, record who can decide it during the owner's absence.

Read the agreement back on a different case

Give Mat and Iona a new example with a clear warning and an event about to start. Each should identify the immediate event owner, the later restriction reviewer and who communicates the result. Revisit the staff note if they still give the player two possible answers. After the test, tell the team what changed without airing the original argument.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details