ArmA2 Community Issue Tracker

This is a suggestion on how to implement both of these features:
http://dev-heaven.net/issues/11383
http://dev-heaven.net/issues/11417

If both of these features are implemented, then the magazine proxies should be tied to the magazine interfaces. Ex:

class CfgMagazineInterfaces {
    class 556_STANAG_Interface {
        proxy = "556StanagProxy";
    };
};

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

class CfgMagazines {
    class 30Rnd_556x45_STANAG {
        magazineInterface = "556_STANAG_Interface";
        model = "556stanagProxy.p3d";
    };
};

With this, you can have multiple proxies on a weapon, and the magazine interface determines which proxy to fill for which magazine model. I'll use the M249 belt & M16 mag example again. You would need to fill the magazine models into different proxies for the belt & M16 mags.

(sorry but I can't get the code tags to work right)