I left the pre-seeded reasons from ACE in the offchance ACE switches to using the CBA functions instead. I think all the cases should be covered now but will need some testing

Tested the status effects that I could (stuff like blockSpeaking/blockRadio I couldn't really test in SP to verify). All seem to be working, though blockThrow doesn't block vanilla throwing. Seems like either an oversight or something that wasn't worth implementing at the time

as far as I know it's just for ace_adv_throw

I've seen code that should work in theory but doesn't

    // prevent players from throwing grenades (does not work)
    // [_unit, "Throw", {true}, {systemChat "block";}] call EFUNC(common,addActionEventhandler);

so should it be "ace_blockthrow"? but doing that will cause backward compatibly issues

I mean technically this runs separately from ace's so it'd be fine there. If we have a known way of block vanilla throwing I wouldn't be opposed to adding it. ACE sets the current throwable ammo to 0 iirc, which works but idk if there's something better

Statuses for disableNVEquipment/disableTIEquipment would be nice

We'll need compats for ACE
ideally something like this, so we can merge into and release ace regardless of cba version

if (CBA version > x) then {
  // port call to CBA
} else {
  // old behaviour
};

We'll need compats for ACE ideally something like this, so we can merge into and release ace regardless of cba version

if (CBA version > x) then {
  // port call to CBA
} else {
  // old behaviour
};

I mean you could just:

if (isNil "CBA_fnc_addStatusEffectType") then {
    [...] call ace_common_fnc_statusEffects_addType; // or whatever its called
} else {
    [...] call CBA_fnc_addStatusEffectType;
};