mirror of
https://github.com/Sheldan/abstracto.git
synced 2026-03-20 20:47:07 +00:00
added explanation about immune roles
This commit is contained in:
@@ -85,4 +85,14 @@ Make a role immune against a command::
|
||||
* Description: Makes the role immune from all commands in the `feature`/the `command`.
|
||||
Enforce the role restrictions of commands::
|
||||
* Usage: `restrict <featureName|commandName>`
|
||||
* Description: Causes the role restrictions for a all commands in the `feature`/the `command` to be in effect again.
|
||||
* Description: Causes the role restrictions for a all commands in the `feature`/the `command` to be in effect again.
|
||||
|
||||
==== What does it mean if a role is immune?
|
||||
A command can take a member as a target, for example `ban`. If a role is considered immune, this means, if the member which is the target of the command has the given role, this command will fail. Not all commands support this feature, but only the following:
|
||||
|
||||
* Ban
|
||||
* Kick
|
||||
* Warn
|
||||
* Mute
|
||||
|
||||
While a role can be made immune for any command, only these commands actually use this information.
|
||||
@@ -29,7 +29,6 @@ In order to change this you need to use the command `setConfig` with the provide
|
||||
Emotes:: The features have section of the keys of used emotes in the feature, you can change this emote with the `setEmote` command.
|
||||
|
||||
== Features
|
||||
The following features are available, and they can be enabled/disabled with the command `enable`/`disable`.
|
||||
|
||||
include::features/core.adoc[]
|
||||
|
||||
|
||||
Reference in New Issue
Block a user