-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
GuildDelete event triggers every time bot starts #5350
Comments
I am seeing the same running on Ubuntu 18.04 |
12.4.1 is no longer supported, please check 12.5.1 for the same issue. bot.ws.on("GUILD_DELETE", console.log); |
Can reproduce on Output that @almostSouji requested: { id: 'censored_guild_id' } 0 Good thing that I keep track of guild add / removes! The guild in question actually removed my bot around 2021-02-24... However every time that I start my bot, that guild will have a |
I actually did not expect that to log anything. Since that's the case this behavior is coming directly from Discord and there is nothing we can do about it. Discord devs are aware but currently unsure about why it happens. |
If you want to prevent it from, say sending the set message on guildDelete like I have, you could add something like
|
I also get the same error. This should be fixed with #5367
This also happened to me. The guild which triggered it was removed about a week ago. |
Reopening, apparently this is something we need to handle (they should however not be considered unavailable) From the discord developers server:
|
This is handled in #5367 |
Please describe the problem you are having in as much detail as possible:
Every time I start the bot, the guildDelete event triggers. However while the guild object is valid, the name and member count is undefined. This results in an error.
Include a reproducible code sample here, if possible:
Can't be reproduced without this specific Token. May be related to Discord itself. Starting the bot with a different token fixes the issue.
Further details:
Relevant client options:
The text was updated successfully, but these errors were encountered: