Quote:
|
Originally Posted by tater
Two things.
1. you'll note that the bungo pete mod should also include a Names.cfg inside the roster folder. You can add your new ship to that usuing the same formula as all the other ships:
Classname=what you want it called in plain english
2. Many times doing this you will get an error in the mission editor where it can't find the ship. It means you missed something.
New ship is called "ShipName."
In Data/Roster/Japan/Sea/ShipName.cfg you need the class name set to ShipName. You need the Type= set to what you want (4 is DD, 0 through 4 act like escorts).
In Data/Sea/ShipName/ShipName.cfg you need the class set to ShipName exactly as it is in the roster version I just talked about. The Type also needs to be exactly the same. All the files in the ShipName folder inside Sea need to also be called ShipName. ShipName.cfg, ShipName.eqp, ShipName_sil.dds(or tga), etc. Failure to have the cfg in there named right will give the same error.
The stock game uses a NDD_Name convention, but the class names are then DDName. I find this confusing, and it is easy to mess one up. Dump the _ and name the ship in a less complicated way to avoid having to check so often to get them to match up.
tater
|
Yeah, that's why I keep getting the mess ups, but should I split the four varients? Two for the asashio, the two for the new ship?