ASF login about 20 attempts and done

[alexdevilrock]

I update ASF V2.1.7.9 for V2.1.8.1
And now ASF in login just rejoin 15 - 20 times and login done.
Сhange version for V2.1.7.9 and the problem persists.
I had not received this error earlier, so not sure that this lock steam, besides, I've been waiting more than a day. Now it happens every time I restarted ASF.
It screenshot V2.1.7.9

I understand that perhaps it lock steam, in this case, I do not demand explanations.
But maybe it bug. Just wanted to know.
If it lock steam, I think it would be useful to add an error.

[zennox1337]

I have the same problem

[GuestLab]

[ccubed]

i too have this issue with the latest version.

2016-12-24 12:01:19|mono-sgen-29017|INFO|bot|OnDisconnected() Disconnected from Steam!
2016-12-24 12:01:19|mono-sgen-29017|INFO|bot|OnDisconnected() Reconnecting...
2016-12-24 12:01:19|mono-sgen-29017|INFO|bot|Connect() Connecting...
2016-12-24 12:01:24|mono-sgen-29017|INFO|bot|OnDisconnected() Disconnected from Steam!
2016-12-24 12:01:24|mono-sgen-29017|INFO|bot|OnDisconnected() Reconnecting...
2016-12-24 12:01:25|mono-sgen-29017|INFO|bot|Connect() Connecting...
2016-12-24 12:01:30|mono-sgen-29017|INFO|bot|OnDisconnected() Disconnected from Steam!
2016-12-24 12:01:30|mono-sgen-29017|INFO|bot|OnDisconnected() Reconnecting...
2016-12-24 12:01:32|mono-sgen-29017|INFO|bot|Connect() Connecting...
2016-12-24 12:01:37|mono-sgen-29017|INFO|bot|OnDisconnected() Disconnected from Steam!
2016-12-24 12:01:37|mono-sgen-29017|INFO|bot|OnDisconnected() Reconnecting...
2016-12-24 12:01:39|mono-sgen-29017|INFO|bot|Connect() Connecting...
2016-12-24 12:01:44|mono-sgen-29017|INFO|bot|OnDisconnected() Disconnected from Steam!
2016-12-24 12:01:44|mono-sgen-29017|INFO|bot|OnDisconnected() Reconnecting...

[alexdevilrock]

Archi write what not support experimental version, but now it error have and in stable verson.

[ccubed]

In my case this was resolved with the newest experimental build.

[JustArchi]

It has nothing to do with ASF, but with Steam returning wrong servers for ASF to connect. Removing ASF.db manually usually solves this.

[JustArchi]

Should be "fixed" since V2.1.8.2, even if the culprit has nothing to do with ASF but Steam Network.

[NotTsunami]

Maybe you can add a color tag or some way to identify through ASF what error/warning is the fault of the Steam Network (which is almost always the case) and what is an ASF error, that way hopefully it would lessen false reports.

[vladislaw952]

Btw, i think all this guys, who has problem like "Disconnect from steam" using amazon server. Why i talking about it? Because i doing some test, i have one amazon server with 200 bots(100+100), restaring one of two asf and i have same problem too, but second asf working fine. this force me to starting new amazon, upload asf and i can`t starting asf => Disconnect from steam. So i have my home pc, and i dont have this problem. Idk what to do right now.
Thx.

[Pandiora]

It isn't about the Amazon-Servers and I'm also running two instances. The reason why the second instance might fail to start is due to failed logins and you have to wait 25-30 minutes between restarts. Had this problem for a long time and it is about the Steam-Servers, not ASF nor Amazon-Servers.

The reason why it might run on your home-network is, that this IP probably hasn't gotten any login-errors and you "start from scratch" until Steam bans you temporarily for 25-30 minutes.

[JustArchi]

@Tsunamical I don't want to make assumptions what might be steam network issue, and what could be ASF issue. It's very sensitive subject, as what today is steam network quirk might in future be ASF incompatibility with some Steam change that will be falsely assumed to be steam issue, when it's ASF that should be corrected and not Steam. I'm used to people not reading FAQ or giving any useful feedback, that's why those errors/warnings are crucial for me to see what is happening, as I am able to tell what should be corrected and what is intended - if ASF had extra logic of guessing itself which case it is, there is too high chance it could guess wrong in the future, and that could lead to ignoring issue that should potentially be solved by me. So it's easier for me to yell at people to go read FAQ rather than expecting them to report things when ASF tells them to 😆 . The way it's now I can at least clearly see what is wrong.