FSM name changes not recognised when using Set FSM variable actions

[jess84]

I guess this is probably halfway between bug and feature request, but I'll put it here anyway.

This has been bothering me for a while, and resulted in things not working and then having to track down the cause;

If you use an action where you're selecting another FSM from the dropdown (e.g. Set FSM Float), if the name of that target FSM changes, it is not automatically updated. Therefore the action is looking for an FSM that no longer exists.

It then means manually tracking down all of these situations.

As this behaviour is different to other similar situations, such as renaming an object or a gameobject (which is updated fine), it would be a nice to have functionality.

[Lane]

Did a quick test on this..

It still seems to work despite the names being different, but yeah the name displayed is the old one. Is it actually breaking the connection for you?

[jess84]

yeah, it breaks the link for me. (so float variables in other FSMs on the same prefab not being set)

[jeanfabre]

Hi,

 yes, Fsm names are not "Pointers", so you have to use this with extrem care indeed.

when I start using these kind of action, I enforce a very strict policy of "name it and never rename", which also means that I careful name each fsm so that I don't have to refactor them later and other parts of my project can rely on fsm names.

 When this is not good, like when I know this is a work in progress and I am not sure myself where this is going, I don't rely on this and go for global event that I fire to a gameobject specifically ( the one with this fsm that I don't trust by name) and then problem is solved, I do the work inside the fsm that simply catch this global event, likely getting data from it and storing into it itself into its own variables.

 I would however enjoy a proper pointer system like events and variables... maybe one day:)

bye,

 Jean