HB ARCHIVES: Kick's Old Posts Thread--DO NOT DELETE!

just wondering how to change how close the character gets to the mob in order to attack, because as a melee class right now it targets but doesnt get close enough and waits until the mob comes to the bot

is this just bot behaviour or can i change it?

 

View attachment 8472 2013-04-22 18.30.txt im having issues with the kick profile it might be , but i left it on for 6 hours to 9 hours from level 86 and its still on it 86 dunno why , its getting stuck on some quets

 

everytime I start my 58-70 bot in hellfire with some quests picked up (contiueing since last time botting) it flies to honorhold which is an alliance city in hellfire peninsula, and Im horde. everytime it lands there and tries to kill their guards, what am I doing wrong ?

 

View attachment 1680 2013-04-24 04.55.txt View attachment 3840 2013-04-24 05.06.txt View attachment 4380 2013-04-24 04.57.txt View attachment 5560 2013-04-24 04.55.txt View attachment 5628 2013-04-24 04.58.txt


Here are a few logs.

My bot errors out on deathknight starting quests....so I installed a new HB and delete them since I am leveling a palli.

But then it turns questing bot into a grind bot and won't follow the profile correctly.

 

Your last log says, that it is grinding for lvl 21. Would just leave it grinding untill then and it will probably pick up quests. Also deleting files is never a good idea! Try a clean install, clear caches and just let it run for a while. Sometimes it takes awhile to compile quests and then it will start ob the grind to 21 to be high enough to continue on quests.

 

Are you sure you started the horde version?

 

Wow I feel dumb. Didn't know that it grinds out EXP. Thought it only quested lol. I can just bust those levels out by hand with Zygor, would probably be quicker.

 

Whaddafak

[UseItemTargetLocation-v393(warning) @line 810]: Attribute 'WaitForNpcs' is not recognized by this behavior--ignoring it. ???

starts the 88-89 profile and this shit starts spamming.
Didnt happen earlier today but something else happened, I am lvl 88 and a half and it seemed like the bot thought i was lvl 89 and almost 90, because it wanted to go grind to lvl 90 by killing some npcs.

 

Trying to Use this profile to quest on my level 30 monk and this is what im getting-
Starting the bot!
Currently Using BotBase : Questing
[Compiler Error]: c:\Users\user\Desktop\HB\Quest Behaviors\Deprecated\Escort6641.cs(19,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.Escort6641' already contains a definition for 'Escort6641'
[Compiler Error]: c:\Users\user\Desktop\HB\Quest Behaviors\SpecificQuests\DeathknightStart\FindAndBeatNpcs.cs(35,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.DeathknightStart.FindAndBeatNpcs' already contains a definition for 'FindAndBeatNpcs'
[Compiler Error]: c:\Users\user\Desktop\HB\Quest Behaviors\SpecificQuests\DeathknightStart\IntotheRealmofShadows.cs(31,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.DeathknightStart.IntotheRealmofShadows' already contains a definition for 'IntotheRealmofShadows'
[Compiler Error]: c:\Users\user\Desktop\HB\Quest Behaviors\SpecificQuests\DeathknightStart\TheGiftThatKeepsOnGiving.cs(44,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.DeathknightStart.TheGiftThatKeepsOnGiving' already contains a definition for 'TheGiftThatKeepsOnGiving'
[Compiler Error]: c:\Users\user\Desktop\HB\Quest Behaviors\SpecificQuests\DeathknightStart\TheGiftThatKeepsOnGiving.cs(299,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.DeathknightStart.TheGiftThatKeepsOnGiving' already contains a definition for 'WoWUnitExtentions'
Errors in quest behaviors!

 

I'm getting compile errors whenever I try to load a profile from the 1-90 Questing profile.
I've tried deleting cache and using a fresh install but it keeps doing the same. Also tried multiple characters and profiles.

 

Hi, Rella, and thanks for the log.

Your problem has nothing to do with Kick's profiles. You will need to follow up to the Support forum to get your problem resolved. Before posting there however, you might want to try a 'clean install'. Instructions here:

HelpDesk: "Clean installing" Honorbuddy​

cheers,
chinajade

 

Every time I try to load the 1-12 for Horde my client just crashes never have a chance to do anything and can't figure it out. Cleared my cash and new meshes. Trying fresh install right now.

View attachment 349740 2013-04-25 00.43.txt

 

Hi, Clarkgaybeul, and thanks for the log,

It looks like your local copy of Kick's profiles have been damaged. I'd delete your local copy, and redownload fresh from the Subversion.

cheers,
chinajade


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

 

Hi Ruinit, and many thanks for the log.

From the log we see this:

[18:14:22.376 D] [InteractWith-v461(debug) @line 1138]: No interactable mobs in area--terminating due to WaitForNpcs="false"
Excluded Units:
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]
Pearlfin Villager [!Alive]​

It was a problem with the profile looking for 'alive' mobs and it should've been looking for 'dead' ones. The profile has been repaired in v2278.

cheers,
chinajade

 

Hi, Wizard, and thanks for the log.

From your log we see this:

[18:26:49.568 N] [Compiler Error]: d:\INSTALL\*****\Quest Behaviors\Vehicles\VehicleMover.cs(175,18) : error CS0101: Пространство имен 'Honorbuddy.Quest_Behaviors.Vehicles.VehicleMover' уже содержит определение для 'VehicleMover'​

This means the 'clean install' was not done correctly. You can find the full instructions for a successful 'clean install' here:

HelpDesk: "Clean installing" Honorbuddy​

cheers,
chinajade

 

Hi Shae,

Your first problem looks like your local copy of Kick's profiles are damaged. You should delete your local copy, and install fresh from Kick's subversion.

As to your question--its a common one, and answered in this HelpDesk article:

HelpDesk: Updating Singular and Quest Behaviors between Honorbuddy drops​

Also, next time, we'll need to see the full, unedited log please.

cheers,
chinajade


[size=-2]Ref: Shae's issue w/partial log[/size]

 

Hi, Muskyguy20, and many thanks for the log.

It looks like your "auto loot" setting in the WoWclient has become unchecked. Correct that, and you should be off-and-away.

cheers,
chinajade


[size=-2]Ref: Muskyguy20's issue w/log[/size]

 

Hi, Gdubai, and thanks for the log.

From this log, it thinks you are done with all the quests, and there was nothing to do. If that is not correct, you are suffering from cache corruption problems. You can find the remedy here:

HelpDesk: Cache corruption problems​

cheers,
chinajade


[size=-2]Ref: Gdubai's issue w/log[/size]

 

Hi, Kokster, and thanks for the log.

Unfortunately, this log doesn't match your problem description. This log looks like you are suffering from cache corruption. You might try cleaning your caches:

HelpDesk: Cache corruption problems​

As for as "WaitForNpcs", indeed that behavior has never supported that attribute, and its something we eventually need to clean up. But, it is harmless to remain. I was unable to locate and fix the offending call, since the log doesn't match your problem description.

cheers,
chinajade


[size=-2]Ref: Kokster's issue w/log[/size]

 

Hi StreakyMcStreakerton, and many thanks for the log.

Indeed, your quest behaviors are damaged:

[01:27:43.969 N] [Compiler Error]: c:\Users\*****\Desktop\bubu\Quest Behaviors\Kick's Profiles\1-90 Questing Profile Pack\Quest Behaviors\Vehicles\BasicVehicleBehaviour.cs(43,18) : error CS0101: The namespace 'Honorbuddy.Quest_Behaviors.BasicVehicleBehaviour' already contains a definition for 'BasicVehicleBehaviour'​

The easiest way to clean up this problem is by doing a 'clean install'. You can find the instructions to succeed at it here:

HelpDesk: "Clean installing" Honorbuddy​

cheers,
chinajade


[size=-2]Ref: StreakyMcStreakerton's issue w/log[/size]