the 8.4 version is not uploaded in mpgh... search for james' blog for it
mine say fail adobe flash player... even tho i have the up to date one
Latest Le Bot 8.4 still acting like the same as previous version, relog, stand in battleon and do nothing even the bot is activate.
Well looks like Le bot is broken and doesn't metter if its 8.3 or 8.4 both doing same crap just stand in battleon. So any other good not broken clients?
Originally Posted by pingve
Well looks like Le bot is broken and doesn't metter if its 8.3 or 8.4 both doing same crap just stand in battleon. So any other good not broken clients?
Le Bot works, I just tried it.
You're probably just doing something wrong... but I don't see where you could go wrong.
Have you tried pressing start on one of the bots? Or do you mean the auto-relog doesn't work as the previous poster said?
See thing is i use Le bot long time and doing everything good i have maked my own bots etc. Its all same. So i think Le bot 8.5 would be good. (with fixes).
Originally Posted by pingve
See thing is i use Le bot long time and doing everything good i have maked my own bots etc. Its all same. So i think Le bot 8.5 would be good. (with fixes).
There wouldn't be a Le Bot 8.5.
James is remaking the whole trainer and I know think he would name something else.
Good to know there's Brazilian people helping AQW hacking community. BR hue.
the link does not work
i'm new to this but whenever i try to start it up it says failed to load flash player
I cant specifically attack a certain monster but rather even if I specify the name of the monster that I should be attacking, it is acting as if the commands are "random attack". Is there a solution to this?
Originally Posted by pipeds
I cant specifically attack a certain monster but rather even if I specify the name of the monster that I should be attacking, it is acting as if the commands are "random attack". Is there a solution to this?
It's broken, nothing you can do for now.
Originally Posted by Oliboli8769
It's broken, nothing you can do for now.
Thanks for clarifying, I thought it was only me, that experienced that issue.