diff --git a/docs/assets/developer-portal/app-verification.png b/docs/assets/developer-portal/app-verification.png new file mode 100644 index 00000000..41c70c40 Binary files /dev/null and b/docs/assets/developer-portal/app-verification.png differ diff --git a/docs/assets/developer-portal/applications-list.png b/docs/assets/developer-portal/applications-list.png new file mode 100644 index 00000000..dd55a108 Binary files /dev/null and b/docs/assets/developer-portal/applications-list.png differ diff --git a/docs/assets/developer-portal/bot-page.png b/docs/assets/developer-portal/bot-page.png new file mode 100644 index 00000000..21d6778e Binary files /dev/null and b/docs/assets/developer-portal/bot-page.png differ diff --git a/docs/assets/developer-portal/bot-token-public.png b/docs/assets/developer-portal/bot-token-public.png new file mode 100644 index 00000000..5f69a506 Binary files /dev/null and b/docs/assets/developer-portal/bot-token-public.png differ diff --git a/docs/assets/developer-portal/create-application.png b/docs/assets/developer-portal/create-application.png new file mode 100644 index 00000000..60ac5b6d Binary files /dev/null and b/docs/assets/developer-portal/create-application.png differ diff --git a/docs/assets/developer-portal/general-information.png b/docs/assets/developer-portal/general-information.png new file mode 100644 index 00000000..c8021d80 Binary files /dev/null and b/docs/assets/developer-portal/general-information.png differ diff --git a/docs/assets/developer-portal/installation-default-settings.png b/docs/assets/developer-portal/installation-default-settings.png new file mode 100644 index 00000000..26b91c65 Binary files /dev/null and b/docs/assets/developer-portal/installation-default-settings.png differ diff --git a/docs/assets/developer-portal/installation-link.png b/docs/assets/developer-portal/installation-link.png new file mode 100644 index 00000000..a1972ebd Binary files /dev/null and b/docs/assets/developer-portal/installation-link.png differ diff --git a/docs/assets/developer-portal/legal-urls.png b/docs/assets/developer-portal/legal-urls.png new file mode 100644 index 00000000..a78cb1df Binary files /dev/null and b/docs/assets/developer-portal/legal-urls.png differ diff --git a/docs/assets/developer-portal/oauth2-generated-url.png b/docs/assets/developer-portal/oauth2-generated-url.png new file mode 100644 index 00000000..db61c4ef Binary files /dev/null and b/docs/assets/developer-portal/oauth2-generated-url.png differ diff --git a/docs/assets/developer-portal/oauth2-scopes.png b/docs/assets/developer-portal/oauth2-scopes.png new file mode 100644 index 00000000..4a20ed40 Binary files /dev/null and b/docs/assets/developer-portal/oauth2-scopes.png differ diff --git a/docs/assets/developer-portal/privileged-intents.png b/docs/assets/developer-portal/privileged-intents.png new file mode 100644 index 00000000..a6671180 Binary files /dev/null and b/docs/assets/developer-portal/privileged-intents.png differ diff --git a/docs/getting-started/creating-your-first-bot.md b/docs/getting-started/creating-your-first-bot.md index e53a2e44..c387ce37 100644 --- a/docs/getting-started/creating-your-first-bot.md +++ b/docs/getting-started/creating-your-first-bot.md @@ -12,18 +12,23 @@ you should: 1. Go to the [Discord Developer Portal](https://discord.com/developers/applications) and click on . + ![The Applications page of the Discord Developer Portal](../assets/developer-portal/applications-list.png) 1. Give your bot a name, and click . + ![The "Create a new app" dialog](../assets/developer-portal/create-application.png) 1. Now, you should see a page like this. - ![image](https://gblobscdn.gitbook.com/assets%2F-MjPk-Yu4sOq8KGrr_yG%2F-MjdW3OQnwUhacopqSWw%2F-Mjd_-mxrJCrzmaXrAg8%2Fimage.png?alt=media&token=b8e2ae6c-2290-4d37-ad7c-eb412f3fb00e) + ![The General Information page of an application](../assets/developer-portal/general-information.png) 1. Click on the tab on the left side of the screen. 1. Click on . 1. You can give it a name, change the Avatar, etc. + ![The Bot page of an application](../assets/developer-portal/bot-page.png) ## Inviting the bot Now, lets get the bot added to some servers. Go to the tab in the left pane and select `bot` and `applications.commands` as scopes. +![The OAuth2 URL Generator with the bot and applications.commands scopes selected](../assets/developer-portal/oauth2-scopes.png) + You may want your bot to have application commands, which is what the `application.commands` scope allows your bot to make. @@ -37,7 +42,7 @@ your bot's permissions, click on to your bot truly needs them. Try selecting only permissions the bot will need. For testing, Administrator permissions are fine. -![image](https://gblobscdn.gitbook.com/assets%2F-MjPk-Yu4sOq8KGrr_yG%2F-Mk6tNY3LfDkjd6pqdpL%2F-Mk6tkdpddEWoa2jczZk%2Fimage.png?alt=media&token=52c8a29f-a798-48f8-a8c7-4ecca2681f79) +![The OAuth2 URL Generator with the generated invite link](../assets/developer-portal/oauth2-generated-url.png) You can use this link to invite the bot. @@ -55,7 +60,7 @@ Now, lets get your bot's token. To do this, you want to: 1. Go back to the tab. 1. Click on the button in the "Token" section. - ![image](https://gblobscdn.gitbook.com/assets%2F-MjPk-Yu4sOq8KGrr_yG%2F-MjdbU12JISJorAZxrKH%2F-MjdbpUsapzb5n15Po5P%2Fimage.png?alt=media&token=118e259f-940a-4f6c-b3a3-c29f3a54100d) + ![The Token section on the Bot page](../assets/developer-portal/bot-token-public.png) Now, you have your bot's token copied to your clipboard. diff --git a/docs/getting-started/rules-and-common-practices.md b/docs/getting-started/rules-and-common-practices.md index a8f69939..a9aa4ad1 100644 --- a/docs/getting-started/rules-and-common-practices.md +++ b/docs/getting-started/rules-and-common-practices.md @@ -35,6 +35,8 @@ Providing a Terms of Service for your bot is optional, though usually a best pra what they can and cannot do with your service, and makes it easier to settle disputes if someone disagrees with you. +![The Terms of Service URL and Privacy Policy URL fields on the General Information page](../assets/developer-portal/legal-urls.png) + Read more in Discord's official [Legal Docs](https://discord.com/developers/docs/legal). ### Developer Policy @@ -75,6 +77,8 @@ possible. We're talking at 76 servers soon. This is because Discord can be somew bot verification, so verifying as soon as possible gives them enough time to verify before your bot reaches the 100 server cap. If a bot is not verified, it cannot grow beyond 100 servers. +![The App Verification page listing the verification requirements](../assets/developer-portal/app-verification.png) + It's also a good idea to only apply for the privileged intents that you need. Applying for intents your bot doesn't use wastes both your time and Discord's time, as your privileged intent request will be denied simply because you applied for an intent you didn't need. diff --git a/docs/popular-topics/intents.md b/docs/popular-topics/intents.md index 64b7032c..1445d79e 100644 --- a/docs/popular-topics/intents.md +++ b/docs/popular-topics/intents.md @@ -35,6 +35,8 @@ Intents allow bot developers to "subscribe" to specific events in Discord. This Discord defines some intents as "privileged" because of the sensitive information they contain. Currently, there are three privileged intents: `members`, `presences`, and `message_content`. These intents must be enabled in your bot's Developer Portal. Once your bot reaches 100 servers, you will need to verify your bot for these intents to keep working and for your bot to be able to be invited to more guilds. +![The Privileged Gateway Intents section of the Bot page](../assets/developer-portal/privileged-intents.png) + !!! tip Only enable these intents if you need them. These intents give your bot access to quite sensitive information about the users in your guild. These intents are privileged to respect the privacy of users, and you should do that as well.