arRPC sending different headers than official discord client over unix socket

[relma2]

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.