Farming is temporarily disabled - only in one ASF installation #3202
-
|
I have several ASF installations. I don't know why, but ASF won't run the game on only one of them. I have 3 accounts there and on each of these three accounts I can collect cards from: Still, for some reason, when I turn on ASF, I see this:
In short, on account [...]-3 ASF first sees that there are cards to collect but cannot activate them, then it checks other accounts but it does not show cards to collect at all:
My ASF.json looks like this:
Whereas .json from account [...]-3:
And .json from account [...]-4:
And from the last account:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
|
I activated a new game on one of these accounts and after turning on ASF, only this one new game is launched. So for some reason ASF won't launch this one game (ID 7520 ). But why? A few hours ago, from another ASF installation, I was able to retrieve cards with ID 7520 on another Steam account. |
Beta Was this translation helpful? Give feedback.
-
|
Did you farm blacklisted that app? What's the output of: |
Beta Was this translation helpful? Give feedback.
-
|
I don't remember ever using this command. Whenever I wanted to block a game, I simply entered its ID into the "Blacklist" in ASF.json. But anyway, I started the ASF game with the "play" command and the cards came in. I don't know why this installation refused to allow me to automatically farm. |
Beta Was this translation helpful? Give feedback.
-
|
Out of curiosity, I entered the command in ASF
and it turned out that all 3 accounts from this installation have an empty list. |
Beta Was this translation helpful? Give feedback.
-
|
ASF can be temporarily unavailable to check packages data for any reason, mainly Steam failures. When you issue play command, you skip all the requirement ASF needs to do in order to find out that the game can even be played, and goes straight to sending a network request "I'm playing this game", which is not always everything that is required in order to idle particular game. This issue is temporary and usually resolves itself within a week maximum, there is also nothing to fix/improve in this regard, you can manually delete ASF.db if you want to potentially speed up the process (although Steam can give ASF invalid data again and that won't do anything then). |
Beta Was this translation helpful? Give feedback.
-
|
Only this ASF installation with 3 accounts could not run this one game. However, a moment later I launched two other ASF installations with two different accounts and they started the game automatically without any problem. It's normal? It seems to me that if it were Steam's fault (e.g. too many people would enable the game with ID 7520), it is unlikely that two other installations would not automatically enable this game on two other accounts. I removed [...]-3.db, [...]-4.db and [...]-5.db as well as [...]-3.bin, [...]-4. bin and [...]-5.bin but it didn't help. I didn't think about ASF.db. Anyway, I don't know if we will now find out why only one ASF installation did not want to run these games from the machine because, as I wrote,
and I got all the cards. |
Beta Was this translation helpful? Give feedback.
-
|
I already told you above, your information got cached, if Steam responded with something invalid, then invalid info was cached, nothing ASF can do about it, other than occassionally purging the cache and refetching up-to-date info, which is what ASF does already. |
Beta Was this translation helpful? Give feedback.
ASF can be temporarily unavailable to check packages data for any reason, mainly Steam failures. When you issue play command, you skip all the requirement ASF needs to do in order to find out that the game can even be played, and goes straight to sending a network request "I'm playing this game", which is not always everything that is required in order to idle particular game.
This issue is temporary and usually resolves itself within a week maximum, there is also nothing to fix/improve in this regard, you can manually delete ASF.db if you want to potentially speed up the process (although Steam can give ASF invalid data again and that won't do anything then).