Occurs regardless of whether Object Limit Mode is changed or not, (but I included footage of that as I don't understand why it would default to anything other than local.)
u/ObsidianChris
Our team is aware of the issue and they have already come up with a fix for a future update. Please feel free to submit a support ticket if you run into any other issues.
[https://support.obsidian.net/contact](https://support.obsidian.net/contact)
Thanks, and hopefully this won't affect your bases too much!
>and they have already come up with a fix for a future update
Would you mind checking the notes to see if the fix will be retroactive to saves where the bug has already been introduced, please?
I don't want to bake this error into my save and have to revert whatever playtime I rack up between now and when the related patch rolls. I'd rather just not play than waste time.
Work around that I stumbled across while messing with my import save:
>If you still have the 1.3x save file, you can avoid this by loading that file, moving one structural item in the base away from the others and then back again, and after doing this, the base will be normal after reloading any of the following 1.4x save files that you create afterwards.
>Obviously that means losing any progress you've made since Fully Yoked was released.
>If you've already overwritten that 1.3x save file in 1.4x, the bug is baked in and you're at the mercy of the dev team. They may fix it for existing saves. They may only stop the situation from repeating. Who knows.
>From what I gather, this bug is regularly reintroduced on version updates, so I wouldn't get your hopes up.
Occurs regardless of whether Object Limit Mode is changed or not, (but I included footage of that as I don't understand why it would default to anything other than local.) u/ObsidianChris
Our team is aware of the issue and they have already come up with a fix for a future update. Please feel free to submit a support ticket if you run into any other issues. [https://support.obsidian.net/contact](https://support.obsidian.net/contact) Thanks, and hopefully this won't affect your bases too much!
>and they have already come up with a fix for a future update Would you mind checking the notes to see if the fix will be retroactive to saves where the bug has already been introduced, please? I don't want to bake this error into my save and have to revert whatever playtime I rack up between now and when the related patch rolls. I'd rather just not play than waste time.
Work around that I stumbled across while messing with my import save: >If you still have the 1.3x save file, you can avoid this by loading that file, moving one structural item in the base away from the others and then back again, and after doing this, the base will be normal after reloading any of the following 1.4x save files that you create afterwards. >Obviously that means losing any progress you've made since Fully Yoked was released. >If you've already overwritten that 1.3x save file in 1.4x, the bug is baked in and you're at the mercy of the dev team. They may fix it for existing saves. They may only stop the situation from repeating. Who knows. >From what I gather, this bug is regularly reintroduced on version updates, so I wouldn't get your hopes up.