11-01-2013, 12:15 PM
Hi f3re,
It seem that I'm not the only one having this issue ( http://mmominion.com/Thread-Bot-not-rest...light=evac) #
Just looking at the thread above there are at least several people having this issue.
I've also tested this against against various other public meshes.....and the effect is exactly the same - 90% of the time it ignores not only MP rest % but HP as well...
I've tried thanalan, shroud, and many others - I've even tried the "specific monster routine" module which was produced by one user on the forums to actually limit what the bot is attacking - still no avail.
Therefore, after testing it so extensively I'm positive that it wasn't anything to do with my mesh at all. Especially that many other people seem to have seen this as well in pure "grind" mode.....
I've deleted my post on ownedcore as requested.
However I'd greatly appreciate help there, I think the bot is great (the best one in fact and I've tried all of them), and I'll be more than happy to pay for it provided this issue is fixed.
Kind regards
Paul
It seem that I'm not the only one having this issue ( http://mmominion.com/Thread-Bot-not-rest...light=evac) #
Just looking at the thread above there are at least several people having this issue.
I've also tested this against against various other public meshes.....and the effect is exactly the same - 90% of the time it ignores not only MP rest % but HP as well...
I've tried thanalan, shroud, and many others - I've even tried the "specific monster routine" module which was produced by one user on the forums to actually limit what the bot is attacking - still no avail.
Therefore, after testing it so extensively I'm positive that it wasn't anything to do with my mesh at all. Especially that many other people seem to have seen this as well in pure "grind" mode.....
I've deleted my post on ownedcore as requested.
However I'd greatly appreciate help there, I think the bot is great (the best one in fact and I've tried all of them), and I'll be more than happy to pay for it provided this issue is fixed.
Kind regards
Paul