Is there a repro with latest version of ALiVE? We have put in code that reduces the likelihood of aircraft being spawned in hangars too small.

1. Use Mil Placement modules to place air units across the map. As a backup use MACC to place air units too, this way you are ensured to get atleast 1 fixed wing and 1 rotary wing asset. Of course always ensure the faction has ARMED aircraft with A2A and A2G capability.
2. Make sure that the aircraft are virtualized, turn on the module debug and check your RPT - this will tell you if aircraft are registered with MACC. The MACC will select the closest available aircraft to the CAP zone or DCA target.
3. We are working on resupply function for air assets.

I think you are correct... we check aircraft roles...

CAP/DCA aircraft require Air to Air missiles
SEAD aircraft require Air to Ground missiles

We have stats tracking in ALiVE already (as well as AAR) if that helps?

We don't do anything different wrt EH, we use the standard BIS way of adding EH for our mod. For example:

class Extended_Killed_Eventhandlers
{
    class LANDVEHICLE
    {
        class alive_sys_statistics
        {
            killed = "_this call alive_sys_statistics_fnc_unitKilledEH";
        };
    };
    class MAN
    {
        class alive_sys_statistics
        {
            killed = "_this call alive_sys_statistics_fnc_unitKilledEH";
        };
    };
    class AIR
    {
        class alive_sys_statistics
        {
            killed = "_this call alive_sys_statistics_fnc_unitKilledEH";
        };
    };
    class SHIP
    {
        class alive_sys_statistics
        {
            killed = "_this call alive_sys_statistics_fnc_unitKilledEH";
        };
    };
};

Have you tried tasks on Malden yet? If not, please test :)

Very rushed quick tutorial for you guys...

Very rushed quick tutorial for you guys...

The bulk of data is related to map indexes.

ALiVE does static analysis of each map to provide AI commanders with an in-depth insight into the map's terrain, locations etc. Each map index can be 10MB+. There's around 410MB of map data in total.

Before packing as PBO, ALiVE source code is around 477MB. So, code wise, there's around 67MB of source code. There's some 2600+ files that make up ALiVE, no idea how many lines of code but its 5 years of coding by a team of around 4-6 developers...

AI Landing aircraft is BIS code and not related to ALiVE.

If once landed the aircraft is not parked back to its spot correctly, then this would be an ALiVE issue.

Current MACC conducts CAP and DCA missions only

Only need to sync MACC to OPCOM. Recommend creating an airspace marker and specifying it in the module Paramus. Create an airspace per side, try to avoid overlapping them or you quickly run out of aircraft.