ArmA2 Community Issue Tracker

Currently, weapon-magazine compatability is determined by specific magazine classnames defined in the weapon. This means you must know when preparing a weapon config which magazines are available to use. If you add more magazines later you have to update the weapon. This makes addon compatability difficult/impossible.

This feature proposes a solution by introducing a new class: CfgMagazineInterfaces.
Each magazine would be defined to use a defined interface. Then, you define the weapons to use those same interfaces. Here's an example of what it might look like:

class CfgMagazineInterfaces {
    class 556_STANAG_Interface {
    };
};

class CfgWeapons {
    class M16 {
        magazineInterfaces[] = {"556_STANAG_Interface"};
    };
};

class CfgMagazines {
    class 30Rnd_556x45_STANAG {
        magazineInterface = "556_STANAG_Interface";
    };
};

So, if I create a new magazine that uses the 556_STANAG_Interface, then M16 will be able to load that magazine without modifying the config for the M16. Also, in my example, I allowed weapons to use multiple interfaces. That means that the weapon can load magazines from any of those interfaces. This would make the system more flexible (ex, weapons like the M249 which can load ammo belts in addition to M16 mags).