THE TSHE FIELD GUIDE

Find your way.

Everything you need to find your way around TSHE.

87 documents 10 sections
DOCUMENTATION / BOTS / LYXIA / COMMANDS

Tickets Commands

Lyxia tickets slash commands, usage, options, and availability.

100% slash commands

Lyxia is 100% slash-command based. Legacy prefix commands have been removed in line with Discord’s Message Content Intent restrictions. Type / in Discord to discover and run commands.

← All command categories

Tickets

/apppanel

Application panel management

Usage: /apppanel add <channel> <message_id> <application_name> [button_color]

Applies application button to a message

Options:

  • channel — Where is the message located (channel, required)
  • message_id — Message ID (text, required)
  • application_name — Application name (text, required)
  • button_color — Button color (text, optional) Choices: Red, Blue, Green, Gray.

Usage: /apppanel remove <channel> <message_id> <application_name>

Removes ticket button from a message

Options:

  • channel — Where is the message located (channel, required)
  • message_id — Message ID (text, required)
  • application_name — Application name (text, required)

Usage: /apppanel default [channel]

Generates default application panel

Options:

  • channel — Channel (channel, optional)

Usage: /apppanel enable <application_name>

Reenable application form

Options:

  • application_name — Application name (text, required)

Usage: /apppanel disable <application_name>

Close application form

Options:

  • application_name — Application name (text, required)

/appreview

Review an application

Usage: /appreview accept <role>

Accept an application

Options:

  • role — Accept as (text, required)

Usage: /appreview deny [duration] [reason]

Deny an application

Options:

  • duration — Application creation cooldown (text, optional)
  • reason — Reason (text, optional)

Usage: /appreview allow_chat

Allow chat in an application

Usage: /appreview deny_chat

Deny chat in an application

Usage: /appreview history

View user history

/tclose

Close a ticket

Usage: /tclose request [reason]

Request the ticket to be closed

Options:

  • reason — Reason (text, optional)

Usage: /tclose force <silent> [reason]

Closes the ticket without any request sent

Options:

  • silent — If set to true, the ticket creator won't receive a message that their ticket was closed (true/false, required)
  • reason — Reason (text, optional)

/tedit

Edit ticket properties

Usage: /tedit move <category>

Move the ticket to a different category

Options:

  • category — Ticket Category (channel, required)

Usage: /tedit merge <ticket>

Merge the ticket with another ticket

Options:

  • ticket — Target ticket channel (channel, required)

Usage: /tedit rename <name>

Rename the ticket channel

Options:

  • name — New channel name (text, required)

Usage: /tedit whitelist

Whitelist the ticket from inactivity closures

/tnote

Manage internal notes on this ticket

Usage: /tnote add <content>

Add an internal note to this ticket

Options:

  • content — Note content (text, required)

Usage: /tnote list

List internal notes on this ticket

Usage: /tnote remove <index> [clear]

Remove an internal note by its number

Options:

  • index — Note number as shown by /tnote list (number, required) Minimum: 1.
  • clear — Remove all notes instead (true/false, optional)

/tpanel

Generate a new ticketpanel

Usage: /tpanel default [channel]

Generates default ticket panel

Options:

  • channel — Channel (channel, optional)

Usage: /tpanel add <channel> <message_id> <category_name> [button_color]

Applies Ticket button to a message

Options:

  • channel — Where is the message located (channel, required)
  • message_id — Discord message ID (text, required)
  • category_name — Ticket Category name (text, required)
  • button_color — Button color (text, optional) Choices: Red, Blue, Green, Gray.

Usage: /tpanel remove <channel> <message_id> <category_name>

Removes ticket button from a message

Options:

  • channel — Where is the message located (channel, required)
  • message_id — Discord message ID (text, required)
  • category_name — Ticket Category name (text, required)

Usage: /tpanel enable <category_name>

Reenable ticket category

Options:

  • category_name — Ticket Category name (text, required)

Usage: /tpanel disable <category_name>

Disable ticket category

Options:

  • category_name — Ticket Category name (text, required)

/tpermission

Manage ticket permissions

Usage: /tpermission lower [level]

Lower ticket access

Options:

  • level — Permission level (text, optional)

Usage: /tpermission raise [level]

Raise ticket access

Options:

  • level — Permission level (text, optional)

/treset

Reset ticket data

Usage: /treset stats <option>

Reset ticket statistics

Options:

  • option — Type (text, required) Choices: tickets_closed, tickets_claimed, tickets_unclaimed, apps_managed.

Usage: /treset app_cooldown <user>

Unset application cooldown

Options:

  • user — User (user, required)

Usage: /treset application <user>

Delete application data

Options:

  • user — User (user, required)

/tstaff

Ticket utility commands

Usage: /tstaff claim

Claim the ticket

Usage: /tstaff unclaim

Unclaim the ticket

Usage: /tstaff assign <staff>

Assign the ticket to another staff member

Options:

  • staff — Staff member to assign the ticket to (user, required)

Usage: /tstaff transfer <staff>

Transfer the ticket to another staff member

Options:

  • staff — Staff member to transfer the ticket to (user, required)

Usage: /tstaff transfer-ownership <user> [remove_creator]

Transfer the ownership of the ticket to another user

Options:

  • user — User to transfer the ticket to (user, required)
  • remove_creator — Should the original creator of the ticket be removed? (true/false, optional)

Usage: /tstaff priority [priority]

Change the priority of the ticket

Options:

  • priority — Ticket priority (text, optional)

Usage: /tstaff follow

Follow the ticket

Usage: /tstaff unfollow

Unfollow the ticket

Usage: /tstaff discuss

Discuss the ticket with other staff members

Usage: /tstaff history <user>

View the ticket history of the specified user

Options:

  • user — User (user, required)

Usage: /tstaff transcripts [created_by] [claimed_by] [closed_by] [category] [rating]

View a list of transcripts based on the specified filters

Options:

  • created_by — Ticket created by (user, optional)
  • claimed_by — Ticket claimed by (user, optional)
  • closed_by — Ticket closed by (user, optional)
  • category — Ticket category (text, optional)
  • rating — Ticket rating (text, optional) Choices: None, ⭐☆☆☆☆, ⭐⭐☆☆☆, ⭐⭐⭐☆☆, ⭐⭐⭐⭐☆, ⭐⭐⭐⭐⭐.

Usage: /tstaff open <user> <category>

Force open a ticket for another user

Options:

  • user — User to open the ticket for (user, required)
  • category — Ticket category to open the ticket in (text, required)

/tstats

Show ticket statistics and open ticket insights

Usage: /tstats overview

Show an overview of open tickets and response metrics

Usage: /tstats category <category>

Show statistics for a specific ticket category

Options:

  • category — Ticket category (text, required)

/tuser

Manage ticket users

Usage: /tuser add <user>

Add user to ticket channel

Options:

  • user — User to add (user, required)

Usage: /tuser remove <user>

Remove user from ticket channel

Options:

  • user — User to remove (user, required)

Usage: /tuser remove_all

Remove all added users from the ticket channel

Usage: /tuser list

List all users added to the ticket channel

Permission and availability

Discord only displays commands available to your role and context. Member-management commands also require Lyxia’s role to be high enough in the Discord role list.

Lyxia is private

Lyxia is a private TSHE bot. It is configured for this community and cannot be invited to, copied for, or used in another server.