MBObjectBase / Generic Saveable Class

[brandonm4]

What about a generic save structure, so we don't have to come up with unique saveable classids for our MBObjectBase objects?

Something like:

[SaveableClass(5001000)]
GenericSaveData : MBObjectBase
{
 [SaveableProperty(100)]
 public string ModuleId {get;set;}  //same as the SubModule module id
 [SaveableProperty(200)]
 public string ModuleReference {get;set;}  //reference for the module to know what type of data is here
 [SaveableProperty(300)]
public string JsonData {get;set;}
}

This way we could serialize/deserialize our data objects without stepping on other modules toes / data object by accidentally using the same SaveableClass id.

Or is this not even a potential problem?

[sirdoombox]

It seems like currently there's a bug somewhere in Taleworlds save system that makes this a bit of a risky proposition. I'm considering something for this but right now I'm not 100% what the right way to go about it is to prevent bricking saves.