For those with 'quest behavior' issues with the .557 drop...

Some internal restructuring of Honorbuddy took place in .557, and an 'upgrade install' just gets you into trouble.

Do a clean install of Honorbuddy...
This means a new directory, do not install additional plugins or combat routines, do not copy anything from your previous installation. The specific instructions for accomplishing the goal are here:

HelpDesk: Clean installing Honorbuddy​

It would also be a good time to clean out your caches: HelpDesk: Cache corruption problems

If still no joy, make a post in the Support forum, and attach your full log.

Ref: [Guide] How to attach your log​

cheers,
chinajade


[EDIT 13Mar2013 by chinajade] A note to Quest Behavior developers

As AknA has pointed out, the release notes failed to communicate some very important information to Quest Behavior developers. Quest behaviors must now be prefixed with a special tag that tells where they should be perceived by a profile to sit in the file system relative to the Honorbuddy/Quest Behaviors/ directory. For instance:

[CustomBehaviorFileName(@"SpecificQuests\DeathknightStart\WaitForPatrol")]
public class WaitForPatrol : CustomForcedBehavior
{

...​

So, two things to note:

1. All behaviors must now be placed into the Honorbuddy/Quest Behavior/ directory.
   Previously, some authors were taking advantage of an undocumented artifact that Honorbuddy would also search for Quest Behaviors in the Honorbuddy/Default Profiles/ directory. With the new .557 drop, Honorbuddy only looks for Quest Behaviors in the Honorbuddy/Quest Behaviors/ directory.
   
   
2. Profiles will find your behavior by the name defined in the CustomBehaviorFileName tag no matter where the file physically sits in the Honorbuddy/Quest Behavior/ subdirectory.
   For instance, defining a behavior like this:
   
   [CustomBehaviorFileName(@"KicksProfiles\CapePressingService")]
   public class MyAwesomeBehavior: CustomForcedBehavior
   {
   

   ...​
   
   would require the profile to invoke the behavior as:
   
   <CustomBehavior File="KicksProfiles\CapePressingService" />​
   
   We ask quest behavior and profile writers to please organize their offerings in a sane fashion, and try not to pollute the common shared namespace--thank you!

[size=-2]Linq: [noparse]For those with 'quest behavior' issues with the .557 drop[/noparse][/size]

 

Thank you so much ChinaJade Cured my questing problem right up.

 

Worked for me, thanks ChinJade!

 

nice, worked perfect.

 

I don't understand something, why do you do a fresh install when the whole thing isn't the problem? Seeing as the only trouble with this update is the quest behaviors and the MOP Daily Profile folder. Either way, it's your choice on how you approach this issue, I've been using the auto updater to do the dirty work for me since they added it. I just don't have the time or patience to go through my folders reapplying every last plugin maps etc that I accumulated through my time to EVER consider this fresh install. http://www.thebuddyforum.com/honorbuddy-forum/115079-hb-questing-error-issues-577-fix.html

 

Hi, Phazekiller,

I understand your perspective. But, these are the considerations:

1. In this drop, HBcore seriously changed the way it internally compiles, locates, handles, and invokes quest behaviors.
   To make this happen, the HB-shipped behaviors now have a 'special tagging' that will be missing from any of the old quest behaviors. There are also other differences that the older behaviors will cause problems.
   
   
2. Some of the quest behaviors have been reorganized/restructured.
   If you copy anything from your previous installation, you will create 'naming conflicts' and 'compile problems' for Honorbuddy.
   
   
3. Many in our Community simply do not have the skills to perform the analysis of how to safely upgrade 'alternate style' as you did.
   We do not keep track of the skill sets of our individual Community members, and the 'lowest common denominator' is to express it in terms that work for everyone, and requires as little technical skill as possible.

The changes to HBcore give considerable more power to Quest Behaviors. The problems caused by the internal changes is not any fault of the Quest Behaviors, although that's what the inexperienced eye will believe the problem to be.

I seriously understand the desire to preserve all the old stuff. But, if you don't follow our recommendations, you are just setting yourself up for heartburn when nothing works right.

cheers,
chinajade

 

Well, I finaly figured it out, had to add '[CustomBehaviorFileName(@"Misc\QBName")]' to the behavior for it to work.

 

Thank you, was experiencing this, all cleared up now.

 

Hey guys I'm sorry but I'm finding this very difficult to comprehend and fix. Any way I can get some help.

 

Hi, Zamz,

Certainly: HelpDesk: Clean installing Honorbuddy

That HelpDesk article was written after the original post was made. Due to your comment, I've updated the original post to link to the appropriate HelpDesk article--thank you for implicitly pointing this out.

cheers,
chinajade

 

Can someone give me step by step instructions on where to find those files and delete them? Would be greatly appreciated.

 

Hi, Pleuch,

This article should guide you through the process:

HelpDesk: "Clean installing" Honorbuddy​

If you continue to have problems, please follow up to the Support forum with your full log that demonstrates whatever issue you're having.

Ref: [Guide] How to attach your log​

Thread closed--Back to the grave, ye old musty necro'd thread!

cheers,
chinajade