Improve saving system error handling
thecodewarrior opened this issue ยท 2 comments
Add class and field name to SerializeObject error stacktraces, as well as logging the data being deserialized (not when serializing because deserialization is more prone to having hard to find errors plus in order to log when serializing we'd have to serialize... and obviously we can't do that.)
Specifically (in serializeobject) add a try catch around field sterilization to wrap the exception with the originating field name.
In AbstractSaveHandler add a try catch to log the nbt as well.
Possibly create a separate log file for packet issues so that we don't spam? e.g. in AbstractSaveHandler catch any exceptions and log them in full, then throw a simplified error with just an error name and the type being serialized.