Please bullet point the changes you have made below:
Adds a new method getAllIntentsApartFromPresence to DiscordUtils to generate intents without the presence intent
Changes the bot so that it doesn't listen to presence intent
The rationale for this is based on a bit of a hunch, but, reading https://github.com/discordjs/discord.js/issues/3533 it seems as though the presence intent causes a GuildMember object to come back without a joinedAt attribute. In the bot we are assuming this is always present, so if there is a presence update and the member has been cached we are running into an issue where the cached GuildMember does not have this attribute. In theory if we stop listening to this presence and cache the GuildMember in the proper way we may resolve some of the crashing we are currently seeing
Overview
Please bullet point the changes you have made below:
getAllIntentsApartFromPresencetoDiscordUtilsto generate intents without the presence intentGuildMemberobject to come back without ajoinedAtattribute. In the bot we are assuming this is always present, so if there is a presence update and the member has been cached we are running into an issue where the cached GuildMember does not have this attribute. In theory if we stop listening to this presence and cache the GuildMember in the proper way we may resolve some of the crashing we are currently seeing