Tickets
The bots ticket system that is built specifically for SCP:SL
Settings
The general settings for the built in ticket system
settings:
# The channel all new ticket creation will be sent to
ticket_log_channel: ""
# The channel where the application message (active/not active) will be sent to
application_message_channel: ""Application Types
This is just a showcase, you can find all predefined application types in the /SCPToolsBot/configs/ticket-settings.yml
The types (roles/positions) of application that users are able to send
# The types of roles that can be applied for. Duplicate one of the roles that already exist
# to create a new one, you can add as many as you like
application_types: [
{
# The name of the role
name: "",
# The role description, meaning their supposed work in the team
description: "",
# The roles emoji that will be shown in the list of applicable roles
emoji: "",
# The roles id, meaning the discord role itself
role_id: ""
}
]Types
Do not add any more ticket types than defined in the config, they will not work and could result in a crash
This is just a showcase, you can find all predefined ticket types in the /SCPToolsBot/configs/ticket-settings.yml
The types of tickets that can be created, each with a different purpose and some own quirks
# ** WARNING ** Do not add or remove any types as it will cause errors
# The types of tickets that can be opened
types: [
{
# The name of the ticket type
name: "",
# ** WARNING ** Don't change this as it will change how the bot defines
# the type defining the ticket in the code
type: "",
# The roles that will be added to the ticket once it is created
roles: [ ],
# The roles that can interact with the tickets log
log_permissions_roles: [ ],
# The channel that the ticket will be created under (ticket is a thread)
parent_channel: "",
child_rules: {
# ** WARNING ** Do not remove the %r% in the type name as it will cause errors
# The naming scheme the ticket type follows, the %r% stands for the number of the ticket
parent_name: "Ticket #%r%",
# ** WIP ** This feature has not been implemented yet, and it's implication is not certain for 100%
# Should the status bar be displayed
use_status_bar: true,
# ** WIP ** This feature has not been implemented yet
# Should the ticket be locked when first created, needing a staff member to unlock it
lock_on_default: false
}
}
]Last updated