Reply To: Large BT advice

[Gavalakis]

Hey!
Sorry for the late reply.
That’s a nice question indeed 🙂

My personal suggestion regarding on where to use what, would be to use FSMs at the top higher level to define the different very broad states that a character can be in, like for example, “Gather”, “Combat”, “Idle”, with each of these states being a Sub-Behaviour Tree, or a FlowScript state, which are better for defining precise behaviours than FSMs are.

So, once again, for complex behaviours, I would always use an master FSM at the topmost level and have each FSM state either be a Behaviour Tree state, or a FlowScript state depending on what you feel comfortable with or prefer over the one.

I would personaly never use a BT with nested FSMs (and I think I will also remove that ability in future version), but is some relevant non-complex behaviours, I might simply opt to use a single Behaviour Tree or FlowScript and forget about nested graphs.

Regarding BehaviourTrees vs FlowScripts, I would use FlowScripts when the behaviour is heavility based on events rather than conditions. For behaviours based on conditions (like for example checking variables, distance between objects, etc), I would use a Behaviour Tree instead of a FlowScript.

Let me know what you think.
Cheers!

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