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
Some of these would become weird if multiple enemies are meant to spawn. I guess one can blacklist individually each of those encounters in DABFL, and only leave the "accidental" one enemy pods, but one would need to know what to do...
+TemplatesToBlacklist = "WychHekatrixM2"
+TemplatesToBlacklist = "WychHekatrixM3"
+TemplatesToBlacklist = "KabaliteDracon"
+TemplatesToBlacklist = "KabaliteArchon"
+TemplatesToBlacklist = "Succubus"
+TemplatesToBlacklist = "Incubus"
+TemplatesToBlacklist = "WrackM1"
+TemplatesToBlacklist = "WrackM2"
+TemplatesToBlacklist = "WrackM3"
+TemplatesToBlacklist = "GrotesqueM2"
+TemplatesToBlacklist = "GrotesqueM3"
+TemplatesToBlacklist = "Haemonculus"
+TemplatesToBlacklist = "KabaliteWarriorSybariteM1NR"
+TemplatesToBlacklist = "KabaliteWarriorSybariteM2NR"
+TemplatesToBlacklist = "KabaliteWarriorSybariteM3NR"
+TemplatesToBlacklist = "WychHekatrixM1NR"
+TemplatesToBlacklist = "WychHekatrixM2NR"
+TemplatesToBlacklist = "WychHekatrixM3NR"
+TemplatesToBlacklist = "KabaliteDraconNR"
+TemplatesToBlacklist = "SuccubusNR"
+TemplatesToBlacklist = "HaemonculusNR"
;----end of eldar
;dark eldarsblacklist
+TemplatesToBlacklist = "KabaliteWarriorM1"
+TemplatesToBlacklist = "KabaliteWarriorM2"
+TemplatesToBlacklist = "KabaliteWarriorM3"
+TemplatesToBlacklist = "KabaliteWarriorDarkBlasterM2"
+TemplatesToBlacklist = "KabaliteWarriorDarkBlasterM3"
+TemplatesToBlacklist = "ScourgeHaywireBlasterM2"
+TemplatesToBlacklist = "ScourgeHaywireBlasterM3"
+TemplatesToBlacklist = "KabaliteWarriorSybariteM1"
+TemplatesToBlacklist = "KabaliteWarriorSybariteM2"
+TemplatesToBlacklist = "KabaliteWarriorSybariteM3"
+TemplatesToBlacklist = "WychM1"
+TemplatesToBlacklist = "WychM2"
+TemplatesToBlacklist = "WychM3"
+TemplatesToBlacklist = "WychHekatrixM1"
;dark eldarsblacklist
+TemplatesToBlacklist = "Dark Eldar Warrior"
+TemplatesToBlacklist = "Veteran Dark Eldar Warrior"
+TemplatesToBlacklist = "Trueborn Dark Eldar Warrior"
+TemplatesToBlacklist = "Dark Eldar Scourge"
+TemplatesToBlacklist = "Dark Eldar Sybarite"
+TemplatesToBlacklist = "Veteran Dark Eldar Sybarite"
+TemplatesToBlacklist = "Trueborn Dark Eldar Sybarite"
+TemplatesToBlacklist = "Dark Eldar Wych"
+TemplatesToBlacklist = "Veteran Dark Eldar Wych"
+TemplatesToBlacklist = "Elite Dark Eldar Wych"
+TemplatesToBlacklist = "Dark Eldar Hekatrix"
+TemplatesToBlacklist = "Veteran Dark Eldar Hekatrix"
+TemplatesToBlacklist = "Elite Dark Eldar Hekatrix"
+TemplatesToBlacklist = "Dark Eldar Dracon"
+TemplatesToBlacklist = "Dark Eldar Archon"
+TemplatesToBlacklist = "Dark Eldar Succubus"
+TemplatesToBlacklist = "Dark Eldar Wrack"
+TemplatesToBlacklist = "Dark Eldar Grotesque"
+TemplatesToBlacklist = "Dark Eldar Haemonculus"
Just to mention about your comment about the weirdness of the MTF lockdown sitrep, I've had that happen without this mod, so I'm not sure this mod is doing it in the first place. Its a thing with the SCP mod I think. I've even set them to friendly, but even with that, Lockdown sitreps still happen, and they happen for Facilities even. Hell I've had full SCP taskforce lockdown (i.e. all the Foundation forces) AND one of the MTF sitreps at the same time (as friendly), so they'd be shooting each other.
In any case, none of the two mods I looked at should be relevant here - their units are not in the usual encounter lists.
If it's this mod that the raiders are from:
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1774066942&searchtext=scp+foundation+raider
then adding
+GroupsToBlacklist = "Raider_MTF"
should do the trick.
If it's the GOC mod, then adding the same with "Raider_GOC" should do the trick.
Ah...not one Pod had 20 Sectos:D Success:D
so I think I understand the issue, but I do not plan on fixing it myself, since it goes against the purpose of this mod. If you use DABFL, then DABFL will try to merge the sitrep list with the normal default follower list, which will put troopers back on this list, and then thanks to my mod they become valid followers to MTF leaders. This is exactly what this mod is supposed to do.
If you don't want it to work this way, then you can go to this mod's XComGame and add:
+GroupsToBlacklist = "Raider_MTF"
This should prevent such interactions in the future.
/s
The only way where this might backfire is if in mod X some enemy Y which is completely busted is added to bunch of "normal" encounterlists under the premise of "yes, this enemy is bonkers, but it can only be a follower of enemy Z from my mod, so unless you run into enemy Z, you won't get enemy Y".
Then these mods might cause some unbalanced interactions with my mod. But then that's what the config for, to blacklist those enemies. So if anyone runs into such weird scenarios, let me know, and the config will be updated.