Installera Steam
logga in
|
språk
简体中文 (förenklad kinesiska)
繁體中文 (traditionell kinesiska)
日本語 (japanska)
한국어 (koreanska)
ไทย (thailändska)
Български (bulgariska)
Čeština (tjeckiska)
Dansk (danska)
Deutsch (tyska)
English (engelska)
Español – España (spanska – Spanien)
Español – Latinoamérica (spanska – Latinamerika)
Ελληνικά (grekiska)
Français (franska)
Italiano (italienska)
Bahasa Indonesia (indonesiska)
Magyar (ungerska)
Nederlands (nederländska)
Norsk (norska)
Polski (polska)
Português (portugisiska – Portugal)
Português – Brasil (portugisiska – Brasilien)
Română (rumänska)
Русский (ryska)
Suomi (finska)
Türkçe (turkiska)
Tiếng Việt (vietnamesiska)
Українська (ukrainska)
Rapportera problem med översättningen
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?