Can anyone be more elaborate about how the Load/Save feature works?

I recently released a daily word game (worddad.com) but I'm having some strange bugs related to the Load/Save feature. It then occurred to me that I'm very confused about how this feature actually *works*.

- During the game I do a Save every time players move a letter tile

- I also do a separate save of the current date

- At the start of the game I compare the current date to the saved date. If they are the same then I do a Load. (If a Load exists.)

When the game loads is it loading *everything*, including the game's code? I feel like I can make a change to the game's code but I don't see it because I'm using a Load from before I made the change. But I'm pretty sure that I've had the exact opposite happen, too. I make a change, launch the game which Loads a version from earlier in the day. But the code change shows up.

Confused.

So what exactly is getting Saved?

Save/load is only really suitable for quick tests, in my opinion. It’s kind of like save states in emulators. Much better to use local storage and store a dictionary with whatever variables you need, and then load it on startup, and go to and populate whatever layout you need from there. This is more in line with how most games save their data.

Save action saves the state of all objects on the layout, all variables etc. It doesn't save the game code.

You can exclude some objects (for example static backgrounds, UI elements) from saving by adding NoSave behavior to them.

If you make big changes to your game, saves made in old versions may become incompatible with the new version. If you load such save, the game may not function correctly.

For a word game saving everything is probably not a good idea. I would suggest using LocalStorage to save player's progress only.