As we have hit the deadline for intents (Oct 7th), bots now operate under the default set of intents, which is all intents minus the privileged ones (members and presence).
For now, bots just declare their intents while instantiating the bot, but we could do something better.
My proposal is to add an intents key on the yaml configuration file, it would point to a list of strings representing the fields in the discord.Intents object. It would work like this:
- Start off from the default set of intents,
discord.Intents.default()
- Add or remove intents if they are in the list or the string starts with
! respectively
- Feed that to
Bot(..., intents=intents)
Example, adding the members intent but removing the typing intent:
intents: [members, !typing]
As we have hit the deadline for intents (Oct 7th), bots now operate under the default set of intents, which is all intents minus the privileged ones (
membersandpresence).For now, bots just declare their intents while instantiating the bot, but we could do something better.
My proposal is to add an
intentskey on the yaml configuration file, it would point to a list of strings representing the fields in thediscord.Intentsobject. It would work like this:discord.Intents.default()!respectivelyBot(..., intents=intents)Example, adding the members intent but removing the typing intent: