Thank you! And I'm sorry for your loss. A tough thing to go through, especially around the holidays.

It's a plausible idea and I think I know how I could set it up, and even have it config editable... but currently I'm taking a short break away from xcom2 modding (and most on-line activity tbh, to process the loss of my father, topped with a massively hectic, now completely re-written, christmas)

The idea has merit though and I wanted to voice that it has been heard. I will see what spare modding time the new year brings. :)

Is there any way to deliberately trigger the bug in Advent-only missions?

I'm using Playable Aliens and Non-Skirmisher Hybrids with Extract Corpses. I have been having (an admittedly minor) issue where if I knock the last enemy unconscious, the mission ends before I can drag them to a Skyranger evac point. I get a corpse even though I'm taking extra risks to bring them in alive.

It would be nice if, when all enemies are dead, I can take a few extra turns to do battlefield cleanup before mission ends and potentially recruit a few extra troops. (Ideally, the faction anchor would self destruct if there are no unconscious enemies on the map, but I recognize this would take extra coding on a mod that hasn't otherwise needed an update in a year.)

The lost will spawn until all the "originally placed" units are dead.
This mod functions correctly in that regard in that the mission won't end until they are all dead.
You have likely hit an issue where there is a single/pod of Lost in some corner of the map, or indeed INSIDE a shipping container (the most common cause of this issue).

If you feel this mod is stopping your mission from ending, you can use the console-commands as discussed in the description to kill-off the anchor and return to 'normal' gameplay rules.

this mod as a HUGE BREAKING BUG the lost sometimes spawn endlessly and will not stop on missions the one it happened on was a heaven

If you use [Shift] instead of tab you should get to the anchor faster and before cycling through enemies ... also don't use the console command to kill it, this won't trigger it's death handling correctly, use the perks it has to kill it correctly ....

Regarding Lost interactions. One or two Lost almost always head towards the faction anchor. The Lost never target the anchor but remain beside it presumably with the intention to target it in the next turn. These are the 'hiding' lost that can cause the 'infinite waves' of lost.

Personally, if I start a lost mission without a third party, I use
X2AllowSelectAll true, followed by tab to select it, move the cursor to it
KillClosestUnitToCursor
to remove it. This may cycle your through some enemies showing their location but I prefer that over a couple lost just seeming to randomly run away and the continuous lost waves that result.

As long as whatever is KO'ing them is doing it correctly there should be no issues .. however! as stated in the description you may need to actually execute some units (like MOCX) with another mod

does this mod conflict in any way with knocking enemy units unconcious?

Was the invisible tile thing on a sitrep with MoxC? I've had one occurence where a MocX rookie and a pathfinder spawned under the walkmesh and I ended up with mostly invisible foes and very glitchy targeting.

My bad sorry

Check issue 6

It seems with this mod that once you kill all the enemies for a mission, the game doesn't count the mission as completed until you end the turn instead of it doing it automatically for you.

oh no my b I meant the middle of the part we were at,but yes we were in the very corner of the map,tho left/right of it can't remember
But yeah it seem it was just a hiccup as so far he didn't do it again

Hmm, doesn't sound like he was targeting the Faction Anchor then honestly

.. the FA sits itself in the far ""top-left corner"" of the map.. if he was aiming at something in the middle of the map, it shouldn't have been this.

This change was done roughly around update 1.9 - 30 Mar, 2021, when I was adjusting it's pod-spawning mechanics.

Well luckily it only happened once so far,next time he targeted us.
But ye it was funny to see him basically,refusing to move and keep aiming at that one tile in the middle of the map

Well, that sucks because nothing should consider it a valid target.. especially the hunter as they're on the same damn team!!

I've completely exhausted everything I know on how to stop things targeting the anchor

The chosen hunter when in sniper mode (not yet in team range to actually fight) keep targeting the anchor in the ground with its mark

@LeyShade
Or the Faction you want to blacklist from it.

Faction Anchor it nice when you use lwotc bc i get more loot

@MabelTheBraixen - You could just add all the Lost units to the Faction Anchors config to not count them and then ignore them when it does it's end of mission check...

@MabelTheBraixen
I've never tried it, but:
https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1157127420

Ah, I see. I'll just deal with it, even though I despise the lost. Thanks for the reply though.

Unfortunately not.. the way it's done is an "all or nothing" approach ... there are either enemies from teams other than Advent alive (keeping the Anchor alive), or everyone is dead (and so thus the Anchor can die).

I just ended up using KillallAis. Is there option in the config to just make it so the mission ends even though there is lost left?

If you have a mission with the Lost and they keep spawning it normally means that one of them from the "initial spawn" is hiding in a building corner or something. You need to kill this one to get the reinforcement spawns to stop.

This normally involves searching the whole map, or using console commands to root it out. (X2AllowSelectAll true, followed by tab .. or KillallAis)

Does anyone know how to disable the lost team as a faction held by the hook? I got a mission where they kept spawning every turn around the map too far for soldiers to reach and it ended up creating an infinite mission

literally 600+ campaigns according to my photobooth (though many were ofc quick restarts for mod troubleshooting reasons), have never had an issue with this

i tried starting a new campaign without faction anchor and my game breaks, but the game is fine if i run with it somehow

Have you tried "X2AllowSelectAll true" to make sure there aren't some enemies hiding somewhere? (Look at the paragraph at the end of the "Known Issues" section.) I used to have the anchor not kill itself all the time, but not even once since the July 1 update last year -- every time I thought it might be happening, there was an enemy pod trapped behind a wall or something.

Hello, I ran into such a problem, on one of the missions to protect the settlement on the Mordovian map, I cleaned up everyone, but the anchor continues to live and does not allow me to complete the mission.

I posted basically that to MOCX and have added it to my own local tweaks mod. I could try to setup a test, but I'm looking to play a little, so with any luck it might occur "naturally". :)

that's the one.. you can add the MOCX fakebleedout to that

I think I found it: XComGameData_SoldierSkills.ini

[XComGame.X2Effect_SpawnShadowbindUnit]
AbilitiesShadowCantHave=CarryUnit
AbilitiesShadowCantHave=PutDownUnit
....

there's a config somewhere for "AbilitiesShadowCantHave" .. it's right next to the one for templar ghosts ... XComGameData_SoldierSkills ? maybe

but yes, ultimately a MOCX issue .. might be worth a report to RM over on that mod :)

Yeah, even with the right setup, it's super rare. I guess a shadow going into MOCX bleedout is technically a bug in MOCX, but you'd never see it without rebellious MOCX (or maybe if you mind control a MOCX). Even then, it won't usually cause any problems at all.

Yes, that certainly is an edge case.. and adds to the wondrous issues caused with MOCX. :)
Thank you for the detailed explanation of the issue though.

I found a weird edge-case. It's not worth trying to fix, I just wanted to share that it's possible.

Relevant mods: MOCX and rebellious MOCX (25% chance to show up on team one instead of team Advent).
-MOCX comes in on Team one
-A spectre shadowbinds a MOCX sniper (the log lists the sniper as unconscious)
-I kill nearly everything else before the spectre and shadow, then I kill the spectre
-The shadow goes into MOCX bleedout (the log lists the shadow as unconscious), sniper is still unconscious as well
-I finish all other enemies
-The anchor sees only unconscious or evac'ed enemies and suicides
-I kill the "unconscious" shadow, the MOCX sniper wakes up
-I finish the mission objective (destroy the device) and with no anchor, it ends right away

No worries man. The mod I was thinking about was Mission Overhaul: Mercury, which isn't compatible with CI anyway. The Protect The Device mission from that, don't even have the Neutralize all enemies objective. If it had, I would just have edited that objective out before use.
Just trying to build a new modlist, for my next game.
Thanks for a lot of good mods.

I don't think it does.. as the waves will never start as the last unit hasn't died ..
try just killing the anchor with KillAllAis

How does this mod work, with missions were the map starts empty?
I think, there's some modded missions were the map starts empty. Xcom when gets some turns to prepare before reinforcements starts dropping.
Basically wave-defense missions.

very good mod!

I know I've had plenty of four way fights that lasted until the last faction unit is dead with this mod.

I know the mod works. ... yet people still run into these issues, like yourself here.
I'm past the point of trying to figure out every use case .. but if you want to check the log was enabled in the configs, and upload the launch.log somewhere (like pastebin), I could check what was going on

Well, the thing is.. the anchor is not suppose to be targetable and/or killable by anything but the script

Somethings keep killing it though
The logs would have the point it decided to commit to death

You did your best

Gangshit

Then at some point prior, the Faction Anchor died

I was on a retliation mission that became a fourway between XCOM, ADVENT, MOCX, and Hive. After the last ADVENT and MOCX goons died, the mission ended even though a ton of Hive lids were still on the map.

@RustyDios Thanks for the reply, I understand the problem better now.

the non-compatible solution: involves a player downloading the SDK, opening every map parcel in the game and editing the kismet to have all the extra code needed for more teams. And then -not- having any extra mappacks or mission editing/extending/adding mods.