Skip to main content
Percy gives server moderators precise control over which commands are available, where, and to whom. You can silence Percy in specific channels, prevent individual members from using the bot entirely, or limit individual commands to only the channels where they make sense — all without touching Discord’s built-in permission system. All /config commands require the Manage Guild or Manage Messages permission.

​
Ignoring Channels and Members

“Ignoring” a channel or member tells Percy to silently refuse all commands from that source. It is the bluntest tool — use it when you want Percy completely quiet in a channel, or when a member is misusing the bot.
Members with the Administrator permission can always use Percy, even if their account or channel has been ignored.

​
Disabling Commands per Channel

Use these commands when you want a command off by default server-wide but available in one specific channel — or vice versa.

​
How Precedence Works

When Percy decides whether to run a command, it checks permissions in this order:
  1. Manage Guild bypass — members with Manage Guild always bypass all restrictions.
  2. Channel-level rules — a per-channel enable or disable overrides the server-wide setting.
  3. Server-level rules — a server-wide disable blocks the command everywhere except channels that explicitly re-enable it.
So you can disable a command globally and then carve out individual channels where it’s still allowed.

​
Practical Examples

Disable gambling server-wide, then re-enable it in one channel:
Block Percy from responding in #general:
Check what’s currently disabled in #bot-commands:
Re-enable a command you disabled by mistake:
Configuration and admin commands cannot be disabled through this system. Percy always responds to /config, /prefix, and related admin commands so you can never lock yourself out of the bot’s settings.
Use /config ignore all followed by /config unignore #bot-commands to funnel all bot usage into a single channel quickly, then open up individual channels as needed.

​
Next Steps

Server Setup

Set a custom prefix and run through the initial server setup checklist.

Audit Log

Log every moderation action and server event to a dedicated channel.