FreeSpace Wiki - User contributions [en]

Template:Table3610

2010-01-19T07:35:58Z

Tomo: Should be 'or later', not 'earlier'. These features are not in 3.6.9

<noinclude>[[Category:Templates|Table3610]]</noinclude>
<div style="padding: 1px 2px 1px 2px; background-color: #202035; border: solid 1px #505099; padding: 0px 4px; font-size: -1; color: #CCCCFF">'''FS2 Open 3.6.10 or later:''' {{{1}}}</div>

...With Vast Seas

2010-01-10T14:34:28Z

Tomo: /* Notes */

{{Mission|previous=A Blue Planet...|next=The Dragon Awakes|campaign=Blue Planet: Age of Aquarius Campaign Walkthrough}}

'''MISSION 2 - PART 2'''

'''Fighter squadron:''' [[222nd Nightwolves]] 

'''Description:''' ''Against all hope and reason, Earth lies in ruins.'' 

----
==Background==
All life on Earth has been extinguished by orbital bombardment. Probes detected signals within Sol only weeks ago, so reason suggests the attack came only recently...but reason alone may not suffice to explain this catastrophe.

==Walkthrough==
This is a straightforward mission. Do not ram or destroy the Hermes pod.

==Notes==
If the ruined Earth is not present in the background, or if weapon shots do not appear, please ensure the MediaVPs are installed and there is a [[mod.ini]] enabling their use with Blue Planet.

Because of their emotional content, many of the lines in this mission were used in auditions for the roles of Sam, Mina, and Corey.

==Total number of forces==

{| border=0 align=center

{|border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#3C1E1E; font-size: 150%" |
'''Forces involved'''

|- align="center"
| colspan=2 style="background:#202020"| '''Belligerents'''
|- align="left"
| style="width:160px" |
| style="width:160px" |
|- align="center"

|- align="center"
| colspan=2 style="background:#202020"| '''Ships'''
|- align="left"
| style="width:160px" |
| style="width:160px" |
|- align="center"
|- align="center"
| colspan=2 style="background:#202020"| '''Spacecraft'''
|- align="left"
| style="width:160px" |
| style="width:160px" |
|- align="center"
| colspan=2 style="background:#202020"| '''Casualties'''
|- align="left"
| style="width:160px" |
| style="width:160px" |
|- align="center"

|}

==New equipment==
''To be added later''

[[Category: Blue Planet]]

Installing Mods for FS2 Open

2010-01-10T14:33:48Z

Tomo: /* Installing a mod */

==Important Note==
When installing/playing a mod, it is recommended to create a new pilot for every campaign that you play. That is, one pilot for FS2, one for FSPort, etc. This will in most cases avoid the dreaded pilot file corruption problems that crop up sometimes.

== Improvements upon Retail ==
While installing mods for FreeSpace has never been hugely difficult, [[Source Code Project|FS2_Open]] has made considerable improvements to the way that they are handled. Under retail, installing more than one mod involved either installing several copies of FS2 or tiresome dragging and renaming of folders and files. Under FS2_Open, less than a minute's work when installing a mod can mean that you can swap between mods with nothing more than a click of a button.

== Installing the Media VP files ==
To truly take advantage of FS2_Open's modding features, you should install the [[MediaVP|media VP]] files to a subfolder of your FreeSpace 2 folder. Although you can call this folder anything you like, the assumption that will generally be made is that if you have put them in a folder it will be called ''mediavps'', so it is probably best to stick to that. Now that you have put the media VP files in that folder, you must go to the mod tab on the Launcher and select "mediavps" as your mod when running FS2. If you don't do this, FS2 will run with none of the media VPs' features. It will be like playing retail again.

== Installing a mod ==
Be very wary of what the readmes that come with mods tell you to do. Many mods were written before FS2_Open had these new features or by people only vaguely aware of what they do. For this reason, always remember this:

'''Do ''NOT'' install anything to Freespace2\data or into the root FreeSpace 2 folder regardless of what the instructions say.'''

Installing files into Freespace2\data or the root FreeSpace folder is the method used for retail campaigns and very old SCP builds only. This guide is about installing mods for up-to-date FreeSpace Open builds.

If you are following this guide, there is no reason to install files into either of the folders mentioned. Installing a mod to Freespace2\data means that FS2 retail and multiplayer will load the mod and probably break.

What you should do is make a separate folder for every mod within your FreeSpace 2 folder. '''If the mod consists completely of VP files, stick them all in a folder within the root FreeSpace 2 directory and you're done with this step.'''

If the mod's readme tells you to install to Freespace2\Data, make a new folder called Data within the one you just created and then follow the instructions using this new Data folder as if it were Freespace2\Data (i.e if the readme file instructs you to put a file in Freespace2\data\tables, put it in Freespace2\ModName\data\tables instead).

'''Run the Launcher, click on MOD tab, select the folder that contains all the mod's files (i.e. not ModName/Data, simply ModName) and you're ready to play.'''

(Launcher MOD tab is really setting the -mod flag, so you get the command line explained in the next section. For more info about how -mod and MOD Tab work, read [[Command-Line_Reference#-mod]]).

The last step is only required if you want the mod to be able to access the Media VP files and it doesn't already have a [[mod.ini]].
 This is done by creating a new text file called [[mod.ini]] (be careful that the computer doesn't call it mod.ini.txt). Cut and paste this into the file:

<pre>[multimod]
SecondaryList = mediavps;</pre>

:::'''PLEASE NOTE:'''
::::Older mods will use "secondrylist" and start the mod list with a leading comma. This is no longer necessary (these were workarounds for bugs that have since been fixed), and thus [[deprecation|deprecated]].

Place this file in the mod's folder, then run the game as described above.
Most, if not all, mods should already come with a ready-made mod.ini. If they don't, or if you are unsure how to create one, feel free to bug the mod's creator about it.

== Alternative method / more info ==
Alternative method by jr2 (if you don't want to use mod.ini)

Just install the MOD as mentioned above, except skip the part about making a mod.ini file. 
Then, in the launcher, under the Features tab, enter the following: 
:-mod mod1,mod2,mediavps 
where <mod1> is the mod you want to play, <mod2> is the mod that the mod you're playing depends on, and <mediavps> is the name of the folder where you've stuck the Media VP files. 

===Example 1===
To run Transcend, if I've installed it to C:\Freespace2\transcend,
and if I've installed Media VPs to C:\Freespace2\mediavps, I'd type:

:-mod transcend,mediavps

into the Features tab.

===Example 2===
To run the Solar Wars Chapter 1 mod for the Inferno Chapter 1 mod, if I've installed Solar Wars Chapter 1 to

:C:\Freespace2\solar_wars_ch1

and if I've installed Inferno Chapter 1 to

:C:\Freespace2\infr1

and if I've installed the Media VPs to

:C:\Freespace2\mediavps

I'd type:

:-mod solar_wars_ch1,infr1,mediavps

Basically, (remember, -mod mod1,mod2,mediavps) FS2_Open looks for the files it needs in <mod1>, if they are there, then it uses them, if not, it looks in <mod2>, if not there, <mediavps>, if not there, then the main FS2 directory. If there are more than one version of the file it needs, then it will use the one that it finds first, in the order that it looks for them, as seen above.

Also, you could use the mod.ini method so that mediavps is automatically appended to the list and you'd only have to type <mod1>,<mod2> in.

[[Category:Source Code Project]]
[[Category:User-made Campaigns|*]]
[[Category:Tutorials|Mods, installing for FS2 Open]]

Installing Mods for FS2 Open

2010-01-10T14:32:25Z

Tomo: /* Installing a mod */

==Important Note==
When installing/playing a mod, it is recommended to create a new pilot for every campaign that you play. That is, one pilot for FS2, one for FSPort, etc. This will in most cases avoid the dreaded pilot file corruption problems that crop up sometimes.

== Improvements upon Retail ==
While installing mods for FreeSpace has never been hugely difficult, [[Source Code Project|FS2_Open]] has made considerable improvements to the way that they are handled. Under retail, installing more than one mod involved either installing several copies of FS2 or tiresome dragging and renaming of folders and files. Under FS2_Open, less than a minute's work when installing a mod can mean that you can swap between mods with nothing more than a click of a button.

== Installing the Media VP files ==
To truly take advantage of FS2_Open's modding features, you should install the [[MediaVP|media VP]] files to a subfolder of your FreeSpace 2 folder. Although you can call this folder anything you like, the assumption that will generally be made is that if you have put them in a folder it will be called ''mediavps'', so it is probably best to stick to that. Now that you have put the media VP files in that folder, you must go to the mod tab on the Launcher and select "mediavps" as your mod when running FS2. If you don't do this, FS2 will run with none of the media VPs' features. It will be like playing retail again.

== Installing a mod ==
Be very wary of what the readmes that come with mods tell you to do. Many mods were written before FS2_Open had these new features or by people only vaguely aware of what they do. For this reason, always remember this:

'''Do ''NOT'' install anything to Freespace2\data or into the root FreeSpace 2 folder regardless of what the instructions say.'''

Installing files into Freespace2\data or the root FreeSpace folder is the method used for retail campaigns and very old SCP builds only. This guide is about installing mods for up-to-date FreeSpace Open builds.

If you are following this guide, there is no reason to install files into either of the folders mentioned. Installing a mod to Freespace2\data means that FS2 retail and multiplayer will load the mod and probably break.

What you should do is make a separate folder for every mod within your FreeSpace 2 folder. '''If the mod consists completely of VP files, stick them all in a folder within the root FreeSpace 2 directory and you're done with this step.'''

If the mod's readme tells you to install to Freespace2\Data, make a new folder called Data within the one you just created and then follow the instructions using this new Data folder as if it were Freespace2\Data (i.e if the readme file instructs you to put a file in Freespace2\data\tables, put it in Freespace2\ModName\data\tables instead).

'''Run the Launcher, click on MOD tab, select the folder that contains all the mod's files (i.e. not ModName/Data, simply ModName) and you're ready to play.'''

(Launcher MOD tab is really setting the -mod flag, so you get the command line explained in the next section. For more info about how -mod and MOD Tab work, read [[Command-Line_Reference#-mod]]).

The last step is only required if you want the mod to be able to access the Media VP files and it doesn't already have a [[mod.ini]].
This is done by creating a new text file called [[mod.ini]] (be careful that the computer doesn't call it mod.ini.txt). Cut and paste this into the file:

[multimod] 
SecondaryList = mediavps;

:::'''PLEASE NOTE:'''
::::Older mods will use "secondrylist" and start the mod list with a leading comma. This is no longer necessary (these were workarounds for bugs that have since been fixed), and thus [[deprecation|deprecated]].

Place this file in the mod's folder, then run the game as described above.
Most, if not all, mods should already come with a ready-made mod.ini. If they don't, or if you are unsure how to create one, feel free to bug the mod's creator about it.

== Alternative method / more info ==
Alternative method by jr2 (if you don't want to use mod.ini)

Just install the MOD as mentioned above, except skip the part about making a mod.ini file. 
Then, in the launcher, under the Features tab, enter the following: 
:-mod mod1,mod2,mediavps 
where <mod1> is the mod you want to play, <mod2> is the mod that the mod you're playing depends on, and <mediavps> is the name of the folder where you've stuck the Media VP files. 

===Example 1===
To run Transcend, if I've installed it to C:\Freespace2\transcend,
and if I've installed Media VPs to C:\Freespace2\mediavps, I'd type:

:-mod transcend,mediavps

into the Features tab.

===Example 2===
To run the Solar Wars Chapter 1 mod for the Inferno Chapter 1 mod, if I've installed Solar Wars Chapter 1 to

:C:\Freespace2\solar_wars_ch1

and if I've installed Inferno Chapter 1 to

:C:\Freespace2\infr1

and if I've installed the Media VPs to

:C:\Freespace2\mediavps

I'd type:

:-mod solar_wars_ch1,infr1,mediavps

Basically, (remember, -mod mod1,mod2,mediavps) FS2_Open looks for the files it needs in <mod1>, if they are there, then it uses them, if not, it looks in <mod2>, if not there, <mediavps>, if not there, then the main FS2 directory. If there are more than one version of the file it needs, then it will use the one that it finds first, in the order that it looks for them, as seen above.

Also, you could use the mod.ini method so that mediavps is automatically appended to the list and you'd only have to type <mod1>,<mod2> in.

[[Category:Source Code Project]]
[[Category:User-made Campaigns|*]]
[[Category:Tutorials|Mods, installing for FS2 Open]]

Installing FreeSpace 2

2010-01-10T14:30:03Z

Tomo: /* Installing with only the game data files */

There are several methods to installing FreeSpace 2. The supported methods include installing from the boxed media, manually setting up the retail data, or installing using the GOG distribution.

== Installing from CDs/DVD ==

This is the default way for Windows users. Perform a normal install of FS2 if you are in Windows, or if you want to use this method in Linux or OS X, you should be able to run the installer via Wine. That exercise is beyond the scope of this article however. Once the game is installed, it leaves the movies on the installation media. You will want to copy the .mve files from the CDs/DVD to the data/movies folder inside your FS2 dir, for example C:\Games\Freespace2\data\movies\, creating the data and/or movies folders if they don't exist. If it's not already, you will want to patch the game to version 1.2 (GOTY editions already are). Now you will want to proceed with [[Installing FreeSpace 2 Open]]

== Installing with only the game data files ==

For this method, you will need a collection of .vp files. These include:

* root_fs2.vp
* smarty_fs2.vp
* sparky_fs2.vp
* sparky_hi_fs2.vp
* stu_fs2.vp
* tango1_fs2.vp
* tango2_fs2.vp
* tango3_fs2.vp
* warble_fs2.vp

Create a Freespace2 folder and put these .vp files in it. Generally these are the only .vp files that should be in your folder, save for a few exceptions. These all need to be v1.2 files. You can safely put the multiplayer misison pack and multiplayer voice pack in with these, and if you don't have the .mve cutscenes, you can put the FS2OggCutscenePack.vp file in this directory as well. Any other .vp files should typically be installed as a mod, by creating a folder in the Freespace2 folder and putting it in there. Multiple mods can be used through [[mod.ini]] files, so there's not usually a need to stick a new experimental .vp file (or other game data files) inside an already working mod folder.

You may also want to get the [http://swc.fs2downloads.com/files/hud_presets.7z HUD color presets].

[http://swc.fs2downloads.com/files/fs2_retail_data.md5 MD5 Checksums for v1.2 retail files]

== Installing from Good Old Games (GOG.com) ==

The GOG version is a single Inno Setup Installer executable file, just run it to install the game. Be sure not to install to a path with spaces in the name. At first, the GOG version installed one .vp file that was not updated to version 1.2. This should have been fixed in newer versions though.

== Installing from the .cab files on Linux/OS X ==

If you have access to the installer files from retail media, but you can't run the installer, Linux and OS X have access to a little tool called [http://sourceforge.net/project/showfiles.php?group_id=30550 Unshield] (OS X version is in Darwin/MacPorts). It can be used to extract the retail data from the cab files. Then proceed with the Installing with only game data files instructions.

== GOG Install Methods for Linux/OS X ==

If you have the GOG version and are on *nix, the install method can currently be a little rocky. You will either need Wine, or a Windows install more than likely. Either one should work with both options you have. Essentially you can either install the game, or unpack the installer. Installing should be rather straightforward, in Wine this will be a task for the reader to enjoy. Once installed you can either use the directory you installed it to or copy the .vp files listed above to the final location. Extracting the installer requires the use of the [http://innounp.sourceforge.net/ Inno Setup Unpacker] command line program, which should be very easy to use even in Wine. Download the innounp program, and use the -x command line option to extract the required files listed above. Then follow the instructions for installing with only the game data files.

[[Category:Source Code Project]]

Mod.ini (old)

2010-01-10T14:28:49Z

Tomo: /* Introduction */

==Introduction==
Mod.ini defines the options for a given Mod.
The core use for these is to allow a Mod to easily use assets from another mod, such as the MediaVPs.

The file must be called "mod.ini" and be in the main folder of the mod.
It must be in ASCII text format (not Unicode) and use Windows-style end-of-line markers.
::: '''''PLEASE NOTE''': '''Launcher v 5.4''' or later, '''must be used'''. Earlier versions had some bugs that would cause this explanation about mod.ini to fail.''

==Sections==
===Launcher===
<pre>[launcher]</pre>
Information about the Mod, displayed in the Launcher.

Attributes:
*modname = ''Name of Mod'';
*image255x112 = ''Mod bitmap.bmp'';
*infotext = ''Information about the Mod'';
*website = ''URL to Mod website, if applicable'';
*forum = ''URL to a Mod forum, if applicable'';
*mantis = ''URL to a Mod bugtracker, if applicable'';

The Mod Bitmap is displayed
===MultiMod===
<pre>[multimod]</pre>
Defines the other mods whose assets are used by this one.

Attributes:
*primarylist = ''list of mods'';
**These mods will override assets in the current Mod
*secondarylist = ''list of mods'';
**These mods will be added to the assets for the current Mod, and may be overrided by data in the current Mod.

===Settings===
<pre>[settings]</pre>
Defines other required settings.

Attributes:
*flags = ''list of additional commandline flags'';

==Examples==
===MediaVPs 3.6.10===
<pre>
[launcher]
image255x112 = FSU-MVP.bmp;
infotext = Freespace II - 3.6.10 MediaVPs;
website = http://www.hard-light.net/;
forum = http://www.hard-light.net/forums;
mantis = http://www.hard-light.net/mantis;

[multimod]
primarylist = ;
secondarylist = ;
</pre>
===Derelict===
<pre>
[launcher]
image255x112 = Derelict.bmp;
infotext = Five years have passed since the jump node to the Capella system was collapsed...;
website = http://www.3dap.com/hlp/hosted/ce/;
forum = http://dynamic.gamespy.com/~freespace/forums/forumdisplay.php?s=83686deb4fd49b5f670f6d92203b257d&forumid=89;

[multimod]
primarylist = ;
secondrylist = ,mediavps;

[settings]
flags = -spec;
</pre>

[[Category:Modding]]

Command-Line Reference

2010-01-10T14:26:21Z

Tomo: /* -mod */

The following command-line options can be chosen from the launcher.

===Graphics===
====-spec====
Enables specular mapping. Only polygons mapped with textures for which a shinemap exists will receive specular mapping; no attempt is made to generate spec maps where they do not exist. Specular maps are specified with the base map name plus "-shine" (i.e. TCov3A-shine.pcx).

====-env====
Enables environment mapping. It only works if [[Command-Line_Reference#-spec|-spec]] is also set. Environment mapping intensity will be determined from the shine map too (see [[Texturing]] for more info). At the time of this writing (build 3.6.9 RC7), environment mapping only works when the video mode is OpenGL. [[Installing FreeSpace 2 Open#Video setup|See Video setup.]]

====-glow====
Enables glowmapping. Only polygons mapped with textures for which a glowmap exists will be glowmapped. Glow maps are specified with the base map name plus "-glow" (i.e. TCov4A-glow.pcx)

====-jpgtga====
{{Note | This option is not present in builds after 3.6.9 and is now always on.}}
Enables the use of TGA and JPG file formats for image files. If a ship is showing up partially invisible, select this option.

====-pcx32====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/3eynan 2007/03/22]).}}

{{Warning|This will not improve the rendering of any ships in-game, and is usually more of a burden on performance than is worthwhile. Use at your own risk.}}
Enables PCX files to be loaded into 32-bit memory.

====-mipmap====
Enables mipmapping generation within GPU on certain kind of texture formats, (IIRC, DDS formatted textures with a power of 2 size in both width and height). 
Since the use of already mipmapped DDS textures has become common, it has become depreciated.
The quality of the generated mipmaps depends on each GPU and used driver. It is normally used with [[Command-Line_Reference#-img2dds|-img2dds]] flag.

====-nomotiondebris====
Disables motion debris.

====-2d_poof====
{{Note| This option is not present in builds post version 3.6.9.}}
Applies nebula poofs in 2d, effectively preventing them from forming intersections with ships.

====-noscalevid====
Disables fullscreen scaling of video clips.

====-missile_lighting====
Applies lighting to missiles.

====-normal====
Enables normal maps. It needs GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary normal maps (the same name of the base map plus "-normal"). DXT5_NM DDS format is needed.

====-3dshockwave====
Enables 3D Shockwaves. This only has any effect when both a 2d and 3d shockwave effect are present, otherwise the only available effect is used.

====-rlm====
{{Note| This option is not present in builds after [http://tinyurl.com/2yndle 2005/09/30] and is now always on.}}
Enables more accurate lighting model for OpenGL mode.

----

===Game Speed===
====-img2dds====
Converts all images to DDS (compressed) format. Decreases memory usage but potentially reduces image quality.

====-no_vsync====
Disables vertical sync.

====-cache_bitmaps====
Caches bitmaps between missions, which will ideally reduce the load-time from one mission to another.

===HUD===
====-dualscanlines====
Adds a second pair of scanning lines to the target window when scanning an object.
====-targetinfo====
Displays target info, such as name and class, beside the targeted object.
====-orbradar====
Enables 3D radar (the Orb). 3D radar will replace the standard 2D version.
====-ballistic_gauge====
Adds an ammo gauge to the HUD when armed with a ballistic weapon.
====-rearm_timer====
Displays time remaining until rearm and repair from a support ship is complete.

===Gameplay===
====-smart_shields====
{{Note| This option has been moved to [[Ai_profiles.tbl]] table since 3.6.9. builds. It doesn't exist as a flag anymore.}}
Enables "smart" shield recharging. Shield recharge is distributed to the most damaged shield quadrant instead of being distributed equally across the entire shield and be wasted when a quadrant is full.
====-ship_choice_3d====
Uses ship models in ship selection window. It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their ships. In this situation, and if it is not used, the game will probably crash to desktop in the ship selection window.
====-weapon_choice_3d====
Uses weapon models in weapon loadout window for secondary weapons (missiles and bombs). It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their secondary weapons. In this situation, and if it is not used, the game will probably crash to desktop in the weapon loadout window.
====-3dwarp====
Use full geometry for the subspace warp effect.
====-warp_flash====
Enable a flash at warp in and warp out.
====-no_ap_interrupt====
Tells the game to not allow players to interrupt an autopilot already-in-progress.
====-tbp====
Enable feature set for The Babylon Project. This option also forces the Enable 3d Shockwave and Use 3d Models for Weapon Selection options as of 3.6.10 testing builds r4983 or higher.
====-wcsaga====
Enable feature set for The Wing Commander Saga. 
It does the following changes to the normal FS2 engine behavior:
* It removes -class name in the briefing ship render window, (the window that appears when ship icons are clicked).
* It removes enemy names ingame for wings of ships.
* Enemies can scream when dying. (Without the flag only friendlies scream).

===Audio===
====-snd_preload====
Preload mission sounds. Useful in preventing game stuttering when sounds are played for the first time.
====-nosound====
Disables all sounds.
====-nomusic====
Disables music only.

===Multiplayer===
====-standalone====
Creates a standalone server.
====-startgame====
Once you launch and choose a pilot within the game, you will immediately have begun to host a game. This can be used in conjunction with several options to customize the game you create: -closed, -restricted, -password, -gamename, -allowabove, and -allowbelow. -startgame has no effect when -standalone is used.

See related: [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]] [[Command-Line_Reference#-gamename|-gamename]] [[Command-Line_Reference#-allowabove|-allowabove]] [[Command-Line_Reference#-allowbelow|-allowbelow]]

====-closed====
Hosts a new game in a closed state, where no one can join until the in-game "Close" button is cleared. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -restricted or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]]

====-restricted====
Hosts a new game in a restricted state. The host is presented with option to accept or deny each client's request to join the game. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-password|-password]]

====-multilog====
Creates a log file with a summary of packets sent and received in multiplayer games. The file is saved as \data\multi.log within the active mod folder—or with main data folder if no mod is active.

====-clientdamage====
This feature is not available in current builds.

====-mpnoreturn====
Disables return to the flight deck screen after a mission completes.

===Troubleshooting===
====-fixbugs====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/3eynan 2007/03/22]).}}
Originally used to disable certain crashing behavior as a stop-gap measure.

====-nocrash====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/3eynan 2007/03/22]).}}
Originally used to disable certain crashing behavior as a stop-gap measure.

====-oldfire====
This feature is not available in current builds.

====-nohtl====
{{Warning| Enabling this will significantly reduce performance.}}
Reverts to software rendering mode.

====-no_set_gamma====
Disables the gamma settings in the options screen.
====-nomovies====
Disables all video playback.
====-noparseerrors====
Disables some parsing warnings and makes other parse errors non-fatal. Do not rely on this when creating new tables. The errors are there for a reason.
====-safeloading====
Loads missions the old way. Typically safer, but slower.
====-query_speech====
Determines if the current build includes text-to-speech.
====-d3d_bad_tsys====
Enable inefficient texture system.
====-novbo====
Disables OpenGL VBO.
====-noibx====
Disables IBX caching of model geometry data. This will dramatically increase load times, but will help troubleshoot a model if one is working incorrectly.
====-loadallweps====
Load all weapons, even those not used.
====-no_glsl====
Disables the use of GLSL rendering (OpenGL shaders). The game will revert to legacy fixed render pipeline. Please note that Normal and Height map effects will be unavailable.

===Experimental===
====-ingame_join====
Enables ingame joining in multiplayer. FIXME: Host option?
====-voicer====
Windows-only. Enables voice-recognition for wingmen commands. Must be specifically compiled into a build in order for it to be available; 3.6.10 final includes the feature. See [[Voice Recognition]] for more details.

====-alpha_env====
{{Note| This option is not present in builds post version 3.6.9. In current builds this effect is always on}}
Enables alpha environment mapping. OpenGL only. Environment mapping intensity will be determined from the alpha channel of specular maps.
====-decals====
Enables damage decals. 
(Decals have been disabled in builds after May 4, 2006)
====-tga16====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/yr8tub 2006/04/05]).}}
Originally used to converts TGA images to 16-bits in order to reduce memory footprint (at the expense of image quality), superseded by [[Command-Line_Reference#-closed|-img2dds]].
----

===Development Tools===
====-fps====
Displays current frames per second.
====-pos====
Displays current position coordinates of camera.
====-window====
Runs the game in a window. No check to make sure that resolution is no higher than your desktop resolution, so be careful.
====-timerbar====
Displays a timing bar across the top of the screen. Timebar format varies by build.
====-stats====
Shows total and free physical memory, virtual memory and system pagefile.

====-coords====
Shows coordinates of the mouse cursor.
====-show_mem_usage====
Shows detailed RAM usage in HUD.

The meaning of the info displayed in the upper right corner is:

'''DYN''' = dynamic memory, basically anything that's been allocated by the vm_* memory functions. This does NOT indicate total memory usage but does account for most of it.

'''POF''' = model memory, how much memory is being used by models (does not include textures)

'''C-BMP, BMP''' = bmpman memory, how much is used by the textures/images that are loaded. C-BMP means that you are using -cache_bitmaps and it will try to keep textures in memory between level loads and as the new level is loading it will keep what it needs and unload what it doesn't. Can greatly increase level loading speed, but does so at the cost of memory between level loads. This does not increase overall memory usage though, only during the loading screen. BMP means that it is not cached and all textures are unloaded from memory at the start of level load and all needed textures are then loaded from the disk again.

'''S-RAM''' = sound memory, how much is used by the sounds loaded in memory at the time. This counts static sounds only (from sounds.tbl, etc.) and not streaming sounds (music, voices, briefing stuff, etc).

'''V-RAM''' = approximate memory usage of video textures. This does not mean that your card has this much memory, and can report higher numbers that your card actually has memory. For OpenGL it also includes some of the geometry data, but this number does not reflect the total memory that your video card is using. It only reports how much data the game has purposefully loaded into API memory (meaning it could be in system memory, video card memory, or AGP memory).

''(It only works with debug builds, not with release builds).''

====-pofspew====
Reads all objects in the pof file of the selected mod, and creates an ibx cache file for each object in the data/cache folder for that mod. 
Details for each object are output to a pofspew.txt file created in the data folder. 
Otherwise, ibx files are created in game before each mission.

====-tablecrcs====
{{Sectstub}}

====-missioncrcs====
{{Sectstub}}

====-dis_collisions====
Disables all collisions.
====-dis_weapons====
Disables weapons rendering.
====-output_sexps====
Outputs SEXPs to sexps.html.
====-output_scripting====
Outputs scripting to scripting.html.
====-nograb====
Unix only. Disables focus grabbing in a window.
==Other==
The following options are not available as checkboxes in the launcher. Many require parameters, which follow the flag separated by a space. The prototype for use in this case is "-option argument"

===Lighting===
These factors can dramatically alter the atmosphere of the game. [[Sample Lighting Settings|This page]] has some sample lighting settings with screenshots.

====-ambient_factor====
This must be entered into the "Custom flags" field. This is a multiplier applied to the intensity of ambient lighting. Ambient light is lighting applied to all parts of a ship. FS2's standard value is 120. Try 75 for a good and realistic looking value. However, that is relative.

====-no_emissive_light====
By default, all ships in FS2 have a light generated on their own, it is more or less similar to a minimal amount of -ambient_factor. This feature was implemented to help the player seeing the ships over a black background. This flag disables this feature. Use it with a low -ambient_factor value to obtain an ultra-realistic dark looking.

====-spec_exp====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts the size of the shiny spot on ships. Higher number mean smaller spots. Default is 16. However, 11 is recommended. This is a relative value.

====-spec_point====
This must be used with the -spec command line parameter and must be entered into the
"Custom flags" field. Adjusts how much laser weapons contribute to specular highlights. Higher number mean greater contributions. Default is 1.0. However, 0.6 is recommended. This is a relative value.

====-spec_static====

This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much suns contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, is 0.8 recommended. This is a relative value.

====-spec_tube====

This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much Beam Weapons contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, 0.4 is recommended. This is a relative value.

====-ogl_spec====
'''''OpenGL Only'''''. Takes a numerical argument. This value changes the basic shininess of the specular light in OpenGL. A lower value reduces the overall intensity of the light making it broader and less powerful. A higher value makes it more focued and brighter. The default value is 80, and the usable range is 0 to 128 (clamped). The original default value was 60, but it was raised to behave more D3D like.

===Graphics===

====-height====
Enables height maps (parallax mapping). It only works if [[Command-Line_Reference#-normal|-normal]] is also set. It also needs GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary height maps (with the same name than base map plus "-height").

====-clipdist====
Changes the distance from the viewpoint for the near-clipping plane.

Takes one argument decimal specifying the distance to the near-clipping plane.

====-res====
Allows you to specify a resolution if the desired one cannot be set in the Launcher.
For example, -res 1920x1080 would run the game in 1920 x 1080 resolution. Since it requires an argument, it needs to be entered as a custom flag when using the Launcher. The "Run at specified resolution" option the Launcher gives is essentially this, but without being able to actually specify a resolution, it doesn't work.

===Gameplay===
====-mod====
{{Note| Please note that the ''[[mod.ini]]'' file is a feature exclusive to the Windows Launcher.}}
Specifies in which folders inside FreeSpace 2 directory, the game looks for all the game data (models, missions, textures, tables, ...). Retail version only looks inside ''Freespace2/data/'' structure and ''Freespace2/vp archives''.

This flag allows installing several different mods that modify retail behavior, and switching between them without needing to erase files or having undesired cross effects. Each mod should be installed in its own folder.

It takes one argument string: the chain of names of the used directories. Comma (''',''') must be used as separator. In this way, '''-mod dir1,dir2,dir3,...,dirx''' causes the game to use the following directory precedence:

#Freespace2/dir1/
#Freespace2/dir2/
#Freespace2/dir3/
# ... (the rest of the typed directories) ...
#Freespace2/dirx/
#Freespace2/

This flag can be indirectly set, (and it is normally set), through Launcher MOD tab and [[mod.ini]] file.

Within this Launcher tab you can select one directory, (let's call it ''moddir''), so the flag is at least set to '''-mod moddir'''.
If ''Freespace2/moddir/[[mod.ini]]'' exists it will be used to modify the -mod flag, too.

For further details, see '''[[mod.ini]]'''

'''Data precedence'''

As already said, within the different directories, the data precedence is set by the specified order in the -mod flag. The lowest priority goes to the Freespace2 installation directory.

Inside each directory, data precedence is the following:

#Individual files located in ''Current_dir/data/'' subdir structure. See [[FS2_Data_Structure|FS2 Data Structure topic]] for deeper info about the different folders and contents this structure has.
#Files located inside vp archives. (These vp archives are "similar" to zip archives. They just contain other files and folders. Moreover, files have to be stored using the same ''data/'' structure used outside it). Vp archives are read in alphabetical order, so aaa.vp files have higher priority than aab.vp files and so on.

The highest priority file overrides the rest of them. In this way, if you have a ''Mission.fs2'' inside ''Freespace2/Pri1/data/missions/'' it doesn't matter how this ''Mission.fs2'' is inside ''Freespace2/Pri1/aaa.vp'', ''Freespace2/Pri1/aab.vp'', ... or ''Freespace2/data/missions/''. This data precedence allows the user to quickly replace old files by corrected or enhaced ones adding them in a higher priority place.

'''Additional notes'''
# As derived from the explanation, the exact names for directories or vp archives are actually irrelevant. It only matters the directory order inside -mod flag argument and the alphabetical order for vp archives inside each used directory.
# This flag is also used by [[Portal:FRED|FRED]]. So if there is special mod info, (like backgrounds maps, ship models or whatever), it must be typed, (''Fred2_Open_r.exe -MOD whatever''), or FRED won't be able to use it. No Launcher MOD tab is available for this use.
# Be careful while typing the directory names in the flag argument or inside mod.ini files. The program doesn't check if the typed directories exist. If they do not exist, they are just ignored. No warnings, no errors, no messages at all.

{{Warning| '''Priority and Texture Formats'''

''Obsolete behavior - Until FS2_open v3.6.9.:''

FS2_Open can use several file formats in textures: [http://en.wikipedia.org/wiki/PCX PCX], [http://en.wikipedia.org/wiki/DirectDraw_Surface DDS], [http://en.wikipedia.org/wiki/JPG JPG] and [http://en.wikipedia.org/wiki/TGA TGA]. Make sure you keep the format when you update your texture. For example if you update the old ''TextureOfMyFighter.tga'', do not save it as ''TextureOfMyFighter.dds'' in a higher priority place, because there is a chance of the game loading the old one despite of all.

The reason to do this is that, loading process (including priorities) is applied firstly for a kind of textures (TGAs), then for another kind (JPGs), and so on. This behavior can lead to situation where your new, updated and higher priority placed texture is not read because the format of the older one.

''New behavior - From FS2_open v3.6.10. (including previous beta testing releases):''

The former issue has been fixed. Now texture format priority is only applied within the same location. In this ''strange'' situation it goes DDS -> TGA -> JPG -> PCX. Examples:
* ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.dds'' is loaded instead of ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.tga''.
* But your improved ''/Freespace2/data/maps/MyTexture.xxx'' will override them both despite of its format.
In this way, when you update any texture, you don't have to pay attention to its original format. Just place it in a higher priority place.

Nevertheless, global priority is kept between animated and static textures. Because of their management, animated textures (ANIs and EFFs) are looked for BEFORE static ones. In this way there's no way to update an animated texture with a static one (an obsolete ANI is always going to be loaded before the newer DDS version). The solution: use an updated EFF with just one frame.

}}

====-fov====
Specifies the Field of View for the player eyepoint.

Takes one argument decimal specifying the angle of the viewing cone in radians, from 0 to 2*pi

You can set the cone of view making things look bigger/smaller. The problem with this is that if you choose a small FOV, you will have a squashed look on the edges of your screen - stretched edges with a too high FOV. It is recommended to change the FOV as FS2 normally has some perspective distortion at the screen edges (FOV too high). Set the FOV to something like 0.39 - it will fix the distortion problem, and (as a nice side-effect) will make everything look bigger and more realistic scale-wise. On the other hand, it also stretches the backgrounds - this is usually not a big issue, but it does get annoying if using a skybox.
The default is 0.75, if you go higher, you'll get the fish-eye effect. Feel free to experiment. This must be entered into the "Custom flags" field

===Multiplayer===
====-gamename====
Specifies the name of the game to be created by the host. This only works when used in conjunction with -startgame.

Takes one argument string, the name to be assigned to the game being created.

This argument does nothing when used with -standalone. To set the name for a standalone server, see [[Multiplayer(Main)#Standalone Servers|Standalone Servers]].

See related:   [[Command-Line_Reference#-startgame|-startgame]]   [[Multiplayer(Main)#Standalone Servers|Standalone Servers]]

====-password====
Specifies the password for a standalone server. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -restricted.

Takes one argument string, the required password for the game being created.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]]

====-allowabove====
Specifies a player's minimum rank for joining a game. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking above which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-allowbelow====
Specifies a player's maximum rank for joining a game on a standalone server. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking below which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-port====
Specifies the port on which to host a game or serve a standalone game.

Takes one argument integer, the port on which the host will listen for clients.

====-connect====
{{Sectstub}}

====-timeout====
{{Sectstub}}

====-cap_object_update====
Caps the maximum object update the server will respond to regardless of what the client has set. If the client is set to request high object updates but the server is capped to low, then that's all the client will get.

Takes one argument integer (0 to 3) which corresponds to the object update cap (With 0 being low and 3 being LAN).

[[Category:Lists]]
[[Category:Source Code Project]]

Mod.ini (old)

2010-01-10T14:19:23Z

Tomo: /* Introduction */

==Introduction==
Mod.ini defines the options for a given Mod.
The core use for these is to allow a Mod to easily use assets from another mod, such as the MediaVPs.

The file must be called "mod.ini" and be in the main folder of the mod.
::: '''''PLEASE NOTE''': '''Launcher v 5.4''' or later, '''must be used'''. Earlier versions had some bugs that would cause this explanation about mod.ini to fail.''

==Sections==
===Launcher===
<pre>[launcher]</pre>
Information about the Mod, displayed in the Launcher.

Attributes:
*modname = ''Name of Mod'';
*image255x112 = ''Mod bitmap.bmp'';
*infotext = ''Information about the Mod'';
*website = ''URL to Mod website, if applicable'';
*forum = ''URL to a Mod forum, if applicable'';
*mantis = ''URL to a Mod bugtracker, if applicable'';

The Mod Bitmap is displayed
===MultiMod===
<pre>[multimod]</pre>
Defines the other mods whose assets are used by this one.

Attributes:
*primarylist = ''list of mods'';
**These mods will override assets in the current Mod
*secondarylist = ''list of mods'';
**These mods will be added to the assets for the current Mod, and may be overrided by data in the current Mod.

===Settings===
<pre>[settings]</pre>
Defines other required settings.

Attributes:
*flags = ''list of additional commandline flags'';

==Examples==
===MediaVPs 3.6.10===
<pre>
[launcher]
image255x112 = FSU-MVP.bmp;
infotext = Freespace II - 3.6.10 MediaVPs;
website = http://www.hard-light.net/;
forum = http://www.hard-light.net/forums;
mantis = http://www.hard-light.net/mantis;

[multimod]
primarylist = ;
secondarylist = ;
</pre>
===Derelict===
<pre>
[launcher]
image255x112 = Derelict.bmp;
infotext = Five years have passed since the jump node to the Capella system was collapsed...;
website = http://www.3dap.com/hlp/hosted/ce/;
forum = http://dynamic.gamespy.com/~freespace/forums/forumdisplay.php?s=83686deb4fd49b5f670f6d92203b257d&forumid=89;

[multimod]
primarylist = ;
secondrylist = ,mediavps;

[settings]
flags = -spec;
</pre>

[[Category:Modding]]

General hints (FRED)

2010-01-10T14:09:17Z

Tomo: /* Using FRED with mods */

Here are some '''general FREDding hints''' that do not require separate articles to elaborate, from beginner level until intermediate.

*Use the Y-axis (height) and rotate most of your ships on one or more of the axes to give a more realistic feeling.
*Use the Selection Lock (Spacebar) if you have selected all the ships you want to move or rotate. This will make sure you do not select an unwanted craft by accident. Press Spacebar once more to disable Selection Lock.
*If you want a directive to appear only after a specified event, use event chaining:
**Collect all the triggering conditions in one event. Chain the next event (which is the actual directive) to the previous event with a delay of at least 1 second.
**This will make it sure the event will not appear sooner than desired. This is especially useful if you want Command to order the desctruction/capture/inspection of a ship.
*Use the designer's notes of the Mission Specs Editor (SHIFT-N) as a reminder for yourself. There are some things that you want to be in your mission only temporarily, for testing purposes such as enabling No Traitor if you want to test if a ship sends the right message if its hull dropos below 50%.
*Using keyboard shortcuts makes editing more convenient.
*If you do not want a ship to open fire, simply use the turret-lock-all SEXP instead of disarming all the turrets manually.
*If you want to use a special, special-case support ship, you have to make changes in the [[ships.tbl|ship tables]]. You cannot simply place a support ship and disallow all player orders.
*Always remove player orders for ship classes other than fighters or bombers. By default, the player can give orders to transports and above. If you give the 'Attack my ship' order to a transport that is supposed to board and capture a ship, it will not follow its default orders until the player-given orders are accomplished.
*If you do not want a ship destroyed, but you want to make its subsystems destroyable, use the [[ship-guardian]] SEXP.
*Increasing/decreasing the skill level of single turrets also affects the given turret's rate of fire. It is advised to increase the level of sentry guns by at least one rank.
*Pressing TAB while having multiple ships selected changes the central point of rotation. If you start rotating, that ship will be the center of the circle your ships will be rotated around. The same is true for moving, the selected 'central' ship will be moving with the cursor.
*If you get lost on the grid, press SHIFT-Z. Or, zoom on any of the ships by selecting the fighter in the Selection Menu (H) and pressing ALT-Z.
*Wingmen initial orders is limited, but using the add-goal SEXP removes this limitation.
*Placing a waypoint into the center of a jump node enables you to measure distances between any ships and the jump node. The waypoint and the jump node must share the same coordinates. Technically, the engine measures the distance between the assigned ship(s) and the waypoint, but since the center of the node and the waypoint are at the same position, you can measure distance between ships and the jump node.
*Colored text can be used in the Command briefing, but cannot be used in the debriefing.
*An ideal mission length ranges between five and eleven minutes. It is not advised to make a mission longer, as FreeSpace players are not used to flying for more than ten minutes.
*For better performance, use the wireframe view mode. The textured view mode eats up more memory and makes the mission editor run slower.
*If you want a ship just to suddenly appear, use the No Warp Effect feature in the arrival cue section of the Ship Editor. If the departure cue has the No Warp Effect set, then the ship will suddenly disappear. This is useful for nebula missions. Beware of using the ship-vanish SEXP: ships that vanish do not count as "departed", so the "has-departed-delay <ship that vanishes using ship-vanish>" will not trigger.
*Believe it or not, the EMP effect also works on AI-controlled ships. Bear this in mind while creating nebula missions.
*Players usually start by increasing the throttle to maximum. Set the player's speed to 100% by default in the Initial Status options if it's likely that most players would start the mission by accelerating.
*In case one or more ships in a wing departs without the departure cue becoming true, the wing will not be considered departed. This means if you order one (or all) ships from Beta wing to leave the area and there is an event which becomes true if Beta wing has departed, the event will become incomplete until you restart the mission.
*The "Neutral" IFF is hostile to the player. If you want the "Hostile", "Neutral" and "Friendly" sides to attack each other, set the All teams at War option in the Mission Specs Editor.
*You can manually set the player traitor but using the change-iff SEXP on the player's ship to make the player "Neutral" (FreeSpace Open introduced the "Traitor" IFF).
*The Protect Ship option is not completely reliable. The AI may still attack those ships. Rather make that ship invulnerable. It looks daft, but this is the best solution to make the AI not lose the mission for the player by destroying any ships which are supposed captured or not destroyed. You can also use the change-iff to make the ship Friendly (as it was used in [[First Strike]]). Hostiles will still attack that ship, so make sure they ignore it.
*Changing the order of events in FRED is not recommended. Such a move will confuse the game engine, and weird mission flaws will come up. [[Editing a mission in a text editor#Changing Event hierarchies|Use a text editor]] instead for this purpose. You won't need to change the order of in-mission events anyway, except for chained events.

== Using FRED with mods ==
*Note that FRED2 Open uses the same mod usage as FS2 Open, that is,
-mod mod1,mod2,mediavps
where <mod1> is the name of the mod being played, <mod2> is the name of the mod that the mod being played depends on, and <mediavps> is where the Media VP files are put. See the wiki instructions Getting Started >
Installing mods for fs2_open >
Alternative method / more info
for complete details. Also, I've heard (and FRED2 Open says) that you should run with the -fredhtl option.
So, say you were creating a mod for the FreeSpace Port (for a mission during the Great War)
You'd use something like the following, depending on where you installed FSPort and the Media VPs: (note the quotes)
"\<whatever dir Fred is in>\FRED2_build_date_whatever.exe" -mod fsport,mediavps -fredhtl
This would allow you to use FS1 weapons, ships, etc. Note you might not need mediavps if you use the [[mod.ini]] options mentioned in the installing mods wiki mentioned above, or if you weren't creating a mission for FS Open.

==See also==
[[Typical FREDding mistakes]]

[[Category:FRED Tips]]

Mod.ini (old)

2010-01-10T14:01:46Z

Tomo:

==Introduction==
Mod.ini defines the options for a given Mod.
The core use for these is to allow a Mod to easily use assets from another mod, such as the MediaVPs.

The file must be called "mod.ini" and be in the main folder of the mod.

==Sections==
===Launcher===
<pre>[launcher]</pre>
Information about the Mod, displayed in the Launcher.

Attributes:
*modname = ''Name of Mod'';
*image255x112 = ''Mod bitmap.bmp'';
*infotext = ''Information about the Mod'';
*website = ''URL to Mod website, if applicable'';
*forum = ''URL to a Mod forum, if applicable'';
*mantis = ''URL to a Mod bugtracker, if applicable'';

The Mod Bitmap is displayed
===MultiMod===
<pre>[multimod]</pre>
Defines the other mods whose assets are used by this one.

Attributes:
*primarylist = ''list of mods'';
**These mods will override assets in the current Mod
*secondarylist = ''list of mods'';
**These mods will be added to the assets for the current Mod, and may be overrided by data in the current Mod.

===Settings===
<pre>[settings]</pre>
Defines other required settings.

Attributes:
*flags = ''list of additional commandline flags'';

==Examples==
===MediaVPs 3.6.10===
<pre>
[launcher]
image255x112 = FSU-MVP.bmp;
infotext = Freespace II - 3.6.10 MediaVPs;
website = http://www.hard-light.net/;
forum = http://www.hard-light.net/forums;
mantis = http://www.hard-light.net/mantis;

[multimod]
primarylist = ;
secondarylist = ;
</pre>
===Derelict===
<pre>
[launcher]
image255x112 = Derelict.bmp;
infotext = Five years have passed since the jump node to the Capella system was collapsed...;
website = http://www.3dap.com/hlp/hosted/ce/;
forum = http://dynamic.gamespy.com/~freespace/forums/forumdisplay.php?s=83686deb4fd49b5f670f6d92203b257d&forumid=89;

[multimod]
primarylist = ;
secondrylist = ,mediavps;

[settings]
flags = -spec;
</pre>

Mod.ini (old)

2010-01-10T14:01:18Z

Tomo: Created page with '==Introduction== Mod.ini defines the options for a given Mod. The core use for these is to allow a Mod to easily use assets from another mod, such as the MediaVPs. The file must…'

==Introduction==
Mod.ini defines the options for a given Mod.
The core use for these is to allow a Mod to easily use assets from another mod, such as the MediaVPs.

The file must be called "mod.ini" and be in the main folder of the mod.

==Sections==
===Launcher===
<pre>[launcher]</pre>
Information about the Mod, displayed in the Launcher.

Attributes:
*modname = ''Name of Mod'';
*image255x112 = ''Mod bitmap.bmp'';
*infotext = ''Information about the Mod'';
*website = ''URL to Mod website, if applicable'';
*forum = ''URL to a Mod forum, if applicable'';
*mantis = ''URL to a Mod bugtracker, if applicable'';

The Mod Bitmap is displayed
===MultiMod===
<pre>[multimod]</pre>
Defines the other mods whose assets are used by this one.

Attributes:
*primarylist = ''list of mods'';
**These mods will override assets in the current Mod
*secondarylist = ''list of mods'';
**These mods will be added to the assets for the current Mod, and may be overrided by data in the current Mod.

===Settings===
<pre>[settings]</pre>
Defines other required settings.

Attributes:
*flags = ''list of additional commandline flags'';

==Examples==
===MediaVPs 3.6.10===
<pre>
[launcher]
image255x112 = FSU-MVP.bmp;
infotext = Freespace II - 3.6.10 MediaVPs;
website = http://www.hard-light.net/;
forum = http://www.hard-light.net/forums;
mantis = http://www.hard-light.net/mantis;

[multimod]
primarylist = ;
secondarylist = ;
</pre>
===Derelict===
<pre>
[launcher]
image255x112 = Derelict.bmp;
infotext = Five years have passed since the jump node to the Capella system was collapsed, sealing off a massive wave of Shivan Juggernaughts from pushing further into GTVA space. The supernova and subsequent nebula hang like a growing scar throughout the GTVA as light from that event continues to spread across our worlds. You are to take a new tour of duty with the 212th Silver Scythes squadron in the Tau Sigma cluster, a remote group of systems beyond the Altair Jump Node. These are mining colonies, and while the GTVA presence is small, it is nontheless important.;
website = http://www.3dap.com/hlp/hosted/ce/;
forum = http://dynamic.gamespy.com/~freespace/forums/forumdisplay.php?s=83686deb4fd49b5f670f6d92203b257d&forumid=89;

[multimod]
primarylist = ;
secondrylist = ,mediavps;

[settings]
flags = -spec;
</pre>

FreeSpace 2 Mission File Format

2009-09-24T19:51:51Z

Tomo: /* $Formula: */

FS2 files are simple text files defining how FS2 will 'execute' a given mission.
It refers to external files for the actual assets used in the mission, including [[Model files]] and [[Tables]].

==General Format==
File section headers start with the "#" character.
Each file section should be separated by a blank line.

Statements start with either the "$" or "+" characters, and may last for multiple lines.
Comments are indicated by ";!", and continue to the end of the line.

Data finishes at "#End"

==Sections==

===#Mission Info===
*Defines that the file is a Mission file.

===#Command Briefing===
*Defines the Command Briefing section of the briefing. If no command briefing is required, leave this blank.

===#Briefing===
*Defines the Mission Briefing. Leaving this blank will cause 'no briefing' to be shown instead of a mission briefing.

----

===#Players===
*Defines the players for the mission. At least one player must be defined.
----
===#Objects===
*Defines all the objects in the mission and their initial state.
*This includes all ships (including the player ships), installations and other objects.
*Does not include asteroid (debris) fields.
----
===#Wings===
*Defines all wings in the mission, friendly and hostile
----
===#Events===
*The SEXPs that make up the Events List.

====$Formula:====
<pre>$Formula: ( SEXP_TEXT
FIRST_OPERAND
SECOND_OPERAND
)
+Name: Event name
+Repeat Count: 1
+Interval: 1
+Chained: 30 ;! Indicates that Event is chained to the previous Event and the chain time in seconds.
+Team: 0
</pre>
----

===#Goals===
*The mission directives
----
===#Waypoints===
----
===#Messages===
----
===#Reinforcements===
----
===#Background bitmaps===
----
===#Asteroid Fields===
----
===#Music===
----
===#End===
*The end of the file.

FreeSpace 2 Mission File Format

2009-09-24T19:50:07Z

Tomo:

FS2 files are simple text files defining how FS2 will 'execute' a given mission.
It refers to external files for the actual assets used in the mission, including [[Model files]] and [[Tables]].

==General Format==
File section headers start with the "#" character.
Each file section should be separated by a blank line.

Statements start with either the "$" or "+" characters, and may last for multiple lines.
Comments are indicated by ";!", and continue to the end of the line.

Data finishes at "#End"

==Sections==

===#Mission Info===
*Defines that the file is a Mission file.

===#Command Briefing===
*Defines the Command Briefing section of the briefing. If no command briefing is required, leave this blank.

===#Briefing===
*Defines the Mission Briefing. Leaving this blank will cause 'no briefing' to be shown instead of a mission briefing.

----

===#Players===
*Defines the players for the mission. At least one player must be defined.
----
===#Objects===
*Defines all the objects in the mission and their initial state.
*This includes all ships (including the player ships), installations and other objects.
*Does not include asteroid (debris) fields.
----
===#Wings===
*Defines all wings in the mission, friendly and hostile
----
===#Events===
*The SEXPs that make up the Events List.

====$Formula:====
<pre>$Formula: ( SEXP_TEXT
FIRST_OPERAND
SECOND_OPERAND
)
+Name: Event name
+Repeat Count: 1
+Interval: 1
+Chained: 30 ;! Optional indicates that SEXP is chained to previous
+Team: 0
</pre>
----
===#Goals===
*The mission directives
----
===#Waypoints===
----
===#Messages===
----
===#Reinforcements===
----
===#Background bitmaps===
----
===#Asteroid Fields===
----
===#Music===
----
===#End===
*The end of the file.

FreeSpace 2 Mission File Format

2009-09-24T19:44:58Z

Tomo: Created page with 'FS2 files are simple text files defining how FS2 will 'execute' a given mission. It refers to external files for the actual assets used in the mission, including POF and TBL file…'

FS2 files are simple text files defining how FS2 will 'execute' a given mission.
It refers to external files for the actual assets used in the mission, including POF and TBL files.

==General Format==
File section headers start with the "#" character.
Each file section should be separated by a blank line.

Statements start with either the "$" or "+" characters, and may last for multiple lines.
Comments are indicated by ";!", and continue to the end of the line.

Data finishes at "#End"

==Sections==

===#Mission Info===
*Defines that the file is a Mission file.

===#Command Briefing===
*Defines the Command Briefing section of the briefing. If no command briefing is required, leave this blank.

===#Briefing===
*Defines the Mission Briefing. Leaving this blank will cause 'no briefing' to be shown instead of a mission briefing.

----

===#Players===
*Defines the players for the mission. At least one player must be defined.
----
===#Objects===
*Defines all the objects in the mission and their initial state.
*This includes all ships (including the player ships), installations and other objects.
*Does not include asteroid (debris) fields.
----
===#Wings===
*Defines all wings in the mission, friendly and hostile
----
===#Events===
*The SEXPs that make up the Events List.

====$Formula:====
<pre>$Formula: ( SEXP_TEXT
FIRST_OPERAND
SECOND_OPERAND
)
+Name: Event name
+Repeat Count: 1
+Interval: 1
+Chained: 30 ;! Optional indicates that SEXP is chained to previous
+Team: 0
</pre>
----
===#Goals===
*The mission directives
----
===#Waypoints===
----
===#Messages===
----
===#Reinforcements===
----
===#Background bitmaps===
----
===#Asteroid Fields===
----
===#Music===
----
===#End===
*The end of the file.

ASCII or text files

2009-09-24T19:20:37Z

Tomo: /* FS2 */

These are ASCII text files that can be opened in any pure ASCII editor, like Notepad or Wordpad. Avoid saving them in word processors such as Microsoft Word, as the formatting information may screw the file up. Many FS data files, such as tables, FS1 or FS2 missions, and campaigns can be read as TXT files.

==FreeSpace player file formats==

===PLR===

===PL2===

==FreeSpace mission file formats==

===FS2===
Files with FS2 extension are mission files for FreeSpace 2. Can be opened with the proper version of [[FRED]] or any text viewer.

See [[FS2 Mission File Format]]

===FSM===
The FreeSpace 1 mission file format. Almost identical to '''FS2''' mission files used by FreeSpace 2, although the FS2 format has several additional features as well as some minor differences in syntax. .FSM files can be loaded by FreeSpace 2, although .FS2 files cannot be loaded by FreeSpace 1. Given that ship classes, briefing icons, head animations, and other nuances were updated or tweaked in FreeSpace 2, however, it is advisable to use the Import Mission feature in FRED2_Open rather than opening a .FSM file directly.

==FreeSpace campaign file formats==

===CS2===
Stores campaign information

===CSG===
Stores campaign progress information

'''''Obsolete''''', replaced with '''CS2'''

===CSS===
Stores campaign scoring information

'''''Obsolete''''', replaced with '''CS2'''

==FreeSpace table file formats==

===TBL===
Table file containing game data

See [[Tables|tables]]

===TBM===
Modular table file containing game data

See [[Tables|tables]]

==Other ASCII or text file formats==

===EFF===
Files containing information of effect animations

See [[Multimedia_Files|multimedia files]]

[[Category:File Types]]

ASCII or text files

2009-09-24T19:15:53Z

Tomo: /* FS2 */

These are ASCII text files that can be opened in any pure ASCII editor, like Notepad or Wordpad. Avoid saving them in word processors such as Microsoft Word, as the formatting information may screw the file up. Many FS data files, such as tables, FS1 or FS2 missions, and campaigns can be read as TXT files.

==FreeSpace player file formats==

===PLR===

===PL2===

==FreeSpace mission file formats==

===FS2===
Files with FS2 extension are mission files for FreeSpace 2. Can be opened with the proper version of [[FRED]] or any text viewer.

[[FS2 Mission File Format]]

===FSM===
The FreeSpace 1 mission file format. Almost identical to '''FS2''' mission files used by FreeSpace 2, although the FS2 format has several additional features as well as some minor differences in syntax. .FSM files can be loaded by FreeSpace 2, although .FS2 files cannot be loaded by FreeSpace 1. Given that ship classes, briefing icons, head animations, and other nuances were updated or tweaked in FreeSpace 2, however, it is advisable to use the Import Mission feature in FRED2_Open rather than opening a .FSM file directly.

==FreeSpace campaign file formats==

===CS2===
Stores campaign information

===CSG===
Stores campaign progress information

'''''Obsolete''''', replaced with '''CS2'''

===CSS===
Stores campaign scoring information

'''''Obsolete''''', replaced with '''CS2'''

==FreeSpace table file formats==

===TBL===
Table file containing game data

See [[Tables|tables]]

===TBM===
Modular table file containing game data

See [[Tables|tables]]

==Other ASCII or text file formats==

===EFF===
Files containing information of effect animations

See [[Multimedia_Files|multimedia files]]

[[Category:File Types]]