A good way to make save games that doesn't have version portability probs

There is something in the standard Java API to do exactly what you want, the catch is that it’s for Java Beans style class. Take a look at the java.beans.XMLEncoder. One of the things it was designed to solve is the version problem with serialized Swing objects but it’s also got some other cool stuff.

Serialization invokes the default constructor to create the object. As long as you einitialize the field in either its declaration or the default constructor, then yes by definition its handled.

Okay, well then maybe I’ll just stick with keeping the same UID like you mentioned in the first place. ::slight_smile: