Tickets

A player types /ticket, picks a kind, and says what is wrong. Your team answers — in game with /tickets, or in the Discord thread it opened. Both are the same conversation.

What to configure

tickets.toml:

• kinds is what somebody may open, and what each one is for. The default is help, bug and report; the arrow after each is where you write the description a player sees when they pick it.
• limit-per-person is how many somebody may have open at once. Default three.
• cooldown stops the same person opening one every second.

discord.tickets.category puts the threads somewhere, and discord.tickets.roles is who on Discord can see and answer them. Without a category the Discord half stays off and tickets are a purely in-game thing — which is a fine way to run it.

The transcript

Closing a ticket does not delete it. The whole conversation is kept, so a report that comes back a month later has its history, and so an answer somebody gave can be found again. That is the difference between a ticket and a message in chat.

Reports about people

report is a kind like any other, but the person being reported is not told and does not see the thread. What happens next is moderation — a ban carries its reason and who set it, and the player sees that reason on the screen they are shown.