Moderation and sanctions
The moderation module covers manual sanctions: warn, kick, ban, and delete messages in bulk. Every action is logged to the moderation channel configured for the server.
Warnings are kept with their reason, their author and their date, so a repeat offence can be handled knowing the member's history rather than by guesswork.
Commands
*warn <@member> <reason>- Records a warning against the mentioned member, with the given reason. It is added to their history and announced in the moderation channel.
*getwarn <@member>- Shows the mentioned member's warning history: reason, moderator and date for each.
*kick <@member> <reason>- Removes the member from the server. They can rejoin with a valid invite.
*ban <@member> <reason>- Bans the member from the server. The ban stands until lifted manually from Discord.
*clear <number> {@member}- Deletes the given number of messages in the current channel, between 1 and 99. With a mention, only that member's messages are removed among those examined.
What Discord enforces, and the bot cannot work around
Bulk deletion only works on messages under fourteen days old. That is a Discord API limit, shared by every bot. Older messages must be deleted one at a time.
A bot cannot sanction a member whose highest role sits above its own in the server hierarchy. When a command fails on a moderator or an administrator, that is almost always why: the bot's role needs to be moved up.
Where the alerts go
The channel receiving moderation notifications is chosen in the dashboard. Pointing it at a staff-only channel avoids publishing warning reasons, which often carry the context of the incident.