引用自 *****gamer2014：

Its an authenticator error.. You have to open Idle Master, click on sign out, and then sign in and reauthenticate on ur phone app-.

I don't have mobile auth. It's not authentication error, signing out and signing in does nothing = the latest IM tells me idling complete while an old version I was using times out retrieving the badges page.

ASF is working for me. Too bad it doesn't allow idling while you're playing a game yourself, which is why I've always used IM for my main account, but now had to enable ASF for the main instead.

I'm using SAM now since IM is completely useless to me while this issue occurs. Will probably give ASF a try next.

Still same issue.

Started happening today. What's going on? Steam community issue?

Edit: ok, just started successfully now. Hopefully it'll keep being logged in. Having to log in every single time I start it is annoying enough (still less annoying than idling without the tool ofc.)

Edit 2: As predicted, logged out before the first card dropped. Actually after 15 minutes, when it tried to check the cards remaining I guess.

Edit 3: Looks like it's something about my community profile - even my web-browser keeps losing log-in with steam. I browse community for a bit, next page I'm logged out again. WTF. At least Steam Client hasn't asked me to relogin, but no clue why my browser and IM sessions keep being invalidated. Is Valve trying some new security feature?

Everything was working yesterday, but today when I tried logging in with Idle Master it said "Please verify your humanity by re-entering the characters below." Except there's nothing to enter and nowhere to enter it.

Do I need to update my version of IM, or is the version dealing with the captcha not out yet?

Edit: Tried again now, and no more captcha message. Weird.

Euleusis - dropped all 3 cards, Steam play time shows 31 minutes.

Since yesterday I'm getting invalid cookie too. I'm using the old non-GUI version of idlemaster which doesn't require passwords. Tried updating the cookie information, didn't help.

So the issue is there with the current GUI version of the program too?