Hard Light Productions Forums

General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: chronicking on January 14, 2008, 09:11:31 am

Title: Launcher & mod.ini file.....
Post by: chronicking on January 14, 2008, 09:11:31 am
does the 5.5c launcher on the "useful stuff" link support the older style of mod.ini file  or does it have to be the newer mod.ini file.   what i mean is that on the wiki page it shows two kinds of mod.ini files

[multimod]
SecondryList = ,mediavps;      <<<<<<<<no "a" in secondrylist

[multimod]
SecondaryList = mediavps;      <<<<<<< a in secondary but no "," before mediavpa;

and should you have a primarylist = ;  beforehand    like i've seen come with alot of mods?

i guess i should also ask whether the 5.5b launcher that comes with turley's installer support the same thing?

thanx for any replies guys.
Title: Re: Launcher & mod.ini file.....
Post by: Jeff Vader on January 14, 2008, 09:14:09 am
I don't think it's important either way. But, if you want to be sure, use secondarylist, without the comma. Primarylist doesn't do anything useful, as far as I know. And now that you've once again typoed it, it's Turey. Just wanted to point that out.
Title: Re: Launcher & mod.ini file.....
Post by: chronicking on January 14, 2008, 09:26:26 am
lobo to the rescue once again.  no dis towards turey.  i guess i've assumed it's turley with all the quick reading i've been doing of late.  which maybe i shouldn't do since it usually takes me two glances at something before i truely start to retain it, but that's another story.   just never heard the name turey before but have turley.  my bad....

since i have your attention,  one more question about some of the mods.   i  glanced at quite a few before downloading last night and noticed a few have their own nebula packs.   i can't remember the name of the mod, because it was late and i looked at so many of them, but it had green and i think blue nebulae packs to download with it separate.    does Lightspeed's Nebulaevp at the useful stuff page do this for these mods now or should those nebulae packs be downloaded?

questions may seem a bit redundant , but i've spent alot of time setting this thing up to do some serious gaming and i want to get it right.    thanks again....
Title: Re: Launcher & mod.ini file.....
Post by: Jeff Vader on January 14, 2008, 09:31:29 am
i  glanced at quite a few before downloading last night and noticed a few have their own nebula packs.   i can't remember the name of the mod, because it was late and i looked at so many of them, but it had green and i think blue nebulae packs to download with it separate.    does Lightspeed's Nebulaevp at the useful stuff page do this for these mods now or should those nebulae packs be downloaded?
I think I've seen those too. And if I recall correctly, the campaign descriptions said that the nebula packs contained actually parts of LightSpeed's Nebulae, but fior some reason the campaign only features the blue and green ones. So you should be fine by having the nebula pack you can download from my site.
Title: Re: Launcher & mod.ini file.....
Post by: ARSPR on January 14, 2008, 10:16:33 am
IIRC:

SecondryList was a typo. Launcher was fixed so now it recognizes both writings for backwards compatibility. But as you can imagine, always use SecondaryList.

The initial comma was a hack because old launcher versions added an extra space. So if you selected MODFolder and you have a SecondaryFolder, -mod flag was built:
Code: [Select]
-mod MODFolder, SecondaryFolderAnd then the game looked for a " SecondaryFolder" instead of the right "SecondaryFolder".

With the extra comma you get:
Code: [Select]
-mod MODFolder, ,SecondaryFolderAnd the game runs fine because it just looks in an extra folder called " " which usually didn't exist.

Read -mod flag launcher help (http://www.hard-light.net/wiki/index.php/Command-Line_Reference#-mod) for more info.

OTOH PrimaryList is useful but only in very strange cases. Example you've got one master vp which patches or upgrades several different mods. You need it to have the highest priority and you don't want to copy it in every single mod folder. Then you just copy it to just ONE folder which is pointed through PrimaryList. (Another example, I'm using PrimaryList while I'm beta testing MediaVps because of how I've got them installed...)
Title: Re: Launcher & mod.ini file.....
Post by: Jeff Vader on January 14, 2008, 10:30:55 am
OTOH PrimaryList is useful but only in very strange cases. Example you've got one master vp which patches or upgrades several different mods. You need it to have the highest priority and you don't want to copy it in every single mod folder. Then you just copy it to just ONE folder which is pointed through PrimaryList. (Another example, I'm using PrimaryList while I'm beta testing MediaVps because of how I've got them installed...)
Ah, cool. I've always secretly wondered about that but didn't actually ask about it since there didn't seem to be a use for it.
Title: Re: Launcher & mod.ini file.....
Post by: karajorma on January 14, 2008, 10:37:13 am
OTOH PrimaryList is useful but only in very strange cases. Example you've got one master vp which patches or upgrades several different mods. You need it to have the highest priority and you don't want to copy it in every single mod folder. Then you just copy it to just ONE folder which is pointed through PrimaryList. (Another example, I'm using PrimaryList while I'm beta testing MediaVps because of how I've got them installed...)

I've always known what PrimaryList did but I've never been able to figure out any use for it. :D