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

12-58 horde

[MountHook-vUnknown(info)] Inserting hook
[Profile Message]: Compiling N. Barrens Quests
[Profile Message]: Compiling Ratchet Quests
Could not find quest giver NPC with ID 3339 in database.
Bot stopping! Reason: Could not create current in quest bot!

clean honorbuddy, updated svn. what else can I do.

edit: I just started up the 1-12 auto loader and it's downloading the meshes. I'll update when it's finished.

 

Hey there!!!

I've just a realy annoying bug in deepholm. Everytime my bot wants to sell stuff he'll fly to the highest place in northern deepholm and stuck at the "celling" of deepholm.

I attached a log. it is the third char where this error occurs.

so long smv

View attachment 5976 2014-04-12 19.56.txt

 

im in Nagrand and my character is trying to take a quest off Hemet nesingwary but it doesn't accept it

 

Been using this profile pack for a couple of days on a few different toons:

Alliance Hunter: no real issues up to level 62, had to step in and help on a few quests but I think it would have figured it out on its own. I just didn't want to look odd with others around.

Alliance Rogue: no issues so far, but not very far in yet.

Overall, i'm really digging the pack and thanks a million for posting it. I only use the bot when i'm able to watch it, but in the future I may try some true AFK botting. It's just awesome that I can be doing some other projects on the computer while mr. bot quests away the levels for me.

I will update my reply here with any issues and logs, but it seems like most of those have been worked out at this point.

 

Go into your hb folder and delete CACHE.

Go into your wow folder and delete CACHE.
Go into your wow folder and data folder and delete CACHE.
Go into your C:, ProgramData (Show hidden files), delete Blizzard Entertainment.

I had same issue, support told me to do this, and it solved it. Its a common error.

 

Hi

Having problems with the Valley of the Four Winds-profile. When I start it says:

"[Profile Message]: Compiling Valley of the Four Winds Quests"

In HBs info it says: "Goal: Picking Up Quest - The Search for the Hidden Master : QuestID - 30086 : To - Xiao : ID - 56110"


The character stands ontop of Xiao without doing anything. Doesn't even target him.

I tried with several chars, I deleted the cache and I updated the profiles. Suggestions? Other profiles works well.

 

Hello

I have a Problem with the "[Fly][N - Quest] Deepholm 82-84 [Kick]"
http://puu.sh/89KdR/bb537a6631.png
http://puu.sh/89Kgp/6e717deeb5.png
Can some help me please? :>

Thanks!

Edit: Oh my fail, works now. Its okey, thanks

 

Hello guys

im using kicks questing wich is really awesome and everything but i got a little problem


for example if im lvling in an area thats lvl 62-64 it will stay there till atleast 65 i got heirlooms on so i lvl up to max lvl of area before i hit that lvl

is there any possible way to get the bot to change questing area if im at max lvl? so for example if im lvl 64 i shouldnt be in the lvl highest lvl of the zone 64

but in a zone that has instead 63-65 or something like that if you understand . Plz help!


PS why the ef is my bot using ground mount when i can fly in a area?????

 

Hello!

I'm using "[QO] Sha'tari Skyguard Rep A [Kick]" to... well... farm Sha'tari Skyguard reputation, but my toon keeps getting stuck, trying go up up an un-climbable hill.

I have little to no experience with profile writing but I've been trying to fix the issue by adding the following blackspot to the profile:

Code:

	<Blackspots>
		<Blackspot X="-3996.589" Y="3117.768" Z="323.7128" Radius="260" />
	</Blackspots>

These coords are the exact coords of the place my toon always gets stuck on. I've been playing up and down with the radius, so far I've ranged from 0 to 260 but the toon always gets stuck on the exact same spot.

Here are the last few lines of the log right before the toon gets stuck:

Code:

[19:52:27.785 D] Stop and dismount... Reason: Combat
[19:52:28.487 N] (Singular) <<< ADD >>> CurrentTarget now: Skettis Soulcaller.7A13 h=100.0%, maxh=6986, d=11.0 yds, box=1.3, player=N, hostil=Y, faction=90, loss=Y, face=N, agro=Y, IsBotPoi=Kill, TargetIndex=1
[19:52:28.487 N] (Singular) FaceTarget: facing since more than 70 degrees
[19:52:29.073 N] (Singular) MoveToMelee(PathGenerated): towards Skettis Soulcaller.7A13 @ 11.0 yds
[19:52:29.079 N] (Singular) .... h=100.0%, m=100.0%, moving=N, mobs=1, Skettis Soulcaller.7A13, 100.0%, 11.0 yds, face=N, loss=Y
[19:52:29.079 N] (Singular) Possible Interrupt Target: Skettis Soulcaller.7A13 @ 11.0 yds casting Shadow Bolt #20298 for 1648 ms
[19:52:29.081 N] [Singular] *Hammer of Justice on Skettis Soulcaller.7A13 @ 100.0% at 11.0 yds 
[19:52:29.112 N] (Singular) FaceTarget: facing since more than 70 degrees
[19:52:29.112 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 11.0 yds
[19:52:29.148 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 10.7 yds
[19:52:29.185 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 10.4 yds
[19:52:29.247 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 9.9 yds
[19:52:29.282 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 9.6 yds
[19:52:29.310 N] (Singular) [WoWRedError] You are too far away!
[19:52:29.321 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 9.3 yds
[19:52:29.349 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 9.0 yds
[19:52:29.384 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 8.8 yds
[19:52:29.458 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 8.2 yds
[19:52:29.491 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 7.9 yds
[19:52:29.531 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 7.6 yds
[19:52:29.561 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 7.3 yds
[19:52:29.624 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 6.8 yds
[19:52:29.657 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 6.5 yds
[19:52:29.705 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 6.1 yds
[19:52:29.736 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 5.9 yds
[19:52:29.766 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 5.6 yds
[19:52:29.832 N] (Singular) MoveToMelee(Moved): towards Skettis Soulcaller.7A13 @ 5.1 yds
[19:52:30.001 N] (Singular) StopMoving: RangeOfUnit, within 0.0 yds of Skettis Soulcaller.7A13 @ 3.7 yds, method: Styx.TreeSharp.Action.RunAction
[19:52:30.003 N] (Singular) EnsureMovementStoppedWithinMelee: stopping because target at 3.7 yds
[19:52:30.003 N] (Singular) StopMoving: Now, unit == null, method: Styx.TreeSharp.Action.RunAction
[19:52:30.370 N] (Singular) .... h=100.0%, m=96.5%, moving=N, mobs=2, Skettis Soulcaller.7A13, 100.0%, 3.5 yds, face=Y, loss=Y
[19:52:30.375 N] [Singular] *Holy Avenger on Skettis Soulcaller.7A13 @ 100.0% at 3.5 yds
[19:52:30.779 N] [Singular] *Hammer of the Righteous on Skettis Soulcaller.7A13 @ 100.0% at 3.5 yds 
[19:52:30.942 N] (Singular) [WoWRedError] Your target is dead
[19:52:30.942 N] (Singular) [CombatLog] SPELL_CAST_FAILED Hammer of the Righteous#53595 failure: 'Your target is dead'
[19:52:30.952 N] (Singular) YourCurrentTarget: changed to: (null)
[19:52:31.982 D] Clearing POI - Reason POI is dead from Combat
[19:52:32.016 D] Changed POI to: Type: Loot, Name: Skettis Soulcaller
[19:52:32.082 D] InteractDebug:509811484
[19:52:32.082 D] Interact Done:509811484
[19:52:32.082 D] [Lua.Events] Attached to event LOOT_OPENED with handler 

[19:52:32.948 N] (Singular) YourCurrentTarget: changed to: Skettis Soulcaller.7A13 h=0.0%, maxh=6986, d=3.5 yds, box=1.3, trivial=True, player=N, attackable=Y, neutral=N, hostile=Y, entry=21911, faction=90, loss=Y, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, IsBotPoi=Loot
[19:52:32.948 N] Looting Skettis Soulcaller Guid:0xF130559700447A13
[19:52:32.948 V] Blacklisting F130559700447A13 for 00:15:00 [Type: Loot] - Reason : Looting done!
[19:52:32.948 V] Blacklisting F130559700447A13 for 00:00:02 [Type: Loot] - Reason: Done looting!
[19:52:32.948 D] ItemId: 0, IsCurrency: 0, IsCoinage: 1, Byte6: 0, Byte7: 0, TextureId: 0, Quantity: 2145, Int10: 0, Int14: 0, Status: 5
[19:52:32.949 D] [Lua.Events] Detached from event LOOT_OPENED with handler 

[19:52:32.949 D] Clearing POI - Reason Finished looting
[19:52:33.621 D] Changed POI to: Type: Hotspot, Loc: <-4029.307, 3144.122, 308.7712>
[19:52:33.650 N] Moving to Type: Hotspot, Loc: <-4029.307, 3144.122, 308.7712>
[19:52:36.010 N] (Singular) OnMountUp: stopping to help HB mount quicker (fewer failed mount attempts)
[19:52:36.010 N] (Singular) StopMoving: Now, unit == null, method: Styx.CommonBot.Mount.

[19:52:36.555 N] Mounting: Swift Brown Wolf
[19:52:38.383 N] Moving to Type: Hotspot, Loc: <-4029.307, 3144.122, 308.7712>
[19:52:43.505 D] Generating new path because we are not on the old path anymore!
[19:52:43.541 N] Moving to Type: Hotspot, Loc: <-4029.307, 3144.122, 308.7712>
[19:52:45.430 N] (Singular) YourCurrentTarget: changed to: (null)
[19:52:45.432 N] Moving to Type: Hotspot, Loc: <-4029.307, 3144.122, 308.7712>
[19:52:50.983 D] Changed POI to: Type: Hotspot, Loc: <-3981.431, 3077.621, 340.5073>
[19:52:51.016 N] Moving to Type: Hotspot, Loc: <-3981.431, 3077.621, 340.5073>
[19:52:51.021 D] Could not generate full path from {-4030.598, 3144.817, 308.7359} to {-3981.431, 3077.621, 340.5073} (time used: 4 milliseconds)
[19:52:51.049 N] Moving to Type: Hotspot, Loc: <-3981.431, 3077.621, 340.5073>
[19:52:57.115 D] Updating repair cost for current equipped items. New value: [4g20s17c]
[19:52:57.116 N] Moving to Type: Hotspot, Loc: <-3981.431, 3077.621, 340.5073>
[19:55:57.129 D] Updating repair cost for current equipped items. New value: [4g20s17c]
[19:55:57.130 N] Moving to Type: Hotspot, Loc: <-3981.431, 3077.621, 340.5073>

EDIT: I have now read the Blackspot tag description and I understand it does not literally blacklist the area. Any change there is a bug in HB's navigation paths?

 

issue with the quest the arcanic oubliette

issue with the quest the arcanic oubliette View attachment 1840 2014-04-15 15.44.txt


it just runs around the barrier in circle's and does not click the little totems to open up the quest hub


yes you can shoot me now i have 1 addon on that hasnt' seemed to bother anything titan panel

 

Hello. i had issue With the quest..

Watching Our Back - Quest - World of Warcraft
watching Our back.

the bot keeps getting stunned by the guard that watching those plans.
So i had to move the bot Automatic, behind some boxes.

thanks.. the profile Works very good..

 

Fix link?

 

Link is at 3rd post on 1st page.

" If you are a Subversion expert, here is the only information you need...
Subversion Link: https://kicks-scripts.googlecode.com/svn/trunk/ "

 

Thank you Sir! I first started a grinding profile, but I always watch how the bot plays (I'm just lazy), and that was boring. This profile is great so far!

 

Hi, Ggez, and thanks for the log.

Were you certain you cleared all four caches? You will want to make certain by following the process outlined in this article:

HelpDesk: Cache corruption problems​

If you did some quests manually, or ran another questing profile, that can also cause issues. This article will explain why, and the corrective actions at your disposal:

HelpDesk: Quest giver is not offering expected quest​

cheers,
chinajade


[size=-2]Ref: Ggez's original post w/log[/size]

 

Hi, Znebto,

Bliz is constantly nerfing zones and bumping experience given for questing, kills, etc. This is a never-ending battle, and we choose not to waste time tuning such things when there are many other pressing issues to resolve.

This article should help assuage your issue:

HelpDesk: Quests are 'green' or 'gray'​

cheers,
chinajade

 

Hi, Martynrbell,

This can be caused for a number of reasons—none related to the profile. If you would like the problem analyzed, you must attach your full log that captured the issue. Please see the guide for Reporting Problems or Seeking Assistance.

cheers,
chinajade

 

Hi, Averkey,

This is caused by a clean Honorbuddy installation, believe it or not. It is not a profile issue.
The senior staff are working on a solution to make the problem go away permanently.

To understand what is going on, and how to correct the problem, please see this article:

HelpDesk: Honorbuddy can't find the quest-giving NPC​

cheers,
chinajade

 

Hi, SMuve, and many thanks for the log.

The profile is not running when Honorbuddy decides to make a vendor run—thus, your problem is not with this profile pack.

We looked through the log. But, in every instance where Honorbuddy mounted to go sell, the bot was stopped immediately afterward without giving us a chance to observe the problem. With no information in the log, there's really nothing we can offer as a corrective action.

If it happens again, please open a new thread in the Support forum with a fresh log.

cheers,
chinajade


[size=-2]Ref: SMuve's original post w/log[/size]

 

Hi, Tofsen,

There is absolutely no chance of assisting you with problems like this, unless you attach the full log that captured the issue. Please see the guide for Reporting Problems or Seeking Assistance.

cheers,
chinajade