| So you want to make a custom weapon. There's A LOT involved in
creating a weapon so I'm going to spread out over several tutorials. They're
not going to be your basic "copy these files, make these objects, tweak
these setting, put it in an .mn3" tutorial. If they were you'd spend
20 minutes here and the next month testing and re-testing. For those
who just want the 10 minute overview go to
Custom
Weapons Fast. Come on back if want learn more. There's
still a lot I need to learn but I'll save you a lot of wasted time 'discovering'
how most things work.
What these tutorials will teach you:
What they won't teach you:
I personally feel to many people are confusing customizing or the use of custom elements with MODs. MODs involve C++ scripting that I haven't learn.... yet. ;) There's plenty that we can do through the creation of custom oof, ogf, oafs, and the gam file. As far as oofs, ogfs, and oafs are concerned there are plenty of tutorials on those subjects including my 3 part series on custom objects (oofs) which I plan on revisiting once I'm done here. There will be five sections. The first (this one) will cover an overview of what makes up a weapon. Next I'll go over setting up the powerup .gam. Third will be a review of the weapon.gam. In the forth section, we'll bring evrything from the first three sections together to create a simple primary weapon. Finally we'll examine the ship.gam where we set up the firing details weapon. I'm not going to into counter measures. This is because they're not fired from a ship causing them to be very limited. Most countermeasures (mines, seekers, and gunbouys) are actually robots spawned from invisible weapons (it'll make more sense after learning the weapon.gam) Enough hot air... first a quick review of basic definitions for those who need it: 1) OOF: Outrage Object File- Physical
object model such as a powerup, a missile, barrel, crate, etc.,..
You're going to need to look through the Table.gam (D3's main .gam file)
and the oofs, ogfs, and oaf that are involved in the weapons. To
see how to extract the table.gam, oofs, etc, from the d3.hog using Hog2WorkShop
take a look at
|