You could create an ActionList asset to close a series of menus, and then you would just need to run it instead of recreating the same chain of actions every time.
No, I mean you can just create a regular ActionList assent called, say, "Turn off xxx menus" where xxx is the label you'd have given the menus if such a functionality existed. There you can add a regular "turn off menu" action for each individual menu you want to turn off at the same time. Once this is done, you will be able to run the the asset you've just created instead of using several "turn off menu" actions every time you need to turn off all the menus with that "label". No parameters necessary.
Comments
You could create an ActionList asset to close a series of menus, and then you would just need to run it instead of recreating the same chain of actions every time.
Do you mean with parameters? And if so, what is the Type for menus?
No, I mean you can just create a regular ActionList assent called, say, "Turn off xxx menus" where xxx is the label you'd have given the menus if such a functionality existed. There you can add a regular "turn off menu" action for each individual menu you want to turn off at the same time. Once this is done, you will be able to run the the asset you've just created instead of using several "turn off menu" actions every time you need to turn off all the menus with that "label". No parameters necessary.
Menu name fields in Actions can be overridden with parameters of type "String".