tldr: make a "new" mod with the official modding tools and copy the data of the mod you want to keep un-updated into the "new" mod's folder. This process (and strong advice to do so with any substantial mod) should be documented on the wiki in the modding section to prevent... dissatisfaction.
So, I just had a save destroyed by Steam automatically updating mods. I'd expect this to be an ongoing problem particularly while the game is quite new and mods are frequently updated. As Steam appears to have no way to disable automatic mod updating (barring cutting yourself off from the cloud for everything on Steam), I figured the only real way forward was to save a backup copy of the mods I use locally so that their contents remain fixed unless I perform an update myself.
Finding out exactly how to do this was not at all obvious to me and took a thoroughly irritating half hour to work out. My initial plan was simply to make a copy of the mods from the steam folder, move the copy into the local mod installation folder and then change the "ModName.mod" and "descriptor.mod" files to have the correct directory location etc. in them. This failed utterly with the game not recognising the presence of the mods at all.
After a whole lot of fruitless google-ing and reading of the wiki I finally had the idea that worked: go viking and make like you're going to steal some $#*&! Fitting in a way as in the lost save I was playing as Sweden in 867...
Anyhow, all it needed was to make a fresh mod with the modding tools then copy the contents (except the "descriptor.mod" file) of the mod into the "new" mod's folder. For every single mod. It's definitely a bit clumsy, but at least it works and can preserve saves from being rendered unusable by mod updates. One major potential issue with it though is that every time you make a "new" mod the game asks you to publish it... so if lots of people do this, I can see many, many, many versions of popular mods popping up on the workshop and ParadoxMods as people accidentally publish their backup copy. So I'd add a "do not publish" button to that screen that's more obvious
So my request: please please please add this method to the modding section of the wiki (or somewhere else really prominent) to reduce the number of people who go through this enraging process. Having a save rendered unplayable by a mod update is very annoying, so I'd honestly recommend this to EVERYONE who mods the game.
Maybe my brain's just gone stupid from the covid lockdown, but it wasn't immediately obvious to me how to do it.
So, I just had a save destroyed by Steam automatically updating mods. I'd expect this to be an ongoing problem particularly while the game is quite new and mods are frequently updated. As Steam appears to have no way to disable automatic mod updating (barring cutting yourself off from the cloud for everything on Steam), I figured the only real way forward was to save a backup copy of the mods I use locally so that their contents remain fixed unless I perform an update myself.
Finding out exactly how to do this was not at all obvious to me and took a thoroughly irritating half hour to work out. My initial plan was simply to make a copy of the mods from the steam folder, move the copy into the local mod installation folder and then change the "ModName.mod" and "descriptor.mod" files to have the correct directory location etc. in them. This failed utterly with the game not recognising the presence of the mods at all.
After a whole lot of fruitless google-ing and reading of the wiki I finally had the idea that worked: go viking and make like you're going to steal some $#*&! Fitting in a way as in the lost save I was playing as Sweden in 867...
Anyhow, all it needed was to make a fresh mod with the modding tools then copy the contents (except the "descriptor.mod" file) of the mod into the "new" mod's folder. For every single mod. It's definitely a bit clumsy, but at least it works and can preserve saves from being rendered unusable by mod updates. One major potential issue with it though is that every time you make a "new" mod the game asks you to publish it... so if lots of people do this, I can see many, many, many versions of popular mods popping up on the workshop and ParadoxMods as people accidentally publish their backup copy. So I'd add a "do not publish" button to that screen that's more obvious
So my request: please please please add this method to the modding section of the wiki (or somewhere else really prominent) to reduce the number of people who go through this enraging process. Having a save rendered unplayable by a mod update is very annoying, so I'd honestly recommend this to EVERYONE who mods the game.
Maybe my brain's just gone stupid from the covid lockdown, but it wasn't immediately obvious to me how to do it.
- 1
- 1
Upvote
0