Let’s say every line itself works as expected. One issue is that in line 18, you check if “con” is your background. However, the condition that this is even executed is that “img” is the background (line 14). So the condition in line 18 can never be true. A more general thing: Every act cycle, you create a new StartButton (line 10) including an entire new MyWorld and a ControlButton. If “img” is your background, you add both to the world – every act cycle a new one. The act method should contain those things which need to be checked every act cycle. So in your case, if the BackToMenu button is pressed. Adding it (and everything else) to the world should only happen one single time, so it belongs in the constructor, not the act method.

First thing is that the initial world building code should go in the constructor of the class. Any changes from that can be determined later depending on user actions through the act method. You need to keep in mind that it will take many act steps just waiting for a button to be clicked. Therefore, you cannot program the entire thing as simply as you have tried (or, in a single block of code). In fact, you said: Is line 25 supposed to be with "y" also, instead of "k"? Either way, both y and k are created before and during the same act step as this check for the click on one of those objects. There is no way these can be clicked on if they were just created and not added into the world. Even if you add them into the world, they would need to exist there for multiple act steps before the user could possibly click on them (meaning you need to leave this act step to get that chance and pick up the click on a subsequent act step. But, again, you would be creating new objects and check on them instead of the ones already in the world. Adding fields to hold the buttons can assist in checking on any clicks on them. You could add a field to track what is going on at that time. If it helps, you could even give names to the different states as far as what is going on. That would be something along these lines (just a skeleton):

Thank you so much when I saw this code I was very confused on what it meant (this is only my 2nd year of java in school), but after I tried it and looked through what each thing did I started to understand. The only issue I am having is the GAME_PLAY screen mostly because the actual game is in a separate subclass of World. I tried making it so when the mode is set equal to GAME_PLAY it sets the world to MyWorld() which does work, but for some reason no matter what button I press the screen only changes to the control menu. I did check the size of the images to check if it was just overlapping and it wasn't that and I also just to double check if there was overlap I moved the buttons to opposite sides of the screen but it still did not work. After that I removed the button meant to swap to the control screen and then checked if Start even worked and it swapped to the control screen so I // the line what set mode to CONTROLS and then it worked, but I cant seem to be able to have both work at the same time.

Then, remove the field GAME_PLAY and all cases in switch blocks that referred to GAME_PLAY. Afterwards, if issue persist (which I believe it will), provide the entire class coding for review (starting at line 1 in your editor). Explain exactly what is happening and how you want it improved.

I removed all cases of GAME_PLAY and now I am having the opposite issue where both buttons swap to the game and no longer swaps to controls. For how I want to to be improved I just need it where when the start button is pressed it swaps to MyWorld() and when ControlButton gets pressed it swaps to the control screen background and spawns the BackToMenu button.

The (same) problem is with lines 47, 49 and 54. They do not retain the objects in the fields provided on line 8. The values for those fields remains null and the checks for clicks will fail on these, or, at least, not work as you intended. To retain the buttons in the fields, you must not create a new variable (which those lines do). Look back at what I gave to see how they get retained. Also, note that the field names I gave are not (at least case-wise) the same as the class name. This helps for readability of your code (letting you know it is a variable name, not a class name).