-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
arRPC sending different headers than official discord client over unix socket #95
Comments
I've just discovered that the 3rd party FreeBSD implementation of the Discord Application won't talk to the Mudlet application I'm coding for because it is using this project - apart from anything else when my Application starts up on FreeBSD the callback message it is getting contains the bogus values you can see on lines 42-50 of: https://github.com/OpenAsar/arrpc/blob/main/src/server.js As it happens not doing that check (or making my application check against the value |
I am on the Vesktop Flatpak, using a Discord RPC bridge EnderIce22/rpc-bridge to connect to games running via Proton. It works flawlessly with the official Discord client, but not the Vesktop Flatpak. I have two log files for the game Hades here:
vesktop-flatpak-with-bridge.log
official.bridge.log
official.bridge.log is the log file with the official discord client running. The first response from discord-rpc over the pipe is a DISPATCH command with the header
"^A^@^@^@y^A^@^@"
, and data from my user profile provided.However, the first response from arRPC over the pipe in vesktop-flatpak-with-bridge.log is a DISPATCH command with a completely different header:
"^A^@^@^@E^A^@^@"
Notice there's an "E" in the spot where there should be a "y" - In addition, the username is "arRPC" and it does not contain my user info.This breaks the implementation of RPC-bridge by EnderIce as the Unity Game does not know what to do with this different header, so it does not send a response back over the pipe, breaking the rich presence.
Please fix so the headers match.
The text was updated successfully, but these errors were encountered: