It is worth to point out that Skyrim Workshop in Steam is still having problems. Mod subscription data is still disappearing from the game, as it has done almost trough the spring and summer 2015. Our support thread in Steam Skyrim Discussions was started as 22 March, when problem had already been going on for a while. No solid solution has been found to this date.
Bethesda updated their Creation Kit and Workshop support to following changes.
– Size cap for the mods was lifted. Skyrim Workshop can now manage larger files than before.
– Managing of Workshop mods was changed from Skyrm launcher to Steam.
– CK now supports master files (.ESM) and they can now be uploaded to Workshop.
At the same time, Valve and Bethesda were planning on staring curated Workshop, bringing paid mods for Skyrim to Steam. As we know, this experiment was short lived, due to several reasons. For technical point of view, the Workshop was not considered as a proper platform for paid mods. The ongoing problem with subscriptions contributed to this, because how Skyrim manages script data.
What is the problem?
Skyrim Workshop looses data about mod subscriptions. You may have properly subscribed to a mod, but not able to get any data from it to your game. As if Worksop would remember that user has subscribed to a mod, but is unable to locate and provide data to the game itself.
Subscription doe not need to be a new one. This problem can appear with old mods that user has been subscribed to a long time, or it may be a completely new mod that user has just subscribed to. So far problem does not seem to be related to which version of CK were used when creating the mod, or even when it was uploaded to Skryim Workshop.
Problem is not persistent to all users, but may become persistent for any user experiencing it. It is especially troubling, because Skyrim stores script data to character save files and this data can not be properly cleaned away from them. Community has tools to help the problem, but none of the solutions can make save 100% clean. More importantly, if bugged file acts as a master file for other mods, then you will experience persistent Crashing after Bethesda screen, leading saves for that character to become permanently unplayable.
What can you try?
We do not have any solid solution for this. The most helpful process seems to be the following, although it may not always work.
- Favorite your mods, so you can easily find them later on.
- Unsubscribe from all mods causing trouble.
- Open the Data Files view from your default launcher and delete all mods that you have just unsubscribed from.
- Close your computer. Let it shut down, before starting it again (Not required, but recommended.)
- Use your Favorites list to subscribe mods you had previously unsubscribed from.
And as always: run LOOT to sort your load order. It does not matter what platform you used to mod your game. Game itself does not know where your mods came from.
More recommendations and discussion about this problem can be found from our support thread linked above.
Problem remains unsolved, until Valve and/or Bethesda takes steps to fix it. So far this has not happened. My recommendation is to avoid all scripted mods from Steam Skyrim Workshop for now. Rely on locally stored mods instead, like ones installed from Skyrim Nexus.
I also hope that problem with the Workshop does not scare away potential new players. We have plenty of peoples helping you to mod and fix your games in Steam Skyrim Discussions, Skyrim Nexus and other sites devoted to mod and troubleshoot your games. You can also check out our New player Spreadsheet aimed to help new players to get familiar with Skyrim and mod the game.