About “Conditional Action Gate”, are you refering to Selector Composite with just 2 children and a condition assigned to it?
Although it does not follow the Behaviour Tree standards 🙂 I can certainly add this, at least online.
Regarding your 2nd suggestions.
Right now you dont have to explicitly declare a Transform variable. Instead you can (and better should) declare a
BBParater.
With that, you access the value of the parameter with the .value property and it allows you to select a blackboard variable instead of directly assigning a reference as well.
I could easility add converters within the BBParemeter class to allows selection of for example a Transform where a Vector3 is required, thus declaring a BBParameter would allows for:
– A direct Vector3 value
– A blackboard Vector3 blackboard variable
– A Transform blackboard variable
I suppose that is what you mean.
I am not sure what you mean with the “Loop” though.
Also, if you’d like to take the maths off the graph, you can bind Blackboard variables to properties and have perfect control of what a “variable” gets or sets by the data bound property in your script.
So you can have a “Fear” variable, bound to a Fear public property in for example your “Character” mono script.
Then whenever you use get the fear variable it returns the Fear property value, where you can calculate it however you’d like in code and out of the graph.
Gavalakis
