feat(DiscordRPC): add support for targeting a specific Discord instance#241
Merged
Merged
Conversation
…ce (PTB/Canary) Scans the OS pipe/temp directory to detect which Discord IPC sockets (discord-ipc-x) are currently open. If only one client is running the plugin connects automatically as before; if two or more are detected, a dropdown lets you pick which instance receives the Rich Presence, with automatic fallback to the lowest available pipe if the selected one closes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces #223 (closing that one — its branch got tangled up during a rebase attempt and picked up a bunch of unrelated commits). Same feature, rebased cleanly on current master as a single commit, with all of review feedback from the original PR applied.
Adds support for targeting a specific Discord instance (Stable/PTB/Canary) for the Rich Presence. Useful if you run multiple Discord clients at once (e.g. Stable + PTB under different accounts) and want to control which one gets the Tidal activity instead of just whichever client happened to open first.