Security response
Unauthorized channel and role activity, privilege grants, bot additions, webhooks, risky invites, and prunes are handled by event-specific protections.
PRODUCT DOCUMENTATION
A clear operating guide for Zero Entropy.
Zero Entropy is a Discord security bot that monitors high-risk server activity, reacts to unauthorized changes, and gives guild owners tightly scoped controls for trusted users and join roles.
The current invite requests Administrator permission. Review its access before authorizing it in any server.
01 / OVERVIEW
What the bot does
Zero Entropy is an anti-abuse and server-security bot. It watches role, channel, member, webhook, invite, and audit-log events. When it identifies an action that is not protected by the bot’s access rules, it can kick the responsible member, remove a created item, restore selected role permissions, and send an alert.
Important: this is a strict protection model. Whitelisting is not blanket administrator access; it only permits the specific offense types configured for that guild.
Owner controls
The guild owner manages the whitelist, its exempt actions, autoroles, and the bulk Shield-role assignment command.
Private setup
On setup, the bot creates or reuses ze-alert and ze-cmd channels and stores their IDs for alerts and text commands.
02 / INSTALL & SETUP
Add the bot with the right hierarchy
- 1
Invite Zero Entropy
Use the official invite above. It currently requests Administrator permission, which gives the bot the Discord access needed by its security and setup actions.
- 2
Put the bot at the top of the role hierarchy
The bot must be above roles it needs to create, edit, assign, or remove. Its own setup guidance expects the bot at the top, then
Zero Entropy+, thenZero Entropy Shield. - 3
Allow the initial setup to finish
When it joins or becomes available, the bot creates its support roles and private alert/command channels when they are missing. It records the resulting alert and command channel IDs.
- 4
Review the default policy before delegating
By default, a newly managed whitelist exemption set permits
member_kick,member_ban,channel_create, andchannel_delete. Owners can change the available exemptions.
03 / ACCESS MODEL
Who is protected and who can manage settings
| Actor | How the bot treats them | Management access |
|---|---|---|
| Guild owner | Protected from the bot’s enforcement checks. | Can manage whitelist, exemption types, autoroles, and bulk protection. |
| Zero Entropy bot | Protected from its own enforcement checks. | Performs setup and automated security actions. |
| Whitelisted member | Only protected for the offense types enabled for that guild. Safe role creation has a separate allowance. | Can use kick, ban, help, and rules commands; cannot manage owner-only settings. |
| Other member | Subject to normal security enforcement. | ze ping is available; other command access is restricted. |
Discord access the bot relies on
Zero Entropy reads audit logs to identify many action executors. It also needs to manage roles and channels, kick and ban members, create/delete channels and roles, delete webhooks and invites, and send messages in its private channels. Administrator permission in the current invite covers these capabilities, but Discord role hierarchy still applies.
04 / PROTECTIONS
What Zero Entropy actively monitors
Roles and privilege escalation
Detects roles gaining Administrator, Kick Members, Ban Members, or Manage Guild permissions. It attempts to restore the previous permissions and kicks the non-protected executor. Unauthorized role creation/deletion is also enforced; safe roles created by a whitelisted member are allowed.
Channels and cleanup
Unauthorized channel creation is deleted and the executor is punished. Unauthorized channel deletion triggers punishment and cleanup of recent channels or roles created/deleted by that user, using Discord audit logs.
Member and bot actions
Unauthorized member kicks, bans, member pruning, dangerous role grants, and non-owner bot additions are monitored. A dangerous role grant can result in the recipient and responsible executor being kicked.
Invites, linked roles, and webhooks
Invites carrying roles with administrator/moderation permissions are deleted. Guild-connections linked roles are sanitized for those permissions. Unauthorized webhook creation is deleted; unauthorized webhook deletion is enforced.
Protection is not a substitute for Discord hierarchy. If Discord prevents the bot from editing a higher role or deleting an object, Zero Entropy cannot complete that action. Keep the bot’s role above the roles it must control.
05 / COMMAND REFERENCE
Slash and text commands
Slash commands are registered globally. Text commands use the ze prefix and are accepted only in the configured ze-cmd channel. The bot creates that channel during setup when needed.
Owner-only management
/whitelist add|remove|list [user]Manage users trusted for eligible actions in this guild.
/whitelist_offense add|remove|list [offense]Manage whitelist exemptions: kick, ban, create_channel, delete_channel, create_role, and delete_role.
/automod_roles_on_join add|remove|list [role]Manage roles automatically assigned to new non-bot members.
/protect_all_membersAssign the Zero Entropy Shield role to members who do not have it. Each run processes up to 5,000 members.
Owner or whitelisted member
/kick [member] [reason]Kick a member if Discord hierarchy allows it.
/ban [member] [reason]Ban a member if Discord hierarchy allows it.
Text-command equivalents
ze pingCheck bot responsiveness. Available to anyone in the command channel.
ze whitelist +|-|listOwner whitelist management. Use ze whitelist offense +|-|list for exemption types.
ze auto role +|-|listOwner autorole management.
ze kick @member ze ban @memberOwner/whitelisted moderation actions, subject to hierarchy.
ze protect all members ze help ze rulesBulk Shield-role assignment is owner-only; help and rules are available to the owner or a whitelisted member.
06 / OPERATIONS & LIMITS
Know the operating constraints
Alerts and command channels
ze-alert receives security alerts. ze-cmd is the text-command channel. The bot denies the default role access when it creates these channels, while allowing the bot to read and send messages.
Audit-log timing
Many detections resolve the executor from a recent audit-log entry. Discord availability and audit-log timing can affect whether an executor can be identified or an action can be reverted.
Shield role
New non-bot members receive Zero Entropy Shield when that role exists. The role is also the target of the bulk protection command; it is not a special Discord permission level.
Enforcement outcome
Most unauthorized-action responses use a kick, not a ban. Some flows additionally delete the triggering object, wipe invites, or clean up related recent channel/role actions.
07 / FAQ
Frequently asked questions
Why did the bot not remove a role or channel?
Discord role hierarchy may prevent it. Put Zero Entropy’s bot role above every role it needs to manage and ensure it retains the required server permissions.
Does whitelisting make someone fully exempt?
No. A whitelisted user is only exempt from actions configured through the whitelist-offense controls. The owner and the bot itself are the fully protected actors in the implemented checks.
What happens when the bot joins?
It attempts setup after a short delay: creates/positions its support roles, creates private alert and command channels if missing, and stores the channels for later use.
Why can’t I use a text command in another channel?
Text commands are deliberately limited to the configured ze-cmd channel. Use slash commands anywhere Discord exposes them, or use the text-command channel created by setup.