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
Steam is a fickle mistress for some users apparently, without a rhyme or reason near as anybody can tell.
For anyone else running into this, it looks like it's downloading them loose into the directory where cloudsaves are normally cached.
------------------------------------------------------
Where the mod packages ended up:
steam/userdata/##usernumber##/
Correct directory structure for files in this folder should be:
steam/usderdate/#usernumber/#steamappID#/remote (or local)/*stuff goes here*
Even if it hadn't screwed up the directory structure, that would be an odd place to put workshop content. I don't think I've ever downloaded workshop mods that didn't use the workshop/content directories as the depot/staging folders like:
*/steam/steamapps/workshop/content/##steamapp ID##/
So it looks like it's doubly screwing up - like if you tried installing skyrim mods by putting them in your bare documents/mygames/ folder (so not only aiming for the wrong place but also missing it). Or maybe that was a very very old way of staging workshop mods and they've never updated it?