Caliban2017
commented
1 year ago I'm not sure if it is helping to extend the time between the Logins to avoid the IP Block. I think it is more working like 20 Accounts in 4-5 Hours, then you can begin again... so this is what i have noticed.
In the last Weeks i did ~20 Accounts in the Morning (arround 8-9 AM) and waited until 1-2 PM and did one more 20 Accounts and waited till 9-10 PM and 20 Accounts again. This worked without any Problems in the last Weeks/Months. But i believe there is a maximum of Accounts in a given Timewindow of 4-5h. I don't know if you can expand it to more Accounts in this Timewindow by wait more between the Logins... but of course i can try it.. So i could increase the Band times to test it?
KevinIbay
SamMackrill
Thread for discussion. If you login too many times on a single IP address then ArenaNet will slow-down access and eventually block the IP There is logic and settings to slow things down and help prevent this however it is not well documented on how this works and the approach needs testing.
My intention is to improve the approach so it is easier to understand and has reasonable defaults Some of the assumptions and behaviour I have gathered from various sources:
GW2-Alternator tries to counter this by slowing down the login attempts after a failure (throttling) However the delay required depends on the past login history and is difficult to guess There are tuning parameters in Settings to help adjust this:
this means: 1-12 accounts have a 0s delay 13-24 accounts have a 30s delay 25-40 accounts have a 45s delay
above that it is set to band3 + 60s
If a login fails then the delay is set to
40 + 20 * ConsecutiveFailCount