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




When mods are installed in Documents, there is a fixed loading order. If there are multiple versions of the same file, the last one loaded is used, so hak > patch hak > override > base game.
Only those haks specified in the module properties list are loaded, bottom to top.
By "file", I mean individual game files, like scripts, models and textures, which may be held in containers like .hak and .bif files, or in the override folder.
I'm less clear what happens with Steam Workshop Items. They have the same folder structure as Documents. At run time, in effect, the folders are merged with the corresponding folders in Documents, but I'm not yet sure which takes priority, or whether conflict management is at file or container level.
Evidently, certain folders, such as override, must be aggregated across all subscribed Items and Documents (otherwise that type of mod wouldn't affect all modules globally).
However, I'm less sure whether that's true of, say, the hak folder, which in principle only needs to be aggregated from the Module Item, Required Items and Documents.
Maybe Beamdog can cast some light.
Bottom line - although there has been no official comment on this, the conventional wisdom in the community is that everything works a lot better if files are moved from the Steam folders to Documents.