Hi,
Could you provide any information about best practice to avoid breaking save games when making changes to data saved, as a result of changes made to the game? It happened a few times on my last game (which used ES2) I think as a result of changing the data saved in types. I'm not using any of the autosave functions, but rather have defined types to store the data and am manually saving the data.
Thanks!
Avoiding Breaking Save Games
Re: Avoiding Breaking Save Games
Hi there,
Unlike Easy Save 2, Easy Save 3 is more adaptable to changes. If it finds a field which no longer exists then it will skip it.
If you change the name of a field, but want the old save data to still be saved, you can do this by creating an ES3Type for it and modifying it to use your old field name rather than your new one.
If the data type changes then you can modify the ES3Type to load using the old data type, and then convert this to the new data type.
All the best,
Joel
Unlike Easy Save 2, Easy Save 3 is more adaptable to changes. If it finds a field which no longer exists then it will skip it.
If you change the name of a field, but want the old save data to still be saved, you can do this by creating an ES3Type for it and modifying it to use your old field name rather than your new one.
If the data type changes then you can modify the ES3Type to load using the old data type, and then convert this to the new data type.
All the best,
Joel