I posted a bug on bugtracker for this but I wanted to see if anyone else has had this experience. I was running a bot in eastern plaguelands (quest bot) and the bot had all of a sudden stopped looting. The mobs were grey but the bot would just sit and not loot for about 10 seconds, then move on. Checking the logs revealed something like the mob was already looted. Thing is the bot ran fine and was able to loot up to a point. Even if I kill honorbuddy, I cant even manually loot the mobs. I have to physically kill the wow client and restart it. The moment the character logs in he can loot again (without HB being started). So my question is, I wonder if because the bot is using interact on objects and mobs if its possible it fucks up and prevents all looting?
i have the exact same error, kicks 1-60 ally questing profile was used, in the haunted small town in eastern plaguelands. (Corin's Crossing) was the name. works great for sometime, but all of the sudden it seems to be "out or range" and cant loot anything.
Exact same place. Must be corins crossing. I also noticed it paths into buildings as well. It may be a mesh issue?
What's a wow issue? The looting problem? I disagree. I can hunt in Corins Crossing manually all day and night, but the minute I start HB, it can be reproduced in 5 minutes. Killing HB doesnt resolve the issue once it exists either, the client needs to be killed. If you mean pathing into the buildings, how could that be a wow issue? Not understanding you Tony, can you elaborate?
This is an issue with the OpenThatStuff plugin, happened to me on two characters as well using Kick's profile in EPL. After disabling that plugin the issue went away.
