kareshi92

anyway I found out why it didn't work. Sorry. I copy and pasted the configuration fire into the new one which shouldn't be done. cheers

Same bro sometimes it will stop out of nowhere and let the mob kill... been dead few time since using this new bot. almost level up from the last one thou. almost lol now back to 0 exp soon

Thanks for the info stef, hope it'll get fix on the next release thou seems easy to fix to me they just have to test the coordinate before release

The bot click on my number 5 character. I'm sorry I can't provide any photo since moderator might be monitoring this forum.

I still can't select my 6th character correctly, to make it worst you even remove the number 7th making it completely impossible to select my number 6th character now. So I'll be using v0.52f for now. Until it get fixed. Another old issue not fixed is that the stuck at Aqueduct. you can try let it run and eventually it'll get stuck at a particular place hitting air without moving. however it dosen't get stuck at every instance but it really slow down clear speed and rerun count. also bot won't go back to take item even if unique item drop if running normal instance like dried lake. It will however go back to take the item if running map.

I'm just trying to help you improve the bot seriously. Please be constructive when commenting it will do you more good than harm.

Same here just that my skill is different. Also it won't open the corrupted area in Aqueducts; more specifically it won't open the sewer door before entering. It should be programmed to open sewer door too. Also when NavMash Path finding is on, it click on my frenzy charge cooldown and stuck there until my frenzy charge end; it should programmed to avoid the "timer" zone too. Timer zone mean the place where the countdown of skill take place. Hope this is brief enough. Also: There is a choice to choose act 4 The Dried Lake but it will never walk there. P.S. the stuck doesn't happen every time thou, if it is left to bot for a night it will go to town after getting stuck over the "run timeout" setting. However its an obvious drag of time and inefficient farming we got there.