Fake Permissions
Give a role permissions that exist only inside Ludicrous Bot. A role with fake ban_members can run the bot's ban command, while Discord still refuses it the native ban button and the API, so a rogue or stolen moderator account cannot script mass actions straight against Discord.
Overview
Before You Start
Required Discord Permissions
- Server owner or a Ludicrous Bot co-owner to grant, revoke, list, or reset fake permissions
- Administrator is deliberately not enough, in Discord or on the dashboard: widening who can moderate is the owner's call
- Moderators need no Discord permission at all, which is the point
Setup Steps
- Create a normal role with no Discord permissions and give it to your moderators.
- Open Fake Permissions in the dashboard, or run /fakepermissions add <role> <permissions> in your server.
- Tick the permissions that role should have inside the bot, then save.
- Test it: the holder should be able to run the bot command and still find the native Discord action greyed out.
Dashboard Instructions
- Open the server dashboard.
- Select this module in the sidebar.
- Review warnings and empty states.
- Save once the preview matches your desired behavior.
Example Use Cases
- Moderators: manage_messages, moderate_members, manage_nicknames, kick_members.
- Administrators: the moderator set plus manage_roles and ban_members.
- Co-owners: administrator, which covers every command in the bot and nothing in Discord.
- ,fakepermissions add @Moderator ban_members kick_members. The prefix form takes several permissions at once.
Troubleshooting
- Ludicrous Bot still needs the real Discord permission itself, and its role still has to sit above whoever is being moderated. Fake permissions widen who may ask; they never widen what the bot can do.
- Role hierarchy is unchanged: a fake moderator still cannot act on someone whose highest role is at or above their own.
- Channel visibility permissions (View Channel, Send Messages, Read Message History) cannot be faked. The bot uses them to decide whether you may see another channel's content, so faking one would leak channels Discord hides from you.
- A role carrying fake permissions is blocked from every automatic and self-service grant path (reaction roles, level rewards, autoroles), and can only be handed out by someone who holds those permissions themselves.
FAQ
Why not just give the role the real Discord permission?
Because a real permission works everywhere: the Discord client, third-party apps, and the API. A stolen moderator account with real ban_members can mass-ban in seconds. With fake permissions the only route is the bot, which checks hierarchy, rate limits itself, and logs every case.
Does fake Administrator make someone a server admin?
No. It unlocks every Ludicrous Bot command for them and changes nothing in Discord. They still cannot open Server Settings, delete channels, or manage roles outside the bot.
What happens when the role is deleted?
The grants are removed automatically. If the role was deleted while the bot was offline, the dashboard lists the leftover grants so you can clear them.
Are fake permissions included in backups?
Yes. They are part of the bot configuration a server backup captures and restores.