安装 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(越南语)
Українська(乌克兰语)
报告翻译问题




GL
Sure, I will use that to try to solve my problem.....
And after that I will let you know.....
When you mix up other mods the ones at the top of the list overwrite things lower down the list, so rule of thumb for load order:
Top: Tuning mods meant to alter things globally (like no smoke has to be able to alter buildings added by other mocs, so up it goes. Same for things like Inedible Foods)
Under the tuning mods; your biggest mod or mods package (in order). Big mods are usually pretty stable on their own, with complex production chains. You don't want a random little mod to cime and break anything, so your biggest mod has to be pretty high up.
Under the big mod: Everything else. Small mods that add a few buildings (often "reskins" of vanilla buildings), things like aging speed mods, extra disasters, etc etc, all that can go towards the bottom of the list.