-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
TypeError: thread.members._add is not a function #10393
Comments
Stack trace from another crash
|
Do you by any chance have any custom |
I do not: https://github.com/DawnbrandBots/emcee-tournament-bot/blob/master/src/index.ts#L28-L39 I have that on a different bot but that bot has yet to crash because of this despite being in exponentially more servers. |
|
Which package is this bug report for?
discord.js
Issue description
Creating this issue for posterity, bulk of the discussion and fix were noted here: https://discord.com/channels/222078108977594368/1248260322163294238
After a recent update to @discordjs/ws, it seems like Messages are being instantiated as channels in some very specific cases.
Full trace of the issue is here:
Sample "TextChannel" that is actually a "thread":
(Note the
memberCount
property here means we know it's a thread)I think the possible problem commit was: #10278
Code sample
Versions
Issue priority
Medium (should be fixed soon)
Which partials do you have configured?
User, Channel, GuildMember, Message, Reaction, ThreadMember
Which gateway intents are you subscribing to?
Guilds, GuildMembers, GuildPresences, GuildMessages, DirectMessages
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: