Member actions
Moderation commands are still limited by Discord permissions and role
hierarchy. Hedwig cannot moderate a member whose highest role is equal to or
above the bot’s highest role. Owner-level Discord members and protected
roles may also be unavailable as targets.
Channel controls
These are message-command aliases, not slash-command aliases:
,cc for
channel create, ,cr for channel rename, ,cm for channel move, ,ct
for channel topic, ,channeldelete for delete channel, ,deleterole for
delete role, ,deleteemoji for delete emoji, and ,whohas for list inrole. Use the configured server prefix instead of , when it differs.
Roles and server lists
These list commands are message/prefix commands.
,whohas is an alias for
,list inrole.
Autoroles
Autoroles are assigned when a member joins. Use/autorole add with a role,
/autorole show to review the current list, and /autorole remove to delete
an entry. The invoking user needs Manage Server. When the bot assigns a
role, it also needs Manage Roles, and its highest role must be above every
autorole. Autoroles do not retroactively change existing members.
Evidence and message recovery
list and ghostping are message/prefix commands.
A safe moderation workflow
1
Log the action
Keep event logging enabled so staff can review what happened.
2
Use the least destructive action
Start with a warning or mute when a ban is not necessary.
3
Check the target
Use
/userinfo and /permissions before changing roles or taking action.4
Document exceptions
Keep allowlists and staff permissions intentional. Use
/antinuke status when an incident involves destructive actions.Before troubleshooting a failed action
Use/userinfo to confirm the target and /permissions to inspect the
invoking member. Then check the bot’s role position, channel overrides, and
whether the channel is ignored with ,ignore (or the server’s configured
prefix). /purge, deletion commands, bans, and role changes are destructive;
use them only in channels where the moderation policy is clear.