Do consider the following way I’d set it up:
- this is a menu actor:
It has an Instance Editable variable that can point to another menu. You can have more of those, perhaps you want to navigate forth & back, or zigzag between them. The script in this menu actor:
- I’ve placed a bunch of menus in the level and told each one where to go next using the above-mentioned variable:
Below, once a menu actor is selected, you can set up more stuff - what each widget component displays and in what mode, who is hidden and so on.
Think of this as of a template for a menu page.
You can change the order of scripted events, ofc, in case you want different / more delays and control showing / hiding better. It behaves like so:
This should support any number of menus and dramatically minimise the amount of script needed.
Not sure how your menus are made, and what else is needed. There’s always more to do. To have it work better, I’d have a base widget class that dispatches a transition call. Or have the button call an interface and send message to the owning actor.