Why in game tickets

When a report lives in a Discord channel, staff have to ask where it happened, who was there and whether it is still going on. Players give up halfway through. This free resource moves the whole conversation into the server. A player types your command, fills in a short form and sends it, and the ticket arrives with their coordinates already attached.

For the person reporting

• Pick a category, give it a title and describe the problem.
• Your location is saved with the ticket automatically.
• Answer staff questions inside the same thread.
• See a notification on screen as soon as staff reply or update the status.

For the person answering

• Every open ticket in one place, without leaving the game.
• Reply directly and keep the history together.
• Move tickets through statuses you design. Each status has its own label and colour, and you decide whether players can still reply once it is set. Mark something resolved and the thread is closed.
• A webhook pushes ticket activity wherever you keep your logs.

Yours to configure

Choose the command name, restyle the theme, rename or add categories and decide which staff ranks can see the queue. All of it is in the config file.

Install notes

Works on ESX and QBCore. Requires oxmysql and ox_lib. Free to download and use.