安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
Then I considered uploading it as its own addon but the file size was too big without having to divide the pack into 3 parts. Which I was initially trying to avoid. I might rebuild this and do that.
I'll probably get around to building a collection and linking it here also and letting users decide which method they want to choose is easier for them.
Then as they subscribe to more mods over time,they may have to
update their mod load order.
Personally I usually just extract mods out of their vpks,delete whatever
stuff could be conflicting and create "manually installed" mods.
I guess that's the price to pay for having easy to subscribe-install mods
on the workshop:because we can't directly affect the vpk contents we
may have to fix things the hard way.
instead of doing this?
Collections are literally made for this,and allow people for easier/better
control over the addons they may want to subscribe or not.
Doing this forces people to manually check each entries,wich may not
be very different than browsing the workshop randomly and find the
occasionally missed good stuff.
Well these are my two cents anyway.