No problem. I completely understand what you mean now.
Indeed this is not possible at least right now and will best require a new node.
Instead of using nested lists within lists in a custom ActionTask, you could probably instead create a custom FSM node with two ActionLists, where one is required and the other is optional. A good start for creating such a node, would be to look at the included “SuperActionState” node (which makes use of more than one ActionLists effectively and with cleaner UI).
If you want I can help you with the code for making such a node.
Let me know if so.
Gavalakis
