Ok, I am lost. I am using some simple button logic as shown below
The beginning of the game menu looks like this
You would think when I press the “Play Game” button, the buttons would be replaced with the mode selection buttons right? WRONG! You get this instead
Keep in mind, there is NO other logic that is interacting with said logic whatsoever to cause this problem. So my question to you is this, HOW THE FLYING GLITCH IS THIS POSSIBLE?! I’m getting fed up with all the bugs I keep finding, I just want to finish ONE project without issue. I’m at my wit’s end here
What and where are the new buttons supposed to be and go?
Are the other buttons underneath the other buttons?
If you’re expecting all 3 buttons to move off screen when any of the buttons are pressed, then the issue is the OR condition evaluates all conditions. If only 1 button is pressed then that object is picked but the other 2 are not picked. So, there aren’t any instances to move off screen for the buttons that aren’t clicked. You would need to use the pick all condition or action to pick the other buttons.
You could create a group for those 3 buttons.
Group is pressed
… Pick all objects in group
… Move group off screen
NVM, Apparently the logic works when I PURPOSEFULLY unoptimize it by doing repeat logic for every button press. Though I feel like this is a bad habit though lol. But it works
You’ve got the menu mode var so it looks like you could you that to separate the logic and just hide the buttons or create the mode buttons from an external layout when menu mode is 2. im nit picking a bit but …It’s better to have a trigger once with a wait triggered by button press or a boolean called ‘showwarning’
agreed with petlimpet.
it is objectively better to show which button is visible according to the menu_mode, instead of according to which button got pressed.
buttons change menu_mode. then menu mode changes buttons opacity (or positions in this case).
extras button, option button and play button should only have a single action (set the right mode).
Even better than moving the buttons… move the camera 
Then you can set up all the menus visually and just slide the camera around to change menu. Do this all on a separate layer, now you can show/hide the entire layer to open or close the menu (and have the game visible in background if you want)
Optimize? That’s for things that happen many times per tic and take a lot of processing power. You probably don’t have to worry about the menu…
