Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
This mod is safe to be removed mid campaign. But may left a quirky after effect for any spark(s) that produced and soldier(s) recruited before removal. Any spark or soldier after removal are completely safe from any after effect from both the old or new.
If added mid-campaign, any spark before adding the mod may still don't have any compatibility with any other old (and new) soldier/sparks. The workaround is to "force bond" thru console or use "Spark can do convert mission" then look up those "Form bond" convert mission..
Questions:
Is raising SPARK CI also hardcoded and very difficult like giving them bidirectional bonds?
I get to here in a Robots on covert actions mod, but I don't know how to make SPARK eligible or to remove the check entirely.
static function bool IsNewUnitValidForIntSlot(XComGameState_StaffSlot SlotState, StaffUnitInfo UnitInfo)
{
local XComGameState_Unit Unit;
Unit = XComGameState_Unit(`XCOMHISTORY.GetGameStateForObjectID(UnitInfo.UnitRef.ObjectID));
if (Unit.ComInt >= eComInt_Savant || (!Unit.GetSoldierClassTemplate().bAllowAWCAbilities && !Unit.IsResistanceHero())) //not a soldier hero NOR can it get AWC abilities
{
// If this unit is already at the max Com Int level, they are not available
return false;
}
return IsNewUnitValidForCovertActionSoldierSlot(SlotState, UnitInfo);
Just curious about your take on this.
I have a technitian bonded to a SPARK right now. They're becoming a pretty great duo.
The SPARK does have a point animation - is it the same point animation that soldiers use when granting actions? The sparks use it when using the fear ability and for something else that I don't remember atm.
Honestly, I'm just happy to have the option for RP purposes :)
@Malidictus - I changed it to not exclude robots in my private branch. I could grant teamwork my Spark, but I still can't get the Spark to show the skill despite having met all the requirements. I am wondering if there is a hardcoded limitation.
TargetCondition.ExcludeRobotic = true;
That's not the only skill which deliberately excludes robotic units, though. A lot of the Psi Operative skills do, as well. The first one I ran across - Soulfire - has the same X2Condition_UnitProperty object added to it, with ExcludeRobotic set to true. In the case of Soulfire, that's a lore-based design choice - it's a psychic attacks and robotic enemies aren't affected by psychic effects.
I wonder if excluding robotic for Teamwork is a necessity or a similar lore-based decision, i.e. you can't be friends with a robot. Could be SPARKs don't have an animation to play for it, or somehow break when affected by it. For my own sake of curiosity, how would you go about changing that stat if you could? Pulling the BondmateTeamwork templates out of the manager would work, but I'm not sure how you'd address that specific limitation.
Once I have investigated what is needed to override only a single function, I'll come back and reconsider this.
As to Teamwork - is there a way to un-exclude it for SPARKs?
very cool
Boogie overload imminent.