Added Support for Discord Canary and PTB in Rich Presence #7
Conversation
This file contains 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
…cordPTB.exe to the process list check
|
Sick! Thank you very much for help! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi there,
I've submitted a pull request to address issue #6 I opened myself where the Rich Presence feature was not functioning correctly with Discord's Canary build.
Problem:
The
discordProcessList()function in ProcessListFunc.java was checking for only the "Discord.exe" process, which corresponds to Discord's stable release, but not the Canary or PTB versions.Solution:
I've updated the
discordProcessList()function to check for the "DiscordCanary.exe" and "DiscordPTB.exe" processes in addition to "Discord.exe". This update allows the application to detect and support all versions of Discord: stable, Canary, and PTB.I have tested these changes and confirmed that they fix the original issue. The Rich Presence feature now functions as expected in both the stable and Canary Discord builds.