Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite Save Data Management #4

Open
doczi-dominik opened this issue Mar 7, 2022 · 0 comments
Open

Rewrite Save Data Management #4

doczi-dominik opened this issue Mar 7, 2022 · 0 comments

Comments

@doczi-dominik
Copy link
Owner

Relying on the intricacies of the Haxe Serializer turned out to be insufficient for this use-case. To ensure the most compatibility between updates, GelaVolt should use a simple, custom serializing format that only stores data that is different from the default, i.e. overrides.

Another nice addition would be a save data versioning system and a migration pipeline. If the current save is v5 and GelaVolt loads a v2, it should be able to migrate v2 -> v3 -> v4 -> v5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant