JDA.getPresence().setGame(); randomly doesn't work
See original GitHub issueWhen I use
JDA.getPresence().setGame(game);
it mostly updates the game of my bot, but sometimes the old game stays.
JDA.getPresence().setGame(null);
also doesn’t work everytime. Sometimes it doesn’t clear the game, the bot still plays.
I’m using JDA 3.0.0_180.
Issue Analytics
- State:
- Created 6 years ago
- Comments:30
Top Results From Across the Web
Discord jda bot || UserUpdateActivitiesEvent does not trigger
I used jda.getUserCache(); to check if the caching worked and I am i the cache, but it still doesn't work. java ...
Read more >Code a Discord Bot in Java with Discord JDA! (Episode 1
Hello. In this new series, I teach you how to code your own Discord in Java using Discord JDA ! In this episode,...
Read more >Presence (JDA 4.4.0_352 API)
Sets all presence fields of this session. Parameters: status - The OnlineStatus for this session (See setStatus(OnlineStatus) ) ...
Read more >Gateway - Discord Developer Portal
The Gateway API lets apps open secure WebSocket connections with Discord to ... If an app doesn't receive a Heartbeat ACK, it should...
Read more >report_volume5.pdf - Senate Intelligence Committee
(U) The Committee found that Manafort's presence on the Campaign at;td proximity to. Trump created opportunities for Russian intelligence ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That actually wouldn’t work. You don’t receive any kind of notification if a different login on the same account changes your game. So if you have 2 bots logged into the same account (we’ll call them LoginA and LoginB), if LoginA sets the game to “a cool game”, and then LoginB sets it to “a weird game”, LoginA’s JDA will still report the current game as “a cool game” even though it has changed for everyone else.
Additionally, with only one login, it still gets updated internally even if it fails.
Rip, didn’t know that.