🪄 Pixie Docs
Overview Commands Blog Status Invite
Security

Moderation: Mass Actions

Bulk role changes, banning a whole role or list of IDs at once, and auto-kicking someone on every rejoin.

Part of Moderation - see also Actions, Timeouts, and Nicknames.

Giving/removing roles

Manage Roles
$role <@member> <role name>
$role add <@member> <@role>
$role remove <@member> <@role>
$role massadd <@role> [bots]
$role massremove <@role> [bots]
$role color <@role> <name/hex> [, name/hex]
$role icon <@role> <emoji/link>   (or attach an image)
$role name <@role> <new name>
$role delete <@role>

The bare form ($role @user Trusted) toggles that role on the member - on if they don't have it, off if they do. add/remove are explicit instead of toggling. massadd/massremove apply to every member in the server at once (with a confirm prompt showing the count) - bots are skipped unless you add the word bots at the end, e.g. $role massadd @Verified bots. color/icon/name edit the role itself (icons need boost level 2, gradients need level 2 too). delete removes the role entirely and asks you to confirm first - can't be undone. You can't touch a role at or above your own highest role (server owner is exempt from that check), or above Pixie's own highest role.

Backing up and restoring a role

Manage Roles
$rolewipebackup backup <@role>
$rolewipebackup restore <@role>

backup saves everyone who currently has a role to a .txt file (one user ID per line) and then removes that role from all of them - useful before a big reorg, or to pause a role's effects without losing who had it. restore reads a backup file back and re-adds the role to everyone in it; attach the file to the restore command, or reply to the message that has it (e.g. reply to the backup message the bot originally sent you). Both steps ask you to confirm first.

Mass ban

Server Owner only
$massban [@role or @member or id...] [reason]

Restricted to the actual server owner - not Administrator, not a Fake Perm. Mention any mix of roles, members, and/or raw IDs (or attach a .txt file with one ID per line) and it bans everyone matched, skipping bots, yourself, and Pixie. For example $massban @Raiders bans every member of that role. It deliberately makes you wait it out: a 10-second-locked confirm button first, then - if more than 10 people are affected - a second "are you actually sure?" prompt locked for 30 seconds, before a final ban button. There's no undo once you confirm the last step.

Mass timeout

Administrator
$masstimeout [time] <@role/@member/id...>

Also $mto. Mention any mix of roles, members, and/or raw IDs - every role given expands to its current members. Skips bots and yourself automatically. Time is optional and can go anywhere in the argument list (30s/10m/2h/1d, default 1 minute, capped at Discord's own 28-day timeout ceiling - asking for longer than that just times out for 28 days instead). Example: $mto 2h @Raiders @troublemaker 123456789012345678.

Auto-kick on rejoin

Ban Members for set/remove, Administrator for the list
$autokickban <@member or id> [reason]
$unautokickban <user id>
$autokickbanlist

Kicks a member immediately (if they're currently in the server) and then kicks them again automatically every time they try to rejoin - effectively a ban that doesn't touch Discord's IP-level ban, which matters for cases like a compromised/hacked account you don't want IP-banned. Works on someone not currently in the server too (by ID) - they'll just get auto-kicked the moment they do join. unautokickban removes someone from the list, and autokickbanlist shows everyone currently on it with their reasons.