Tickets
Opened in game or on Discord with one command, answered wherever your team is, optionally forwarded to your own queue, and the conversation survives closing it.
This page is older than Keystone 0.4.3, released 15 November 2026. Something may have changed since.
On this page 5 parts
Tickets
A player types /ticket <what is wrong> and the ticket is open. Your team
answers — in game with /tickets, or in the private Discord channel it opened.
Both are the same conversation.
Without learning a syntax
#New in 0.2.6. /ticket <what is wrong> opens a ticket straight away, with the kind
set by default-kind; /ticket bug … still chooses a kind. /bug and /feedback
are commands of their own (shortcuts). An answer reaches the player in game
with a chime, now or the next time they join.
What to configure
#tickets.toml:
kindsis what somebody may open, and what each one is for. The default ishelp,bugandreport; the arrow after each is where you write the description a player sees when they pick it.limit-per-personis how many somebody may have open at once. Default three.cooldownstops the same person opening one every second.
discord.tickets.category puts the ticket channels in that category, 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.
A public forum for some kinds (from 0.3.4). In discord.toml:
tickets.forumis a forum channel id; blank turns it off.tickets.forum-kindslists the kinds that go there (default["feedback"]).tickets.forum-tagslists forum tag ids to put on every post, up to 5.
A ticket of a forum kind (/feedback <text>) becomes a public post in that forum, titled with its first line, which everybody can read and answer. Answers reach the player in game the way they do from a ticket channel. Closing the ticket locks the post and keeps it. /ticket stays a private channel. The bot needs Create Posts and Manage Threads in the forum.
Every ticket card, in a channel or in a forum post, has a Close ticket button. In a private channel anyone who can see the channel may press it; on a forum post only the person who opened it (with a linked account) and members who can manage threads or channels may.
Forwarding to another queue
#New in 0.2.6, off by default. With tickets.forward.url set, every ticket, line
and close is posted there as JSON, with tickets.forward.key as a bearer token.
What cannot be delivered is kept and retried for three days. Answers come back
through POST /v1/tickets/reply and POST /v1/tickets/close (key scope
tickets.write).
verified (from 0.3.4): an opened event carries "verified": true only when
the player's name is proven in this session — the server runs in online mode, or
the accounts module confirmed the name on Discord for an account linked there. A
password does not count: it proves the name to this server, not to anybody's
account elsewhere. On the other end, never tie a ticket with "verified": false
to a person's account; on an offline server anybody can type any name.
This is data leaving the machine, so it is guarded: the address must be https on
the internet and only the owner can set it; loopback, LAN, link-local and names
that resolve there are refused unless tickets.forward.allow-local; redirects
are never followed; the log shows only the scheme and host.
The transcript
#Closing a ticket does not delete it. The whole conversation is kept in the mod, so a report that comes back a month later has its history, and so an answer somebody gave can be found again. The Discord channel is deleted when the ticket closes — it is a window onto the ticket, not the ticket itself. 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 channel. 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.
Did this page help?
Opens the feedback panel with this page attached. It lands in the same queue as everything else.