ASF just told me that it had finished idling this game (Game Tycoon 1.5) for 12:01 hours, but after that, ASF checked my badges page and started to farm that same game again. Then, I went to check how many hours I actually have on that game, and turns out that I have only 2.5 hours. Here's the full log for this particular bot:
http://pastebin.com/raw/1fjk6x2b
(Sorry for the bad title, I just couldn't think of a better one). Thanks!
EDIT: Now ASF did idle the game, I just checked my Steam profile and the in-game time increased to 3 hours. I didn't have to restart ASF. Here are the remaining log lines:
2016-08-10 05:13:52|INFO|master|ShouldFarm() Status for 273770 (Game Tycoon 1.5): 0 cards remaining
2016-08-10 05:13:52|INFO|master|Farm() Stopped farming: 273770 (Game Tycoon 1.5)
2016-08-10 05:13:52|INFO|master|FarmSolo() Done farming: 273770 (Game Tycoon 1.5) after 02:59 hours of playtime!
2016-08-10 05:13:52|INFO|master|IsAnythingToFarm() Checking badges...
2016-08-10 05:13:52|INFO|master|IsAnythingToFarm() Checking first page...
2016-08-10 05:13:54|INFO|master|StartFarming() Farming finished!
You reached MaxFarmingTime, where is the "issue"? I'd say that actually everything is working as intended and ASF worked around steam fuckup.
I thought that something wrong was going on on the ASF side, because it was telling me that it was idling the game, when in fact it wasn't. I didn't knew that Steam could fuck up on this too. Ha. Thanks though
Steam can fuckup in any single request being sent to it, and ASF is supposed to smartly detect the fuckup sooner or later and react accordingly. It's actually very, very rare to spot ASF bug, and 99% of those cases are due to steam fuckup I didn't think about when coding that routine.
So yeah, I'd suggest to take every ASF issue with grain of salt, or even better - simply stop caring and leaving it in background doing it's job. The more you look at ASF, the more issues you will find, and noone of them is fixable.
Most helpful comment
Steam can fuckup in any single request being sent to it, and ASF is supposed to smartly detect the fuckup sooner or later and react accordingly. It's actually very, very rare to spot ASF bug, and 99% of those cases are due to steam fuckup I didn't think about when coding that routine.
So yeah, I'd suggest to take every ASF issue with grain of salt, or even better - simply stop caring and leaving it in background doing it's job. The more you look at ASF, the more issues you will find, and noone of them is fixable.