Report this content

We want the Dreams coMmunity to be a safe, diverse and tolerant place for everyone, no matter their age, gender, race, sexual orientation or otherwise. If you believe this content to contradict these principles, you can file a report for our coMmunity teams to investigate.

Note that misuse of the reporting tool will not be tolerated.

Item being reported:

Of your two suggestions for managing situations where the persistent variable limit is exceeded, I prefer this one. The creators choice of variable to delete is always going to be more accurate than simply choosing the one that hasn't been written for longest.

To give creators even more control over this, perhaps the Variable gadget could also have a "Loaded" output that would emit a pulse at the start of the scene if and only if there was a saved value to load. This would allow creators to manage situations where for example, there are three versions of a game with different formats for saved data in the variables, and migrating data to version 3 requires different logic depending on whether the current version is version 1 or version 2.

And if the creator puts all of this logic in a scene that doesn't do anything else and sends players on a detour to that scene when resuming the game, the extra thermo used won't be a problem. This would work something like this:

Player resumes game and the last scene they were in loads.
"Version Check Needed" variable doesn't load a value.
Absence of "loaded" pulse from "Version Check Needed" variable triggers logic that sends player to "Version Check" scene.
"Version Check" scene loads.
"Version Check" scene migrates data if needed.
"Version Check" scene writes a persistent value to "Version Check Needed" variable.
"Version Check" scene sends player back to scene they came from.
This time, that scene's "Version Check Needed" variable does load a value.
Detour to "Version Check" scene logic doesn't get triggered.
Scene uses "delete" input of "Version Check Needed" variable to delete its value, because we want to do all of this again if the player exits the dream.
At the next regular scene transition, the value of the "Version Check Needed" variable is written to the save file.
The next scene finds that value, and doesn't repeat all of the version check detour logic - which we don't need to do in this case, because the player didn't reach the start of the scene by quitting and resuming later.