Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I'm so ♥♥♥♥♥♥♥♥ sick of this bull S.
If your savegame is 1.3, just downgrade it...
Too late now. You can do that to keep your save going but you must not load it with the new version. It´s now corrupted and can´t be fixed. Won´t work with V1.3 either.
Actually, yes, you can prevent updates.
If you set the game to a specific version (via Betas in Steam), it will stay locked to that version and won't auto-update. The only time it updates automatically is when you leave it set to the latest public version or None. I know this works because I use it to test mods on my private servers all the time. So, for example, if your game is modded for v1.3, then in the Betas drop down, select v1.3 Stable.
That said, it's always wise to back up your saves and generated worlds. I use Windows Task Scheduler to run automatic backups of my dedicated server games for Valheim, V-Rising, Minecraft Paper, Enshrouded, and 7DTD every night at midnight, and I also have it delete anything older than 30 days. It’s a simple setup that’s saved me more than once.
I get the frustration - it sucks when updates break things. But honestly, with a bit of prep, you can avoid 90% of this headache. If you're modding or hosting, due diligence is part of the game.
As for your issue, the resolution could possibly simply be that your mods need to be updated to match the current game version.
You can, but you don't need to. I currently have 15 installs of the game, with versions from A19, A20, A21 and 1.x, including latest stable. Oh, and one A16. The only issue is having to clear the registry when switching alphas. No, I don't play all those, I keep them for testing things, or can't be bothered to delete them.
V1.4 is the current stable version since the 11th April. So nope, that´s not it.
Good catch on that Seven.
In case other people reading our posts might not know - the game folder can be duplicated and it will still run on its own - frozen to the version of that original installation. This works well if people want to play an up-to-date game attached to Steam, and an overhaul one that's detached from Steam.
With the changes in mod location in A20, and the UserDataFolder launch or startup option, it is really easy to set up multiple versions, and multiple mod installs, all using their own mod and save folders. I didn't see any updated guides with a quick look but it's a topic that comes up often. I've answered with brief instructions on how it can be done in the past but it would be great if someone who is good at writing clearly would author one.
I took your hint and created the guide: https://steamcommunity.com/sharedfiles/filedetails/?id=3469283915
- You've broken the save before the new update.
- The new update IRREVERSIBLY screwed up your save.
If you actually care about your saves, you need to follow those steps/rules:
- NEVER launch your older saves on newer versions of the game, especially when you have mods installed.
- Backup your saves, just in case. Blackout is still a thing, and it still can destroy your save.
- There are ways to "save your save". But the moment you try to launch that save without doing those steps - your save is completely screwed. AND you need to know if your save is possibly ruined BEFORE you launch it. Every time the game is overwriting your game save with newer data, it saves everything as *.bck files, so you can remove the non-bck files, and rename the bck files back. This way, your save will be restored. But that will only work, if you did that before the game had a chance to overwrite the *.bck files with the broken data.