Closed JMPZ11 closed 6 months ago
I was able to get around this by using the custom export type,"Spriggit.Yaml.Starfield" as package name, "0.18.0" as version.
the case has to match or you get a strange error
Update: yaml to esm doesn't work at all if the custom provider is used (or non-latest version is selected) - in both 0.18 and 0.19 codebase, however both versions can read the yaml correctly with no special options applied. so, looks like I cna use 0.19, but will need two separate entries (since the 0.19 starfield model is nerfed)
Opening Spriggit v0.18.0+5a68a8cad
Until spriggit stabilizes on 1.0, I'd recommend updating the UI/CLI exe itself to the newest versions when possible. See if it does better. Still a few improvements to be made so that the UI/CLI doesn't need to be so aggressively updated on every release
Once I figure out how to get it to build I should be able to stop bugging you so much - VS2022 gives one error, vscode gives a different one altogether lol.
Upgraded to spriggit 0.19.0 UI and changed to use 0.18.0 model; problems solved. Thanks!
FYI - 0.19.0 is now working fine with the latest model. Thanks!
hmm gotten this same issue but for 0.24 any help would be great
Two days ago everthing was fine, and today I can't serializing anything with the same error: System.ArgumentException: Object of type 'Mutagen.Bethesda.Plugins.ModPath' cannot be converted to type 'Mutagen.Bethesda.Plugins.ModPath'.
Looking at the logs, it seems it is pulling a nuget package at runtime (doesn't sound typical) with mismatched version numbers - could that be the cause? I see no configuration option in the json or xml I could use to fix this... so I'm kinda blocked at the moment.