12-06-2013, 03:12 AM
It's a relatively rare bug that happens when the bot's current position falls into some kind of distance logic hole in the melee combat code. I've seen it happen myself. Are you able to replicate it manually, because that could help in diagnosing/fixing it.