Skip to main content
Discord nukes happen fast — a single compromised admin account can delete every channel, ban every member, and destroy months of community building in under thirty seconds. Ares is Seshy’s built-in anti-nuke system, and it was designed with one principle: stop the damage before the second action lands. With 22 distinct protection layers, a sub-second response time, and zero configuration required to go live, Ares is the most capable protection system available to ERLC communities — and it comes included with Seshy at no cost.
Nukers move fast. Ares moves first.
Ares is enabled by default the moment Seshy joins your server. Zero setup steps are required — protection is active immediately.

​
How Ares Works

Ares attaches to Discord’s gateway and monitors every audit log event and permission change in real time. It applies two types of detection logic simultaneously:
  • Rate-limit detection — counts destructive actions (bans, kicks, deletions) within short time windows. If the count crosses the configured threshold, Ares fires.
  • Permission detection — flags the moment any user or bot is granted a dangerous permission like Administrator or Manage Server, even if no rate limit has been crossed yet.
When either trigger fires, Ares executes its configured punishment action — ban, kick, timeout, role strip, or warn — before the attacker can take a second destructive step. The entire detection-to-action cycle completes in under one second.
Ares requires the Administrator permission to monitor and respond to all protected actions. Without it, Ares cannot intercept dangerous permission changes or reverse destructive actions. Make sure Seshy’s role sits above all other roles in your role hierarchy.

​
Protection Layers

Ares maintains 22 active protection layers across every category of server attack:

​
Punishment Types

When Ares detects a threat, it responds with the punishment action you configure. Choose the response that fits your risk tolerance:

Ban

Permanently bans the offending user from the server. Best for confirmed nuke attempts where the account is clearly compromised.

Kick

Removes the user from the server without a permanent ban. Use when the account may be a victim of a token grab rather than a malicious actor.

Timeout

Mutes the user for 1 hour, 24 hours, or 7 days. Halts destructive actions while preserving the ability to review and reverse the action if it was a false positive.

Strip Roles

Removes all roles from the user instantly, eliminating their permissions without removing them from the server.

Warn Only

Logs the action and sends an alert to your Ares log channel without taking any action against the user. Useful during initial setup to observe triggers before applying punishments.
Configure your punishment type in /settings → Ares → Punishment Action. You can set different punishment levels for different protection categories — for example, instant ban for mass deletions, but timeout for permission changes.

​
Whitelist System

Trusted users and bots — your own bots, senior staff, co-owners — should never be blocked by Ares. The whitelist system lets you exclude specific users and roles from any or all protection layers with granular control. Add a user to the whitelist with /ares whitelist add @user. Whitelisted users can perform actions that would otherwise trigger Ares without being flagged or punished. You can also whitelist by role, so an entire staff tier bypasses specific protections automatically. Configure granular overrides in /settings → Ares → Whitelist, where you can specify exactly which protection layers each whitelisted entity is exempt from — rather than a blanket bypass.

​
Shared Blacklists

Shared blacklists let multiple servers coordinate protection against known bad actors. Create a blacklist group or join an existing one using a share code, and every server in the group automatically receives bans when a member is added. Each group supports three access tiers:
  • Owner — full control, including managing members and editors
  • Editor — can add and remove entries from the shared blacklist
  • Member — receives all blacklist updates but cannot modify entries
Every addition and removal is recorded in a full audit log — you always know who added a user to the shared blacklist, when they did it, and what reason was given. No silent changes, complete accountability.

​
Security Audit Log

Every action Ares takes is written to your configured Ares log channel. The audit log records:
  • Every blocked action — what was attempted, who attempted it, and which protection layer fired
  • Every whitelist change — who was added or removed, and by which staff member
  • Every protection trigger — including near-misses where the rate limit was approached but not crossed
Review the audit log after any incident to understand exactly what happened and confirm Ares responded correctly.

​
Enabling Ares

1

Run /ares enable

Type /ares enable in any channel. Ares confirms that all 22 protection layers are active and displays your current punishment configuration.
2

Review your whitelist

Add any trusted bots, co-owners, or senior staff to the whitelist with /ares whitelist add @user so they are never accidentally flagged.
3

Configure your punishment action

Open /settings → Ares → Punishment Action and select the response level you want. Start with Timeout if you want to observe before committing to bans.
4

Set your Ares log channel

Designate a private staff channel in /settings → Ares → Log Channel so your team receives real-time alerts whenever a protection layer fires.

​
Commands