My suggestion would be to use FSMs in this case. The reason why is, because you have a series of definete steps, which can easily be translated to states.
The way I would probably set this up, would be to have one state for each step, as well as the wrong inbetween steps.
Then each step/state, OnEnter, would play some animations like you need and once that is complete, show the UI buttons relevant to this step towards the next that were previously hidden (I’m just making a suggestion here).
Each button could then correspond to a state transition going to the next step/state, or a wrong inbetween one. Checking the buttons can easily be done the the “UGUI/Button Clicked” Condition attached on the transitions.
If you need a screenshot of what I mean, by all means let me know 🙂
But, I definetely suggest FSM in this case over BTs.
Gavalakis
