Moderator guide: Difference between revisions
Import>Ardakaz Created page with "This guide helps moderators to do their job. As a mod, you are responsible for making sure the server rules are followed. You are also expected to guide new players and be helpful and friendly in general. And always, please '''assume good faith'''. Most people want to be nice. == Commands == === Inspecting & repairing === * <code>/co inspect</code> - View logs about specific block. ** Left click = the block you're looking at ** Right click = the block next to it (..." |
Import>Ardakaz Rewriting :D |
||
| Line 3: | Line 3: | ||
As a mod, you are responsible for making sure the server [[rules]] are followed. You are also expected to guide new players and be helpful and friendly in general. And always, please '''assume good faith'''. Most people want to be nice. | As a mod, you are responsible for making sure the server [[rules]] are followed. You are also expected to guide new players and be helpful and friendly in general. And always, please '''assume good faith'''. Most people want to be nice. | ||
== | == Checking grief alerts == | ||
If you want to hide yourself before checking, do <code>/vanish</code>. That makes you invisible and allows flying. | |||
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. | |||
<code>/tpo <player></code> can be also used for teleport. | |||
<code> | == Advanced lookup & rollbacks == | ||
You can also view the logs using <code>/co lookup <params></code> | |||
{| class="wikitable" | |||
|+Lookup parameters | |||
!Parameter | |||
!Description | |||
!Example | |||
!Required | |||
|- | |||
|User (u) | |||
|Player | |||
|Ardakaz | |||
|Yes | |||
|- | |||
|Time (t) | |||
|Time range | |||
|10h | |||
|Yes | |||
|- | |||
|Radius (r) | |||
|Block range | |||
|20 | |||
|No (defaults to 10) | |||
|- | |||
|Action (a) | |||
|Action type | |||
|container | |||
|No | |||
|- | |||
|Block (b) | |||
|Block/item type | |||
|diamond_ore | |||
|No | |||
|} | |||
The rollback command is <code>/co rollback <params></code>. The parameters are same as above. | |||
== | == Other useful tools == | ||
=== Invsee === | |||
Stolen items can be removed or checked with <code>/invsee <player></code> or <code>/endersee <player></code> (enderchest). If a rollback is already done, those items can be removed with <code>/disposal</code>. | |||
=== 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. | |||
After they answer you can use <code>/jail <player></code> to unjail. | |||
== Punishing rule breakers == | |||
For minor infractions, you can use <code>/warn <player> <reason></code> to make a note for staff about that player. (<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. | |||
=== 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. | |||
[[Category:Guides]] | [[Category:Guides]] | ||
Revision as of 11:53, 31 December 2024
This guide helps moderators to do their job.
As a mod, you are responsible for making sure the server rules are followed. You are also expected to guide new players and be helpful and friendly in general. And always, please assume good faith. Most people want to be nice.
Checking grief alerts
If you want to hide yourself before checking, do /vanish. That makes you invisible and allows flying.
When you see an unclear alert use /co teleport <x> <y> <z> to teleport there. Then use /co inspect 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 /co-back to return.
/tpo <player> can be also used for teleport.
Advanced lookup & rollbacks
You can also view the logs using /co lookup <params>
| Parameter | Description | Example | Required |
|---|---|---|---|
| User (u) | Player | Ardakaz | Yes |
| Time (t) | Time range | 10h | Yes |
| Radius (r) | Block range | 20 | No (defaults to 10) |
| Action (a) | Action type | container | No |
| Block (b) | Block/item type | diamond_ore | No |
The rollback command is /co rollback <params>. The parameters are same as above.
Other useful tools
Invsee
Stolen items can be removed or checked with /invsee <player> or /endersee <player> (enderchest). If a rollback is already done, those items can be removed with /disposal.
Interrogation room
If someone doesn't answer when you ask about grief, you can use /jail <player> <jail> to prevent them for playing before they answer.
After they answer you can use /jail <player> to unjail.
Punishing rule breakers
For minor infractions, you can use /warn <player> <reason> to make a note for staff about that player. (/warnings <player> can be used to see them)
If the player continues rule breaking or does major grief, you can use /ban <player> <reason> to ban them.
Ban evaders
You can use /alts <player> 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 /banip <player> <reason> to ban all players from that address.