10 Replies
- What's your exact discord.js
npm list discord.js and node node -v version?
- Not a discord.js issue? Check out #other-js-ts.
- Consider reading #how-to-get-help to improve your question!
- Explain what exactly your issue is.
- Post the full error stack trace, not just the top part!
- Show your code!
- Issue solved? Press the button!
- ā
Marked as resolved by OPShard did not receive any guild packets in 15000 ms.
I think that's what causes the issue but I'm not sure
I'm also listening to client.rest.on('rateLimited'), but nothing
it suddenly stopped working and now none of my 12k guilds can use it š
tried it both on VPS and on my windows pc, same issue
lmk if I can provide any code / whatever to fix this
oh okayyy
what does zombie shard mean?
but what could be the issue?
I have no idea of how websockets even work
roughly 12k
I read that one shard can be 2.5k max
so I have shardCount: 5 rn
yea
I tried to put the recommended 12 shards, but same problemhttps://i.anderle.dev/08xQBhjgS2.png that doesn't seem to work either
OHH let me try one sec
same issue, some shards say
Heartbeat acknowledged, latency of 1461ms. or smth
but like half of them same issue
it's a well known vps host which should definitely have a good network connection
like one of my friends has a bot in more than 100k guilds and it works fine
no I don't use that
when creating the client I added makeCache and sweepers
could that be an issue?
basically I set everything to 0 that I don't need
because I experienced high ram usage
one of my friends said that it could be rate limit, even if I don't get any log message?
alright
yess
nothing
raw doesn't exist
or am I
dumb
ohh I'll just change it in the dist then
aight
ReferenceError: data is not defined
oh wait
I see
data =>
now I don't even get a ts error
a lot of GUILD_CREATE
should i copy smth or
that's like a part
it did spam a lot
still not able to fix
ye, I'll disable them all and check again
it worked again for some reason btw
but not anymore :kek:
yeah I already did, thank you
a friend is helping too, and he's asking why does discord.js send identify before first heartbeat
I started without anything, only the client but same thing
like create the client object, add the listeners and then call client.login
it doesn't work on my windows machine with 50mbps and not on my vps with 500 mbps
do you think switching to using a ShardingManager will fix this?
because the discordjs guide says internal sharding is not good for bigger bots
okay
man btw
thank you so much for helping me with this
oh btw for the network traffic
my vps shows it's using only 10 mpbsbuildStrategy?
or wdym
uhh alright?
I'm not sure if I understand
this?
I'm lost
what do I do with that
ok sorry I don't think I understood what you mean with "using worker strategy"
couldn't find that example, but thank you
yeah no worries lmao
just wasn't sure what you meant
nah that didn't change anything
I'll make sure and try on my vps too
yeah same thing
I restarted the vps and noticed something new
it worked for 4/5 shards this time
like I look at the messages "shard received all guilds"
I got this message from 4/5 shards and the last shard was missing 1.7k guilds
but I got the clientReady event this time
but that would mean, in 1.7k guilds the bot won't work, right? nvm the last shard got ready before the client was ready
I'm wondering why it works completely fine and fast for those 4 shards, and then suddenly stops working and returns to being super slow
then this time again it stopped at the first shard already, after like 200 guilds
and this time it worked, all shards started in not even 20s
so it's always different every time and I refuse to understand why š
yeah it's called "shared vCPU"
oh wait that could mean
someone else is blocking the network or smth?
but like why wouldn't it work on my own pc then
no, only clientReady
no I didn't, I can do that
I'll just keep on debug then
oh yea
okay same error
only listened to the debug event
oh yeah I'm using the newest discordjs version on my windows pc and 14.13.0 on my vps
uh I was lazy to update
I think
I updated a week ago and wanted to push this to the vps soon
but then this issue came up
so yep now they're on different versions
yesss
š
my node version is 20.17.0 in case you need it
yeah, even in the same region
the vps is like 20km away from me
I mean my discord is working fine or is that smth else
I mean my desktop client
can you like.. connect to a different one?
oh also this
shouldn't it connect to somewhere in EU if my vps is there
(idk what resuming session means just wondering about the url)
can you check this somehow?
I mean can I
it's been happening for let's say 2 weeks, whenever I tried to restart the vps I got it fixed
but today a restart didn't fix it
can it even be that a relay is down for such a long time?
but it's weird that it connects to us east right?
yeah I don't think it's that tbh
seems to be related to intents and / or makeCache settings
I started the bot without anything (just shardCount and empty intents) and it worked
now I tried guilds and guildmembers intents and it worked too
I'll slowly add more, and see where it stops working
I THINK TOO
YES
YESYESS
it's
GuildPresences
it works with all other intents
except this
and the good thing is
I removed the single feature I needed this for
ages ago
that explains why it sometimes starts being slow at the very start, and sometimes everything goes well for 4/5 shards?
I mean like
sometimes that one guild
could be in shard 4
and sometimes in shard 0
or is that the same always?
oh I see
oh interesting
:method: (static) ShardClientUtil#shardIdForGuildId()
@14.16.1
Get the shard id for a given guild id.man, thank you so so much for spending so much time on this
I really appreciate what you did for me
will take a look!
this was such a hard one
really, thank you
I'm just
so happy rn
thank you lmao
and for being so patient
I'll mark this as solved