-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discord Issue] As of September 1st, the bot doesn't respond to commands! #1215
Labels
Comments
3 tasks
Will slash commands be supported some day? |
Yes, slash commands will eventually be supported. |
3 tasks
3 tasks
3 tasks
3 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug
As of September 1st, the Message Content Intent is being enforced, which is the "intent" that allows a bot to read the contents of messages. JMusicBot needs this intent to be able to have custom-prefixed commands. If your music bot stopped responding to commands on September 1st, it is almost certainly because the bot's intents have not been migrated and you'll need to update its settings in the developer portal. (Note that if your bot is in more than 75 servers, it will likely be permanently broken. JMusicBots should be kept private).
The Solution
Version Info
This affects all connections to Discord, regardless of which version of JMusicBot is used.
The text was updated successfully, but these errors were encountered: