Save states I guess #370
Merged
Save states I guess #370
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Estebanfer just dropped this feature in the Discord, I only added API, UI and some checks...
save_state(slot)Save current level state to slot 1..4load_state(slot)Load saved slotStateMemory* get_save_state(slot)1..5I believe these state copies are invalid after unloading the current level (at least loading from next level just crashed a lot), but not cleared, so I added a thing to invalidate them on level unload. Death screen is automatically cleared if loading from UI, but I'm not even sure if that's already messing with fate too much, or should it be part of the api too...