Bertrand
Active Member
- Joined
- Aug 8, 2012
- Messages
- 1,249
- Reaction score
- 9
I was on early 1.5 beta build till few hours, then decided to dl the latest official just for this bug and i noticed it is still not solved.
I know it is a diablo 3 issue and not db but still, i believe i read somewhere that there will be a check implemented in order to restart the tp cast if char is not in base within 10 sec of casting...
btw, i am not sure but i think rads atom unstucker doesnt catch this one. I had my bot on 1/4 time left of the vallor buff, that means he was not fighting any elite in the past 22 mins. And i dont think he was moving for 20 mins without encoutnering any elite, especially if it is a 24% ms/sprint 100+k dps barb.
update: Holly cow this is more urgent than i thought. Rads atom 1.4.2 *DOES NOT* detect this as a stuck. The bot can get stuck a whole day like this ? This needs immediate attention to those using rads atom 1.4.2 and the latest stable build.
I know it is a diablo 3 issue and not db but still, i believe i read somewhere that there will be a check implemented in order to restart the tp cast if char is not in base within 10 sec of casting...
btw, i am not sure but i think rads atom unstucker doesnt catch this one. I had my bot on 1/4 time left of the vallor buff, that means he was not fighting any elite in the past 22 mins. And i dont think he was moving for 20 mins without encoutnering any elite, especially if it is a 24% ms/sprint 100+k dps barb.
update: Holly cow this is more urgent than i thought. Rads atom 1.4.2 *DOES NOT* detect this as a stuck. The bot can get stuck a whole day like this ? This needs immediate attention to those using rads atom 1.4.2 and the latest stable build.
Last edited:






