By using Script Control tasks to call existing functions, you still seperate actions (functions) into small pieces and combine them together in the behaviour tree. So this way the behaviour tree controls the flow of which the functions will be called, checked etc.
Actions can still be reconnected as you please to define or alter the behaviour. Its almost the same as writing custom tasks. Only this way, you are writing the “task” within your own class and it’s definition it’s even based per type (as in our previous example). The script control task simply wraps the functionalities of your class. I hope this made sense 🙂
Behaviour trees are more about how and when things are executed rather than what. That’s how I see it at least.
Replacing subtrees at runtime is currently non convenient, but in the next version there will simply be exposed fields in the inspector to choose what subtrees to replace with which.
I will build a dll version tomorrow that I will be back and send it to you (at the email you registered with?)
No, I did not study at ITU. Not even close. I am self tought regarding programming 🙂
Cheers!
Join us on Discord: https://discord.gg/97q2Rjh
Login
Register
By registering on this website you agree to our Privacy Policy.
