Regarding your request, I’m the first one who would like to see an implementation in GDevelop. As you can see here
I’ve already discussed it in the past.
However,
I want to clarify that while it’s true this could be a useful feature, you’d still end up having both systems included in the engine… so I believe Silver is right.
Let me explain: …
even in emulators, the save-state function is secondary.
Emulators allow you to save the game by emulating the console’s native save system… here’s the point… it could happen that a player saves the game in a “death situation” that can’t be avoided… forcing them to restart the entire game from scratch with no alternatives (imagine reaching Bowser in Super Mario NES with a save state and dying there).
If you’ve played (as I believe you have) with emulators, you’ll know that it’s good practice to save normally and use save states only when you’re in a relatively safe situation… that’s exactly what I also said in the thread I opened.
With classic saving, it’s the developer who decides the safest point in the game to save, avoiding unintended behavior. When using save states, you give the player the ability to choose where to save… so it’s not quite as safe.
To wrap up:
I too would like to see this feature in the system… but I wouldn’t use it in the
way you would like.
That’s why you’d still be obliged to use global variables and JSON to save.
There are also some threads on how to save faster without going through the various JSON conversions… I’ve opened some as well… but the system itself definitely wouldn’t change.
edit:You could also say, “Alright, I could have more save-state slots available.”
However,… it would still be a secondary feature, even for emulators.