Elesbaan70

> the new data after serialization will be 100% incompatible with previous version of the mod because of how binary serialization work - _chunk of bytes, requires a class which...

@aubergine10 The "Settings" label is incorrect for this. It should be labeled "serialization" and "lifecycle". I would fix it, but I don't have any permissions here. :-)

> I think it won't make much of a difference if we convert JSON string as binary array or do similar with Bson. Whatever we select it need to end...

After all this discussion, it turns out that we will have to go with XML anyway. The Unity port of Newtonsoft.Json doesn't really work, and it hasn't been maintained in...

Linq to XML is a DOM, not a serializer. I haven't look at it in a while, so I'll take a fresh look, but working with a DOM basically means...

> If I recall properly lists are a pain to work with. I guess I don't have context for that, because I'm not sure what you're referring to. > doing...

Yes, that's one of the annoying limitations I mentioned in `System.Xml.Serialization` is that dictionaries are not supported. Another is that it's hard to make enums backward-compatible. After sleeping on it,...

If anyone wants to follow the progress in code, it is here: https://github.com/Elesbaan70/TMPE/tree/xml-persistence

As I've mentioned before (maybe elsewhere, since I don't see it here), the ideal persistable architecture involves having a set of semi-stable data objects that are maintained by the application,...

I am removing the compression task since this apparently causes issues on some Linux distros. But we really should come back to it later, because the size of the DOM...