Really this is disappointing.. you fix many errors but even after this has been posted thousands of times, it gets no attention.
4 Bots running, all 4 got authentication failed.
Due to them being opened with a relogger they will auto-try and reconnect (click retry auth until it works) - which is GREAT!
BUT
after it connects i get this message:
[17:09:52.862 N] Was not able to attach to any running Diablo III process, are you running the bot already?
It was attached and due to it getting auth failed (Auth server fuckups or what not) it will detatch? AND not remember which PID to attach to!
Then i say ok.. lets try click START maybe it's nothing - then i get Index out of range.
So i think having 4 bots stop immediately TOGETHER stand still and do nothing while elites gangbang them - that's going to get us banned soo fast they don't even need to check for an hooks or any coordination tracking.
4 Bots running, all 4 got authentication failed.
Due to them being opened with a relogger they will auto-try and reconnect (click retry auth until it works) - which is GREAT!
BUT
after it connects i get this message:
[17:09:52.862 N] Was not able to attach to any running Diablo III process, are you running the bot already?
It was attached and due to it getting auth failed (Auth server fuckups or what not) it will detatch? AND not remember which PID to attach to!
Then i say ok.. lets try click START maybe it's nothing - then i get Index out of range.
So i think having 4 bots stop immediately TOGETHER stand still and do nothing while elites gangbang them - that's going to get us banned soo fast they don't even need to check for an hooks or any coordination tracking.
