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

[drdeath]

View attachment 5448 2015-12-26 11.15.txt

hi i re loaded Hb set the profile and got this again it keeps happening on some quests no all use to have no problems with this befor the ban wave and new hb

 

[f299]

The auto-loader won't actively change the profile you're running as you level.

All it does is conveniently load the profile you need for your character based off of race/faction.
If you're using v2, it will also load based off of level - and will navigate to the questing location if you aren't in the proper location.

After the auto-loader loads into a profile, it has no control of the bot at all. So from that point on, the actual 'questing' profile will determine what happens with the bot.
For the bot to load profiles as you level, this sort of logic would need to be hard-coded into the actual questing profiles or into a plugin.

The simplest solution would be to use a 'DoWhen' that reloads the Auto-Loader everytime you level.
If you want, I can give suggestions on how to do this.

Hey Echo! Thanks for the reply.

I would love to hear your suggestions on how to accomplish this.

 

[EchoTiger]

I have log files for all 5 characters this happened to - it wasn't an isolated incident - I'll see about finding one.

Alright, thanks!

 

[EchoTiger]

Love your work. this is amazing.
been working with it for a few years now.
And lately it's just flawless.

Love you 2 days 90 - 100 no heirlooms, no stucks, no bullshit.
I logoff every 8 hours. it's amazing.

Glad to see it's working so well for you!

90-100 has been more recently/actively tested than the rest of the levels, especially the Alliance side.
The Horde side has been as well, but not as much.

Currently most of our testing focus is on the 1-90 portion.
Any bugs or improvements that can be made are being worked on.

 

[EchoTiger]

Had exactly same issue for minimum 1 time. don't have logs for it, but there is definitely as issue.

And this is with Alliance? If so, it's gotta be a new bug.
We've never ran across it.

If a log can't surface up, I'll get some testers on it very soon to see what's going on.

 

[EchoTiger]

View attachment 195034

hi i re loaded Hb set the profile and got this again it keeps happening on some quests no all use to have no problems with this befor the ban wave and new hb

You're getting an "Access to the path 'F:\System Volume Information' is denied" error. I'm not entirely sure what causes that or the solution to it.
You may need to report this to the "Support Section" for Chinajade or Tony to look at.

 

[EchoTiger]

Hey Echo! Thanks for the reply.

I would love to hear your suggestions on how to accomplish this.

Here's a quick snippet I wrote up:

<CustomBehavior File="RunCode" Type="Definition" Code="int StartLevel = StyxWoW.Me.Level;" /> <!-- Store your starting level as a int Variable --> 
<CustomBehavior File="WaitTimer" WaitTime="500" /> 
<CustomBehavior File="Hooks\DoWhen" ActivityName="LoadAutoLoader_OnLevelUp" AllowUseWhileMounted="true" UseWhen="StartLevel != StyxWoW.Me.Level" > 
     <CustomBehavior File="RunCode" Code="Logging.Write(System.Windows.Media.Colors.Yellow, &quot;[Profile Notification]: We leveled!  Loading Auto-Loader.&quot;);" /> 
     <CustomBehavior File="RunCode" Code="ProfileManager.LoadNew(&quot;C:/Example/Honorbuddy/Questing Profiles/Auto-Loader v2.xml&quot;);" /> 
</CustomBehavior>

You would place this directly under the <QuestOrder> in each of the questing profiles.

What it's doing is: When the profile starts, your current level is stored in the bot as the int "StartLevel" to be used as reference when we level.
DoWhen hooks into the bot passively and won't activate until the UseWhen returns "true"

In this situation, the UseWhen is set to: "StartLevel != StyxWoW.Me.Level" - which in English that's simply saying: "If our starting level doesn't equal our current level."
So when our starting level doesn't equal our current level, the UseWhen will see "true" and the DoWhen will activate.

Once the DoWhen activates, it'll load the auto-loader.



Now the only issue with this is: not all profiles are located in the same directory.
So in order to load the Auto-Loader, it needs to be in a static path.
That way we can load to it directly without traversing various directories.

Given this, in the code above you should see this:

C:/Example/Honorbuddy/Questing Profiles/Auto-Loader v2.xml​

You'll need to change this directory to the location of your Auto-Loader.
Be sure to use forward slashes ( / ) and not back slashes ( \ ) when writing the directory or else you'll get an error.
Back slashes in C# are an "escape" trigger.

 

[zaaq]

I got a problem
In terokkar forest the bot had to kill wolfs and spiders but it just keept flying right over them and it refused to dismount

Never had this problem before, so i Wonder if it's because of the new HB update?

 

[f299]

Here's a quick snippet I wrote up:

<CustomBehavior File="RunCode" Type="Definition" Code="int StartLevel = StyxWoW.Me.Level;" /> <!-- Store your starting level as a int Variable --> 
<CustomBehavior File="WaitTimer" WaitTime="500" /> 
<CustomBehavior File="Hooks\DoWhen" ActivityName="LoadAutoLoader_OnLevelUp" AllowUseWhileMounted="true" UseWhen="StartLevel != StyxWoW.Me.Level" > 
     <CustomBehavior File="RunCode" Code="Logging.Write(System.Windows.Media.Colors.Yellow, &quot;[Profile Notification]: We leveled!  Loading Auto-Loader.&quot;);" /> 
     <CustomBehavior File="RunCode" Code="ProfileManager.LoadNew(&quot;C:/Example/Honorbuddy/Questing Profiles/Auto-Loader v2.xml&quot;);" /> 
</CustomBehavior>

You would place this directly under the <QuestOrder> in each of the questing profiles.

What it's doing is: When the profile starts, your current level is stored in the bot as the int "StartLevel" to be used as reference when we level.
DoWhen hooks into the bot passively and won't activate until the UseWhen returns "true"

In this situation, the UseWhen is set to: "StartLevel != StyxWoW.Me.Level" - which in English that's simply saying: "If our starting level doesn't equal our current level."
So when our starting level doesn't equal our current level, the UseWhen will see "true" and the DoWhen will activate.

Once the DoWhen activates, it'll load the auto-loader.



Now the only issue with this is: not all profiles are located in the same directory.
So in order to load the Auto-Loader, it needs to be in a static path.
That way we can load to it directly without traversing various directories.

Given this, in the code above you should see this:

C:/Example/Honorbuddy/Questing Profiles/Auto-Loader v2.xml​

You'll need to change this directory to the location of your Auto-Loader.
Be sure to use forward slashes ( / ) and not back slashes ( \ ) when writing the directory or else you'll get an error.
Back slashes in C# are an "escape" trigger.

Beautiful, thank you Echo! I'll test it out soon.

 

[EchoTiger]

I got a problem
In terokkar forest the bot had to kill wolfs and spiders but it just keept flying right over them and it refused to dismount

Never had this problem before, so i Wonder if it's because of the new HB update?

I have an idea of what it may of been.
The <Objective/> tag has issues with flying mounts in which it won't dismount if the player is flying.

Do you remember which quest it was?

 

[zaaq]

I have an idea of what it may of been.
The <Objective/> tag has issues with flying mounts in which it won't dismount if the player is flying.

Do you remember which quest it was?

I got the same problem in Nagrand.

Right now its doing Talbuk mastery and Clefthoof mastery (part 2) and Again it wont dismount. Just flying arround in cirkels.

 

[EchoTiger]

I got the same problem in Nagrand.

Right now its doing Talbuk mastery and Clefthoof mastery (part 2) and Again it wont dismount. Just flying arround in cirkels.

I'll look into it. Something may need to be done to improve the <Objective/> tag's "KillMob" mounting logic.

 

[drdeath]

thanks EchoTiger did a new instal on a diffrent drive and looks like its running as great as it all ways did thanks

 

[Ilja Rogoff]

And this is with Alliance? If so, it's gotta be a new bug.
We've never ran across it.

If a log can't surface up, I'll get some testers on it very soon to see what's going on.

Had it with alliance too, afair. Right now I got it on a horde char, see attached log.
After restarting HB, it used the portal as it should

 

[LiquidAtoR]

Upon starting the questing bot with Singular routine and Kicks profile loaded trough Autoloader v2 from the store gives a few errors (it runs, so they are not critical):
XML error on line 5580, deprecated quest behaviour, and a NAME attribute that's not recognized in a few places:

[19:43:19.865 D] Activity: Honorbuddy Startup Complete
[19:43:19.865 N] Honorbuddy Startup Complete
[19:43:46.477 N] Starting the bot!
[19:43:46.477 N] Currently Using BotBase : Questing
[19:43:46.477 D] Character is a level 40 Human Mage
[19:43:46.477 N] Current zone is Western Plaguelands (http://wowhead.com/zone=28)
[19:43:46.482 D] Loading profile from store:///1-100 Questing Profile Pack/Classic/[A - Quest] 1-58 [Kick]/[A - Quest] EK 12-58 [Kick].xml
[19:43:51.374 N] Warning: XML Error: Could not parse 'If' body node! - On line 5580
[19:43:52.486 D] Downloaded map Azeroth
[19:43:52.713 D] Changed map(s) to Azeroth
[19:43:52.753 N] Changing current profile to [A - Quest] EK 12-58 [Kick] ($Rev: 4572 $)
[19:43:52.754 D] BlackspotManager forcing unload of meshes - New profile loaded
[19:43:52.811 D] [EnablePlugins-vUnknown(debug)] Database "ProfileCompatibilityInfo" has changed--re-reading.
[19:43:52.819 D] [EnablePlugins-vUnknown(debug)] Database "ProfileCompatibilityInfo" re-read complete.
[19:43:53.095 N] [KillUntilComplete-v2150(warning)] Attribute 'Name' is not a recognized attribute--ignoring it.
[Ref: "[A - Quest] EK 12-58 [Kick] ($Rev: 4572 $)" @line 6225]
[19:43:53.165 D] [Message-v1728(debug)] Weapon AzimuthMin: -0,35 (given)
[19:43:53.165 D] [Message-v1728(debug)] Weapon AzimuthMax: 1,13 (given)
[19:43:53.168 D] [InteractWith-v2156(debug)] Weapon AzimuthMin: -0,35 (given)
[19:43:53.168 D] [InteractWith-v2156(debug)] Weapon AzimuthMax: 1,13 (given)
[19:43:53.219 N] [BasicVehicleBehaviour-v2022(warning)] *****
* THIS BEHAVIOR IS DEPRECATED, and will be retired on July 31th 2012.
*
* BasicVehicleBehavior adds _no_ _additonal_ _value_ over the VehicleMover behavior.
* Please update the profile to use the VehicleMover behavior.*****
[19:43:53.700 N] [KillUntilComplete-v2150(warning)] Attribute 'Name' is not a recognized attribute--ignoring it.
[Ref: "[A - Quest] EK 12-58 [Kick] ($Rev: 4572 $)" @line 8683]
[19:43:53.700 N] [KillUntilComplete-v2150(warning)] Attribute 'Name' is not a recognized attribute--ignoring it.
[Ref: "[A - Quest] EK 12-58 [Kick] ($Rev: 4572 $)" @line 8684]

 

[EchoTiger]

Had it with alliance too, afair. Right now I got it on a horde char, see attached log.
After restarting HB, it used the portal as it should

Thanks for the log, It's a bit messy so I'll have to investigate it a bit to see what exactly is failing.

 

[EchoTiger]

Upon starting the questing bot with Singular routine and Kicks profile loaded trough Autoloader v2 from the store gives a few errors (it runs, so they are not critical):
XML error on line 5580, deprecated quest behaviour, and a NAME attribute that's not recognized in a few places:

That's all fine.
It's just from where old code is still lingering in the profiles and Honorbuddy is telling us that it's old.
It shouldn't cause any actual performance or execution issues though.

 

[Zaldo]

Hello! First: Thanks for the great profile!
I've been using it for years and it has always impressed me.
But since the latest HB-build I have the following problem:
The bot will of course continue questing in Hyjal with lvl 80th
But he flies to Northrend, from there to Dalaran and through the portal to Stormwind to fly to the North. There he gets stuck in the mountains.

I have also attached a log.View attachment 8028 2015-12-27 20.59.txt

 

[DoubleTap]

Leveling an Alliance Druid.
He's in STV at level 36.
I have no active quests.
No matter what I do the bot dumps me in the water by the island in Butchers Bay.
HB even ran be from Iron Forge all the way back to the same spot.

I've reloaded the game and HB multiple times, reloaded the profile, manually started quests, traveled to different parts of STV and other zones..nothing has help.

Log attached.

 

[EchoTiger]

Leveling an Alliance Druid.
He's in STV at level 36.
I have no active quests.
No matter what I do the bot dumps me in the water by the island in Butchers Bay.
HB even ran be from Iron Forge all the way back to the same spot.

I've reloaded the game and HB multiple times, reloaded the profile, manually started quests, traveled to different parts of STV and other zones..nothing has help.

Log attached.

It looks like it's trying t pick up The Damsel's Luck from Fleet Master Firallon.
Could you try picking it up manually then starting the bot?