Skip to content

Commit

Permalink
Clarify v6 gateway privileged intents
Browse files Browse the repository at this point in the history
  • Loading branch information
msciotti committed Sep 15, 2020
1 parent 05a3591 commit 7bdf9dd
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions docs/topics/Gateway.md
Original file line number Diff line number Diff line change
Expand Up @@ -292,9 +292,11 @@ Some intents are defined as "Privileged" due to the sensitive nature of the data
- `GUILD_PRESENCES`
- `GUILD_MEMBERS`

In order to specify these intents in your `IDENTIFY` payload, you must first go to your application in the Developer Portal and enable the toggle for the Privileged Intents you wish to use.
In order to specify these intents in your `IDENTIFY` payload, you must first go to your application in the Developer Portal and enable the toggle for the Privileged Intents you wish to use. If your bot is in 100 or more guilds, you must also get your [bot verified](https://support.discord.com/hc/en-us/articles/360040720412-Bot-Verification-and-Data-Whitelisting).

In the future, access to Privileged Intents will come with restrictions and limitations. [Read more here.](https://github.com/discord/discord-api-docs/issues/1363)
On **October 7, 2020** the events under the `GUILD_PRESENCES` and `GUILD_MEMBERS` intents will be turned **off by default on all gateway versions**. If you are using **Gateway v6**, you will receive those events if you have enabled the flags for those intents in the Developer Portal and have been verified if your bot is in 100 or more guilds. You do not need to use Intents on Gateway v6 to receive these events; you just need to enable the flags.

If you are using **Gateway v8**, Intents are mandatory and must be specified when connecting.

## Rate Limiting

Expand Down

0 comments on commit 7bdf9dd

Please sign in to comment.