FR: mission flag for preventing the protection that comes with disarm or disable orders

[Svedalrain]

If any ship receives an order to disarm or disable a target, whether by sexp or from a player, that target becomes protected. The intent seems to be for any disable or disarm order to precede capturing the ship, and the protection prevents it from being killed by AI.

Mission designers often run into that protect, and I as a player used to in missions like Forced Entry, since the best way to remove the turrets from a ship is to order fighters to disarm it, whether or not the intent is to capture or kill it later.

The automatic protect is handy for missions involving capture. A mission flag to disable that protect would allow disarm and disable orders on ships for all other purposes without affecting retail missions.

[EatThePath]

Overlaps with #2943, though is broader in scope and proposes a different solution

[Baezon]

I think both would be decent approaches, since player orders will still be an issue otherwise.

[LightblueMobius]

#2943 mentions the "disarm" order only but "disable" has the exact same issue, apparently. Code-wise I have no idea what the best solution could be between an entirely new SEXP or additional arguments to existing SEXPs.

[Goober5000]

An ai-profiles flag makes the most sense, I think. (You can have different profiles for different missions.)

However, the difficult part is not the flag, but finding all the places where disarm/disable targets are protected/ignored.

[wookieejedi]

There is now a way to set this for AI profiles in #5512, along with new orders if you do not want to set it via table, so I reckon this can be closed.

[Goober5000]

Yup, #5512 takes care of it.