Closed afonsojramos closed 2 years ago
What would this be useful for? I did some brief testing and found that, if provided anything other than 0
or 3
, the payload is actually rejected with an error. Furthermore, providing 3
results in the type
being changed to 0
anyways.
I'm happy to oblige if I can understand the use case, but right now, I don't see the point.
In my view, this would be useful just as another way of customising what is displayed in Discord. I have build a Rich Presence for Trakt (https://github.com/afonsojramos/discrakt/) which enables integration with all the services that Trakt is able to connect to, such as all of the ones below:
As this is for TV/Movies, the "Watching" verb would apply much more than the "Playing" one does!
I see where you're coming from now - the issue is that it won't work. As stated in my previous comment, Discord does not let rich presence applications actually change their ActivityType
; it will always be Playing
.
But you mentioned that it could be 0
or 3
, which is already better than just the current 0
, wouldn't you say?
I said it could be 0
or 3
, but I also said passing 3
is changed to 0
by Discord when the request is received.
Regardless of whether 0
or 3
is sent, it's treated as a 0
by Discord, so it makes no difference.
Oh well, that's unfortunate, thanks anyway!
The ActivityType enum is present in the SDK Docs and, even if it says "ActivityType [...] will be discarded and will not change anything in the client." I can find cases online where such has been said to be possible (here).
Has this been changed recently? Would it be possible to have this implemented?