ASF stopped working 2 days ago

STEAM GROUP

Archi's SC Farm Archi-ASF

Join Group

STEAM GROUP

Archi's SC Farm Archi-ASF

4,673,131
MEMBERS

50,403

IN-GAME

358,311

ONLINE

Founded

October 29, 2015

Language

English

Overview Announcements Discussions Events Members Comments Curator

All Discussions > 🇬🇧 Support (English) > Topic Details

Gr3ylok Dec 10, 2018 @ 12:39am

ASF stopped working 2 days ago

Well, my alts don't seem to have any problems, my main however doesn't want to idle the cards cause it can't get the badge information?

Ye I checked the badges page, everything loads normally, I also restarted ASF and the box it was running on and all seems fine, yet it wont load for that account.

https://gyazo.com/f87c808db314484166b1c07f1d33a08c

the parental pin is in the config (config made months ago, never had issues) so what do I do now?

A moderator of this forum has marked a post as the answer to the topic above.
Click here to jump to that post.

Originally posted by Archi:

Originally posted by Gr3ylok:
Originally posted by Ryzhehvost:
Anyway, glad you were able to resolve it. I would also suggest that parental pin was somehow connected to it, because after you made new config you got completely different issue. But only thing that matters is that it works for you now.
How would that pin screw it up tho, doesn't make sense because ASF was running on that machine for many months, with the SAME config I use now? Ohwell Ima give it a rest, thanks.

If you for one second forgot about your only argument of "it worked before" then you'd analyze the ASF changelog and found out that PIN property was renamed, and then realize that you forgot to update your old config for up-to-date ASF release, what regenerating config (and you falsely believing that login limiter delay has anything to do with it) actually did.

And if you compared your old config with new config carefully, then you'd also see how old one used SteamParentalPIN while new one has SteamParentalCode - but you compared global config only, the one that has nothing to do with your issue.

< >

Showing 1-15 of 17 comments

Rudokhvist

Dec 10, 2018 @ 12:46am

Try to enable debug mode and check the log, maybe you'll find out the reasons why it fails.

Gr3ylok Dec 10, 2018 @ 1:27am

Originally posted by Ryzhehvost:
Try to enable debug mode and check the log, maybe you'll find out the reasons why it fails.

I see it has problems with GetClanChatGroupID > they do respond in said groupchat.
https://gyazo.com/a8e32ef1dc31191554381b1f09fd93b0
Also requests failing with APIkey? and the badge page obviously.
https://gyazo.com/7c3a6acc0739f2657a451a40ac4223d3
Didnt really notice anything else, suggestions?

Gr3ylok Dec 10, 2018 @ 2:11am

Closed ASF
Downloaded steamidlemaster
SIM is idling metal gear solid
Open ASF get message that the account is occupied (sim)
Close SIM
ASF notices account is no longer occupied and resumes idling
Request failing when checking badgepage
https://gyazo.com/d283761f8252ec34a029db1ae3b31d39

Last edited by Gr3ylok; Dec 10, 2018 @ 2:11am

Gr3ylok Dec 10, 2018 @ 2:20am

Tried !play 440 (tf2) > all accounts go idle tf2
Tried !resume > all bots stop idling, but main keeps idling tf2 eventho it says it resumed idling cards

https://gyazo.com/9368dbd33841d799d11e07249a75c3ff
https://gyazo.com/ef3fbbf1b64c11338bd8005379fbaff7

Last edited by Gr3ylok; Dec 10, 2018 @ 2:21am

Gr3ylok Dec 10, 2018 @ 2:28am

Removed Gr3ylok BIN + Data Base File
Restart ASF > have to enter steamguard code again, same problems occured..guess I'm SOL.
https://gyazo.com/61762497eb0394f15ada8709e1cfa11d

Rudokhvist

Dec 10, 2018 @ 2:48am

Even though you said this config worked before I can recommend to remove this bot from asf completely and make new config from scratch.

Gr3ylok Dec 10, 2018 @ 3:24am

Originally posted by Ryzhehvost:
Even though you said this config worked before I can recommend to remove this bot from asf completely and make new config from scratch.

Removed ASF folder and all configs with it.
Downloaded ASF again, made new config.
Now when I start asf "RateLimitExeeded 25 minutes of cooldown"

https://gyazo.com/fd6f65ca7b59af3f856a35d52a7c1455

First time I ever see this error, was this the problem before too? ill check back in 30 mins I guess.

Gr3ylok Dec 10, 2018 @ 3:34am

Open ASF.json
Edit "LoginLimiterDelay": 10, into "LoginLimiterDelay": 20,
Reboot ASF > is idling cards now.

I also compared the new config I made versus the old one, bot.json were exactly the same so the only thing that I changed was LoginLimiterDelay.

Still unsure as to why and what caused it, but thanks for your input

Archi

Dec 10, 2018 @ 4:45am

You didn't even paste your old config for analysis, I'm pretty sure that you didn't set SteamParentalCode properly.

Gr3ylok Dec 10, 2018 @ 4:59am

Originally posted by Archi:
You didn't even paste your old config for analysis, I'm pretty sure that you didn't set SteamParentalCode properly.

As I mentioned before, I've been running ASF on this machine for many many months.
Nothing is wrong with the parentalpin because as I also mentioned, everything works now, ONLY thing I changed was the limiterdelay

"SteamLogin": "Gr3ylok",
"SteamPassword": "********",
"SteamParentalCode": "****",
"Enabled": true,
"s_SteamMasterClanID": "103582791432553344",

#10

Rudokhvist

Dec 10, 2018 @ 5:14am

Anyway, glad you were able to resolve it. I would also suggest that parental pin was somehow connected to it, because after you made new config you got completely different issue. But only thing that matters is that it works for you now.

#11

Gr3ylok Dec 10, 2018 @ 5:16am

Originally posted by Ryzhehvost:
Anyway, glad you were able to resolve it. I would also suggest that parental pin was somehow connected to it, because after you made new config you got completely different issue. But only thing that matters is that it works for you now.

How would that pin screw it up tho, doesn't make sense because ASF was running on that machine for many months, with the SAME config I use now? Ohwell Ima give it a rest, thanks.

#12

A moderator of this forum has indicated that this post answers the original topic.

Archi

Dec 10, 2018 @ 5:25am

Originally posted by Gr3ylok:
Originally posted by Ryzhehvost:
Anyway, glad you were able to resolve it. I would also suggest that parental pin was somehow connected to it, because after you made new config you got completely different issue. But only thing that matters is that it works for you now.
How would that pin screw it up tho, doesn't make sense because ASF was running on that machine for many months, with the SAME config I use now? Ohwell Ima give it a rest, thanks.

Last edited by Archi; Dec 10, 2018 @ 5:27am

#13

Gr3ylok Dec 10, 2018 @ 5:37am

Originally posted by Archi:
Originally posted by Gr3ylok:
How would that pin screw it up tho, doesn't make sense because ASF was running on that machine for many months, with the SAME config I use now? Ohwell Ima give it a rest, thanks.

If you for one second forgot about your only argument of "it worked before" then you'd analyze the ASF changelog and found out that PIN property was renamed, and then realize that you forgot to update your old config for up-to-date ASF release, what regenerating config (and you falsely believing that login limiter delay has anything to do with it) actually did.

And if you compared your old config with new config carefully, then you'd also see how old one used SteamParentalPIN while new one has SteamParentalCode - but you compared global config only, the one that has nothing to do with your issue.

Fair enough compared wrong configs then, did indeed not notice the PIN/CODE change.

#14