Management & Security
Player tickets and support
Categorised tickets, reports, appeals, evidence, conversation and email notifications give players a protected support channel.
Player tickets and support give a community a clear way to report a problem, request an incident review or appeal a decision. Every ticket has a public reference, category, state, conversation and separate internal staff notes.
Players track their case without administration access
The public reference acts as a private private access code. Players see only public conversation; internal IDs, staff notes, technical request details and email history remain protected.
Ticket system capabilities
Operators configure categories and requirements to match community policy.
- player report, technical issue, ban appeal and custom categories
- required target player or evidence depending on category
- new, under review, answered, closed and rejected states
- public replies, internal notes and email notifications
Better support without private-message chaos
A ticket remains traceable when the moderator changes or the conversation lasts several days.
- process a ban appeal with decision history
- report a suspicious player with evidence
- request an investigation of lost equipment
- ask a general question about rules or a community service
Protected public and administrative flows
Submission uses form protection, a spam trap, abuse blocking and attempt limits and verified-email checks. Every available request-metadata field is stored independently for authorised administrative audit.
Email enters the email queue and a separate delivery service handles SMTP. Tickets never run RCON, grant refunds or change a ban; the appropriate owner performs an action after review.
Faster answers and more trustworthy support
Players know their case has a state and history while staff work in one conversation with the context they need.
Need more information?
We will show you how this feature can work on your server. Contact us or join us on Discord.
