Gracefully stop the bot

Is there any way to gracefully stop the bot? I want it to appear as offline as soon as it stops.

client.user!.setPresence({
  status: "invisible"
});
await client.destroy();

client.user!.setPresence({
  status: "invisible"
});
await client.destroy();

doesn't seem to work…
Also, what's the reason that

setPresence

setPresence

unlike basically any other similar method isn't async?

d.js docs•8/22/22, 11:13 PM

• What's your exact discord.js

npm list discord.js

npm list discord.js

and node

node -v

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.

조

조아오•8/23/22, 2:12 AM

I think you need to await the

setPresence

setPresence

since destroying the client might stop your request from actually firing

ChilliOP•8/23/22, 2:45 AM

setPresence does not return a Promise, it returns the presence synchronically, looking at the type definitions…

ChilliOP•8/23/22, 2:46 AM

ChilliOP•8/23/22, 2:47 AM

()

ChilliOP•8/23/22, 2:48 AM

I tried to await another API thing before destroying the client (force fetching the client user, to be exact), but the bot still didn't immediately switch to offline after stopping it

조

조아오•8/23/22, 2:48 AM

I uses the Ws, thats why it's sync

조

조아오•8/23/22, 2:49 AM

Maybe add an 1-2s cooldown before destroying? idk

조조아오 I uses the Ws, thats why it's sync

ChilliOP•8/23/22, 2:52 AM

Ws? As in websockets?

조

조아오•8/23/22, 2:59 AM

It calls the websocket to the change, not a rest request and when you destroy the client you also destroy the Ws

조

조아오•8/23/22, 2:59 AM

That might be the race condition

ChilliOP•8/23/22, 3:24 AM

There's another weird thing: editing a message in the exit handler takes around 15 seconds…

ChilliOP•8/23/22, 3:25 AM

this is the handler

ChilliOP•8/23/22, 3:26 AM

Approximately 15 seconds between and , and the only await inside is editing a message saved in a variable