Thanks a lot for your positive feedback on the assets. I am really glad you like them so far 🙂
There is indeed an inconsistency right now between Blackboard usage in Dialogue Trees in comparison with all other type of graphs (BT, FSM, FlowScripts) and is something that I would of course like to change in the future so that Dialogue Trees also work the same way as all the other type of graphs do, blackboard-wise. The reasons behind this inconsistency, is a bit of a long story to be honest 🙂
Right now, if you want to use scene object references for blackboard variables to be used in a Dialogue Tree, there are really two options:
– The first one is the just like to stated, to use a Scene Global Blackboard indeed.
– The other option is to use Bound Dialogue Trees instead of Asset Dialogue Trees. If you are using a Bound Dialogue Tree, then scene object references would be no problem.
Other than the differences in the ability to use scene object references, the local blackboard that the Dialogue Trees are currently using, versus using a Blackboard Component are pretty much equivalent. You can still for example access the Blackboard variables either through actions, conditions or even through code.
Unless I misunderstood something, can you please explain in a bit more details what you would like to do that is not possible by using the local blackboard, that would otherwise be by using a Blackboard component like the other graphs systems do.
Please let me know.
Thank you!
Join us on Discord: https://discord.gg/97q2Rjh
Login
Register
By registering on this website you agree to our Privacy Policy.