Natfoth VS Shipped QB's

[tubajedimr]

So as the wonderful ChinaJade has so wonderfully pointed out, the Quest Behaviors that are shipped are different then the ones made by Natfoth, though they share the same names. If you have been using Natfoth's and you DL'd the new HB recently, your QB's have in fact been replaced with HB's shipped QB's and you should probably swap them out.

I have also included in this post the corrected version of TalkToAndListenToStory for those that have been having trouble with it, and haven't seen the correction yet.

I'm not sure if this conflict between the two QB's is going to be a long standing issue or if it will be corrected, but for the time being, this is the simple fix. The link to Natfoth's QB's is here.

Thanks,
TubaJedi

 

[Nuok]

Use the built in there more likely to be supported, and are currently working very well.

 

[tubajedimr]

Use the built in there more likely to be supported, and are currently working very well.

That was what I was using and had nothing but errors when beta testing my 10-15 quest profile. After switching to Natfoth's, errors pretty much ceased, other then some known errors that he hasn't fixed yet, such as the included file in my post.

 

[chinajade]

If you have been using Natfoth's and you DL'd the new HB recently, your QB's have in fact been replaced with HB's shipped QB's and you should probably swap them out.

Aye, this is a horrible maintenance issue that I don't believe anyone saw coming. CustomBehaviors with the same names, but different attribute expectations (and maybe different behavior) is an untenable situation to be in.

Profiles written against one set of these behaviors will be completely incompatible with profiles written with the other set of these behaviors.

I believe the Community or the HBteam and Natfoth need to figure out what to do with this pronto. The current state of affairs will fragment the Community based on the different expectations of the Profile Writers.

We need to rapidly figure out what the right thing to do is, and do it. If that involves fixing bugs in the shipped behaviors, we need to get that addressed pronto. The alternative of jettisoning the shipped behaviors in favor of Natfoth's is also a viable option. But as a Community, and particularly the Profile Writers, need to all be on the same page as what to do about this. If not, the result is just going to be a horrible mess.

From a Wiki standpoint, it will always document what is shipped with Honorbuddy. The Wiki is hosted by Bossland GmbH, and this seems to be the 'right thing to do' in this situation. That does not preclude us from capturing Natfoth's behaviors in another section of the Wiki. I will admit that documenting dozens of 'almost identical' behaviors is not an appealing option for me, and promises substantial confusion for the poor Profile Writers.

cheers,
chinajade

 

[tubajedimr]

I've opted to just not use the custombehaviors in my profiles for now unless I absolutely have to for one reason or nother. And I think if I do use them I will include the .cs files I use in the profile post just to try and keep things smooth. This is a huge oversight by the HB team.

It might be worth noting that perhaps one could custom rename the files. Such as NoCombatToMoveNAT or NoCombatToMoveHB

Nevetheless, this is still slightly confusing. When do you use one and not the other?

I've been experiencing error after error with the HB shipped CS's and none with natfoth (other then known errors). I think thats worth noting too.

The HB Behaviors all come back as "Cannot Parse" (don't know the exact error)


EDIT: The error is "Error compliing behavior for Custom Behavior with ID XXXXX" and it does this for every single one of them I use.