It'd be helpful to know what kind of errors you're getting. Are you using the mission editor for playtesting? If not, then please do so or you'll have no clue about the cause of a crash and I won't be able to help you.
To start the mission editor, use the "mod_tools.exe" in the "mod_tools" subdirectory of your Nexus install.
What I discovered:
Slots 51 52 55 ;
(in SHIPCLASS "cls_xxx")
... caused a crash for me when launching the mission editor. Removing either 51 or 52 from that line solved it. Not sure, why this happens... you probably tried to mount two main drive slots on one ship!?
SHIPTYPE 1
Name "Punisher"
Class #cls_xxx
Devices #weap_phaser #weap_phaser #weap_phaser ;
Devices #shld_b123 ;
Devices #eng_bFusEng #eng_secFusEng ;
Devices #supp_sensor #supp_bSgen #supp_ecm #supp_res #supp_bWGen ;
SHIPTYPE
... causes another crash when loading the mission. The devices #eng_secFusEng, #supp_bSgen and #supp_bWGen don't fit into any of the slots on this shipclass, removing them fixes the issue (but makes the ship unusable, because there are no generators anymore).
You know how slots, devices and sets work? Here's a quick rundown:
- every device belongs to one or multiple sets, each identified by a different number, e.g.:
DEVICETYPE ...
...
Sets 23 70 73 124 ;
...
DEVICETYPE
- a shipclass has "slots", where you can fit devices into
- each slot only accepts a single device from one or multiple sets
- you tell the slot which sets to accept by using the set's number, e.g.:
SHIPCLASS ...
...
Slots 61 61/62;
...
SHIPCLASS
=> these two slots will accept ALL devices belonging to set 61 and the second slot will ALSO accept devices from set 62
- if you try to fit a device to a shipclass, the game will try to find a valid slot for it by looking at the set numbers of the device and the open slots
- if there are no available slots for this device anymore, the game will give you an error saying as much and exit*
*) you'll only get the error when using the editor - when playing through the normal game's exe it'll just crash