Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
[0021.19] Warning: Redscreen: BehaviorTable index 3911 has a duplicate name (Viper::CustomMeleeTargetScore) - INVALID
[0021.19] Warning: Redscreen: BehaviorTable index 3951 has a duplicate name (ViperNeonate::CustomMeleeTargetScore) - INVALID
[0021.19] Warning: Redscreen: BehaviorTable index 4034 has a duplicate name (FindBerserkerMeleeDestination) - INVALID
[0021.19] Warning: Redscreen: Unknown node type specifier: VWCondition (TargetIsHumanoidAlien), Previous=TargetIsNotHumanoid
You are right
Redscreen: BehaviorTable index#4018 (AffectedByBindEffect), child#1 references non-existing BehaviorTable (AffectedByEffect-BindSustained) - INVALID
I had strong unit which got grabbed from top floor of the building regardless option to prevent such thing is turned on.
Anyway , once she got pulled in, my other unit went into panic mode and started berserk shooting at viper.
What happened next was retarded.
Berserked unit shoot viper 3 times and viper dropped my unit 3 times and grabbed her again 3 times , each time doing damage.
....Result is dead unit.
'+CustomNodes=(NodeTypeString="VWCondition", ExtendsFromType="Condition", ClassName="ViperWeapons.X2AIBehavior_ViperWeaponsCondition")'
should be this instead:
'+CustomNodes=(NodeTypeString="VWCondition", ExtendsFromType="Condition", ClassName="ViperPullandBindRework.X2AIBehavior_ViperBindReworkCondition")'
because otherwise crashes can happen.
Either of those should be changed to fit the other.