Set Up Fake Permissions for XRYPTON Commands

Grant roles the ability to run permission-gated XRYPTON commands without giving them the real Discord permission, using the fakeperms module.

Fake Permissions let you grant a role the ability to run XRYPTON commands that normally require a specific Discord permission, without actually giving that role the permission in Discord’s settings. This is ideal for delegating moderation power to trusted roles while keeping their real Discord permissions minimal.

Fake permissions only affect XRYPTON’s internal command checks. They do not grant any real Discord permissions — a role with fake ban_members still cannot ban through the Discord client, only through XRYPTON.

All fakeperms commands require the Administrator permission. Only give fake permissions to roles you fully trust.

---

How It Works

When a member runs a XRYPTON command, the bot checks whether they have the required Discord permission. With fake permissions enabled, XRYPTON also checks whether any of the member’s roles has been granted that permission through fakeperms add. If so, the command runs as if the user had the real permission.

Delegate Safely

Give moderators access to ,ban, ,kick, or ,purge without granting the real Discord permissions that could be abused elsewhere.

Role-Scoped

Fake permissions are attached to roles, not individual users. Anyone with the role inherits the granted permissions.

---

Setup

1. View Valid Permissions

Before assigning anything, list every permission string XRYPTON accepts. Permission names use snake_case.

,fakeperms perms

Common examples: ban_members, kick_members, manage_messages, manage_roles, manage_channels, moderate_members, mention_everyone.

2. Grant a Fake Permission

Assign a permission to a role using its name or mention.

,fakeperms add <role> <permission>

Example — let the @Moderator role use ban commands:

,fakeperms add @Moderator ban_members

Members with @Moderator can now run ,ban even though the role does not have the real Ban Members permission in Discord.

3. Review a Role’s Fake Permissions

,fakeperms list <role>

Shows every fake permission currently attached to the role.

4. Remove a Fake Permission

,fakeperms remove <role> <permission>

Example:

,fakeperms remove @Moderator ban_members

---

Command Reference

Command	Usage	Description
fakeperms	,fakeperms	Show the fake permissions help menu. Alias: fp.
fakeperms add	,fakeperms add <role> <permission>	Grant a fake permission to a role. Alias: set.
fakeperms remove	,fakeperms remove <role> <permission>	Revoke a fake permission from a role.
fakeperms list	,fakeperms list <role>	List all fake permissions assigned to a role.
fakeperms perms	,fakeperms perms	Show every valid permission name accepted by fakeperms add.

All commands require Administrator.

---

Examples

Give trial moderators purge access without Manage Messages:

,fakeperms add @TrialMod manage_messages

Let a support role time out members:

,fakeperms add @Support moderate_members

Audit a role before an event:

,fakeperms list @EventStaff

---

Tips

Run ,fakeperms perms first to copy the exact permission string. Typos are silently rejected.

Fake permissions stack with real Discord permissions — a user only needs one of them to pass the command check.

Fake administrator bypasses every XRYPTON permission check. Treat it exactly like giving out the real Administrator permission.