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










REGULAR_BLADESTORM_REACTION_PENALTY = false
; If true, just moving around the target will not trigger it.
REGULAR_BLADESTORM_MOVEMENT_TRIGGER = false
; If true, attacking the target in melee will not trigger it.
REGULAR_BLADESTORM_ATTACK_TRIGGER = false
; If true, the attack will use the regular Crit calc and bonus damage assigned to it.
REGULAR_BLADESTORM_ALLOW_CRIT = true
The comments say, that inversing the settings should cause bladestorm to trigger in more situations, but the name of the variables suggests the opposite and I just had a unit caught in a bind after I deliberately parked them next to a viper
The ability to reorder mods was removed in a recent version of the AML. All that function did was rejigger the order mod names were written into XComModOptions.ini, and that had no effect on how the game processed them.
robojumper's got a blog piece about load order in XCOM 2. It's... complex
https://robojumper.github.io/too-real/load-order/