Closed JMPZ11 closed 6 months ago
Yeah, there's two phases to a deserialization: 1) Finding the target package that the spriggit files used when they were made (TryGetMetaInfo) 2) Once the version is known, downloading that package and doing the deserialization with it
Right now, though, even if you're running the v18 UI/CLI, it downloads the latest (v19) logic to do step number 1. If there's significant changes, this might not do the job.
It happens on both UI version - I think my description wasn't clear.
At least with Starfield, if the custom version field is populated at all, deserialization fails, as it uses the Skyrim translator. In UI 0.18.0 it happens when the custom option is selected, and it seemed to occur even if you had disabled the custom option but had not cleared the values first.
I should be able to get some steps to reproduce - I haven't been able to write out any 0.19.0 files so I don't know if the file version has an impact.
Let me know if you need anything to help reproduce. I really am just trying to help!
Ok, this isn't happenning in the new version anymore - no clue what was wrong but probably related to sleep. Closing.
I was able to export using Spriggit.Yaml.Starfield and 0.18.0 as the custom provider, but the import back to esm is using skyrim