🪄 Pixie Docs
Overview Commands Blog Status Invite
Engagement & Rewards

Vanity & Booster Perks

Two separate reward systems for members who represent your server - a role for repping your vanity URL or server tag, and an auto-shoutout when someone boosts.

✨ Vanity Rewards

$vanity

Also /vanity overview. Anyone can run it to see current settings; with Manage Guild it opens the full settings panel instead. Gives a role to members who qualify either way:

Configurable from the panel: award role, announcement channel and message (<user> mentions without pinging), vanity text, tag-repping toggle, and an optional grace period before the role is removed after someone stops qualifying (avoids flicker for a brief drop).

The message can also be a full script (start it with {embed}$v) for a custom embed with colors/fields/buttons. Unlike the plain system, a script decides pinging per directive: {user.mention} inside {message: ...} pings for real, inside {description: ...} or any other embed field it just shows, silently - your call either way. $vanity setmsg [message] (prefix only) sets it directly without opening the panel - omit the message to view the current one, reset to reset it; $vanity preview posts a button that shows it privately.

🚀 Booster Shoutouts

$boostershoutout

Also $bshoutout, /boostershoutout overview. Same access pattern as vanity - open to view, Manage Guild to configure. First run walks through picking a channel and message. Posts an announcement automatically whenever someone boosts the server; unlike vanity, this one DOES ping - <user> in the message (and the automatic "just boosted" header above it) both notify them. <server> inserts the server's name.

Same as vanity, the message can be a full script instead - see the Scripting page's welcome/boost section for the extra {boost.count}/{boost.times_text} variables and how to rebuild the boost-badge buttons. $boostershoutout setmsg [message] (prefix only) sets it directly without opening the panel - omit the message to view the current one, reset to reset it; $boostershoutout preview posts a button that shows it privately, and $boostershoutout test (also the standalone $testboost) sends the real thing in the configured channel. {boost.count}/{boost.times_text} show as a fixed 1/time on both Preview and Test, since neither is a real boost event.