Spectre-63

Not only that, but the complete lack of respect shown by some posters makes me wonder why people bother contributing. I couldn't think of a more effective way to get a new modder to stop modding than to refer to the product of his work the way some posters have here. Sad, really.

LOL...he said "client side script"! Frederf, I appreciate your confidence in my scripting abilities but I fear you've over-estimated them! I had a hard enough time getting the weapons functional!

Frederf - yes, it could. The downside to doing so would be the mod being characterized as a 'cheat'; which I want to avoid at all costs.

DaSquade - the 'untagged' version of my mod will run 'Client side'...the only issue is the ammunition. Because the ammoboxes need to be modified by whoever created the mission, you'll run out of the multi-round magazines and won't be able to get reloads. Sorry!

Thanks, Frederf...I'll try some of those when I get home.

Frederf - I guess that's the part that's got me confused: how do I inherit the stock M203 Muzzles? They're not a separate class unto themselves, they're defined under each M16's class. I tried doing this: class M203Muzzle : M16A2 but that wound up giving me a weapon that had no optics and used the reloadMagazineSound for the standard M16Muzzle. I also tried: class M203Muzzle : M16A2\GrenadeLauncher but got an error. If there's a way to script this to inherit the M203 Muzzle from the existing weapons, please show me!

Frederf - did you get my PM? Any chance of more help with the icons??

Oh I can make the 203's ladder sight work. My point was that, the way the M-203 muzzle's are coded, I can't configure it to use whatever sight is currently being used for the stock M-203. From what I can see, I must code in some sight or you get no sight whatsoever. Mabes - at this point, I don't have any plans to include HeinBloed's sight, so no worries.

Thanks Rocko/Ricki That helps alot!

I'm having a somewhat similar problem adding images to my GrenadierPack mod. Here's the setup: Inside the .pbo I have the config.cpp, and a folder named "Images" that contains the .paa files for the images. In my config.cpp, how do I reference the image files? Just by name? I tried referencing them by \S63_GrenadierPack\Images\image.paa but I got an error when attempting to view the image inside the ammobox. Should the first part of the path be the proper name of the mod (i.e. the Classname that is in the config.cpp) or the actual name of the PBO file (which, in my case, is S63_GrenadierPack_Cfg)??? Suggestions???

snoops - unfortunately, in order to make my mod not default back to the BIS sights, I'd have to include HeinBlood's mod as a pre-requisite. It's an unfortunate byproduct of the way the M203 Muzzles are coded and I haven't found a way around it. If I don't include the BIS sight, you get no sight whatsoever for the M203 which, obviously, would make aiming a bit challenging.

I actually found the error last night: the M16A4_ACG_GL had an extra "};" in it and that caused the issue with the GL not getting the info on the Muzzle...hence no 'bang-bang'.

It isn't compatible? Uh-oh, that changes things a bit for me. If it's possible please make it so. One more thing, does this work with HeinBlood's GDTModGrenadier? I'd really love to have this with HeinBlood's sight modification. If you haven't done so, you should chat with him about combining the to addons/mods. They are both excellent! I haven't used HeinBlood's mod. I'll take a look but, to be honest, I'm new enough to this that the chances of making my mod compatible with others is slim. That said, now that things are working properly, I'm going to work on trimming out the unnecessary code. That may resolve the incompatibilities with the NWD_ScopeFix.

what issues are you experiencing with the two combined? I've got both installed, so I'll play with it tonight.

I tried TexView, but it crashed every time I opened a new folder or opened a file in Vista. AlterTexView seems to have worked alright tho'.