Naleksuh Posted March 18, 2020 Report Posted March 18, 2020 Recently, client.gamesPlayed randomly stopped working for me. Everything else works fine, but the bot is online and not in-game. I have not made any changes to my code in several months when it just randomly stopped working, and it appears McKay last contributed to the repository six days ago, leading me to believe the problem is a change to steam's API. Has anyone else encountered this strange error? Quote
Dr. McKay Posted March 18, 2020 Report Posted March 18, 2020 It still works fine for me. Make sure your account owns the game you're trying to play and that the account's game visibility state is public. Quote
Naleksuh Posted March 18, 2020 Author Report Posted March 18, 2020 It's public and free (TF2). Like I said, it was working fine for several months then with no changes randomly stopped, which is why I strongly believe it is something in the third-party. However, I reinstalled the repository and that seemed to fix it. It could have been a change to there. Quote
Naleksuh Posted May 8, 2020 Author Report Posted May 8, 2020 It's been around two months, but it happened again. Interestingly enough, it's ingame as it should be when actually viewing the profile, but shows as Online from Steam Friends. This leads me to believe it's neither a bug with my code, nor a bug with the library, but with steam itself. Restarting the bot fixed this error, but it is something to be on the lookout for. Quote
Dr. McKay Posted May 9, 2020 Report Posted May 9, 2020 That does seem like it's a Steam bug. Did you try restarting your own Steam client, by chance? I wonder if that might have resynced things. Quote
Naleksuh Posted May 12, 2020 Author Report Posted May 12, 2020 I did not try that, only tried restarting the bot (which fixed it). It's possible it fixed it not on the bot's end, but by sending a status change event. If this happens again, I will try restarting my Steam client and see if that fixes it. Quote
Naleksuh Posted February 18, 2021 Author Report Posted February 18, 2021 Update: it's been 9 months since my last post (11 months total), and it has happened a third time. I can confirm that restarting my own steam client does fix it. So, it seems like restarting the bot just pushes a refresh, and really only Valve can fix this. However, it might be something in the bot that is triggering it initially Dr. McKay 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.