Archisteamfarm: Add command to stop the remaining unconnected bots to not connect until error 84 is solved.

[blabla123ble]

Purpose

I have around 50 accounts connected to only one instance of ASF and sometimes I need to restart them and sometimes I will get error 84 or RateLimitExceeded and it will keep on trying to connect the remaining accounts even though it wont connect and I will fall into a loop of forever trying. Account 1 connects but after account 8 it doesnt anymore, after this all the remaining ones will get error 84 and wont take into consideration the first error 84 given which will be account number 9 and afterwards and by the time account 50 tries to connect and gets this error, it will be around the time account 9 that first got blocked be called to connect again and reseting the steam side counter.

Solution

Add a command or increment the one called _stop_ since it already has the basic functionality and since we can write commands via the application it will be much better to solve. Or you could do it automaticly, as soon as a error 84 appears it will stop connecting the others until the 25 minutes expires or taking into consideration the first account that got the rate limit exceeded

Why currently available solutions are not sufficient?

I could increment the logging timer but if I put too much I will take a bigger amount of time and even with it sometimes I will get this Rate Exceeded

Does your suggestion fall into ASF scope?

I really think it is because some down time can occour and put me into this loop

Is your suggestion abiding to Steam guidelines?

Yes

Additional info

If you dont consider it too important I would like to know why. Thank you!

[Abrynos]

Is your suggestion abiding to Steam guidelines?
Yes

actually: no

as FAQ shows internal documents unofficially "allow" up to a maximum of 10 accounts per user. there is no "ban on sight"-rule, but still: because of this i think the anser to

Does your suggestion fall into ASF scope?

should also be "no"

[JustArchi]

Normally I'd close the issue as out of the scope per reasons stated by @Abrynos above, but there is no argument against improving existing login procedure to take into account rate limiting which is in fact global and affects all the bots, not just the one that tried to log in, and this is what I'm going to do in regards to the issue.