Yeah, that would work. I was thinking of having parameters to the embedded flowscripts that show up like parameters you can write on custom actions/conditions. But you set them up as value inputs to a flowscript, just like a macro. At the moment, to pass data to the flowscript I must create a blackboard variable and have the flowscript read it.

This is fine, but it means the name must remain constant. If I wanted to re-use the flowscript in a different situation and reference a different BB variable then I need to write a new embedded flowscript and change the name it is reading. I have been working around this by making my macros the re-usable parts and then changing the BB variables that are fed into them in the embedded flowscripts.

Hope this makes sense! I can attach some example screenshots if you like.