Home Trending Latest threads New posts Developer diaries

Supported Version no longer updating?

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Stellaris 54260 Bug Reports 37676 Console edition 1313 Suggestions 21785 Tech Support 3219 Multiplayer 392 User Mods 4795 Stellaris AAR (After Action Reports)
Pants_Doe

Pants_Doe

Private
24 Badges
May 16, 2016
23
12
  • Crusader Kings II
  • Stellaris: Synthetic Dawn
  • Stellaris
  • Cities in Motion 2
  • Magicka
  • Crusader Kings II: Sword of Islam
  • Crusader Kings II: Sunset Invasion
  • Crusader Kings II: Sons of Abraham
  • Crusader Kings II: The Republic
  • Crusader Kings II: Rajas of India
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: Legacy of Rome
  • Crusader Kings II: Charlemagne
  • Stellaris: Apocalypse
  • Stellaris: Humanoids Species Pack
  • Stellaris: Distant Stars
  • Stellaris - Path to Destruction bundle
  • Stellaris: Leviathans Story Pack
  • Stellaris: Digital Anniversary Edition
  • Stellaris: Galaxy Edition
  • Stellaris: Galaxy Edition
  • Cities: Skylines - Snowfall
  • Cities: Skylines - After Dark
  • Cities: Skylines
I've kept my various mods up to date as new releases come out by opening the .mod file and manually changing the version number. It shows as correct to me when I launch Stellaris. However, when uploading to Steam, all of my mods still show as only supporting 1.2.1 and everyone is getting warnings about them, even though their files look correct. I've tried 1.2.3 and 1.2.*, and neither are showing as "supported" when people attempt to use them.

What can I do to fix this problem?
 
  • 1
Reactions:
Users are reporting that their descriptor.mod file in the .zip shows as supporting 1.2.* as well. Everything about the mod on my local system and in the .zip file it creates seems to be created and uploaded correctly.
 
It's a user problem. There is something going on with how Steam (or Paradox?) has chosen to update the mod files and where they get stored, I've fixed it on my end, but other users are reporting it doesn't work for them. See this thread.
 
  • 1
Reactions:
we have lots of reports of users who cannot auto-update our mod on steam (me included)
I have read that the default save location of mods was changed with the last patch from /Documents Folder into the steamworkshop root directory. somehow steam doesnt instantly delete the old mod files when one unsubscribes, so the only way we got it working again is to manually delete it.

Quote from our steam description
"There seem to be some issues with steam updating our mod.
The following Instructions will make 100% sure that you get the newest update:
Unsubscribe
Delete local newhorizons.zip in *\Documents\Paradox Interactive\Stellaris\workshop\content\281990\688086068
Delete local newhorizons.zip in \Program Files (x86)\Steam\SteamApps\workshop\content\281990\688086068
Resubscribe
Enjoy "

Unfortunately it seems that nearly all of our subscribers have to go through this workaround to get it working again, it is particularly annoying because the size of our mod is 1.7gb.
Would be great if you guys can find a way to fix this issue.
 
  • 1
Reactions:
You must log in or register to reply here.
Top Bottom
Back