Security Setup
Fake Permissions
Restrict moderators to only use babes for moderation.
Nuke-proof moderation
Moderators never hold a real Discord permission — a rogue account cannot mass-ban through the API.
One required permission per command
Every command needs exactly one fake permission (some need two). administrator unlocks all of them.
Set up in two minutes
Grant permissions to a role with a single command. Three ready-made tiers are below.
Overview
Why use fake permissions?
Fake permissions negate the possibility of a rogue moderator using a script which floods the Discord API and mass bans all members, or any other harmful action. Moderators never hold the real Discord permission, so the only way to moderate is through babes — and every action then runs through the bot’s own limits, logs and Antinuke thresholds. It’s a security measure which ensures that your server can’t be nuked whatsoever.
How do fake permissions work?
When a role is given a fake permission, such as ban_members, its members will be able to use the ,ban command with babes, but they won’t be able to use the native Discord ban feature. A member without the fake permission is told exactly which one is missing:
e
,ban @john spamming
✔@exon: john has been banned
m
,ban @john spamming
⚠️ @mia: You're missing permission:
ban_membersGetting command permissions
You can locate the required permission for a command with ,help (command) — it is shown in the Information field of the help card. The same permission is listed on the command list under permissions, and the dashboard’s Commands tab shows it as a Requires: … badge on every command card while Fake Permissions mode is active.
,help (command)
,help ban
Permission Mode
babes has two ways to control who may run commands. Pick one on the dashboard under General → Permission Mode; exactly one is active at a time.
Fake Permissions
DefaultEach command requires a permission, for example ban_members for ,ban. Only a fake permission on one of the member’s roles unlocks it. Real Discord permissions and the per-command role, member and channel lists are ignored. The server owner is always exempt.
Advanced Mode
The classic setup: every command has its own allowed / disallowed role, member and channel lists on the Commands tab — see Command Permissions. Real Discord permissions apply and fake permissions are ignored completely.
In Fake Permissions mode a moderator with the real Ban Members permission but without the fake ban_members cannot use ,ban. That is intentional — access is granted in exactly one place. Grant the fake permission instead.
,fakepermissions is only available while Fake Permissions mode is active. In Advanced Mode the command is switched off and cannot be enabled.
Setting up fake permissions
The following commands can only be used by the server owner.
Granting fake permissions to a role
Use the fakepermissions add command to grant one or more fake permissions to a role. Separate several permissions with commas.
,fakepermissions add (role) (permission, permission…)
,fakepermissions add @Moderator ban_members, kick_members
e
,fakepermissions add @Moderator ban_members, kick_members
✔@exon: Granted Ban Members, Kick Members to @Moderator
Revoking fake permissions from a role
Use the fakepermissions remove command to revoke fake permissions from a role.
,fakepermissions remove (role) (permission, permission…)
,fakepermissions remove @Moderator ban_members, kick_members
Viewing fake permissions
Use the fakepermissions list command to view all fake permissions.
You can optionally specify a role to only view the fake permissions of that role.
,fakepermissions list [role]
,fakepermissions list @Moderator
Revoking all fake permissions
Use the fakepermissions reset command to reset all fake permissions on the server.
,fakepermissions reset
,fakepermissions reset
Recommended Configuration
A sensible three-tier setup. Adjust the role names to your server — each tier is one command.
- manage_messages — Allows the moderator to delete messages and warn members.
- moderate_members — Allows the moderator to timeout and mute members.
- manage_nicknames — Allows the moderator to change nicknames.
- kick_members — Allows the moderator to kick members from the server.
,fakepermissions add (moderator role) manage_messages, moderate_members, manage_nicknames, kick_members
,fakepermissions add @Moderator manage_messages, moderate_members, manage_nicknames, kick_members
- manage_messages — Allows the administrator to delete messages and warn members.
- moderate_members — Allows the administrator to timeout and mute members.
- manage_nicknames — Allows the administrator to change nicknames.
- manage_roles — Allows the administrator to manage roles.
- ban_members — Allows the administrator to ban members.
- kick_members — Allows the administrator to kick members.
,fakepermissions add (admin role) manage_messages, moderate_members, manage_nicknames, manage_roles, ban_members, kick_members
,fakepermissions add @Admin manage_messages, moderate_members, manage_nicknames, manage_roles, ban_members, kick_members
- administrator — Allows the co-owner to use all moderation commands.
,fakepermissions add (co-owner role) administrator
,fakepermissions add @Co-Owner administrator
Available permissions
These are the only fake permissions that exist. Every command on the command list names the one it needs.
administratorUnlocks every command. The only key that opens the most dangerous ones.
hardbannukechannelnukehoneypotstripstaffhistory removeallroleplay
ban_membersBan and unban members.
bansoftbanunbanteambanteamunbanteambansrecentban
kick_membersKick members from the server.
kick
moderate_membersTimeout and mute members.
timeoutuntimeoutuntimeoutallmuteunmute
manage_messagesDelete messages, warn members and read moderation history.
warnwarningsclearwarnshistorymodstatspurgeclearsnipereactionhistoryembed
manage_channelsLock channels, run filters and manage channel-bound features.
lockdownunlockenabledisablefilterautoresponderbumpremindercountergiveawaysvc-filterthread watchtiktoksoundcloudpinterestx
manage_rolesGive, take and create roles.
rolerolecreatetemproletempremoverole
manage_nicknamesChange member nicknames.
nick
manage_guildServer configuration.
settingsaliaswelcomegoodbyejoingatetimerstarboardclownboardticketsgivexpremovexpinvites add / remove / reset247allowdisallowyoutubetwitchredditkicknotify
manage_expressionsAdd, rename and remove emojis and stickers.
emoji add / rename / removeemojiaddemojiaddmanysticker
manage_webhooksCreate and manage webhooks.
webhook
manage_threadsManage threads.
thread addthread lockthread unlockthread renamethread remove
move_membersMove members between voice channels.
drag
attach_filesImage and media tools that upload a file.
media …ocrocrtr
embed_linksAccepted for parity with bleed — no command needs it yet.
Commands that need two permissions
A few commands change things that are both role- and server-wide. The member’s roles must carry both fake permissions (or administrator).
manage_roles&manage_guildroleallclearrolerole hasrole humansrole botsrole cancelbuttonrolereactionrolemuteroleboosterrole awardboosterrole cleanup
manage_guild&manage_channelssetupmuterolefilter addfilter removefilter whitelistfilter regexfilter wordmigrate
manage_guild&manage_nicknamesforcenickname
manage_roles&manage_channelsperms
Server owner only
These commands cannot be unlocked with a fake permission — not even administrator. Only the server owner can run them.
unbanallstickyrolecustomizefakepermissions
Commands without a required permission (fun, information, music, …) are public.
FAQ
Does the fake administrator give the role Discord’s Administrator permission?
No. Fake permissions exist inside babes only. The role gets every babes command, but nothing changes in Discord’s own permission system — that is the whole point.
A moderator has the real permission but the command is denied. Why?
In Fake Permissions mode real Discord permissions are ignored on purpose. Grant the fake permission to one of the member’s roles, or switch the server to Advanced Mode if you want Discord permissions to count.
Can I use fake permissions together with the per-command role lists?
No — exactly one mode is active. Fake Permissions mode ignores the allowed / disallowed lists, Advanced Mode ignores fake permissions. Switching the mode keeps both configurations stored, so you can switch back at any time.
Which permission does a command need?
Run ,help (command) or look it up on the command list. The permission names are the same as on bleed, so guides written for bleed apply one to one.
What does the bot need itself?
babes still needs the real Discord permission for the action — Ban Members to ban, Manage Roles to hand out roles, and so on. Fake permissions decide who may ask; Discord decides what the bot is able to do.