Generally speaking, I would probably never use a Behaviour Tree with SubFSMs as at least to me, it makes much more sense that the “root”, is an FSM (with BT States) rather than a BT (with nested FSMs). This way, the login is more clearly separated into states and each state (a BT) defines the logic of that state, while the transitions when to change the states.
I would use a BT as “root” only with SubBTs and not SubFSMs.
To be honest, some time ago I was considering deprecating Nested FSM in BTs completely just to provide a more streamlined workflow, but some people were still using them, so this never happened 🙂
As far as doing checks regardless of what state the FSM is in, would not the “Any State” work for what you are after?
Please let me know what you think.
(PS: Hmm. I will check the follow up email notification. Never reported that it does not work before.)
Join us on Discord: https://discord.gg/97q2Rjh
Login
Register
By registering on this website you agree to our Privacy Policy.