Now, this may be too much to ask for, but occasionally, I find myself using too many “Save” behaviors just for things that don’t need that much attention, but are important for the completion of the game. Maybe we should have two new behaviors called Save State and Load State.
Games Can have Up to 3 of each at a time.
Save States have a single property- the name. Every object in every level is saved exactly like it is,
Once a State has been named and saved, A Load State can be used, and has the same “name” property. When triggered, the game restarts- BUT goes back to like it was when the game was saved.
In other words- a behavior that Saves the game as a whole, not just an integer...