Bot not reading messages or responding to commands after September 1, 2022

[ryanpohlner]

FYI to anyone with this issue. From jagrosh/MusicBot#1215 (the same applies to this bot):

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

1. Head on over to https://discord.com/developers/applications and find your bot application.
2. Click on the Bot tab on the sidebar
3. Turn Message Content Intent (should be the last checkbox on the page) ON
4. Shut down and restart your bot

[hofrob]

I know it's probably unrelated, but my bot does not play sounds anymore in voice chat. Do you know if anything changed recently?

Sometimes I see "UnhandledPromiseRejectionWarning: DiscordAPIError: Missing Permissions" in the logs. Or this one "Error [VOICE_CONNECTION_TIMEOUT]: Connection not established within 15 seconds."

It's still listening to commands ... but for some reason we can't hear it. I tried giving it more permissions, but this didn't help either.

[dextraa9791]

I know it's probably unrelated, but my bot does not play sounds anymore in voice chat. Do you know if anything changed recently?

Sometimes I see "UnhandledPromiseRejectionWarning: DiscordAPIError: Missing Permissions" in the logs. Or this one "Error [VOICE_CONNECTION_TIMEOUT]: Connection not established within 15 seconds."

It's still listening to commands ... but for some reason we can't hear it. I tried giving it more permissions, but this didn't help either.

Im having the same issue. Since like 2 days. Also seeing the same errors in the logs.

[markokajzer]

Yeah seems like some things have changed on Discord's site and the bot is now fully kaputt. I am currently in the progress of updating the bot to a newer discord.js (and ytdl) version. We'll also update the docs a bit to reflect any new things you need to check here or there.

ETA ~weekend

For progress updates, join our Discord :)

[hofrob]

Awesome, thank you so much!

[markokajzer]

So the bot is upgraded to Discord.js v13 and it can connect to voice again.

To make it resond to messages, not that you need to enable the "message content intent" in your Discord application 👇

You will find this setting in the Bot tab, e.g. https://discord.com/developers/applications/<applicationid>/bot

I'll update the wiki / docs accordingly.

The proper solution of course is to move to Slash commands, which we're thinking about in the Discord at the moment. If you have something to add to that discussion, feel free to join in!