Just did a fresh install of that version. No custom classes, only using Singular. Happens on my druid and warrior. My character gets all up in the mobs face (usually right on top of them) and occasionally it will not attack because it gets too close (so its like not facing the right way).
what he said also happens to me. The character runs inside of the mob and the mob backs up and this repeats pretty much until the mob dies. log attached, but i doubt there's much if any indication in there. View attachment log.zip
upload log to the forum http://www.thebuddyforum.com/honorbuddy-forum/guides/9859-how-attach-your-hb-log-file-pictures.html
I don't really care about getting service. The bot still works for me, just was trying to be helpfull with something I noticed.
Its happening to all melee, i guess you fixed old problem with new problem. I had this problem with pirox bot, when i was farming some mobs with default 5 yards melee range, my character was too far away to attack that mob so i reduced melee range to 2 yards then my character start running on top of that mob and mob is running away from me on proper distance (5 yards). If we fight 30 sec then we will move like 20 yards from position where we started fight. Before update we had problem with bot because he was not attacking mobs, now we have problem with characters who are pushing mobs from position where fight started as long as they are fighting. So IMO solving first problem like this is not good because you are creating new problems and soon people will start reporting us when they see how our bots fight mobs. Attaching log to this is just nonsense imo, because i can see what problem is, and only solution for that is making melee distance 5 yards again (if that was default before update), and then fix problem with characters who dont attack mobs with some better solution. Just to recap, im not attaching log because im not asking you to tell me what is problem, i know what is problem and im asking you for solution to that problem as you will not be able to see solution in any of our logs. Thanks for your time.
