More about extended mod support

posted on May 14th, 2011, 6:39 am

there is a configuration file for each mod (info.ini). there you can set name, icon, version, website, author name, if your mod is standalone (not based on fleet operations files) or which is the "parentMod". for the "campaign mod" in my example this was simply the line parentMod=sta2 (foldername of my sta2 mod)

posted on May 14th, 2011, 8:15 am

You guys are awesome!

[Anonymous]

posted on May 14th, 2011, 12:47 pm

Last edited by Anonymous on May 14th, 2011, 12:49 pm, edited 1 time in total.

Can we have a list of commands for the info.ini file?  I'd like to start modding for it now.

Oh, I have 2 more questions.

Where does the mod logo go?
What if the parent mod is the stock Fleet Operations?

posted on May 14th, 2011, 1:50 pm

What if the parent mod is the stock Fleet Operations?

a full list will provided if all commands are considered final. mods can even work without the configuration file wheres they can access fleet operations files by default.
an

Where does the mod logo go?

in the info.ini you can define a .ico file that will appear in the window titlebar, shortcuts for your mod etc and a "screenshot" or mod logo for the mod selection screen

posted on May 14th, 2011, 4:13 pm

lol this is goona b great

posted on May 15th, 2011, 4:28 pm

What if someone wants to host a game that uses multiple mod packs at once?  Will you have to "merge" the required mods?

Would there be some way of making it so that a mod can "merge" a mod without modifying any files?  Example:

info.ini

Code: Select all

requiredMod0 = myMod
requiredMod1 = otherMod
requiredMod2 = transwarpMod
requiredMod3 = superMod

Could something like that be implemented with conflicting files being resolved by using the last file on the list?

posted on May 15th, 2011, 9:12 pm

manual loading order lists are planned for later, with the first release it will only be possible to chain up mods using the parentMod property

posted on May 15th, 2011, 9:31 pm

Oh.  Okay.

posted on May 15th, 2011, 11:22 pm

manual loading order lists are planned for later, with the first release it will only be possible to chain up mods using the parentMod property

Either way, it beats copying your entire install.  Who cares if you have something like the physics project copied as a sub mod several times? Sure it would be cool to just have one mod access another, but the parent/child method is good enough for me. Heck, its beyond good enough, its awesome!

posted on May 16th, 2011, 5:35 pm

Why isn't this feature on the priority list?

//www.fleetops.net/project-progress.html

posted on May 16th, 2011, 5:41 pm

maybe it was classified, or it is simply finished.

[Anonymous]

posted on May 16th, 2011, 6:50 pm

Last edited by Anonymous on May 16th, 2011, 6:52 pm, edited 1 time in total.

What's the current progress of this thing?  And can we have an estimated release?  My guess is Q3 2011 or earlier.

I almost forgot, will this thing be as a patch or full installation?

posted on May 17th, 2011, 8:20 am

What's the current progress of this thing?  And can we have an estimated release?  My guess is Q3 2011 or earlier.

when it's done

I almost forgot, will this thing be as a patch or full installation?

it will be either released as a patch or a full installation

posted on May 17th, 2011, 1:27 pm

Will there be any example mods when the thing is released?

posted on May 17th, 2011, 2:26 pm

not decided yet.
of course we'll provide documentation for the feature