I'm sure lots of botters here utilize reloggers with some form of anti-idling shutdown/relog. Sadly enough many of those reloggers do not have a interval function before relogging. To give an example what would have happened had I not spotted it right off today.
1) Starts relogger
2) Relogger starts D3 + DB
3) Creates game and ends up idling in game due to Nav servers being down
4) Anti idling plugins shutdown D3 + DB
5) Loops back to step 2
What I would have potentially ended up with would be a ton of relogs/games per hour and ended up hitting the "input limit"
I'm thinking since DB cannot function without nav servers being up, wouldn't it be better just to deny logins to DB should anything amiss occurs to the nav servers or situations like this in the future? All we would end up with would be a ton of relog attempts into DB, which ain't bad at all considering the alternative
1) Starts relogger
2) Relogger starts D3 + DB
3) Creates game and ends up idling in game due to Nav servers being down
4) Anti idling plugins shutdown D3 + DB
5) Loops back to step 2
What I would have potentially ended up with would be a ton of relogs/games per hour and ended up hitting the "input limit"
I'm thinking since DB cannot function without nav servers being up, wouldn't it be better just to deny logins to DB should anything amiss occurs to the nav servers or situations like this in the future? All we would end up with would be a ton of relog attempts into DB, which ain't bad at all considering the alternative
