Reply To: Can Nested FSM/BTs have their own BlackBoards?

[Gavalakis]

Hey,

Thanks a lot for your time in writing your suggestion.
Very similar to this, is something I want to improve and implement long time now, meaning the ability of sub-trees to have their own public/protected blackboard variables able to define through the inspector panel of a sub-tree node like you mention. The only real problem I am facing is the fact that changing the workflow in such a drastic way will break designs already created up to current version. So the real problem is to implement these in a way that will not break anything and keep everything seamless.

Most of the work to actualy support these features has been done code wise, so it’s mostly about me putting them to use in a way that will not break anything 🙂

I am not really sure what you suggest with the Blackboard changes at the end though :).
The way I’ve though of this, is that if each behaviour has it’s own blackboard variables, then the Blackboad component added on the GraphOwner, would be only used to parametrize the “master” behaviour’s variables.
Can you elaborate on that?

Thanks!

Join us on Discord: https://discord.gg/97q2Rjh