Embed Scripting

A small scripting language for building embeds and buttons out of one string - live variables (member, server, channel, date/time), conditionals, and buttons, all resolved fresh every time the message is posted or re-rendered.

The basics

A script is one string made of directives separated by $v. Each directive looks like {name: content} (a few, like {timestamp}, take no content). Start the whole thing with {embed}$v to build a real embed instead of a plain text message:

{embed}$v{title: Server Rules}$v{description: Be nice to each other.}$v{color: #ff66aa}

Leave off the leading {embed}$v and use just {message: ...} to send plain text instead of an embed.

Directives

The four-part directives (author, footer, field, button) split their content on && - trailing parts can just be left out entirely if you don't need them.

Variables

Drop a {variable.name} anywhere inside a directive's content and it's replaced with the live value when the script renders. A bare {user} is shorthand for {user.display_name}.

Who {user.*} resolves to depends on context: on createembed/scripttest it's whoever ran the command; on a paginated page turn it's whoever clicked the reaction; on a manual pagination update/set/remove re-render it falls back to the message's original author.

Conditionals

{if COND}...{elseif COND}...{else}...{/if} - no nesting one inside another, but as many separate if-blocks in the same script as you want. A condition is a variable compared with ==/!=, or just the variable by itself as a truthy check (empty text, 0, false, none, and no all count as false).

{embed}$v{if {user.boost} == Yes}{description: Thanks for boosting, {user}!}{else}{description: Welcome, {user}!}{/if}

Buttons

{button: style && label && url && disabled && emoji} adds up to 5 buttons per row (Discord's own limit). style is one of link, blurple, green, grey/gray, or red. Only link buttons do anything on their own (they just open the URL) - a non-link button posted this way has no built-in action; click it and Pixie tells you so. To actually make one do something, attach a role to it with buttonrole add afterward. A link button with no real URL (left blank, or a variable that resolves empty) is dropped rather than breaking the whole message - scripttest/createembed tell you when that happens.

{embed}$v{title: Links}$v{button: link && Support Server && https://discord.gg/example}

The optional 5th field is an emoji - either a plain one (🥷) or a real custom server emoji in <:name:id> form. Combine with disabled (leaving url blank) for a decorative, non-clickable badge:

{button: grey && {guild.boost_count} && && disabled && <:boost_emoji:1534009361058500749>}

Multiple embeds in one message

Separate whole scripts with --add to post up to 10 embeds in a single message (Discord's own cap). Only the first segment's {message: ...} text is used; buttons from every segment are combined onto the same message.

{embed}$v{title: Page One} --add {embed}$v{title: Page Two}

Testing and posting

$scripttest <script>
$createembed <script>

Also $testscript/$scriptembed. scripttest just shows you the result - nothing else happens, and it isn't trackable for pagination. createembed posts it as a real message and starts tracking it, which is what pagination and buttonrole both require. If a script produces nothing at all (no text, embed, or buttons) or Discord rejects it (e.g. a field over its character limit), you'll get a specific error back instead of a blank success. A typo that isn't fatal - an invalid hex color, an unrecognized button style - still posts (using a sensible default) but adds a follow-up warning telling you exactly what it ignored.

Pagination

Every command below needs Manage Guild + Manage Messages. Only messages posted with createembed can have pages added - this mirrors how the feature this was modeled on works. Navigation is two reactions (⬅️/➡️) on the message itself, not buttons, and wraps around in both directions. Every page re-renders against live variables each time it's shown, so a page showing {guild.count} always reflects the current member count, not whatever it was when the page was written.

<message> accepts either a raw message ID or a full message link, everywhere above.

Stickying a message

$stickyembed <message>

Also $sticky. Not a pagination feature - works on any createembed message, with or without extra pages. Toggles whether it stays pinned to the bottom of its channel, automatically re-posted whenever something pushes it down. Run the same command again to unstick it.

Server name/icon/banner changes

{guild.name}/{guild.icon}/{guild.banner} update automatically - the moment you rename the server or change its icon/banner in Server Settings, every tracked createembed message whose script references one of those three variables gets re-rendered on the spot. Nothing to run, nothing to remember.

$serverprofileupdated

Also $refreshembeds, $syncembeds, /script refresh. A manual force-refresh for edge cases the automatic trigger can't see - e.g. you just added a {guild.icon} reference to an existing script via pagination update, so it's now stale relative to a profile change from before that edit. Scans every tracked message, re-renders the ones that reference those three variables, leaves everything else untouched. Safe to run any time, including when nothing's changed.

Button roles

Attaches a real, working role-toggle button to any message this bot sent - it doesn't have to be one made with createembed, unlike pagination. Clicking gives the role if you don't have it, removes it if you do.

buttonrole add <message> <role> <style> <label>
buttonrole remove <message> <role>
buttonrole removeall <message>
buttonrole reset

style is blurple, green, grey/gray, or red (no link - a role button always needs a click handler, which a link-style button can't have). buttonrole list <message> (no permission needed) shows what's attached without changing anything. @everyone and managed roles (bot/booster/integration roles) can't be attached, neither can a role positioned above Pixie's own highest role, and neither can a role at or above your own highest role (server owner is exempt from this last check) - that last one exists so Manage Roles alone can't be used to set up a button that hands out a role you couldn't normally assign yourself. All four are rejected up front with a clear reason rather than failing silently when someone clicks.

Putting it together

A welcome-style embed with a conditional booster shoutout, a field, and a link button:

$createembed {embed}$v{title: Welcome to {guild.name}!}$v{description: Hey {user.mention}, you're member #{guild.count}.}$v{color: #ff66aa}$v{if {user.boost} == Yes}{field: Booster && Thanks for boosting! inline}{/if}$v{footer: Joined {user.joined_at}}$v{button: link && Read the Rules && https://discord.com/channels/...}

Using this for welcome messages, boost shoutouts, vanity rewards, level-ups, jail messages, and VC XP rewards

Welcome/Leave Messages, Booster Shoutouts, Vanity Rewards, Chat Leveling's level-up message, Jail's jail-channel message, and VC XP's reward-role message all still use their own simple <token>/{token} setup by default - nothing changes for that. But set the message to a script (start it with {embed}$v) and it takes over completely, exactly like the rest of this page - full custom embed, colors, fields, buttons, all of it. Switch back to plain token text any time and it reverts to the simple system.

Every one of these also has a plain prefix command to set the message directly (paste text or a whole script in one go - no need to click through a panel), a preview command that posts a button showing the render privately, and now a matching test command that sends the real thing end-to-end in its configured channel: welcomemessage setmsg/preview/test, leavemessage setmsg/preview/test, boostershoutout setmsg/preview/test, vanity setmsg/preview, jailconfig setmsg/preview, and xp setmsg + previewlevelup/testlevelup, vcxp setmsg + previewreward/testreward. Running setmsg with no message just shows the current one and how to change it - it never resets anything by accident; use the word reset as the message to actually reset.

Both panels ($welcomemessage/$leavemessage/$boostershoutout) have a Preview button next to Test - Preview renders your current message exactly as it would send (script or plain) and shows it to only you, with zero side effects: no real post, no notifications, nothing. Test does the real thing end-to-end, posting for real in the configured channel. When the message is script-controlled, the panel also disables the old Image/Send-in-Embed toggles (the script decides that now) and its footer reminds you how to switch back to the classic system.