Discord_Shutdown does not unset Discord user's Playing status about discord-rpc HOT 7 CLOSED

Fixed on canary and ptb, should get to stable soon.

from discord-rpc.

Should be fixed in stable now.

from discord-rpc.

Discord_Shutdown clears out the callback pointers so none of them are called, shuts down the io thread, and closes the connection to Discord. The intent was for this to get called as your game shuts down, but it is safe to call whenever and re-init later if you want.

Right now the Playing <game> status in Discord is driven by the process existing, not by the rpc connection. We're planning to add an explicit call to disable it, though.

from discord-rpc.

But the process doesn't exist in my scenario. For example, this was taken 5 minutes after starting send-presence.exe, typing f into the prompt, and closing it as soon as Discord: ready was shown. As you can see, no send-presence process exists, but the RP info is still displayed with the time left having counted down to 00:00.

from discord-rpc.

Looking at the Send-Presence example 'Discord_Shutdown' is called twice when you 'quit' using the q input option it causes this issue, I actually did this in my own code too accidentally and had the same issue where the rich presence status was stuck displayed even though the process had closed after the 'Discord_Shutdown' function was called (all be it was twice).
After removing the second un-needed execution of the 'Discord_Shutdown' function and testing it seemed to have fixed it in my code/senario... Could this be an issue then with executing 'Discord_Shutdown' more than once? If that's the case even though you shouldn't there probably should be something stopping this issue from even happening in the first place.

from discord-rpc.

Nah, Discord_Shutdown should be safe to call a second time. That sounds like a bug on Discord's side.

from discord-rpc.

Good that this is fixed. I thought I was going crazy.

from discord-rpc.