Backwards compatibility and ES3Type
Posted: Thu Jul 04, 2019 1:34 pm
Hello guys,
I finally took my time but i also moved to ES3 (we did implement ES2 saves in our game a couple of years ago - and we were very happy with it, then we had to put the save system in standby as too many things were being refactored and changed). I did read in a few places, that backwards compatibility is automatically managed by ES3, and that it's not necessary to create ES3Type files anymore.
Did I understand correctly? If so, can I save a serializable class in "classic" way without any additional file or that's only for simpler unity types? Also, is there any detail on how backwards compatibility works? (i would love to make sure before having to run a lot of tests and/or releasing)
Thanks in advance for your time,
H
I finally took my time but i also moved to ES3 (we did implement ES2 saves in our game a couple of years ago - and we were very happy with it, then we had to put the save system in standby as too many things were being refactored and changed). I did read in a few places, that backwards compatibility is automatically managed by ES3, and that it's not necessary to create ES3Type files anymore.
Did I understand correctly? If so, can I save a serializable class in "classic" way without any additional file or that's only for simpler unity types? Also, is there any detail on how backwards compatibility works? (i would love to make sure before having to run a lot of tests and/or releasing)
Thanks in advance for your time,
H