#Failed to find guild, or unknown type for channel
45 messages · Page 1 of 1 (latest)
• What's your exact discord.js npm list discord.js and node node -v version?
• Post the full error stack trace, not just the top part!
• Show your code!
• Explain what exactly your issue is.
• Not a discord.js issue? Check out #useful-servers.
After doing some debugging, This is what I constantly see on every login.
Discord version: 13.9.0
Node version: 16.18.0
Another thing I noticed was this:
I personally don't believe I need sharding because I haven't hit the limit nor am I anywhere close to it
I'm unsure on whats the cause for this and would love some help
To add a little more information on this: I have this one guild that always emits under the guildDelete event every single time before my bot logs in. I assume that could be the Unavailable guild but how do I fix this?
This is v13 ignoring Forum channels because it doesnt know how to handle them
I see. Is there any way to speed up this process?
Also what's the cause for this? Forums too?
Speed up what process
All the errors that come up
Thats why it only recommends 1
They arent errors, theyre just debug output
This is a known Discord thing, cant remember why it happens
Yeah true however that takes ~20s for my bot to login
So the initial number is 1 and not 0 i assume?
Is there any way to prevent this?
I think you can change the client ready timeout
ahh, because debug shows WS -> Shard 0 so i was confused
So I wasn't sure if shard starts at 0 or 1
Shard 0 and shard 1 would be two shards
no, not a discord.js bug
We only handle the data Discord sends us
Is it based on certain bot applications only?
Cant tell you
It doesn't happen on my dev bot
if i set it to 0, would it just ignore it then?
That would not be a good idea, means you're giving it no time at all to get guilds ready
I see. i just made a guild check to ignore it so it's okay
So you reckon I just leave it at the default one and let it take 20s to get it all up?
Does v14 handle forums correctly?