Fixed role react issues #86
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The role reaction cog recently broke, due to this change. Basically, Discord added a new "Intents" system for bots to have more granular permissions or something. By default, bots no longer have permission to access member data, which was causing issues. This PR fixes the issue simply by making the bot require all intents to avoid permission issues (there's only one other one that isn't enabled by default anyway). However, this fix comes with a few extra steps required:
First, it requires updating to the latest version of
discord.py, so you'll need to runpip install -r requirements.txtagain.In addition, you also need to enable Privileged Intents on the bot's developer portal page:
Boton the left sidebarPrivileged Gateway Intentsenable both options