Moderation

The switch is the status card at the top of the Moderation page: one click turns Moderation off or back on and is saved straight away, no Save needed (Discord commands notice within about 30 seconds). It is on by default, and only staff clicking it ever turns it off. While it is off the settings stay visible but dimmed, and changing one asks you to turn Moderation on first. When off, every moderation command replies that moderation is turned off, and AutoMod actions and actions taken in Discord are no longer recorded as cases. Your existing case log is kept, and temporary bans that are already running still end on time (their automatic unban is still logged).

/warn, /warnings, /pardon, /timeout, /untimeout, /kick, /ban, /unban, /purge, /lock, /unlock, /slowmode, /case, /modlogs and /reason. Each one needs the matching Discord permission: Timeout Members for warnings, timeouts and case lookups, Kick Members for /kick, Ban Members for /ban and /unban, Manage Messages for /purge, and Manage Channels for /lock, /unlock and /slowmode. Diski checks that permission itself too, so a Discord permission override can never hand the bot’s powers to someone without it. You can restrict or disable any of them further on the Slash Commands page.

A moderator can only act on members whose highest role is below their own, and Diski can only act on members below its own highest role — the same rules Discord uses. Nobody can moderate themselves, the server owner or Diski. The owner is exempt from the first rule. Discord doesn't allow timing out members with the Administrator permission. If Diski says a member is above it, move the Diski role higher under Server Settings → Roles.

Timeouts and temporary bans take a duration like 10m, 2h, 1d, 1w or combinations such as 1h30m (a bare number means minutes). Timeouts last from 1 minute to 28 days, the most Discord allows. Temporary bans last from 1 minute to 365 days; leave the duration empty on /ban for a permanent ban.

A /ban with a duration is lifted automatically when it ends — Diski checks every minute, and bans that ended while the bot was offline are lifted as soon as it is back. The unban is recorded as its own case from “Diski (automatic)”. Unbanning someone early with /unban or by hand ends the temporary ban, and banning a member permanently replaces any temporary ban they had. The case is saved before the ban is applied (it is what lifts the ban later), so if the case log can’t be reached the ban isn’t applied at all. If Diski can’t lift a ban when it ends — it lost the Ban Members permission, or Discord kept failing for about half an hour — it records a note against the member (on the Cases tab and in /modlogs) and posts a notice in the log channel, so you can unban them by hand.

Where every case is posted as an embed the moment it is created: the member, the moderator, the reason, any duration and the case number. Editing a reason with /reason or pardoning a warning with /pardon updates that embed in place. Leave it empty to keep the log on the dashboard only. Diski needs View Channel, Send Messages and Embed Links there.

How much of a banned member's recent message history Discord removes when /ban doesn't say otherwise — from none up to the previous 7 days. Moderators can still choose a different amount with /ban's delete_messages option.

When on, /warn, /timeout, /untimeout, /kick, /ban, /unban, /lock and /pardon refuse to run until the moderator fills in the reason option, and pardons from the dashboard need a reason too. Useful when several people moderate and you want every case explained.

Sends the member a private message when they are warned, timed out, kicked or banned, with the server name, the action, the reason, how long it lasts and the case number. For kicks and bans the DM goes out before the action, while Diski still shares a server with them — and if Discord then refuses the kick or ban, Diski deletes that DM again. Members who have closed their DMs simply don't get one — the action still happens, and the case shows whether the DM was delivered. AutoMod actions are not DMed here; AutoMod has its own DM setting.

Adds the moderator’s name to the member DM. Off by default so members can’t single out who acted; escalations and automatic actions show “Diski (automatic)”.

An optional web address (starting with http:// or https://, up to 300 characters) added to every warning, timeout, kick and ban DM so members know where to appeal — a form, a website or an appeals server invite.

After this many days a warning stops counting toward /warnings and the escalation ladder. It stays in the case log, marked Expired. Set 0 and warnings never expire. Changing the number applies to existing warnings straight away, because expiry is worked out from each warning’s date.

Up to 10 steps, each with a warning count (1–20) and an action: a timeout for a set time, a kick, or a ban (permanent or for a set time). When a member’s active warnings reach exactly a step’s count, Diski applies that step automatically and records it as a case with the reason “Escalation: N warnings”. Warnings from AutoMod count too. Pardoned and expired warnings don’t count, so a member who is pardoned and warned again can reach the same step again. If Diski can’t apply a step — the member left, or sits above Diski’s role — it posts a notice in the log channel instead. Steps run with Diski’s permissions, not the moderator’s: anyone who can warn (Timeout Members) can push a member onto a kick or ban step without holding Kick Members or Ban Members themselves, so only add kick and ban steps if you trust everyone who can warn with that.

The Cases tab lists every case, newest first, with its number, type, member, moderator, reason, date and status. Filter by type or status, search reasons, names, user IDs or a case number like #12, and click a case to see everything about it. Warnings show Active, Pardoned or Expired; temporary bans and locks show Active until they end. From a case you can rewrite its reason or pardon a warning — kicks and bans can only be carried out from Discord.

A pardoned warning stops counting toward the member’s active warnings and the escalation ladder, but stays in the log with who pardoned it and why. Pardon from a case on the dashboard or with /pardon. Only warnings can be pardoned, and moderators can’t pardon their own warnings.

Fix or expand a reason with /reason or from the case on the dashboard. In Discord, only the moderator who made the case — or someone with Manage Server — can change it. The case keeps a note of when it was edited.

/purge deletes up to 100 recent messages in the channel it is used in, optionally only from one user or only messages containing some text. Pinned messages are skipped, and Discord only lets bots bulk-delete messages from the last 14 days. The result is shown only to you, and the purge is logged as a case.

/lock stops @everyone from sending messages in a channel by denying Send Messages on the channel's @everyone permissions — and in text, announcement and forum channels also Send Messages in Threads, Create Public Threads and Create Private Threads, so threads and forum posts are locked too (Discord only lets Diski deny a permission it has itself, so /lock tells you if it couldn't cover threads). Diski remembers each setting as it was before, and /unlock puts them back exactly. Roles or members whose own permissions in that channel allow sending are not affected; /lock names them so you can remove that allow. Diski needs Manage Permissions in the channel.

Bans, unbans, kicks and timeouts done from Discord itself (right-click menus) or by another bot are recorded as cases too, the moment Discord writes them to the server's audit log — attributed to whoever the audit log names and marked “Discord (manual action)”. Diski's own actions are never recorded twice. This needs the View Audit Log permission (Discord only tells bots that have it); without it those actions are simply not logged, and neither are actions taken while Diski is offline.

When an AutoMod rule warns, times out, kicks or bans someone, the action is recorded as a case from “AutoMod”. AutoMod warnings count toward the escalation ladder, but each rule adds at most one warning per member per minute — a burst of spam is still deleted and logged, it just can’t stack warnings into an instant escalation. Timeouts, kicks and bans are only recorded once Diski has confirmed they actually happened.

Kicks, bans and timeouts done by the Security module on its own — the account-age gate, raid protection and lockdowns — are recorded as cases from “Diski (automatic)” with a reason starting “Security:”, so they show in a member’s history. They aren’t posted to the log channel one by one (a raid would flood it); Security reports them in its own alert channel. Like every other case, they aren’t recorded while Moderation is turned off.