quote:

Because the game always does a CTD while loading.

quote:

ORIGINAL: Hannable

j) Copy the Asari bias line from the Mass Effect bias file and paste it at the bottom of the DWE biases, in this case, line 38 (making sure that there is still an empty line underneath the Asari entry)

quote:

ORIGINAL: ehsumrell1

Hello Hannable;

You didn't mention what version you are running, but usually a CTD at start-up
means a missing or corrupted file. From what I see, if you're running Shadows
I don't see mention of you adding an Asari DesignTemplate file to the DesignTemplate
directory. Just a guess that might be the problem, but more info would be helpful.
[&:]

quote:

ORIGINAL: Fenrisfil

quote:

ORIGINAL: Hannable

j) Copy the Asari bias line from the Mass Effect bias file and paste it at the bottom of the DWE biases, in this case, line 38 (making sure that there is still an empty line underneath the Asari entry)

I think this is probably your problem. The bias line will be pretty much meaningless when moved into a new mod and if your moving it into a mod with a different number of races it won't have the correct number of coma seperated numbers in the line. Not only that but adding in an extra race will require an additional coma separated value to be added to each line of the bias file.

I recommend copying the most neutral line of the list (or any race similar to the Asari, I don't know the extended mod so can't recommend one)and simply changing the number and race name to match the Asari. Then go down the list and add in a ", 0" to the end of each line (copy and paste it). You will probably want Asari to have 10 or something so they like themselves and you may want to modify other species bias rating, but it's not vital and it may be worth leaving that until after you have tested the mod.

Remember each race you add will require not just their own bias line but an update to every other races bias line.

quote:

So yeah, I'm boggled.

quote:

First thing backup your broken mod folder, the one your posting about here, and put it somewhere safe. Delete it from the 'Customization' folder, you can restore and fix it when you have a better grasp of how things work.
Have a look in the 'Customization' folder and you will find a folder labeled 'Distant Worlds Original'
That has the absolute bare minimum of what you need to make a working mod. Its a very common mistake to throw everything you want into a folder in 10 minutes and then load DW and find that it doesn't work, copy the 'Distant Worlds Original' folder, rename it to your mod's name and take it from there. Replace one race, learn the structure of that mod folder regarding where race names are used,

biases.txt
Policy/YourNewRace.txt
races/YourNewRace.txt

I would suggest taking a race you are familiar with, one you have played the game with, and start with copying that races file in the races folder and renaming it to your new races name. Make a backup of that file once you have renamed it and then edit that file to your liking using the 'Distant Worlds Legends - Modding Guide.pdf' as a guide to what all the various sections are, as your just starting to learn the modding process don't over complicate things, leave the original race ship choice and only make small changes to the race file so you can remember what you have altered in case things go wonky. Once that is done do the same for a policy file, choose the same race as you did in the races folder, rename it to your races name, make a backup and edit the new race policy file. Now onto the last one and it is easily the worst of the three, the biases text file, this is what causes most mods to malfunction, only experience and time will help with this one, I suggest make a backup of the file, open it for editing and copy the line that has the race you selected in the race / policy folder and copy that, move to the bottom of the file, one line below Mechanoid (*note that there is a blank line below Mechanoid, make sure you put that blank line back once you have finished) now paste your line and renumber that line to 22 and change the race name to YourNewRace, make sure that there is a blank line below it (see previous * comment) and save the file. As tjhkkr pointed out, you have to be very careful when you change any of the text in the previously mentioned files, worst one is the biases.txt. Always ensure to use Notepad or Textpad to make sure that when the file is saved it is compatible with DW. Make a new folder in your mod folder and name it 'raceImages' you will then need to put your race image in that folder, race_22.png and race_22a.png. Now make another new folder in you mod folder and call it 'troopImages' copy one of the DW troop images and paste it in there and rename it Troop_22.png.

Load DW and change the theme to your new mod /theme, it should work unless I've missed something which is nothing unusual as I'm blonde and large, there are much more talented folk on here than me at this sort of thing, but that should be the bare basics to get a mod /theme working. Once you know its working backup the whole mod / theme folder and name it mod_ver_00, that way you have a base to work from, if things go wonky, and they will, you can just delete the broken mod /theme folder and drop the most recent backup into the 'Customization' folder. Just remember to edit, test and if it works backup the folder and increase the revision number, mod_ver_01, mod_ver_02, mod_ver_03 etc.
Make a cup of tea and read the 'Distant Worlds Legends - Modding Guide.pdf', page 5 has the full breakdown of the mod folder structure. With the guide open download Igards Star Trek Mod or Haree78's Distant Worlds Extended mod and have a look at the way they have put things together, reference the modding guide and just get a feel for what does what and what goes where, hence the term Reverse Engineer. Once you can alter the theme with confidence go back to your original Mod that did not work, the one your posting about here, restore it in the 'Customization' folder and you should have a facepalm moment as to why it would not work.

quote:

ORIGINAL: Hannable

Holy crap, I think I finally got it to work. I'm not even sure what I fixed except that I copied a bias line from one of the stock races and added another column for the new race and it worked for some reason. Not even sure why except perhaps there was a syntax error somewhere that I was making by adding biases manually.