安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
!!_preytons_sfo_nrke.pack:
Patch 3.0: Vanilla attributes renamed in main_units_tables.
1-blablamod
2-anothermod
3-a main mod
4- a submod for the main mod
they said because the lower you are the more you decide on the final change, like they "knda" overrule the ones that come before
Good question, see the overrides win from top to bottom, meaning the higher something is loaded the higher priority it has.
Most mod authors will name their files such that if it is a submod or something it will load up higher. I am not sure why they would say it would have to be loaded after, maybe they know something I don't, but I test it with them loaded before and it works lol.
A simple solution would be to just use this mod manager available here in the workshop, it will auto sort for you based on naming conventions:
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2845454582&searchtext=mod+manager