FreeSpace Wiki - User contributions [en]

The Romans Blunder

2007-09-09T16:03:32Z

AcePace: Added transcript of opening scene.

{{Mission|next=A Lion at the Door|previous=The Place of Chariots|campaign=Campaign Walkthrough}}

'''ACT 1, MISSION 3'''

'''Fighter squadron:''' [[53rd Hammerheads]]'''
'''Description:''' You have been ordered to intercept the Iceni.

----
==Background==
The 53rd is scrambled to intercept the [[NTF Iceni|Iceni]], before it reaches Sirius, but somone high up made a mistake... if it was a mistake.

==Walkthrough==

This is a more difficult mission. You seem to have no chance of catching the [[NTF Iceni]], and it leaves the area. After a small conversation between the pilots and Command, two enemy freighters jump in with cargo, who are escorted by some fighters. Prioritize the fighters. Once they are gone, destroy the freighters. Do not splurge much effort at the containers, they are always destroyed by the shockwave of the explosion of the freighter carrying it.

After the freighters and the fighters are down, two [[NTF]] cruisers (NTC Glorious, NTC Imporvious) jump in and make your day difficult. They have fighter assistance as well. Try to lure them away by pulling back at the time they begin approaching on you. Without the assistance of the cruisers, they do not stand much long against you and your wingmen. Attack the cruisers after the fighters. The Glorious is the weaker one, target the anti-fighter beam(s) on it, and attack it with the [[GTM Tempest]]s. Fire at will with your rockets to destroy the cruiser.

The Impervious is tougher ([[GTC Leviathan]]-class), the [[GVD Psamtik]] jumps in and will destroy it on her own. After these cruisers have been destroyed, you can leave the area. The mission is more difficult to survive than completing its mission goals. Disarm the cruisers of their anti-fighter beam turrets first.

==Tips==

The Psamtik won't arrive until you take out the cruisers' fighter cover, so make sure you do that first. Despite what command says, the cruiser's anti-fighter beam cannons will not fire at you.

As usual, your teammate's AI is lacking. it may be difficult to keep them alive in this mission.

==Notable ships present==
[[NTF Iceni]]

[[GVD Psamtik]]

==Noteable quote==

This mission is quite well known for the opening dialoge in the mission.

Command: Engage full burners and intercept the Iceni. They are two kilometers from the Sirius jump node.

Alpha 2: Command, we're five clicks from that corvette! Those coordinates you gave us were bogus! We don't stand a chance of catching that ship!

Command: You have your orders, pilot.

Alpha2: Command, where's the blockade? Why isn't the Alliance guarding this node?

Command: Our line of defense has been reprioritized for engagements elsewhere in the system.

Iceni Jumps
Enemy Leader: I regret your efforts to intercept us have failed, pilots. You would be well advised to question the wisdom of your leaders. Helm, engage subspace drive.

Beta1: The Iceni has jumped! I repeat. The Iceni has jumped!

Command: Acknowledged, pilot.

Alpha2: Request a status brief, Command! What the hell is going on here?

Command: You're out of line, pilot!

Alpha2: Out of line? I don't think so. We're risking our lives out here! We deserve a straight answer!

Command: You can discuss this at your debriefing. We now have reports that rebel vessels are heading for the jump node. Stand by for mission update. Command out.

Alpha2: Damn it! Command let Bosch escape!

Alpha3: What are you talking about?

Alpha2: They pulled the blockade. They gave us the wrong coordinates. There's no other explanation.

Alpha3: Why? Why would they let him go?

Alpha2: You tell me, pilot. I'm informed on a need-to-know basis.

Alpha3: Stand down. We're on your side here.

Alpha2: Why did we attack the Iceni? Why did we destroy that cargo? I can live with being a pawn if the game makes sense.
[[Category:Main Freespace 2 Campaign]]

Talk:The Romans Blunder

2007-09-09T13:44:34Z

AcePace: Question before editing.

Any use posting a transcript of this mission? Specifically the opening text, which is quite famous in the FS2 community. [[User:acePace | AcePace]]

Talk:.DDS

2007-09-08T18:18:17Z

AcePace:

Question before adding information on the file format, we're talking about the microsoft DirectX format? [[User:acePace|Ace pace]]
*Yep, you got it. DDS in this case = DirectDraw Surface. [[User:Shade|Shade]] 11:40, 8 September 2007 (CDT)
**Thank you, time to data dump abit. I figure more data can't hurt.[[User:acePace|Ace pace]]

Added stuff, I really don't know Wiki formatting and this is getting embaressing. [[User:acePace|Ace pace]]

.DDS

2007-09-08T18:14:59Z

AcePace: Just added some details.

DDS is a compressed texture format that is supported by FreeSpace SCP. Any modeler should use DDS for their textures as much as possible, as it is 1/2 the size of a PCX and 1/8 the size of a TGA image.

Background on DDS
The DDS File format was created by Microsoft for it's DirectX graphics API, however, it has become a general format for Textures and is supported by OpenGL(the graphics API the FS2 SCP uses).
The official discription of DDS is "The Microsoft DirectDraw Surface (DDS) file format is used to store textures and cubic environment maps, both with and without mipmap levels. This format can store uncompressed and compressed pixel formats, and is the preferred file format for storing DXTn compressed data."

Tools

Several tools exist for working with this format, besides any tools created by the FS2 SCP team. These tools are detailed here: [http://developer.nvidia.com/object/nv_texture_tools.html nVidia website] and should be usful.

Usage of DDS
The primary note to any texturer using the DDS file format is that even if DDS enables you to have twice the texture size, doesn't mean you should use all the available memory.

{{stub}}
[[Category:File Types]]

Talk:.DDS

2007-09-08T18:01:27Z

AcePace:

Question before adding information on the file format, we're talking about the microsoft DirectX format?
*Yep, you got it. DDS in this case = DirectDraw Surface. [[User:Shade|Shade]] 11:40, 8 September 2007 (CDT)
**Thank you, time to data dump abit. I figure more data can't hurt.

Talk:.DDS

2007-09-08T16:25:05Z

AcePace: New page: Question before adding information on the file format, we're talking about the microsoft DirectX format?

Question before adding information on the file format, we're talking about the microsoft DirectX format?

Talk:Is-ship-stealthy

2007-09-08T16:22:57Z

AcePace: New page: Just to make sure before I write, they're talking about the FREd flag?

Just to make sure before I write, they're talking about the FREd flag?

Talk:Num-assists

2007-09-08T16:22:19Z

AcePace: Question.

Can someone tell me what should be here? -Ace Pace

Total conversions

2007-08-31T08:16:27Z

AcePace: Reversed, my bad, or confused.

FreeSpace 2 Open engine has lot of potential and it has been used to create various '''total conversions''' that basically replace all the files related to original FreeSpace 2 with their own files. Due to terms set in the release of the FreeSpace 2 source code in 2002 none of the total conversions using FreeSpace 2 Open engine may be used for commercial purposes.

==Released total conversions==

===[[Beyond the Red Line]]===

[[Image:Btrl logo 250x100.jpg]]

Beyond the Red Line is a total conversion based on the Battlestar Galactica (Reimagined) TV series.

*'''Current release:''' ''Playable demo''

===[[The Babylon Project]]===

[[Image:TBP logo 255x112.jpg]]

The Babylon Project is a total conversion using the scenery from Babylon 5 universe. It features multiple campaigns and over a hundred models based on designs from the Babylon 5 universe.

*'''Current release:''' ''3.4 beta''

===[[Wing Commander Saga]]===

[[Image:Wcs logo 160 128.jpg]]

The Wing Commander Saga is a total conversion combining the FreeSpace 2 engine with the universe from the Wing Commander.

*'''Current release:''' ''Prologue''

==Other total conversions==

===[[The Apocalypse Project]]===

===[[Starfox: Shadows of Lylat]]===

Shadows of Lylat is a total conversion based on the Starfox video game series.

[[Image:SoL.gif]]

*'''Release Date:''' 2007/2008, chapter 1 release

===[[Star Wars Conversion|''Star Wars'' Conversion]]===
The ''Star Wars'' Conversion is a project to put ''Star Wars'' into ''FreeSpace'', preserving the gameplay of FS. Currently, the ''Star Wars'' Conversion project is actively progressing.

===[[Halo for Freespace]]===

Bringing the Halo universe to FreeSpace 2!

===[[Fringespace]]===

This project is designed to duplicate, as closely as possible, the "feel" of Tachyon: The Fringe, within the Freespace2_Open game engine as well as an attempt to update the visuals and the playing experience for Tachyon fans.

[[Image:Fs_logo_sm.jpg]]

[[Category:Main]]

Total conversions

2007-08-31T08:15:42Z

AcePace: /* The Babylon Project */ Changed beta to final as per thread.

FreeSpace 2 Open engine has lot of potential and it has been used to create various '''total conversions''' that basically replace all the files related to original FreeSpace 2 with their own files. Due to terms set in the release of the FreeSpace 2 source code in 2002 none of the total conversions using FreeSpace 2 Open engine may be used for commercial purposes.

==Released total conversions==

===[[Beyond the Red Line]]===

[[Image:Btrl logo 250x100.jpg]]

Beyond the Red Line is a total conversion based on the Battlestar Galactica (Reimagined) TV series.

*'''Current release:''' ''Playable demo''

===[[The Babylon Project]]===

[[Image:TBP logo 255x112.jpg]]

The Babylon Project is a total conversion using the scenery from Babylon 5 universe. It features multiple campaigns and over a hundred models based on designs from the Babylon 5 universe.

*'''Current release:''' ''3.4 final''

===[[Wing Commander Saga]]===

[[Image:Wcs logo 160 128.jpg]]

The Wing Commander Saga is a total conversion combining the FreeSpace 2 engine with the universe from the Wing Commander.

*'''Current release:''' ''Prologue''

==Other total conversions==

===[[The Apocalypse Project]]===

===[[Starfox: Shadows of Lylat]]===

Shadows of Lylat is a total conversion based on the Starfox video game series.

[[Image:SoL.gif]]

*'''Release Date:''' 2007/2008, chapter 1 release

===[[Star Wars Conversion|''Star Wars'' Conversion]]===
The ''Star Wars'' Conversion is a project to put ''Star Wars'' into ''FreeSpace'', preserving the gameplay of FS. Currently, the ''Star Wars'' Conversion project is actively progressing.

===[[Halo for Freespace]]===

Bringing the Halo universe to FreeSpace 2!

===[[Fringespace]]===

This project is designed to duplicate, as closely as possible, the "feel" of Tachyon: The Fringe, within the Freespace2_Open game engine as well as an attempt to update the visuals and the playing experience for Tachyon fans.

[[Image:Fs_logo_sm.jpg]]

[[Category:Main]]

FreeSpace 3

2007-08-09T09:24:02Z

AcePace: Added note of trademark status.

'''FreeSpace 3''' is the name a hypothetical sequel to ''FreeSpace 2'' would logically have. Asking about ''FreeSpace 3'' on the forums tends to provoke annoyance from established members, since it has allegedly "been asked about so many times before".

==IP controversy==
In early July, 2004, news appeared that controversial game developer [[Derek Smart]], creator of the game ''Battlecruiser: 3000AD''[http://www.gamespot.com/pc/strategy/battlecruiser3000ad/index.html], and active participator in many online forums, was considering bidding for the IP licence with the intent[http://forums.avault.com/showthread.php?t=3209] of developing ''FreeSpace 3''. This proposal was met with derision from the HLP community; the reaction was such that Smart threatened to potentially sue developers and terminate community projects once he had acquired the license, on account of copyright infringement. According to polls, however, the majority of customers would buy the game regardless of Smart's involvement.

In late July, 2004, further news arrived that Smart had decided not to develop ''FreeSpace 3''. Smart never acquired the license, and at present the license is believed to be owned by [[Interplay]].
==Community opinion==
The general consensus among the HLP community is that there will never be a FreeSpace3. Many reasons for this are presented. A select few are:

*[[Volition]], Inc. is the developer of the previous FreeSpace games in the series and is generally held as the only authorative developer
*[[Interplay]] owns the rights to the FreeSpace universe (as of 11-15-2006)
*the ownership of [[Volition]] has been transferred from Interplay to THQ
*the emotive consensus "''if it ain't by V, it ain't FreeSpace 3''"

While it could be argued that by having the source code available the FreeSpace community could set about creating FreeSpace 3 themselves, no such project has emerged. Disregarding the legal issues, the community has universally renounced any such undertaking, due to a multitude of reasons. While the main reason is that there's very little hope consensus could be reached regarding any possible storyline or direction, there are also numerous other issues involved. When all of these are taken into account, the conclusion has been that any and all plans regarding FreeSpace 3 are indefinitely shelved. For further information, read the HLP forum's official FS3 statement[http://www.hard-light.net/forums/index.php/topic,25531.0.html].

Attempts have been made to make FreeSpace 3 a reality, such as petitions and mailings to both Volition and Interplay. No attempts to date have been fruitful, and continuous mentions of FreeSpace 3 will ultimately be met with either derision or ''ad hominem'', or both.
==Current license status==
According to a post by Volition developer Dave Baranec[http://www.volition-inc.com/Staff/DaveBaranec] on the [http://www.hard-light.net HLP] forum, it would seem that Volition are furthering their talks with THQ about the current situation of the FreeSpace scene and the future of the FreeSpace series.

A nameless [[Interplay]] contact has stated numerous times that Interplay does not own the IP rights to FreeSpace. While it can be argued that the contact may not be in possession of the complete facts—due to his position as helpdesk—the preceeding is the only known semi-official statement regarding the current status of the license. The current status of the license is yet to be officially confirmed.
However, acording to the US Trademark and Patent office[http://tess2.uspto.gov/bin/showfield?f=doc&state=73ldnq.2.6] the license is alive and well with Interplay.

[[Interplay]] recently introduced their 20th anniversary edition of ''FreeSpace 2'', which can be ordered via their homepage. Moreover, recently Home of the Underdogs[http://www.the-underdogs.info] removed the game from their download list, only to later re-insert it[http://www.the-underdogs.info/game.php?id=4150]. No explanation for this has been given.

== See also ==
*[http://nodewar.penguinbomb.com/aotd/Turnsky/bang.jpg Cartoon on NodeWar regarding the issue]

*[http://forums.avault.com/showthread.php?t=3209 The original FS3 license discussion] at the ''Adrenaline Vault''

*[http://www.petitiononline.com/FS3/petition.html An online petition] to rescue the franchise

*[http://www.3dactionplanet.com/hlp/hosted/fsurp/help/karajorma/freespace2.html Karajorma's FAQ including section about FreeSpace 3]

Talk:Coding In C

2007-07-19T15:15:10Z

AcePace:

Whats the purpose of this page? We don't need to offer coding help here, any one can get that anywhere, far more usful is coding data about the Freespace 2 code layout, what the structure of the game is code wise(done to some extent), what are some of the more common re-usable functions(such as the FS2 file writing functions which are OS independent). -Ace

I agree, but maybe put some links to some good tutorials at the top of the page. If you think this is a good idea, do it, as I don't have any experience with the FS source.

Note that there is already a [[Sourcecode Reference]] page, also.
[[User:Mustang19|Mustang19]]

Hmn, I'll round some up, maybe with some book reccomendations.
Beyond what I linked, maybe http://cprogramming.com/tutorial.html#ctutorial this stuff?

Coding In C

2007-07-19T15:14:05Z

AcePace: -Added a book reccomendation as per talk page.

Note: While the following guide is a starter, the book The C Programming Language, Second Edition by Brian W. Kernighan and Dennis M. Ritchie, is considered one of the best books on the C language.

==File types==
There are two main types of file types in C/C++; .c/.cpp files, and .h files. .c/.cpp files are the meat of the source code; they contain the actual function and variable definitions. When a program is '''''built''''', it is '''''compiled''''' to create machine-readable code. To form a complete program, the machine code is '''''linked''''' with other compiled .c/.cpp files to form the complete program (the .exe).

.h files contain code, such as class, function, or struct definitions, that is used in multiple files but usually doesn't really do anything when the program is built.

==Comments==
Anything after // is considered a comment and ignored. Also, anything between a /* and a */ is considered as well (This is called a '''''block comment'''''). You may not put block comments inside of each other, although you can put pretty much anything else in them.

Note that comments are not ignored if they are inside '''''strings''''' (read on to find out what strings are!).

===Comments Example===
<pre>
//I'm a comment!
/* So am I.*/
/* Look, you can do //this and //this! */
char String[] = "//I look like a comment but I'm really a string.";
</pre>

==Variables==
C and C++ have a number of different types of variables; these are slices of memory that hold information. Because all variables are stored in binary, they are interchangeable, to a degree. '''All variables are case sensitive'''

For example, an '''''int''''' is an integer, or a number without any fractions or decimals; -2,-1,0,1,2,3,4,5...etc. An integer is 4 bytes, or 32-bits, long.

Another important type of variable is '''''char'''''. A char is one byte (8 bits) in size. It's essentially a shorter int, except it's most commonly used to represent a character, that is, letters and numbers and such. This means that any given letter is also a number; 'A' is 65, for example. This text->number conversion is called [http://www.cplusplus.com/doc/papers/ascii.html ASCII]. Single quotation marks are used to denote a character. For example, 'A'

A collection of characters is called a '''''string'''''; this isn't really a variable, however, it is standard. A string is a series of characters followed by a null character, or a char with a value of 0. (NOT the character '0'; that would be 48). Double quotation marks are used to denote a string. So, "This is a string". 'This is not a string'.

If you want to use decimals or fractions you'll have to use a '''''float''''' or a '''''double'''''. A float is the same size as an int, except it can be fractions. A '''''double''''' is twice as large as an int (8 bytes) but can be much more accurate than a float.

Finally, all the above integers can be prefixed with '''''unsigned'''''; this means that the variable only contains positive values. The '''''extern''''' prefix indicates that the variable exists, but is in some other file, so the compiler should let it be used. (The linker will complain if it doesn't really exist). '''''const''''' means that the variable can't be changed by the program after it's built, which lets addtional optimizations be performed. Some other prefixes are '''''short''''' and '''''long''''' - look them up if you're interested.

===Variable example===
<pre>
int i; //Create the variable i.
i = 42; //Set i equal to 42
int j = 94; //Create the variable j and set it to 94
j = -1 * (i * j + 1138); //You can also use arithmetic signs - Now j is -5086!
</pre>

==Arrays==
An array is a series of the same type of variable. So, a string would be an array of chars. An individual variable in an array is usually called an '''''element'''''

===Array example===
<pre>
int Array[2]; //Create an integer array with two integers
Array~[0] = 42; //Set the first integer to 42
Array~[1] = 94; //Set the second integer to 94
char String[] = "Hello!"; //Create an array of chars (a string) and autosize it to whatever size the given string is
</pre>

==Pointers==
Pointers are difficult to grasp and work with, to say the least, but they're worth it. A pointer is basically the address of a particular variable (sometimes a function). Think of them as the address to a house, or the URL to a site - they aren't the actual house or site, but they let you get to it.

There are two important characters with pointers - '''''&''''' and '''''*'''''. & is used to change a variable to the address of a variable. So, &variable would give you the address of a variable.

The asterisk is the reverse of &. It means the variable at the address given. In other words, *(&variable) is the same thing as variable.

However, the asterisk can also be used to declare a pointer, a special type of variable. Confused yet? Here's an example:

===Pointer example===
<pre>
int i = 42; //Our favorite integer, i
int *integerptr; //This defines a pointer to an integer.
integerptr = &i; //integerptr now points to i
(*integerptr) = 94; //We just changed the value of i!
</pre>

==Functions==
A function is a collection of instructions (usually other functions). Every function has a return type - even if it doesn't. A function with no return type has a return type of '''''void'''''. Otherwise, a function may return with any of the above variable types (A function can't really return a string or array, although it can return a '''''pointer''''' to one).

Functions can also be given arguments, so one function can be used in different places. These arguments can be the same types as a function's return types. This means you can take the return of one function and plug it into another function's arguments.

There are two steps to creating a function. Actually writing the function, and optionally declaring it. Thus, you can declare a function in a header file and use that function through your entire project, but only have the meat of it in one spot. You must declare or write out the function before you use it.

Note that the arguments to a function are not really the variables that are plugged into them. So, if you want to change a variable from inside a function , you will probably have to use a pointer. This is called '''''passing by reference'''''

===Function example===
<pre>
void func1(int a, float b); //Declare func1
int func2() //Define func2
{
return 1; //func2 returns integer 1;
}
int func3(int c) //Define func3
{
func1(c, c + .5); //execute func1
return c; //return c;
}

void func1(int a, float b) //Define func1. It doesn't do anything, basically.
{
float z = a + b; //Make a new variable and add up a and b in it
}

void Execute() //You can't execute a function except from inside another.
{
func1(func2(), func3(func2())); //What will z be?
}
</pre>
==Tutorial One - Baby Steps==
To start out, I'll give a classic example - a "Hello, World!" program written in C. Are you ready? Here it is...
<pre>
#include <stdio.h>

int main(int argc, char** argv)
{
puts("Hello, world!");
return 0;
}
</pre>
----
That wasn't too bad, was it? Here's what each line does:

<pre>!#include <stdio.h></pre>

This line puts the contents of the file "stdio.h" into the current source code file after it's loaded into memory but before it's compiled. The '<' and '>' tell the compiler that it's a library file - that is, it's not part of the current program but in the compiler's own file list. We need this file to get the function declaration for puts().

The entire line is called a '''''preprocessor directive'''''; that's what the '#' is for. The preprocessor does everything before the code is compiled, adding or replacing source code before it's sent off to the compiler. It's useful if you want to make it easy to completely remove a feature from a program.

<pre>int main(int argc, char** argv)</pre>
This defines the main function, which is where execution in a C program always starts. Argc is the number of command-line arguments, argv is the array of command-line arguments. (ie argv[0] might be "-fps")

<pre>{</pre>
Starts the main function's code block

<pre>puts("Hello, world!");</pre>
This function writes "Hello, world!" to the command-line, or console if you're on Linux.

<pre>return 0;</pre>
This can return pretty much anything you like, as long as it's an integer.

<pre>}</pre>
Ends the function block

That's it! A working C program!

==Scope==
The '''''scope''''' of a variable is the area you can get at it. A variable created inside a function only exists inside that function. Basically, anywhere you see brackets like { or } defines a code block. Any time you see these, variables created inside them will only exist inside of them.

===Scope Example===
<pre>
int a = 1;
void func1()
{
//You can access a here, but not c or d
int b;
}

void func2()
{
//You can access a here, but not b or d
if(a)
{
int d = 2;
}
}
</pre>
==Flow control - If statement==
If the code in the parentheses is true, or a nonzero value, then the code statement immediately after it or inside the code block immediately after it is executed. After if, '''''else if''''' may be used to define an alternate option. Or, '''''else''''' may be used to define if none of the else or else if blocks are true

===If example===
<pre>
int a = 1;
int b = 2;
if(a == 0)
{
//Do something fun if a is 0
}
else if(a == 1)
{
//Do something else if a is 1
}
else if(a == 1 && b == 2)
{
//If a is 1, and b is 2, do something here.
//With the above values, this is what would happen.
}
else
{
//Otherwise, do this.
}
</pre>

==Flow control - while statement.==
While the code in the parentheses is true or a nozero value, then the code statement immediately after it or inside the code block immediately after it is executed.

===While example===
<pre>
int i; //Create the variable i
void DoStuff();//Declare teh function DoStuff

i = 0; //Make i be 0
while(i < 42) //While this is true, do whatever's after this
{
DoStuff();
i++; //++ is shorthand for "Add 1 to the variable after this line of code".
//++i; //This would be shorthand for "Add 1 to the variable before this line of code"
//Replace with -- for "Subtract one from"
}
</pre>

==Flow control - for statement==
Usually used to go through array values; essentially a variant of the while loop

===For example===
<pre>
//This does the same thing as the while example
int i;
void DoStuff();

for(i = 0; i < 42; i++)
{
DoStuff();
}
</pre>

==Flow control - switch==
Execute the code after the case statement that matches the value in the parentheses.

===Switch example===
<pre>
//Declare some functions
void DoFunStuff();
void DoSadStuff();
void DoOtherStuff();

//Give ourselves a variable
int a = 2;

switch(a)
{
case 0: //If a is 0...
DoFunStuff(); //...Do fun stuff!
break; //We're done, jump to the end of the code block.
case 1: //If a is 1...
DoSadStuff(); //...aww, crap, we gotta do sad stuff.
break;
default: //If none of the above match...
DoOtherStuff(); //...Do some other stuff.
//Since a IS 2, we'll be doing this other stuff.
break;
}
</pre>

==Structs==
Structs are a block of different types of variables. They help organize code, since then you can group similar variables together. For example:

===Struct Example===
<pre>
struct Person
{
char name[128]; //Name can *only* be 128 letters long, including spaces
unsigned int age; //Granted, ints range from -2,147,483,648 to 2,147,483,648 - but just in case...
unsigned int weight;//Who has negative weight?

}; //<-- this little semicolon is important. Remember him.

//Now we have a function that takes a Person as an argument.
int CarlEatClone(Person poor_fellow)
{
for(;poor_Fellow.weight > 0; poor_fellow.weight--); //Simulate this poor fellow being digested.

//Note that no one is actually harmed, because the poor_fellow is actually a copy.
//Also note how "weight" inside poor_fellow is referenced
}
//Use like this:
//CarlEatClone(TerranGuy);

//In this function, poor_fellow must be a pointer
int CarlEat(Person *poor_fellow)
{
for(;poor_fellow->weight > 0; poor_fellow->weight--);

//Note again how weight is referenced, now that poor_fellow is a pointer
//No cloning is involved here...poor guy.
}
//Use like this:
//CarlEat(&TerranGuy);
</pre>
----
Written by [[User:WMCoolmon|WMCoolmon]]

Talk:Coding In C

2007-07-19T14:21:55Z

AcePace:

Talk:Coding In C

2007-07-17T11:08:38Z

AcePace: -Started talk page, opened discussion on page purpose.

FreeSpace Open Installer

2007-07-17T10:09:39Z

AcePace:

You can use the excellent installer by Turey, that should give you a baseline of everything you need to play. The rest of this guide is full of information if you want to start tweaking things, or tackle things manually. However, for most players, you can stop with this step.

The programs web page is [http://www.fsoinstaller.com/ here]

The most recent Installer includes:

* Retail Freespace 2
* FreeSpace Open 3.6.9 Final (regular and debug)
* FRED2 Open 3.6.9 Final (regular and debug)
* Launcher 5.5a
* launcher6.ini
* Mac Executables
* Soulstorm's OSX Launcher
* fs2open_pxo.cfg
* The OpenAL Installer (optional)
* 3.6.8 Zeta MediaVPs (optional, includes the 710 patches)
* 3.6.8 Zeta adveffects (only for those with high-power systems, requires regular MediaVPs, includes 710 patch)
* .OGG Cutscenes
* Derelict SCP Version (With optional voice)
* Just Another Day 1 & 2 (separate options for each)
* FreeSpace Port
* Awakenings
* Homesick
* Transcend
* Sync

Source:
[http://www.hard-light.net/forums/index.php/topic,42854.0.html Original thread by Turey]

Walkthrough installing


Based off the walkthrough available [http://www.hard-light.net/forums/index.php/topic,47045.0.html here]

This Installer is known to work on Windows, Linux (tested on OpenSuse, Gentoo and Fedora, should work on others), and Mac (OSX Panther, with a hacked install of Java 1.5)

First step is Installing the FreeSpace Open Installer.

REQUIREMENTS AND NOTES
You can update your installation by simply running the Installer again. It will download files that are out of date.

The Installer requires an internet connection to install. This is because:
* It checks to see if it is out of date by pulling the number of the most recent version off of the web.
* It automatically takes you to the download page of the most recent version if your version is out of date.
* It checks that all the files are up-to-date.
* This Install process downloads about 3.3 GB of data, if you download everything. Just so you can prepare; for example, you could set it to download overnight.

Download Links:
[http://www.fsoinstaller.com/files/installer/FreeSpaceOpenInstaller.zip Windows Installer (Zipped .exe, 19 MB)] (Doesn't need Java, get this one if you are unsure and are using Windows)]: Works with Windows without having to use Java. 20 MB in size. Download it, open it, then skip to the "Using the Installer" section.
--this one is "easy" for Windows users. Not that the .JAR version is hard... but if you've never used the Control Panel before, and don't intend to, then use this option.

[http://www.fsoinstaller.com/files/installer/java/FreeSpaceOpenInstaller.jar Win/Linux/Mac Installer (.jar, 26 KB)] (Requires Java 1.5): Works with Windows, Linux, and Mac. 20 KB in size. Requires Java version 1.5 or higher. See "For Java" section, below.
--this one is cross-platform. It's also exactly the same as the .EXE version, except that it requires JAVA, and possibly using the Command Prompt. Don't worry; I have instructions...

You can also get the Installer [http://www.fsoinstaller.com/files/installer/java/ source code here.]

Retail Install:
Note: Use this if you intend to save time by copying essential files from your installation CDs rather then downloading them.
1. Install FreeSpace 2 from your disks, if you haven't already. Install it to C:\Games\FreeSpace2. If you don't have the FS2 Retail Disks, skip down to step 6, below.
2. Now, put disk 2 of FreeSpace 2 back into your CD drive.
3. Copy all the files with the extension of ".MVE" from the disk root directory ( \ ) to the folder C:\Games\FreeSpace2\data\movies\ (create this folder if it doesn't exist)
4. Do the same thing for disk 3.
5. If you ONLY have the FS2 disks, then put this file (right-click Save Target/Link As) in C:\Games\FreeSpace2\Installer\ (create this folder if it doesn't exist) If you have BOTH the FS1 and FS2 disks, skip to the next step.
6. If you don't have the Descent: FreeSpace a.k.a. Conflict: FreeSpace (aka FS1) Disks, then skip to step 10. If you do, insert disk 1 in your CD drive. Copy all of the files with the extension of ".MVE" from the disk directory \Data\movies\ to the folder C:\Games\FreeSpace2\fsport\data\movies\ (create this folder if it doesn't exist)
7. Do the same thing for disk 2.
8. If you ONLY have the Conflict: FreeSpace a.k.a. Descent: FreeSpace (aka FS1) disks (and not the FS2 disks), put this file (right-click, Save Target/Link As) in C:\Games\FreeSpace2\Installer (create this folder if it doesn't exist) If you have BOTH the FS1 and FS2 disks, then skip to the next step.
9. If you have BOTH the FS1 and the FS2 disks, then put this file (right-click, Save Target/Link As) in C:\Games\FreeSpace2\Installer (create this folder if it doesn't exist)
10. Run the Installer, under the "Installing the FreeSpace Open Installer" section, above.

Using the launcher:
1.First window, click next.
2.2. Press "Next" again, or click the big button to change the location for the FreeSpace 2 install. (Don't, unless you have a reason to, eg, you really want another location or you've already installed Retail FS2 to a different directory than C:\Games\FreeSpace2 .)
3. Make sure "Update Installed Sections Only" and "Say Yes to All" are not checked. Then hit "Next".
4-6. If you are a Windows user, select everything, except for "Macintosh (Universal Binary) Executables", and "Launcher for OS X"
If you are a Mac user, select everything, except for "Windows Executables"
7. Wait for the Installer to finish (this may take a long time!). You will know it is done when the "Next" button becomes black, instead of gray.
When it becomes black, click it. This means the installation is finshed.
8. READ the NOTES!!! They might contain important information. After you do, hit "Exit" (The notes are saved in the \FreeSpace2\Installer directory for later viewing.)
9. Hit the Close button on the Command Prompt Window.

OpenAL notes:
10-11. If you don't have it, get OpenAL: (all users, Windows / Mac / Linux)
Go to www.openal.org, and click on the "Downloads" link on the left.
12. Get the correct version for your OS:
Windows users get "1.1 Installer for Windows" -
Note: If you're using Windows, and you have nvopenal.dll or ctoal.dll in your Windows\System32 directory,
then delete them and then install the newest version of OpenAL. These files are older versions, and will cause problems with the new install.
Mac users get Installer for OS X.
Linux users get the Binary RPM, or compile from the source code.

If you have any issues with the installation post [http://www.hard-light.net/forums/index.php/topic,47045.0.html here].

FreeSpace Open Installer

2007-07-17T10:09:18Z

AcePace:

You can use the excellent installer by Turey, that should give you a baseline of everything you need to play. The rest of this guide is full of information if you want to start tweaking things, or tackle things manually. However, for most players, you can stop with this step.

The programs web page is [http://www.fsoinstaller.com/ here]

The most recent Installer includes:

* Retail Freespace 2
* FreeSpace Open 3.6.9 Final (regular and debug)
* FRED2 Open 3.6.9 Final (regular and debug)
* Launcher 5.5a
* launcher6.ini
* Mac Executables
* Soulstorm's OSX Launcher
* fs2open_pxo.cfg
* The OpenAL Installer (optional)
* 3.6.8 Zeta MediaVPs (optional, includes the 710 patches)
* 3.6.8 Zeta adveffects (only for those with high-power systems, requires regular MediaVPs, includes 710 patch)
* .OGG Cutscenes
* Derelict SCP Version (With optional voice)
* Just Another Day 1 & 2 (separate options for each)
* FreeSpace Port
* Awakenings
* Homesick
* Transcend
* Sync

Source:
[http://www.hard-light.net/forums/index.php/topic,42854.0.html Original thread by Turey]

Walkthrough installing


Based off the walkthrough available [http://www.hard-light.net/forums/index.php/topic,47045.0.html here]

This Installer is known to work on Windows, Linux (tested on OpenSuse, Gentoo and Fedora, should work on others), and Mac (OSX Panther, with a hacked install of Java 1.5)

First step is Installing the FreeSpace Open Installer.

REQUIREMENTS AND NOTES
You can update your installation by simply running the Installer again. It will download files that are out of date.

The Installer requires an internet connection to install. This is because:
* It checks to see if it is out of date by pulling the number of the most recent version off of the web.
* It automatically takes you to the download page of the most recent version if your version is out of date.
* It checks that all the files are up-to-date.
* This Install process downloads about 3.3 GB of data, if you download everything. Just so you can prepare; for example, you could set it to download overnight.

Download Links:
[http://www.fsoinstaller.com/files/installer/FreeSpaceOpenInstaller.zip Windows Installer (Zipped .exe, 19 MB)] (Doesn't need Java, get this one if you are unsure and are using Windows)]: Works with Windows without having to use Java. 20 MB in size. Download it, open it, then skip to the "Using the Installer" section.
--this one is "easy" for Windows users. Not that the .JAR version is hard... but if you've never used the Control Panel before, and don't intend to, then use this option.

[http://www.fsoinstaller.com/files/installer/java/FreeSpaceOpenInstaller.jar Win/Linux/Mac Installer (.jar, 26 KB)] (Requires Java 1.5): Works with Windows, Linux, and Mac. 20 KB in size. Requires Java version 1.5 or higher. See "For Java" section, below.
--this one is cross-platform. It's also exactly the same as the .EXE version, except that it requires JAVA, and possibly using the Command Prompt. Don't worry; I have instructions...

You can also get the Installer [http://www.fsoinstaller.com/files/installer/java/ source code here.]

Retail Install:
Note: Use this if you intend to save time by copying essential files from your installation CDs rather then downloading them.
1. Install FreeSpace 2 from your disks, if you haven't already. Install it to C:\Games\FreeSpace2. If you don't have the FS2 Retail Disks, skip down to step 6, below.
2. Now, put disk 2 of FreeSpace 2 back into your CD drive.
3. Copy all the files with the extension of ".MVE" from the disk root directory ( \ ) to the folder C:\Games\FreeSpace2\data\movies\ (create this folder if it doesn't exist)
4. Do the same thing for disk 3.
5. If you ONLY have the FS2 disks, then put this file (right-click Save Target/Link As) in C:\Games\FreeSpace2\Installer\ (create this folder if it doesn't exist) If you have BOTH the FS1 and FS2 disks, skip to the next step.
6. If you don't have the Descent: FreeSpace a.k.a. Conflict: FreeSpace (aka FS1) Disks, then skip to step 10. If you do, insert disk 1 in your CD drive. Copy all of the files with the extension of ".MVE" from the disk directory \Data\movies\ to the folder C:\Games\FreeSpace2\fsport\data\movies\ (create this folder if it doesn't exist)
7. Do the same thing for disk 2.
8. If you ONLY have the Conflict: FreeSpace a.k.a. Descent: FreeSpace (aka FS1) disks (and not the FS2 disks), put this file (right-click, Save Target/Link As) in C:\Games\FreeSpace2\Installer (create this folder if it doesn't exist) If you have BOTH the FS1 and FS2 disks, then skip to the next step.
9. If you have BOTH the FS1 and the FS2 disks, then put this file (right-click, Save Target/Link As) in C:\Games\FreeSpace2\Installer (create this folder if it doesn't exist)
10. Run the Installer, under the "Installing the FreeSpace Open Installer" section, above.

Using the launcher:
1.First window, click next.
2.2. Press "Next" again, or click the big button to change the location for the FreeSpace 2 install. (Don't, unless you have a reason to, eg, you really want another location or you've already installed Retail FS2 to a different directory than C:\Games\FreeSpace2 .)
3. Make sure "Update Installed Sections Only" and "Say Yes to All" are not checked. Then hit "Next".
4-6. If you are a Windows user, select everything, except for "Macintosh (Universal Binary) Executables", and "Launcher for OS X"
If you are a Mac user, select everything, except for "Windows Executables"
7. Wait for the Installer to finish (this may take a long time!). You will know it is done when the "Next" button becomes black, instead of gray.
When it becomes black, click it. This means the installation is finshed.
8. READ the NOTES!!! They might contain important information. After you do, hit "Exit" (The notes are saved in the \FreeSpace2\Installer directory for later viewing.)
9. Hit the Close button on the Command Prompt Window.

OpenAL notes:
10-11. If you don't have it, get OpenAL: (all users, Windows / Mac / Linux)
Go to www.openal.org, and click on the "Downloads" link on the left.
12. Get the correct version for your OS:
Windows users get "1.1 Installer for Windows" -
Note: If you're using Windows, and you have nvopenal.dll or ctoal.dll in your Windows\System32 directory, then delete them and then install the newest version of OpenAL. These files are older versions, and will cause problems with the new install.
Mac users get Installer for OS X.
Linux users get the Binary RPM, or compile from the source code.

If you have any issues with the installation post [http://www.hard-light.net/forums/index.php/topic,47045.0.html here].

Talk:FreeSpace Open Installer

2007-07-17T10:08:06Z

AcePace: -Started Talk page, added formatting and content discussions.

Formatting--
I'm a newb to Wiki editings and I have no idea how to properly format these things, mostly copy pasting what already is on a page. If someone can clean this up, I'd be happy.

Content--
I pretty much copy pasted the walkthrough in HLP, but it needs some minor edits, actully..not so minor, but damn sight better then what existed before.

FreeSpace Open Installer

2007-07-17T10:06:51Z

AcePace: Redid the page, I need some help with the formatting.

You can use the excellent installer by Turey, that should give you a baseline of everything you need to play. The rest of this guide is full of information if you want to start tweaking things, or tackle things manually. However, for most players, you can stop with this step.

The programs web page is [http://www.fsoinstaller.com/ here]

The most recent Installer includes:

* Retail Freespace 2
* FreeSpace Open 3.6.9 Final (regular and debug)
* FRED2 Open 3.6.9 Final (regular and debug)
* Launcher 5.5a
* launcher6.ini
* Mac Executables
* Soulstorm's OSX Launcher
* fs2open_pxo.cfg
* The OpenAL Installer (optional)
* 3.6.8 Zeta MediaVPs (optional, includes the 710 patches)
* 3.6.8 Zeta adveffects (only for those with high-power systems, requires regular MediaVPs, includes 710 patch)
* .OGG Cutscenes
* Derelict SCP Version (With optional voice)
* Just Another Day 1 & 2 (separate options for each)
* FreeSpace Port
* Awakenings
* Homesick
* Transcend
* Sync

Source:
[http://www.hard-light.net/forums/index.php/topic,42854.0.html Original thread by Turey]

Walkthrough installing


Based off the walkthrough available [http://www.hard-light.net/forums/index.php/topic,47045.0.html here]

This Installer is known to work on Windows, Linux (tested on OpenSuse, Gentoo and Fedora, should work on others), and Mac (OSX Panther, with a hacked install of Java 1.5)

First step is Installing the FreeSpace Open Installer.

REQUIREMENTS AND NOTES
You can update your installation by simply running the Installer again. It will download files that are out of date.

The Installer requires an internet connection to install. This is because:
* It checks to see if it is out of date by pulling the number of the most recent version off of the web.
* It automatically takes you to the download page of the most recent version if your version is out of date.
* It checks that all the files are up-to-date.
* This Install process downloads about 3.3 GB of data, if you download everything. Just so you can prepare; for example, you could set it to download overnight.

Download Links:
[http://www.fsoinstaller.com/files/installer/FreeSpaceOpenInstaller.zip Windows Installer (Zipped .exe, 19 MB)] (Doesn't need Java, get this one if you are unsure and are using Windows)]: Works with Windows without having to use Java. 20 MB in size. Download it, open it, then skip to the "Using the Installer" section.
--this one is "easy" for Windows users. Not that the .JAR version is hard... but if you've never used the Control Panel before, and don't intend to, then use this option.

[http://www.fsoinstaller.com/files/installer/java/FreeSpaceOpenInstaller.jar Win/Linux/Mac Installer (.jar, 26 KB)] (Requires Java 1.5): Works with Windows, Linux, and Mac. 20 KB in size. Requires Java version 1.5 or higher. See "For Java" section, below.
--this one is cross-platform. It's also exactly the same as the .EXE version, except that it requires JAVA, and possibly using the Command Prompt. Don't worry; I have instructions...

You can also get the Installer [http://www.fsoinstaller.com/files/installer/java/ source code here.]

Retail Install:
Note: Use this if you intend to save time by copying essential files from your installation CDs rather then downloading them.
1. Install FreeSpace 2 from your disks, if you haven't already. Install it to C:\Games\FreeSpace2. If you don't have the FS2 Retail Disks, skip down to step 6, below.
2. Now, put disk 2 of FreeSpace 2 back into your CD drive.
3. Copy all the files with the extension of ".MVE" from the disk root directory ( \ ) to the folder C:\Games\FreeSpace2\data\movies\ (create this folder if it doesn't exist)
4. Do the same thing for disk 3.
5. If you ONLY have the FS2 disks, then put this file (right-click Save Target/Link As) in C:\Games\FreeSpace2\Installer\ (create this folder if it doesn't exist) If you have BOTH the FS1 and FS2 disks, skip to the next step.
6. If you don't have the Descent: FreeSpace a.k.a. Conflict: FreeSpace (aka FS1) Disks, then skip to step 10. If you do, insert disk 1 in your CD drive. Copy all of the files with the extension of ".MVE" from the disk directory \Data\movies\ to the folder C:\Games\FreeSpace2\fsport\data\movies\ (create this folder if it doesn't exist)
7. Do the same thing for disk 2.
8. If you ONLY have the Conflict: FreeSpace a.k.a. Descent: FreeSpace (aka FS1) disks (and not the FS2 disks), put this file (right-click, Save Target/Link As) in C:\Games\FreeSpace2\Installer (create this folder if it doesn't exist) If you have BOTH the FS1 and FS2 disks, then skip to the next step.
9. If you have BOTH the FS1 and the FS2 disks, then put this file (right-click, Save Target/Link As) in C:\Games\FreeSpace2\Installer (create this folder if it doesn't exist)
10. Run the Installer, under the "Installing the FreeSpace Open Installer" section, above.

Using the launcher:
1.First window, click next.
2.2. Press "Next" again, or click the big button to change the location for the FreeSpace 2 install. (Don't, unless you have a reason to, eg, you really want another location or you've already installed Retail FS2 to a different directory than C:\Games\FreeSpace2 .)
3. Make sure "Update Installed Sections Only" and "Say Yes to All" are not checked. Then hit "Next".
4-6. If you are a Windows user, select everything, except for "Macintosh (Universal Binary) Executables", and "Launcher for OS X"
If you are a Mac user, select everything, except for "Windows Executables"
7. Wait for the Installer to finish (this may take a long time!). You will know it is done when the "Next" button becomes black, instead of gray.
When it becomes black, click it. This means the installation is finshed.
8. READ the NOTES!!! They might contain important information. After you do, hit "Exit" (The notes are saved in the \FreeSpace2\Installer directory for later viewing.)
9. Hit the Close button on the Command Prompt Window.

OpenAL notes:
10-11. If you don't have it, get OpenAL: (all users, Windows / Mac / Linux)
Go to www.openal.org, and click on the "Downloads" link on the left.
12. Get the correct version for your OS:
Windows users get "1.1 Installer for Windows" - note: If you're using Windows, and you have nvopenal.dll or ctoal.dll in your Windows\System32 directory, then delete them and then install the newest version of OpenAL. These files are older versions, and will cause problems with the new install.
Mac users get Installer for OS X
Linux users get the Binary RPM, or compile from the source code.

If you have any issues with the installation post [http://www.hard-light.net/forums/index.php/topic,47045.0.html here].

Source pcxutils

2007-07-15T12:08:00Z

AcePace: /* Major Classes/Functions/Structs */ -Added another function, even if it's not really used, to have it there.

==Summary==
Contains low-level routines for loading .pcx 2d graphics files.

==Major Classes/Functions/Structs==
{| border="1" cellspacing="0" cellpadding="4"
|-
! Class/Group/Struct
! Method/Function/Element
! Notes
|-
| rowspan = 3 | pcx_* functions
| pcx_read_bitmap*()
| Various funcitons to read the bitmap contents from different format .pcx files (8 bit, 16 bit etc.).
|-
| pcx_read_header()
| Reads the header from a .pcx file
|-
| pcx_write_bitmap()
| Dumps a 8bpp bitmap to a file.
|}

[[Category:2d Graphics]]

User talk:Wanderer

2007-07-15T12:00:30Z

AcePace:

RE: Your suggestion for the TBP ships; basically I'm using the thing that I am for that because I directly copied the entry for the Ulysses and its components, and from there on I've gone ahead copying from my last entry and altering what needs to be changed. So I probably won't be changing those anytime soon. If it bothers you that much you're welcome to alter them, but as the functional equivalent is the same, I really can't be moved to care much. [[User:ngtm1r|ngtm1r]]

Thanks for the additions to [[Species_defs.tbl]]. I'm using an old version, and I knew there was stuff I was missing. [[User:Black Wolf|Black Wolf]] 18:31, 13 Nov 2005 (CET)

No problems. I also got a few ideas from the entry you made. Like building all the table files around the same format for easier reference (Yeah, i must be dreaming, only an idiot would have this kind of ideas... ...what that makes out of me?). [[User:Wanderer|Wanderer]] 19:05, 13 Nov 2005 (CET)

== Big thanks ==

Big thanks for all the work you're doing on individual ship entries - I've put in a request with the admins for some official recognition, probably a custom user title on the forums, though the actual title will be admin discretion (as will the granting of it in the first place, but personally I reckon you're a shoe in). [[User:Black Wolf|Black Wolf]] 05:14, 16 Dec 2005 (GMT)

== Good job ==

Nice job maintining the FS Wiki --[[User:Nubbles|Nubbles]] 22:10, 16 June 2007 
The ship images are great. Good job. --[[User:Moniter|Mars]] 20:34, 20 June 2006 (BST) 
Thank you, Wanderer, for holding off the bots. The Hard Light community owes you one. [[User:Mustang19|Mustang19]] 
Nice work, though damn if it's not weird seeing us both do a series of edits at the same time.

Manually Installing FreeSpace 2 Open

2007-07-15T11:39:25Z

AcePace: /* System Requirements */ -Added SOME data, better then nothing.

= CURRENTLY COLLATING INFORMATION FOR THIS PAGE =
: [[User:Fractux|Fractux]] 10:22, 13 April 2007 (CDT)
'''FOR NOW, GO TO: [[Getting Started(Main)]]'''
----
----

== Before you Begin ==

===System Requirements===
While the original FreeSpace 2 has rather low system requirments, such as a Pentium 200MHz, 32 MB RAM (64 recommended), and a 3D accelerator (Direct3D, Glide) required, FreeSpace 2 Open has slightly higher requirments. However, any computer from the early 2000s should be able to play this, though toggling all the modern graphical eye candy will require a more modern computer.

== FreeSpace Open Installer ==

You can use the excellent installer by [http://www.hard-light.net/forums/index.php?action=profile;u=3428 Turey], that should give you a baseline of everything you need to play.

There are two versions of the installer that you can download:

*[http://www.fsoinstaller.com/files/installer/FreeSpaceOpenInstaller.zip Windows Installer (Zipped .exe, 19 MB)] (Windows)
*[http://www.fsoinstaller.com/files/installer/java/FreeSpaceOpenInstaller.jar Win/Linux/Mac Installer (.jar, 26 KB)] (Requires [http://www.java.com/ Java 1.5 +])
**You can get the source code to the Java Installer [http://www.fsoinstaller.com/files/installer/java/ here].

This Installer is known to work on Windows, Linux (tested on Gentoo, Fedora, Ubuntu), and Mac (OSX Panther, with a hacked install of Java 1.5) (more info for users)

The most recent installer version of the Installer allows you to download:
(As of April 12, 2007)

*FreeSpace 2

*Windows:
**FreeSpace Open 3.6.9 Final (regular and debug)
**FRED2 Open 3.6.9 Final (regular and debug)
**FreeSpace Open Launcher 5.5a

*Macintosh:
**FreeSpace Open 3.6.9 Final (regular and debug)
**Soulstorm's OSX Launcher

*The OpenAL Installer ('''NOTE:''' [http://www.openal.org/ OpenAL] must be installed to run FS2 Open)

*3.6.8 Zeta Media VP Files (optional, includes 710 patch)
*3.6.8 Zeta Advanced effects (only for those with high-end systems. Requires regular Media VP Files, includes 710 patch)

*.OGG Cutscenes

'''Modifications available for Direct Download: '''
* Derelict SCP Version (With optional voice)
* Just Another Day 1 & 2 (separate options for each)
* FreeSpace Port
* Awakenings
* Homesick
* Transcend
* Sync

=== Requirements and Notes ===
You can update your installation by simply running the Installer again. This will download any files that are out of date.

The Installer requires an internet connection to install.
* It checks to see if your installation files are out of date via the web.
* It automatically takes you to the download page of the most recent version, if your version is out of date.

Source: [http://www.hard-light.net/forums/index.php/topic,42854.0.html Original thread by Turey]

=== Linux Specific Information ===

Pre-Compiled binaries for FS2 Open 3.6.9 Final are not currently available in the Installer.

You have two options:
* Use Pre-Compiled binaries available [http://www.hard-light.net/forums/index.php/board,113.0.html here] or [http://www.hard-light.net/forums/index.php/board,97.0.html here]. (Check both locations for the most up to date binary)
* Download the source from CVS. Follow the instruction in the article covering [Fs2 open on Linux|FS2 on Linux].

== Manual Installation Guide ==

=== Linux Specific Information ===

Derelict

2007-07-15T11:21:52Z

AcePace:

{| border=0 align=right cellpadding=4 cellspacing=1 width=30% style="margin: 0 0 1em 1em; background: #202020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%;"|'''''Mod Info'''''
|-
! style="color: white; height: 30px; 70%;"|[[Derelict Mission Walkthrough]]
|}
==General Info==
'''Original Authors:''' John 'Agatheron' Crowdis, Chris 'Kellan' Regan, Robert 'Dark' Wild, and Rodrigo 'Styxx' Barni. 
'''Update Author:''' Blaise Russel. 
'''Missions:''' 46 
'''Mods included:''' 
[[GTA Cypher]] 
[[GTB Hydra]] 
[[Shivan Knossos]]

 
'''SCP Required'''

Derelict is widely considered to be one of the best user-created mods. Derelict SCP was enhanced in 2006 by a complete set of voiceovers, in addition, several of the missions have been cleaned up.

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

The loss of Capella created serious economic hardship throughout the Alliance, a new Great Depression is upon us. The complete loss of the planetary resources and economic foundation of a rich world was devastating in its own right, but that is not all. Two hundred million refugees continue to walk the stars, seeking a new home. Some have settled, while others have been forced to move from place to place, hoping that the next place may welcome them with open arms.

While the Galactic Terran-Vasudan Alliance continues to hold, the current depression has given way to political instability. Local governments rise and fall as often lunar tides, organized crime and piracy have prospered in a black market environment. It seems no one is immune. Radical voices are raising echoes not heard since the blood cries of the Neo-Terran Front. The Ghosts of the past are catching up with us.

Since collapsing the Capella Jump Node, the recovering GTVA Fleet has spent much of its time and resources in police actions. Our own resources are taxed to the limit, and yet still we have the challenge to live up to our calling. Even so, it is alarming that there are those who are starting to take matters into their own hands.

What happens in the political arena is not our concern today. As part of the GTVA forces, ours is to keep space safe for our citizens

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.

This is not an easy assignment, pilot. You will often be working in less-than-ideal conditions, but we trust that your skill will help to bring some much needed relief to this region.

==Player Comments==

''Definately download worthy. One of the best user made campaign I ever played with brilliant atmosphere.''

''A masterpiece of user made campaigns. Hailed by many as one of the best. Great in depth storyline, atmosphere and intense action.'' ~ KR

''Renowned by many to be the best FreeSpace 2 fan-made campaign made, Derelict is definitely worth a (several) play through(s)''

==Related Links==
[http://nix1999.shackspace.com/ Download Site] provided by ShackSpace 
[http://www.hard-light.net/forums/index.php?topic=38019.0.html Release Thread] 
[http://freespace.volitionwatch.com/derelict/index.shtml Derelict on Volition Watch] 
[http://www.nukelol.com/downloads/freespacefiles/campaigns/derelict_scp/derelict.zip Derelict SCP Mirror 1]

[[Category:User-made_Campaigns]]

I believe this campaign could easily be considered one of the best ever made. You do not believe me? Then go play it! It is a jewel, a well polished one!

[[Category: Derelict]]

Self-destruct

2007-07-15T10:59:08Z

AcePace:

The Self-Destruct sexp immediately sets a ships health to zero.
This triggers the ships destruct animation rather then dissapearing the ship, if that is what you meant to do, there are better SEXPs.

Testing

2007-07-15T10:46:57Z

AcePace: -One small addition.

==Guide to Testing for mission designers==
Keywords: Patience, Time, Circumspection, Purposefulness

*Never be afraid of testing. Always be straightforward and logical: If you think that part is buggy and you are afraid that you discover that you did something wrong, other people, who played that mission will warn you and that's most inconvenient. 
*Do not be afraid of time: the more time you spend to look after your mission the better it will become, the more ideas you will get how to make it better. 
*Never, never, never get annoyed by a bug you can fix. If a debriefing shows up at a bad time every time you test your mission, keep cool. Open up the debriefing window, look at the SEXP tree and think slowly, logically and first of all, calmly. The more time you spend with a bug the more chance you have to fix it. If you manage to fix a problem that you had been fighting with for hours, you will feel more deliberated. 
*Never be satisfied: Always want to add new things. If needed, sit ten, twenty or even thirty minutes looking onto the boring grid of FRED while thinking into the possible ways of adding new items. Look into the Events window and zoom in/out at the ships and an idea will soon come what to add. 
*If testing makes you sick, consult your General Practician 
*Use the Designer's notes! Note down bugs you do not want to fix in the moment you discovered it, note down anything you will want to add. Keep erasing your notes as soon as they become obsolete. Do not let others see your mission until there are any notes left. This window can also be used to communicate with other mission designers, if not only you have been assigned to that mission. 
*Concentrate on fixing only one bug: Do not try to fix multiple bugs unless you are sure it won't need any testing after you have fixed it(typing mistakes, no ships in escort list, etc). 
*Never release a mission without testing its last version twice or three times. A seemingly minor change like changing wing delays can result in unexpected difficulties.
*Never be the sole tester, give it out to others, preferably from any skill level, to test for difficulty, pacing, etc. What works for you, might not work for others.

=See also=
[[General hints]] 
[[Typical mistakes]] 
[[Tips for mission balancing]]

[[Category:FRED Tips]]

Volition

2007-07-15T10:36:39Z

AcePace: -Added some fluff.

'''Volition''' is the developer and publisher of the ''FreeSpace'' series. The most notable programs Volition developed was FreeSpace and [[Wikipedia:Red Faction|Red Faction]].

In 1993 Parallax software was founded, and made both Descent 1 and 2, in 1996, Parallax software and Outrage entertainment merged to form '''Volition''', which started work on the Freespace series. FreeSpace 1 was released in 1998 and FreeSpace 2 in 1999. In 2000, the company was aquired by THQ and continued working on several more games.

Currently, Volition is working on Saints Row 2 for the Xbox360, after the moderately sucessful Saints Row. Other games that Volition has developed(besides FreeSpace and Red Faction) are Summoner 1 and 2, the Descent series and a sequal to Red Faction.

==External links==
*[[wikipedia:Volition Inc.|Volition]] on Wikipedia
*[http://www.volition-inc.com Volition inc. website]

{{stub}}

Source Code Reference

2007-07-15T10:26:23Z

AcePace: /* Alphabetical view */ -Another guess from a quick look at the source.

== External libraries ==

Freespace2 relies on the following libraries, which are included in the source tree:
* lua: LUA Scripting language
* libjpeg: Jpeg library
* oggvorbis: Ogg Vorbis sound library
* dx8sdk: DirectX 8 SDK
* dx9sdk: DirectX 9 SDK

See msdn.microsoft.com for discussion of the DirectX libraries. For the other libraries, look in the README files for more info

== Freespace2 Source Code ==

The root also contains the actual Freespace2 code, in the code/ directory. The Freespace2 source code consists in several components, each of which is kept in a separate subdirectory. These components are listed below, from different views.

=== Alphabetical view ===

* [[Source ai|ai]] (Computer AI)
* [[Source anim|anim]] (Displaying .ani animated bitmaps)
* asteroid (Handle asteroids - movement, collisions, creating smaller asteriods when larger ones are blown up etc.)
* autopilot (Handles autopilot control - where if there are no enemies, travelling a long distance etc. control is temporarily switched to the computer)
* [[Source bmpman|bmpman]] (Manage 2d graphics files, such as .bmp, .tga, .jpg etc.)
* camera (???)
* cfile (File/directory management routines including .VP file handling that are OS independent eg. handles differences between Linux & Windows)
* cmdline (Handles command line switches, such as -mipmap etc.)
* cmeasure (Handles countermeasures - flares that the player & AI can drop to disrupt missiles)
* controlconfig (Configures keyboard/mouse/joystick controls)
* cutscene (Handles cutscene viewing)
* [[Source ddsutils|ddsutils]] (Handles compressed textures for 3d graphics cards that support it)
* debris (Creates & handles flying debris from exploding ships)
* debugconsole (Handles debugging console and file)
* decals (Adds support for painting decals - small 2d textures - onto ships etc.)
* demo (Allows you to save & playback games to show as demos)
* directx (Specific includes for the Microsoft DirectX library - Windows only)
* exceptionhandler (Deals with crashes, saving stack trace, system info etc.)
* fireball (Displays & handles fireballs and warping effects)
* freespace2 (Main code - handles engine initialisation, loading resources, plus windows resources like icons & dialog boxes)
* fs2open_pxo (Network code)
* gamehelp (Displays context sensitive help text)
* gamesequence (Handles progression of events during a campaign, such as entering a mission, showing credits etc.)
* gamesnd (Handles sounds & music)
* globalincs (Basic global constants & definitions, eg. version, colours)
* [[Source graphics|graphics]] (Low-level wrapper for all 2d & 3d graphics that handles different display engines (DirectX, OpenGL etc)
* hud (Handles the HUD - all the 2d cockpit graphics that the player can see eg. radar, ammo, escort list, sqaud etc)
* iff_defs (Handles traitor ships???)
* io (Handles IO devices, such as keyboard, mouse & joystick)
* irc (Adds support for an IRC chat client)
* [[Source jpgutils|jpgutils]] (Opens, reads JPG files)
* jumpnode (Displays & handles jump nodes)
* lab (Responsible for lab model display?)
* lighting (Handles light sources, and their effect on ships)
* localization (Handles a global string table for translating all written text into foreign languages)
* math (Library of math routines for handling vectors, splines etc)
* menuui (Handles all the misc user interface, such as the main menu, tech room, campaign list etc)
* mission (Handles general mission actions eg. briefing, goals, training info, in-mission messages etc)
* missionui (Handles UI for general mission actions)
* mm (Headers for older MS Multimedia library)
* model (Displays and handles ship models eg. reading files, collission detection etc)
* nebula (Displays and handles nebulae)
* network (All multi-player code, eg. UI, network traffic)
* object (High-level code to handle all objects eg. ships, weapons, debris, asteroids, waypoints, fireballs, shockwaves)
* observer (Handles all non player ship views? Maybe the external views stuff, or death observation?)
* osapi (Wraps low-level Operating System calls, for different OS, eg. multi-threads, windows event loops, main app window)
* palman (Handles bitmap palettes - different colour maps for the same 2d bitmap)
* parse (Handles scripting files, eg. python, LUA etc)
* particle (Displays and handles particles, such as smoke, fire)
* [[Source pcxutils|pcxutils]] (Handles 2d .pcx graphics files)
* physics (Handles realistic physical behaviour of objects, such as ship acceleration/deceleration, rotation etc.)
* playerman (Handles pilot files & player ship movement)
* popup (Displays & handles 2d pop-up windows, eg. when the player dies)
* radar (Displays & handles the radar)
* [[Source render|render]] (Low-level 3d rendering code for some primitives)
* ship (Displays & handles all ship code, eg. shields, afterburner)
* sound (Low-level sound, speach & music routines)
* species_defs (Reads species_defs.tbl to handle different behaviour for different species)
* starfield (Displays & handles background images such as starfields, nebulae etc)
* stats (Displays & handles player statistics, medals etc)
* [[Source tgautils|tgautils]] (Handles .tga 2d graphics files)
* ui (Low-level user inteface routines eg. buttons, scrollbars)
* vcodec (Handles player voice streaming for multiplayer ???)
* weapon (Displays & handles everything to do with weapons)
* windows_stub (Low-level windows functions that are needed for Unix)

There are also some directories that are only used for generating tools (not part of the main fs2 executable):
* cfilearchiver (Creates .VP file archives)
* cfileextractor (Extracts .VP file archives)
* cryptstring (Creates encrypted strings)
* fred2 (The FReespace EDitor)
* inetfile (FTP & HTTP network handlers)
* scramble (Utility to scramble file tables for the Demo version)
* variables (???)
* wxfred2 (Cross-platform version of FRED2)

=== Layer view ===

* Infrastructure
** System
*** cfile/
*** exceptionhandler/
*** irc/
*** localization/
*** osapi/
** Math
*** math/
** Sound
*** sound/
*** vcodec/
** Windows
*** ui/
*** windows_stub/
** 2D graphics
*** [[Source anim|anim]]
*** [[Source bmpman|bmpman]]
*** [[Source ddsutils|ddsutils]]
*** [[Source jpgutils|jpgutils]]
*** [[Source pcxutils|pcxutils]]
*** [[Source tgautils|tgautils]]
*** palman/
** 3D graphics
*** decals/
*** mm/
*** directx/
*** [[Source graphics|graphics]]
*** camera/
*** [[Source render|render]]
** User Input
*** controlconfig/
*** io/
* Freespace2
** Common
*** globalincs/
*** cutscene/
*** cmdline/
*** debugconsole/
** In Space
*** [[Source ai|ai]]
*** asteroid/
*** autopilot/
*** cmeasure/
*** debris/
*** demo/
*** fireball/
*** gamehelp/
*** gamesequence/
*** gamesnd/
*** hud/
*** iff_defs/
*** jumpnode/
*** lighting/
*** nebula/
*** object/
*** observer/
*** model/
*** network/
*** particle/
*** parse/
*** popup/
*** physics/
*** radar/
*** ship/
*** species_defs/
*** starfield/
*** weapon/
** In Base
*** stats/
*** menuui/
*** mission/
*** missionui/
** Engine
*** fs2open_pxo/
*** freespace2/
*** playerman/
* FRED
** fred2/
** wxfred2/
* Tools
** cfilearchiver/
** cfileextractor/
** cryptstring/
** lab/
** scramble/
** inetfile/
** variables/

=== Category Browser ===
The subdirectories above are also categorised by function. See the Category:Source Code to browse this way.

[[Category:Source Code]]

Source Code Reference

2007-07-15T10:22:30Z

AcePace: /* Alphabetical view */ -Changed lab header from my guess.

== External libraries ==

Freespace2 relies on the following libraries, which are included in the source tree:
* lua: LUA Scripting language
* libjpeg: Jpeg library
* oggvorbis: Ogg Vorbis sound library
* dx8sdk: DirectX 8 SDK
* dx9sdk: DirectX 9 SDK

See msdn.microsoft.com for discussion of the DirectX libraries. For the other libraries, look in the README files for more info

== Freespace2 Source Code ==

The root also contains the actual Freespace2 code, in the code/ directory. The Freespace2 source code consists in several components, each of which is kept in a separate subdirectory. These components are listed below, from different views.

=== Alphabetical view ===

* [[Source ai|ai]] (Computer AI)
* [[Source anim|anim]] (Displaying .ani animated bitmaps)
* asteroid (Handle asteroids - movement, collisions, creating smaller asteriods when larger ones are blown up etc.)
* autopilot (Handles autopilot control - where if there are no enemies, travelling a long distance etc. control is temporarily switched to the computer)
* [[Source bmpman|bmpman]] (Manage 2d graphics files, such as .bmp, .tga, .jpg etc.)
* camera (???)
* cfile (File/directory management routines including .VP file handling that are OS independent eg. handles differences between Linux & Windows)
* cmdline (Handles command line switches, such as -mipmap etc.)
* cmeasure (Handles countermeasures - flares that the player & AI can drop to disrupt missiles)
* controlconfig (Configures keyboard/mouse/joystick controls)
* cutscene (Handles cutscene viewing)
* [[Source ddsutils|ddsutils]] (Handles compressed textures for 3d graphics cards that support it)
* debris (Creates & handles flying debris from exploding ships)
* debugconsole (Handles debugging console and file)
* decals (Adds support for painting decals - small 2d textures - onto ships etc.)
* demo (Allows you to save & playback games to show as demos)
* directx (Specific includes for the Microsoft DirectX library - Windows only)
* exceptionhandler (Deals with crashes, saving stack trace, system info etc.)
* fireball (Displays & handles fireballs and warping effects)
* freespace2 (Main code - handles engine initialisation, loading resources, plus windows resources like icons & dialog boxes)
* fs2open_pxo (Network code)
* gamehelp (Displays context sensitive help text)
* gamesequence (Handles progression of events during a campaign, such as entering a mission, showing credits etc.)
* gamesnd (Handles sounds & music)
* globalincs (Basic global constants & definitions, eg. version, colours)
* [[Source graphics|graphics]] (Low-level wrapper for all 2d & 3d graphics that handles different display engines (DirectX, OpenGL etc)
* hud (Handles the HUD - all the 2d cockpit graphics that the player can see eg. radar, ammo, escort list, sqaud etc)
* iff_defs (Handles traitor ships???)
* io (Handles IO devices, such as keyboard, mouse & joystick)
* irc (Adds support for an IRC chat client)
* [[Source jpgutils|jpgutils]] (Opens, reads JPG files)
* jumpnode (Displays & handles jump nodes)
* lab (Responsible for lab model display?)
* lighting (Handles light sources, and their effect on ships)
* localization (Handles a global string table for translating all written text into foreign languages)
* math (Library of math routines for handling vectors, splines etc)
* menuui (Handles all the misc user interface, such as the main menu, tech room, campaign list etc)
* mission (Handles general mission actions eg. briefing, goals, training info, in-mission messages etc)
* missionui (Handles UI for general mission actions)
* mm (Headers for older MS Multimedia library)
* model (Displays and handles ship models eg. reading files, collission detection etc)
* nebula (Displays and handles nebulae)
* network (All multi-player code, eg. UI, network traffic)
* object (High-level code to handle all objects eg. ships, weapons, debris, asteroids, waypoints, fireballs, shockwaves)
* observer (???)
* osapi (Wraps low-level Operating System calls, for different OS, eg. multi-threads, windows event loops, main app window)
* palman (Handles bitmap palettes - different colour maps for the same 2d bitmap)
* parse (Handles scripting files, eg. python, LUA etc)
* particle (Displays and handles particles, such as smoke, fire)
* [[Source pcxutils|pcxutils]] (Handles 2d .pcx graphics files)
* physics (Handles realistic physical behaviour of objects, such as ship acceleration/deceleration, rotation etc.)
* playerman (Handles pilot files & player ship movement)
* popup (Displays & handles 2d pop-up windows, eg. when the player dies)
* radar (Displays & handles the radar)
* [[Source render|render]] (Low-level 3d rendering code for some primitives)
* ship (Displays & handles all ship code, eg. shields, afterburner)
* sound (Low-level sound, speach & music routines)
* species_defs (Reads species_defs.tbl to handle different behaviour for different species)
* starfield (Displays & handles background images such as starfields, nebulae etc)
* stats (Displays & handles player statistics, medals etc)
* [[Source tgautils|tgautils]] (Handles .tga 2d graphics files)
* ui (Low-level user inteface routines eg. buttons, scrollbars)
* vcodec (Handles player voice streaming for multiplayer ???)
* weapon (Displays & handles everything to do with weapons)
* windows_stub (Low-level windows functions that are needed for Unix)

There are also some directories that are only used for generating tools (not part of the main fs2 executable):
* cfilearchiver (Creates .VP file archives)
* cfileextractor (Extracts .VP file archives)
* cryptstring (Creates encrypted strings)
* fred2 (The FReespace EDitor)
* inetfile (FTP & HTTP network handlers)
* scramble (Utility to scramble file tables for the Demo version)
* variables (???)
* wxfred2 (Cross-platform version of FRED2)

=== Layer view ===

* Infrastructure
** System
*** cfile/
*** exceptionhandler/
*** irc/
*** localization/
*** osapi/
** Math
*** math/
** Sound
*** sound/
*** vcodec/
** Windows
*** ui/
*** windows_stub/
** 2D graphics
*** [[Source anim|anim]]
*** [[Source bmpman|bmpman]]
*** [[Source ddsutils|ddsutils]]
*** [[Source jpgutils|jpgutils]]
*** [[Source pcxutils|pcxutils]]
*** [[Source tgautils|tgautils]]
*** palman/
** 3D graphics
*** decals/
*** mm/
*** directx/
*** [[Source graphics|graphics]]
*** camera/
*** [[Source render|render]]
** User Input
*** controlconfig/
*** io/
* Freespace2
** Common
*** globalincs/
*** cutscene/
*** cmdline/
*** debugconsole/
** In Space
*** [[Source ai|ai]]
*** asteroid/
*** autopilot/
*** cmeasure/
*** debris/
*** demo/
*** fireball/
*** gamehelp/
*** gamesequence/
*** gamesnd/
*** hud/
*** iff_defs/
*** jumpnode/
*** lighting/
*** nebula/
*** object/
*** observer/
*** model/
*** network/
*** particle/
*** parse/
*** popup/
*** physics/
*** radar/
*** ship/
*** species_defs/
*** starfield/
*** weapon/
** In Base
*** stats/
*** menuui/
*** mission/
*** missionui/
** Engine
*** fs2open_pxo/
*** freespace2/
*** playerman/
* FRED
** fred2/
** wxfred2/
* Tools
** cfilearchiver/
** cfileextractor/
** cryptstring/
** lab/
** scramble/
** inetfile/
** variables/

=== Category Browser ===
The subdirectories above are also categorised by function. See the Category:Source Code to browse this way.

[[Category:Source Code]]

Talk:Source Code Reference

2007-07-15T10:17:40Z

AcePace: -Starting the page, adding a note.

External libraries Notice:
Acording to the update on 3.6.10, DX support is getting the axe, should we put a notice of this now or when the first release occurs?

Very simple missions

2007-07-15T09:15:42Z

AcePace: /* Hints */ -Random addition.

==Which missions are considered simple?==
A mission being simle is not an official naming for a mission which needs some requirements, it's a general description.

Simple missions normally have only a needed amount of messages, debriefing stages and a limited number of ships and even fewer ending possibilities.

If you are making a campaign and have some missions which play little part in the plot, it is not advised you make them overly complicated. For these missions, you are advised to make them simple. This way, you get more time to work on more important missions.

==Hints==
*Make only a limited number of messages. Do so by making sure none will overlap one another. The more messages you make the higher the possibility that they will overlap. The following messages are a must to every FreeSpace 2 mission:
**Notification about mission failure and success
**Notidication about permission to return to base
**Report about big friendly or hostile ships destroyed or, when the goal is such, disarmed or disabled
**Arrival and departure message for mission critical ships
*A further note on messages is that they should not be overly complex nor should you display plot messages in the middle of a combat engagment.
*Limited number of ships: Do not place so many larger ships than a cruiser or corvette. Placing a destroyer demands that fighters should be launched from it. Destroying the destroyer sooner or later badly affects the number of fighters present in the mission unless there is only one wing to arrive from the destroyer
*Stages: Say that the mission consists of three parts. Each part is triggered by the arrival of a hostile or friendly ship. You have to set the arrival cues of these ships so that they only arrive after a previous stage was completed, often by the destruction of a hostile ship or the departure of a friendly one. This makes it sure that the three stages won't intertwine, saving the FREDder from a lot of time to test each possibility in case the stages overlapped.
*You still need to test the difficulty of the mission and optimize it for game balance. The simplest way to do this is to keep the number of fighters and bombers low.
*Avoid the use of random numeric variables. The fact of randomization is rarely apparent and to make it so requires additional testing time.

==Example mission==
Through this mission example, you will see how a simpler mission looks like in theory. In practice, there is no guarantee it can be done exactly as it is described below.
See [[#Notes about Example|Notes]]

===Mission description===
A Leviathan cruiser ran the GTVA blockade and is to be hunted down. Command sorties a Deimos corvette and some fighters. The corvette arrives six clicks away from the Leviathan, but since the Deimos is faster, they have a chance to catch up with it and destroy it with their beam cannons. In the meanwhile, the NTF attempts to disarm the forward beam cannons to give chance for their cruiser to survive. In the first part, the player must destroy some bombers which come from the front and attempt to take down the beam cannons. The second part is about the battle between the Leviathan and the Deimos. In the third part, the Deimos is to be escorted back to the node until it makes the jump to subspace.

===This mission has===
*Three to eight friendly fighters
*The two warships: A Deimos and a Leviathan
*Enemy bombers and fighters, as many as makes the mission acceptably difficult.
*A jump node, where the Deimos comes from
*Two waypoints
*At least the following events (not mentioning message-only events)
**Destroy Leviathan cruiser directive
**Defend friendly Deimos directive
**Destroy enemy fighters (one event for each attacking wing)
**An event which summerizes the requirements to grant the player authorization to return to base.
**(Chained to the previous event), an event which displays the "Return to base" directive.
**Good-secondary-time, which tells the fighters to use their Trebuchet warheads in case they have some, or the player has the possibility to arm his wingmen with them.
**Events which order warships to use their beams (Retail FreeSpace 2 and ancient FreeSpace Open versions)
*Additional events which are only made to send messages
**Enemy cruiser escaped (Mission failure message)
**Friendly corvette escaped (Mission successful message)
**Friendly corvette destroyed (Enemy destroyed corvette message)
**Additional enemy bombers jumped in (Part 3)
**(Optional) Events which display messages which report the hull/subsystem status on either or both warships
**(Optional) An event which checks how far the friendly corvette is from the jump node and display a message in which the corvette makes report about it ("We are reaching the node in three minutes, pilots.")

===In the mission happens===
*The Leviathan follows a waypoint. When it reaches it, it jumps out and fails the mission
*The Deimos has the order to attack the Leviathan, when it is down, it changes orders and starts moving towards a waypoint, which is placed inside the jump node. When the Deimos is inside the node after the Leviathan is destroyed or departed, it jumps out
*Ten-thirty seconds after start, enemy bombers start jumping in from the front with the orders to attack the front beam cannons. When both cannons are down, the bombers depart and stop arriving. (The Deimos still stands a chance with its rear beam cannons, so the mission is still not lost).
*After the Leviathan has been destroyed or has departed, new wings of hostile targets start jumping in and attack the Deimos. They cease their attacks when the Deimos has been destroyed or departed.

===Misc additions===
*Ediitng the Mission specs editor
**Giving a name to the mission
**Setting All ships beam-freed by Default (In FreeSpace Open, if set, the events which enable warships to use their beams are redundant)
**Support ship settings
***Allowed/disallowed
***Will it repair hull?
**Advised for testing No traitor flag
*Alligning the Team Loadout options
*Warships added to Escort list
*The Attack my target order removed from the issuable orders for the friendly corvette
*Initial orders for all ships
*Advised Some sort of background, preferably with nebulae and planets and multiple, coloured suns

===Notes about Example===
This mission has not been made by the author of the article. It is not guaranteed that mission balance can be kept using the numbers above or the mission in this shape could be too short. It is a main rule in making a balanced mission to not stick to the mission's preliminary description. If the mission is too easy, have a hostile cruiser or corvette jump in to attack the friendly Deimos. If the mission is too hard, give the player reinforcements and/or make the Deimos have cruiser escort.

[[Category:FRED]]

FS Short Hand

2007-07-15T09:06:21Z

AcePace: Added some minor fluff.

'''Ingame Terminology'''
----

Wing - A unit of fightercraft, varying in size from one to six ships. The normal number is four. Ships of a wing are labelled by their wing name and a number (i.e. Alpha 1, Alpha 2, and so on).

Cruiser - Smallest combatant capital craft classification. Cruisers are at least several times the size of a fighter or bomber and posess mainly antifighter weaponry, with one or two (or in the case of the SC Rakshasa, three) anti-capital weapons. The defensive fire of a cruiser is rarely capable of stopping a determined bomber wing, and most are vunerable to even a well-handled lone fighter. Unable to carry fighters, Canonical examples include the Fenris and the Leviathan.

Corvette - Middle ground combatant capital craft, falling between the cruiser and the destroyer in size and capablity. Equipped with between two and four anticapital weapons and considerably more impressive antifighter armament then a cruiser. Corvettes are capable of defending themselves adequately against a small number of enemy fighters or bombers. With the exception of the Moloch, corvettes are unable to carry fighters of their own. Canonically, these are rather rarer in the Freespace-verse then other ship classes, with the Deimos being the corvette with most game time.

Destroyer - Large combatant capital craft, combining the functions of destroying enemy ships and transporting fighters. Destroyers vary wildly in armament and effectiveness against different types of targets. They will have at least one heavy-calibur anticapital weapon and probably several more, plus a number of cruiser-corvette anticapital weapons. Destroyers tend to need fighter cover more then corvettes; some of them actually mount fewer antifighter weapons, and all have much larger amounts of surface area that needs to be defend. Most of the significent capital ships in Freespace canonically have been destroyers, from the GTD Galatea and GTD Bastion in the original Freespace and the GTD Aquitaine and GVD Psamtik in Freespace 2.

Superdestroyer - Bigger, meaner, and tougher then a destroyer, yet too small for the Juggernaut classification; first applied well before the Juggernaut classification came into exsistance. Only the Hades and Lucifer have canonically been given this classification.

Juggernaut - The pinnacle of combatant capital craft. A Juggernaut is capable of making mincemeat out of an enemy fleet singlehanded and is superbly equipped to combat other capital craft. Due to its large surface area its defenses against fightercraft attack are generally somewhat thinly spread, but a Juggernaut's sheer ability to absorb damage means that only another Juggernaut or a mass attack by corvettes and destroyers is capable of destroying one in anything like a timely manner. Only the Colossus and Sathanas have canonically been given this classification.

FreeSpace Lingo

2007-07-04T18:00:07Z

AcePace: Cleaned out the spam.

This section is for various terms, acronyms, short hand and other little things that fans of FreeSpace use on a regular basis. It's for people new to the FreeSpace community, and for the rest of us to realise how odd some of the things we say are.

* [[FS Abbrevations]] 
* [[FS Short Hand]] 
* [[Various Terms]]