Discord protects third-party access to sensitive information with privileged intents.
Inventor-Supported Intents
Inventor currently only supports receiving data from the Message Content and Server Members intents if you choose to enable them. You can use Inventor without one or both intents, but some functionality will be unavailable.
Updating Intents
You can update your bot’s intents at any time, unless your bot is verified. Verified bots must pass approval for each intent they require, which involves a submission to Discord with the purpose of the intent.
Tip: Discord will not approve the message content intent solely for the purpose of message-based commands.
Discord is also good at recognizing token ‘intent-worthy features’ that only exist because the bot developer wants to also enable message commands. They regularly deny bots for this.
Verified bots should not request intents from Discord that they do not actually require to operate. There is nothing wrong with using the platform (slash commands, etc.) and we highly recommend that verified bots avoid using privileged intents as much as possible to enhance user privacy. You can always put message commands on a secondary development or private bot.
To update your bot’s intents:
-
Go to your bot’s application page in the Discord Developer Portal.
-
Go to the “Bot” tab and, under “Privileged Gateway Intents”, enable/disable intents as needed.
-
Save your changes on the developer portal.
-
Go to the Inventor dashboard, click “Settings”. Under the “Intents” tab, toggle the intents to match the ones you enabled on the developer portal. For verified bots, the process is more involved, as noted above.
-
Save your changes on the Inventor dashboard.
-
Check if your bot is online on Discord. If it is offline, restart your bot from Inventor settings.
-
If you encounter any issues, try using the “Sync with Discord” option in bot settings on Inventor. This can occasionally resolve intent issues.
This process can result in one or more Inventor Runtime errors being generated, usually relating to bot disconnects or gateway errors. If you follow the instructions and your bot is working as expected at the end, you can safely ignore these errors.
Keep in mind that removing intents may break some of your flows which may rely on data or events that are provided through intents. This breakage can produce flow errors that are unrelated from the temporary connection issues of revoking the intent. Those errors (or any other breakage in functionality) may need to be corrected separately.