You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 7, 2018. It is now read-only.
I'm a novice, so please bear with me if I've gotten anything wrong.
It seems that if I want to automatically save, you need to call game:save() after every event. For example, every item script may need to say game:save() within on_variant_changed so that each time I pick up an item the game saves.
I'm wondering if instead, Solarus can build this trigger into the relevant places and provide a configuration variable like game.set_autosave(boolean) which can be passed in to make the game automatically save any time the save data changes.
The text was updated successfully, but these errors were encountered:
I don't know if there will be such a variable, but i can give you a useful tip : using the metatable or the multi-event script, you can automate this operation in a one-time process.
If you want help about how to implement, you can open a thread on the Solarus Forums
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm a novice, so please bear with me if I've gotten anything wrong.
It seems that if I want to automatically save, you need to call
game:save()
after every event. For example, every item script may need to saygame:save()
withinon_variant_changed
so that each time I pick up an item the game saves.I'm wondering if instead, Solarus can build this trigger into the relevant places and provide a configuration variable like
game.set_autosave(boolean)
which can be passed in to make the game automatically save any time the save data changes.The text was updated successfully, but these errors were encountered: