[Scuddie]

Someone do me a favor.  Put together a quick scrap mission that doesnt serve a purpose except to prove a point.  Put two fenrises facing a lilith in the mission, then beam-free-all.  Now, change the forward beam cannon on one of the fenrii to something like a BFRed.  Just so you know it's different.  Leave the other fenris alone.  Save, and start FS2.  Launch the mission and see what happens.

Incase you don't notice, both fenrii have BFReds, even though you only changed one of them.  Now normally, you wouldnt do much of this.  However, if you decide to make a campaign involving live-action R&D of new types of weapons, etc, it would bring in some problems.

Anyway, I'm surprised this hasn't been fixed yet.  And I would assume it wouldn't be too hard to get a fix for it.  And that's all I have to say about it.

BTW WMC, Get yer butt in IRC, I'm going to help you debug that modular bug of yours.  I dont know how to write C++, but I can definately read it, and there looks to be some bad grammar in weapons.cpp, but then again, I could be wrong.

[WMCoolmon]

What build is this problem in? I think I may have fixed this with this build, and my updates to the turret code; a lot of the code seemed to be referencing the ship class struct rather than the ship struct.

My butt will be in IRC as soon as you specify a server/room. I can't really compile or debug atm, but I'd like a look-see at what you've found.

[Scuddie]

#nodewar.  You know where it is

And I'm referring to the way that all ships of one type have identical weapon loadouts.  If you have one ship have a different than normal weapon, they all do.  I'll check your build and see if it's working.  But Bob's custom warp build still had this bug.

[Kazan]

could also use #fs2source on mgo.maxgaming.net

[WMCoolmon]

Yeah, I can join #fs2source but not #nodewar.

[Inquisitor]

That is the purpose of having the channel