When you 'Save as', you are making a copy of the currently active scenario and making it active. Do the 'Save as' first, them make the changes. Only the active scenario will acquire those changes (Greenfoot updates the files of the currently active scenario as the changes are being made, so you do not have to tell it to 'Save').

Thanks for the reply. I think I also just have general issues with saving changes. If I create a new scenario and add classes, save the changes, then when I reopen the file those changes are still there. However, if I instantiate the classes and place say two objects from the class in the world window, and try to save the scenario like that (no additional save as copies this time), then when I reopen the file, the instances are gone from the world window. I was following the tutorials and found out something was off when I couldn't keep the changes from moving the rocks around.

I guess I should have specified -- changes in your code are saved as you make them. If you manually add actors into your world and want to save them, you need to 'Save the World' (from the menubar, 'Controls>Save the World'). After doing this, your world subclass will gain a 'prepare' method with the code for your manual actions and a call to it from the constructor of that world (this code change is saved automatically).

Great! Thanks for the clear explanation in your reply. This makes perfect sense now! Cheers -Edit: Also, the info here really creates that confusion: https://academy.oracle.com/self-study/greenfoot/greenfoot_2_6.html