The ticket system unifies support and reports: the player opens a ticket with /report, staff reply with /reports or from the web panel, and optionally everything syncs to private Discord threads.
Enabling tickets
- 1Panel → My servers → your server → Tickets tab.
- 2Enable Tickets active and save the quick settings.
- 3Restart
Adictos_WebLogsin FiveM to sync the config. - 4Assign the View tickets permission (
view_tickets) to the staff roles that should manage them.
In-game commands
| Command | Who | Description |
|---|---|---|
/report | Player | Opens the menu and creates a ticket (category, subject, message) |
/reports | Staff | Lists open tickets and lets you reply, assist and close |
/ticketadd [id] [id_jugador] | Staff | Adds another connected player to an existing ticket |
id for /ticketadd is the internal number shown in the web panel or in the in-game staff list.Web panel (staff)
- 1Side menu → Tickets (requires the
view_ticketspermission). - 2Select a ticket to see the history and reply.
- 3Use Assist to mark that you’re handling it, Close when it’s done, or Reopen if needed.
- 4You can add players to the ticket (licence or Discord ID) so several people take part in the same conversation.
On the Dashboard you’ll see how many tickets are waiting for a staff reply (last message from the player or no staff reply).
Full configuration
For categories, limits, blacklist, schedules, tags, AI, NUI appearance and Discord sync:
- 1Panel → Admin → Ticket settings (requires
edit_tickets_configor being the Owner). - 2Define up to 6 categories with icon, colour, open-ticket limit and extra fields.
- 3Under Blacklist block users (Discord, licence) or Discord roles, in all categories or only in some.
Notify staff on Discord (webhook)
Independent from thread sync. When a player opens a ticket with /report, the panel can send an embed to a staff channel:
- 1Create a webhook in Discord (staff channel → Integrations → Webhooks).
- 2My servers → Tickets → Webhook — new in-game tickets → paste the URL and enable it.
- 3Optional: a second webhook for staff actions (assist, reply, close).
Automatic closing
| Setting | Effect |
|---|---|
| Days without a staff reply | Closes if the player wrote and no staff member replied within X days |
| Days without a player reply | Closes if staff replied and the player didn’t answer within X days |
Set either one to 0 to disable it. Configurable under My servers → Tickets or Ticket settings → General.
Discord (threads and bot)
Optional: players open tickets from buttons, /ticket or the category command (e.g. /new) on Discord; each ticket is a private thread or a channel synced with the panel. The command accepts an optional user or role (objetivo), for staff only: the user becomes the ticket owner and is notified once; the role gets access as with /add, without pinging the whole role. It requires connecting the bot under My servers → DiscordBot and starting the ticket bot from Panel Settings. Details in the Discord roles section.