ANTI-SPAM
Spam protection
Messages from a member who sends the number of messages you set within the time you set are deleted; an automatic mute can also be applied. The threshold and period are set in the panel.
Moderation
SAKBOT's moderation side takes on three jobs: enforcing the rules (warn, mute, kick, ban), guarding the rules (spam, link, invite and profanity filters) and keeping the record (who did what, which message was deleted and why). Moderation settings are off by default.
In SAKBOT, moderation does not start with punishment. Warnings come first, they add up, and when a tier you defined is reached the penalty is applied automatically. That way you do not have to make the same decision again for every incident, and penalties stay consistent.
A moderator types !warn @member REASON (optionally with a duration). The warning records the reason, the moderator and, if timed, the expiry date. You can see a member's history with !warnings.
You define the tiers in the panel (for example a mute at 3 active warnings, a kick at 5, a ban at 8). When a tier's threshold is reached, SAKBOT applies the penalty itself.
Timed mutes are lifted automatically when they expire; expired warnings no longer count as active and do not affect the penalty count. Removed warnings stay in the history.
The member writes a reason with !appeal; the appeal is posted to the notification channel and appears in the panel's pending appeals list. If accepted, the warning is removed; if rejected, it stays active. The decision maker and date are recorded.
| Tool | What it does | How to use it |
|---|---|---|
| Warning | Adds a timed or permanent warning to a member; the reason and moderator are recorded. | !warn (Manage Messages permission) |
| Warning history | Lists a member's warnings, their durations and statuses. | !warnings |
| Appeal | Lets a member appeal a warning; the decision is made in the panel. | !appeal + panel |
| Mute | Mutes a member for a set time; lifted automatically when it expires. | !mute or an automatic penalty tier |
| Kick | Removes the member from the server. | !kick or an automatic penalty tier |
| Ban | Bans the member; timed bans are possible too. | !ban or an automatic penalty tier |
| Bulk message deletion | Tries to delete the latest messages in the channel (1–100). | !clear COUNT |
| Audit log | Writes deleted messages, warnings and penalties to the channel you choose. | Log channel (panel) |
Moderators can use !mute, !kick and !ban directly (with the matching Fluxer permission), and the same penalties can also be applied automatically through warning tiers, so the decision follows the server's rules rather than a moderator's mood in the moment.
ANTI-SPAM
Messages from a member who sends the number of messages you set within the time you set are deleted; an automatic mute can also be applied. The threshold and period are set in the panel.
LINKS AND INVITES
Blocks or deletes unauthorised links and invites. You set the allowed domains and allowed invite codes; the filter only runs in the channels you choose.
WORD FILTER
Blocks or deletes messages that match your own list of banned words. The list is managed entirely in the panel; no code is needed to add or remove words.
Details: privacy notice.
Logs do not have to pile up in one channel: you can choose separate channels for panel, member, role, moderation and event logs. That keeps the moderation record apart from the general member feed.
Commands are handy for everyday work, but the panel is better for reviewing history and making decisions. In the Moderation section:
!clear and !warn require the Manage Messages permission; members without it cannot use these commands.The warning is recorded with the default duration set in the panel. When it expires, the warning becomes "expired" and no longer counts as an active warning, so penalty tiers are not triggered by mistake.
Automatic penalty tiers have their own switch; while it is off, warnings are recorded but no mute/kick/ban is applied. You can also turn off the warning system entirely and keep only the filters on.
Remove the warning from the moderation records in the panel. The record is not deleted; it becomes "removed", stays in the history and no longer counts towards automatic penalties.
The deletion is written to the log channel with "whose message was deleted and by which filter". You can reduce false matches by extending the allowed domains and allowed invite codes lists.
When the bot is removed from a server, that server's data can be deleted by the operator. There is no legal retention commitment for the records; details are in the privacy notice.
Turn on the warning system and filters in the panel and define tiers that match your rules. Setup takes a few minutes.