Back to Courses
Staff & Moderation

The Mod Help System

Module 1: The First Line of Defense

The in-game Mod Help System is the primary way players report rulebreakers, glitches, or ask for assistance. When a player types !mod [reason] into the chat, a notification is sent to all active staff members on the server. Understanding how to manage this queue effectively is what separates a chaotic server from a well-managed community.

Module 2: Claiming and Prioritizing Tickets

When a mod call comes in, it enters a queue. It is crucial that your staff team utilizes the Claim function.

Module 3: Communication Protocol

Professionalism is key. Once a moderator teleports to a player, they should follow a standardized script.

"Hello, you requested a moderator. How can I help you today?"

Moderators should listen to the player's complaint, ask for evidence (if the server requires video proof for bans), and investigate objectively. They should never escalate a situation by arguing with the player. If a player becomes abusive, the moderator should issue a swift punishment rather than engaging in a shouting match.

Module 4: Resolution and Logging

Once the issue is resolved—whether that means issuing a warning, kicking a rulebreaker, or simply answering a question—the ticket must be officially closed in the system.

Furthermore, major actions should be logged. Even if you have webhooks tracking commands, having moderators write a brief summary in a dedicated Discord channel (e.g., `#mod-logs`) provides necessary context that raw data cannot.

Conclusion

A fast, fair, and professional response to mod tickets builds immense trust with your player base. Train your staff on these protocols, and your server will develop a reputation as a safe and enjoyable place to roleplay.