Stellaris updates so often that mod authors often don’t bother to update the version number even when that is all that needs to change. So here’s a guide to doing that on your own.
Other Stellaris Guides:
- Beginner’s Guide.
- Quick Tips for Beginners.
- Useful Console Commands (Cheat Codes).
- How to Make a Successful Empire (MegaCorp DLC).
- ID’s for the New Relics (Ancient Relics Story Pack).
- Ship Designer (Fleet Guide).
- Stay on Target Achievement Guide.
- Last, Best Hope Achievement Guide.
So You Have that Little Icon
All credit goes to Gavril!
Stellaris updates so often that mod authors often don’t bother to update the version number even when that is all that needs to change. So here’s a guide to doing that on your own. From my experiments, it looks like steam does not actually update mod files unless you unsub or the mod author makes an update of some kind, so you should only need to do this when you unsub or Stellaris or the mod are updated. Remember that mods can be updated fairly often if it’s an active author. The author will likely post a link to another mod and leave that one for legacy or update the version himself when it’s ready. Moving on!
And It’s Annoying
Now, how do you fix this? Start by going to the mod workshop page. The URL for the page has the number steam uses to identify the mod at the end of it. You will need this number.
Now you need to go to:
- C:Usersyour_nameDocumentsParadox InteractiveStellarismod.
In this folder you will find a whole bunch of .mod files. These are really just txt files, so you can open them with any old text editor. Remember that number I had you find? Here is where you need it. ugc_<mod id number>.mod. You need to open the file with the id number of the mod you want to change.
But It’s an Easy Fix
Almost there! Now in the file you just opened, you will find a line that looks like this:
- supported_version = “2.3.1”
All you have to do from here is change the version number to your current version. Whatever that is. To save a bit of time between minor updates, you can replace the patch number (MAJOR.MINOR.PATCH) with an asterisk (*). E.g. 2.3.*
Great guide! I had done this on my own before finding the guide but didn’t think of looking up the mod id. I just opened each file until I found the right one lol.
Only thing I can think to add is a little bit about which kind of mods can be updated without worry. For example this should be no problem for minor graphics, music or ui mods. But it may not work on something more advanced like ai, overhaul and similar scope mods. Doesn’t hurt to try anyway, just except some possibility of breaking the game until you disable the mod and get a proper update.
In all, very helpful information in this guide. Thanks for putting it up!
You are a golden god for this save! Thank you so much! Now I can crush the xeno scum through the power of pray and love!
This piece of advice does work, but there needs to be a warning attached. If you update the mod version in the file, and it turns out the base code of the game has changed so the mod no longer works – or worse, crashes the game – you just wasted your time and caused frustration. Keep that in mind when you’re modding, and realize that you are not a developer – just a player that wants a better gaming experience. Modding is not a panacea, and messing with game files may cause unintended consequences.