Discord RPC Errors Causing Frequent Crashes

[ThisIsTeddyBear]

After extensive testing of the VALORANT-rank-yoinker tracker/software, it has become evident that the Discord RPC module is causing frequent crashes due to hitting Discord's rate limits. When the rate limits are reached, the tracker generates errors, making it unstable and unusable in prolonged sessions.

Unfortunately, I do not have the exact logs of the issue as they were mistakenly deleted. However, as part of troubleshooting, I removed the Discord RPC module entirely from the code and ran the tracker without it. This completely resolved the issue, confirming that the Discord RPC module is the root cause of the problem.

Since Discord's rate limiting can severely affect the tracker's performance, it would be helpful to either:

1. Fix the Discord RPC implementation to ensure it adheres to Discord's API rate limits.
2. Provide an alternative workaround (e.g., rate-limiting RPC calls or allowing the Discord RPC feature to be toggled on/off).

The tracker is otherwise stable and works perfectly fine without the Discord RPC module. However, as Discord integration is an important feature, it would be great to have this addressed or optimized.

---

Steps to Reproduce:

1. Use the tracker for an extended period with Discord RPC enabled.
2. Note that errors and crashes occur after Discord's rate limits are hit.
3. Observe that removing the Discord RPC module resolves these crashes.

---

Suggested Improvements:

• Optimize the frequency of RPC calls to avoid hitting Discord's rate limits.
• Introduce a configuration option to toggle Discord RPC on or off.
• Implement a retry mechanism or graceful degradation if rate limits are hit, preventing crashes.

Thank you for looking into this! Let me know if further details or testing are needed.

[ThisIsTeddyBear]

@OwOHamper For example, keep Discord and VALORANT open at the same time, then launch the tracker. Mid-game, try closing Discord and reopening it again, this often causes the tracker to crash multiple times.

Moreover, using RPC for prolonged periods also leads to crashes. In my use case, since I don’t need RPC, I’ve completely removed it from the tracker, and since then, there haven’t been any errors in that area.

And @OwOHamper I'm sorry for using chatgpt but I thought the message was clear enough to everyone understand issue.

[xoxfaby]

it can already be turned off in the config