Proof of Concept: SaveComponent #21
Open
+1,205
−0
Conversation
This file contains hidden or 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
Member
|
I'm away from home for a while. Will take a look later! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR builds on the discussion in #17 and explores a possible mechanism for saving game data.
This is an initial proof of concept, shared for discussion and feedback only (not intended for merging).
To try it out, set the main scene to:
Lab/SaveComponent/SaveTest/SaveTestStartThe simple demo shows how properties, components, and component properties could be persisted in
GameState.I've added documentation in
Lab/SaveComponent/README.mdthat describes everything in more detail.(Disclosure: GenAI helped with the documentation).