chinajade
Community Developer
- Joined
- Jul 20, 2010
- Messages
- 17,540
- Reaction score
- 172
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:
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.
cheers,
chinajade
[EDIT 13Mar2013 by chinajade] A note to Quest Behavior developers
So, two things to note:
[size=-2]Linq: [noparse]For those with 'quest behavior' issues with the .557 drop[/noparse][/size]
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:
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.
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:Well, I finaly figured it out, had to add '[CustomBehaviorFileName(@"Misc\QBName")]' to the behavior for it to work.
[CustomBehaviorFileName(@"SpecificQuests\DeathknightStart\WaitForPatrol")]
public class WaitForPatrol : CustomForcedBehavior
{
public class WaitForPatrol : CustomForcedBehavior
{
...
So, two things to note:
- 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.
- 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]
Last edited: