The FSM state itself uses an ActionList under the hood. There is not much point in using an ActionList inside another ActionList as it will only makes things confusing to handle although you certainly can do that.
As a side note, an ActionList by default runs all it’s actions in order one after another. When one action completes the next is fired, like a mini sequencer. The ActionList that the FSM State has, is set to run all actions within in parallel though.
So if in your state you have for example 2 Action List within the State’s List, then the 2 Action Lists will be executed in parallel while each of the 2 added ActionLists within will execute their actions in order.
Again, this is highly unrecommented as the state will become totaly unmanagable and chaos. I just mentioned it just to know how it works 🙂
I think it will be fine just using single actions in an FSM state
All actions in a state will run in parallel to each other. Execution is still called in the order they are listed top to bottom per frame. For example:
generally i need sequential run. assume that i need 2 itween move actions in one state.i do not want to use 2 states for this. how can i do that using 1 state?
I will expose the option to select if the actions will run in sequence or in parallel in the next release.
Right now, if you add an ActionList action in your state, all actions within that ActionList Action will run in sequence, but I don’t recomment it because it will be difficult to manage in the editor.
If you need the option to select Seuencer or Parallel ASAP, let me know and I will tell you changes you have to make.
I will actually submit the new version tomorrow 🙂
It will be better to wait since I made the change a bit more involved if that’s ok with you.
If not I can tell you a temporary solution