[H - Quest] 10-60 Kalimdor (LowHangingFruit AFK)

You're not even running my profile. You're running and old version of Tuba's: "[10:03:16 AM:868] Changing current profile to Horde 1-65 Questing: By TubaJedi v.4.1.3"

 

I just changed it over to yours and its doing the exact same thing. Says the same error with the same quest ID and shuts down HB.

 

If you were running Tuba's profile then you were (should have been) using custom CBs - this profile is designed to work with the CBs that came with HB. Did you try reinstalling HB?

 

I will try a fresh install real quick and see if that works.

 

Thanks for the input. I'll add all of this in the next revision. edit: fixed in 1.5.10

Edit: The ForceSetVendor script supports the QuestId parameter, so I was using that instead - are you sure another conditional on top of that is necessary?

 

Fresh install of HB and the same error comes up. Here is the log from the fresh one.

 

You're using a very outdated version of the profile (1.5.3). Please download the latest from the first post, v1.5.9. The error you're seeing was fixed in 1.5.7, I think. Anyways, grab the latest and you should be good to go.

- Ben

 

Yeah it was the old version that i was using that was causing the problem. It fixed now and running like a charm. Thanks for the quick help.

 

You're absolutely right, if the ForceSetVendor has a completed QuestId, it will be skipped. Its the ForceSetVendor with QuestId="0" that were giving me grief.

I'm using the profile to level a mage and there are a *lot* of deaths with mages--its to be expected with any profile. Sometimes the mage gets into a 'death loop', and you have to stop Honorbuddy, help it through a quest, then restart Honorbuddy to get out of the loop. That's when certain of the ForceSetVendors were causing a tour of central Kalimdor with unneeded visits to the trainers, repair, and mail.


Thanks again for looking into this!

cheers,
chinajade

 

I took a look through and I think I have everything cleared up in 1.5.10 (which I'll post later today). The only places where there's a QuestId="0" ForceSetVendor without a conditional wrapper should be the hearth+sell+train sessions at various levels. What I did for these was put them after the grind to the given level but before the checkpoint for that same level. If you happen to stop/start HB after the grind but before the char makes it to the vendor, that sell/train session should be skipped because of the checkpoint. This should be stop/start friendly, but please let me know if that's not the case. edit: fixed in 1.5.10

- Ben

 

Just FYI...
You can arrange for this with the UserSettings CB (ships with Honorbuddy). Its one less thing for both you and your users to worry about.

cheers,
chinajade

 

Damn, that is fantastic. Thanks for letting me know about that, I'll get it into the next revision. edit: fixed in 1.5.10

- Ben

 

This profile is SO MUCH better then the other 1-60 horde q profile. Never get's stuck or hangs.
Level 26 and still going strong!! (Priest)

 

hey benkoren the profile is pretty flawless but when ever it goes to fly somewhere it always gets hung up on the flight master and never flys and the debug window just spams

[6:26:22 PM:711] Changed POI to: Type: Fly, R: Update
[6:26:22 PM:908] Cleared POI - Reason Done with FP
[6:26:22 PM:908] Cleared POI
[6:26:23 PM:108] Changed POI to: Type: Fly, R: Update
[6:26:23 PM:317] Cleared POI - Reason Done with FP
[6:26:23 PM:317] Cleared POI
[6:26:23 PM:510] Changed POI to: Type: Fly, R: Update
[6:26:23 PM:713] Cleared POI - Reason Done with FP
[6:26:23 PM:713] Cleared POI
[6:26:23 PM:887] Changed POI to: Type: Fly, R: Update
[6:26:24 PM:84] Cleared POI - Reason Done with FP
[6:26:24 PM:84] Cleared POI
[6:26:24 PM:298] Changed POI to: Type: Fly, R: Update
using latest HB version

 

That's an HB issue, not a profile issue. Please post on the bugtracker: Bugzilla Main Page

 

would using an older version fix it?

 

Hi, MrTrailMix,

No.

The cause of the problem is usually one of the following:
1) You've switched toons while Honorbuddy was open
2) You've reloaded the WoWclient GUI while Honorbuddy was open

When these things happen, Honorbuddy becomes partially 'unhooked' from the WoWclient. At this time, there is no way for HB to detect this and rehook itself into the WoWclient properly.

The workaround is to simply shut down HB, and relaunch it after one of the above actions has been conducted. After doing this, your problems with flightmasters should be fixed. If not, please submit a BugTracker with your logs, as you've discovered a bug.

cheers,
chinajade

 

Uhh yea, the bot was running it went to this NPC and then HB said Could not pickup quest from item with id:12842 the item was not found!
Honorbuddy Stopped!
Could not create current in quest bot; exception was thrown
Thread was being aborted.
what does that mean? Help appreciated, thanks.

 

Howdy, Ben. I've had a problem where the bot will often approach a vendor to empty bags and repair, and it will do so, however it will persist on doing it over and over again resulting in nothing done. Usually reloading the bot corrects the behavior but it eventually happens again. Also, in Stonetalon Moutain there is a Cliff Stormer mob that is attacking me with it's lightning ability from an unknown location. TomTom says it's almost 9000ft away. This is a problem because it's hurting me while I'm grinding to from 28 to 30.

P.S. Thanks for the awesomesauce profile! <3

 

First of all, I idol you! secondly I have a question. Why can we not have learn skills enabled?