cornhelium 0 Posted May 26, 2006 sigh... Had a quick look in the config. The weapons aren't set up to take JAM mags. In the 'magazines=' section, they only have their own mags defined. So, where you'd expect to see: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE"> magazines[]={"GALIL_Mag","JAM_W556_30mag","JAM_W556_30HDmag"}; there's just: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE"> magazines[]={"GALIL_Mag"}; This explains helping_hand's picture. He can't pick up a JAM mag because the weapon isn't configured to take them. ...the guys have instead defined their own magazines but used JAM's sub-magazine-level values such as ammo (the actual bullet fired, its damage and stealth values) and recoil to make them. Hence the JAM dependency. I suggest simply adding the relevant JAM mags for the next release. The magazine classnames can be found in the JAM readme. As for the FN MAG, it's based on the BIS class MachineGun7_6Manual. The invisibility of the magazines on the inventory screen may be down to this entry: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE"> scopeWeapon = private; scopeMagazine = public; which should I think be: <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE"> scopeWeapon = public; scopeMagazine = public; Great models btw  Cheers, CH Share this post Link to post Share on other sites
Blackbuck 9 Posted May 26, 2006 hmm it would appeat the apprentice was right for once but then again it is a beta so... that MAG is fabulous by the way Share this post Link to post Share on other sites