Skip to main content

Tickets in player view

This page explains how players use the ticket system in the shop frontend.

Navigation path:

  • Shop -> Tickets

For shared lifecycle and Discord behavior, see Tickets concept.

Access requirements​

  • tickets.view to open the ticket area and see participating tickets
  • tickets.create to create new tickets
  • tickets.send_message to reply and edit the subject while a ticket is active
  • tickets.close to close an active ticket
  • tickets.archive to archive a resolved ticket when auto-archive is disabled

Ticket overview​

The page separates tickets into two sections:

  • Active tickets for Open and In progress
  • Closed tickets for Closed and Archived

Open a ticket row to view the conversation, participants, actions, and any Discord shortcut.

Active ticket rows may show a Waiting for Response badge (blue) when support has replied and is waiting for the player to respond.

Creating a ticket​

Typical flow:

  1. Open Shop -> Tickets.
  2. Select New Ticket.
  3. Enter a subject.
  4. Enter your first message.
  5. Submit the ticket.

After creation, the ticket appears in the active list. If Discord ticket channels are configured, dzbot also creates the linked Discord channel in the background.

Conversation view​

Inside a ticket, players can usually:

  • read the full public message history
  • reply while the ticket is active
  • edit the subject while the ticket is active and reply rights are enabled
  • open the linked Discord channel if one exists

The participant chips show everyone who currently has access to that ticket in the shop.

Closing, archiving, and reopening​

Resolved-ticket actions depend on server configuration and assigned rights:

  • Close ends the active conversation
  • Archive finishes the ticket and removes the Discord channel
  • Reopen opens the ticket again after it was closed or archived

If Tickets Auto Archive is enabled in server settings, closing skips the long-lived closed state and archives the ticket immediately.