Maybe bot should re-start farm if farming is stuck?

[Rudokhvist]

Just to discuss it separately from issue #16.

As @Haoose pointed, it'll skip to the next game, and assume that currently farming game is 100% farmed. It's nice to note that it's only temporary, so as I said, on next CardsFarmer module restart (e.g. triggered by steam disconnect, or cd-key activation), bot will recheck if assumption is proper, and if needed, farm the same ID further. It's a mechanism which tries to detect that cards don't drop for some reason (steam-related).

Maybe it would be better not skip the game, but re-start farming instead? I've met the problem of game stuck for 10+ hours, and I solved it either by restarting bot with !stop and !start, or by giving a !farm command. Why not make this process automatical, and maybe even decrease timeout to 5 hours (no big deal if bot is really still farming, it would just continue after restart.)

[JustArchi]

As I said bot will resume farming that appID on next module restart.

It's more for games with broken hours reporting, temporary issue we discovered together with @Pandiora , when one game wouldn't drop cards neither update hours played. That was the main reason to implement a module that would skip a game for some time and move onto other ones, and then eventually try the faulty game again on next module restart.

[Rudokhvist]

Okay, I'll try to investigate this "stuck" games I talking about to find the reasons it happens. Maybe then we'll return to this problem again.

[JustArchi]

Closing it until then, as there's no bug regarding this, and bot indeed does handle stuck games after 10 hours.