One challenge I face is when trying to re-use menu UI's across scenes, I often find my UI's getting un-mapped. Or if I want to re-use them, sometimes they don't get un-mapped but I just have to go through and manually re-map them all to another model.
A possible solution would be if I could use a Trigger Router from the start. Basically I load all the triggers and it connects to that router, and in that router I set who they go to. If I then move it to another scene, it doesn't break all my links, it just breaks who it goes to. I then go to the router and hit refresh and select the new person and it would then continue working again. This would make re-using UI buttons much more easier and cause less issues.
It also would give you the ability to test a set of buttons/options on another model quickly.
Another big use case for this would be for a scene like Get Her Pregnant. I have a set of buttons for Girl 1, and then the same exact set of buttons for Girl 2. Instead I could have a toggle button that changes the router to go to the other girl. I could then remove an entire row of buttons in the UI and instead just use the router toggle button with one row.
This could then cut the number of buttons needed/used in half for that section. A scene that has a need for possibly 40 buttons could then have 20 with a router for example. Or it could be the difference between someone even giving that option in their UI because they don't want to create another 20 buttons or don't have the space for them or want to mess with show/hide toggles and that many atoms in their project.
Does anything like this exist? If not it might be a plugin idea to consider.
A possible solution would be if I could use a Trigger Router from the start. Basically I load all the triggers and it connects to that router, and in that router I set who they go to. If I then move it to another scene, it doesn't break all my links, it just breaks who it goes to. I then go to the router and hit refresh and select the new person and it would then continue working again. This would make re-using UI buttons much more easier and cause less issues.
It also would give you the ability to test a set of buttons/options on another model quickly.
Another big use case for this would be for a scene like Get Her Pregnant. I have a set of buttons for Girl 1, and then the same exact set of buttons for Girl 2. Instead I could have a toggle button that changes the router to go to the other girl. I could then remove an entire row of buttons in the UI and instead just use the router toggle button with one row.
This could then cut the number of buttons needed/used in half for that section. A scene that has a need for possibly 40 buttons could then have 20 with a router for example. Or it could be the difference between someone even giving that option in their UI because they don't want to create another 20 buttons or don't have the space for them or want to mess with show/hide toggles and that many atoms in their project.
Does anything like this exist? If not it might be a plugin idea to consider.
Last edited: