🛡️ Moderator Guidelines

Moderator Rules & Guidelines

[!IMPORTANT]
Do not give to players who are not staff.

First of all, Congratulations! You have made the next big step to becoming staff - and these are the guidelines you will be using throughout TrialMod and Mod. There are several more responsibilities that come along with being higher among the staff ranks - one of the big ones is being able to ban. These guidelines will highlight important rules that come along with being a Trial-Mod & above, the appropriate punishment as you are able to handle a significantly larger amount of issues, and the new commands you have access to!

Core Rules

No Alternate Accounts: Mods are not permitted to use an alt.
Abuse Gating: Abuse is not tolerated under any circumstances.
No Raiding Staff Targets: If you tp to someone to resolve an issue (if no admins are online to do so), you are NOT allowed to raid them. Take nothing with you, and if killed report to higher staff.

Note that these are suggested punishments and you do not have to follow them verbatim, just don’t go wild. You are a TrialMod+ at this point so you should know the best course of action. Don’t be afraid to judge situations on their severity and hand out punishments accordingly.

Rules & Handling Your New Powers

How to handle and act towards friends breaking rules:

Don’t let your friends control your staff actions, and always avoid being biased. Favouritism is not taken lightly; if you feel as if you can’t appropriately punish people you are friends with, ask another staff member to handle the issue. Always handle your friends the same way as any non-friend is handled - they do not get special treatment.

How to act professionally:

Don’t let your emotions affect how you staff - if a player is giving you attitude, keep your cool. Don’t react to a player pushing your buttons, they’re trying to get a reaction out of you and it’s important to not give them what they want. Try to defuse situations quickly and professionally, but remember if you cannot do this, or if an issue is personally offending you and clouding your judgement, let someone else handle it. Sometimes it’s better to walk away!

If a personal attack escalates to a violation of chat rules, handle the situation like any other rule violation. Just because it’s aimed at you doesn’t mean that you’re not allowed to enforce rules.

How to handle ban appeals:

The staff member who issued the ban handles the ban appeal, and it’s up to their judgement whether they have made a mistake and should accept or deny the appeal. Do not post on an appeal unless you are the one who handled the punishment or are directly involved with the details of the situation. If you are stuck or confused on whether to deny, accept or shorten the ban, consult with other staff. Try to respond to an appeal as soon as you can - within 24 hours is preferred.

General Operations & Warnings

Check History First: Always run /history <username> before warning or muting. Adjust your mute length based on prior offenses (offenses within the last 24 hours accumulate).
Warning Format: You must include the player's username in warnings so they know it is directed at them (e.g. (Username), please don't spam.). Simply saying "spam" or "don't spam" in chat is unprofessional.
Emergency Kicking: If spam is too fast or disruptive, use /kick <username> (which automatically reasons "spam") to stop the flood and give you time to check /history.
Inactivity Notice: If you are going away for an extended time (3+ weeks), tell a staff member or post in the "Staff Discussion" forum/Discord channel to prevent inactivity demotions.
TP Raiding Restriction: If you teleport to a player to assist them, you are not allowed to raid them.

Vanish & Dynmap

Vanish mode makes you invisible to and undetectable by players, allowing you to patrol player activities without being seen:

Toggle Vanish:
/cmi vanish
Hide on Dynmap:
To prevent players from tracking your coordinates on the web map while vanished, run:
/dynmap hide
Show on Dynmap:
To make yourself visible on the web map again, run:
/dynmap show

Command Reference

CoreInspect (Log Lookup)

/co i (or /co inspect): Toggles log inspection. When enabled, right-click blocks or chests to view logs in chat. Run again to disable. Only use for active investigations.
/co l p:<user> a:<action> t:<time> r:<radius> i:<include> e:<exclude>: Queries specific logs.
- action: Can be +inventory (pickup), -inventory (drop), block, container.
- time: e.g., 12h (hours), 3d (days).
/co L 1:20: Expands search results to 20 results per page.
/co page <number>: View a specific page of log results.

Mod Utilities

/erealname <nickname>: Shows a player's full username when they have a nickname enabled.
/displayshops owner <username>: Transfer shop slab/block ownership. You must be looking at the individual shop block/slab.
/unwarn <username>: Removes the last warning from a player's history. Use only if a mistake was made.
/dupeip <player>: Verifies whether multiple accounts are registered on the same IP. Do not ban players as alts based on /dupeip alone; refer suspected alts to an Admin.
/ipreport: Lists online players sharing IPs.
/nick list: Lists pending nickname requests. Accept/deny requests via /nick view <player>.

Discord Ticket Handling

Moderators have access to general support tickets and player reports:

Privacy: If a player report or support ticket leaks base coordinates or home locations, you are strictly forbidden from utilizing or sharing this info.
Conflict of Interest: If a player report is filed against you, you may post your side of the story, but the final decision must be evaluated and closed by an Admin.
Claiming & 24h Rule: Claim tickets you are actively resolving. If another staff member has claimed a ticket but has not responded for 24 hours, you may step in.
Closing: Close tickets after player confirmation, or after 24 hours of inactivity. Ensure you delete the ticket logs upon closure (transcripts are archived automatically).

Conclusion

If you have any further questions, feel free to contact higher staff, who are almost always willing to help. Remember - you were promoted because we trust you, and we believe you’re going to be a good addition to our staff team. If you ever doubt your performance as a Trial-Mod, or even Moderator, we urge you to speak to higher staff, because they will let you know on how you can improve.

An important note to remember is we do not tolerate needless drama among our staff team - so please keep things professional. We understand that there may be conﬂict, but it’s important to remember we are a team, and therefore we must cooperate and be nice. If you ever doubt a staff member’s actions, please take them to Dakota and they will deal with things as they see ﬁt.

Besides that - once again, congratulations. If you make a mistake, it’s not the end of the world. Please remember that they’re absolutely ﬁne - as long as you ﬁx them, and learn from them. Don’t beat yourself up over a mis-tabbing of a name, or an incorrectly timed mute. As a Trial-Mod/Moderator, you are always welcome to seek out feedback from other/higher staff members to improve your performance. This is not only healthy for your experience but also encouraged as it helps us understand that you’re aiming to improve. Good luck! Welcome to the staff team!

Last Updated: 3/12/2024 by parcheesi15