|
| 1 | +# Verification |
| 2 | + |
| 3 | +This cog is used to add a verification system that adds or removes certain roles from a member when they send the bot a command with a pre-set password via direct messages. |
| 4 | + |
| 5 | + |
| 6 | +## `verification` |
| 7 | + |
| 8 | +The `.verification` command shows the current verification configuration. This includes the roles that will be added to or removed from the member (verification roles), the configured password and the amount of time a member has to be in the server before they can verify. |
| 9 | + |
| 10 | + |
| 11 | +### `add` |
| 12 | + |
| 13 | +The `add` subcommand adds a verification role. If you set `reverse` to `true`, the role will be removed from the member instead of being added. Note that verification will fail if the member does not have all reverse verification roles! |
| 14 | + |
| 15 | +```css |
| 16 | +.verification [add|a|+] <role> [reverse=False] |
| 17 | +``` |
| 18 | + |
| 19 | +|Argument|Required|Description| |
| 20 | +|:------:|:------:|:----------| |
| 21 | +|`role`|:heavy_check_mark:|The verification role| |
| 22 | +|`reverse`| |Remove this role instead of adding it to the member.| |
| 23 | + |
| 24 | +Required permissions: |
| 25 | + |
| 26 | +- `verification.read` |
| 27 | +- `verification.write` |
| 28 | + |
| 29 | + |
| 30 | +### `remove` |
| 31 | + |
| 32 | +The `remove` subcommand removes an existing verification role. |
| 33 | + |
| 34 | +```css |
| 35 | +.verification [remove|r|-] <role> |
| 36 | +``` |
| 37 | + |
| 38 | +|Argument|Required|Description| |
| 39 | +|:------:|:------:|:----------| |
| 40 | +|`role`|:heavy_check_mark:|The verification role| |
| 41 | + |
| 42 | +Required permissions: |
| 43 | + |
| 44 | +- `verification.read` |
| 45 | +- `verification.write` |
| 46 | + |
| 47 | + |
| 48 | +### `password` |
| 49 | + |
| 50 | +The `password` subcommand sets the *secret* password the member will need to verify with. |
| 51 | + |
| 52 | +```css |
| 53 | +.verification [password|p] <password> |
| 54 | +``` |
| 55 | + |
| 56 | +|Argument|Required|Description| |
| 57 | +|:------:|:------:|:----------| |
| 58 | +|`password`|:heavy_check_mark:|The password| |
| 59 | + |
| 60 | +Required permissions: |
| 61 | + |
| 62 | +- `verification.read` |
| 63 | +- `verification.write` |
| 64 | + |
| 65 | +!!! note |
| 66 | + The password has a maximum length of 256 characters. |
| 67 | + |
| 68 | + |
| 69 | +### `delay` |
| 70 | + |
| 71 | +The `delay` subcommand sets the amount of time a member has to be in the server before they can verify. |
| 72 | + |
| 73 | +```css |
| 74 | +.verification [delay|d] <seconds> |
| 75 | +``` |
| 76 | + |
| 77 | +|Argument|Required|Description| |
| 78 | +|:------:|:------:|:----------| |
| 79 | +|`delay`|:heavy_check_mark:|The amount of time in seconds| |
| 80 | + |
| 81 | +Required permissions: |
| 82 | + |
| 83 | +- `verification.read` |
| 84 | +- `verification.write` |
| 85 | + |
| 86 | + |
| 87 | +## `verify` |
| 88 | + |
| 89 | +The `verify` command is used by server members to verify themselves. If the specified password is correct and the configured delay has elapsed, the configured verification roles will be added to or removed from the member. |
| 90 | + |
| 91 | +```css |
| 92 | +verify <password> |
| 93 | +``` |
| 94 | + |
| 95 | +|Argument|Required|Description| |
| 96 | +|:------:|:------:|:----------| |
| 97 | +|`password`|:heavy_check_mark:|The verification password| |
| 98 | + |
| 99 | +!!! note |
| 100 | + As this command can only be used in direct messages, it does not start with the configured bot prefix! So, for example, if the configured password is `Tr0ub4dor&3`, a member would have to send this exact message to the bot to complete verification: |
| 101 | + <!-- markdownlint-disable-next-line MD038 --> |
| 102 | + ``` |
| 103 | + verify Tr0ub4dor&3 |
| 104 | + ``` |
0 commit comments