In the Nested FlowScript inspector panel, you can assign any existing flowscript you want to (not always a new one), but the flowscript assigned there has to be an asset flowscript and not a bound flowscript of a FlowScriptController in the scene.
Even though you can assign a bound flowscript of a controller in the scene, it is really not recommended for two important reasons to keep in mind:
1. The controller’s gameobject will be instantiated.
2. The variables used will be the ones of the graph the nested flowscript *node* is within (eg the FSM), not the ones of the FlowScriptController you are referencing the flowscript from.
For the above two reasons, sub-systems are designed to work with asset graphs. Is there a reason why you don’t want to use an asset graph?
Gavalakis
