Permissions in NadekoBot

Some commands also need a Discord permission - members can only use .kick and .voicemute if they have the Kick Members and Mute Members server permissions. The permission commands add restrictions on top of that, based on who runs a command and where.

To change permissions you need the Administrator server permission. To let someone else change them, give them the role you set with .permrole - there is no permission role by default.

NadekoBot's permissions work as a chain of rules. Every time someone uses a command, NadekoBot checks the chain from the top: if a rule allows or blocks the command, that decides it, and if not, it goes on to the next rule, down to the last rule, which allows all commands.

See the chain with .lp. A rule higher in the chain wins over every rule below it. Remove rule number X with .rp X, and move rule X to place Y with .mp X Y (it moves the rule, it does not swap the two).

Turn on .verbose true and NadekoBot tells members which rule stops them from using a command or module.

Each rule turns a module or a single command on or off, for the whole server, one channel, one role or one member. The short names say which: s for server, c for channel, r for role, u for user, followed by m for a module or c for a command - .sm Gambling disable turns off the gambling module on the server, and .sc .nowplaying enable turns on one command.

The "all modules" versions change every module at once: .asm for the server, .acm for a channel, .arm for a role and .aum for a member.

The Permissions module also deletes messages with words you filter, links or server invites, on the whole server or in single channels, and sets a cooldown on a command.