Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
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?