How players create tickets is described under Tickets & reports. For the team:
- The team gets new tickets with [Open] [Teleport] [All tickets] in chat (
mradmin.tickets.notify). - Under dashboard → Tickets or
/mradmin tickets: filter, answer, claim, close, reopen. Whoever answers first claims the ticket automatically. - The ticket shows the history like a chat. Whoever is offline learns about new answers at the next join.
- You create categories under
tickets.categories(in the web interface as a table). Default: cheating, chat, griefing, scam, bug, question/other. - Automatic tickets from plugins: if a plugin reports a problem of a player, they automatically get a ticket - e.g. with MRchunks, when their chunk loader is locked because of lag, with all measurements. Only the team can close it. Switch off with
tickets.plugin-reports: false. - More settings under
tickets: cooldowns, limits, how long closed tickets are kept.
In the browser the same tickets are under Tickets in the web interface - plus unban requests and the contact form.
Permissions
mradmin.tickets.create (players) · .notify · .view · .reply · .claim · .close · .reopen · .teleport - all in mradmin.groups.support, see Permissions.