-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discord RPC] No indication of what game you're playing when inside a level #472
Comments
I've wanted to expand Freelancer Support for Discord RP for a while. I'll address this as well. |
I don’t think old Discord clients or mobile should really fall within our concern - if you’re using Discord, you probably should be using the newest version, because it’s the only supported version, and mobile seems like a niche that discord themselves should add support for. |
@RDIL let me know if the suggestion i made is good enough, or if you have something else in mind. |
I think that we could do that, but instead of such a long message, we could say “In HITMAN [version]” |
Another way to approach this would be to rename the discord application to HiTMAN and make the hover text have the Peacock shizz in it, so it's clear what game the user is playing without having to hover over the image. |
(Just for the record, it’s stylized in all caps, but the game font’s uppercase i just doesn’t have the top and bottom lines, so it should be written as HITMAN. Sorry, just an OCD rant.) |
See Exhibit A:
This is what the custom discord RPC looks like when the user is inside of a level.
The issue is that there's no indication of what game said user is playing other than the image (and not everyone has played HITMAN before, therefore they wouldn't be able to tell what game they're playing from their discord profile).
It does say "Playing HITMAN WoA" when browsing the main menu but that text is replaced with the mission title when entering a level.
Not a bug but a small issue I saw with the discord RPC.
The text was updated successfully, but these errors were encountered: