Variables - Petto

A variable is a word in braces, like {user} or {server_name}, that Petto swaps for real data when it sends a message. Write Welcome {user} to {server_name}! and the new member reads Welcome @Liam to Cozy Corner! This page lists every variable Petto knows, grouped by where its data comes from. The examples use a member called Liam (username liam) joining a server called Cozy Corner with 1,204 members.

You don’t have to remember any of this. The dashboard has a searchable variable list with a copy button next to every field that takes variables, and !embed vars shows the list inside Discord.

How variables resolve

The rules behind the scenes: order, empty values, testing.

Need logic or loops?

Petto Code ({{ }}) adds if, loops, data and buttons. Full docs on code.petto.sbs.

A variable written with other capitals, dots or underscores than the real one ({user.displayname}, {server_member_count}) still works when it can only mean one variable. Anything doubtful is left as typed, and the card and embed editors of the dashboard point out the variables Petto does not know.

Writing variables

Case and spaces don’t matter. {user.mention}, {User.Mention} and { user.mention } all work.
Names from other bots work too. {mention}, {member}, {username}, {server}, {level.xp} and others are read as their Petto equivalent (full list below).
A variable Petto doesn’t know stays as you wrote it. {usr} shows up as {usr}, so a typo is easy to spot.
A variable with no data in that message is empty. {level} in a welcome message has no level to show, so it disappears. A few say so instead: N/A, Unknown, Never, Not boosting.
Values are never read again. If a member’s message contains {server_owner}, {message_content} shows that text as it is, it doesn’t turn into a mention.
There are no filters or conditions. Things like {user.name|upper} or “if boosting, say X” are not part of variables. For that, write a custom command in Petto Code.
Functions can’t hold other variables. {choose:Hi {user}|Hey} breaks. Put the variable outside: {choose:Hi|Hey} {user}!
There is no escape character. A variable Petto knows is replaced even inside code formatting. To show one as text, for example in a help message, describe it in words instead.
Discord’s limits still apply. The text after replacing must fit in the message: 2,000 characters for a message, 4,096 for an embed description, 256 for a title, 100 for a channel or thread name.

Names from other bots that Petto understands

You write	Petto reads it as
`{mention}`, `{user_mention}`, `{member}`, `{member.mention}`, `{user.ping}`	`{user}`
`{user.tag}`	`{user_tag}`
`{username}`, `{user.username}`	`{user_name}`
`{user.nickname}`, `{member.name}`	`{user.display_name}`
`{nickname}`, `{user.nick}`	`{user_nick}`
`{user.discriminator}`	`{user_discrim}`
`{user.avatar_url}`	`{user.avatar}`
`{user.display_avatar_url}`	`{user.display_avatar}`
`{member.id}`	`{user.id}`
`{server}`, `{server.name}`, `{guild}`	`{server_name}`
`{server.id}`	`{server_id}`
`{server.members}`	`{server_membercount}`
`{server.icon}`	`{server_icon}`
`{channel.link}`	`{channel}`
`{message.link}`, `{message.id}`, `{message.content}`	`{message_link}`, `{message_id}`, `{message_content}`
`{level.level}`, `{level.current}`	`{level}`
`{level.xp}`, `{level.total_xp}`	`{level_xp}`
`{level.rank}`, `{level.total}`, `{level.rank_total}`	`{level_rank}`, `{level_rank_total}`, `{level_rank_total}`
`{level.next}`, `{level.previous}`, `{level.progress}`, `{level.bar}`	`{level_next}`, `{level_previous}`, `{level_progress}`, `{level_bar}`
`{level.xp_needed}`, `{level.xp_current}`, `{level.xp_to_next}`	`{level_xp_needed}`, `{level_xp_current}`, `{level_xp_to_next}`
`{level.streak}`, `{level.messages}`, `{level.voice_minutes}`, `{level.type}`	`{level_streak}`, `{level_messages}`, `{level_voice_minutes}`, `{level_type}`
`{level.role}`, `{level.role_name}`	`{level_role}`, `{level_role_name}`

Because case doesn’t matter, {USER_MENTION} and {Server} work as well.

A ! right before a mention, even before {user.mention}, makes it a silent mention: it shows as a mention and notifies nobody.

Where each group works

The groups under Every message work everywhere variables are accepted. The others only have data in the message of their feature.

Feature	Groups with data
Welcome, DM on join	Every message, Invites
Leave, Boost, Birthdays	Every message (the member is the one leaving, boosting or celebrating)
Custom commands	Every message, Triggering message, Command arguments
Autoresponders	Every message, Triggering message, Command arguments (the text after the trigger)
Level-up messages, rank cards	Every message, Leveling, Triggering message for text level-ups
Giveaways	Every message, Giveaways. `{user}` is the winner in winner messages
Bump reminder	Every message, Bump
Sanction messages	Every message, Sanctions
Starboard / Monkeyboard / Clownboard	Every message, Starboard / Monkeyboard / Clownboard
Suggestions, Confessions	Every message, Suggestions, Confessions
Polls, Partners, Requests, Forms	Every message, plus their own group
Honeypot, Counters, Verification	Every message, plus their own group
Vanity and Server Tag, Quests, Rollouts	Every message, plus their own group
Feeds	Only the Feeds group (the words above each notice)
Sticky messages (saved embed only), Reaction roles, Button responders, Auto-thread, Uploads	Every message
Saved embeds and image cards	Whatever the feature that sends them provides

Some features also have their own placeholders that are not part of this engine, such as {count} in counter names or {number} in ticket names. They are listed in Placeholders of one feature. Timers send their text exactly as written, with no variables.

Every message

User

The member the message is about: who joined, who wrote the trigger, who leveled up, who used the command.

Variable	What it gives	Example
`{user}`	Mentions the member	@Liam
`{user.mention}`	Mentions the member (same as `{user}`)	@Liam
`{user.name}`	Username	liam
`{user.id}`	User ID	293504726505357312
`{user.avatar}`	Avatar link (global)	`https://cdn.discordapp.com/avatars/…`
`{user.display_avatar}`	Server avatar, or the global one	`https://cdn.discordapp.com/…`
`{user.avatar_decoration}`	Picture of their avatar decoration, empty if none	`https://cdn.discordapp.com/…`
`{user.nameplate}`	Picture of their nameplate, empty if none	`https://cdn.discordapp.com/…`
`{user.server_tag}`	Their server tag text, empty if none	PTT
`{user.server_tag_badge}`	Picture of their server tag badge, empty if none	`https://cdn.discordapp.com/…`
`{user.display_name}`	Name in this server (nickname, or username)	Liam
`{user.joined_at}`	Date they joined this server	10/19/2026
`{user.joined_at_timestamp}`	That date as a unix number	1792368000
`{user.created_at}`	Date the account was made	7/1/2020
`{user.created_at_timestamp}`	That date as a unix number	1593561600
`{user.account_age}`	How old the account is	6 years
`{user.account_age_days}`	The same, in days	2300
`{user.joined_age}`	How long they have been in this server	3 months
`{user.boost}`	Whether they boost the server	Yes / No
`{user.boost_since}`	Date they started boosting	7/1/2026, or Not boosting
`{user.boost_since_timestamp}`	That date as a unix number, empty if not boosting	1782864000
`{user.color}`	Color of their highest colored role, as hex	#f0a88f
`{user.top_role}`	Name of their highest role	Booster
`{user.role_list}`	All their roles, as mentions	@Member, @Booster
`{user.bot}`	Whether the account is a bot	No
`{user.join_position}`	Which member they were, by join date	1204
`{user.join_position_suffix}`	The same, with its ending	1204th

chu creates an embed with {user.*} variables and Petto shows it filled: chu's mention, username, ID, join date and position, top role, color, roles and No for boosting — In Discord: a saved embed made from a code with the User variables, filled with chu.

Turn the _timestamp numbers into a date that shows in each reader’s own time zone: <t:{user.created_at_timestamp}:R> gives “6 years ago”, <t:{user.joined_at_timestamp}:D> gives “October 19, 2026”.

User (legacy)

The original names. They still work and give the same as their dot version.

Variable	What it gives	Example
`{user_tag}`	Username (same as `{user.name}`)	liam
`{user_name}`	Username	liam
`{user_avatar}`	Avatar link	`https://cdn.discordapp.com/avatars/…`
`{user_id}`	User ID	293504726505357312
`{user_discrim}`	Old discriminator, `0` on new usernames	0
`{user_nick}`	Name in this server	Liam
`{user_joindate}`	Date they joined this server	10/19/2026
`{user_createdate}`	Date the account was made	7/1/2020
`{user_displaycolor}`	Highest role color as hex (`#000000` if none)	#f0a88f
`{user_boostsince}`	Date they started boosting	Not boosting

chu creates an embed with {user_name}, {user_nick} and the other legacy names, and Petto fills them, with Not boosting at the end — In Discord: the legacy names give the same data.

Server

Variable	What it gives	Example
`{server_name}`	Server name	Cozy Corner
`{server_id}`	Server ID	707307527846625280
`{server_prefix}`	In custom commands, the prefix that was typed. Elsewhere it shows `/`	!
`{server_membercount}`	Members, bots included	1204
`{server_membercount_ordinal}`	The same with its ending	1204th
`{server_membercount_nobots}`	Members without bots	1198
`{server_membercount_nobots_ordinal}`	The same with its ending	1198th
`{server_botcount}`	Bots	6
`{server_botcount_ordinal}`	Bots with the ending	6th
`{server_icon}`	Server icon link	`https://cdn.discordapp.com/icons/…`
`{server_rolecount}`	Roles	38
`{server_channelcount}`	Channels	54
`{server_randommember}`	Mentions a random member	@Mia
`{server_randommember_tag}`	Username of a random member	mia
`{server_randommember_nobots}`	Mentions a random member who is not a bot	@Noah
`{server_owner}`	Mentions the owner	@Ana
`{server_owner_id}`	Owner’s ID	1100000000000000001
`{server_createdate}`	Date the server was made	7/1/2020
`{server_boostlevel}`	Boost level, 0 to 3	2
`{server_boostcount}`	Boosts	9
`{server_nextboostlevel}`	The next boost level (3 at most)	3
`{server_nextboostlevel_required}`	Boosts that level needs (2, 7 or 14)	14
`{server_nextboostlevel_until_required}`	Boosts still missing for it	5

Petto fills the owner, the creation date, 1840 members with people and bots counted apart, the boosts and a random member — In Discord: the Server variables with the numbers of Petto Land.

The counts without bots, the bot count, the join position and the random member are worked out from the members Petto has loaded. On very large servers they can be a little off.

Guild

Dot versions of the server data, plus a few extras.

Variable	What it gives	Example
`{guild.name}`	Server name	Cozy Corner
`{guild.id}`	Server ID	707307527846625280
`{guild.count}`	Members	1204
`{guild.icon}`	Icon link, `N/A` if none	`https://cdn.discordapp.com/icons/…`
`{guild.banner}`	Banner link, `N/A` if none	N/A
`{guild.owner_id}`	Owner’s ID	1100000000000000001
`{guild.created_at}`	Date the server was made	7/1/2020
`{guild.created_at_timestamp}`	That date as a unix number	1593561600
`{guild.emoji_count}`	Custom emojis	42
`{guild.role_count}`	Roles	38
`{guild.boost_count}`	Boosts	9
`{guild.boost_tier}`	Boost level in words	Level 2, or No Level
`{guild.channels_count}`	Channels	54
`{guild.vanity}`	Vanity invite, `N/A` if none	discord.gg/cozy
`{guild.region}`	The server’s language setting	en-US
`{guild.max_members}`	Member limit	500000

Channel

The channel the message is sent in (for a DM on join, the DM).

Variable	What it gives	Example
`{channel}`	Mentions the channel	#general
`{channel.mention}`	Mentions the channel	#general
`{channel.name}`	Channel name	general
`{channel.id}`	Channel ID	1498210265458675853
`{channel.topic}`	Channel topic, `N/A` if none	Say hi!
`{channel_name}`	Channel name (legacy)	general
`{channel_createdate}`	Date the channel was made (legacy)	7/1/2020

chu creates the embed in general and Petto fills the mention, name, ID and topic of general — In Discord: the Channel variables for the channel the message is in.

Invites

Only in welcome messages and DM on join: the invite the new member used. Petto needs Manage Server to see invites.

Variable	What it gives	Example
`{inviter}`	Mentions who invited them, or Unknown	@Mia
`{inviter.name}`	Display name of who invited them, or Unknown	Mia
`{inviter.id}`	ID of who invited them	1100000000000000002
`{inviter.invites}`	How many invites that person has now	12
`{invite.code}`	The code of the invite	cozy

Petto welcomes Mia in the welcome channel, invited by kira who now has 12 invites, with the code of the invite — In Discord: a welcome with the Invites variables.

Date and time

Variable	What it gives	Example
`{date}`	Today’s date, Colombia time (GMT-5)	10/19/2026
`{date.now}`	Same as `{date}`	10/19/2026
`{date.utc_now}`	Date and time in UTC	Mon, 19 Oct 2026 17:00:00 GMT
`{date.utc_timestamp}`	Right now as a unix number	1792429200
`{timestamp}`	Right now, shown in each reader’s own time zone	October 19, 2026 12:00 PM
`{timestamp.unix}`	Right now as a unix number, to build your own `<t:…>`	1792429200
`{timestamp.short_time}`	Hour and minutes	12:00 PM
`{timestamp.long_time}`	Hour, minutes and seconds	12:00:00 PM
`{timestamp.short_date}`	Short date	10/19/2026
`{timestamp.long_date}`	Long date	October 19, 2026
`{timestamp.full}`	Date and time	October 19, 2026 12:00 PM
`{timestamp.full_long}`	Weekday, date and time	Monday, October 19, 2026 12:00 PM
`{timestamp.short_datetime}`	Short date and time	10/19/2026, 12:00 PM
`{timestamp.medium_datetime}`	Short date and time with seconds	10/19/2026, 12:00:00 PM
`{timestamp.relative}`	”just now”, and it keeps counting	5 minutes ago
`{timestamp:<when>\|<style>}`	Any moment you write, in any style	see below

Petto fills today's date, the current time and how long ago, a time in 2 hours and the New Year party on December 31 — In Discord: {date}, {timestamp} and two written moments; the timestamps show in each reader's time zone.

{timestamp:…} reads the moment the way you would say it: in 2h, 3d 4h, tomorrow 8pm, today 18:30, 2026-12-31 23:59, a unix number or a Discord timestamp. Times are read in Colombia time (GMT-5), unless they end in utc (2026-12-31 23:59 utc). After | comes the style: short_time, long_time, short_date, long_date, full, full_long, short_datetime, medium_datetime or relative (or Discord’s letters t T d D f F s S R). Without a style it is full. A moment Petto can’t read gives nothing.

Examples

Event starts {timestamp:2026-12-31 18:00|full_long} ({timestamp:2026-12-31 18:00|relative})
→ Event starts Thursday, December 31, 2026 6:00 PM (in 2 months)

Doors open {timestamp:in 2h|R}
→ Doors open in 2 hours

Discord timestamps (all the {timestamp…} variables) are drawn in the message text, embed descriptions and fields. In embed titles, footers and author names Discord shows the raw <t:…> code instead, so use {date} there.

Functions

Variable	What it gives	Example
`{choose:a\|b\|c}`	One of the options at random, picked again every time	b
`{range:1-100}`	A random whole number from the first to the second	42
`{newline}`	A line break, useful in commands where you can’t press Enter
`{separator}`	A divider line	──────────────────────

Petto shows a dice result, a divider line and one of three games chosen at random — In Discord: {range}, {separator}, {choose} and {newline}.

{choose1:…}, {choose2:…} and so on work the same, if you like to number them. Each one is picked on its own.

Actions and pictures

Variable	What it does
`{reactreply:emoji}`	Petto reacts with that emoji to the message it sends. Repeat it for more reactions (`{reactreply:👍}{reactreply:👎}`). If the reply is only this, Petto reacts to the message that set it off instead. Works in custom commands, autoresponders, level-ups, welcome, leave and boost messages, sticky messages, panels and saved embeds
`{imgcard:name}`	Draws the image card called `name` and puts it in the first embed (or at the top of a V2 design). `{imgcard:name\|attachment}` sends the picture on its own. Only the first one counts, and the token itself is removed from the text

A pizza or tacos vote by Petto in general with the reactions 🍕 and 🌮 under it — In Discord: a saved embed with two {reactreply:...}: Petto reacts to its own message.

Names from other bots

These names, used by other bots, also work and give the same as the Petto variable they point to. They are read in any case.

Name	Same as
`{boost.count}`	`{server_boostcount}`
`{boost.level}`, `{boost.tier}`	`{server_boostlevel}`
`{boost.next_level}`	`{server_nextboostlevel}`
`{boost.required}`	`{server_nextboostlevel_required}`
`{boost.remaining}`, `{boost.until_next}`	`{server_nextboostlevel_until_required}`
`{level.new_rank}`, `{level.new_level}`	`{level}`
`{level.old_rank}`, `{level.old_level}`	`{level_previous}`
`{level.user_xp}`	`{level_xp}`
`{level.user_rank}`	`{level_rank}`
`{guild.members}`, `{guild.member_count}`	`{guild.count}`
`{server.member_count}`	`{server_membercount}`
`{user.joined}`	`{user.joined_at}`
`{user.created}`	`{user.created_at}`

chu uses {mention}, {username}, {server}, {server.members} and {boost.*} and Petto fills them — In Discord: names from other bots work like their Petto variable.

Variables for one event

Triggering message

The message that set the reply off. Works in autoresponders, custom commands, auto-thread and text level-ups.

Variable	What it gives	Example
`{message_link}`	Link to that message	`https://discord.com/channels/…/…/…`
`{message_id}`	Its ID	1498210265458675853
`{message_content}`	Its text	good morning everyone

nova says good morning and Petto answers quoting {message_content} with the link of the message — In Discord: an autoresponder that quotes the message that set it off.

Command arguments

What the member typed after the command name in a custom command, or after the trigger in an autoresponder. Text in quotes counts as one argument. Mentions typed by the member never ping anyone through these. The examples are for !hug Mia "big world" now:

Variable	What it gives	Example
`{args}`	Everything after the command, as typed	Mia “big world” now
`{arguments}`, `{args_raw}`	Same as `{args}`	Mia “big world” now
`{arg1}` … `{arg10}`	One argument, by position	`{arg2}` → big world
`{args_from:N}`	Every argument from position N	`{args_from:2}` → big world now
`{arg_count}`	How many arguments	3
`{command_name}`	The command used (the trigger, in an autoresponder)	hug
`{prefix}`	The prefix used (empty in an autoresponder)	!

kira types !hug with Mia, a quoted text and a word, and Petto fills {arg1}, {arg_count}, {args}, {args_from:2} and the command — In Discord: a custom command with its arguments.

Leveling

In the level-up message, its saved embed, and rank cards.

Variable	What it gives	Example
`{level}`	The level reached	12
`{level_next}`	The next level	13
`{level_previous}`	The level before	11
`{level_xp}`	Total XP	23,450
`{level_xp_current}`	XP earned inside this level	1,420
`{level_xp_needed}`	XP this level takes to finish	2,350
`{level_xp_to_next}`	XP still missing for the next level	930
`{level_progress}`	Progress to the next level, 0 to 100	60
`{level_bar}`	A progress bar of 10 segments	▰▰▰▰▰▰▱▱▱▱
`{level_rank}`	Place on the leaderboard	3
`{level_rank_total}`	Members on the leaderboard	120
`{level_top_percent}`	The top percent they are in, one decimal	2.5
`{level_streak}`	Days in a row with activity	4
`{level_messages}`	Messages counted	3,210
`{level_voice_minutes}`	Minutes in voice counted	540
`{level_type}`	`text` or `voice`	text
`{level_role}`	The reward role just earned, as a mention (empty if none)	@Level 10
`{level_role_name}`	The name of that role	Level 10

Petto says chu reached level 12, with a bar of 10 segments, the XP missing, the rank 3 of 120 and the Regular role — In Discord: a level-up message with its progress bar and reward role.

In the level-up text (not in saved embeds), {EMOJI} is replaced by Petto’s star icon.

Giveaways

In giveaway messages and their saved embeds.

Variable	What it gives	Example
`{gw.prize}`	The prize	Discord Nitro
`{gw.winners}`	Number of winners	3
`{gw.winner_text}`	The winners line	3 lucky winners!
`{gw.entries}`	Entries so far	87
`{gw.host}`	Mentions the host	@Ana
`{gw.host_name}`	Host’s username	ana
`{gw.host_avatar}`	Host’s avatar link	`https://cdn.discordapp.com/avatars/…`
`{gw.ends}`	When it ends, relative	in 2 days
`{gw.timestamp}`	Same as `{gw.ends}`	in 2 days
`{gw.duration}`	The end as a unix number, for your own `<t:…>`	1792602000
`{gw.claim_time}`	Time a winner has to claim (in the claim message)	10 minutes
`{gw.reaction}`	The entry emoji in reaction mode	🎉
`{gw.entry_mode}`	`react with` or `click on`	click on
`{gw.entry_text}`	How to enter	Click the button below to enter!
`{gw.status}`	`Active` or `Ended`	Active
`{gw.preset}`	The bonus entries of the preset, one per line	@Booster — +2 entries

Petto announces that Luna won Discord Nitro out of 87 entries, hosted by liam, 1 lucky winner, Ended — In Discord: a winner message made from a saved embed with {gw.*}.

The winner message is used when there is no claim time; with one, the claim message is sent instead. In winner, claim, accept and deny messages {user} is the winner. In the giveaway message itself there is no member, so use {gw.host}.

Bump reminder

Variable	What it gives	Example
`{user.mention}`	Who bumped (in the thank-you message)	@Liam
`{nextBump}`	When the next bump is allowed, relative	in 2 hours

Petto thanks chu for the bump and says the next one is in 2 hours — In Discord: the bump thank-you with {nextBump}.

Sanctions

In sanction messages: the DM, the reply and the log entry.

Variable	What it gives	Example
`{case.id}`	Case number (empty in the DM of a ban or kick, sent before the case exists)	42
`{case.type}`	`ban`, `hardban`, `tempban`, `softban`, `unban`, `kick`, `mute`, `tempmute`, `unmute`, `warn`, `jail` or `unjail`	tempban
`{case.action}`	The action in words	temporarily banned
`{case.emoji}`	The icon of the action	🔨
`{case.reason}`	The reason	Breaking rule 3
`{case.duration}`	How long it lasts, `Permanent`, or `N/A`	7 days
`{case.expires}`	When it ends, relative, or `Never`	in 7 days
`{case.expires_at}`	When it ends as a date and time, or `Never`	October 26, 2026 12:00 PM
`{case.source}`	Who applied it	A moderator, Automod, The honeypot, Warn escalation, Automatic expiry, Anti-nuke
`{case.moderator}`	Mentions the moderator	@Ana
`{case.moderator_name}`	Moderator’s name	ana
`{case.moderator_id}`	Moderator’s ID	1100000000000000001
`{case.moderator_avatar}`	Moderator’s avatar link	`https://cdn.discordapp.com/…`
`{case.user}`	Mentions the sanctioned member	@Liam
`{case.user_name}`	Their name	liam
`{case.user_id}`	Their ID	293504726505357312
`{case.user_avatar}`	Their avatar link	`https://cdn.discordapp.com/…`
`{case.appeal}`	Link to appeal this sanction, empty if appeals are off or this kind can’t be appealed	`https://petto.sbs/appeal/…`

In a DM Petto tells Bruno he was temporarily banned from Petto Land: case 42, the reason, 7 days, the moderator and the appeal link — In Discord: a ban DM made from a saved embed with {case.*}.

Starboard

In the starboard repost design.

Variable	What it gives	Example
`{star.count}`	Stars	5
`{star.emoji}`	The starboard emoji	⭐
`{star.channel}`	Mentions the channel of the message	#memes
`{star.channel_name}`	Its name	memes
`{star.link}`	Link to the message	`https://discord.com/channels/…`
`{star.message_id}`	ID of the message	1498210265458675853
`{star.author}`	Mentions the author	@Liam
`{star.author_name}`	Author’s name	liam
`{star.author_id}`	Author’s ID	293504726505357312
`{star.author_avatar}`	Author’s avatar link	`https://cdn.discordapp.com/…`
`{star.content}`	The text (`No text content` if none)	this is the best meme
`{star.image}`	First picture, empty if none	`https://cdn.discordapp.com/attachments/…`
`{star.attachments}`	Links to the other files	`[photo.png](https://…)`
`{star.time}`	When it was sent	October 19, 2026 12:00 PM

Petto reposts nova's meme with 7 stars, the channel, the text, the link and when it was sent — In Discord: a starboard repost made from a saved embed with {star.*}.

Monkeyboard

The same as the starboard, for the monkeyboard: {monkey.count}, {monkey.emoji}, {monkey.channel}, {monkey.channel_name}, {monkey.link}, {monkey.message_id}, {monkey.author}, {monkey.author_name}, {monkey.author_id}, {monkey.author_avatar}, {monkey.content}, {monkey.image}, {monkey.attachments} and {monkey.time}.

Clownboard

The same as the starboard, for the clownboard: {clown.count}, {clown.emoji}, {clown.channel}, {clown.channel_name}, {clown.link}, {clown.message_id}, {clown.author}, {clown.author_name}, {clown.author_id}, {clown.author_avatar}, {clown.content}, {clown.image}, {clown.attachments} and {clown.time}.

Suggestions

In the design of a suggestion.

Variable	What it gives	Example
`{suggestion.id}`	The ID	si2tr-foytm
`{suggestion.number}`	Number in this server	12
`{suggestion.content}`	The text	Add a music channel
`{suggestion.image}`	Picture link, empty if none	`https://cdn.discordapp.com/…`
`{suggestion.status}`	`pending`, `approved`, `denied`, `considering` or `implemented`	approved
`{suggestion.status_label}`	The status in words, empty while pending	Approved
`{suggestion.reason}`	The staff’s reason	Coming this week!
`{suggestion.staff}`	Mentions who answered	@Ana
`{suggestion.staff_name}`	Their name	ana
`{suggestion.author}`	Mentions who suggested it	@Liam
`{suggestion.author_name}`	Their name	liam
`{suggestion.author_id}`	Their ID	293504726505357312
`{suggestion.author_avatar}`	Their avatar link	`https://cdn.discordapp.com/…`
`{suggestion.up}` / `{suggestion.down}`	Votes for / against	8 / 1
`{suggestion.up_emoji}` / `{suggestion.down_emoji}`	The vote emojis	✅ / ❌
`{suggestion.score}`	For minus against	7
`{suggestion.percent}`	Percent in favor, 0 to 100	89
`{suggestion.link}`	Link to the message	`https://discord.com/channels/…`
`{suggestion.channel}`	Mentions the channel	#suggestions
`{suggestion.thread}`	Mentions the thread, empty if none	#Thread for suggestion si2tr-foytm
`{suggestion.created}`	When it was made, relative	5 days ago
`{suggestion.created_time}`	When it was made, date and time	October 14, 2026 5:00 PM

Suggestion 12 by Mia, approved, with the votes, the percent and kira's answer — In Discord: a suggestion design with {suggestion.*}.

Confessions

In the design of a confession.

Variable	What it gives	Example
`{confession.id}`	The ID	si2tr-foytm
`{confession.number}`	Number in this server	12
`{confession.content}`	The text	I still sleep with the light on.
`{confession.image}`	Picture link, empty if none	`https://cdn.discordapp.com/…`
`{confession.link}`	Link to the message	`https://discord.com/channels/…`
`{confession.channel}`	Mentions the channel	#confessions
`{confession.created}`	When it was made, relative	5 days ago
`{confession.created_time}`	When it was made, date and time	October 14, 2026 5:00 PM

Confession 12 with its text, its ID and when it was sent — In Discord: a confession design with {confession.*}.

Polls

In the design of a poll. The vote buttons are added under it.

Variable	What it gives	Example
`{poll.question}`	The question	What should we build next?
`{poll.options}`	The options, one per line, with their letter	🇦 A new command …
`{poll.results}`	Each option with a bar, percent and votes	🇦 A new command ████████░░░░ 67% (4) …
`{poll.votes}`	People who voted	6
`{poll.votes_text}`	The votes in words	6 votes
`{poll.type}`	Single or multiple choice	Single choice
`{poll.status}`	`Open` or `Closed`	Open
`{poll.ends}`	When it closes, relative (empty if never)	in 2 hours
`{poll.image}`	Picture of the poll, if any	`https://…`
`{poll.host}`	Mentions who started it	@Ana
`{poll.winner}`	The option with most votes (empty on a tie or with no votes)	A new command

A poll with two options and their bars, 6 votes, single choice, open, closing in 2 hours, started by liam — In Discord: a poll design with {poll.*}.

Partners

In the replies of Partners.

Variable	What it gives	Example
`{partner.name}`	Partner server’s name	Cozy Club
`{partner.id}`	Its ID	1100000000000000001
`{partner.members}`	Its members	1,240
`{partner.invite}`	The invite that was posted	`https://discord.gg/cozy`
`{partner.manager}`	Mentions the Partner Manager	@Liam
`{partner.manager_name}`	Their name	liam
`{partner.count_day}` / `{partner.count_week}` / `{partner.count_total}`	Partnerships of the manager today / this week / in total	1 / 4 / 21
`{partner.rank_week}` / `{partner.rank_total}`	Place of the manager this week / in total	2 / 3
`{partner.top_week}` / `{partner.top_week_count}`	Best manager this week and their count	@Mia / 6
`{partner.top_total}` / `{partner.top_total_count}`	Best manager in total and their count	@Ana / 48
`{partner.server_day}` / `{partner.server_week}` / `{partner.server_total}`	Partnerships of the whole server	2 / 9 / 87
`{partner.min_members}`	Members a partner server needs	100
`{partner.min_age_days}`	Days old it needs to be	14
`{partner.cooldown_days}`	Days before the same server can partner again	7
`{partner.cooldown_ends}`	When that wait ends	in 3 days
`{partner.cooldown}`	The wait as text	3d 4h

Petto announces the partner Cozy Club with 1,240 members and thanks Chillet, with this week's count and rank — In Discord: a partner reply with {partner.*}.

Requests

In the answer to who makes a request.

Variable	What it gives	Example
`{request.number}`	Number of the request	12
`{request.text}`	What was asked for	A banner for my server
`{request.link}`	Link to the request card	`https://discord.com/channels/…`
`{request.channel}`	Channel where the staff sees it	#requests
`{request.status}`	Its state	Open

Petto tells Mia that her request 12 for a banner is open and where the staff sees it — In Discord: the answer to a request with {request.*}.

Forms

In the saved embed of a form message (sent, accepted, denied).

Variable	What it gives	Example
`{form.name}`	Short name of the form	staff
`{form.title}`	Title of the form	Staff application
`{form.number}`	Number of the submission	12
`{form.status}`	State of the submission	Accepted
`{form.reason}`	The reviewer’s reason	Great answers

In a DM Petto tells Mia that her staff application 12 was accepted, with the reason — In Discord: a form answer by DM with {form.*}.

Honeypot

In the message of a honeypot channel.

Variable	What it gives	Example
`{honeypot.action}`	What happens to who writes there	a softban
`{honeypot.count}`	Members caught so far	17
`{honeypot.channel}`	Mentions the bait channel	#do-not-write

Petto warns not to write in the bait channel, that writing there gets a softban, and that 17 were caught — In Discord: the message of a honeypot channel with {honeypot.*}.

Counter milestones

In the saved embed of a counter milestone. The plain text of the announcement uses the short forms.

Variable	What it gives	Example
`{counter.count}`	Members now	1,000
`{counter.goal}`	The member number reached	1,000
`{counter.server}`	Server name	Cozy Corner

Petto celebrates that Petto Land reached 1,800 members and has 1,840 now — In Discord: a milestone embed with {counter.*}.

Verification

Variable	What it gives	Example
`{verify.link}`	The link the member opens to verify	`https://petto.sbs/verify/…`

In a DM Petto asks Mia to verify with the link to enter Petto Land — In Discord: the verification DM with {verify.link}.

Vanity and Server Tag

In the thank-you messages and the log of Vanity and Server Tag rules.

Variable	What it gives	Example
`{rule.name}`	Name of the rule that matched	supporters
`{rule.source}`	`vanity` or `guildtag`	vanity
`{rule.value}`	What the rule looks for	discord.gg/cozy
`{rule.condition}`	The rule’s condition	contains
`{rule.reason}`	Why it matched	Matched custom_status …
`{rule.role}`	Mentions the rule’s role	@Supporter
`{rule.role_id}`	That role’s ID	1010101010101010101
`{rule.action}`	`add_role` or `remove_role`	add_role
`{rule.action_text}`	`add` or `remove`	add
`{rule.result}`	`completed` or `error`	completed
`{rule.error}`	The error, if the role couldn’t change
`{rule.matched_value}`	What the member has that matched	join discord.gg/cozy
`{rule.event}`	Name of the log event	vanity_add
`{rule.event_title}`	Title of that event	Vanity role added
`{vanity.rule}`	Name of the Vanity rule	supporters
`{vanity.word}`	The text it looks for	discord.gg/cozy
`{vanity.source}`	Where it looks	custom_status
`{vanity.value}`	What the member has set	join discord.gg/cozy
`{vanity.role}`	Mentions its role	@Supporter
`{tag}`	The member’s Server Tag	COZY
`{tag.rule}`	Name of the Server Tag rule	wear-our-tag
`{tag.condition}`	Its condition	is_guild_id
`{tag.rule_value}`	The value it compares	707307527846625280
`{tag.guild_id}`	Server the tag belongs to	707307527846625280
`{tag.enabled}`	Whether the member shows the tag	true
`{tag.badge}`	Badge of the tag	badge
`{tag.role}`	Mentions its role	@Tag wearer

Petto thanks chu for having cinnamochi in the status, gives the Rep role and shows the status, the rule and the action — In Discord: a Vanity thank-you made from a saved embed with {rule.} and {vanity.}.

Rollouts

In Rollout alerts about Discord experiments.

Variable	What it gives	Example
`{rollout.name}`	Name of the experiment
`{rollout.id}`	Its ID
`{rollout.kind}`	Kind of experiment	Users experiment
`{rollout.type}`	What changed	Rollout increased
`{rollout.status}`	Its state	Rolling out
`{rollout.percent}`	Share of Discord that has it	50%
`{rollout.from}` / `{rollout.to}`	Share before / now (from is empty for a new one)	37.5% / 50%
`{rollout.change}`	The change (empty for a new one)	+12.5%
`{rollout.badge}`	Short text for the button	+12.5% (50%)
`{rollout.kind_icon}` / `{rollout.event_icon}`	Petto’s icon for the kind / the event
`{rollout.variants}`	One line per variant with its change
`{rollout.ranges}`	Ranges of each variant
`{rollout.platforms}`	Where it applies	android, desktop
`{rollout.filters}`	Filters of the experiment, if any
`{rollout.source}`	Where the data comes from

Petto says an experiment went from 37.5% to 50%, with its kind, status, platforms and ID — In Discord: a Rollout alert made from a saved embed with {rollout.*}.

Quests

In the saved embeds of Quest alerts. There are many, so they’re folded.

All quest variables (113)

Variable	What it gives	Example
`{quest.name}`	Name of the quest	Watch the trailer
`{quest.game}`	The game or brand	March of Giants
`{quest.publisher}`	Who published it	Ubisoft
`{quest.id}`	ID of the quest	1552897885883072582
`{quest.url}`	Link to accept it in Discord	`https://discord.com/quests/…`
`{quest.link}`	Link to the game page, empty if none	`https://example.com/game`
`{quest.image}` / `{quest.logo}`	Banner / logo, empty if none
`{quest.color}`	Main color as hex	#4752c4
`{quest.reward}`	The rewards, with their type	200 Orbs
`{quest.reward_type}`	Type of the first reward: Orbs, Collectible, Code…	Orbs
`{quest.reward_amount}`	Orbs, empty if the reward is not Orbs	200
`{quest.reward_image}`	Picture of the first reward
`{quest.reward_name}`	Name of the first reward	200 Orbs
`{quest.rewards_count}`	How many rewards	1
`{quest.reward_types}`	Every kind of reward	Orbs, Collectible
`{quest.reward_nitro_amount}`	Orbs a Nitro member gets	240
`{quest.reward_expires}`	When the first expiring reward expires, relative
`{quest.task}`	The first task	Watch a video
`{quest.task_type}`	Kind of task: `video`, `play`, `stream`, `activity`	video
`{quest.task_minutes}` / `{quest.task_seconds}` / `{quest.task_time}`	Length of the first task	2 / 120 / 2 min
`{quest.tasks}`	Every task with its time	Watch a video (2 min)
`{quest.platforms}`	Where it can be done	Desktop, Mobile
`{quest.starts}` / `{quest.starts_at}`	Start, relative / as date and time	1 day ago / Oct 1, 2026 5:00 PM
`{quest.expires}` / `{quest.expires_at}`	End, relative / as date and time	in 5 days / Oct 7, 2026 5:00 PM
`{quest.starts.<style>}` / `{quest.expires.<style>}`	Start / end in a Discord style: `relative`, `short_time`, `long_time`, `short_date`, `long_date`, `full`, `full_long`, `short_datetime`, `medium_datetime`, or `unix` for your own `<t:{quest.expires.unix}:R>`	`{quest.expires.long_date}` → October 8, 2026
`{quest.starts_ago}` / `{quest.expires_in}`	Start / end in plain words, for titles and footers	2 days ago / in 5 days
`{quest.starts_date}` / `{quest.expires_date}`	Date in plain text (UTC)	Oct 1, 2026
`{quest.starts_datetime}` / `{quest.expires_datetime}`	Date and time in plain text (UTC)	Oct 1, 2026, 5:00 PM UTC
`{quest.duration}`	How long the quest lasts	7 days
`{quest.time_left}`	Time left, or `Ended`	5 days 3 hours
`{quest.days_left}` / `{quest.hours_left}`	Whole days / hours left	5 / 123
`{quest.countries}` / `{quest.excluded_countries}`	Country codes it’s only for / not available in
`{quest.orbs.<field>}`, `{quest.decoration.<field>}`, `{quest.code.<field>}`, `{quest.ingame.<field>}`, `{quest.nitro.<field>}`	The reward of that kind, empty if the quest has none. Fields: `name`, `type`, `image`, `amount` (Orbs only), `nitro_amount`, `expires`	`{quest.orbs.amount}` → 200
`{quest.reward1.<field>}` to `{quest.reward3.<field>}`	First, second and third reward, same fields	`{quest.reward2.name}` → Cool frame
`{quest.limits}`	Region and age limits, or None	None
`{quest.age_gate}`	`18+` when it has an age limit
`{quest.status}`	`New quest` or `Ending soon`	New quest
`{quest.source}`	Where the data comes from	discordquest.com

Petto announces a new quest: the game, the publisher, 200 Orbs for watching a video of 2 minutes, the platforms, when it ends and the link — In Discord: a Quest alert made from a saved embed with {quest.*}.

Feeds

In the words above each notice of a feed (!feed message). They only work there.

Variable	What it gives	Example
`{feed.title}`	Title of the post, video or stream	We built a new feature today
`{feed.url}`	Link to what was published	`https://www.youtube.com/watch?v=…`
`{feed.author}`	Name of the account	Petto Studio
`{feed.description}`	Description, empty if none
`{feed.platform}`	Name of the platform	YouTube
`{feed.image}`	Link of the cover picture, empty if none

Petto says there is a new YouTube video, with its title, the account and the link — In Discord: the words above a feed notice with {feed.*}.

Placeholders of one feature

These short placeholders are filled by the feature itself, not by the engine above. They only work in the place listed. Where the table says yes under “Variables too”, the regular variables also work in that same text.

Where	Placeholders	Variables too
Counter names and topics	`{count}` `{goal}` `{left}` `{percent}` `{role}` `{tz}` (old: `{value}` `{remaining}` `{option}`)	no
Counter milestone text	`{count}` `{goal}` `{milestone}` `{server}` and `{counter.count}` `{counter.goal}` `{counter.server}`	no
Ticket channel names	`{number}` `{username}` `{userid}` `{category}`	no
Ticket welcome text and quick replies	`{user}` `{username}` `{category}` `{server}` `{number}`	no
Ticket staff hours message	`{start}` `{end}` `{timezone}`	no
Form messages	`{form}` `{number}` `{server}` `{status}` `{reason}`	yes
Appeal messages	`{username}` `{server}` `{reason}` `{form}` `{link}`	no
Appeal line in the sanction DM	`{server}` `{link}`	no
Birthday message	`{age}`, the age the member turns (empty without a year)	yes, except in a saved embed, where `{age}` doesn’t work
Level-up text	`{EMOJI}`, Petto’s star icon	yes
VoiceMaster channel names	`{user}` and `{user.name}` (username), `{user.display_name}`	no
Suggestion thread name	`{suggestion.id}` `{suggestion.number}` `{suggestion.status}`	no
Command aliases	`{0}`, `{1}`, … the words typed after the alias	no
Sticky message text	`{newline}` `{separator}`	only through a saved embed

Counters

A counter name is any text with {count}. Discord allows 100 characters in a channel name and 1,024 in a topic.

Placeholder	What it gives	Example
`{count}`	The value, in the counter’s format (`plain`, `grouped`, `compact`)	1204 / 1,204 / 1.2k
`{goal}`	The next goal (goal counters)	1,250
`{left}`	How many are missing for it	46
`{percent}`	How far it is	96%
`{role}`	Name of the counter’s role (role counters)	Staff
`{tz}`	The time zone of a clock	UTC, GMT+2, CEST

Examples

!counter create humans "👤 People: {count}"
!counter create goal "🎯 {count}/{goal} ({percent})"
!counter edit #members template "🌸 {count} members, {left} to go"

The milestone text takes {count} (members now), {goal} or {milestone} (the number reached) and {server}, with numbers grouped (1,000):

Example

!counter announce message 🎉 We just hit {goal} members in {server}!

Tickets

Placeholder	Where	What it gives	Example
`{number}`	names, welcome, quick replies	Ticket number with 4 digits	0042
`{username}`	names, welcome, quick replies	Opener’s username	liam
`{userid}`	names	Opener’s ID	293504726505357312
`{category}`	names, welcome, quick replies	The category’s label	Support
`{user}`	welcome, quick replies	Mentions the opener	@Liam
`{server}`	welcome, quick replies	Server name	Cozy Corner
`{start}` `{end}` `{timezone}`	staff hours message	The staff hours	09:00, 18:00, America/Bogota

Channel names are made lowercase, accents and symbols become -, and they are cut at 90 characters: {category}-{username} gives support-liam. A saved embed as the ticket welcome uses the regular variables instead (the member is the opener, the channel is the ticket).

Examples

!ticket category edit support --naming "{category}-{username}-{number}"
!ticket category edit support --welcome "Hi {user}! Tell us what you need, ticket #{number} is all yours."
!quickreply add closing "Thanks {username}! If everything is solved, we'll close ticket {number} soon."

Forms and appeals

Form messages (the DM after sending, accepting or denying, set with !form message) take {form} (the title), {number}, {server}, {status} and {reason}, and the regular variables too, so {user} mentions the member. A saved embed for those messages uses the Forms group instead. Appeal messages (set in the dashboard) take {username}, {server}, {reason}, {form} and {link} (the status page of the appeal). The “sent” message and the staff reply notice only fill {server}, and the thread name only {username}. The line about appeals in a sanction DM takes {server} and {link}; if it has no {link}, the link is added at the end.

Recipes

Copy-paste ready. Each one says where it goes and what the member sees.

Welcome with member number and inviter

Command

!welcome setup #welcome --message "Welcome {user} to **{server_name}**! You're our {user.join_position_suffix} member. Invited by {inviter.name} ({inviter.invites} invites)."

Result

Welcome @Liam to Cozy Corner! You're our 1204th member. Invited by Mia (12 invites).

Level-up with a progress bar and reward

Command

!level notify reply --message "{EMOJI} {user} reached level **{level}**! {level_bar} {level_xp_to_next} XP to level {level_next}."

Result

✦ @Liam reached level 12! ▰▰▰▰▰▰▱▱▱▱ 930 XP to level 13.

With --milestone 10 --message "{user} is level 10 and unlocked {level_role}!" that level gets its own text.

A hug command with a target

Command

!customcommand add hug "{user} gives {arg1} a big hug {choose:🤗|💞|🫂}"

Result

!hug @Mia  →  @Liam gives @Mia a big hug 💞

A dice roll

Command

!customcommand add roll "🎲 {user.display_name} rolled **{range:1-6}**"

Result

🎲 Liam rolled 4

Autoresponder that answers with what came after the trigger

Command

!autoresponder add say, {user.display_name} says: {args} --mode startsWith

Result

say good night everyone  →  Liam says: good night everyone

Account age in a welcome DM

Command

!dmonjoin setup --message "Hi {user.display_name}! Your account was made <t:{user.created_at_timestamp}:R>. Read the rules in {server_name} before chatting."

Result

Hi Liam! Your account was made 6 years ago. Read the rules in Cozy Corner before chatting.

Boost goal

Command

!boost setup #boosts --message "💎 {user} boosted! We have {server_boostcount} boosts, {server_nextboostlevel_until_required} more for level {server_nextboostlevel}."

Result

💎 @Liam boosted! We have 9 boosts, 5 more for level 3.

A ban DM with the appeal link (saved embed)

Make an embed called ban-dm from one code, then use it for the DM of bans:

Commands

!embed create ban-dm {embed}$v{title: {case.emoji} You were {case.action} from {server_name}}$v{description: **Reason:** {case.reason}{newline}**Ends:** {case.expires}{newline}{newline}Think it was a mistake? Appeal here: {case.appeal}}$v{color: #ed4245}
!sanctionmessage set ban dm ban-dm

The member gets an embed titled ”🔨 You were banned from Cozy Corner” with the reason, Never as the end and the appeal link.

Event countdown

Command

!customcommand add movienight "🍿 Movie night starts {timestamp:2026-12-19 18:00|full_long}, that's {timestamp:2026-12-19 18:00|R}!"

Result

🍿 Movie night starts Saturday, December 19, 2026 6:00 PM, that's in 2 months!

Each reader sees the time in their own time zone. The time you write is read in Colombia time (GMT-5); add utc to write it in UTC.

How variables resolve

Need logic or loops?

​Writing variables

​Where each group works

​Every message

​User

​User (legacy)

​Server

​Guild

​Channel

​Invites

​Date and time

​Functions

​Actions and pictures

​Names from other bots

​Variables for one event

​Triggering message

​Command arguments

​Leveling

​Giveaways

​Bump reminder

​Sanctions

​Starboard

​Monkeyboard

​Clownboard

​Suggestions

​Confessions

​Polls

​Partners

​Requests

​Forms

​Honeypot

​Counter milestones

​Verification

​Vanity and Server Tag

​Rollouts

​Quests

​Feeds

​Placeholders of one feature

​Counters

​Tickets

​Forms and appeals

​Recipes

Writing variables

Where each group works

Every message

User

User (legacy)

Server

Guild

Channel

Invites

Date and time

Functions

Actions and pictures

Names from other bots

Variables for one event

Triggering message

Command arguments

Leveling

Giveaways

Bump reminder

Sanctions

Starboard

Monkeyboard

Clownboard

Suggestions

Confessions

Polls

Partners

Requests

Forms

Honeypot

Counter milestones

Verification

Vanity and Server Tag

Rollouts

Quests

Feeds

Placeholders of one feature

Counters

Tickets

Forms and appeals

Recipes