Stop spamming the Steam-Servers (change Interval)

[Pandiora]

Theres one more reason why bots can´t connect > the interval for connecting your different bots is to low. Steam completely blocks access to their servers for some time if you spam 3 logons in just 1 second. I tried to login with Steam-Client after running ASF and get an error, that my login-attempt failed. (login-credentials definitely correct)

[JustArchi]

I released the most simple solution, we just delay creating bots to 1 bot per second.

e8335ac

Try it. I don't have enough accounts.

[Pandiora]

The delay is to short. I changed the delay to 5s first and was able to connect 80 bots, then I got the "Invalid Password"-Error again. Now I modified the delay to something random between 5 and 10 seconds and nearly all bots connected and started farming! I will update program.cs with a delay of 5 - 15 seconds. I think then it would be possible to connect over 200 bots. I know it will take long until all bots connected and this isn´t as fast as in the beginning, but its the best solution so far.

Edit: The delays has to be added for reconnects also. Just add this here so I won´t forget.

[JustArchi]

I took your idea and improved it greatly, so bots now limit steam logins also on reconnects + they're sleeping asynchronously (we should avoid Thread.Sleep() at all cost because it's blocking main thread too)

Pull my latest changes and test if all of your bots still work properly.

[JustArchi]

Still need feedback ^

[Pandiora]

I would say it works now with the 5s delay but I´m getting some errors with debian(mono) after ~110 bots connected:

• EXCEPTION: UrlToHttpResponse() The Task was canceled
• WEB API Call timed out

There are 5 users trying to reconnect at the same time. With Windows it looks like its working, there were 188 bots connected at the same time. But ~20 bots were missing and didn´t connected for some reason. The log is gone so I can´t figure out what happened. Also there are no messages that those bots tried to reconnect, so dunno.

Maybe its better to read the delay from config? I think it would help if someone has more bots then me. Its like there is a limit per minute or hour like you said and this way everyone could use its own delay depending on how much bots he owns. A user like you with 5 bots don´t need a 5s delay.

Update: Tested it the second time now with debian and I have still the same problem. htop shows me spikes in cpu-usage - maybe my server can´t handle it. I´m having 2 cpu´s and 4 GB RAM, thought that would be enough. Curious this problem occurs again for 110 connected users. Last time when I tested with Thread.Sleep this was also a wall I hit and after I used random delays it worked. So maybe its the same problem again.

[JustArchi]

For now I think that we leave 5 sec on, and make it switchable in future.

[JustArchi]

Anyway, fixed for now.