Loot mobs setting
Quote Originally Posted by decks View Post
I have about 5 bots leveling at the moment, i noticed that all of them got stuck on the same quests. The problem was "loot mobs" was turned off, due to this my bots got stuck when encountering a quest that involves picking up an item. At first i thought it was corruption of some cache or HB itself, so i did reinstall of HB on the first encounter, and second. By the third time i started following the bot a bit more into detail. The profile seems to turn off loot mobs when the pull distance is set to 1yard. When set back to 100 yard loot mobs is back enabled. It seems loot mobs is at times not being enabled back.
All i wanted to know is that this is the normal behavior of pull distance ad its relation to loot mobs setting or it is a corruption of some sort? I can't pinpoint to what quest it actually starts with.
I have a lot of logs but asking first if you needs some specefic logs or need all of them.
Greet D
Hi, Decks, and thanks for the outstanding problem description and research.
What you describe sounds like an issue with Honorbuddy itself, and should be reported to the Release thread.
There may be a second issue here of PullDistance being set to something specific and fail to be restored. However, we would need to identify the specific quests for which this is happening, as half-a-million lines of profile code is simply too large to conduct random inspections on.
Quote Originally Posted by lastir View Post
I'm having the same issue. Specifically with the quest The Archmage's Staff - Quest - World of Warcraft. The bot would use the quest item to summon the quest mob, kill it, and then start that process over again because it wasn't set to loot mobs to get the item it was looking for.
Attachment 110240
Hi, Lastir,
I've looked through the BC profile (which is what your log says you were using). From what I can tell, Looting was turned back on every time it was temporarily turned off. I've made a request to have the <LootMobs> and <UseMount> directives create log entries every time they are modified. I'm afraid this is going to be the only way we will catch this.
cheers,
chinajade
Hi, i was told to post this matter under release. Sadly i accidently ran my scripts and lost all my logs while reinstalling my HB instances. Off today i still noticed the problem happening on rather fresh installations. I have added all the logs i have after the fresh installations.
Greets D