Are you an LLM? You can read better optimized documentation at /en/message-templates/advanced/variables.md for this page in Markdown format
Variables
INFO
Some message templates have their own unique variables related to the feature they represent. Those variables are described in corresponding articles, such as:
Common Variables
Message Templates have some common predefined variables:
| Variable | Type | Description |
|---|---|---|
guild | Guild | Server information |
bot | Member | Member instance of JuniperBot itself |
member | Member | Member instance related to this template |
channel | TextChannel | Target channel where this template should be sent (if only guild message, not DMs) |
sourceChannel | TextChannel | Source channel like the channel where the custom command were invoked. It is different from channel that the last one may be different target channel selected in the message template interface. |
message | Message | Message instance related to this template. For example, custom command invocation message or violation message in Auto-Moderation. |
override | Embed | Embed overrides (allows to set template embed values by code) |
Those variables are always included in every message template. Sections below will describe some additional variables for a different message templates.
Custom Commands
Additional variables passed to custom commands Actions.
| Variable | Type | Description |
|---|---|---|
arguments | Arguments | Information about arguments passed to the command. |
parameters | Parameters | Information about parameters passed to the action. |
component | Component | Information about component executed the action. |
modal | Modal | Information about modal executed the action. |