Moderator Induction
Welcome to the staff team! This induction will what is expected of you, what tools you have, and how to use them properly.
Staff permissions
Permissions is commonly referred to as "perms".
Trial Moderator:
- /grim alerts
- /ban
- /banlist
- /kick
- Access to discord staff channels
Moderator:
All of the above, and:
- /grim spectate
- /view
- /ledger
- /gamemode
- /pardon (not /unban, /pardon !!!)
- Access to open tickets
Senior Moderator:
All of the above, and:
- /tp
Manager:
All of the above, and:
- Limited console access
Admin:
All of the above, and:
- Complete console access
Commands
/view
Use to view and edit a player's inventory or echest. They can also be offline.
Command usage:
/view (inv/echest) <player>
Example:
/view echest RPiCPU will show you RPiCPU's echest. You will be able to move items around, and add items or remove them.
/ban
Used to ban someone. Read #Banning for an in-detail guide on using it.
Command usage:
/ban <player> [reason]
Example:
/ban RPiCPU being naughty - permanent ban will ban RPiCPU with the reason "being naughty - permanent ban".
/pardon
Used to unban someone.
Command usage:
/pardon <player>
Example:
/pardon RPiCPU will unban RPiCPU.
/ledger
Used for investigating grief and rolling back grief.
Full guide (strongly recommended): Help:Moderator_tutorial_to_ledger
/grim
Grim is our anticheat, which flags potentially cheating players.
Full guide (also strongly recommended): #Anticheat
Anticheat
Under construction.
Banning
Firstly, read the rules to double check what the player did was wrong.
Secondly, you must have valid video or picture proof that they were breaking the rules.
If both of the above are true, post the proof in #logs in the discord. If you can't find it, it is in the STAFF category, under #tickets.
Then, ban them by running /ban {player username} {reason}
You MUST include a reason! It should include what the player did to get banned, and if its permanent or temporary. If it is temporary, you must state the length of the ban, and the unban date.
Check Help:Ban_lengths on info for how long to ban someone.
Console
Managers and above have access to the console.
The console is rarely used for player issues. It should only be used for when the server has crashed or has a server-side issue.
- this is under construction, in the meanwhile DM me (blue lightning/rpicpu) on discord for instructions -
Code of Conduct
All staff must follow the Staff Code of Conduct at all times.
Discord channels
Staff are expected to monitor and use the Discord often, or else you might be demoted due to inactivity.
The "STAFF" category is below the #tickets channel.
Here is a full list of channels and their uses:
- #staff - Important staff announcements. You should check this on a regular basis.
- #logs - Use to log reason and evidence of banning players.
- #general - Staff general chat.
- #alerts - General staff alerts, e.g. members editing or deleting a message, a ticket staff alert, a user asking to verify
- #spam - Anything really
- #modlog - When you use your permissions, e.g. using creative, you must log the actions you took here
Log warnings
When warning someone, post a message in #logs with a reason for the warn, and evidence if applicable.
Log bans
When banning someone, post a message in #logs with a reason for the ban, evidence and the length of the ban.
Handling tickets
Follow this process:
- Be professional
- Ask what the issue is
- Ask for relevant details
- Ask for witnesses and ping them to add them to the ticket
- If someone is being blamed, ping them and ask for their point of view and reason/excuse
- Review evidence calmly
- Decide based on facts, not opinions
If a ticket seems to be resolved/is inactive, ping the ticket owner and ask them whether you can close it.