Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.greed.best/llms.txt

Use this file to discover all available pages before exploring further.

The Command Restrictions feature allows you to limit which roles can use specific commands, providing an additional layer of security and control over command usage.

​
Requirements

  • Bot must have permissions to:
    • Administrator (for the bot)
    • Administrator (for the user setting restrictions)
Both the bot and the user setting restrictions must have Administrator permissions for this feature to work properly.

​
Basic Commands

​
Add Restriction

,restrict add [command], [role]
The command and role must be separated by a comma. The role can be mentioned, named, or ID.

​
Remove Restriction

,restrict remove [command], [role]

​
List Restrictions

,restrict list

​
Reset All Restrictions

,restrict reset

​
Features

​
Command Control

  • Restrict any command to specific roles
  • Multiple roles can be restricted for the same command
  • Restrictions persist across server restarts
  • Easy to manage with clear commands

​
Role Management

  • Works with any role in the server
  • Supports role mentions, names, and IDs
  • Can be used with custom roles
  • Restrictions are role-based, not user-based

​
Security

  • Additional layer of command protection
  • Prevents unauthorized command usage
  • Works alongside Discord’s permission system
  • Helps maintain server security
Command restrictions are in addition to Discord’s built-in permission system. Users still need the appropriate Discord permissions to use commands.
Make sure to test restrictions after setting them up to ensure they’re working as intended. If a command is restricted to a role that no longer exists, the restriction will be automatically removed.