Skip to content

Latest commit

 

History

History
13 lines (7 loc) · 906 Bytes

permissions.md

File metadata and controls

13 lines (7 loc) · 906 Bytes

Permissions

For what does Pyron need:

Administrator Pyron uses the Administrator permission as a fallback in case specific permissions are missing for future commands or events. This can be toggled off either when adding the bot or afterward by editing the bot's role permissions.

Manage Server Pyron uses the Manage Server permission to access the guild’s invites and begin tracking them.

Manage Roles Pyron uses the Manage Roles permission to assign roles to users who have reached a certain number of invites. The number of invites required is determined by the administrators.

Kick,Ban Members Pyron uses the Kick/Ban Members permission to kick users when the command is run by someone with administrator permissions.

Manage Messages Pyron uses the Manage Messages permission for a purge command, which will be available soon.