Security

Image & Reaction Mute

Two lightweight, single-permission mutes - image mute blocks attachments/embeds/links, reaction mute blocks adding reactions - both server-wide, with no other effect on the member.

Unlike Jail, neither mute touches a member's other roles at all - there's nothing to back up or restore, and no isolation channel. The mute role is simply added or removed, and Pixie keeps that one permission denied for the role on every channel automatically.

Setup

Manage Guild + Manage Messages

$imuteconfig
$rmuteconfig

Also $imutesetup/$rmutesetup, /imute config//rmute config. Opens a panel with a Set Mute Role button - pick an existing role, or have Pixie create one for you (you'll be asked which role to place it directly below; picking your lowest staff role keeps the hierarchy correct). Each mute has its own separate role and its own separate setup - they don't share a role.

Channel permissions stay in sync automatically from then on: the mute role gets Attach Files + Embed Links denied everywhere (image mute) or Add Reactions denied everywhere (reaction mute), including any new channel created afterward. A Force Sync Perms button on the same panel re-checks every channel on demand, for if something's drifted (a channel's perms edited by hand, etc).

Muting (and unmuting) a member

Manage Roles

$imute <@member> [reason]
$rmute <@member> [reason]

$imute/$rmute toggle - run it on someone who isn't muted to mute them, run it again on someone who already is to unmute them. Same rules either direction: you can't touch yourself or Pixie itself, or a member whose top role is equal to or higher than yours (server owner is exempt from that last check); Pixie's own role also has to sit above the mute role, or it can't assign or remove it.

The slash side keeps muting and unmuting as two separate, explicit commands instead of one toggle - /imute add//rmute add only mutes (errors if already muted), /imute remove//rmute remove only unmutes - same split as $role's bare toggle vs its own /role add//role remove.

Releasing a member directly

Manage Roles

$unimute <@member> [reason]
$unrmute <@member> [reason]

Also /imute remove//rmute remove. Removes the mute role, nothing else - for when you specifically want "unmute" rather than the bare command's toggle.

Who's currently muted

Manage Roles

$imuted
$rmuted

Also /imute list//rmute list. Reads live off who currently holds the mute role - there's no separate tracking list to fall out of sync.