Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rbxweb.net/llms.txt

Use this file to discover all available pages before exploring further.

Message on mute reacts to a role assignment — specifically, when a moderator gives a user your server’s mute role. This is distinct from Auto mute, which fires automatically on @everyone pings. Open Dashboard → Message on Mute.

​
How it works

When enabled, the bot watches for members gaining the configured mute role. Each time it sees that assignment, it posts the configured embed to the selected channel, identifying who was muted and which moderator did it. The feature does not check why the mute happened — it only reacts to the role change. If you assign the mute role through Discord’s native UI, through /role, or through any other bot, this feature still fires.

​
Settings

​
Enable
toggle
Master switch.
​
Message template
embed or text
The message posted when the mute is detected. Same template editor as elsewhere.
​
Channel
channel picker
Where the notification is posted.
​
Mute role
role picker
The role to watch for. The bot only posts when this specific role is added to a member.

​
Available placeholders

  • {user} — ping the muted user
  • {user_name} — muted user’s name as text
  • {muted_by} — moderator who applied the mute
  • {server} — server name
  • {reason} — reason field, if the mute came from a command that supports one
See the placeholders reference for the full list.

​
Interaction with Auto mute

Message on mute and Auto mute are independent features. If both are enabled and Auto mute applies the configured mute role, Message on mute will fire too (and both messages will post). To avoid double-notifications, either:
  • Use a different mute role for Auto mute than the one watched by Message on mute, or
  • Disable Message on mute when Auto mute is active.