Not getting hello @discordjs/ws
identify payload: https://hastebin.abelpurnwasy.com/hejobegana.js
dispatch event: https://hastebin.abelpurnwasy.com/yaxivupali.coffeescript
manager:
12 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 staffi have no clue what you think you're doing, none of this is valid
you are not at all supposed to be manually sending identify/resumes/heartbeats
the library does all of that for you
So @discordjs/ws does all that automatically?
yes...? im so confused what made you think otherwise
did you look at the readme
I’m trying to achieve zero downtime deploys so my gateway stays online and my client can go off and come back on after few mins to continue
I’ll be honest I was not using the package before that’s why all of that there and no I didn’t look at the readme
I just read the readme I’ll do some changes
literally set up a basic manager, and provide
updateSessionInfo
and retrieveSessionInfo
to point to an external store
that's all you needohh
still dont get the heartbeat logs
those aren't debug logs
there's a HeartbeatComplete event
https://discord.js.org/docs/packages/ws/main/WebSocketShardEvents:Enum
those logs from my client
my proxy heartbeat completes though
{ ackAt: 1730468366446, heartbeatAt: 1730468366384, latency: 62 } 0
no, I just meant heartbeats dont go to debug :jynEHEH:
oh
my client destroys the websocket since it thinks hello not received
the thing is i need to send events to my client (discord.js) that is connected to the proxy or itll end up doing:
https://hastebin.blackforthosting.com/alutakamec.yaml
Is it possible to do this in discord.js client options?
Ohhh