The example missions (one for A2 one for OA) uses the communication menu to call in the support (default space bar - communication) and is split into 4 different sub menus

1. Fixed Wing
Close air support
JDAM
Anti-personel cluster bomb
Anti-tank cluster bomb
Mine dispenser cluster bomb

2. Rotor Wing
Close air support (2 attack choppers)
Transport

3. Artillery
High explosive suppresion
Willie pete suppresion
Smoke
Illumination
Laser guided
SADARM
High explosive Fire for Effect
Willie pete Fire for Effect

4. Air Drop
Ammo
Vehicle

Only 1 support mission can be executed at any given time (so cant have CAS and artillery firing at the same time for example) and the mission designer can impose limits on how may times both fixed wing, rotor wing and artillery can be called (air drops are part of fixed wing), from within "Support\SupInit.sqf"

The ammo drop includes the ability to add custom code so you can use your own loadouts.

I've done my best to ensure multiplayer compatibility and haven't found any game breaking issues thus far.

To add to your own missions the following is required:

Functions module placed on the map
artillery module (named m119Batt)
3 virtual artillery pieces (named vp1,vp2, and vp3 respectively)
artillery module must be synced (f5) to the virtual pieces
an object named spwnpad placed in the editor (I use an invisible helipad)
a player named s1 with the following in his init line

Code:
null = [] execVM 'Support\CommsMenu.sqf';
if you intend to use the menu I created.*
copy the Support folder into your mision


add the following to your init.sqf file

Code:
//wait till both functions module and Multiplayer framework has initialised
waituntil {!(isnil "bis_fnc_init")};
waitUntil{!(isNil "BIS_MPF_InitDone")};
//execute init file for air support
null = [] execVM "Support\SupInit.sqf";

* If you dont wish to use my comms menu you still require a player named s1 and can trigger the calls like so

Code:
null = [parameter1,parameter2] execFSM "Support\Support.fsm";

parameter1 can be :
Fixed
Rotor
Arty

parameter2 depends on what Parameter 1 is and must be in quotes:

Fixed :
"Ammo"
"Vehicle"
"JDAM"
"CBUAP"
"CBUAT"
"CBUM"
"CAS"

Rotor :
"CAS"
"Transport"

Arty :
"HE"
"WP"
"SMOKE"
"ILLUM"
"LASER"
"SADARM"
"FFEHE"
"FFEWP"

Credits :
Much of the code for the fixed aircraft and chopper gunships comes from Draper's Air Support Scripts although a lot has been changed/moved/replaced so many thanks goes to him for allowing people to use his code.

Also thanks to all of you guys who frequent these forums regularly handing out free support and advice and even demo scripts where needed (you know who you are) without which I doubt I would have completed this project.

And finally thanks to BIS for continuously improving and updating the series (I mean who patches a 10yr old game) when many devs/publishers would have washed their hands and walked away - BIS I salute you