Command Management
Turn any command - or a whole group of them - off for this server, with a clear message telling anyone who tries it how to get it back.
$disable <command or group>
$enable <command or group>
$disabled
Also /cmd disable/enable/disabledlist (with autocomplete
suggesting valid targets as you type). disable accepts either a single command
(avatar) or a whole group at once (role disables every
role ... subcommand in one go) - up to 100 disabled entries per server.
disabled lists everything currently off, and marks whether each one is a single command or
a whole group.
Anyone who tries a disabled command sees exactly what's blocking them and how to fix it - a single
command shows 🚫 $avatar is disabled in this server., a group shows
🚫 the role group of commands is disabled in this server. - either way followed by
admins: run $enable <command> to turn it back on, so staff never have to guess the
exact name to re-enable.
Disabling something already covered by a disabled parent group is a no-op (Pixie tells you which ancestor group already covers it). The command-management system itself can't be disabled - that's blocked specifically so a server can never accidentally lock itself out of ever re-enabling anything.