Cài đặt Steam
đăng nhập
|
ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
SkipExclusions.AddItem(class'X2AbilityTemplateManager'.default.DisorientedName);
So I'm even more confused. It should currently be preventing the ability when the Officer is disorientated. I'll try to boot up a campaign later, see what happens on my set-up.
You could try AIBTExplorer, it does some syntax checking of AI behaviours
https://github.com/RossM/AIBTExplorer
Here's a pastebin of my XComAI.ini: pastebin.com/sR1354F7
(Seems native XCOM doesn't include this check by default??)
+Behaviors=(BehaviorName=AffectedByEffect-Disoriented, NodeType=Condition)
+Behaviors=(BehaviorName=IsNotAffectedByEffect-Disoriented, NodeType=Inverter, Child[0]=AffectedByEffect-Disoriented)
Then you need to add that condition as a child to the 'TryCallReinforcements' behaviour routine. Possibly after the 'IsAbilityAvailable' check, so something like:
Child[1]=IsNotAffectedByEffect-Disoriented, \\
(Make sure to increase the [index] for any following child behaviours)