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

Save game compatibility between releases #66

Open
Trilarion opened this issue Aug 23, 2018 · 0 comments
Open

Save game compatibility between releases #66

Trilarion opened this issue Aug 23, 2018 · 0 comments
Labels
discussion General discussions programming Strongly related to programming

Comments

@Trilarion
Copy link
Owner

This is obviously an important problem with no simple solution. The data is stored as serialized json format but translates directly to Java objects (we use gson). This means that properties that aren't needed anymore will be ignored; properties that are new in newer versions of releases, however, may be problematic. And if the whole structure changes, there is a problem anyway. Updaters/importers will be necessary for major changes. These updaters/importers may even need to be chained. In any case the version number (that is stored in Version.java) should always be included and act as a save game version.

This was partly discussed already in #21 and the problem applies to save games as well as scenarios.

Let's see how much of a hassle this will be.

@Trilarion Trilarion added discussion General discussions programming Strongly related to programming labels Aug 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion General discussions programming Strongly related to programming
Projects
None yet
Development

No branches or pull requests

1 participant