HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

Quest Signed in Blood (Mount Hyjal Horde)

Bot talks to one of the twilight's, lures him away from the group, but then i get an error.


[InteractWith-v719(error)] PROFILE ERROR: You must specify one or more: MobIdIncludesSelf, MobIdN, FactionIdN

[Ref: "[Fly][N - Quest] Hyjal 80-82 [Kick]($Rev: 2166 $)" @line 2360]
[InteractWith-v719(warning) @line 2360]: Attribute 'ItemId' is not recognized by this behavior--ignoring it.
[InteractWith-v719(error) @line 2360]: Stopping Honorbuddy. Please repair the profile!
Bot Stopped! Reason: Profile has too many errors

 

DarkRave, about how long did it take?

 

On the quest Into The Maw of Madness - Quest - World of Warcraft as Horde it looks like the quest doesn't get picked up but the profile expects it to have been.

I got this error:

However, after picking up the quest manually it completed it as expected.

View attachment 6748 2013-11-07 02.42.zip

Thanks!

 

Another issue I've found is on the quest Shizz Work - Quest - World of Warcraft. I'm playing a Horde mage, and when the quest is picked up my character doesn't use the whistle to summon the Felhound needed for the quest.

I think the issue is that I already have one pet summoned (my water elemental), so this section of the code goes through without summoning the Felhound:

[Fly][H - Quest] BC 58-70 [Kick]
Lines 2550-2553

Code:

<If Condition="HasItem(30803) &amp;&amp; (Me.Minions.Count &lt; 1)">
    <RunTo DestName="Foreman Razelcraz" X="431.1503" Y="2889.698" Z="52.17432" />
    <CustomBehavior File="Misc\RunLua" WaitTime="1000" NumOfTimes="1" Lua="UseItemByName(30803)" />
</If>

View attachment 3044 2013-11-07 18.41.txt

Thanks again, and let me know if you need any more info!

 

Deepholm 82-83 maybe some coordinates not correct? because i am flying to X="846.4485" Y="676.6024" Z="-69.31956" but could not reach them or there is nothing there... so quest do not start. Or it just for me?

 

View attachment 9028 2013-11-08 22.45.txt

Have a problem with this profile that wont go away. Basically it just grinds instead of doing questing. When it started grinding at lvl 75 I thought it would start questing again at 76 but after the ding it was still farming. Been doing this for 2 days, I have cleared the cache probably 10 times during this time and let it rest over the night but I still got the same problem.

I have also tried a fresh install but doesn't work.

 

So why does it not fly between quests in some zones? For example Uldum Horde doesnt work.

 

Hey unsure why but on all my characters it always wants to level in the 15-25 area my rogue is currently level 28 is is trying to level in westfall.

 

I keep getting this error message while questing in Outlands. Bot will auto-stop and will not progress any further. How do I get past this?

[InteractWith-v719(fatal)] [PROFILE ERROR] Challenge From the Horde has not arrived in our bag within 5s.

 

....

 

I found myself stuck in Un' Guro Crater with 2 others stuck in the same place using Kick's profle i presume i tried to reset it but it just keept running there after dying

Here is a screencap.

 

hello kick The questbot or the profile i don't know which keep turning off the loot option and the bot doesn't loot at all i had to put plugins Combatlooter to get the bot to loot i can
give a log if want

 

I keep getting this error message when questing in Outlands


[InteractWith-v719(fatal)] [PROFILE ERROR] Challenge From the Horde has not arrived in our bag within 5s.

I'm a lvl 61 destro lock questing in Hellfire Peninsula. The toon seemed to be questing just fine until this error message. Once the error message pops up, the bot automatically stops (the start/stop button actually toggles) and if I press start the bot will initialize again, and give the same error message once it says "loading Hellfire Ramparts quests" or something of that sort.

Log is now attached. thanks.

 

Problems with quest "Children Of Tortolla" in Hyjal. I checked log and also found issues with mailing. Seems it both profile issue and hb-issue, would appriciate if you could notify other devs if issues if nessecary and save me the trouble . I ain't keeping my logs for long. :O

 

still no update on these?

 

Stuck at: Goal: Picking Up Quest - Proving Your Strength : QuestID - 10479 : To - Warden Bullrok : ID - 18407

 

loot mobs setting

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

 

Death knight prifile don't works with a new HB:

Honorbuddy
-> Settings & Tools
-> use "Pull Distance" slider
Disposition: Honorbuddy stopped due to Profile Writer request
Bot Stopped! Reason: None Given

 

Yesterday i started a new toon, a druid. I setted like always, Talents,Weapon style... and working good, but i noticed that always, when i start the bot it disables framelock, imo, i think that is a profile related problem, because it not happends if I load another profiles.

Could you give me a solution to use put framelock always ON in kicks's profiles? Is like that is not saving config or the profile changes the configuration whenever it's needed, because i read the log sometimes and says..."pull distance 0","No loot while scorting"...messages like this ones...

 

Confirmed.

Uldum is a complete disaster.