Tags

Tired of sending the same answer over and over? Send a tag! - Pre-defined messages inside and outside of tickets.

Structure & Info

Every tag has a name and content and an ID. The ID is just for identification and is nothing a normal user has to care about - it can be used though for some commands where the option name-or-id is available.

The name has to be unique and must meet the following conditions:

  • minimum of 2 characters

  • maximum of 50 characters

  • only underscore letters, numbers, underscores and spaces

The content must be between 2 and 4000 characters long and can contain any available Markdown.

Limits

There are limits for Free- and Gold-Users.

Plan
Maximum of available tags

Free

10

Gold

100

Configuration

Create a tag

  • Command: /config tags add

This opens up a modal where you have to fill in the name and the content.

Edit a tag

  • Command: /config tags edit

This opens up a modal where you can edit the name and content of the tag.

Delete a tag

  • Command: /config tags delete

This just deletes the tag instantly.

List all tags and preview them

  • Command: /config tags list [page]

This will respond with a page of tags, the first page by default. All tags are sorted by their creation date - newest first.

Each page displays up to 10 tags with their ID, name and content.

Every tag content is trimmed down to 512 characters here because we could hit a Discord-limit if that wouldn't be.

Use the preview to see the full content.

Here you can delete more than one in one go by just selecting them from the select menu below.

To preview tags you can select one at a time from the other select menu.

Use the buttons to change pages.

-- Bild --


Send tags

Send tags with the /tag command.

The tag is typically sent as plain text. To change this behavior, use the available options. Every option is optional.

  • mention - set a user that should get pinged in the response.

-- Bild --

  • as-embed - if the tag content should be inside of an embed.

-- Bild --

-- Bild of both variants --

mention and as-embed will both have no effect if the command is run inside of a ticket.

Last updated

Was this helpful?