Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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/