Commands

A list of Ticket Tool's commands

The default prefix for Ticket Tool is $. Pinging Ticket Tool before the command would also work: @Ticket Tool#4843help
If you've changed the default prefix for Ticket Tool in your server, replace the $ with the prefix you set.

Commands will have 2 "arguments", which is a piece of information that can be used by the command to execute a special action:

The Required Argument, written in []
The Optional Argument, written in {}

General Commands

Command	Usage	Description
$help	$help $help commands $help setup $help faq	Provides some basic documentation and assistance about the bot: its commands, how to set it up, and a list of frequently asked questions.
$debug	$debug	Provides useful troubleshooting information about your server, the channel $debug is used in, and your own permissions on the server. Support team members may ask you to run this command and provide them with the link it generates to get the information they need to assist you.
$permlevel	$permlevel {User ID} $level {User ID}	Ticket Tool responds with your own permission level on this server, or the permission level of the user whose ID you inputted after the command. This is useful for permission issues regarding accessing your server's dashboard
$ping	$ping	Provides the current latency between your server, the bot, and the Discord API. This might be used while troubleshooting.
$panel	$panel [ID]	Send a panel to the current channel. The ID of a panel is in Panel Configs, to the left of the panel name.

Command

Usage

Description

$help

$help $help commands $help setup $help faq

Provides some basic documentation and assistance about the bot: its commands, how to set it up, and a list of frequently asked questions.

$debug

Provides useful troubleshooting information about your server, the channel $debug is used in, and your own permissions on the server. Support team members may ask you to run this command and provide them with the link it generates to get the information they need to assist you.

$permlevel

$permlevel {User ID} $level {User ID}

Ticket Tool responds with your own permission level on this server, or the permission level of the user whose ID you inputted after the command. This is useful for permission issues regarding accessing your server's dashboard

$ping

Provides the current latency between your server, the bot, and the Discord API. This might be used while troubleshooting.

$panel

$panel [ID]

Send a panel to the current channel. The ID of a panel is in Panel Configs, to the left of the panel name.

Ticket Commands

Command Usage Description

Command	Usage	Description
$close	$close	Closes a ticket channel that is in the `Opened` state.
$open	$open	Re-opens a ticket channel that is in the `Closed` state.
$delete	$delete	Deletes a ticket channel, no matter if it's in the `Opened` or `Closed` states.
$rename	$rename [Name]	Renames the ticket channel.
$transcript	$transcript {#channel} {X Amount of lines}	- Creates a transcript of the last 500 (free) - 1000 (premium) messages in the current channel, which is then uploaded as a .html file. - If no send channel is chosen, then the transcript will be sent to your defined Transcript Channel. - 💎 Premium Users will have the ability to use this command in all channels, regardless if it's a ticket or not.
$add	$add [@User#1234] $add [User ID] $add [@Role] $add [Role ID]	Gives an additional user or role access to the current ticket channel. They are given the same permissions as the User Opened Permissions.
$remove	$remove [@User#1234] $remove [User ID] $remove [@Role] $remove [Role ID]	Removes a user’s or role's access to the ticket channel if they had access to the ticket when it was created, or if they had been added with the `$add` command.
$claim	$claim {@User} $claim {User ID}	Premium Only Command. If Ticket Claiming is enabled, then this allows a support team member to claim the ticket.
$unclaim	$claim {@User} $claim {User ID}	Premium Only Command. This allows a support team member to unclaim the ticket if someone had previously claimed it.
$closeRequest	$closeRequest / $ca	Sends the Close Ask Message to the ticket channel.

$close

Closes a ticket channel that is in the Opened state.

$open

Re-opens a ticket channel that is in the Closed state.

$delete

Deletes a ticket channel, no matter if it's in the Opened or Closed states.

$rename

$rename [Name]

Renames the ticket channel.

$transcript

$transcript {#channel} {X Amount of lines}

- Creates a transcript of the last 500 (free) - 1000 (premium) messages in the current channel, which is then uploaded as a .html file. - If no send channel is chosen, then the transcript will be sent to your defined Transcript Channel. - 💎 Premium Users will have the ability to use this command in all channels, regardless if it's a ticket or not.

$add

$add [@User#1234] $add [User ID] $add [@Role] $add [Role ID]

Gives an additional user or role access to the current ticket channel. They are given the same permissions as the User Opened Permissions.

$remove

$remove [@User#1234] $remove [User ID] $remove [@Role] $remove [Role ID]

Removes a user’s or role's access to the ticket channel if they had access to the ticket when it was created, or if they had been added with the $add command.

$claim

$claim {@User} $claim {User ID}

Premium Only Command. If Ticket Claiming is enabled, then this allows a support team member to claim the ticket.

$unclaim

$claim {@User} $claim {User ID}

Premium Only Command. This allows a support team member to unclaim the ticket if someone had previously claimed it.

$closeRequest

$closeRequest / $ca

Sends the Close Ask Message to the ticket channel.

Multipanels

Multipanels are panels with multiple buttons attached to them. They can be set up in 3 different ways. The first way can be done on the dashboard using buttons, explained here. The second way is using Dropdowns as explained here. The other option to implemet multipanels is VIA the $panel command.

Here are the steps to create multipanels:

Step One

Find the IDs of each panel you wish to combine. You can find them in your Panel Configs in the Dashboard. The ID would be number of the panel, which is situated on the left of the panel name within the panel selector.

Step Two

Go to the channel you want the panel to be in, then use the $panel command in the following way: $panel [ID] [ID] {ID}...

Replace the ID part with the number of the panel. If we want to follow the panels in the image given in Step 1, then it would be $panel 1 2 3.

Now you should have your own multi-panel!

Up to 25 panels can be combined into a single panel!
The first panel will have both its message and reaction sent to the channel like it was sent to the channel on its own, while the others will only have their reactions added to this panel. When a user clicks one of the reactions, a ticket is made through the corresponding panel.
For the first panel that is sent, you can make a new panel that has it’s “Create Ticket” reaction disabled, and use it as the base panel message. This way, you can keep all your other panels with their original messages, in case you wish to switch back.

The multipanels can be used for many things, such as using them to create tickets for a specific language, like in our Support Server

Command Style Tickets

To use these commands, Command Style Tickets must be enabled, and the command must be performed in the monitored channel.

Command	Usage	Description
$new	$new $new {Reason} $new {@User#1234} $new {@User#1234 Reason} $new {User ID} $new {User ID Reason}	- Creates a new ticket in the specified channel, with an optional reason, or setting a specific user as the ticket owner (Support team only). - If a reason is included, the variable {reason} can be used in the ticket message.

Command

Usage

Description

$new

$new $new {Reason} $new {@User#1234} $new {@User#1234 Reason} $new {User ID} $new {User ID Reason}

- Creates a new ticket in the specified channel, with an optional reason, or setting a specific user as the ticket owner (Support team only). - If a reason is included, the variable {reason} can be used in the ticket message.

Last updated 9 months ago