TaurusBR
Member
- Oct 7, 2019
- 142
- 141
Thanks for clarifying the problem. Just one question: even if you downgrade from the current version (v1.43) to an old one (v1.42), does it get bugged?Ahh, you're using an older save file
When I load an older save file (1.39 or even 1.42) I get the same error. The one thing you could do is load the game, ignore the errors, create a new save after loading and delete the old one.
Still, it's volen's job to fix this. It's the second time I'm mentioning this but volen didn't aknowledge it at all.
It may have to do withSave.onLoad.add()
(performs any required processing before the save data is loaded—e.g., upgrading out-of-date save data) andConfig.saves.version
(this setting is used to set the version property of saves, to upgrade out-of-date saves via aConfig.saves.onLoad
callback)
![]()
Regards.
Edit:
Oh, shit. Even downgrading, the problem persists.
Now it's time to wait for the dev to fix the problem or start a new game with each update. It's sucks.
Last edited: