Jump to content

Moderator guide: Difference between revisions

m outdated
clarifications on muting
 
(9 intermediate revisions by 2 users not shown)
Line 4: Line 4:


== Checking grief alerts ==
== Checking grief alerts ==
If you want to hide yourself before checking, do <code>/vanish</code>. That makes you invisible and allows flying.
If you want to hide yourself before checking, do <code>/vanish on</code> and take your armor off. That makes you invisible and allows flying. Use <code>/vanish off</code> to disable it.


When you see an unclear alert use <code>/co teleport <x> <y> <z></code> to teleport there. Then use <code>/co inspect</code> to check it (left click tells about the block you're looking at and right-click tells about the block next to it or container transactions). Finally, use <code>/co-back</code> to return.
When you see an unclear alert use <code>/co teleport <x> <y> <z></code> to teleport there. Then use <code>/co inspect</code> to check it (left click tells about the block you're looking at and right-click tells about the block next to it or container transactions).


<code>/tpo <player></code> can be also used for teleport.
<code>/tpo <player></code> can be also used for teleport.
Line 52: Line 52:


=== Interrogation room ===
=== Interrogation room ===
If someone doesn't answer when you ask about grief, you can use <code>/jail <player> <jail></code> to prevent them for playing before they answer.
If someone doesn't answer when you ask about grief, you can use <code>/jail <player> <jail></code> to prevent them for playing before they answer. Always follow the player to the interrogation room, '''do not leave them alone'''.


After they answer you can use <code>/jail <player></code> to unjail.
After they answer you should use <code>/jail <player></code> to remove them from the room. '''Never leave people in the interrogation room even if you ban them'''. The interrogation room must be always empty when moderators are not online.


== Punishing rule breakers ==
== Dealing with rule breakers ==
For minor infractions, you can use <code>/warn <player> <reason></code> (<code>/warnings <player></code> can be used to see them).
 
For minor infractions, talk to the player and make sure they understand the rules. Use <code>/note <player> <reason></code> to record what happened.
 
If the player is not online, do the rollbacks and give a warning with <code>/warn <player> <reason></code> (<code>/warnings <player></code> can be used to see them).


If the player continues rule breaking or does major grief, you can use <code>/ban <player> <reason></code> to ban them.
If the player continues rule breaking or does major grief, you can use <code>/ban <player> <reason></code> to ban them.
Tempbans <code>/tempban <player> <reason></code> can be used when a permban is not warranted (eg. minor but repeated issues) but the player is not trusted to follow the rules without some consequences. 
=== Reasons for a permanent ban ===
* The player has no intention of following the rules (either they say so or repeatedly ignore warnings)
* Mass griefing and stealing
* Lavacasts
* Malicious spamming
* Intentional offensive language (slurs etc)
* Failure to take responsibility for their actions
* Harassing other players in a creepy or dangerous way
=== Reasons for a temporary ban ===
* The player probably didn't read the rules and is likely to learn with a short timeout
* The grief is small and probably not malicious but annoying and repeated
* A regular trusted player causes trouble in a way that normally might be grounds for a permanent ban, and is genuinely sorry


=== Ban evaders ===
=== Ban evaders ===
You can use <code>/alts <player></code> to check if players are logged from a same IP. Then you can see if someone is ban evading that way. If that continues, use <code>/banip <player> <reason></code> to ban all players from that address.
You can use <code>/alts <player></code> to check if players are logged from a same IP. Then you can see if someone is ban evading that way. If that continues, use <code>/banip <player> <reason></code> to ban all players from that address.
When banning someone for ban evasion, always put <code>Ban evasion of <player></code> as the reason. The reason of IP bans must always be <code>Ban evasion</code>.
=== Building trust ===
Generally we let people play if we can '''trust them and they take responsibility''' for their actions. This is judged by the moderators, within the team if needed.
== Chat moderation policy ==
* Racial slurs, praising genocide etc. always warrant a permban
* NSFW: Not tolerated
* Cursing at the game is ok (if not excessive), cursing at other players should be moderated
* Don’t let casual sexism or prejudices against minorities slide. ”Not cool” is often a good phrase to use to make a point.
* Spamming can be the same stuff over and over or repetitive images or random stuff ingame from discord
* If a request to stop the bad behavior in chat is not heeded, use <code>/mute</code> ingame or a timeout on discord. Short times to simply stop the player, longer times for bigger offences.
== Checking the alert list ==
The following symbols are used to mark alerts on Discord. Moderators should regularly check and mark the list to avoid backlog piling up.
* ✅ Checked and complete. No need to scroll up any further. Use when everything above has been cleared.
* ❗ Use when something is clearly against the rules but you can’t fix ingame right now.
* ❓ Use when something is probably against the rules but you can’t check ingame right now.
* 🔄 Use when rollback has been done, warnings/bans given and issue solved.
* ☑️ May be used on something that has been confirmed no problem but all issues above have not been solved.
To set certain locations (like public chests) to ignored: <code>/griefalert ignore x y z</code>
== Other instructions ==
* Alerts don't always show when people put items back so '''never moderate grief from Discord'''.
* It's recommended to use vanish while checking any grief. It keeps you safe and doesn't disturb people.
* '''Always include the reason while banning someone!’''
* Player reports (<code>/report</code>) are sent to discord, but should also be closed ingame with <code>/reports list</code> (to see them) and <code>/reports close</code> (to resolve).
== Moderation examples ==
* A griefer steals diamonds from someone's chest.
<Moderator> Hey Griefer, have you read the rules? You stole diamonds from someone's chest.
* The griefer doesn't answer.
<Moderator> Griefer? Did you see my question? You can't steal here.
* The griefer doesn't answer. The moderator teleports them to the interrogation room.
<Moderator> Could you answer to my question? Stealing is not allowed.
<Griefer> Sorry, I don't know the rules.
<Moderator> Please use /rules to read them. We don't allow stealing here.
<Griefer> I'm sorry. I'll not steal again.
<Moderator> Good :)
<Moderator> Can you return the diamonds?
<Griefer> Ok
* The moderator lets the griefer out from the interrogation room. The griefer returns the diamonds.
<Moderator> Thanks
* The moderator makes a note about the griefer.
* A griefer is making a lavacast over spawn.
<Moderator> Hey Griefer! Have you read the rules? This is not an anarchy server.
<Griefer> Fuck you. I want to grief.
<Moderator> You have come to the wrong server then. Bye!
Griefer was hit with the banhammer! (Grief: Making a lavacast.)
[[Category:Guides]]
[[Category:Guides]]
[[Category:Staff_documents]]
[[Category:Staff_documents]]