What are Mass Command Alerts?
Mass Command Alerts notify your team when a command affects many players at once, such as :ban all or :kick others. They help you spot abuse and accidental mass punishments quickly.
Requires a Webhook Channel in Webhook Configuration.
Configuration Options
Find Mass Command Alerts on the ER:LC Integration → Webhooks page.
| Setting | Description |
|---|---|
| Enable Mass Command Alerts | Turns the feature on or off |
| Commands to Monitor | The commands that can trigger an alert, such as :ban, :kick, :mod or :unmod |
| Targets That Trigger an Alert | all, others or both |
| Minimum Players Affected | Alerts when a command hits at least this many unique players. 2 to 100. |
| Alert Cooldown | Minimum minutes between alerts for the same command and target. 1 to 60. |
| Mention Roles on Alert | Up to 5 roles to ping, including @here and @everyone |
| Alert Delivery Channel | Where alerts are posted. Leave it empty to post in your webhook channel. |
When you turn it on, Melonly fills in defaults. It monitors :ban, :kick, :mod and :unmod on the targets all and others, with a minimum of 3 players. You need at least one command, plus at least one target or a Minimum Players Affected value.
You can monitor :admin, :unadmin, :mod, :unmod, :helper, :unhelper, :ban, :unban, :kick, :kill, :refresh, :respawn, :heal, :jail, :wanted, :unwanted and :shutdown.
Example Use Cases
- Notify supervisors when
:kickhits many players after an incident - Check that
:modor:unmodon many players was intentional - Cut noise by raising Minimum Players Affected or Alert Cooldown
Need help?
Still have questions? Join our Discord server for support from the Melonly Team.