Patrick L.There are many improvements coming soon to the structure of the setuptickets commands, but this is a general basis of how the command works for setting up tickets in your server.
| Parameter | Description | Example |
| ReactionChannel | The channel the reaction embed is sent to | #client-support |
| LoggingChannel | The channel all ticket logs are directed to | #ticket-logs |
| TicketCategory | The category ID that all tickets are parented to | 845119815260831765 |
| PanelName | The "name" of the panel | Client Support |
| PanelColor | The color that is displayed on the reaction embed & open message | #ff0000 |
| OpenMessage | The message that is displayed to the client at the top of the ticket | Hey {USERTAG}! Thank's for opening a ticket. A staff member will be with you shortly. |
| DefaultTicketName (Optional) | The prefix of a ticket channel. Defaults to ticket is nothing is provided |
client |
| PingGhost (Optional) | The role that is mentioned on ticket open. Defaults to @everyone if none provided |
@Premium Support |
How to setup tickets?
To setup a ticket panel, just use the command format with the arguments provided in the table above. Check out the example provided to see how the command should be.
/setuptickets #client-support #ticket-logs 845119815260831765 "Client Support" "#ff0000" "Hey {USERTAG}! Thank's for opening a ticket. A staff member will be with you shortly." "client" @Premium Support
A few side notes
- PanelName, PanelColor, OpenMessage, and DefaultTicketName are required to be inside of quotations!
- Remember that DefaultTicketName is not required, however, to set the PingGhost you must use the DefaultTicketName argument
- TicketCategory must be a category id, not a category name