All ACE basic features are supported for all 3rd party addons. The only requirement is that the addon is compatible to CBA eXtended Event Handlers.

As of CBA v0.7.1, XEH supports 3rd party addons even when they are not setup to use XEH,

however there are several limitations then: http://dev-heaven.net/projects/cca/wiki/Extended_Eventhandlers#New-in-303-Extended_FiredBIS_Eventhandlers-and-support-for-addons-that-do-not-support-XEH

Some (more advanced) features require support in the config classes of the 3rd party vehicles.

Some of these properties are already inherited from default base classes, these values could be somewhat right for the custom vehicle, however for best experience, the right properties need to be applied.

All requirements and documentation for using ACE features with (custom) vehicles, is available in each Feature's +notes card.

An overview is available on the API page.

See Developer Information for more technical information about the ACE Mod.

Some of the features are setable/overridable by mission makers with setVariable, however this is not possible for all.

Any 3rd party (addon maker, mission maker or player), can apply the needed config properties to the custom vehicles.

It basically comes down to a simple and small replacement config, much like Unit/Weapon replacement configs.

You need:

1. Basic arma config understanding (TODO: BIKI Link)
2. Basic arma pbo tools and understanding (Able to unpack and pack a pbo) (TODO: BIKI Link)

Examples

Add Afterburner to PlaneX. See Afterburner+notes for the required config properties.

1. Unpack PlaneX.pbo
2. In it's config.cpp, lookup the addonclassname in CfgPatches (found to be planeX), and the plane base class in CfgVehicles (found to be planeX_base)
3. Create a new addonfolder, e.g: ind_ace_planeX_afterburner
4. Create a config.cpp inside (Content listed below)
5. Pack the addon folder into pbo
6. Load the addon in a modfolder

class CfgPatches {
   class ind_ace_planeX_afterburner {
       units[] = {};
       weapons[] = {};
       requiredAddons[] = {"ace_sys_afterburner", "planeX"}; // Include the ace system addon (optional, only for reference), AND especially the 3rd party addon that we are adjusting.
       requiredVersion = 1.0;
   };
};

class CfgVehicles {
    class Plane; // External class reference
    class planeX_base: Plane { // this needs to match the original config
        ACE_hasAfterburner = 1;
    };
};

Otherwise take Robalo's ACE configs as example: http://forums.bistudio.com/showthread.php?t=120120

Sharing

Anyone can create these ACE 3rd Party support configs.

It would be great to accumulate them on this or some other page, so we aren't all doing the same tasks double :)