FreeSpace Wiki - User contributions [en]

Command-Line Reference

2011-12-09T10:29:59Z

CommanderDJ: /* Development Tools */

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

===Graphics===
====-spec====
'''"Enable Specular"'''

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====
'''"Enable Environment maps"'''

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). [[Installing FreeSpace 2 Open#Video setup|See Video setup.]]

====-glow====
'''"Enable Glowmaps"'''

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)

====-mipmap====
'''"Enable mipmapping"'''

Causes for non-mipmapped textures to have mipmaps generated within the 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====
'''"Disable motion debris"'''

====-noscalevid====
"Disable scale-to-window for Movies"

Disables fullscreen scaling of video clips.

====-missile_lighting====
'''"Apply Lighting to Missiles"'''

====-normal====
'''"Enable Normal Maps"'''

Normal maps require 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. (Technical note: DXT5 will work, since only the GREEN and ALPHA channels are read by the current shader system. One direction of lines goes into the GREEN channel, the other direction goes into the ALPHA channel. RED and BLUE can be either base gray (#808080) or black. Usual practice is after creating the DXT5_NM, copy the RED channel to the ALPHA channel, black out the RED and BLUE an then save as either a DXT5 or u8888 (uncompressed) DDS file.)

====-post_process====
'''"Enable Post Processing"'''

enables the use (if present) of post-processing effects as defined by the post_process.tbl. Bloom usage has an additional cmdline option for setting it's value, most post processing effects are achieved in mission per the mission designer or can be enabled globally in the table.

====-soft_particles====
'''"Enable soft particles"'''

====-3dshockwave====
'''"Enable 3D Shockwaves"'''

This only has any effect when both a 2d and 3d shockwave effect are present, otherwise the only available effect is used.

====-fxaa====
'''"Enable FXAA antialiasing"'''

Enables the FXAA postprocessing stage. Needs optional FXAA shaders, which can be found here: http://www.hard-light.net/forums/index.php?topic=76145.0

====-flightshaftsoff====
'''"Force Lightshafts off"'''

Disables Lightshafts even if a mission designer enables them via SEXP in a mission.

===Game Speed===
====-img2dds====
'''"Compress non-compressed images"'''

Converts all images to DDS (compressed) format. Decreases memory usage but potentially reduces image quality.

====-no_vsync====
'''"Disable vertical sync"'''

====-cache_bitmaps====
'''"Cache bitmaps between missions"'''

Will ideally reduce the load-time from one mission to another.

===HUD===
====-dualscanlines====
'''"Another Pair of Scanning Lines"'''

Adds a second pair of scanning lines to the target window when scanning an object.

====-targetinfo====
'''"Enable Info next to Target"'''

Displays target info, such as name and class, beside the targeted object.

====-orbradar====
'''"Enables 3D radar"'''

An Orb style 3D radar will replace the standard 2D version.

====-rearm_timer====
'''"Enable Rearm/Repair Completion Timer"'''

Displays time remaining until rearm and repair from a support ship is complete.

====-ballistic_gauge====
'''"Enable the analog Ballistic Ammo gauge"'''

Adds an ammo gauge to the HUD when armed with a ballistic weapon.

===Gameplay===
====-ship_choice_3d====
'''"Use Models for Ship Selection"'''

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====
'''"Use Models for Weapon Selection"'''

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====
'''"Enable 3D Warp"'''

Use full geometry for the subspace warp effect.

====-warp_flash====
'''"Enable Flash upon Warp"'''

Enable a flash at warp in and warp out.

====-no_ap_interrupt====
'''"Disable Interrupting of AutoPilot"'''

Tells the game to not allow players to interrupt an autopilot already-in-progress.

===Audio===
====-snd_preload====
'''"Preload mission game sounds"'''

Useful in preventing game stuttering when sounds are played for the first time.

====-nosound====
'''"Disable Sound and Music"'''

====-nomusic====
'''"Disables Music"'''

===Multiplayer===
====-standalone====
'''"Run as Stand Alone Server"'''

Creates a standalone multi-player server.

====-startgame====
'''"Skip Mainhall and Start Hosting"'''

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====
'''"Start Hosted Server as 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====
'''"Host Confirms Join requests"'''

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 Flight Deck option"'''

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

===Troubleshooting===
====-nohtl====
'''"Software Mode (very slow)"'''
{{Warning| Enabling this will significantly reduce performance.}}
Reverts to software rendering mode.

====-no_set_gamma====
'''"Disable Setting of Gamma"'''

Disables the gamma settings in the options screen.

====-nomovies====
'''"Disable Video Playback"'''

Disables all video playback.

====-noparseerrors====
'''"Disable Parsing Errors"'''

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.
*'''Note:''' the parameter was removed as of the July 5, 2011 nightly build.

====-query_speech====
'''"Does this build have Speech?"'''

Determines if the current build includes text-to-speech.

====-novbo====
'''"Disable OpenGL VBO"'''

====-noibx====
'''"Don't use cached index buffers (IBX)"'''

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"'''

====-disable_fbo====
'''"Disable OpenGL RenderTargets"'''

====-no_glsl====
'''"Disable GLSL (shader) Support"'''

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.

====-disable_glsl_model====
'''"Don't use shaders for model rendering"'''

====-ati_swap====
'''"Fix Color issues on some ATI cards"'''

====-no_3d_sound====
'''"Use only 2D/stereo for sound effects"'''

===Experimental===
====-ingame_join====
'''"Allows Ingame Joining"'''

Enables ingame joining in multiplayer. FIXME: Host option?

====-voicer====
'''"Voice Recognition"'''

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.

===Development Tools===
====-fps====
'''"Show frames per second on HUD"'''

Displays current frames per second.

====-pos====
'''"Show Position of Camera"'''

Displays current position coordinates of camera.

====-window====
'''"Run in Window"'''

Runs the game in a window. No check to make sure that resolution is no higher than your desktop resolution, so be careful.

====-fullscreen_window====
'''"Run in Fullscreen Window"'''

====-timerbar====
Displays a timing bar across the top of the screen. Timerbar format varies by build. This is a relic from the Volition development days, and is unmaintained.
*'''Note:''' the parameter was removed as of the July 5, 2011 nightly build.

====-stats====
'''"Show Statistics"'''

Shows total and free physical memory, virtual memory and system pagefile.

====-coords====
'''"Show Coordinates"'''

Shows coordinates of the mouse cursor.

====-show_mem_usage====
'''"Show Memory Usage"'''

Shows detailed RAM usage based on file, handler and process usage and display on the left-center side of the screen during mission load and while in mission.

The meaning of the info displayed in the upper right corner of the HUD 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====
Is actually now (or should be) a typed reference rather than as a selection item. Takes 1 argument, usually a descriptive name.
Example usage: "-table_crcs MediaVPs" will create a table_crcs.csv file in the running mod (name can be separate of the mod selected) that allows for the validation of the tables used by that mod while on-line. The descriptive parameter given helps "allocate" that .csv file to the mod in question, and as such should closely or exactly match that mods name if possible.

====-missioncrcs====
Is actually now (or should be) a typed reference rather than as a selection item. Takes 1 argument, usually a descriptive name.
Example usage: "-mission_crcs MediaVPs" will create a mission_crcs.csv file in the running mod (name can be separate of the mod selected) that allows for the validation of the missions used by that mod while on-line. The descriptive parameter given helps "allocate" that .csv file to the mod in question, and as such should closely or exactly match that mods name if possible.

====-dis_collisions====
'''"Disable Collisions"'''

Disables all collisions.

====-dis_weapons====
'''"Disable Weapon Rendering"'''

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.

====-save_render_target====
'''"Save Render Targets to file"'''

====-debug_window====
'''"Display Debug Window"'''

Lists the fs2_open.log in (nearly)real-time generation.

====-verify_vps====
'''"Spew VP crcs to vp_crcs.txt"'''

Exports the CRC values of the VP files being loaded into a vp_crcs.txt file.

====-reparse_mainhall====
'''"Reparse mainhall.tbl when loading halls"'''

Mainhall.tbl will be reparsed every time a mainhall is loaded, as opposed to just once at game startup.

==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====
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 focused 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===
====-bloom_intensity====
Requires -post_processing ("Enable Post Processing") command.
Default value is 75. Range is 0-200.

====-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.

====-fxaa_preset====
Requires both -post_processing and -fxaa. Can be used to adjust the FXAA quality and speed, 0 is fastest, 6 is highest quality. Default setting is 3.

===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 the Launcher's MOD 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 that this ''Mission.fs2'' is also 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 enhanced 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. A special build of wxLauncher is able to configure FRED so that the -mod doesn't have to be done manually see [http://www.hard-light.net/forums/index.php?topic=67950.msg1387911#msg1387911 the forum post] for more details.
{{Table3612|As of 3.6.12 FRED now loads cmdline_fso.cfg just like FS does so FRED will use the same settings as FS including the -mod settings}}
# 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]]

Colors.tbl

2011-09-26T05:31:31Z

CommanderDJ: /* Example Table */

==General Format==

*Colors.tbl simply starts with "#Start Color" (without the quotes)
*All following entries are of the form "$Color name: (R G B A)" (without the quotes, but with the brackets), where R, G, B, and A are red, green, blue and alpha values (between 0 and 255 inclusive).
*Colors.tbl must end with "#End" (without the quotes).

==Possible Colors==

*Blue
*Bright Blue
*Green
*Bright Green
*Black
*Grey
*Silver
*White
*Bright White
*Violet Gray
*Violet
*Dim Red
*Red
*Bright Red
*Pink
*Light Pink
*Yellow
*Bright Yellow
*UI Light Green
*UI Green
*UI Light Pink
*UI Pink

==Syntax and Usage==

*All colors are optional (defaults will be used if the color is not specified).
*However, any colors included must be included in the order specified above, otherwise they will be skipped.
*Note that at this point colors.tbl only allows redefinition of the 22 pre-existing UI colors. New colors cannot be added as of yet.

==Example Table==
The values in this table are the code's default values.
<pre>
#Start Colors

;; This is colors.tbl. Here you can redefine the RGBA values for the 22 default colours for the UI.
;; Any redefining is optional, so you don't need to include all colors (the ones you skip will just use the default values).
;; However, any you DO redefine need to be placed in this order (and spelled this way):

;;$Blue
;;$Bright Blue
;;$Green
;;$Bright Green
;;$Black
;;$Grey
;;$Silver
;;$White
;;$Bright White
;;$Violet Gray
;;$Violet
;;$Dim Red
;;$Red
;;$Bright Red
;;$Pink
;;$Light Pink
;;$Yellow
;;$Bright Yellow
;;$UI Light Green
;;$UI Green
;;$UI Light Pink
;;$UI Pink

;;Redefine colors this way:
;;$Color Name: (RVALUE GVALUE BVALUE AVALUE) (the brackets are necessary!)
;;where RVALUE, GVALUE, BVALUE and AVALUE are integers between 0 and 255 inclusive
;;AVALUE is alpha value. Every default color just leaves this as 255, so if you're not sure, just use 255

$Blue: (93 93 128 255)
$Bright Blue: (185 185 255 255)
$Green: (0 120 0 255)
$Bright Green: (50 190 50 255)
$Black: (0 0 0 255)
$Grey: (65 65 65 255)
$Silver: (160 160 160 255)
$White: (105 105 105 255)
$Bright White: (255 255 255 255)
$Violet Gray: (160 144 160 255)
$Violet: (192 104 192 255)
$Dim Red: (80 6 6 255)
$Red: (126 6 6 255)
$Bright Red: (200 0 0 255)
$Pink: (185 150 150 255)
$Light Pink: (230 190 190 255)
$Yellow: (255 255 122 255)
$Bright Yellow: (255 255 0 255)
$UI Light Green: (161 184 161 255)
$UI Green: (190 228 190 255)
$UI Light Pink: (184 161 161 255)
$UI Pink: (228 190 190 255)

#End
</pre>

Colors.tbl

2011-09-26T05:30:18Z

CommanderDJ:

==General Format==

*Colors.tbl simply starts with "#Start Color" (without the quotes)
*All following entries are of the form "$Color name: (R G B A)" (without the quotes, but with the brackets), where R, G, B, and A are red, green, blue and alpha values (between 0 and 255 inclusive).
*Colors.tbl must end with "#End" (without the quotes).

==Possible Colors==

*Blue
*Bright Blue
*Green
*Bright Green
*Black
*Grey
*Silver
*White
*Bright White
*Violet Gray
*Violet
*Dim Red
*Red
*Bright Red
*Pink
*Light Pink
*Yellow
*Bright Yellow
*UI Light Green
*UI Green
*UI Light Pink
*UI Pink

==Syntax and Usage==

*All colors are optional (defaults will be used if the color is not specified).
*However, any colors included must be included in the order specified above, otherwise they will be skipped.
*Note that at this point colors.tbl only allows redefinition of the 22 pre-existing UI colors. New colors cannot be added as of yet.

==Example Table==
The values in this table are the code's default values.
<pre>
#Start Colors

;; This is colors.tbl. Here you can redefine the RGBA values for the 22 default colours for the UI.
;; Any redefining is optional, so you don't need to include all colors (the ones you skip will just use the default values).
;; However, any you DO redefine need to be placed in this order (and spelled this way):

;;$Blue
;;$Bright Blue
;;$Green
;;$Bright Green
;;$Black
;;$Grey
;;$Silver
;;$White
;;$Bright White
;;$Violet Gray
;;$Violet
;;$Dim Red
;;$Red
;;$Bright Red
;;$Pink
;;$Light Pink
;;$Yellow
;;$Bright Yellow
;;$UI Light Green
;;$UI Green
;;$UI Light Pink
;;$UI Pink

;;Redefine colors this way:
;;$Color Name: (RVALUE GVALUE BVALUE AVALUE) (the brackets are necessary!)
;;where RVALUE, GVALUE, BVALUE and AVALUE are integers between 0 and 255 inclusive
;;AVALUE is alpha value. Every default color just leaves this as 255, so if you're not sure, just use 255

$Blue: (-1 93 128 255)
$Bright Blue: (185 185 255 255)
$Green: (0 120 0 255)
$Bright Green: (50 190 50 255)
$Black: (0 0 0 255)
$Grey: (65 65 65 255)
$Silver: (160 160 160 255)
$White: (105 105 105 255)
$Bright White: (255 255 255 255)
$Violet Gray: (160 144 160 255)
$Violet: (192 104 192 255)
$Dim Red: (80 6 6 255)
$Red: (126 6 6 255)
$Bright Red: (200 0 0 255)
$Pink: (185 150 150 255)
$Light Pink: (230 190 190 255)
$Yellow: (255 255 122 255)
$Bright Yellow: (255 255 0 255)
$UI Light Green: (161 184 161 255)
$UI Green: (190 228 190 255)
$UI Light Pink: (184 161 161 255)
$UI Pink: (228 190 190 255)

#End
</pre>

Colors.tbl

2011-09-26T05:25:38Z

CommanderDJ: Created page with "==General Format== *Colors.tbl simply starts with "#Start Color" (without the quotes) *All following entries are of the form "$Color name: (R G B A)" (without the quotes, but wi…"

Ridiculous

2011-03-03T05:21:59Z

CommanderDJ: /* Comments */

'''Ridiculous''' is a parody for ''FreeSpace 2''

==Overview==
Author: IronBeer

Originally posted: 11/10/2010

Mods:

-Full voice acting, including 3 new pilot personas

-Several unique music tracks

-A couple unique head .anis

-Some (non-unique) custom ships

-Some new weapons. You might even get to use one or two!

Missions: 9

==Description==
:''A few years after the Second Shivan Incursion, a recon and exploration team flying off of the GVD Minotaur stumble across something that will forever alter the future of the Alliance. Get drawn into something far beyond hope of control and face down some of the roughest odds this side of Gamma Draconis.

==Comments==

Long story short, I ''had to dislike this''. The story was just not good enough. Why am I talking about story in a parody campaign, you might ask? It is because ''the gameplay was BAAAAD''. In my opinion, one can divide a FreeSpace campaign (or a computer game in general) experience in two major segments: story and gameplay. Of course, these groups could be divided even further, for instance atmosphere and characters or controls and mission design comes to my mind instantly, but that is not the point of this comment.
I believe that – to a certain extent, that is – if one of these major segments fail to deliver properly, the other can make up for it (your mileage will probably vary on this one, but Deadly Premonition comes to my mind as an example for a game where the story makes up for the bad gameplay). In the case of Ridiculous, the gameplay is bad. That is the reason I’ve had such high standards for the plot and basically – it had to made up for the neverending dogfights that reminded me of Second Great War Part 2. The basic idea is good, but the delivery was botched and all in all, I must call Ridiculous a wasted opportunity, solely based on the gameplay – with more enjoyable missions, the story would have been solid and enough for me as well. As it stands, there is room for improvement for IronBeer’s next campaign but the basics are set and solid – let’s hope that the next campaign will feature better missions, because, frankly, that is all we need. -- ''Lucika''

Actually I felt this as a good parody. Indeed, gameplay wasn't top notch, but the sheer number of funny and awesomely '''ridiculous''' moments more than made up for it. Some of the things that were pulled off during this were nice, quite good actually. The basic idea is, if you're playing this, do not expect BP-like gameplay, this is a "kill 'em all and stay alive" type of campaign, with a very funny side attached to it. Keep an open mind and you will enjoy it! -- [[User:ktistai228|ktistai228]] 21st January 2011, 9:07 AM GMT+2

The gameplay of this campaign is standard FreeSpace stuff. I don't think Ridiculous' gameplay is bad, because it adheres to the norm when it comes to FS-style combat. In any case, gameplay was not the main point of this campaign, which is why solely basing a review on its gameplay is unfair. The campaign is a parody, and an excellent one at that. Both the general gist of the plot and isolated moments in missions deliver many laughs along with quite a few WTF moments. I found the plot to be immersive enough to draw me in, and that's why I kept playing. A very good first campaign from IronBeer. --[[User:CommanderDJ|CommanderDJ]] 05:21, 3 March 2011 (UTC)

==Availability==
[http://www.mediafire.com/?m62z36mowd7nehz Mediafire Link V 1.02]

[[Category:User-made_Campaigns]]

Syrk: The Unification Wars

2010-11-30T08:05:56Z

CommanderDJ: /* Development Team */

''Unification. Civil War. Shivans. No canon contradictions.''

'''Syrk: The Unification Wars''' is a pre-FS1 mod that is being developed for the FSO engine by the Syrk Development team.
[[Image:Ravana.jpg|thumb|right|480px|Behold the Ravana!]]

==Overview==
'''Author:''' Lucika, with help from the Syrk Dev team.

'''Missions:''' Presently assumed to be 60 with three loops.

'''Mods:''' Many various models from various mods.

''Requirements:'' 3.6.12+ FSO Inferno Build. Media VP Package Version 3.6.10+ is highly recommended.

==Description==
''"Humanity has risen. Originated on the third planet of the Sol system and having greater dreams about their future, they’ve colonized Sol. But their fragile peace has shattered in no time, and a civil war started and the conflict’s outcome will surely determine humanity’s fate… Even though every single human is sure about this, none of them can expect that they’ll meet their nemesis on the other side of an unstable jump node…"''

The campaign that shows you the bloody process that lead to the formation of the GTA is coming to a Sol near you! With 4 Terran factions fighting for control of humanity, starting a story that stretches much farther than any of you could ever imagine, '''Syrk: The Unification Wars''' will allow you to witness such milestones of human history as the siege of Pluto or the majestic arrival of the very first Orion ever made. To spice this all up, you will encounter the Destroyers as well!

...record scratch.

Yes, our mortal enemies, the Shivans appear in a campaign that is set long before the Great War. Yet I can assure you, canon will not be contradicted! With 20(...40...60!) dogfightful missions we will be showcasing a yet uncovered part of Terran history, the events that started it all: the Unification Wars.

==Development Team==
'''Lucika''' - Project leader, Founder, Storyline Writer, FREDder and Tester.

'''Rodo''' - Background Artist, Tester and Contributor.

'''Dragonsniper''' - FREDder, Tabler, Tester and Contributor.

'''Headdie''' - Tabler

'''[[User:Sifle|Sifle]]''' - FREDder

'''ShadowWolf''' - Tabler

'''CommanderDJ''' - FREDder

==Previous/Inactive Development Team Members==
'''Shiv''' - Co-Founder and FREDder. Made it possible to host Syrk at GameWarden.

'''Dilmah G''' - Co-Founder, FREDder and Tester.

'''maelstrom0511''' - FREDder.

'''Retsof''' - Weapon effects creator.

'''Moonred''' - FREDder, Tester.

==Links==
'''Website'''
*http://www.hard-light.net/forums/index.php?board=201.0

'''Syrk Dev Youtube Page'''
*http://www.youtube.com/user/SyrkDev

'''Hiring Thread'''
*http://www.hard-light.net/forums/index.php?topic=71910.0

[[Category:User-made Campaigns]]

Setting up a campaign file

2010-10-05T05:46:47Z

CommanderDJ: /* Available missions */

In ''FreeSpace'', '''campaigns''' are stored in text-based *.fc2 files. Setting up a campaign can be done in two ways: in FRED's Campaign Editor (SHIFT-C in retail, and in most—but not all—FreeSpace Open builds) or in a conventional text editor like Notepad.

This article will be about the '''Campaign Editor'''.

==Prerequisites==
Before you start setting up your campaign, make sure that you have all the missions that you want to be in your campaign. Gradually adding new and new missions to a campaign file is not recommended in FreeSpace.

If you plan to include new, nonretail ships in your campaign, make sure that they are in the table files already. Gradually attaching new and new user-made ships or weapons works on the same principle as adding new missions.

Your missions and table files don't have to be final. You can modify both the mission and table files unpunished. ''FreeSpace'' campaign files only refer to missions and table entries, the contents of these files are unimportant when talking about campaigns. However, if you rename anything, revise the campaign file, as it must reflect the most recent file names. Revising the campaign file in such a way is recommended in a text editor. See [[Editing a mission in a text editor]].

==The Campaign Editor==
The Campaign Editor is accessed by pressing SHIFT-C in [[Portal:FRED|FRED]].

Here is a list of what windows you see, and some explanations on what you can do with them:

===Available missions===
This is a list of all the missions that are within your missions folder. You can take missions from this window and put them into the right-side window by highlighting the mission you want, holding CTRL and clicking on the part of the campaign tree you want the mission in. If the missions that you are looking for aren't in this window, make sure you have the [[FRED Command Line Reference|-mod]] parameter set right and your missions are indeed in the data/missions folder of the current mod. If you put a mission into the right-side window, it will disappear from this list. If you remove a mission from the campaign's mission list, it will reappear in the Available Missions window.

===Campaign name, type, description===
*''Campaign name'' is the name of the campaign. It's this name that will appear in the Campaign Room.
*''Campaign type''' can be single player, multiplayer cooperative, and multiplayer team. If you set your campaign to be single player, it will appear in the Campaign Room. If it's multiplayer, it will appear under the multiplayer campaigns tab in the Campaign Host window.
*''Campaign description'' is the campaign's description that will appear in the Campaign Room.

===Mission options===
These options are by default grayed out. You can edit these options if you click on a mission that you already inserted into the right-side window.
*''Briefing cutscene'': You will not need these unless you want a cutscene be played before your mission.
*''Main hall index'' can be 0 or 1. If it's 0, then if the player is at the selected mission, the Main Hall will be that of the ''Galatea'' (''FreeSpace 1'') or the ''Aquitaine'' (''FreeSpace 2''). If it's 1, then the Main Hall will be that of the ''Bastion'' (''FreeSpace 1'') or the ''Psamtik'' (''FreeSpace 2'').

===Branches===
It's also by default grayed out until you select a mission from the right-side window.

You can define which mission will follow the selected mission and under what conditions. You can also set the conditions under which the player must restart the mission. Details will be given in the section that discusses [[Setting up a campaign file#The right-side window|the right-side window]].

There's a gray area below your Branches section. It's the Developer Notes (set in the Mission Specs Editor) of the selected mission. Developer Notes are used by mission makers to remind themselves of things they are about to implement, improve upon, etc.

===Mission loop description, brief anim, brief voice===
[[Image:CampaignEditLoop.JPG|thumb|right|Campaign loop example]]

Loop missions are like the [[Special Operations Command|SOC]] ones in the Main FreeSpace 2 Campaign. The player can choose whether or not he wishes to complete some bonus missions or proceed with the main branch.

In order to gain access to the mission loop options, you must select the mission in the right-side window that ''precedes'' your loop mission and select a branch that activates your loop. To do that, you must have at least two other missions connected to the mission that you select.

*''Mission loop description'' is the text that appears in the window the player is asked whether or not he wishes to participate in the loop mission. This is the window with the animated SOC logo in it.
*''Mission brief anim'' is the animation file that will be played while the player is the aforementioned window. By default, this is the SOC logo.
*''Mission brief voice'' is the WAV file that will be played when the player is in the aforementioned window. By default, there is no voice.

If the player presses Decline, he will proceed with the main campaign branch.

===Setting up initial status===
You can define which ships and weapons you want the player to have access to at the beginning of the campaign. If you test your campaign and have no weapons available, it is because you forgot about this feature.

This is not permanent, as you can easily make additional ships or weapons available using the [[allow-ship]] and [[allow-weapon]] [[Retail SEXPs|SEXPs]].

===Checking for errors===
You can access an in-built error checker by either pressing ALT-H or clicking on Other --> Error Checker. This is a very basic error finder. It will help you pinpoint some technical errors that will prevent your campaign from loading up.

===The right-side window===
This window is the "heart" of the Campaign Editor. You can define which missions will follow which one and under what conditions. Ideally, you had already dragged some missions into this window, with mission 2 being below mission 1 and mission 3 below mission 2, etc.

Click on the uppermost mission. First, you must set which mission will follow it. Tap your left mouse button and drag it above the mission that you want to follow your selected mission. If you can see a line draw between the two missions, you've been successful. Now select the first mission again. Right-clicking on it will bring up the following options:
*''Remove mission'': Removes the mission from the hierarchy. Missions that are removed from the hierarchy can be readded by dragging them from the Missions available section.
*''Add a Repeat Link'': Defines that under what conditions the player will be forced to replay the mission. From a gameplay perspective, every mission requires this. Otherwise the player can simply jump out at the end of the mission and proceed in the campaign.
*''End of Campaign'': Used to order the game to end the campaign.

If you take a look at the Branches section (to the left), you will see that it now says: "Branch to xx" and, if you clicked on Add a Repeat Link, "Repeat mission." If you expand them, you will see that you can set up a SEXP tree there. This SEXP tree will tell under what conditions will the player be able to proceed in the campaign or forced to replay the mission. One of these trees must be set to [[true]]. This "true" link must also be the last in the list, otherwise your campaign won't run. In the example (look at the picture), the conditions to proceed in the campaign are set, and the repeat link is set to true. If you want to set the conditions under which the player is forced to replay the mission, your "Branch to xx" must be set to true. Neither method is superior to or more advisable than the other. It's a matter or preference. If there are two conflicting set of conditions, the one that is higher in the list will take place (this is why the "true" tree must be last).

==Editing in a text editor==
You can edit your campaign file in a conventional text editor like Notepad or WordPad to apply some minor changes like changing the main hall indices. Only more experienced FREDders are advised to edit their campaigns in such a way. For more details, see [[Editing a mission in a text editor]]

==Tips and miscellaneous notes==
*Most importantly: Don't forget to set up your campaign's list of allowed ships and weapons in the Initial Status window.
*After setting up your campaign file, your campaign will appear in the Campaign Room.
*Missions that are part of a campaign will not be available in the Mission Simulator unless they are completed in campaign mode.
*To test if your hierarchy works properly, jump out at the beginning of every mission. If you are not allowed to proceed, it's okay. Also complete only the necessary mission goals to see if you can proceed when you are indeed supposed to.
*Renaming mission files, Events, Mission Objectives, ships' or weapons' table entry names, and changing the order of your Events can compromise your campaign file's stability.
*If you start testing your campaign in campaign mode, changes applied to your campaign file will only take place if you restart your campaign by clicking on Reset Campaign in the Campaign Room. Altering your missions, however, will take effect immediately.

[[Category:FRED|Campaign file, setting up a]]

Setting up a campaign file

2010-10-05T05:45:58Z

CommanderDJ: /* Available missions */

In ''FreeSpace'', '''campaigns''' are stored in text-based *.fc2 files. Setting up a campaign can be done in two ways: in FRED's Campaign Editor (SHIFT-C in retail, and in most—but not all—FreeSpace Open builds) or in a conventional text editor like Notepad.

This article will be about the '''Campaign Editor'''.

==Prerequisites==
Before you start setting up your campaign, make sure that you have all the missions that you want to be in your campaign. Gradually adding new and new missions to a campaign file is not recommended in FreeSpace.

If you plan to include new, nonretail ships in your campaign, make sure that they are in the table files already. Gradually attaching new and new user-made ships or weapons works on the same principle as adding new missions.

Your missions and table files don't have to be final. You can modify both the mission and table files unpunished. ''FreeSpace'' campaign files only refer to missions and table entries, the contents of these files are unimportant when talking about campaigns. However, if you rename anything, revise the campaign file, as it must reflect the most recent file names. Revising the campaign file in such a way is recommended in a text editor. See [[Editing a mission in a text editor]].

==The Campaign Editor==
The Campaign Editor is accessed by pressing SHIFT-C in [[Portal:FRED|FRED]].

Here is a list of what windows you see, and some explanations on what you can do with them:

===Available missions===
This is a list of all the missions that are within your missions folder. You can take missions from this window and put them into the right-side window by highlighting the mission you want, holding CTRL and clicking on the part of the campaign tree you want the mission in. If that missions that you are looking for aren't in this window, make sure you have the [[FRED Command Line Reference|-mod]] parameter set right and your missions are indeed in the data/missions folder. If you drag a mission to the right-side window, it will disappear from this list. If you remove a mission from the campaign's mission list, it will reapper in the Available missions window.

===Campaign name, type, description===
*''Campaign name'' is the name of the campaign. It's this name that will appear in the Campaign Room.
*''Campaign type''' can be single player, multiplayer cooperative, and multiplayer team. If you set your campaign to be single player, it will appear in the Campaign Room. If it's multiplayer, it will appear under the multiplayer campaigns tab in the Campaign Host window.
*''Campaign description'' is the campaign's description that will appear in the Campaign Room.

===Mission options===
These options are by default grayed out. You can edit these options if you click on a mission that you already inserted into the right-side window.
*''Briefing cutscene'': You will not need these unless you want a cutscene be played before your mission.
*''Main hall index'' can be 0 or 1. If it's 0, then if the player is at the selected mission, the Main Hall will be that of the ''Galatea'' (''FreeSpace 1'') or the ''Aquitaine'' (''FreeSpace 2''). If it's 1, then the Main Hall will be that of the ''Bastion'' (''FreeSpace 1'') or the ''Psamtik'' (''FreeSpace 2'').

===Branches===
It's also by default grayed out until you select a mission from the right-side window.

You can define which mission will follow the selected mission and under what conditions. You can also set the conditions under which the player must restart the mission. Details will be given in the section that discusses [[Setting up a campaign file#The right-side window|the right-side window]].

There's a gray area below your Branches section. It's the Developer Notes (set in the Mission Specs Editor) of the selected mission. Developer Notes are used by mission makers to remind themselves of things they are about to implement, improve upon, etc.

===Mission loop description, brief anim, brief voice===
[[Image:CampaignEditLoop.JPG|thumb|right|Campaign loop example]]

Loop missions are like the [[Special Operations Command|SOC]] ones in the Main FreeSpace 2 Campaign. The player can choose whether or not he wishes to complete some bonus missions or proceed with the main branch.

In order to gain access to the mission loop options, you must select the mission in the right-side window that ''precedes'' your loop mission and select a branch that activates your loop. To do that, you must have at least two other missions connected to the mission that you select.

*''Mission loop description'' is the text that appears in the window the player is asked whether or not he wishes to participate in the loop mission. This is the window with the animated SOC logo in it.
*''Mission brief anim'' is the animation file that will be played while the player is the aforementioned window. By default, this is the SOC logo.
*''Mission brief voice'' is the WAV file that will be played when the player is in the aforementioned window. By default, there is no voice.

If the player presses Decline, he will proceed with the main campaign branch.

===Setting up initial status===
You can define which ships and weapons you want the player to have access to at the beginning of the campaign. If you test your campaign and have no weapons available, it is because you forgot about this feature.

This is not permanent, as you can easily make additional ships or weapons available using the [[allow-ship]] and [[allow-weapon]] [[Retail SEXPs|SEXPs]].

===Checking for errors===
You can access an in-built error checker by either pressing ALT-H or clicking on Other --> Error Checker. This is a very basic error finder. It will help you pinpoint some technical errors that will prevent your campaign from loading up.

===The right-side window===
This window is the "heart" of the Campaign Editor. You can define which missions will follow which one and under what conditions. Ideally, you had already dragged some missions into this window, with mission 2 being below mission 1 and mission 3 below mission 2, etc.

Click on the uppermost mission. First, you must set which mission will follow it. Tap your left mouse button and drag it above the mission that you want to follow your selected mission. If you can see a line draw between the two missions, you've been successful. Now select the first mission again. Right-clicking on it will bring up the following options:
*''Remove mission'': Removes the mission from the hierarchy. Missions that are removed from the hierarchy can be readded by dragging them from the Missions available section.
*''Add a Repeat Link'': Defines that under what conditions the player will be forced to replay the mission. From a gameplay perspective, every mission requires this. Otherwise the player can simply jump out at the end of the mission and proceed in the campaign.
*''End of Campaign'': Used to order the game to end the campaign.

If you take a look at the Branches section (to the left), you will see that it now says: "Branch to xx" and, if you clicked on Add a Repeat Link, "Repeat mission." If you expand them, you will see that you can set up a SEXP tree there. This SEXP tree will tell under what conditions will the player be able to proceed in the campaign or forced to replay the mission. One of these trees must be set to [[true]]. This "true" link must also be the last in the list, otherwise your campaign won't run. In the example (look at the picture), the conditions to proceed in the campaign are set, and the repeat link is set to true. If you want to set the conditions under which the player is forced to replay the mission, your "Branch to xx" must be set to true. Neither method is superior to or more advisable than the other. It's a matter or preference. If there are two conflicting set of conditions, the one that is higher in the list will take place (this is why the "true" tree must be last).

==Editing in a text editor==
You can edit your campaign file in a conventional text editor like Notepad or WordPad to apply some minor changes like changing the main hall indices. Only more experienced FREDders are advised to edit their campaigns in such a way. For more details, see [[Editing a mission in a text editor]]

==Tips and miscellaneous notes==
*Most importantly: Don't forget to set up your campaign's list of allowed ships and weapons in the Initial Status window.
*After setting up your campaign file, your campaign will appear in the Campaign Room.
*Missions that are part of a campaign will not be available in the Mission Simulator unless they are completed in campaign mode.
*To test if your hierarchy works properly, jump out at the beginning of every mission. If you are not allowed to proceed, it's okay. Also complete only the necessary mission goals to see if you can proceed when you are indeed supposed to.
*Renaming mission files, Events, Mission Objectives, ships' or weapons' table entry names, and changing the order of your Events can compromise your campaign file's stability.
*If you start testing your campaign in campaign mode, changes applied to your campaign file will only take place if you restart your campaign by clicking on Reset Campaign in the Campaign Room. Altering your missions, however, will take effect immediately.

[[Category:FRED|Campaign file, setting up a]]