[rstaats10]

Good to know you have it working. The // is not read as a line in the file; it is just for your own comments or what not. The spacing on your purchaseshipsplayer file was causing a problem since you had in basically 2 line spacing at the start and it couldn't read any entries. You had 1 line before the // and 1 line after. That was the problem. Only 1 line spacing is what you need.

You had:
================================================== =====================================
*BEGIN*
================================================== =====================================

// custom

Ship Class Name := Hiigaran Battleship
Short Description := big scary *** kicking machine.
Ship Descriptive Class Name := Battleship
Displayed Size Name := Battleship

What you could of done:

================================================== =====================================
*BEGIN*
================================================== =====================================

// custom
Ship Class Name := Hiigaran Battleship
Short Description := big scary *** kicking machine.
Ship Descriptive Class Name := Battleship
Displayed Size Name := Battleship


FYI. You don't have to add new ships at the end of the file, anywhere is fine as long as there is a 1 line space between entries.
Your maincomponentconfigurationslotsplayer file had the same problem with starting with 2 line spacing. Removing the extra line at the top would have worked. could have been like this to work:

================================================== =====================================
*BEGIN*
================================================== =====================================

// custom
Layout Name := Hiigaran Battleship Layout
Number Of Slots := 69
Slot 1 Xpos := 234
Slot 1 Ypos := 64
Slot 1 Group Name := Weapon 1
Slot 1 Comp Type Allowed := Weapon (Light)

Also your maincomponentconfigurationslotsplayer needs cleaned up. It could or may cause problems later when you try to assign a componet to a slot that is not numbered. see below for some examples of a wrong group name.

Slot 12 Xpos := 212
Slot 12 Ypos := 236
Slot 12 Group Name := Inner Hull
Slot 12 Comp Type Allowed := Hull
Slot 12 Comp Type Abbreviation := H
Slot 12 Comp Box Color Index := 0
Slot 12 Ship Section := Hull
Slot 12 Ship Side Facing := 0
Slot 12 Weapon Firing Point := 0
Slot 12 Weapon Arc Start := 0
Slot 12 Weapon Arc End := 0

Slot 14 Group Name := Inner Hull
Slot 14 Comp Type Allowed := Hull
Slot 14 Comp Type Abbreviation := H
Slot 14 Comp Box Color Index := 0
Slot 14 Ship Section := Hull
Slot 14 Ship Side Facing := 0
Slot 14 Weapon Firing Point := 0
Slot 14 Weapon Arc Start := 0
Slot 14 Weapon Arc End := 0

These are just 2 examples. you had a lot of group names that just say inner hull. They should all be numbered to avoid a possible error down the line. An example of how they should be is: Inner Hull 1, Inner Hull 2, Inner Hull 3 and so on.

You have all the bmp's for the xfile just fine.

Again your spaceobjectsxfiles starts with 2 line spacing. cannot read past the 2 line spacing anywhere in the text files so if you start with 2 line spacing it cannot find any entries in the text file.

I really didn't check your firing points to make sure the arcs and firing point numbers are the same in the maincomponentconfigurationslots as they are with the spaceobjectsxfile entry. It it's not right it can cause problems later when you try to look at the ships weapons arcs in the spacedock with your ship or when using LRS (long range scan) on an enemy ship and looking at their wep arcs. Trust me, I have had a crash once before when they did not match up properly.