Commands not working after going from version 4.2.0 to 4.3.0

[gusty basalt]

Hi, so i upgraded from v4.2.0 to v4.3.0 and now the commands are no longer working. They do work when I @ the bot, but then some interaction where the bot reads the next messages sent in the chat do not work.
It seems like the bot no longer has the message content intent permission, but it is toggled on the application page and it worked fine again when I went back to v4.2.0
Any help appreciated

[versed robin]

Hello, I'm an automated bot to help people with common issues. Here's a list of stuff that I think are related to your problem.

Automated suggestion: You don't have the Message Content Intent enabled

As of September 1st 2022, Discord started requiring message content intent for bots that want to read message content. This is a privileged intent!

If your bot has under 100 guilds, all you have to do is flip the switch in the developer dashboard (over at https://discord.com/developers/applications, also see the image) and then specifying the intent in your DiscordConfiguration (see the code example)
If your bot has over 100 guilds, you'll need approval from Discord's end.

Even though you can just use this to get away with it, it is recommended by Discord to use Slash Commands whenever possible, so look into that if you can (Slash Commands Documentation)

More info:
https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-FAQ

Code Example:

DiscordConfiguration config = new() {
    // ...
    // If you do not set this, your bot will fail to start with the error code: "Disallowed intent(s)"
    Intents = DiscordIntents.AllUnprivileged | DiscordIntents.MessageContents,
    // ...
}

This action was performed automatically. Please use the buttons below to vote on your experience

[neon dagger]

Which intents do you register in your discord configuration?

[gusty basalt]

none, wasn't needed in 4.2.0, guess that's probably the issue then

[neon dagger]

Yes