Automod - Auto-moderation

Automatic moderation system to protect your server

Commands

/mod spam

Anti-spam filter

Parameters:

Parameter	Type	Required	Description
activar	Boolean	Yes	true/false
mensajes	Number	No	Maximum messages in 5 seconds (3-20)

Web Panel

Configurable from: Auto-moderation > Anti-spam

Access panel.yumechanbot.com

Example:

/automod spam activar:true mensajes:5

/mod links

Link filter

Parameters:

Parameter	Type	Required	Description
activar	Boolean	Yes	true/false

Web Panel

Configurable from: Auto-moderation > Link filter

Access panel.yumechanbot.com

Example:

/automod links activar:true

/mod palabras

Banned words management

Parameters:

Parameter	Type	Required	Description
accion	Selection	Yes	Add, Remove, or List
palabra	String	No	Word to add/remove

Web Panel

Configurable from: Auto-moderation > Banned words

Access panel.yumechanbot.com

Example:

/automod palabras accion:Add palabra:badword

/mod caps

Excessive caps filter

Parameters:

Parameter	Type	Required	Description
activar	Boolean	Yes	true/false

Web Panel

Configurable from: Auto-moderation > Caps filter

Access panel.yumechanbot.com

Example:

/automod caps activar:true

/mod raid

Anti-raid protection

Parameters:

Parameter	Type	Required	Description
activar	Boolean	Yes	true/false

Web Panel

Configurable from: Auto-moderation > Anti-raid

Access panel.yumechanbot.com

Example:

/automod raid activar:true

---

🛡️ Anti-Nuke (PRO+)

Requires PRO Premium

This feature requires Server PRO or higher. View premium plans

What is Anti-Nuke?

The Anti-Nuke system protects your server against compromised administrators attempting to destroy the server by performing mass destructive actions. It automatically detects suspicious behavior and takes measures to stop it.

🎯 What does it detect?

Anti-Nuke monitors these destructive actions:

Action	Default Threshold	Time Window
🗑️ Channels deleted	3 channels	10 seconds
🗑️ Roles deleted	3 roles	10 seconds
🔨 Mass bans	5 bans	10 seconds
👢 Mass kicks	10 kicks	10 seconds
🔗 Webhooks created	5 webhooks	10 seconds
➕ Channel spam	10 channels created	10 seconds
➕ Role spam	10 roles created	10 seconds

⚡ Automatic Actions

When a nuke is detected, the system can:

1. 🔒 Remove dangerous permissions (Recommended)

   • Removes roles with: ADMINISTRATOR, MANAGE_CHANNELS, MANAGE_ROLES, etc.
   • The admin loses ability to cause more damage

2. 🚨 Notify designated roles

   • Sends urgent alert with nuke details
   • Mentions the roles you configured
   • Includes summary of actions taken

3. 🔒 Quarantine role (Optional)

   • Creates role "🔒 Quarantine [Anti-Nuke]"
   • Applies role to compromised admin
   • No permissions, isolated from server

4. 📋 Log registration (Automatic)

   • Detailed log in logs channel
   • Timestamp, admin, detected actions
   • Event history

🎨 Configuration from Web Panel

Web Panel

Go to: panel.yumechanbot.com/automod

1. Activate the module

In the panel, find the "Anti-Nuke" module (with PRO badge) and activate it.

2. Configure Thresholds

Adjust how many actions are needed to trigger protection:

Channels deleted: 3    # Ex: If admin deletes 3+ channels in 10s → NUKE
Roles deleted: 3
Mass bans: 5
Mass kicks: 10

Recommendation

• Small servers (< 100 members): Use low thresholds (2-3)
• Large servers (1000+ members): Use medium thresholds (4-5)
• Very active servers: Increase kicks to 15-20

3. Select Actions

Check the actions you want taken automatically:

• ✅ Remove dangerous permissions - ALWAYS recommended
• ✅ Notify roles - To alert real admins
• ☐ Quarantine role - Only if you want complete isolation
• ☐ Log registration - Done automatically if you have logs channel

4. Configure Roles to Notify

If you checked "Notify roles", select which roles should be alerted:

Roles to notify:
- @Admin
- @Senior Moderators
- @Owner

5. Trusted Admins Whitelist

VERY IMPORTANT: Add your most trusted admins to the whitelist:

• Whitelisted admins are NOT monitored by Anti-Nuke
• They can delete channels/roles without triggering protection
• Only add people of extreme trust

How to add to whitelist:

1. Copy the admin's User ID (Right click → Copy ID)
2. Paste it in the whitelist field
3. Press Enter

Careful with Whitelist

• Only add people you know personally
• A whitelisted admin can nuke you without protection
• Review whitelist regularly

📊 Detection Example

🚨 ANTI-NUKE: Suspicious Activity Detected

Admin: @JohnHacked (ID: 123456789)
Status: Possibly compromised account

⚠️ Suspicious Actions:
🗑️ Channels deleted: 5/3 in 10s
🗑️ Roles deleted: 4/3 in 10s

🛡️ Actions Taken:
✓ removed_role:Admin
✓ removed_role:Moderator
✓ notification_sent

📊 Summary:
- Channels deleted: 5
- Roles deleted: 4
- Total destructive actions: 9

🔍 Use Cases

✅ When to use Anti-Nuke

• Large servers with multiple admins
• Public servers with rotating staff
• After promoting new moderators
• High-risk servers (gaming, trading, crypto)
• High-value communities with years of history

❌ When NOT to use Anti-Nuke

• Private servers only with close friends
• Small servers (< 20 members) without history
• Test/development servers
• If you're the only admin (makes no sense)

🎓 Best Practices

1. Start with conservative thresholds (3-5) and adjust as needed
2. Always activate "Remove permissions" - It's your first line of defense
3. Configure notifications - You need to know if something happens
4. Review whitelist monthly - Remove ex-admins
5. Test in test server first before production
6. Have backup of important roles/channels (use /admin backup create)
7. Don't add bots to whitelist - Bots can be compromised

⚙️ Integration with other systems

Anti-Nuke integrates with:

• 📋 Logging: Events are automatically logged
• 🔔 Webhooks: You can receive external notifications
• 💾 Backups: Combine with automatic backup system
• 👥 Roles: Respects role hierarchy (can't remove higher roles)

🐛 Troubleshooting

"Anti-Nuke triggers with normal actions"

Solution: Increase thresholds or add the admin to whitelist

"Anti-Nuke didn't trigger when it should"

Check:

• ✅ Is the module activated?
• ✅ Is the admin whitelisted?
• ✅ Are thresholds too high?
• ✅ Does the bot have permission to remove roles?

"Bot couldn't remove permissions"

Common causes:

• Bot's role is below admin's role
• Admin has owner role
• Bot missing "Manage Roles" permission

Solution: Make sure Yume's role is in the highest position possible

📈 Anti-Nuke Statistics

You can view Anti-Nuke statistics in the panel:

• Total triggers: How many times it activated
• False positives: If it activates with legitimate admins
• Most common actions: What type of nuke is most frequent
• Flagged admins: Detection history

🔐 Security and Privacy

• We don't monitor messages - Only destructive actions
• Local whitelist - Never shared with other servers
• Private logs - Only your server can see events
• No telemetry - We don't send data to external servers

---

Notes

• Filtered messages are automatically deleted
• The user is notified why their message was deleted
• Accumulating infractions may result in automatic timeout
• Easier to configure from the web panel