Started this ~10 months ago, finally converted the last S44 main weapons.

May or may not find it relevant to your interests:

The magic (Thanks to jk)

The weapondefs

I'm not sure I understand why you would do weapons this way (IE, not in the unitdef)? It seems grossly inefficient and difficult to maintain?

S44 weapons have always been 'not in the unitdef' because they are shared across multiple units. It is far more efficient and much easier to maintain this way than defining the same machinegun 9 times. And with the inheritance it is now even easier.

That is imo a good idea.
Would use something like that, if not for two reasons:
-not enought similiar weapons
-did not use it right from start, now too lazy to change it. easier to pile on top of the existing mess

I don't store the weapons in the unitdef.

flozi, what does this do? forbs post doesn't tell me anything more.

What would I be inheriting? can you give an example of how it works out?

example:
http://spring1944.svn.sourceforge.net/v ... iew=markup

At top of file there is the "default" rifle, and under that the "variants" of that weapon.

All the sniper rifles are the same, except:
-each has a unique sound
-the british one reloads faster
-us rifle is more accurate when moving (fooking noscope)

So to make all snipers deal more damage (example) you only need to change one number instead of 4.

------------------------

That is not so nice imo:
It just repeats things that already exist..

Would something like that work?

Yes knorke that would work if you prefer it.

Personally I think the mortars/arty and tank guns are more interesting examples as they use a form of multiple inheritance (Base class, Armour Piercing or Smoke or High Explosive class, then the weapon specific base class)

http://spring1944.svn.sourceforge.net/v ... iew=markup

So, here is code spam:

Basic 'LightGun' class, a class for all 40-50mm direct fire (tank & ship) guns in S44.



Almost all of these weapons have two versions - AP and HE. So make additional classes with those shared attributes:



Now I want to make a particular implementation of a 40mm gun, the British 2pdr:



It should have a HE and an AP version, with some additional specific tags that are not common to the 2pdr itself nor all AP or HE weapons:



At the end I return all the weapons I want to be available in the game, but not their base classes:



Essentially each call of :New just adds all of the new tags to the table, overwriting any that already exist.
The first parameter takes a table of the new values, so you can pass an existing table or a new one using {}.
The second parameter is whether or not to concatenate (true) or overwrite (false) the name string, I use it here to append ' AP Shell' and ' HE Shell' respectively.

edit:


Yes - Its really only useful if you have weapons used by multiple units that share many attributes. In that respect it's a solution to an S44 specific problem, but I thought others might find it useful / be inspired to do something similar / just interesting to see an alternative to the CA defs.

Tried to port this to units: May be incomplete or completely wrong.

script:
http://paste.springfiles.com/view/664e1aca
example:
http://paste.springfiles.com/view/c1eea3b3