Discord bot message variables

Variables let a Better Tickets message change depending on who it's about. Type {{author.username}} in a ticket welcome message and each member sees their own name. This page covers the template syntax (output tags, if conditions and the random tag) and lists every variable available in ticket, application and leveling messages.

Output tags: {{ }}

Wrap a variable name in double braces to insert its value.

{{author.username}} opened this ticket.

Renders as alex opened this ticket. if author.username is alex. Nest with dots ({{author.username}}, {{server.name}}), spacing inside braces doesn't matter. An unknown variable renders as empty, not an error.

{{now}} is always available and holds the current time as a Unix timestamp. Use it inside a Discord timestamp tag, such as Opened <t:{{now}}:R>, to show a time in each reader's own time zone. The Discord timestamp generator explains every timestamp format.

Conditional tags: {% if %}

{% if fruit %}You picked {{fruit}}.{% else %}No fruit picked yet.{% endif %}

A condition is either:

• Truthy: {% if fruit %}, true if set at all.
• Equality: {% if fruit == "apple" %} or !=. Quotes optional for single words, required if the value has spaces. The right side can be another dotted variable too, e.g. {% if author.userId == server.ownerId %}.

Chain more branches with {% elsif %}:

{% if status == "accepted" %}Accepted{% elsif status == "denied" %}Denied{% else %}Pending{% endif %}

Both % symbols matter, {% if claimer} (missing one) is left as broken literal text.

The random tag: {{random: ...}}

Picks one option at random each render, comma-separated:

{{random: A staff member will be with you shortly., Please wait for a staff member., Hello\, we'll be right with you.}}

This is what the default welcome message uses. Escape a literal comma with \,.

Common variables

Available in both ticket and application messages, only author's meaning changes.

Where you can use variables

Tickets

Every ticket message field gets the common variables plus ticketId (the category's identifier). What else each one adds:

Default channel name, used unless you set a template with Premium:

{% if claimer %}✅{{author.username}}-{{claimer.username}}{% else %}{{ticketId}}-{{author.username}}{% endif %}

Default footer:

{% if claimer %}Opened by {{claimer.username}} for {{author.username}}.{% else %}Opened by {{author.username}}.{% endif %}

Applications

Every application field gets the common variables, except Title/Description which only gets server (there's no applicant yet). What each field adds:

Default submission message:

**New application**
Author: <@{{author.userId}}>.
Username: {{author.username}}.
Nickname: {{author.globalName}}
{{qa}}

A decided-by footer is added automatically and can't be edited.

Leveling

Message template (Announcements tab). Common variables plus {{level}}.

Default: 🎉 {{author.username}} just reached level **{{level}}**!

Roleplay

Message template and Footer text (Premium). Does not use common variables, server isn't available and author/target only expose id/username.

Default message (handles with/without target in one template):

{% if target.id %}<@{{target.id}}>! {{author.username}} {{verb}}{% if isBack %} back{% endif %}.
 
{% if mutualCount %}-# {{author.username}} and {{target.username}} {{past}} {{mutualCount}} time(s).{% elsif receivedCount %}-# {{target.username}} {{past}} {{receivedCount}} time(s).{% endif %}{% else %}{{author.username}} is {{gerund}}.{% endif %}

Default footer: {% if rp.animeName %}-# Anime name: {{rp.animeName}}.{% endif %}

Per-command reference, what {{verb}}/{{gerund}}/{{past}} resolve to ({{past}} only shows on actions that track a count):