New Unity Behavior 1.0.1 Package Improvement?

[TheManiacs]

Hi Unity Behavior Developers Team,
I’ve had the chance to try out the new Behavior Package, and I must say, it feels amazing to use. I’m really excited about the potential of using this package as my long-term BT solution. With that in mind, I wanted to share a few suggestions that I think could help improve the experience even further.

1. Support for Complex Object Types in Blackboard and Node Inspector:
   

   
   
   Currently, the Blackboard and Node Inspector don’t seem to support complex object types effectively.
   While I understand that I can create individual float, string, etc., variables in the Blackboard or Node scripts, this approach can be cumbersome for more complex types.
   
   

2. Direct Serialization of Fields in Node Inspector:
   

   
   
   Sometimes, I would like the Node Inspector to have fields that can be serialized directly without needing to wrap them in BlackboardVariable<>.
   This is particularly relevant for nodes that don’t require the field to be shared in the Blackboard but need it for internal functionality.
   Perhaps making an [NormalSerialized] attribute as a marker for serialize normally ?
   For example, my game has some Area IDs that I would like to select from a dropdown to avoid potential typos.
   
   

3: Negate Toggle for Each Condition Individually:
I believe each condition should have a negate toggle option.
I’ve encountered scenarios where I needed to “Repeat while !Condition.” I did define the normal condition script and then I ended up having to create additional scripts just to negate it.
This could become quite cumbersome, especially if there are 10 to 50 different conditions.

Thank you for considering these suggestions. I truly appreciate the effort that has gone into creating this package, and I’m looking forward to seeing how it evolves.

[ShaneeNishry]

Hi @TheManiacs!

I’m so happy you like our package! Thank you so much for the feedback. I’ll address it here:

1. Support for Complex Object Types in Blackboard and Node Inspector

   • Yes! This is definitely on the roadmap. We need more time to solve the property drawer and serialization for it correctly, but it’s coming. This is the same for structs / PODs.

2. Direct Serialization of Fields in Node Inspector

   • That too is very likely to come, but we might use an attribute or something to make sure the user actually wants to show them. It’s on our roadmap.

3. Negate Toggle for Each Condition Individually

   • We’ll look into it! We need to figure out the right UI for it.