Reply To: Possible Bug (or misunderstanding)

[Gavalakis]

Hello,

Until a couple of versions before, an FSM was considered Finished when it has reached a Finished state with no outgoing connections, like in your case. Some people said it was a bit unvonenient to end an FSM automaticaly in such a way and thus I changed it.
So what happens now, it’s that even though the nested FSM’s single state is Finished, the nested FSM as whole is not finished, hense the “clock” icon on the node in the MAIN FSM nested node.
I agree that it’s more logical for a nested FSM to be Finished in that case though.
I will take a look at doing this again in case an FSM is nested, possibly by an option on the Nested FSM State Node.

Regarding the local blackboard. NC doesn’t work this way. All Nested Systems (BTs, FSMs) use a single blackboard that is passed to them from the root/main system. That is also why it is changed in editor time to reflect that.
That way a nested FSM or BT is more flexible as it can be “parametrized”.
For example say you are using the same nested FSM that makes use of a “target” variable, in 2 or more completely different agents. The “target” can be set to completely different value depending on the agent rather than the FSM explicitely.

I’ve made the reference fields on the FSM inspector super transparent to denote that they are just references. I think I will have to remove those 2 reference field completely to remove any confusion.

Thanks

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