Artillery Blacklist

[NZF-JDWang]

We often run ALiVE missions with Simplex Support for the players to call in CAS, Arty etc

The problem is if I have Artillery Auto registration on (so OPFOR will use mortars etc) the BLUFOR AI take over the Simplex Support Artillery and proceed to drop rounds on themselves.

I would like to be able to blacklist that Artillery so it NEVER gets registered by LAMBs.

[BlackAlpha]

In addition to the blacklist, it would be nice if you could cancel artillery missions that are in progress. In fnc_doArtillery.sqf there are a few sleeps. You can blacklist the arty by writing your own code, but if those sleeps are already in effect, then the LAMBS script will still take over and make the artillery fire. A suggestion would be to add an additional check after the sleeps: a variable on the unit that is checked, eg. "lambs_danger_disableArty", and abort the script if the variable is set on true.

[nk3nny]

Nice ideas. Artillery is due a rework. Preferably with adding support for CAS support assets. Don't expect any mature fix for 2.5. But we'll discuss this further for future versions.

Things I would like interlinked:

1. CAS system called in the same way as artillery
2. Ability for groups of artillery to provide supporting fires
3. Ability to blacklist artillery and cancel artillery mid-strike
4. Artillery rewritten with smarter eventhandler based system or similar.
5. Ability to call in smoke support? By ZEUS? Perhaps this is more pertaining to AI profiles NOT ESSENTIAL