Auto mute detects when a user pingsDocumentation Index
Fetch the complete documentation index at: https://docs.rbxweb.net/llms.txt
Use this file to discover all available pages before exploring further.
@everyone or @here — a common spam-bot signal — and applies your server’s mute role to them. An embed is posted to a chosen channel explaining the action. Separately, a follow-up timeout can kick in if the same user keeps spamming after the mute.
Open Dashboard → Auto Mute. The view has two cards: Auto Mute Settings on the left and Timeout on Spam on the right.
Auto mute settings
Behavior
When enabled, the bot scans every message. If a message contains@everyone or @here pings that Discord would actually deliver, the bot:
- Applies the configured mute role to the author.
- Posts the configured embed to the selected channel.
@everyone — the bot reacts to any attempt.
Settings
Master switch for auto mute.
The message posted when a user is auto-muted. Same template editor as elsewhere, with support for placeholders.
Where the mute notification embed is posted.
The role applied to the muted user. This must be a role that removes send-message permissions server-wide.
Timeout on spam
A follow-up layer for repeat offenders. After a user is auto-muted, if they continue pinging@everyone / @here, the bot applies a Discord timeout (server-wide) in addition to the mute role.
Settings
Master switch for the timeout follow-up.
How long the Discord timeout lasts. Options: 1 minute, 5 minutes, 10 minutes, 30 minutes, 1 hour, 6 hours, 1 day, 3 days, 1 week.
The message posted when a timeout is applied. Placeholders available:
{user}, {user_name}, {duration}, {server}.Setup checklist
- Create a Muted role in Server Settings → Roles with send-message permissions denied in every channel.
- Move the bot’s own role above the Muted role so it can assign it.
- Open Dashboard → Auto Mute, pick the Muted role, the notification channel, and customize the message.
- Save.