安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
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?