These are the required steps for Discord Rich Presence when arRPC is running natively (not in a Flatpak), when you want to integrate various Flatpak-based applications that have built-in Discord RPC status support. These instructions are true for all natively installed Discord clients (including the official client, and all third-party clients that either bundle or support using a natively running arRPC on the host machine).
- Enable "Activity Privacy: Share your detected activities with others" in Discord.
- Ensure that Discord RPC is enabled in your chat client. The official Discord client always provides it, whereas Vesktop for example has it under "Vesktop Settings: Enable Rich Presence via arRPC".
- If you are using a native Discord client when running Flatpak-based RPC apps (such as Heroic), then you must install the discord-flatpak-rpc-bridge, to create a bridge between the Flatpak Discord RPC socket and your native Discord RPC socket. That project has a detailed description about why the Flatpak sandboxing makes that necessary, and why there will never be any other solutions.
There's no Wiki, so I am adding the information as a ticket. Perhaps it would be suitable in the Readme so that third-party arRPC-based application developers can discover the information.
These are the required steps for Discord Rich Presence when arRPC is running natively (not in a Flatpak), when you want to integrate various Flatpak-based applications that have built-in Discord RPC status support. These instructions are true for all natively installed Discord clients (including the official client, and all third-party clients that either bundle or support using a natively running arRPC on the host machine).
There's no Wiki, so I am adding the information as a ticket. Perhaps it would be suitable in the Readme so that third-party arRPC-based application developers can discover the information.