Well, to state the obvious....Western forces have been fighting in Afghanistan for almost 15 years without a clear cut victory condition. Lol. So we're right on track!

@SpyderBlack723 They won't run out, they are kept for the immersionz. They will however run out in the sense that it won't just endlessly recruit civilians as long as the HQ is active, it will eventually cease operations as to prevent too much spam.

The second part of this quote is confusing me a bit. So would it essentially be useless to add this mission complete trigger to an Assymetric mission?

"Condition": if (isServer) then {count ([getposATL thisTrigger, 15000, ["EAST","entity"]] call ALIVE_fnc_getNearProfiles) == 0 && {count ([getposATL thisTrigger, 15000, ["EAST","vehicle"]] call ALIVE_fnc_getNearProfiles) == 0}} else {false};

And this on "Activation": if (isServer) then { ["end1","BIS_fnc_endMission",true,true] call BIS_fnc_MP};

That trigger would end the mission once there are no more profiles of side EAST left in the mission. I am strictly referencing recruitment HQ's and how they produce insurgents.

@HeroesandvillainsOS  Is that all this is is a trigger? Nothing else like adding any lines or files to my mission root or whatever? I literally add this to "Condition": if (isServer) then {count ([getposATL thisTrigger, 15000, ["EAST","entity"]] call ALIVE_fnc_getNearProfiles) == 0 && {count ([getposATL thisTrigger, 15000, ["EAST","vehicle"]] call ALIVE_fnc_getNearProfiles) == 0}} else {false};

And this on "Activation": if (isServer) then { ["end1","BIS_fnc_endMission",true,true] call BIS_fnc_MP};

With a trigger the size of my map (adjusting the "15000" to suit my map size) and viola! I have an end game trigger? What happens at the end, do I get a default "mission complete" line like I would in SP?

I don't think this I working with 1.60. I'll have to test vanilla but all of my missions use this trigger and with today's BIS update I get "mission complete" on mission start.

Is anyone else using this having any luck?

Bump

BIS probably changed triggers somehow.

Possibly but I'm leaning towards some startup errors causing problems with ALiVE initialization which is causing the trigger to fire before the profiles get populated.

I have a hunch the /author is not a value error might be responsible but I've yet to try a mission where this error doesn't happen.

I'll have to empty my mod line and take a peek.