It seems it's trying to pick up a quest which takes place inside of "Helheim" - which since it's on a different MapId, it's causing the bot to go to a weird location. Your character was moved out of the Helheim zone somehow, which if you move your character back in - it should work properly. I'll look into adding failsafe codes that'll detect if the player moved the bot out of the Helheim zone at any point.
Yea, I've noticed this before as well. Once the hook for selling is inserted - it won't stop even if you stop the bot and manually sell. The only way around this is to actually close the bot out completely. In terms of the selling issue - the only thing I could attempt to do is add a ForceSell code before it goes to the other side of Guarm. That way while it's questing on the other side, there's no reason it will want to go back to the vendor. Thanks for the report!
Move your character into the Helheim zone. It seems you may have manually moved the character out of it.
third time through and each time I find the bot stuck on the espider quest in eastern plaguelands running into a tree stump until manually moved off its path
Hi Echotiger, I leveled some chars and as I switched to HB3 I experienced some errors concerning pathing. I actually haven't understood when a pathing error has to be posted here in this thread and when in mesh errors thread. Would you mind explaining what exactly changed from HB2 to HB3 in regards of path generation? I posted one "path generation error" in mesh errors thread (my char couldn't reach a certain mob being important for a quest), I was told it has to be posted here and it was fixed. I got a new situation and I so I am not sure where to post it as I assume it's mesh and not quest related: My char died while doing one quest and HB can't find a way to corpse. Is this the right thread for posting such issues?
The "fly all dreanor treasures" is broken, it can not decide if it´s horde or alliance so it get stuck on either Yuuri or the horde quest, cant really find the name now. But anyway the toon sits there untill it logs off
for priest. it says I don't know Arcane Torrent. It's my racial passive and it;s on the bar. bot just shuts down
At the time you posted this - Honorbuddy didn't support blackspots. So it's hard to tell if this stump is already blackspotted or not. Blackspots should be working on this latest Honorbuddy update. So there's a chance the issue is already fixed. But just in case, can you get me a blackspot of this stump? I'll use it to check to see if there's one in currently - if not, I can add it.
If the bot died and can't move to its corpse - then there's a good chance its a Mesh issue. Outside of that - if the bot is just running along just fine, and it says "PathGeneration Failed" randomly out of the blue... then there's a good chance it's the profile. In HB2, coordinates had a default 25yard tolerance radius. That means that if the coordinate is in a location where the bot can't navigate to, the bot will search for a navigatable path within 25yards of the coordinate. However, in HB3 this tolerance was set to default at 5yards. So in areas where XYZ coordinates were used in 'bad spots' - the 6-25 yard tolerance that was once available for looking for an 'acceptable path' no longer exists which this results in a path generation failure. This tolerance change from 25 to 5 is the cause of most of issues related to PathGeneration failures.
Do you perhaps have a log of this? Nothing changed in the bot that would've broken the detection for Horde or Alliance.
this should be it as its a fresh install and only champion i've used it on. I ended up skipping that quest.. doing the next one in the area and switched to the non-auto load 5-12 KINGz or 1-12. The Autoloader v2 version put me who knows where in undercity and crashed for coordinates. running fine at lvl 8 now also i wanted to thank you for all yalls hard work. wanted a healer but didn't feel like dropping another 60 on a character.. NOR questing one up.. fuck all that lol
It seems the "Arcane Torrent" that it was trying to cast was the old version of the Priest's Arcane Torrent. They added a new version which also generates Insanity whereas the old version only generated Mana. I'll update the profile accordingly. Thanks for the report + log! And no problem. ^^
Hi Echotiger, thank you for your explanation. I will post the issue I described to mesh error thread. I got another more general issue that occured a few times: If my char gets an auto-accept quest and tries to pick up another quest, HB seems to have trouble with this situation as two quest/gossip frames are present. Is it possible to close all quest/gossip frames and trying to pickup quest again, before HB stops due to not being able to pickup quest? I guess PickUp behavior has to be changed then. Edit: Seems like this issue occurs not only when an auto accept quest appears.
i did notice this too actually. i have zygor on now and works fine also.. for the 12-58 kick profile. will it buy the riding at 20?
gona get you one as fast as i can. The thing is that the quest iam talking about is Nightmare in the Tomb - Quest - World of Warcraft and the one for horde is Norana's Cache - Object - World of Warcraft as you can see they are specific for each each faction. think there need to be some kind of false/true coding on those tresures. i dont know a damn thing about coding iam just a user, But i have problems on my alliance charakter to. it goes for the horde tresure and just sits there and dosent move for a second until loged out for inactivity.