Message Variables
Message variables are placeholders Kakashi replaces when it sends a configured message. Different editors support different variables—do not assume every placeholder works everywhere.
Welcome and leave variables
| Variable | Value |
|---|---|
{member} | Member/user representation used by the message renderer. |
{member.tag} | The member's Discord tag/name representation. |
{member.avatar} | Avatar URL for image fields. |
{server.name} | Server name. |
{server.icon} | Server icon URL. |
{server.members} | Current server member count. |
Example:
Welcome {member} to **{server.name}**!
You are member #{server.members}.
Ban-message variables
| Variable | Value |
|---|---|
{user} | Banned user representation. |
{user.tag} | Banned user's tag/name. |
{user.avatar} | Banned user's avatar URL. |
{reason} | Reason passed through the Kakashi ban flow. |
{server.name} | Server name. |
{server.icon} | Server icon URL. |
{mod} | Moderator representation. |
{mod.avatar} | Moderator avatar URL. |
Text vs image fields
Avatar/icon variables are most useful in fields that expect a URL, such as an embed thumbnail/image/author icon. A mention/name variable is more useful in ordinary content/description.
tip
When an editor has a test action, test variables there before relying on a real join/leave/moderation event.
Common mistakes
- Copying
{reason}into a welcome message and expecting it to exist. - Putting a text variable into a field that expects a URL.
- Misspelling the braces/name and getting literal text in the output.