FreeSpace Wiki - User contributions [en]

User:Kopachris

2012-12-23T12:18:35Z

Kopachris: I don't like it

POF data structure

2011-04-01T02:41:11Z

Kopachris: /* Chunk specs */

The following information is copied from the Descent Developer's Network [http://web.archive.org/web/20010619182804/descent-freespace.com/ddn/specs/pof/ pof specs page].

==Introduction==
These files are used to hold the ship model data. The data for the ship is basically a BSP tree that doesn't split polygons across the planes (since we're using zbuffering) and the planes are created by halving the largest dimension of each bounding box recursively. Due to the vastness of some of our models, this recursively split structure allows our collision detection and dynamic lighting to do quick out's on the model. For example, to check if a vector interects the model, I check against the bounding box. If it hits, I then check each of the two boxes it is split into. Then I recursively check each subdivided box as long as the vector is still interesecting.

We create the POF file by exporting a 3DS Max file with a special plugin tool to generate a ".P3D" file, which is essentially a 3d studio file only with texture uv's stored for each face vertex rather than for each vertex. We then run the .P3D file through an in-house Win32 program called 'BSPGEN' which creates the POF file. Depending on the model size, BSPGEN takes a few minutes or so.

Each ship is made up of a lot of subobjects where a subobject is a collection of polygons. For instance, each detail level of a hull of a ship is a subobject. A radar dish is a subobject. A piece of debris that the ship explodes into is a subobject. Each subobject can then have children subobjects. To draw the highest detail model of a ship, draw the subobject identified as detail level 0 and draw all it's children.

This document was written by John Slagel from Volition Inc., with revisions and bugfixing from Garry Knudson. FreeSpace 2 additions were made by Dave Baranec (Volition Inc.), Garry Knudson and Francis "Pastel" Avila.

[[POF_Order_FS2|POF block order list for retail FS2 models]]

==Data types==
This uses standard Intel data types.
<pre>
(int) == 4 bytes, signed
(uint) == 4 bytes, unsigned
(short) == 2 bytes, signed
(ushort) == 2 bytes, unsigned
(char) == 1 byte, signed
(ubyte) == 1 byte, unsigned
(float) == 4 bytes, signed
(vector) == 3 floats, 12 bytes total
(string) == an int specifying length of string and char[length] for the string itself
(note: it is NOT null-terminated)
</pre>

==Basic file structure==
The file format is a binary file using standard Intel data types. The header consists of a signature and the file version number:

<pre>
char[4] file_id // must be 'PSPO'
int version // Major*100+Minor
</pre>

Notes:

*PSPO stood for Parallax Software Polygon Object at one time. Conflict, Descent: FreeSpace shipped at POF version 20.14, so version would be equal to 2014 in most POF files (not all). FreeSpace 2 shipped at POF version 21.17, some files are 21.16.

*The rest of the file is a bunch of chunks. Each chunk is:

<pre>char[4] chunk_id // see below for available chunk types
int length // length of the chunk.
</pre>

==Chunk specs==
Here is a breakdown of each of the chunk types:

*'OHDR' (FreeSpace 1) and 'HDR2' (FreeSpace 2) - Object header info

<pre>
#ifdef version2116orhigher
// FreeSpace 2
float max_radius // maximum radius of entire ship
int obj_flags // object flags. Bit 1 = Textures contain tiling
int num_subobjects // number of subobjects
#else
// FreeSpace 1
int num_subobjects // number of subobjects
float max_radius // maximum radius of entire ship
int obj_flags // object flags. Bit 1 = Textures contain tiling
#endif

vector min_bounding // min bounding box point
vector max_bounding // max bounding box point

int num_detaillevels // number of detail levels
for each detail_level, i {
int sobj_detailevels[i] // subobject number for detail level I, 0 being highest.
}

int num_debris // number of debris pieces that model explodes into
for each debris piece, i
int sobj_debris[i] // subobject number for debris piece i

#ifdef version1903orhigher
float mass // see notes below
vector mass_center // center of mass
float[3][3] moment_inertia // moment of inertia
#endif

#ifdef version2014orhigher
int num_cross_sections // number of cross sections (used for exploding ship) (*)
for each cross_section, i {
float depth[i]
float radius[i]
}
#endif

#ifdef version2007orhigher
int num_lights // number of precalculated muzzle flash lights
for each light {
vector location
int light_type // type of light
}
#endif
</pre>

**Notes:

for version<2009, mass is a volume mass
for version>=2009, mass is an area mass
conversion: area_mass=4.65*(vol_mass^2/3); also scale moment_inertia by vol_mass/area_mass
(*) if there is no cross_section data, num_cross_sections is -1 instead of 0, as one would expect.

*'TXTR' - A list of textures used on this ship. The order they appear here is the number that a face uses to reference a particular texture.

<pre>
int num_textures
for each texture,i
string tex_filename[i] // texture filename
</pre>

*'PINF' - Miscellaneous info about the POF file, command line, etc.

Contains a block of NULL-terminated strings. Just read chunk size bytes and stuff it into a string.

*'PATH' - Paths for docking and AI ships to follow

<pre>
int num_paths
for each path, p {
string name[p] // name
string parent[p] // parent's name
int num_verts[p]
for each vert, v {
vector pos[p,v]
float radius[p,v]
int num_turrets[p,v]
for each turret, t {
int sobj_number[p,v,t] // subobject number
}
}
}
</pre>

*'SPCL' - Data for special points

<pre>
int num_special_points
for each special_point, p {
string name[p]
string properties[p]
vector point[p]
float radius[p]
}
</pre>

*'SHLD' - Data for the shield mesh

<pre>
int num_vertices
for each vertex, v {
vector position[v]
}

int num faces
for each face, f {
vector face_normal[f]
int[3] face_vertices // indexed into vertex list
int[3] neighbors // indexed into face list
}
</pre>

*' EYE' - Data for eye points (Where pilot looks in 1st person views). Note the space in front of EYE.

<pre>
int num_eye_positions
for each eye_position, e {
int sobj_number[e] // subobject number this eye is attached to
vector sobj_offset[e] // offset from subobject
vector normal[e]
}
</pre>

*'GPNT' and 'MPNT' - Gun and Missile firing points

<pre>
int num_slots
for each slot, s {
int num_guns[s]
for each gun, g {
vector point[g,s]
vector norm[g,s]
}
}
</pre>

** Notes:

A "slot" is what you see in the loadout screen. Primaries have a max of 2 and secondaries of 3 for player-flyable ships.
"Guns" are the actual number of barrels and hence projectiles you'll get when you press the trigger. There is likely no practical max.

*'TGUN' and 'TMIS' - Turret Gun and Turret Missile firing points.

<pre>
int num_banks

for each bank, b {
int sobj_parent[b] // parent subobject (the subobject with which this turret is associated) (*)
int sobj_par_phys[b] // physical parent subobject (the subobject to which the turret rotates) (*)

vector turret_normal[b]
int num_firing_points[b]
for each firing_point {
vector position[b,f]
}
}
</pre>

** Notes:

For multipart turrets, sobj_parent is the "barrel" of a turret, and the firing points will be in this sobj's axial frame. sobj_par_phys is the "base" of a turret, which the barrel will rotate with.
For single-part turrets, sobj_parent == sobj_parent_phys.

*'DOCK' - Data for docking points

<pre>
int num_docks

for each dock, d {
string properties[d] // see notes below
int num_spline_paths[d]
for each spline_path, p {
int path_number[d,p]
}

int num_points
for each point, d {
vector position
vector normal
}
}
</pre>

** Note: Properties… if $name= found, then this is name. If name is cargo then this is a cargo bay.

*'FUEL' - Data for engine thruster glows

<pre>
int num_thrusters
for each thruster,t {
int num glows[t]

#ifdef version2117orhigher // FreeSpace 2 change
string properties
#endif

for each glow {
vector pos[t,g]
vector norm[t,g] // used to tell if behind glow
float radius[t,g]
}
}
</pre>

*'SOBJ' (FreeSpace 1) and 'OBJ2' (FreeSpace 2) - Data for a subobject. Contains some info and a bunch of vertices and polygons in the form of a BSP tree or Octree depending on how you look at it.

<pre>
int submodel_number // What submodel number this is.

#ifdef version2116orhigher
// FreeSpace 2
float radius // radius of this subobject
int submodel_parent // What submodel is this model's parent. Equal to -1 if none.
vector offset // Offset to from parent object <- Added 09/10/98
#else
// FreeSpace 1
int submodel_parent // What submodel is this model's parent. Equal to -1 if none.
vector offset // Offset to from parent object <- Added 09/10/98
float radius // radius of this subobject
#endif

vector geometric_center
vector bounding_box_min_point
vector bounding_box_max_point

string submodel_name
string properites
int movement_type
int movement_axis

int reserved // must be 0
int bsp_data_size // number of bytes now following
char[bsp_data_size] bsp_data // contains actual polygons, etc.
</pre>
** Note: bsp_data is explained [[bsp_data_structure|here]]

*'INSG' - Squad logo/Insignia data chunk (FreeSpace 2 only)

<pre>
int num_insignias
for each insignia, i {
int detail_level // ship detail level
int num_faces
int num_vertices
for each vertice, j {
vector vertex_position
}

vector offset // offset of the insignia in model coords
for each face, j {
for 0 to 2, k {
int vertex_index // vertex index for this face
float u_texture_coordinate
float v_texture_coordinate
}
}
}
</pre>

*'ACEN' - Auto-Centering info (FreeSpace 2 only)

<pre>
vector point // autocentering point for the entire model
</pre>

** The autocentering point was basically just a little convenient extra data we stuck in models where the pivot point of the model wasn't at the center. Since we rotate ships in the tech room by rotating around the pivot point, it looked dumb when the colossus' rear end was in the middle of the screen and it was spinning on it. So the autocenter point was just a point pretty much near the model we could use to push an extra matrix onto our transform stack and have it show up centered around it. The point itself is in model coordinates.

*'GLOW' - Glowpoint info (FS2_Open only)

<pre>
int num_glowpoints
for each glowpoint, g {
int disp_time // displacement time for blinking (e.g. for Orion runway lights)
int on_time
int off_time
int obj_parent // parent subobject number
int LOD // Should be 0
int type // Should also be 0
string properties // Texture name, no file path or extension, like: "$glow_texture=..."
vector point
vector norm // (0,0,0) is omnidirectional
float radius
}
</pre>

*'SLDC' - Shield mesh collision tree info (FS2_Open only)

<pre>
uint tree_size
for each node, n {
ubyte type // 0 = SPLIT, 1 = LEAF/polylist
uint size
if !type { // SPLIT
vector bound_min
vector bound_max
uint front_offset
uint back_offset
}
else { // LEAF
vector bound_min
vector bound_max
uint num_polygons
for each polygon, p {
uint polygon_addr // indexed into shield mesh face list?
}
}
}
</pre>

** The shield mesh collision tree speeds up collision calculation by adding bounding boxes around each polygon in the shield mesh. It works basically like a [[bsp_data_structure|BSP tree]].

[[Category:File Types]]

POF data structure

2011-03-31T16:50:41Z

Kopachris: /* Chunk specs */ -- added GLOW chunk and SLDC chunk

The following information is copied from the Descent Developer's Network [http://web.archive.org/web/20010619182804/descent-freespace.com/ddn/specs/pof/ pof specs page].

==Introduction==
These files are used to hold the ship model data. The data for the ship is basically a BSP tree that doesn't split polygons across the planes (since we're using zbuffering) and the planes are created by halving the largest dimension of each bounding box recursively. Due to the vastness of some of our models, this recursively split structure allows our collision detection and dynamic lighting to do quick out's on the model. For example, to check if a vector interects the model, I check against the bounding box. If it hits, I then check each of the two boxes it is split into. Then I recursively check each subdivided box as long as the vector is still interesecting.

We create the POF file by exporting a 3DS Max file with a special plugin tool to generate a ".P3D" file, which is essentially a 3d studio file only with texture uv's stored for each face vertex rather than for each vertex. We then run the .P3D file through an in-house Win32 program called 'BSPGEN' which creates the POF file. Depending on the model size, BSPGEN takes a few minutes or so.

Each ship is made up of a lot of subobjects where a subobject is a collection of polygons. For instance, each detail level of a hull of a ship is a subobject. A radar dish is a subobject. A piece of debris that the ship explodes into is a subobject. Each subobject can then have children subobjects. To draw the highest detail model of a ship, draw the subobject identified as detail level 0 and draw all it's children.

This document was written by John Slagel from Volition Inc., with revisions and bugfixing from Garry Knudson. FreeSpace 2 additions were made by Dave Baranec (Volition Inc.), Garry Knudson and Francis "Pastel" Avila.

[[POF_Order_FS2|POF block order list for retail FS2 models]]

==Data types==
This uses standard Intel data types.
<pre>
(int) == 4 bytes, signed
(uint) == 4 bytes, unsigned
(short) == 2 bytes, signed
(ushort) == 2 bytes, unsigned
(char) == 1 byte, signed
(ubyte) == 1 byte, unsigned
(float) == 4 bytes, signed
(vector) == 3 floats, 12 bytes total
(string) == an int specifying length of string and char[length] for the string itself
(note: it is NOT null-terminated)
</pre>

==Basic file structure==
The file format is a binary file using standard Intel data types. The header consists of a signature and the file version number:

<pre>
char[4] file_id // must be 'PSPO'
int version // Major*100+Minor
</pre>

Notes:

*PSPO stood for Parallax Software Polygon Object at one time. Conflict, Descent: FreeSpace shipped at POF version 20.14, so version would be equal to 2014 in most POF files (not all). FreeSpace 2 shipped at POF version 21.17, some files are 21.16.

*The rest of the file is a bunch of chunks. Each chunk is:

<pre>char[4] chunk_id // see below for available chunk types
int length // length of the chunk.
</pre>

==Chunk specs==
Here is a breakdown of each of the chunk types:

*'OHDR' (FreeSpace 1) and 'HDR2' (FreeSpace 2) - Object header info

<pre>
#ifdef version2116orhigher
// FreeSpace 2
float max_radius // maximum radius of entire ship
int obj_flags // object flags. Bit 1 = Textures contain tiling
int num_subobjects // number of subobjects
#else
// FreeSpace 1
int num_subobjects // number of subobjects
float max_radius // maximum radius of entire ship
int obj_flags // object flags. Bit 1 = Textures contain tiling
#endif

vector min_bounding // min bounding box point
vector max_bounding // max bounding box point

int num_detaillevels // number of detail levels
for each detail_level, i {
int sobj_detailevels[i] // subobject number for detail level I, 0 being highest.
}

int num_debris // number of debris pieces that model explodes into
for each debris piece, i
int sobj_debris[i] // subobject number for debris piece i

#ifdef version1903orhigher
float mass // see notes below
vector mass_center // center of mass
float[3][3] moment_inertia // moment of inertia
#endif

#ifdef version2014orhigher
int num_cross_sections // number of cross sections (used for exploding ship) (*)
for each cross_section, i {
float depth[i]
float radius[i]
}
#endif

#ifdef version2007orhigher
int num_lights // number of precalculated muzzle flash lights
for each light {
vector location
int light_type // type of light
}
#endif
</pre>

**Notes:

for version<2009, mass is a volume mass
for version>=2009, mass is an area mass
conversion: area_mass=4.65*(vol_mass^2/3); also scale moment_inertia by vol_mass/area_mass
(*) if there is no cross_section data, num_cross_sections is -1 instead of 0, as one would expect.

*'TXTR' - A list of textures used on this ship. The order they appear here is the number that a face uses to reference a particular texture.

<pre>
int num_textures
for each texture,i
string tex_filename[i] // texture filename
</pre>

*'PINF' - Miscellaneous info about the POF file, command line, etc.

Contains a block of NULL-terminated strings. Just read chunk size bytes and stuff it into a string.

*'PATH' - Paths for docking and AI ships to follow

<pre>
int num_paths
for each path, p {
string name[p] // name
string parent[p] // parent's name
int num_verts[p]
for each vert, v {
vector pos[p,v]
float radius[p,v]
int num_turrets[p,v]
for each turret, t {
int sobj_number[p,v,t] // subobject number
}
}
}
</pre>

*'SPCL' - Data for special points

<pre>
int num_special_points
for each special_point, p {
string name[p]
string properties[p]
vector point[p]
float radius[p]
}
</pre>

*'SHLD' - Data for the shield mesh

<pre>
int num_vertices
for each vertex, v {
vector position[v]
}

int num faces
for each face, f {
vector face_normal[f]
int[3] face_vertices // indexed into vertex list
int[3] neighbors // indexed into face list
}
</pre>

*' EYE' - Data for eye points (Where pilot looks in 1st person views). Note the space in front of EYE.

<pre>
int num_eye_positions
for each eye_position, e {
int sobj_number[e] // subobject number this eye is attached to
vector sobj_offset[e] // offset from subobject
vector normal[e]
}
</pre>

*'GPNT' and 'MPNT' - Gun and Missile firing points

<pre>
int num_slots
for each slot, s {
int num_guns[s]
for each gun, g {
vector point[g,s]
vector norm[g,s]
}
}
</pre>

** Notes:

A "slot" is what you see in the loadout screen. Primaries have a max of 2 and secondaries of 3 for player-flyable ships.
"Guns" are the actual number of barrels and hence projectiles you'll get when you press the trigger. There is likely no practical max.

*'TGUN' and 'TMIS' - Turret Gun and Turret Missile firing points.

<pre>
int num_banks

for each bank, b {
int sobj_parent[b] // parent subobject (the subobject with which this turret is associated) (*)
int sobj_par_phys[b] // physical parent subobject (the subobject to which the turret rotates) (*)

vector turret_normal[b]
int num_firing_points[b]
for each firing_point {
vector position[b,f]
}
}
</pre>

** Notes:

For multipart turrets, sobj_parent is the "barrel" of a turret, and the firing points will be in this sobj's axial frame. sobj_par_phys is the "base" of a turret, which the barrel will rotate with.
For single-part turrets, sobj_parent == sobj_parent_phys.

*'DOCK' - Data for docking points

<pre>
int num_docks

for each dock, d {
string properties[d] // see notes below
int num_spline_paths[d]
for each spline_path, p {
int path_number[d,p]
}

int num_points
for each point, d {
vector position
vector normal
}
}
</pre>

** Note: Properties… if $name= found, then this is name. If name is cargo then this is a cargo bay.

*'FUEL' - Data for engine thruster glows

<pre>
int num_thrusters
for each thruster,t {
int num glows[t]

#ifdef version2117orhigher // FreeSpace 2 change
string properties
#endif

for each glow {
vector pos[t,g]
vector norm[t,g] // used to tell if behind glow
float radius[t,g]
}
}
</pre>

*'SOBJ' (FreeSpace 1) and 'OBJ2' (FreeSpace 2) - Data for a subobject. Contains some info and a bunch of vertices and polygons in the form of a BSP tree or Octree depending on how you look at it.

<pre>
int submodel_number // What submodel number this is.

#ifdef version2116orhigher
// FreeSpace 2
float radius // radius of this subobject
int submodel_parent // What submodel is this model's parent. Equal to -1 if none.
vector offset // Offset to from parent object <- Added 09/10/98
#else
// FreeSpace 1
int submodel_parent // What submodel is this model's parent. Equal to -1 if none.
vector offset // Offset to from parent object <- Added 09/10/98
float radius // radius of this subobject
#endif

vector geometric_center
vector bounding_box_min_point
vector bounding_box_max_point

string submodel_name
string properites
int movement_type
int movement_axis

int reserved // must be 0
int bsp_data_size // number of bytes now following
char[bsp_data_size] bsp_data // contains actual polygons, etc.
</pre>
** Note: bsp_data is explained [[bsp_data_structure|here]]

*'INSG' - Squad logo/Insignia data chunk (FreeSpace 2 only)

<pre>
int num_insignias
for each insignia, i {
int detail_level // ship detail level
int num_faces
int num_vertices
for each vertice, j {
vector vertex_position
}

vector offset // offset of the insignia in model coords
for each face, j {
for 0 to 2, k {
int vertex_index // vertex index for this face
float u_texture_coordinate
float v_texture_coordinate
}
}
}
</pre>

*'ACEN' - Auto-Centering info (FreeSpace 2 only)

<pre>
vector point // autocentering point for the entire model
</pre>

** The autocentering point was basically just a little convenient extra data we stuck in models where the pivot point of the model wasn't at the center. Since we rotate ships in the tech room by rotating around the pivot point, it looked dumb when the colossus' rear end was in the middle of the screen and it was spinning on it. So the autocenter point was just a point pretty much near the model we could use to push an extra matrix onto our transform stack and have it show up centered around it. The point itself is in model coordinates.

*'GLOW' - Glowpoint info (FS2_Open only)

<pre>
int num_glowpoints
for each glowpoint, g {
int disp_time // displacement time for blinking (e.g. for Orion runway lights)
int on_time
int off_time
int obj_parent // parent subobject number
int LOD // Should be 0
int type // Should also be 0
string properties // Texture name, no file path or extension, like: "$glow_texture=..."
vector point
vector norm // (0,0,0) is omnidirectional
float radius
}
</pre>

*'SLDC' - Shield mesh collision tree info (FS2_Open only)

<pre>
uint tree_size
for each node, n {
ubyte type // 0 = SPLIT, 1 = LEAF/polylist
uint size
if !type { // SPLIT
vector bound_min
vector bound_max
uint front_offset
uint back_offset
}
else { // LEAF
vector bound_min
vector bound_max
uint num_polygons
for each polygon, p {
uint polygon_addr // byte offset from beginning of file to each shield polygon in the list?
}
}
}
</pre>

** The shield mesh collision tree speeds up collision calculation by adding bounding boxes around each polygon in the shield mesh. It works basically like a [[bsp_data_structure|BSP tree]].

[[Category:File Types]]

User:Kopachris

2010-03-13T22:40:39Z

Kopachris: /* History */

==History==
Kopachris started his piloting career near the end of the [[14-Year War]] aboard the ''[[GTD Galatea]]''. He was later transferred to the ''[[GTD Bastion]]'' when the ''Galatea'' was taken down by the ''Lucifer'' during the [[Great War]]. On board the ''Bastion'', Kopachris served the [[GTA]] and played an instrumental role in defeating the ''[[SD Lucifer]]'' before it reached Earth.

After the Great War, Kopachris signed up with [[GTI]] and was transferred to the ''[[GTD Krios]]'', playing a major part in defeating the [[Hades Rebellion]]. A long period of inactivity followed, until the [[NTF]] activated the [[Knossos]] portal in [[Gamma Draconis]]. Kopachris played several roles in the [[Second Shivan Incursion]], including several undercover missions, escort mission, and tactical strike missions. Kopachris was one of the few pilots stationed on the ''[[GTD Aquitaine]]'' to see both the unveiling and the destruction of the ''[[GTVA Colossus]]''.

Kopachris died at the end of the Second Shivan Incursion. Eyewitnesses say he didn't make it to the [[Vega]] jump node before [[Capella]] went supernova.

==Projects==
Kopachris is currently planning several major projects. First on the agenda is a collection of FreeSpace tools for Linux. This includes a VP Editor, a launcher, and a POF importer for Blender. These tools are being designed to make modding a simpler, more straightforward process. All of these tools are initially going to be programmed in Python, but may be ported to C/C++ at a later time.

After creating these mod tools, Kopachris plans to use them in the creation of a grand mod consisting of three feature-length campaigns, with a collection of new ships, weapons, command briefing animations, and cutscenes. Kopachris will document the entire process of creating these campaigns in order to create an all-in-one guide to FreeSpace modding.

===Linux Mod Tools===
A VP Editor, called "Linux VP Manager", or LVPM, is currently in the detail planning stage and the beginning of the programming stage. A simple command-line Python script at first, version 0.1 will support extracting single files, a list of files, or an entire directory from a [[*.VP|VP archive]], as well as creating a VP archive from a directory and listing the entire contents of a VP. Later upgrades will include the ability add files to an archive, remove files from an archive, and eventually a GTK+ interface.

Following LVPM, Kopachris intents to create a simple launcher to run on Linux that will help integrate FS2_Open with Linux. The launcher will likely be written in Python with a GTK+ libglade interface and will do nothing more than write arguments to the data/cmdline_fso.cfg file. It will also have an option to install a launcher in the GNOME menu.

The final project for the Linux Mod Tool suite will be an import/export script that will allow [[Blender]] to use [[Model files|POF]] files. This tool won't be limited to Linux, however, and should make modding simpler on any platform. As of right now, the plan is to use empty meshes in Blender to represent point and normal data (such as weapon fire-points and the eye-point) and untextured cubes for subsystem data and other parts that require volume. The exporter will include a tool to set data and options before exporting.

===Three Campaigns and Grand Tutorial===
The first campaign idea takes place immediately after Capella goes supernova and is from the point of view of the squadron leader of the [[70th Blue Lions]]. The player and the rest of the Blue Lions are transferred to the ''[[FreeSpace_2_Terran_Ship_Database#GTD_Messana|GTD Messana]]'' to help refugees fend off pirates and the dregs of the NTF while the ''Aquitaine'' is sent to either integrate with a new fleet or set up a new HQ for the [[3rd Terran Fleet|3rd Fleet]] (the decision hasn't been made yet). Though the bulk of the plot hasn't been decided upon yet, Kopachris has revealed that the campaign will include a return to Capella (now a nebula).

The second campaign goes through the same events and timeline as the first, but from the point of view of the [[pirates]]. A few missions will remain mostly the same, and the plot of each campaign will mingle, but each is meant to tell its own story of what happens after Capella. As opposed to how most user-made campaigns treat pirates, both of Kopachris's campaigns intend to make pirates take on a more clever, sinister role in mission design. Rather than being endless waves of cannon fodder, Kopachris's pirates will have a goal and will use whatever technology they have to reach that goal.

The final cutscene of each of those two campaigns will be the same—15 years later, and contact with Sol is restored. This cutscene will be intended to serve as a preview for the last campaign, which will describe what has been going on with Earth these past years and how the Earth-bound humans and the [[Lost Generation]] interact when they finally meet again.

And of course, the construction of these campaigns will be fully documented in order to create a tutorial of modding FreeSpace. The tutorial will cover such topics as plot design, modeling, texturing, animation, FREDding, music design, and voice recording. Along with documentation, the tutorial project will also include a large reference manual from both canon and non-canon (but highly appraised) sources and all the development files (screenplays, models, textures, sheet music, etc.).

User:Kopachris

2010-03-13T22:40:09Z

Kopachris:

==History==
Kopachris started his piloting career near the end of the [[14-Year War]] aboard the ''[[GTD Galatea]]''. He was later transferred to the ''[[GTD Bastion]]'' when the ''Galatea'' was taken down by the ''Lucifer'' during the [[Great War]]. On board the ''Bastion'', Kopachris served the [[GTA]] and played an instrumental role in defeating the ''[[SD Lucifer]]'' before it reached Earth.

After the Great War, Kopachris signed up with [[GTI]] and was transferred to the ''[[GTD Krios]]'', playing a major part in defeating the [[Hades Rebellion]]. A long period of nothingness followed, until the [[NTF]] activated the [[Knossos]] portal in [[Gamma Draconis]]. Kopachris played several roles in the [[Second Shivan Incursion]], including several undercover missions, escort mission, and tactical strike missions. Kopachris was one of the few pilots stationed on the ''[[GTD Aquitaine]]'' to see both the unveiling and the destruction of the ''[[GTVA Colossus]]''.

Kopachris died at the end of the Second Shivan Incursion. Eyewitnesses say he didn't make it to the [[Vega]] jump node before [[Capella]] went supernova.

==Projects==
Kopachris is currently planning several major projects. First on the agenda is a collection of FreeSpace tools for Linux. This includes a VP Editor, a launcher, and a POF importer for Blender. These tools are being designed to make modding a simpler, more straightforward process. All of these tools are initially going to be programmed in Python, but may be ported to C/C++ at a later time.

After creating these mod tools, Kopachris plans to use them in the creation of a grand mod consisting of three feature-length campaigns, with a collection of new ships, weapons, command briefing animations, and cutscenes. Kopachris will document the entire process of creating these campaigns in order to create an all-in-one guide to FreeSpace modding.

===Linux Mod Tools===
A VP Editor, called "Linux VP Manager", or LVPM, is currently in the detail planning stage and the beginning of the programming stage. A simple command-line Python script at first, version 0.1 will support extracting single files, a list of files, or an entire directory from a [[*.VP|VP archive]], as well as creating a VP archive from a directory and listing the entire contents of a VP. Later upgrades will include the ability add files to an archive, remove files from an archive, and eventually a GTK+ interface.

Following LVPM, Kopachris intents to create a simple launcher to run on Linux that will help integrate FS2_Open with Linux. The launcher will likely be written in Python with a GTK+ libglade interface and will do nothing more than write arguments to the data/cmdline_fso.cfg file. It will also have an option to install a launcher in the GNOME menu.

The final project for the Linux Mod Tool suite will be an import/export script that will allow [[Blender]] to use [[Model files|POF]] files. This tool won't be limited to Linux, however, and should make modding simpler on any platform. As of right now, the plan is to use empty meshes in Blender to represent point and normal data (such as weapon fire-points and the eye-point) and untextured cubes for subsystem data and other parts that require volume. The exporter will include a tool to set data and options before exporting.

===Three Campaigns and Grand Tutorial===
The first campaign idea takes place immediately after Capella goes supernova and is from the point of view of the squadron leader of the [[70th Blue Lions]]. The player and the rest of the Blue Lions are transferred to the ''[[FreeSpace_2_Terran_Ship_Database#GTD_Messana|GTD Messana]]'' to help refugees fend off pirates and the dregs of the NTF while the ''Aquitaine'' is sent to either integrate with a new fleet or set up a new HQ for the [[3rd Terran Fleet|3rd Fleet]] (the decision hasn't been made yet). Though the bulk of the plot hasn't been decided upon yet, Kopachris has revealed that the campaign will include a return to Capella (now a nebula).

The second campaign goes through the same events and timeline as the first, but from the point of view of the [[pirates]]. A few missions will remain mostly the same, and the plot of each campaign will mingle, but each is meant to tell its own story of what happens after Capella. As opposed to how most user-made campaigns treat pirates, both of Kopachris's campaigns intend to make pirates take on a more clever, sinister role in mission design. Rather than being endless waves of cannon fodder, Kopachris's pirates will have a goal and will use whatever technology they have to reach that goal.

The final cutscene of each of those two campaigns will be the same—15 years later, and contact with Sol is restored. This cutscene will be intended to serve as a preview for the last campaign, which will describe what has been going on with Earth these past years and how the Earth-bound humans and the [[Lost Generation]] interact when they finally meet again.

And of course, the construction of these campaigns will be fully documented in order to create a tutorial of modding FreeSpace. The tutorial will cover such topics as plot design, modeling, texturing, animation, FREDding, music design, and voice recording. Along with documentation, the tutorial project will also include a large reference manual from both canon and non-canon (but highly appraised) sources and all the development files (screenplays, models, textures, sheet music, etc.).

User:Kopachris

2009-04-17T04:17:13Z

Kopachris: New page: ==Preferred ships== ===Type:=== *Heavy assault fighter *Intercept fighter ===FS1:=== *Hercules *Valkyrie ===FS2:=== *Terran Mara *Herc II *Erinyes *[[...

==Preferred ships==
===Type:===
*Heavy assault fighter
*Intercept fighter
===FS1:===
*[[Hercules]]
*[[Valkyrie]]
===FS2:===
*[[SF Mara (Terrans)|Terran Mara]]
*[[Herc II]]
*[[Erinyes]]
*[[Perseus]]
*[[Tauret]]
==Preferred weapons==
===FS1:===
*[[Banshee]]
*[[Hornet]]
===Early FS2:===
*[[Prometheus R]]
*[[Subach HL-7]]
*[[Hornet]]
===Mid FS2:===
*[[Prometheus S]]
*[[Tornado]]
===Late FS2:===
*[[Maxim]]
*[[GTW Circe|Circe]]
*[[Tornado]]

SF Mara

2009-04-17T04:14:38Z

Kopachris: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|image=[[Image:mara320x240.jpg]]|caption=The SF Mara}}

The extensively used '''SF ''Mara''''' was one of the [[Shivans|Shivan]] fighters used during their [[Second Shivan Incursion|second invasion]]. The Mara was fast, maneuverable, tough, and relatively small. The craft also had a superior secondary weapon capability that could even compete with that of a bomber-type. Like all Shivan fighters, the Mara was extremely well-shielded and its armoring was somehow superior to that of a typical Shivan fighter. Although it was still weaker than a Terran fighter's, its heavy shielding and swiftness made the Mara a formidable opponent in a dogfight. However, despite its specifications as a fighter-type, Maras were still impractical against larger vessels, thus they were often tasked with bomber escort.

It is the Mara class that was first designated of all Second Incursion-era Shivan fighters after a group of Mara fighters were detected emerging from the [[Knossos]] subspace portal in [[Gamma Draconis]]. The fighters, with the help of a [[SC Rakshasa|''Rakshasa''-class cruiser]], easily took down the patrolling GTVA force.

Some time during the nebula campaign, [[Special Operations Command|SOC]] managed to capture a wing of these fighters, and their engineers retrofitted them for [[Terran]] use. Later, they were used in another SOC operation that discovered the actual size of the Shivan fleet, as well as a third Knossos device.

==Description:==
===FS2 Demo Tech Room Description===
The Mara seems to be a Shivan heavy attack fighter. It is not as maneuverable as other Shivan fighters, but it packs quite a punch, and it is very resistant to our weaponry. Most often they have been used in attacking our supply convoys and transports.
Treat the Mara as a Class C threat.

===FS2 Tech Room Description===
The SF Mara class of Shivan fighters was first encountered by the GTC Vigilant while patrolling the Gamma Draconis jump node in the Capella system. All other information concerning the Mara is classified level Psi.

===Developer Notes===
None

===Name origin===
Mara has many meanings and connotations. Most likely, the fighter class is named after the Hindu goddess of death. In Buddhism, Mara is not a goddess but a male demon.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Space Superiority (?)
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 70.0 - 78.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 120.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 200
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 620
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 17.8 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''FreeSpace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[Shivan Mega Laser]]
|- align="center"
| 2nd
| 2
| [[Shivan Heavy Laser]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''FreeSpace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 80
| [[GTM Trebuchet|Trebuchet]]
|- align="center"
| 2nd
| 80
| [[GTM Hornet|Hornet]]
|}
===Veteran Comments===
{{comment|It would be a disservice to the Mara to say it's just a Herc II with the speed and maneuverability of the Perseus. But that's the Mara in a nutshell.

The one disadvantage of the Mara is the fairly large target profile it presents to the enemy, but its combination of maneouverability, firepower and durability easily makes up for this.

The "Terran Mara" you use in [[Into the Lion's Den]] is slightly superior to the Shivan version.

The above comment is at best an understatement.

The Mara is a highly-capable craft. It can outmaneuver most heavier GTVA fighters and bombers, has enough speed at its disposal to be competitive, and finally has enough weaponry to be a significant threat. All this, even in the hands of an AI pilot. If the Mara were being piloted by players it would be a terror. And the uprated [[SF Mara (Terrans)]] is a truly a nightmare, but fortunately one for the other guy.

Maras are a true nightmare on higher difficulty levels. They always appear in swarms, and instantly start trying to fill your ship with volley after volley of Hornets.

What was said above about outmaneuvering heavier fighters and bombers is only true on higher difficulty levels. Even then, as long as you know how to use a heavy fighter properly, you'll be fine.}}

[[Category:Ship]]

GTW Maxim

2009-04-17T04:04:56Z

Kopachris: /* Veteran Comments */

The '''GTW-66 Maxim Cannon''' is a brand new design; a long-range, high velocity particle accelerator cannon that functions more or less like a mass driver. The weapon has the best range of any primary gun, at 3.5km, and also inflicts the highest degree of hull damage.

A tactically invaluable weapon since it out-ranges any existing anti-fighter defenses, the Maxim's primary disadvantages are first that it draws an amazing amount of power to operate; and second that it causes a substantial amount of recoil per shot, strong enough to affect the pilot's visual aim.

{{FS12_Weapons}}
{{shipimage|image=[[Image:Maxim.gif]]|caption=The GTW-66 Maxim Cannon}}

==Tech Room Data==
Reconstruction efforts after the Great War inspired advancements in metallurgy and efficient conventional explosives. The two are elegantly combined in the GTW-66 Maxim. The Maxim is by definition an energy weapon, though it behaves like a high-velocity mass-driver cannon, accelerating uranium slugs along its smoothbore barrel. The Maxim has a difficult time penetrating energy-based shields, but it has a devastating effect on hull plating and subsystem armor.

==Performance==
===Statistics - Maxim===
{{Primary|3600|6.67|1800|26|Full|26|Poor|4|Good|20}}

===Statistics - Maxim D===
{{Primary|2700|6.67|1800|20|Good|16|Poor|4|Full|20}}

==Notes==
*The weapon has high recoil values [[Weapons.tbl#Weapon Flags|(Shudder)]].

===Veteran Comments===
{{Comment|The Maxim is a rapid-fire, extra-long-range (three kilometers!) anti-hull cannon. It is clearly designed for the purpose of making capital ships' lives miserable, allowing the player to destroy subsystems and even whole smaller capships with ease from beyond the range of return fire. It does produce some "shake" effect as it fires, degrading its accuracy somewhat. Because of its high rate of fire, despite its low shield damage it is also still mildly effective against shielded targets. Be aware though that this weapon is perhaps the biggest energy hog of them all, and will run you dry with mere seconds of sustained fire.

However, the Maxim is still considered by some to be "unfair" and "un-balanced" because of its ability to destroy turrets and destroy cruisers beyond the range of their [[Standard Flak|Flak]] guns. For example, with this gun a [[GTF Ulysses|Ulysses]] can take out all of the subsystems of a [[GTCv Deimos|Deimos]]. The argument is that in "real life" a warship wouldn't just sit on its behind and take the damage, instead jumping out or sending interceptors.

Despite its range and high rate of fire, the Maxim is a mediocre bomb interception weapon. It has high recoil and uses a massive amount of power. The best bomb interception weapon is the Morningstar, with this or the Mekhu in second place.

The Maxim is a very convenient weapon if you know when and where to use them. By default, the Maxim is a good weapon to take down subsystems—especially larger turrets—and weaker cruisers from a safe distance. Remember it devours a lot of energy, so I suggest you keep your recharge rate maximum while firing, unless you are in a hurry to approach your target. The "shake" effect does not affect your accuracy if you do not steer your ship; however, it will be distracting during a dogfight. If you are expecting a hard dogfight, either take "Dogfight Primary" + Trebuchets or Maxim + lots of "Dogfight Missiles."

''This weapon is of little use against Shivan fighters, as they have strong shields and hulls so weak, that you can destroy them witch few hits from anything. Larger ships, or even heavy bombers, are different thing, however.''

If you're expecting to see some warships jump into your operations area, and you have access to this weapon, it's definitely worth a look. Using a Maxim cannon, you may be able to disable at least some of a warship's armaments before it gets anywhere close.

The classic combination of the Circe and the Maxim are excellent against Shivan fighters and bombers '''when fired in short bursts'''. They both use up so much energy that it's hard to keep a steady stream of fire. The long range and the high hull damage of the Maxim is excellent against anything that's slow and unshielded.}}

==Name Origin==
The Maxim gun was one of the first machine guns, operated around the turn of the 19th and 20th centuries. The gun was developed by an American inventor, Sir Hiram Maxim in 1884.

[[Category:Weapon]]

GTW Maxim

2009-04-17T04:04:15Z

Kopachris: /* Veteran Comments */

The '''GTW-66 Maxim Cannon''' is a brand new design; a long-range, high velocity particle accelerator cannon that functions more or less like a mass driver. The weapon has the best range of any primary gun, at 3.5km, and also inflicts the highest degree of hull damage.

A tactically invaluable weapon since it out-ranges any existing anti-fighter defenses, the Maxim's primary disadvantages are first that it draws an amazing amount of power to operate; and second that it causes a substantial amount of recoil per shot, strong enough to affect the pilot's visual aim.

{{FS12_Weapons}}
{{shipimage|image=[[Image:Maxim.gif]]|caption=The GTW-66 Maxim Cannon}}

==Tech Room Data==
Reconstruction efforts after the Great War inspired advancements in metallurgy and efficient conventional explosives. The two are elegantly combined in the GTW-66 Maxim. The Maxim is by definition an energy weapon, though it behaves like a high-velocity mass-driver cannon, accelerating uranium slugs along its smoothbore barrel. The Maxim has a difficult time penetrating energy-based shields, but it has a devastating effect on hull plating and subsystem armor.

==Performance==
===Statistics - Maxim===
{{Primary|3600|6.67|1800|26|Full|26|Poor|4|Good|20}}

===Statistics - Maxim D===
{{Primary|2700|6.67|1800|20|Good|16|Poor|4|Full|20}}

==Notes==
*The weapon has high recoil values [[Weapons.tbl#Weapon Flags|(Shudder)]].

===Veteran Comments===
{{Comment|The Maxim is a rapid-fire, extra-long-range (three kilometers!) anti-hull cannon. It is clearly designed for the purpose of making capital ships' lives miserable, allowing the player to destroy subsystems and even whole smaller capships with ease from beyond the range of return fire. It does produce some "shake" effect as it fires, degrading its accuracy somewhat. Because of its high rate of fire, despite its low shield damage it is also still mildly effective against shielded targets. Be aware though that this weapon is perhaps the biggest energy hog of them all, and will run you dry with mere seconds of sustained fire.

However, the Maxim is still considered by some to be "unfair" and "un-balanced" because of its ability to destroy turrets and destroy cruisers beyond the range of their [[Standard Flak|Flak]] guns. For example, with this gun a [[GTF Ulysses|Ulysses]] can take out all of the subsystems of a [[GTCv Deimos|Deimos]]. The argument is that in "real life" a warship wouldn't just sit on its behind and take the damage, instead jumping out or sending interceptors.

Despite its range and high rate of fire, the Maxim is a mediocre bomb interception weapon. It has high recoil and uses a massive amount of power. The best bomb interception weapon is the Morningstar, with this or the Mekhu in second place.

The Maxim is a very convenient weapon if you know when and where to use them. By default, the Maxim is a good weapon to take down subsystems—especially larger turrets—and weaker cruisers from a safe distance. Remember it devours a lot of energy, so I suggest you keep your recharge rate maximum while firing, unless you are in a hurry to approach your target. The "shake" effect does not affect your accuracy if you do not steer your ship; however, it will be distracting during a dogfight. If you are expecting a hard dogfight, either take "Dogfight Primary" + Trebuchets or Maxim + lots of "Dogfight Missiles."

''This weapon is of little use against Shivan fighters, as they have strong shields and hulls so weak, that you can destroy them witch few hits from anything. Larger ships, or even heavy bombers, are different thing, however.''

If you're expecting to see some warships jump into your operations area, and you have access to this weapon, it's definitely worth a look. Using a Maxim cannon, you may be able to disable at least some of a warship's armaments before it gets anywhere close.

The classic combination of the Circe and the Maxim are excellent against Shivan fighters and bombers ''when fired in short bursts''. They both use up so much energy that it's hard to keep a steady stream of fire. The long range and the high hull damage of the Maxim is excellent against anything that's slow and unshielded.}}

==Name Origin==
The Maxim gun was one of the first machine guns, operated around the turn of the 19th and 20th centuries. The gun was developed by an American inventor, Sir Hiram Maxim in 1884.

[[Category:Weapon]]

GTW UD-8 Kayser

2009-04-17T03:58:34Z

Kopachris: /* Veteran Comments */

The '''GTW UD-8 Kayser''' is an advanced primary weapon that is now in its late OpEval period. It has high marks for both shield and armor penetration, beyond even the formidable [[GTW Prometheus S]]. Its shots move fast, reach a decent range, and pack a heck of a punch. That's the good news. The bad news is that, as expected for a prototype weapon, its compatibility with existing fighters and bombers is poor. Few craft can mount this cannon. The weapon's energy requirements are also very high. Still, when you see one of these on the battlefield, you should immediately be very cautious. It's a powerful device, given only to veteran and elite squadrons. Special Operations Command, especially, seems to have priority selection.

{{FS12_Weapons}}
{{shipimage|image=[[Image:Kayser.gif]]|caption=The GTW UD-8 Kayser}}

==Tech Room Data==
The GTW UD-8 Kayser is the result of an intensive study of Shivan weapon technology. The Kayser emits focused waves of subatomic particles that bombard its target. Impact causes the wave function of the particles to collapse and emit extremely intense, zero-point energy microbursts. Standard policy dictates that weapons of this magnitude be mounted only on bombers, but it has become common practice for field technicians to mount them on fighters.

==Performance==
===Statistics - UD-8 Kayser===
{{Primary|975|4|650|28|Full|28|Very Good|25.2|Poor|9.8}}

===Statistics - UD-D Kayser===
{{Primary|975|3.33|650|16.8|Full|16.8|Full|16.8|Average|9.8}}

==Notes==

===Veteran Comments===
{{Comment|If there is a gun that you want to have when dogfighting, this is that gun. Combining rapid fire with high damage, a well-aimed volley of Kayser fire can convert most fightercraft to small amounts of debris with little difficulty. The downside is high energy requirements, which somewhat reduces the advantage of the rapid firing rate. Make no mistake: if somebody comes at you spraying Kayser pulses, he's not going to do it for long, but you could well be dead before he stops.

To be perfectly honest, I really prefer the [[GTW Subach HL-7|Subach]] for its efficiency and fire rate, and the [[GTW Prometheus S|Prometheus S]] for its power. I take both of them instead of this.

Go all out when you're 90% sure of hitting your target. Otherwise fire in short bursts. With this, you have to make every shot count.

Note on the previous comment, especially in anything that mounts more than 4 guns.

When I first got to use the Kayser, I stopped using other primary weapons if I had the chance. This gun delivers such a punch that it can actually deplete weak shields and '''still''' have enough power to damage the hull. In fact, for some of the fighters with little hull plating, even a direct hit from four Kayser projectiles can knock their shields from full to null. The downside of the Kayser is that it uses up a lot of energy, even more than the Prometheus. This is something that should be taken into account unless you fly an [[SF Mara (Terrans)|SOC-retrofitted SF Mara]].

The Kayser is a good anti-fighter and anti-bomber primary. However, it devours too much energy to be of much use against freighters and cruisers. In such cases, it is advisable to take some Trebuchets or forget the Kayser and take a Maxim or dual Prometheus S cannons. Like most high-consumption anti-bomber cannons, sacrifice some speed for a higher primary recharge rate. With Kaysers, you may run out of energy real fast and at the worst time. Most typically, you will use the Kayser in the main campaign with a GTF ''Erinyes'', the eight guns of which will eat all your primary energy in a few seconds. This might be discouraging, but on a 4-gun Perseus, Kaysers serve well, both as anti-fighter and anti-bomber.

The Kayser is an excellent dogfight weapon if you have a quick, moderately-armored ship. You'll need the extra speed and padding so you can divert some energy to your primaries. As said before, fire in short bursts unless you're sure you'll hit your target (such as against something that's not moving). If you need your speed and all the shielding you can, you should go with something else, such as dual Prom-S.}}

[[Category:Weapon]]

Subspace

2009-04-17T03:51:53Z

Kopachris:

==FreeSpace 2 Tech Room Description==

In simple terms, '''subspace''' is an n-dimensional tunnel between one point in the universe and another. A vessel can travel through this tunnel in a matter of minutes, making a journey that might otherwise take decades or even centuries at [[light speed]].

A jump drive causes a ship to vibrate in multiple dimensions until its modulations are in perfect synchronization with the subspace continuum. A vortex opens, creating an aperture from an infinitesimally small point in the cosmos, enabling the vessel to cross the subspace threshold.

Two types of jumps are possible.

First, an intrasystem jump can occur between two points in a star system. Most small, space-faring vessels are equipped with motivators capable of these short jumps. The presence of an intense gravitational field is required, prohibiting travel beyond the boundaries of a star system.

Second, ships can jump from system to system via nodes. Until [[The Great War]], only larger ships could generate sufficient power to use jump nodes. The development of jump drives for fighters and bombers in 2335 enabled the [[Galactic Terran Alliance]] to destroy the [[SD Lucifer|SD ''Lucifer'']] in subspace. Producing these small jump drives is prohibitively expensive, so they are restricted to missions that require pilots to travel between systems. The Head-Up Display indicates the location of jump nodes with a green sphere.

The vast majority of subspace nodes are extremely unstable, forming and dissipating in nanoseconds. Other nodes have a longer lifespan, existing for centuries or millennia before collapsing. The jump nodes sanctioned by the [[Galactic Terran-Vasudan Alliance]] for interstellar travel are expected to remain stable for many years.

==Wiki Comments==
Intersystem jumps (through subspace) represent a very quick method of travel; journeys that would take years—or even centuries—at light speed are only a matter of hours or days when travelling via subspace, although it's not clear exactly how long they take. In FreeSpace 1 (the fail debrief for [[The Great Hunt]]), it is noted that the ''Lucifer'' will take 48 hours to reach Earth from Delta Serpentis. In the last two FS1 missions, the player is given about 10 minutes to reach the Sol jump node after the ''Lucifer'' has jumped, and another 10 minutes to destroy the ''Lucifer'' in subspace; it can be estimated that the ''Lucifer'' takes 20-30 minutes to reach Earth from Delta Serpentis, or roughly one lightyear per minute. At the same time, the [[FreeSpace Reference Bible]] describes intersystem jumps as being near instantaneous. Like most other questions about canon, this one has contradictory answers.

Note that the FreeSpace 2 techroom description prohibits craft from making intrasystem jumps without the prescence of an intense gravitational field, but does not say that intersystem jump nodes only form in the presence of gravity. Therefore, one could technically say that there are many jump nodes that lead to empty space while only the ones that lead to actual systems are used by the GTVA. Common sense and gameplay seem to imply otherwise, but this possibility has never been explicitly ruled out.

[[Category:FreeSpace Universe]]

Talk:Subspace

2009-04-16T04:33:47Z

Kopachris: New page: Can someone note down what the stuff in the FS2 Tech DB ani says? The ani looks to be completely different (more realistic) than what the Tech DB text says. ~~~~

Can someone note down what the stuff in the FS2 Tech DB ani says? The ani looks to be completely different (more realistic) than what the Tech DB text says. [[User:Kopachris|Kopachris]] 04:33, 16 April 2009 (UTC)

Talk:Sample Lighting Settings

2009-04-16T04:30:05Z

Kopachris:

====Usability====
Galemp's one was pretty simple in the way that I just copied the line onto my Custom Flags field, but I assume TopAce's thing is better. Could we include a code box by any chance (So people can just grab it)? -- [[User:Snail|Snail]] 12:39, 7 March 2009 (UTC)
*Why I made it the style of a list was because GalEmp probably intended to make it list-style. He just does not know that you cannot make lists in a wiki by one enter at the end of each line. [EDIT]What about the current version? - [[User:TopAce|TopAce]] 12:57, 7 March 2009 (UTC)
**Mmmm, good. -- [[User:Snail|Snail]] 18:38, 7 March 2009 (UTC)
 
If you look in CKid's picture, the ship being destroyed in the background is the same ship that's in the foreground of Herra's picture. Just thought that was kind of funny. [[User:Kopachris|Kopachris]] 04:30, 16 April 2009 (UTC)

Weapons.tbl

2008-04-01T01:16:12Z

Kopachris: /* "inherit parent target" */

Revision information.. 
::'''3.6.x branch:''' 2.180.2.24
::'''3.7 branch:''' 4536

==Special Case Weapons==
===Beam Cannons===
*'''REQUIRES: "beam" flag'''
*'''REQUIRES: [[weapons.tbl#$BeamInfo:|$BeamInfo:]]'''
===Flak Guns===
*'''REQUIRE: "flak" and "particle spew" flags'''
*Must have inner and outer radius defined to have any effect.
*Does not use any model or weapon effect though model must be defined, usually Hornet.pof. Instead it uses [[Weapons.tbl#$Pspew:|particle spew]]. Trails can also be added.

==Weapons Table==

===General Format===
*The weapons table consist of several sections
*All sections beginning with <nowiki>#</nowiki> need <nowiki>#</nowiki>'''End''' before the next section.
**<nowiki>#</nowiki>'''Primary Weapons'''
***Defines all '''standard primaries weapons''' as well as '''beam cannons''' and '''flak cannons'''.
**<nowiki>#</nowiki>'''Secondary Weapons'''
***Defines all '''secondary weapons'''.
**<nowiki>#</nowiki>'''Beam Weapons'''
***I haven't got any ideas for this one.
**<nowiki>#</nowiki>'''[[Weapons.tbl#Countermeasures|Countermeasures]]'''
***Defines the used countermeasure.
**'''$Player Weapon Precedence'''
***Player Weapon Precedence is used in weapon selection when a default specified by the mission designer is not available to the player. The next weapon on the list is used in its place (assuming that weapon is allowed for the player).

===Core Table===

====$Name:====
*This is the name of the weapon. If it's going to be used by the player, keep it under 12 characters so it doesn't spill over the HUD box. If the weapon has an @ symbol in front of it, it means it's allowed in the demo. It doesn't really do anything in the retail version.
*Syntax: '''''String'''''

====$Subtype:====
{{Table36| }}

====+Title:====
*This is the title of the weapon in the Weapons loadout screen. Only needed for player allowed weapons. Title may be anything. Numerical value is a reference to translations in [[Tstrings.tbl]]
*Syntax: XSTR('''''"String"''''', -1)

====+Description:====
*This is the description you see in the weapons loadout screen. Again, these aren't based on any hard numbers, just approximations. Only needed for player allowed weapons. Numerical value is a reference to translations in [[Tstrings.tbl]]

=====Example=====

<pre>
XSTR(
"''Standard Issue
''Level 3 Hull Damage
''Level 2 Shield Damage''", -1)
$end_multi_text
</pre>

====+Tech Title:====
*Title of the weapon in the Tech room. Only needed for player allowed weapons.
*Syntax: XSTR('''''"String"''''', -1)

====+Tech Anim:====
*Animation used for the weapon in the Tech room. Only needed for player allowed weapons.
*Syntax: '''''String''''', animation filename
**Example: ''Tech_Subach_HL-7''

====+Tech Description:====
*Descriptive text you see in the tech room. Only needed for player allowed weapons. Numerical value is a reference to translations in [[Tstrings.tbl]]

=====Example=====

<pre>
XSTR(
"''The Subach-Innes HL-7...''", 3245)
$end_multi_text
</pre>

====$Tech Model:====
{{Table36|
*Defines model used in wing loadout screen and in Tech Room for the weapon.
*Syntax: '''''String.pof''''', model filename}}

====$HUD Image:====
{{Table36|
*Defines the picture used to represent the weapon in HUD loadout list
*Syntax: '''''String''''', filename}}

====$Model File:====
*Filename of the model file (.pof) at data/models folder. Additional fields beginning from '''''@Laser Bitmap:''''' and ending to '''''@Laser Tail Radius:''''' are not needed if a model has been defined for the weapon.
*Standard primaries and beam cannons do not use specific models so for those the name is 'none'.
*Flak weapons and secondaries use models, though the exact model is not important with the flak weapons.
*Syntax: '''''String.pof''''' or ''none'', model filename
**Example: ''none''

====$POF target LOD:====
{{Table36|
*Defines the LOD (Level-Of-Detail) of the model used in HUD targetting view
*Syntax: '''''Integer'''''}}

====$External Model File:====
{{Table36|
*Defines the models shown on the gunpoint, used with Bobb's external-visible-weapon code.
*Syntax: '''''String.pof''''', model filename}}

====$Submodel Rotation Speed:====
{{Table36|
*Defines the rotation speed of the external weapon model
*Syntax: '''''Float'''''}}

====$Submodel Rotation Acceleration:====
{{Table36|
*Defines the rotation acceleration of the external weapon model
*Syntax: '''''Float'''''}}

====@Laser Bitmap:====
**The graphic file to be used as the weapon effect if no model is defined.
**Syntax: '''''String''''', filename

====@Laser Glow:====
**The graphic file that determines the glow of the weapon effect if no model is defined
**Syntax: '''''String''''', filename

====@Laser Color:====
**The color of the weapon effect when you fire it.
**Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
***Example: ''250, 0, 0''

====@Laser Color2:====
**The color of the weapon effect at its maximum range.
**Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
***Example: ''0, 0, 250''

====@Laser Length:====
**Length of the weapon effect.
**Syntax: '''''Float''''', meters

====@Laser Head Radius:====
**Width of the head of the weapon effect.
**Syntax: '''''Float''''', meters

====@Laser Tail Radius:====
**Width of the tail of the weapon effect.
**Syntax: '''''Float''''', meters

====$Mass:====
*How much of a kinetic effect this weapon has on its target. 3+ gives you the Flail effect. Set it to 10 and you can knock cruisers around.
*This is somehow multiplied by the speed. ie ''$Mass: 3'' and ''$Velocity: 200'' has much weaker kinetic effect than ''$Mass: 3'' and ''$Velocity: 1000''. Also $Mass is used to calculate intensity of "shudder" effect if flagged.
*Syntax: '''''Float''''', blast effect

====$Velocity:====
*How fast the weapon travels. Is also used to define the weapon range, '''''$Velocity x $Lifetime = range'''''.
*Beams travel instantly so this field has effect only on weapon range and AI beam targetting with certain beam types. $Velocity of beam also applies to its kinetic effect along with $Mass.
*Syntax: '''''Float''''', meters per second

====$Fire Wait:====
*Time in seconds between firings
*Syntax: '''''Float''''', seconds

====$Damage:====
*Base damage this weapon does. The actual damage is this number multiplied by the factors below.
*Base damage this beam does is continuous damage, damage is 5.5 times the damage value per second. The actual damage is this number multiplied by one of the factors below.
*Syntax: '''''Float''''', damage

====$Damage Type:====
{{Table36|
*Defines the damage type that this weapon uses. All armor effects are applied after shield and have no function against shockwave or subsystem damage. '''REQUIRES ADDITIONAL TABLE'''.
*Syntax: '''''String''''', name of the damage type as defined in [[armor.tbl]]}}

====$Arm time:====
{{Table36|
*Defines the time after the launch that is required before the weapon comes hot
*If the time has not been reached when the weapon detonates the Dinky explosion is used
*Syntax: '''''Float''''', seconds}}

====$Arm distance:====
{{Table36|
*Defines the distance from the firing ships that is required before the weapon comes hot
*If the distance has not been reached when the weapon detonates the Dinky explosion is used
*Syntax: '''''Float''''', meters}}

====$Arm radius:====
{{Table36|
*Defines the distance from the target where the weapon will arm itself
*Syntax: '''''Float''''', meters}}

====$Detonation Range:====
{{Table36|
*Defines the distance from the point in space that the weapon was launched where the weapon will detonate
*Syntax: '''''Float''''', meters}}

====$Detonation Radius:====
{{Table37|
*Defines the distance between the target center point point and the weapon which detonates the weapon.
*Syntax: '''''Float''''', meters}}

====$Shockwave damage:====
{{Table36|
*Override for the damage caused by shockwaves
*Syntax: '''''Float''''', damage}}

====$Shockwave Damage Type:====
{{Table36|
*'''REQUIRES ADDITIONAL TABLE'''. Defines the damage type used for the weapon explosions
*Syntax: '''''String''''', name as defined in [[armor.tbl]]}}

====$Blast Force:====
*The intensity of the blast effect when ship is within the outer radius of the explosion. Comes in effect only if inner and outer radius are defined.
*Syntax: '''''Float''''', blast effect

====$Inner Radius:====
*Radius at which the full explosion damage is done. Marks the line where damage attenuation begins.
*Syntax: '''''Float''''', meters

====$Outer Radius:====
*Maximum radius at which any damage is done
*Syntax: '''''Float''''', meters

====$Shockwave Speed:====
*Speed shockwave expands at. Zero means no shockwave and that damage is applied immediately
*Syntax: '''''Float''''', meters per second

====$Shockwave rotation:====
{{Table36|
*Defines how the 3D shockwave is rotated.
*Syntax: '''''Angle''''', three values, pitch, bank, heading respectively, in degrees}}

====$Shockwave model:====
{{Table36|
*Defines the model file (.pof) used as a shockwave for the 3D shockwaves.
*Syntax: '''''String.pof''''', model filename}}

====$Shockwave name:====
{{Table36|
*Defines the name of the animation used for the 2D shockwave
*Syntax: '''''String''''', filename}}

====$Dinky shockwave:====
{{Table36|
*Dinky shockwave are used if the weapon is shot down before arming or if the conditions marked at '''Arm time''' and '''Arm distance''' are not reached before impact
*It uses exactly same entries as the standard shockwaves
*'''''+Shockwave damage:'''''
*'''''+Shockwave damage type:'''''
*'''''+Blast Force:'''''
*'''''+Inner Radius:'''''
*'''''+Outer Radius:'''''
*'''''+Shockwave Speed:'''''
*'''''+Shockwave Rotation:'''''
*'''''+Shockwave Model:'''''
*'''''+Shockwave Name:'''''}}

====$Armor Factor:====
*Multiplier for the damage done to armor
*Syntax: '''''Float''''', damage multiplier

====$Shield Factor:====
*Multiplier for the damage done to shields
*Syntax: '''''Float''''', damage multiplier

====$Subsystem Factor:====
*Multiplier for the damage done to subsystems
*Syntax: '''''Float''''', damage multiplier

====$Lifetime Min:====
{{Table36|
*Defines the minimum lifetime of the weapon
*Syntax: '''''Float''''', seconds}}

====$Lifetime Max:====
{{Table36|
*Defines the maximum lifetime of the weapon
*Syntax: '''''Float''''', seconds}}

====$Lifetime:====
*Time before the standard primaries fizzle out and secondaries self destruct. Multiply this by the speed to get the range. If values are too low (below framerate) then the collision detection and graphic effects may suffer.
*This field has no effect for the beams apart from weapon range and AI beam targeting with certain beam types
*Syntax: '''''Float''''', seconds

====$Energy Consumed:====
*The amount of energy each bolt drains firing ship. Has no effect on turretted weapons.
*Syntax: '''''Float'''''

====$Cargo Size:====
*Cargo size, is not used with non-ballistic primaries.
*Amount of missiles available = Bank capacity / Cargo Size.
*Syntax: '''''Float'''''

====$Homing:====
*Only for secondaries. You can't have homing primaries. If this is set to YES with primaries, then the bolts turn to face their target but keep moving in the same direction. If the field is set to NO then following fields are not required in the table.
*Defines if the missiles in question is homing
*Syntax: '''''Boolean''''', yes or no
*'''+Type:'''
**Defines the homing method
**Syntax: '''''String''''', ''ASPECT'' or ''HEAT''
{{Table36| An additional option, ''JAVELIN'', has been added. This behaves like an aspect missile but automatically only locks onto the engines of a target, and only if the engines are in sight.}}
*'''+Turn Time:'''
**Defines how well missile maneuvers. Number of seconds it takes the missile to do a 360 degree circle
**Syntax: '''''Float''''', seconds
*'''+View Cone:'''
**'''Heat-seeking missiles only''', this is then number of degrees the missile sees. Value / 2 gives the angle from the missile's centerline.
**Syntax: '''''Float''''', degrees
{{Table36| Has been enabled also to aspect seekers as an option.}}

*'''+Min Lock Time:'''
**'''For aspect/javelin missiles only''', the minimum number of seconds to gain target lock
**Syntax: '''''Float''''', seconds
*'''+Lock Pixels/Sec:'''
**'''For aspect/javelin missiles only''', pixels the aspect triangle moves per second while attempting lock-on
**Syntax: '''''Integer''''', pixels per second
*'''+Catch-up Pixels/Sec:'''
**'''For aspect/javelin missiles only''', pixels moved per second while attempting to catch up to the target
**Syntax: '''''Integer''''', pixels per second
*'''+Catch-up Penalty:'''
**'''For aspect/javelin missiles only''', extra pixels to move after catching up ????
**Syntax: '''''Integer''''', pixels
{{Table36|
*'''+Seeker Strength:'''
**Defines the seeking ability of the homing system. Default of heat seekers is 3 and for aspect seekers 2. Spoofing change is defined as '''cm type effectiveness'''/'''seeker strength'''.
**Syntax: '''''Float''''', seeker strength}}

====$Swarm:====
*The number of missiles to fire per volley if it's a swarm missile
*Can be issued to Standard primaries also. Causes single part turrets to malfunction but causes multi part turrets to fire only on their barrel line. Can be used for 'burst fire weapons'.
*Is incompatible with "Corkscrew" option.
*Syntax: '''''Integer''''', number of shots in a swarm
{{Table36|
*'''+SwarmWait:'''
**Defines the time between weapons fired in a swarm
**Syntax: '''''Float''''', seconds
***Default: 0.150}}

====$Free Flight Time:====
{{Table36|
*Defines the free flight time of homing weapons. During this time weapon flies at 1/4 of its velocity + firing ships velocity in a straight line.
*Syntax: '''''Float''''', seconds
**Default: 0.25}}

====$LaunchSnd:====
*Corresponding sound effect when the weapon is launched.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

====$ImpactSnd:====
*Sound the weapon makes when it hits a hull.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

====$Disarmed ImpactSnd:====
{{Table36|
*Sound the weapon makes when it hits a hull before being armed.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

====$FlyBySnd:====
*The sound this weapon makes if it narrowly misses you. -1 is no sound.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]], usually -1

====$Model:====
{{Table36|
*Defines used model file. Included for compatibility with countermeasures as they have been merged with weapons in the code.
*Syntax: '''''String.pof''''', model filename}}

====$Rearm Rate:====
*Defines the rate the weapons are loaded to the ship
*Syntax: '''''Float''''', missiles loaded per second

====+Weapon Range:====
*Defines the range to the target where the weapons under AI will start firing.
*Syntax: '''''Float''''', meters

====+Weapon Min Range:====
{{Table36|
*Defines the minimum range to the target where the weapons under AI will still fire.
*Implemented before FS_Open 3.6.5
*Syntax: '''''Float''''', meters}}

====$Flags:====
*Flags are detailed below, in [[weapons.tbl#Weapon_Flags|weapon flags section]].

====$Trail:====
*This is used if you want your weapon to have a trail. Trail is often used only with secondaries though it works with standard primaries as well.
*'''+Start Width:'''
**How wide the head of the trail is.
**Syntax: '''''Float''''', meters
*'''+End Width:'''
**How wide the tail of the trail is.
**Syntax: '''''Float''''', meters
*'''+Start Alpha:'''
**The opacity of the trail head.
**Syntax: '''''Float''''', value between 0 and 1
*'''+End Alpha:'''
**The opacity of the trail tail.
**Syntax: '''''Float''''', value between 0 and 1
*'''+Max Life:'''
**How long the trail lasts.
**Syntax: '''''Float''''', seconds
*'''+Bitmap:'''
**The graphic file to use for the trail.
**Syntax: '''''String''''', filename

====$Icon:====
*Loadout icon used in the weapons selection screen.
*Syntax: '''''String''''', filename

====$Anim:====
*Green grid animation used on the weapons screen.
*Syntax: '''''String''''', filename

====$Collide Ship:====
{{Table36|
*Hook for [[Scripting.tbl|Lua]] scripting
*'''Globals:''' "Self", weapon with class that the hook is defined in. "Ship", ship that the weapon collided with.
*'''Override:''' Turns off all damage effects from weapon, as well as weapon being destroyed.}}

{{Table37|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

====$Collide Weapon:====
{{Table36|
*Hook for [[Scripting.tbl|Lua]] scripting
*'''Globals:''' "Self", weapon with class that the hook is defined in. "Weapon", other weapon.
*'''Override:''' Turns off weapon killing types with bombs. If two weapons, weapon "A" (arbitrary) is preferred}}

{{Table37|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

====$Impact Explosion:====
*Impact explosion used. Must be defined in weapon_expl.tbl,
*Syntax: '''''String''''', filename or ''none''

====$Impact Explosion Radius:====
*Radius of the defined impact explosion.
*Syntax: '''''Float''''', meters

====$Dinky impact explosion:====
{{Table36|
*Same as Impact explosion but for Dinky (not armed) explosions
*Syntax: '''''String''''', filename or ''none''}}

====$Dinky impact explosion radius:====
{{Table36|
*Same as Impact explosion radius but for Dinky explosions
*Syntax: '''''Float''''', meters}}

====$Muzzleflash:====
*Normally only with flak cannons.
*Defines the muzzle flash the weapon uses
*Syntax: '''''String''''', muzzleflash name, as defined in [[mflash.tbl]]

====$EMP Intensity:====
**If it has an EMP effect, how deeply it scrambles your electronics
**Syntax: '''''Float'''''

====$EMP Time:====
**Duration of the EMP effect
**Syntax: '''''Float''''', seconds

====$Leech Weapon:====
**The amount of weapon energy to drain with each hit
**Syntax: '''''Float'''''

====$Leech Afterburner:====
**The amount of afterburner fuel to drain with each hit
**Syntax: '''''Float'''''

====$Corkscrew:====
{{Table36|
*Allow corkscrew parameters to be defined
*'''+Num Fired:'''
**Defines the number of weapons fired in sequence. Same as the standard swarm entry but for corkscrew missiles
**Syntax: '''''Integer''''', number of missiles
*'''+Radius:'''
**Defines the radius used in the corkscrew motion
**Syntax: '''''Float''''', meters
*'''+Fire Delay:'''
**Defines the delay between missile firings
**Syntax: '''''Integer''''', milliseconds
*'''+Counter rotate:'''
**Defines if every other missile rotates to a different direction (clockwise / anticlockwise)
**Syntax: '''''Boolean''''', ''0'' or ''1'', no or yes
*'''+Twist:'''
**Defines the speed of rotation movement on the radius of corkscrew motion.
**Syntax: '''''Float''''', radians per second}}

====$Electronics:====
{{Table36|
*Defines the weapons effect against electronics. Requires [[weapons.tbl#"Electronics"|"electronics"]] flag. '''+New Style:''' and '''+Old Style:''' options are mutually exclusive.
*'''+New Style:'''
**Defines that the electronics use the new style which enables more options.
*'''+Old Style:'''
**Defines that the electronics use the old style. The old style was the way the D-Missile worked in Descent:Freespace.
*'''+Intensity:'''
**May only be used with '''+New Style:''' electronics. Defines how much the electronics hit affects larger ships. An intensity of 1.0 will disrupt a cruiser without trouble.
**Syntax: '''''Float'''''
*'''+Lifetime:'''
**Syntax: '''''Integer''''', milliseconds
*'''+Engine Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for engine subsytems.
**Syntax: '''''Float'''''
*'''+Weapon Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for non-beam turrets.
**Syntax: '''''Float'''''
*'''+Beam Turret Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for beam turrets.
**Syntax: '''''Float'''''
*'''+Sensors Multiplier:'''
**May only be used with '''+New Style:''' electronics. Defines how much longer the disruption effect lasts for sensor subsystems.
**Syntax: '''''Float'''''
*'''+Randomness Time:'''
**Defines the randomness of duration target suffers from the electronics hit. A random number between 0 and this time will be added or subtracted from the disruption time.
**Syntax: '''''Integer''''', milliseconds

* Without any electronics parameters, a weapon with the "electronics" flag will default to the ''Old Style'' mode with a lifetime of 6000 milliseconds and a randomness of 4000 milliseconds. Thus any ship that gets hit can get disrupted for anywhere between 2 to 10 seconds.}}

====$Spawn Angle:====
{{Table36|
*Defines the cone (with an angle) where the spawned weapons appear. ''Value'' gives the angle from the missiles centerline. The maximum possible angle between any two child weapons would be ''Value*2''.
*Syntax: '''''Float''''', degrees}}

====$Local SSM:====
{{Table36|
*Defines the local SSM (Subspace Missile). In effect missile moves via subspace to a position close to the target and starts homing.
*Weapon must be '''''aspect seeking missile''''' and must have '''''[[Weapons.tbl#"local ssm"|local ssm]]''''' flag.
*'''+Warpout Delay:'''
**Defines the time between the missile launch and the subspace jump.
**Syntax: '''''Integer''''', milliseconds
*'''+Warpin Delay:'''
**Defines the time missile stays in subspace before exiting.
**Syntax: '''''Integer''''', milliseconds
*'''+Stage 5 Velocity:'''
**Defines the velocity of the missile after the subspace jump.
**Syntax: '''''Float''''', meters per second
*'''+Warpin Radius:'''
**Defines how far from the SSM will appear from the outer radius of the target.
**Syntax: '''''Float''''', meters
*'''+Lock Range:'''
**Defines the maximum range where SSM can achieve target lock
**Syntax: '''''Float''''', meters}}

====$Countermeasure:====
{{Table36|
*Defines the countermeasure effectiveness and radius
*'''+Heat Effectiveness:'''
**Defines the countermeasures effectiveness against heat seeking missiles
**Syntax: '''''Float''''', cm effectiveness
***Default: 1
*'''+Aspect Effectiveness:'''
**Defines the countermeasures effectiveness against aspect seeking missiles
**Syntax: '''''Float''''', cm effectiveness
***Default: 1
*'''+Effective Radius:'''
**Defines the countermeasures effective radius
**Syntax: '''''Float''''', meters
***Default: 300}}

====$BeamInfo:====
*'''+Type:'''
**Defines the type of beam in question. Beam types: 0 is a standard non-slashing type beam. 1 is a slashing type beam. 2 is a targetting beam that doesn't seem to have much of an effect on anything. 3 is a beam type that fires pulses in anti-fighter role and acts like type 0 beam in other roles. 4 is a beam that is restricted to what is directly in front of it, along turrets firepoints normal.
**Syntax: '''''Integer''''',, only values from 0 to 4 are legal
*'''+Life:'''
**How long it lasts once the beam is actually firing.
**Syntax: '''''Float''''', seconds
*'''+Warmup:'''
**Warmup time
**Syntax: '''''Integer''''', milliseconds
*'''+Warmdown:'''
**Warmdown time
**Syntax: '''''Integer''''', milliseconds
*'''+Radius:'''
**Muzzle glow radius
**Syntax: '''''Float''''', meters
*'''+PCount:'''
**Particles spewed every interval. ??
**Syntax: '''''Integer'''''
*'''+PRadius:'''
**Particle radius
**Syntax: '''''Float''''', meters
*'''+PAngle:'''
**Defines the random "cone" where the particles are generated
**Syntax: '''''Float''''', angle of the cone
*'''+PAni:'''
**Animation used to represent the particles
**Syntax: '''''String''''', filename
*'''+Miss Factor:'''
**The higher the numbers, the more likely that this beam will miss. One value for every difficulty level
**Syntax: '''''Miss Factor''''', five '''floats''', very easy, easy, moderate, hard, insane, respectively.
***Example: 0.5 0.975 1.35 1.875 2.5
*'''+BeamSound:'''
**Corresponding looping sound effect when the beam is firing.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+WarmupSound:'''
**Corresponding sound effect when the beam is beam warmed up.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+WarmdownSound:'''
**Corresponding sound effect when the beam is warming down.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+Muzzleglow:'''
**Defines the bitmap used to create the muzzle glow
**Syntax: '''''String''''', filename
*'''+Shots:'''
**Defines into how may invidual shots the type 3 (AAA) beams are divided. Note total firing is the same as the +Life:
**Syntax: '''''Integer'''''
*'''+ShrinkFactor:'''
**What percentage of lifetime where beam starts shrinking (0.1 == 10% life left)
**Syntax: '''''Float'''''
*'''+ShrinkPct:'''
**What percentage of max width we subtract per second
**Syntax: '''''Float'''''
{{Table36|
*'''+Range:'''
**Defines the maximum range where the beam still has any effect.
**Syntax: '''''Float''''', meters
*'''+Attenuation:'''
**Defines the point where the damage caused by the beam starts to attenuate. At maximum range damage is zero.
**Syntax: '''''Float''''', from 0 - firing point to 1 - no effect
***Default: 1}}

*'''$Section:'''
**Beams are made up of up to five sections layered atop one another to create the effect. Each section has its own parameters.
{{Table36|
:*'''+Index:'''
:**Field used to define with [[Modular Tables]] the beam section which is edited.
:**Syntax: '''''Integer''''', index number legal values are from 0 to 5
:*'''+remove'''
:**Removes the set beam section.
:*'''+nocreate'''
:**Does not create new section for the beam}}

:*'''+Width:'''
:**Width of the section
:**Syntax: '''''Float''''', meters
:*'''+Texture:'''
:**Texture for the section
:**Syntax: '''''String''''', filename
:*'''+RGBA Inner:'''
:**Defines the color and transparency of the center of the section
:**Syntax: '''''Color''''', red, green, blue, alpha, respectively, value from 0 to 255
:***Example: 255 255 255 255
:*'''+RGBA Outer:'''
:**Defines the color and transparency of the edges of the section
:**Syntax: '''''Color''''', red, green, blue, alpha, respectively, value from 0 to 255
:***Example: 150 150 150 10
:*'''+Flicker:'''
:**Defines how much the section flickers
:**Syntax: '''''Float''''', value from 0 to 1
:*'''+Zadd:'''
:**Defines the 'thickness' of the section. The higher the Zadd, the closer the section appears to be.
:**Syntax: '''''Float'''''
{{Table36|
:*'''+Tile Factor:'''
:**Defines the beam texture tileing factor. Second number defines the tileing type. Type 0 tiles the graphic in the beam as many times as defined by the 1st number. Type 1 uses the 1st value as the lenght of the tile.
:**Syntax: '''''Float''''', '''''Integer'''''
:*'''+Translation:'''
:**Defines the speed of translation of the beam, a positive value moves from the impact point to the firing point, while a negative value moves away from the firing point towards the impact point. Measured in tiles per second, where the tile count is defined in the "+Tile Factor:" field above.
:**Syntax: '''''Float'''''}}

====$Pspew:====
{{Table36|
*Defines a particle spew effect for the given weapon
*'''+Count:'''
**Defines how many particles are spawn when they are ready to be created
**Syntax: '''''Integer'''''
*'''+Time:'''
**Defines the time in milliseconds between next particle(s) spewed
**Syntax: '''''Integer''''', milliseconds
*'''+Vel:'''
**Defines the created particles velocity as percentage of the weapons velocity
**Syntax: '''''Float'''''
*'''+Radius:'''
**Defines the size of the created particles
**Syntax: '''''Float''''', meters
*'''+Life:'''
**Defines how long the particles last.
**Syntax: '''''Float''''', seconds
*'''+Scale:'''
**Defines the particle spread. Small value will make particles group together
**Syntax: '''''Float'''''
*'''+Bitmap:
**Defines the animation used to create the particle spew effect
**Syntax: '''''String''''', filename}}

====$Tag:====
*Allowed for secondary weapons
*Location: After $Impact Explosion Radius:
*Sets this weapon as a TAG missile, level 1, 2, or 3. The second number is the duration in seconds.
*TAG Level 1 will illuminate hidden targets such as stealth fighters or ships normally obscured by nebula conditions.
*TAG Level 2 illiminates targets much like TAG Level 1, but turrets will prefer to shoot at them over other ships.
*TAG Level 3 has no effect in retail.
*Syntax: '''''Integer''''' '''''Float''''', TAG level and seconds respectively

====$SSM:====
{{Table36|
*Defines the weapons SSM index number:
*Syntax: '''''Integer'''''}}

====$FOF:====
{{Table36|
*Defines the field of fire for the weapon. Causes weapon to fire into a firing cone instead of direct firing line thus causing light inaccuracy
*Syntax: '''''Float''''', degrees}}

====$Shots:====
{{Table36|
*Defines the number of shots every time the weapon is fired.
*Syntax: '''''Integer''''', number of shots}}

====$decal:====
{{Table36|
*Defines impact decals if they are in use
*'''''Currently broken'''''
*'''+texture:'''
**Defines the texture used for impact decals (can use '''''-burn''''' and '''''-glow''''' textures)
**Syntax: '''''String''''', filename
*'''+backface texture:'''
**Defines ???
**Syntax: '''''String''''', filename
*'''+radius:'''
**Defines the size of the impact decals on target
**Syntax: '''''Float''''', meters
*'''+burn time:'''
**Defines the time the '''''-burn''''' texture appears on the target
**Syntax: '''''Integer''''', milliseconds}}

====$Transparent:====
{{Table36|
*Defines weapon effect as transparent. Enables optional fields for 'alpha animations'
*'''+Alpha:'''
**Defines the strenght of the alpha (transparency). And also the maximum value for the alpha cycle option
**Syntax: '''''Float''''', from 0 to 1
*'''+Alpha Min:'''
**Defines the minimum alpha value for alpha cycle option
**Syntax: '''''Float''''', from 0 to 1
*'''+Alpha Cycle:'''
**Defines the change in alpha per frame, between '''Alpha''' and '''Alpha Min''' values
**Syntax: '''''Float'''''}}

==Weapon Flags==

==="Electronics"===
*Will seize up the weapons and engines systems of any ship for a short period of time.

==="Spawn ''Name'',''Value''"===
*Will spawn the specified number of defined missiles upon detonation.

==="Remote Detonate"===
*Can be triggered remotely via a second press on the trigger

==="Puncture"===
*Reduces hull damage by 25%

==="Big Ship"===
*These weapons cannot be mounted on small ships like fighters, bombers, sentry guns etc.

==="Huge"===
*Allows this weapon to do the final 10% damage to a ship with the "Big Damage" flag.

==="Supercap"===
*Allows this weapon to do the final 75% damage to a ship with the "supercap" flag.

==="Bomber+"===
*The AI will prefer to use this weapon against bombers

==="child"===
*Cannot be set as a weapon on any ship, but is instead a child of a weapon. Usually defined with "Spawn ''Name'',''Value''"

==="Bomb"===
*Makes this weapon targetable with the B key, and the AI prefers to use it against large ships

==="No Dumbfire"===
*Missile will not fire without a lock

==="in tech database"===
*Has the weapon in the tech database at the start of the campaign

==="Player allowed"===
*Allows this weapon as a player weapon.
{{Table36|
*'''EXTREMELY IMPORTANT NOTE:'''
**Whenever you plan to use a weapon as a player one in your campaign or missions, '''DO USE THIS FLAG'''.
**Not using it can cause problems within fs_open and it's a BAD MOD DESIGN.
**In the future, fs_open will maybe be able to avoid these problems but, nevertheless, it's still a BAD DESIGN.
**As another possible example: be careful to update "retail" tables if you plan to use Shivan weapons in player fighters.}}

==="Particle Spew"===
*Makes the weapon projectile spew out particles
{{Table36|
*Can be defined with [[Weapons.tbl#$Pspew:|Particle Spew parameters]]}}

==="EMP"===
*This weapon will have an EMP effect on any ship within the blast radius
*Can be defined with [[Weapons.tbl#$EMP_Intensity:|EMP Intensity]] and [[Weapons.tbl#$EMP_Time:|EMP Time]]

==="Esuck"===
*Drains the target's energy banks
*Can be defined with [[Weapons.tbl#$Leech_Weapon:|Leech Weapon]] and [[Weapons.tbl#$Leech_Afterburner:|Leech Afterburner]]

==="Flak"===
*Makes this weapon a [[weapons.tbl#Flak_Guns|flak gun]]

==="Corkscrew"===
*Makes this weapon spiral AND swarm 4.
{{Table36|
*Can be defined with [[Weapons.tbl#$Corkscrew:|Corkscrew parameters]]}}

==="Shudder"===
*Makes your ship shudder while you're firing the weapon

==="lockarm"===
*Requires a target lock in order to arm its warhead. In other words weapon causes less damage if it hits the target without target lock.

==="beam"===
*Makes this weapon a [[weapons.tbl#Beam Cannons|beam cannon]]

==="stream"===
*Gives this weapon a streaming effect. In effect weapon keeps firing when firing button is kept pressed.

==="puncture"===
*Reduces hull damage by 75%

==="supercap"===
*Makes weapon capable of causing real damage against ships with "supercap" flag.

==="countermeasure"===
{{Table36|
*Defines the weapon as a countermeasure}}

==="Ballistic"===
{{Table36|
*Defines the weapon as a ballistic weapon that needs ammunition.
*Make sure you define the size and reload rate for ballistic weapons}}

==="pierce shields"===
{{Table36|
*Causes weapons to penetrate shield without causing damage to it.}}

==="no pierce shields"===
{{Table36|
*Prevents weapons (beams) from piercing shields causing shields to be damaged by weapons first.}}

==="local ssm"===
{{Table36| }}

==="tagged only"===
{{Table36|
*Weapon can only be fired at tagged targets}}

==="beam no whack"===
{{Table36|
*Disables beam whacking (push). Practically same as setting beam mass to zero.}}

==="cycle"===
{{Table36|
*Causes weapon to alternate between firing points}}

==="small only"===
{{Table36|
*Causes AI to use the weapon only on small targets (fighters, bombers etc.)}}

==="same turret cooldown"===
{{Table36|
*Forces the turrets to fire on the designated rate of fire on all difficulty levels and all AI levels}}

==="apply no light"===
{{Table36|
*Prevents light from being applied to the weapon model.}}

==="inherit parent target"===
{{Table37|
*Sets spawned 'child' weapons to use parent weapon's target-}}

==="training"===
{{Table37|
*Sets weapon to be of training weapon type. ?}}

==Countermeasures==
*Usually not altered. Only one can exist
{{Table36|
*More than one can exist}}

===$Name:===
*Name of the countermeasure
*Syntax: '''''String''''', name

===$Velocity:===
*Defines the spped of the countermeasure, relative to the ship.
*Syntax: '''''Float''''', meter per second

===$Fire Wait:===
*Definies the minumum time between the countermeasure launches
*Syntax: '''''Float''''', seconds

===Lifetime===
*Countermeasure's life time is defined between with minimum and maximum lifetime
*'''$Lifetime Min:'''
**Syntax: '''''Float''''', seconds
*'''$Lifetime Max:'''
**Syntax: '''''Float''''', seconds

===$LaunchSnd:===
*Defines the sound for the countermeasure launch
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

===$Model:===
*Defines the used model file (.pof)
*Syntax: '''''String.pof''''', model filename

==Player Weapon Precedence==
*First the primary weapons are defined, from most powerful to least powerful, and then the same for secondaries
*Syntax: ( '''''"String" "String"'''''), names of the weapons
*Example:

<pre>
$Player Weapon Precedence: (
"UD-8 Kayser"
"Prometheus R"
"Subach HL-7"
"Harpoon"
"Tempest"
"Rockeye" )
</pre>

==Sample==

<pre>
#Primary Weapons

$Name: @Subach HL-7
+Title: XSTR("GTW Subach HL-7", 3243)
+Description:
XSTR( "Standard Issue
Level 3 Hull Damage
Level 2 Shield Damage", 3244)
$end_multi_text
+Tech Title: XSTR("Subach HL-7", 146)
+Tech Anim: Tech_Subach_HL-7
+Tech Description:
XSTR(
"Descriptive text...", -1)
$end_multi_text
$Model File: none
@Laser Bitmap: newglo9
@Laser Glow: 2_laserglow03
@Laser Color: 250, 0, 0
@Laser Color2: 0, 0, 250
@Laser Length: 10.0
@Laser Head Radius: 0.90
@Laser Tail Radius: 0.90
$Mass: 0.2
$Velocity: 450.0
$Fire Wait: 0.2
$Damage: 15
$Armor Factor: 0.9
$Shield Factor: 0.7
$Subsystem Factor: 0.3
$Lifetime: 2.0
$Energy Consumed: 0.20
$Cargo Size: 0.0
$Homing: NO
$LaunchSnd: 76
$ImpactSnd: 85
$Flags: ( "in tech database"
"player allowed"
"stream")
$Icon: iconSD4
$Anim: SD4
$Impact Explosion: none

#End

#Secondary Weapons

$Name: EMP Adv.
+Title: XSTR("GTM-14 EMP Adv.", 3396)
+Description:
XSTR( "Advanced Missile
Electromagnetic Pulse Weapon
General Purpose Suppression", 3397)
$end_multi_text
+Tech Title: XSTR("GTM-14 EM Pulse Adv.", 3398)
+Tech Anim: Tech_EMP
+Tech Description:
XSTR(
"Descriptive text...", -1)
$end_multi_text
$Model File: EMPulse2.pof
$Mass: 15.0
$Velocity: 275.0
$Fire Wait: 2.0
$Damage: 45
$Blast Force: 20.0
$Inner Radius: 80.0
$Outer Radius: 300.0
$Shockwave Speed: 120.0
$Armor Factor: 1.0
$Shield Factor: 0.8
$Subsystem Factor: 0.5
$Lifetime: 5.0
$Energy Consumed: 0.0
$Cargo Size: 4.0
$Homing: YES
+Type: ASPECT
+Turn Time: 1.0
+Min Lock Time: 2.0
+Lock Pixels/Sec: 70
+Catch-up Pixels/Sec: 100
+Catch-up Penalty: 30
$LaunchSnd: 118
$ImpactSnd: 88
$FlyBySnd: -1
$Rearm Rate: 2.0
$Flags: ( "player allowed"
"EMP")
$Trail:
+Start Width: 0.25
+End Width: 0.75
+Start Alpha: 1.0
+End Alpha: 0.0
+Max Life: 1.5
+Bitmap: MissileTrail04
$Icon: iconEMPulse
$Anim: ecm
$Impact Explosion: ExpMissileHit1
$Impact Explosion Radius: 10.0
$EMP Intensity: 375.0
$EMP Time: 20.0

#End

$Player Weapon Precedence: (
"Subach HL-7"
"EMP Adv." )
</pre>

[[Category:Tables]]

8472 theory

2008-03-28T17:16:21Z

Kopachris:

{{non-canon}}
==Species 8472 Theory==
Perhaps the people at Volition watch Star Trek: Voyager. I don't know. But the Shivans do bear many similarities to species 8472, so here's my theory.

The Ancients were powerful. They conquered and destroyed, adapted and evolved. I believe that they developed subspace technology to the point of being able to use subspace to enter an alternate dimension, possibly similar to [http://memory-alpha.org/en/wiki/Fluidic_space|"fluidic space"]. Ships, both Ancient and Shivan went in and out of fluidic space and normal space for as long as a portal was open. But the Shivans, with their advanced technology and physiology, were able to stop the Ancients. For the first time, the Ancients encountered resistance. Resistance was not futile.

With the Ancients gone, and the technology to enter "fluidic space" gone, many Shivans were trapped in normal space. Many, many Shivans. The Shivans adapted to normal space and developed their technology even more. Their shielding, their beam weapons, everything was honed over thousands of years. In those thousands of years, they had to strip planets of specific resources to create the technology used to hopefully return to their realm. The Sathanas juggernauts were designed to cause a star to go supernova and open a singularity to return to fluidic space. Their first attempt with the technology, about 200-500 years after the destruction of the Ancients, was a disaster. The star they caused to go supernova, which is now the [[wikipedia:Crab_Nebula|Crab Nebula]], was not the right kind and did not create the singularity necessary to return to their realm. The infant Shivan Empire dwindled to a few ships.

But it was enough. The Shivans mapped their way across the galaxy, slowly building ships and building an empire. Over the next eight and a half thousand years, they built a new fleet of Sathanas-class juggernauts, to put their plan into action.

The Shivans are not stupid. No, they are quite intelligent. Their subspace communication nodes that they left behind were able to transmit sensor data clear across the galaxy. When they realized the Terrans and Vasudans were going to develop space-faring technology, they predicted that they would also discover subspace nodes and explore the galaxy. Not wanting to needlessly destroy the Terrans and Vasudans, they reconstructed a Lucifer destroyer on their way back.

The Lucifer, with its shielding that is impervious to plasma, electromagnetic, and projectile based weaponry, had a purpose other than mindless destruction. The Shivans knew the supernova of Capella, the star they determined would be perfect for the job, would end life in the galaxy as we knew it if the shockwaves in subspace were allowed to travel along the subspace conduits that connect stars. To ensure that the Terrans and Vasudans destroy the nodes linking Capella to the rest of the Terran-Vasudan area of the galaxy, the Shivans had to destroy a planet. Only after Vasuda Prime was destroyed would the scientists-made-refugees be led to Altair, where remains of the Ancients would lead them to a better understanding of subspace technology.

Only if the Terrans and Vasudans understood subspace to some level, and under the threat of complete annihilation, would they realize the importance of cutting-off the Capella system.

So Capella was cut off and went supernova, and the Shivans made it back to their own realm, hopefully never to be seen again.

[[Category:Shivan Theories]]

Shivan theories

2008-03-25T03:16:11Z

Kopachris:

There are probably as many theories about the Shivans motives, origin, and actions as there are people who play Freespace 2. These are several of them in order to make people think, please do not simpley read them and decide "which one is right" you should come up with your own ideas.
 
{{category:Shivan Theories}}
 
* [[8472 Theory]]
* [[Capellan Barbecue Theory]]
* [[Freak's Theory]]
* [[Mad Bomber's Theory]]
* [[Ngtm1r's Shivan Theory]]
* [[Shivan Manifesto]]
* [[Snail's Theory]]
* [[Trailer Shivan Theory]]

[[Category:Shivan_Theories]]

8472 theory

2008-03-25T03:15:31Z

Kopachris:

{{non-canon}}
==Species 8472 Theory==
Perhaps the people at Volition watch Star Trek: Voyager. I don't know. But the Shivans do bear many similarities to species 8472, so here's my theory.

The Ancients were powerful. They conquered and destroyed, adapted and evolved. I believe that they developed subspace technology to the point of being able to use subspace to enter an alternate dimension, possibly similar to [http://memory-alpha.org/en/wiki/Fluidic_space|"fluidic space"]. Ships, both Ancient and Shivan went in and out of fluidic space and normal space for as long as a portal was open. But the Shivans, with their advanced technology and physiology, were able to stop the Ancients. For the first time, the Ancients encountered resistance. Resistance was not futile.

With the Ancients gone, and the technology to enter "fluidic space" gone, many Shivans were trapped in normal space. Many, many Shivans. The Shivans adapted to normal space and developed their technology even more. Their shielding, their beam weapons, everything was honed over thousands of years. In those thousands of years, they had to strip planets of specific resources to create the technology used to hopefully return to their realm. The Sathanas juggernauts were designed to cause a star to go supernova and open a singularity to return to fluidic space. Their first attempt with the technology, about 200-500 years after the destruction of the Ancients, was a disaster. The star they caused to go supernova, which is now the [[wikipedia:Crab_Nebula|Crab Nebula]], was not the right kind and did not create the singularity necessary to return to their realm. The infant Shivan Empire dwindled to a few ships.

But it was enough. The Shivans mapped their way across the galaxy, slowly building ships and building an empire. Over the next eight and a half thousand years, they built a new fleet of Sathanas-class juggernauts, to put their plan into action.

The Shivans are not stupid. No, they are quite intelligent. Their subspace communication nodes that they left behind were able to transmit sensor data clear across the galaxy. When they realized the Terrans and Vasudans were going to develop space-faring technology, they predicted that they would also discover subspace nodes and explore the galaxy. Not wanting to needlessly destroy the Terrans and Vasudans, they constructed a new ship on their way back.

The new ship, the Lucifer, with its shielding that is impervious to plasma, electromagnetic, and projectile based weaponry, had a purpose other than mindless destruction. The supernova of Capella, the star they determined would be perfect for the job, would end life in the galaxy as we knew it, if the shockwaves in subspace were allowed to travel along the subspace conduits that connect stars. To ensure that the Terrans and Vasudans destroy the node linking Capella to the rest of the Terran-Vasudan area of the galaxy, the Shivans had to destroy a planet. Only then would the scientists-made-refugees be led to Altair, where remains of the Ancients would lead them to better subspace technology.

Only if the Terrans and Vasudans understood subspace to some level, and under threat of destruction, would they realize the importance of cutting-off the Capella system.

So Capella was cut off and went supernova, and the Shivans made it back to their own realm, hopefully never to be seen again.

[[Category:Shivan Theories]]

8472 theory

2008-03-25T03:14:17Z

Kopachris:

{{non-canon}}
==Species 8472 Theory==
Perhaps the people at Volition watch Star Trek: Voyager. I don't know. But the Shivans do bear many similarities to species 8472, so here's my theory.

The Ancients were powerful. They conquered and destroyed, adapted and evolved. I believe that they developed subspace technology to the point of being able to use subspace to enter an alternate dimension, possibly similar to [http://memory-alpha.org/en/wiki/Fluidic_space|"fluidic space"]. Ships, both Ancient and Shivan went in and out of fluidic space and normal space for as long as a portal was open. But the Shivans, with their advanced technology and physiology, were able to stop the Ancients. For the first time, the Ancients encountered resistance. Resistance was not futile.

With the Ancients gone, and the technology to enter "fluidic space" gone, many Shivans were trapped in normal space. Many, many Shivans. The Shivans adapted to normal space and developed their technology even more. Their shielding, their beam weapons, everything was honed over thousands of years. In those thousands of years, they had to strip planets of specific resources to create the technology used to hopefully return to their realm. The Sathanas juggernauts were designed to cause a star to go supernova and open a singularity to return to fluidic space. Their first attempt with the technology, about 200-500 years after the destruction of the Ancients, was a disaster. The star they caused to go supernova, which is now the [[wikipedia:Crab_Nebula|Crab Nebula]], was not the right kind and did not create the singularity necessary to return to their realm. The infant Shivan Empire dwindled to a few ships.

But it was enough. The Shivans mapped their way across the galaxy, slowly building ships and building an empire. Over the next eight and a half thousand years, they built a new fleet of Sathanas-class juggernauts, to put their plan into action.

The Shivans are not stupid. No, they are quite intelligent. Their subspace communication nodes that they left behind were able to transmit sensor data clear across the galaxy. When they realized the Terrans and Vasudans were going to develop space-faring technology, they predicted that they would also discover subspace nodes and explore the galaxy. Not wanting to needlessly destroy the Terrans and Vasudans, they constructed a new ship on their way back.

The new ship, the Lucifer, with its shielding that is impervious to plasma, electromagnetic, and projectile based weaponry, had a purpose other than mindless destruction. The supernova of Capella, the star they determined would be perfect for the job, would end life in the galaxy as we knew it, if the shockwaves in subspace were allowed to travel along the subspace conduits that connect stars. To ensure that the Terrans and Vasudans destroy the node linking Capella to the rest of the Terran-Vasudan area of the galaxy, the Shivans had to destroy a planet. Only then would the scientists-made-refugees be led to Altair, where remains of the Ancients would lead them to better subspace technology.

Only if the Terrans and Vasudans understood subspace to some level, and under threat of destruction, would they realize the importance of cutting-off the Capella system.

So Capella was cut off and went supernova, and the Shivans made it back to their own realm, hopefully never to be seen again.

8472 theory

2008-03-25T03:13:47Z

Kopachris:

{{non-canon}}
==Species 8472 Theory==
Perhaps the people at Volition watch Star Trek: Voyager. I don't know. But the Shivans do bear many similarities to species 8472, so here's my theory.

The Ancients were powerful. They conquered and destroyed, adapted and evolved. I believe that they developed subspace technology to the point of being able to use subspace to enter an alternate dimension, possibly similar to [http://memory-alpha.org/en/wiki/Fluidic_space|'fluidic space']. Ships, both Ancient and Shivan went in and out of fluidic space and normal space for as long as a portal was open. But the Shivans, with their advanced technology and physiology, were able to stop the Ancients. For the first time, the Ancients encountered resistance. Resistance was not futile.

With the Ancients gone, and the technology to enter "fluidic space" gone, many Shivans were trapped in normal space. Many, many Shivans. The Shivans adapted to normal space and developed their technology even more. Their shielding, their beam weapons, everything was honed over thousands of years. In those thousands of years, they had to strip planets of specific resources to create the technology used to hopefully return to their realm. The Sathanas juggernauts were designed to cause a star to go supernova and open a singularity to return to fluidic space. Their first attempt with the technology, about 200-500 years after the destruction of the Ancients, was a disaster. The star they caused to go supernova, which is now the [[wikipedia:Crab_Nebula|Crab Nebula]], was not the right kind and did not create the singularity necessary to return to their realm. The infant Shivan Empire dwindled to a few ships.

But it was enough. The Shivans mapped their way across the galaxy, slowly building ships and building an empire. Over the next eight and a half thousand years, they built a new fleet of Sathanas-class juggernauts, to put their plan into action.

The Shivans are not stupid. No, they are quite intelligent. Their subspace communication nodes that they left behind were able to transmit sensor data clear across the galaxy. When they realized the Terrans and Vasudans were going to develop space-faring technology, they predicted that they would also discover subspace nodes and explore the galaxy. Not wanting to needlessly destroy the Terrans and Vasudans, they constructed a new ship on their way back.

The new ship, the Lucifer, with its shielding that is impervious to plasma, electromagnetic, and projectile based weaponry, had a purpose other than mindless destruction. The supernova of Capella, the star they determined would be perfect for the job, would end life in the galaxy as we knew it, if the shockwaves in subspace were allowed to travel along the subspace conduits that connect stars. To ensure that the Terrans and Vasudans destroy the node linking Capella to the rest of the Terran-Vasudan area of the galaxy, the Shivans had to destroy a planet. Only then would the scientists-made-refugees be led to Altair, where remains of the Ancients would lead them to better subspace technology.

Only if the Terrans and Vasudans understood subspace to some level, and under threat of destruction, would they realize the importance of cutting-off the Capella system.

So Capella was cut off and went supernova, and the Shivans made it back to their own realm, hopefully never to be seen again.

8472 theory

2008-03-25T03:13:19Z

Kopachris:

{{non-canon}}
==Species 8472 Theory==
Perhaps the people at Volition watch Star Trek: Voyager. I don't know. But the Shivans do bear many similarities to species 8472, so here's my theory.

The Ancients were powerful. They conquered and destroyed, adapted and evolved. I believe that they developed subspace technology to the point of being able to use subspace to enter an alternate dimension, possibly similar to [http://memory-alpha.org/en/wiki/Fluidic_space|fluidic space]. Ships, both Ancient and Shivan went in and out of fluidic space and normal space for as long as a portal was open. But the Shivans, with their advanced technology and physiology, were able to stop the Ancients. For the first time, the Ancients encountered resistance. Resistance was not futile.

With the Ancients gone, and the technology to enter "fluidic space" gone, many Shivans were trapped in normal space. Many, many Shivans. The Shivans adapted to normal space and developed their technology even more. Their shielding, their beam weapons, everything was honed over thousands of years. In those thousands of years, they had to strip planets of specific resources to create the technology used to hopefully return to their realm. The Sathanas juggernauts were designed to cause a star to go supernova and open a singularity to return to fluidic space. Their first attempt with the technology, about 200-500 years after the destruction of the Ancients, was a disaster. The star they caused to go supernova, which is now the [[wikipedia:Crab_Nebula|Crab Nebula]], was not the right kind and did not create the singularity necessary to return to their realm. The infant Shivan Empire dwindled to a few ships.

But it was enough. The Shivans mapped their way across the galaxy, slowly building ships and building an empire. Over the next eight and a half thousand years, they built a new fleet of Sathanas-class juggernauts, to put their plan into action.

The Shivans are not stupid. No, they are quite intelligent. Their subspace communication nodes that they left behind were able to transmit sensor data clear across the galaxy. When they realized the Terrans and Vasudans were going to develop space-faring technology, they predicted that they would also discover subspace nodes and explore the galaxy. Not wanting to needlessly destroy the Terrans and Vasudans, they constructed a new ship on their way back.

The new ship, the Lucifer, with its shielding that is impervious to plasma, electromagnetic, and projectile based weaponry, had a purpose other than mindless destruction. The supernova of Capella, the star they determined would be perfect for the job, would end life in the galaxy as we knew it, if the shockwaves in subspace were allowed to travel along the subspace conduits that connect stars. To ensure that the Terrans and Vasudans destroy the node linking Capella to the rest of the Terran-Vasudan area of the galaxy, the Shivans had to destroy a planet. Only then would the scientists-made-refugees be led to Altair, where remains of the Ancients would lead them to better subspace technology.

Only if the Terrans and Vasudans understood subspace to some level, and under threat of destruction, would they realize the importance of cutting-off the Capella system.

So Capella was cut off and went supernova, and the Shivans made it back to their own realm, hopefully never to be seen again.

8472 theory

2008-03-25T03:12:27Z

Kopachris: New page: {{non-canon}} ==Species 8472 Theory== Perhaps the people at Volition watch Star Trek: Voyager. I don't know. But the Shivans do bear many similarities to species 8472, so here's my theor...

{{non-canon}}
==Species 8472 Theory==
Perhaps the people at Volition watch Star Trek: Voyager. I don't know. But the Shivans do bear many similarities to species 8472, so here's my theory.

The Ancients were powerful. They conquered and destroyed, adapted and evolved. I believe that they developed subspace technology to the point of being able to use subspace to enter an alternate dimension, possibly similar to [http://memory-alpha.org/en/wiki/Fluidic_space|fluidic space]. Ships, both Ancient and Shivan went in and out of fluidic space and normal space for as long as a portal was open. But the Shivans, with their advanced technology and physiology, were able to stop the Ancients. For the first time, the Ancients encountered resistance. Resistance was not futile.

With the Ancients gone, and the technology to enter "fluidic space" gone, many Shivans were trapped in normal space. Many, many Shivans. The Shivans adapted to normal space and developed their technology even more. Their shielding, their beam weapons, everything was honed over thousands of years. In those thousands of years, they had to strip planets of specific resources to create the technology used to hopefully return to their realm. The Sathanas juggernauts were designed to cause a star to go supernova and open a singularity to return to fluidic space. Their first attempt with the technology, about 200-500 years after the destruction of the Ancients, was a disaster. The star they caused to go supernova, which is now the [[wikipedia:Crab_Nebula]], was not the right kind and did not create the singularity necessary to return to their realm. The infant Shivan Empire dwindled to a few ships.

But it was enough. The Shivans mapped their way across the galaxy, slowly building ships and building an empire. Over the next eight and a half thousand years, they built a new fleet of Sathanas-class juggernauts, to put their plan into action.

The Shivans are not stupid. No, they are quite intelligent. Their subspace communication nodes that they left behind were able to transmit sensor data clear across the galaxy. When they realized the Terrans and Vasudans were going to develop space-faring technology, they predicted that they would also discover subspace nodes and explore the galaxy. Not wanting to needlessly destroy the Terrans and Vasudans, they constructed a new ship on their way back.

The new ship, the Lucifer, with its shielding that is impervious to plasma, electromagnetic, and projectile based weaponry, had a purpose other than mindless destruction. The supernova of Capella, the star they determined would be perfect for the job, would end life in the galaxy as we knew it, if the shockwaves in subspace were allowed to travel along the subspace conduits that connect stars. To ensure that the Terrans and Vasudans destroy the node linking Capella to the rest of the Terran-Vasudan area of the galaxy, the Shivans had to destroy a planet. Only then would the scientists-made-refugees be led to Altair, where remains of the Ancients would lead them to better subspace technology.

Only if the Terrans and Vasudans understood subspace to some level, and under threat of destruction, would they realize the importance of cutting-off the Capella system.

So Capella was cut off and went supernova, and the Shivans made it back to their own realm, hopefully never to be seen again.

SJ Sathanas

2008-03-24T00:27:08Z

Kopachris: /* Veteran Comments */

The '''SJ ''Sathanas''''' is the most powerful space-faring warship ever encountered by the [[Galactic Terran-Vasudan Alliance|GTVA]]. With four ultra-heavy beam cannons, a Sathanas outstrips even a [[GTVA Colossus|''Colossus''-class vessel]] in terms of raw firepower.

{{spoiler}}
*Freespace 2
{{shipimage|image=[[Image:sathanas320x240.jpg]]|caption=The SJ Sathanas}}

==Overview==
The prowess of this class was tragically demonstrated when a Sathanas juggernaut destroyed the [[GTVA Colossus|GTVA ''Colossus'']] in the [[Capella]] system. The only apparent weakness of the Shivan juggernaut is that the massive beam cannons are concentrated at the bow. Aside from a comparatively diminuative anti-warship beam cannon at the stern, the other flanks of the massive warship are covered only by point-defense weapons. However, a Sathanas is still more than able to defend itself and project offensive power via the many hundreds of fighters and bombers it carries in its cavernous hangar. Thus, stopping a juggernaut is almost impossible. Even the "expedient" of disabling the massive warship is hardly worth considering, due to the numerous redundant engines found on the hull. In essence, any attack on a ''Sathanas''-class juggernaut can be considered almost suicidal. Only the ''Colossus'' demonstrated enough firepower to take on a Sathanas.

Its prefix designation, SJ, stands for "Shivan Juggernaut."

===History===
The first combat appearance of a Shivan Juggernaut was in the nebula theater, beyond the first [[Knossos]] portal in [[Gamma Draconis]], when the warship destroyed a Vasudan task force assaulting a Shivan gasmining operation. The GTVA immediately began to withdraw from the nebula, though not before sending a pilot in the new [[GVF Ptah|''Ptah'']]-class stealth fighter to scan the vessel. Based on this information, the Alliance launched a targetted bombing mission to eliminate several of the forward beam cannons (there is no canon consensus concerning exactly how many were destroyed, but at least two were taken out) in the Gamma Draconis system, and the [[GTVA Colossus|GTVA ''Colossus'']] engaged and destroyed the weakened juggernaut after it jumped to the Capella system.

After that victory, the GTVA were confident they could eliminate any threats the Shivans could present, and returned to the nebula with the objective of locating and capturing [[Admiral Aken Bosch]]. However, that goal failed to be achieved as GTVA forces discovered that multiple ''Sathanas''-class juggernauts were en route to GTVA space. Gamma Draconis was quickly overrun by the swift advance of the juggernaut fleet, which shortly entered Capella. In a desperate gamble, the GTVA fleet held the Shivans at bay while civilians were evacuated to [[Epsilon Pegasi]] and [[Vega]]. During the closing stages of the battle, the GTVA ''Colossus'' was destroyed in Capella by a Shivan juggernaut while providing a diversion for the [[GTD Bastion|GTD ''Bastion'']], which was tasked with collapsing the jump corridor to Epsilon Pegasi. In a final startling turn of events, the Shivan juggernauts instigated the super-nova of the Capella star as the jump corridor to Vega was destroyed.

===Conclusion===
The Shivan juggernaut fleet is the single, most serious threat to the survival of the Terran and Vasudan species. The GTVA barely managed to stop one Sathanas, and even then it was with a warship that took two decades and enormous amounts of resources to construct. An encounter with any more Shivan juggernauts will only be able to be stopped with extreme difficulty. All technical data concerning ''Sathanas''-class juggernauts has been classified Level Upsilon.

----

{{FS12_Ships}}

==Description:==

===FS2 Tech Room Description===
Very little is known about the SJ Sathanas class. This juggernaut seems comparable in strength to the GTVA Colossus. All intelligence concerning the Sathanas has been classified level Upsilon.

===Developer Notes===
None

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Juggernaut
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 25.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 1 000 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 5978 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Shivan Turret Laser]]
| 22
|- align="center"
| [[Standard Flak]]
| 11
|- align="center"
| [[Long Range Flak]]
| 2
|- align="center"
| [[GTM Piranha|Piranha]]
| 5
|- align="center"
| [[SAAA|Anti-Fighter Beam]]
| 8
|- align="center"
| [[LRed|Large Red Beam]]
| 1
|- align="center"
| [[BFRed|Very Big Red Beam]]
| 4
|}

==Notes==
===User-made campaigns===
This ships also appears in [[Inferno]], where it makes use of a subspace weapon

===Veteran Comments===
{{comment|''It would be the best to steer clear of the juggernaut, as it would be suicide to attack it without capital ship support. However, it is extremely vulnerable to attack from capital ships from the side and the rear, where there are little to no anti capital ship defences.''

''It is also vulnerable to fighters and bombers if they attack near enough to the weapons subsystems, making it impossible for the anti-fighter beams to reach.''

''This giant warship is curious, neither the [[GTVA Colossus|Colossus]] nor the Sathanas have very good anti-fighter defenses. A squadron of [[GTM Helios|Helios]] capable bombers can take out all of its main beam cannons, leaving it vulnerable to attack. If it wasn't for the "supercap" flag, the Sathanas in such a state would be vulnerable to attacks by destroyers.''

''The Sathanas, like most FS2 Shivan capital craft, has an attack-oriented design that makes use of the known Shivan superiority at subspace jumping (at least in capital craft) to deal devastating first-strike blows. If itself attacked, it has problems. It has a single other anti-capital beam, an LRed in a "stinger" posistion aft and below; this weapon is not sufficent to prevent the Sathanas from being flanked. The Sathanas' defenses against fightercraft assault are respectable, but as mentioned above poorly sited to defend against an attack on its main armament. (The Colossus is notably superior in this regard.) In a way the Sathanas is a microcosm of the Shivan war machine, which is dependant on continually being on the assault to keep its flaws from being exposed. On the defensive it can still deal out heavy blows, but ultimately it is not prepared for the role. It is worth noting that the only time ingame the Sathanas was actually attacked, by a Vasudan corvette in "A Monster in the Mist", it was unable to come to grips with its opponent. Even in "High Noon" the Sathanas was essentially on the offensive, in motion towards the statically positioned Colossus.''

''This is one bigass mother of a ship. However, its defensive capabilities against fighters and bombers are far below par, so you can easily see why I disagree with the first comment. A quick salvo of Helios missiles should take care of the four front beams. The only annoying thing one should be warned about this is the forward flak cannon constantly bombarding your ship. If you can get rid of that, the ship is easily fried into helpless cap-ship fodder. Given an endless amount of time, enough missiles, and enough patience, it's possible that a single fighter or bomber could take down this juggernaut, as the Shivans apparently weren't planning on engineering defenses into their cap-ship destroyer. Unless its forward beam turrets are intact, it's as harmless as a fly (although not easily as squashed). Just be warned not to sit in front of it as it jumps out.''

''This ship is sooo not to be trifled with. You have to make sure you take out its front beams before you do anything else or you and your fellow Terrans are screwed bigtime.''

''It is true that a Sathanas '''CAN''' be flanked by a smaller warship, but do not underestimate the strength of its rear-facing LRed. Without any fighters or bombers to disable it, even a [[GVD Hatshepsut|Hatshepsut-class]] destroyer may not be able to survive attacking it from behind. If that single turret is destroyed, however, it will change the outcome. Don't forget that in terms of plotline a sitting Sathanas isn't a good view: the ship should turn to face the opponent and the number of spacecraft housed in the hangar, supposed to be very high, should be enough to overwhelm GTVA bombers and warships without problems. Consider these factors when designing a strike against a Sathanas.''

I find that as long as you're nowhere near any flak cannons, staying low and close to the hull like you're walking on it is a method that can allow you to effectively neutralize every one of its turrets. Of course it'll take a while, since you're certainly not going to get your wingmen to follow you in your plan. The Sathanas in my opinion really only poses a threat to big ships. (A really, really big threat.)

''Get right behind the BFReds with some Helioses and Trebuchets, divert all power to shields, start pounding, and try to ignore the flak.''
}}

[[Category:Ship]]

SF Basilisk

2008-03-24T00:11:27Z

Kopachris: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|image=[[Image:basilisk320x240.jpg]]|caption=The SF Basilisk}}

==Description:==

===FS1 Tech Room Description===
The Basilisk seems to be a Shivan heavy attack fighter. It is not as maneuverable as other Shivan fighters, but it packs quite a punch, and it is very resistant to our weaponry. Most often they have been used in attacking our supply convoys and transports. 
Treat the Basilisk as a Class C threat.

===FS2 Tech Room Description===
The SF Basilisk is a Shivan heavy attack fighter. Slow but heavily armed and well-protected, the Basilisk targets slower-moving vessels, such as bombers, freighters, and gas miners. Their powerful lasers make them a danger to all such craft, so they must be engaged and destroyed as quickly as possible.

===Developer Notes===
None

===Name origin===
In European legends, a basilisk is a reptilian beast that can cause death by a single glance. it is referred to as the snake king and represented the royal power in the babylonian traditions. The basilisk was demonised by the bible, making it an unholy beast.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Heavy Attack
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 65.0 - 68.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 110.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 100
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 950
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 30 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 1'''
| style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
| style="width:240px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[Shivan Mega Laser]]
| [[Shivan Mega Laser]]
|- align="center"
| 2nd
| 2
| [[Shivan Heavy Laser]]
| [[Shivan Heavy Laser]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 1'''
| style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
| style="width:240px" |Standard Loadout
|- align="center"
| 1st
| 80
| [[GTM Phoenix V|Phoenix V]]
| [[GTM Trebuchet|Trebuchet]]
|- align="center"
| 2nd
| 80
| [[GTM Hornet|Hornet]]
| [[GTM Hornet|Hornet]]
|}

===Veteran Comments===
{{comment|''When escorting craft smaller than a cruiser, priority should go to destroying attacking Basilisks before smaller Shivan fighters. If allowed to reach their target, a wing of Basilisks will make one's escort list shorter very quickly.

However, the Basilisk is both slow and ungainly. Between its lack of manueverability and an afterburner that the AI seems to never use, the Basilisk resembles a heavily shielded target drone (that you should nevertheless refrain from going head-to-head with).

The Basilisk is infact, the most heavily shielded fighter in [[Portal:FreeSpace 1|FreeSpace 1]], that really doesn't matter, however, as you can practically destroy it with an [[GTW ML-16|ML-16]] or [[GTW Training Laser|Training Laser]], because of its horrible maneuverability and large target profile.''

''Skewer it with the Banshee. It may have thick shields, but the hull strength is extremely low. For escort missions, you should destroy these as a priority second only to Bombers, since their Hornet-style missiles can heavily damage targets.

''Ridiculously slow, weakly armored. More of a distraction then an actual threat. ''

''Despite that they are very slow, they ARE heavily shielded, more so in fact than any other fighter in the game. Once you punch through their shields, however, they're toast since their underlying hull is paper-thin. However, they are not to be ignored if you are protecting a transport, freighter or even light cruiser. It also has a smaller rotation time than the Tauret or indeed the Myrmidon.''

''Thankfully, one of the most common fighters you will find in-game. Don't bother using missiles on it unless you need to kill it in a pinch. But don't underestimate it. They are quite capable of ruining transports, freighters, and even cruisers.''

''I love this ship! Get a Herc with Banshees and Hornets in FS1, spear these ships, serve them on a silver platter, and watch your kill count go up. Nice large target, slow, no maneuverability, and the shields are easy to get through with the Banshee.''}}

[[Category:Ship]]

GVF Serapis

2008-03-24T00:07:34Z

Kopachris: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|image=[[image:serapis320x240.jpg]]|caption=The GVF Serapis}}

The '''GVF Serapis''' was the mainstay interceptor fighter for the Vasudan navy after its development following the [[Great War]].

==Description:==

===FS2 Tech Room Description===
Fast and highly maneuverable, the GVF Serapis is primarily used as a bomber interceptor. Its thin armor and weak shields give it a low survival rate in dogfights against more heavily armored fighters. Despite having only two primary and secondary weapon banks, the Serapis has been retrofitted to accommodate almost any loadout in the GTVA arsenal. Veteran Vasudan pilots love the Serapis for its agility and loadout options. Some Terran pilots who've been privileged enough to fly it claim to prefer it to any Terran fighter.

===Developer Notes===
None

===Name origin===
Serapis was a Hellenistic-Egyptian god. Unlike most Egyptian deities, Serapis was potrayed as all-human.

==Performance:==
===Statistics===
{{Ship Stats|Advanced Interceptor|Akheton Corporation|Excellent|75.0 - 78.0|135.0|Light|220|200|14}}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[GTW Prometheus R|Prometheus R]]
|- align="center"
| 2nd
| 2
| [[GTW Akheton SDG|Akheton SDG]]
|- align="center"
| colspan=3| Compatible Primaries
|-
| colspan=3| [[GTW Mekhu HL-7|Mekhu HL-7]], [[GTW Akheton SDG|Akheton SDG]], [[GTW Prometheus R|Prometheus R]], [[GTW Prometheus S|Prometheus S]], [[GTW Morning Star| Morning Star]], [[GTW Lamprey|Lamprey]], [[GTW Circe|Circe]], [[GTW Maxim|Maxim]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 60
| [[GTM Harpoon|Harpoon]]
|- align="center"
| 2nd
| 30
| [[GTM Harpoon|Harpoon]]
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=3| [[GTM MX-64|MX-64]], [[GTM EMP. Adv|Emp. Adv]], [[GTM Tempest|Tempest]], [[GTM Harpoon|Harpoon]], [[GTM Hornet|Hornet]], [[GTM Tornado|Tornado]], [[GTM TAG-B|TAG-B]]
|}

==Veteran Comments==
{{comment|
''The Serapis is deployed as if it were a space superiority fighter in the Vasudan missions of the Main Campaign, but don't let that fool you. This is in fact a civilian ultralight for airshows. While that sounds harsh, it is unfortunately rather true. A joy to simply fly thanks to its speed and manuverablity, the Serapis is also disturbingly fragile, at least as much FS1-era [[GTF Valkyrie]] if not more so. The Serapis has an extremely high attrition rate in combat: AI pilots drop like flies in it. Give them Taurets, Horuses, or Seths instead during the main campaign.''

''The Serapis is a light interceptor which was not designed to survive in prolonged battles. Those who liked flying the [[GVF Horus]] or the [[GVF Thoth]] will probably like this fighter as it is superior to its predecessors. The main strength of the Serapis is its weapon compatibility. A pilot who prefers intercepting fighters to doing heavy assault will most likely prefer this during the Vasudan missions. It is to be noted that most Terran interceptors have better combat performance though.''

''The only real reason you should choose this is for the fact that it is the only Vasudan fighter compatible with the Maxim. Its maneuverability and moderate speed makes it good for getting behind bombers and chalking them off, but its lack of armor and shielding make it a bad choice for all but the most skilled of players in engaging other fighters.''

''This fighter is useless. It has less shielding and actually goes '''slower''' than the Valkyrie of old. Its only saving grace is its ability to carry the Maxim and its extra missile bank (which is minuscule anyway). Always use the Tauret or Horus when you can, rather than this paper-thin pair of wings.''

''"Some Terran pilots who've been privileged enough to fly it claim to prefer it to any Terran fighter." This is because they're idiots. The Serapis is slower than the Horus, has weaker shields and armour, and is only marginally more manoueverable. It's only advantage is the extra missile capacity, but since you'll die before you can use them, this isn't much of an advantage. Whoever classed this as an "Advanced" interceptor is having a joke. And as for comparing it to Terran fighters...''

''The Horus is a far better interceptor than this thing. Intercept needs high speed, good manoeuvrability. While this is one of the most manoeuvrable fighters you will ever have access to in the game, it just doesn't have the speed to do intercept. One thing to note however, is that in the right hands, it is a surprisingly capable dog fighter. But it is extremely fragile, to the point that you may want to reroute some power to shields. You really can't take more than a few hits. But overall I find it much more like the Ulysses than anything else. Its a supreme dogfighter like it, but it cannot stand prolonged combat, even less so than the Ulysses. However, it does have a second secondary (Giving it more versatility and a total capacity more than twice the size), and it does have a Maxim, which is a bit odd, but allows it an option when dealing with warships, and makes it good for hunting down transports, freighters and miners.''

''The Serapis can fly, but it's made out of tracing paper; I've seen a video where the front quadrant of a Serapis — at full power, by the way — was completely taken down by just one hit from a Shivan laser mounted on the rear of a [[SC Rakshasa|Rakshasa]] (a second shot knocked the Serapis' hull integrity from 100% to 79%). It has a few advantages over the Horus, however, in that it can carry the Maxim, and that it lacks the inertia of the Horus while pitching. This is why I would rather use this ship for intercept than use the Horus.''

''Piece of crap. Flies well, but is taken down in just a couple shots.''
}}
[[Category:Ship]]

SF Dragon

2008-03-23T23:58:52Z

Kopachris: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|image=[[Image:dragon320x240.jpg]]|caption=The SF Dragon}}

The '''SF ''Dragon''''' is one of the most rarely seen of Shivan fighters. The Dragon is armed with five primary cannons, as well as a low-capacity secondary bank. Despite the small number of missiles it can carry it is very fast and maneuverable, as well as small, making it a very powerful adversary of any GTVA fighter. However the Shivans make limited use of the Dragon, deploying them in small numbers in most cases. But even one wing can cause serious trouble for any GTVA force.

The first Shivan fighter to have ever been captured by the Terrans and the Vasudans was a Dragon class designated [[Arjuna 1]]. Through the capture of this Shivan fighter, the joint Terran-Vasudan forces learned much about Shivan technology, especially fighter systems. Arjuna 1 was later used in a high-risk reconnaissance mission, shortly before the [[Destruction of Vasuda Prime]].

==Description:==
===FS1 Tech Room Description===
The Shivan Dragon is easily the most impressive fightercraft we have yet seen. Its maneuverability is unmatched, and it has quite a few other advantages, including a good top speed, powerful afterburners, and strong shields. It is the only Shivan fighter we have been able to study up close, and we have learned a great deal about Shivan engineering from it.
It seems that the Shivan shield systems are extremely strong, but their hulls are far weaker than our own. They also rely on primary weapons far more then secondaries, as evidenced by the Dragon's small capacity. 
The GTA considers the Dragon as a Class A threat.

===FS2 Tech Room Description===
The Shivan fighter class SF Dragon is a fast, extremely agile craft. Its twin lasers pack a deadly punch. The Dragon's weakness seems to be a thin hull. The trouble is that their speed and maneuverability make them extremely difficult to hit.

===Developer Notes===
None

===Name origin===
The Dragon's name derives from the mythical reptilian creature depicted in tales throughout the world.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Space Superiority (?)
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 75.0 - 90.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 150.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 100
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 700
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 16 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 1'''
| style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
| style="width:240px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[Shivan Heavy Laser]]
| [[Shivan Heavy Laser]]
|- align="center"
| 2nd
| 3
| [[Shivan Heavy Laser]]
| [[Shivan Heavy Laser]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 1'''
| style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
| style="width:240px" |Standard Loadout
|- align="center"
| 1st
| 20
| [[GTM Interceptor|Interceptor]]
| [[GTM Harpoon|Harpoon]]
|}

===Veteran Comments===
{{comment|''The Dragon is widely considered the best Shivan fighter ever (though my personal opinion leans towards the Mara in that regard). It is small, well-armed with lasers though deficent in secondary weaponry, quick, and insanely maneuverable. On higher difficulty levels the Dragon borders on unkillable, and even on lower ones it can be a surprisingly nasty opponent. If at all possible, destroy Dragons at range with missiles rather then getting into a dogfight.''

''It is to be noted that the version of the Dragon you fly in FS1's Playing Judas is much, much weaker then the genuine article.''

''Hell in space. A wing of them show up in the last mission of the main FS2 campaign. If you're flying an Ares, you're screwed.''

''A nasty piece of work, to be sure, that'll rip you to ribbons if you're not careful. Best policy? Harpoon 'em at range and try and keep your distance(!) as much as possible. Once in close contact, do not succumb to target fixation; the Dragon can keep you distracted from other dangers. The only real way to take one down at close range is to make exactly the right counter-turn at exactly the right time, then open fire. Try and get all your wingmates on one at a time; isolate and obliterate.''

''Extremely maneuverable. Target profile is extremely small and speed is rather high as well. Gunpoints for the second primary bank are oddly placed, but still manages to hit the target with little adjustment. The only real flaws are that Shivan primaries suck and that the sole secondary bank is miniscule.''

''There is no other fighter that I dread encountering more than the Dragon. It's fast, agile, and packs a rather nasty punch for a fighter that moves as quickly as it does. Unfortunately, the one you get to pilot in FS1 is not anything like the ones you have to fight, which is a pity, considering how much effort you put into capturing it.''

''The Dragon is, to be completely honest, that hard-to-reach itch. In a [[GTF Hercules Mark II|Herc II]] on Very Easy difficulty, even a single Dragon can be insanely difficult to hit. The Dragon would be pretty much like what the tech description of the [[GTF Loki|Loki]] says; very little firepower, but with immense speed and maneuverability to dissuade pursuers. You could get all your wingmen to try and destroy it, but that would be impossible unless they're flying ships with very good maneuverability and speed like the [[GVF Horus|Horus]] or [[GVF Serapis|Serapis]].''

''And this itch is best scratched by a friendly capship, such as a Deimos in the final mission and you are flying an Ares. Even if you are in a more maneuverable fighter like the Perseus, it can still be somewhat a waste of time to do so (even if you can kill it) so it may not be a bad idea to stay near the Lemnos''

Given that it is one of the few ships you fight that carries Heavy Lasers, I would hardly describe these as an "itch". Unless it's one of those really, really painful itches that feel like something sharp and hot is pinching your skin. . .

The SF Dragon is the fighter that would have ended the war the minute it started had the Shivans deployed it from the start. It has strong shields, yet it has relatively weak armor. The Dragon makes up for this by being crazy hard to hit and infuriating to disable in [[Enter the Dragon]]. I've always dealt with Dragons by hanging back and shooting them with Interceptors or Phoenix Vs.

''This fighter is hell in space. My advice, don't bother dealing with them, your wingmen can do it better. Even in the best fighter you can fly, the dragon is still faster and more maneuverable. It's a shame Terran Intelligence couldn't let us use its full extent in Playing Judas. As was said before, don't succumb to target fixation, especially in A Failure to Communicate. They're kinda like little gnats flying around your head biting you all the time.}}

[[Category:Ship]]

NTF Boadicea

2007-03-13T04:34:35Z

Kopachris: /* Veteran Comments */

The '''NTF ''Boadicea''''' was originally an asteroid in the [[Deneb]] system. During a depot raid, a wing from the [[53rd Hammerheads]] picked up an unusual signal and moved to investigate. Their signal turned out to be this half-breed of a shipyard and a really big rock. Shortly afterwards, the asteroid splintered, revealing it's deadly cargo: the [[NTF Iceni|NTF ''Iceni'']], a unique vessel constructed to the plans of the traitorous [[Famous Persons|Admiral Bosch]] within the asteroid. Shortly thereafter, the ''Iceni'' jumped out and was able to escape the Deneb, easily escaping an unusually poor attempt at blockade.

The Boadicea is named after the queen of a german tribe called the Iceni, She led a enormous army, and was beaten by the Romans (wich had a much smaller force, but were organised).

{{FS12_Ships}}
{{shipimage|image=[[image:boadicea320x240.jpg]]|caption=The NTF Boadicea}}

==Description:==

===FS2 Tech Room Description===
Hidden NTF asteroid base.

===Developer Notes===
None

===Veteran Comments===
''It's an [[NTF Iceni|Iceni]] with destroyable rocks all over it, not much more to say... has a good amount of [[Terran Turret]]s I suppose.''

'' Very, very ugly. ''

''Ugly maybe, but deadly if you set the turrets right. I've seen this thing own some destroyers easily... And it has a lot of missile turrets i think.''

''Useless piece of crud... except for that [[NTF Iceni|destroyer level corvette]] embedded in it'' 
''It looks like a city that a giant crapped on and threw into space.''

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Asteroid Base
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 180 000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 1568 m
|}

===Armaments===

====With NTF ''Iceni''====
*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Turret]]
| 21
|- align="center"
| [[Terran Huge Turret]]
| 7
|- align="center"
| [[Standard Flak]]
| 2
|- align="center"
| [[GTM Piranha|Piranha]]
| 4
|- align="center"
| [[MX-52]]
| 3
|- align="center"
| [[BGreen|Big Green Beam]]
| 3
|}

====Without NTF ''Iceni''====
*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''Freespace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Turret]]
| 12
|- align="center"
| [[GTM Piranha|Piranha]]
| 2
|- align="center"
| [[MX-52]]
| 1
|}

[[Category:Unique ships|Boadicea]]
[[Category:Ship]]

SF Mara (Terrans)

2007-03-13T04:31:06Z

Kopachris: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|image=[[Image:Mara320x240.jpg]]|caption=The SF Mara (Terrans)}}

The '''SF ''Mara''''' was an advanced starfighter used by the [[Shivans]] during their [[Second Shivan Incursion|invasion]] of the galaxy in 2367. It is known that the SF ''Mara'' was one of the fighter classes that were spotted and designated after the conclusion of the [[The Great War|Great War]]. Terran operatives acquired four of these fighters and retrofitted them to Terran standards. Then, [[Special Operations Command]] launched a mission beneath the second [[Knossos]] device to recon the area.

==Description:==

===FS2 Tech Room Description===
N/A

===Developer Notes===
None

===Veteran Comments===
Easily one of the best fighters, if not the best. A simple joy to fly. Only weak point is the 4 gun mounts, but even then the other stats are so rediculous you can wreak havoc. 
''Superior to the Shivan original [[SF Mara|Mara]] just like Snipes says.'' 
''Oh... My... God... This is THE BEST FIGHTER IN THE GAME. IF YOU SAY OTHERWISE, I WILL SEND A SQUADRON OF THEM TO BOMB YOUR HOUSE INTO DUST!'' 
''As odd as it sounds, [[Into the Lion's Den]] is actually somewhat unkind to the Terran Mara, as you spend most of your time scrambling between widely spaced targets and don't really get the chance to stop and dogfight it much. Still, as can be seen from the above commentary, even a tiny taste of the SF Mara (Terrans) capablities is enough to make most people fall in love.''
 
''Best. Damn. Ship. Ever. Too bad Volition didn't make a mission where you could exploit it to it's fullest extent.''

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Advanced Space Superiority
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Triton Dynamics
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| Excellent
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 75.0 - N/A mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 135.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| Very Heavy
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 475
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 700
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| ~ 16 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[GTW UD-8 Kayser|UD-8 Kayser]]
|- align="center"
| 2nd
| 2
| [[GTW UD-8 Kayser|UD-8 Kayser]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 420
| [[GTM Tempest|Tempest]]
|- align="center"
| 2nd
| 420
| [[GTM Tempest|Tempest]]
|}

[[Category:Ship]]

GTM Harbinger

2007-03-12T05:38:07Z

Kopachris: /* Veteran Comments */

'''GTM-N1 Harbinger Bomb'''

{{FS12_Weapons}}
{{shipimage|image=[[Image:Harbinger_320x240.jpg]]|caption=The GTM-N1 Harbinger Bomb}}

==Tech Room Data==
Fusion bomb surrounded by 3 salted fission bombs - propulsion unit is a half-size version of a regulation GTA fighter thruster (Class II) - given the weight of the payloads, the missile is slow despite the power of the thruster - as the Harbinger is exceptionally large, GTA bombers are limited to carrying 6 of these weapons at any given time - the resultant shock wave from this weapon is potentially deadly, due to the size of the payloads (5000 Mt in total) - use near allied installations or allied ship groupings is strongly discouraged by the GTA - most effective when used in preemptive defensive strike against non-military installations. 
The Harbinger is our best chance of destroying the Lucifer.
==Veteran Comments==
''The big bomb of Freespace 1, the Harbinger can take out anything and everything in the game. Like all space-bombs you need to get in really close, nearly running into your target at maximum speed to ensure the bomb gets where it's going: interceptors and blob turrets are adept at destroying bombs before they reach their targets.''
 
''Insanely high subsystem damage value. A single Harbinger should be sufficent to destroy any subsystem on any ship in the game.''
 
''Theoretically, the Tsunami should be stronger because it has a matter-antimatter warhead, so all the matter is turned to energy, thus resulting in a bigger boom. With fission and fusion, there's leftover matter that's not turned into energy.''

==Performance==
===Statistics===

{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 1500 m
|-
| '''Rate of Fire'''
| 1 / 30 s
|-
| '''Velocity'''
| 50 mps
|-
| '''Damage'''
| 3200
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Minimal/None
|-
| Against Subsystems
| Excellent '''''(x 16)'''''
|-
| '''Shockwave Radius'''
| 100 m / 250 m
|-
| '''Homing System'''
| Aspect Seeking
|-
| Minimum Lock Time
| 7.0 s
|-
| Turn Rate
| 1.5 s
|}

===Statistics - Harbinger#End===

{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 1800 m
|-
| '''Rate of Fire'''
| 1 / 10 s
|-
| '''Velocity'''
| 90 mps
|-
| '''Damage'''
| 3200
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Minimal/None
|-
| Against Subsystems
| Excellent '''''(x 20)'''''
|-
| '''Shockwave Radius'''
| 1 m / 20 m
|-
| '''Homing System'''
| Aspect Seeking
|-
| Minimum Lock Time
| 3.0 s
|-
| Turn Rate
| 1.5 s
|}

===Notes===
*Weapon is capable of easily damaging [[Weapons.tbl#Weapon Flags|(Huge)]] even larger vessels.
*Weapon can be shot down [[Weapons.tbl#Weapon Flags|(Bomb)]]
*Weapon must be locked onto the target in order to be fired [[Weapons.tbl#Weapon Flags|(No Dumbfire)]]

[[Category:Weapon]]

GTM Synaptic

2007-03-12T05:20:34Z

Kopachris: /* Veteran Comments */

'''GTM-1 Synaptic Bomb'''

{{FS12_Weapons}}
{{shipimage|image=[[Image:Synaptic_320x240.jpg]]|caption=The GTM-1 Synaptic Bomb}}

==Tech Room Data==
Missile propulsion unit carrying several small intelligent "bomblets" - when distance to target is less than 100 m or when time to impact is less than 2 sec., bomblets direct missile to the most vulnerable part of the ship of those parts of the ship facing the missile - bomblets then separate from missile propulsion unit and form a sphere - inertia continues to carry bomblets in the direction of the target - the missile propulsion unit continues to advance toward the target - when the missile hits the target or 1.5 sec. after the missile should have hit the target, the bomblets explode - the spherical shape of the formation of the bomblets helps to ensure a fairly even level of damage across a sensitive area on the target - the spherical shape also ensures that the target will not be able to effectively maneuver away from the blast, thus "pinning" the target to a specific area in space - can also act as dumbfire - medium payload per bomblet (15 Kt) - very small payload for missile (2 Kt). 

Nicknamed the "Earthshaker" by the bomber pilots who tested this, it is a bombers best defense against fighters. The Synaptic Bomb can do a lot of damage to a lot of ships at one time.
==Veteran Comments==
''Generally the shockwave seems to wash over enemy interceptors' sheilds, and the bomblets rarely hit their marks, so load up on [[GTM Hornet]]s or [[GTM Interceptor]]s instead, or just put in another bank of bombs.'' 
''I don't like it. The bomblets hardly ever hit their target, and that's pretty much the whole purpose of it.''

==Performance==
===Statistics===

{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 225 m
|-
| '''Rate of Fire'''
| 1 / 5 s
|-
| '''Velocity'''
| 90 mps
|-
| '''Damage'''
| 60
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Good
|-
| Against Subsystems
| Excellent
|-
| '''Shockwave Radius'''
| 50m / 100 m
|-
| '''Homing System'''
| None
|}

===Notes===
*Weapon can be shot down [[Weapons.tbl#Weapon Flags|(Bomb)]]
*Weapon [[Weapons.tbl#Weapon Flags|spawns]] 15 smaller warheads

====Spawned warheads====
{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 1050 m
|-
| '''Velocity'''
| 175 mps
|-
| '''Damage'''
| 35
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Excellent
|-
| Against Subsystems
| Average
|-
| '''Shockwave Radius'''
| None
|-
| '''Homing System'''
| Heat Seeking
|-
| View Cone
| 180 degrees
|-
| Turn Rate
| 1.5 s
|}

[[Category:Weapon]]

GTM Hornet

2007-03-12T05:17:30Z

Kopachris: /* Veteran Comments */

The '''GTM-4 Hornet''' is a Great War-era early swarming missile. This missile rack launches four warheads per volley that each follow individual, slightly erratic paths to the target. This gives them a better chance of intercepting the target and increases their resistence to countermeasures. Though the Hornet has since been eclipsed by other missiles, most especially its direct descendant the [[GTM Tornado]], vast quantities of Hornets remain available due to overzealous production.
 
While the Hornet will lock and track a figher-sized target, in general it lacks the speed and agility to succesfully engage anything except bombers or the slower assault fighters. Modern superiority fighters and interceptors are simply too maneuverable to be caught by this aging design.
 
Where the Hornet still performs well is in the role of heavy assault. In dual fire mode, 8 missiles are launched in each rapidly-loaded volley. Light warships and slow ships with minimal armor are quickly shredded by the blizzard of incoming warheads. Unlike the Tornado, the Hornet arms its explosives immediately upon exiting its launch tube, so if a target is big enough you can even launch a salvo without gaining lock on it. Assault fighters such as the Hercules Mark II can carry large numbers of these missiles, and a wing of Hornet-equipped assault fighters spell certain doom for any light ship that crosses their path.

{{FS12_Weapons}}
{{shipimage|image=[[Image:Hornet_320x240.jpg]]|caption=The GTM-4 Hornet}}

==FS1 Tech Room Data==
Infrared and ultraviolet tracking - designed to fire in small groups of 4 missiles per burst - light medium payload per missile (12 Kt) - semi-intelligent on-board tracking - single-pass kill probability will not exceed 60% on average -designed as an offensive version of the Fury. 
As a "swarm" based weapon, this missile can take out an unshielded fighter without any difficulty. It's four missile system almost guarantees one or two hits, and its speed is quite amazing. Twice as powerful against naked hulls.

==FS2 Tech Room Data==
The GTM-4 Hornet was showing its age even toward the end of the Great War, but it was cheap to manufacture. As a result, war-time production of the Hornet ran full-tilt at factories in eight star systems right up to the end of the war. After hostilities ceased, the GTVA found itself with an inventory of 2.6 million Hornet missiles. This stockpile has been spread among all GTVA battle groups, with each receiving at least 100,000 Hornets. This aspect-seeking missile still delivers a devastating four-missile punch, which makes it a consistent favorite of many pilots.

==Veteran Comments==
''The Hornet is perfectly usable in a dogfight. You just need to understand how it works. The Hornet flies a lag-pursuit curve to the target, rather then a lead-pursuit like most FS missiles. It does its best work fired in a head-on pass or from within a 45" degree cone from the target's six-o'clock position. Do not expect high-deflection Hornet shots to hit anything. Also in FS2 do not expect wonders from the Hornet, as its FS1 design lacks the power against shields most FS2 missiles have.''
 
''I usually prefer either the [[GTM Tempest]] or the [[GTM Fury]] (depending on the generation) to this missile, as they pack more damage per missile bank. I generally use the Hornet to bombard tough cruisers like the [[GVC Mentu]] or the [[GTC Aeolus]], or on any freighters or transports in the area. The Hornet has several advantages over its dumbfire cousins, including range and accuracy.'' 
''Choose the Tornado over it as soon as you get it. It may take more space, but Tornadoes do more damage and have better homing capabilities.'' 
''In FS1, this is a solid weapon with a set of drawbacks that keep it from dominating. It outdamages the Interceptor by 50 base points (100 base points on double fire mode), provided all 4 missiles strike their target, but is considerbly slower... and thus, does not track as well. Beccause of this, it is less useful in a dogfight, but can still be useful in that capacity when combined with the Flail. Furthermore, the Hornet is launched in multiples of 4 (8 on double), and will provide more threats for the evading pilot to deal with. 
''The best use of the Hornet lies in its "Bombing" capabilities. The Hornet inflicts up to 400 base points per salvo, which can be repeated every second. It won't take long to overtake the capabilities of a standard bomb... and futhermore, Hornets cannot be intercepted like Harbingers or Tsunamis can. Add in a few squadrons wielding these, and even the biggest capital ships will be shredded in seconds. 
''One other drawback of the Hornet is that it does next to null against Subsytems. You'll want the Interceptor for that job, if you aren't going to employ Stilletos.''
 
''This was my FS1 secondary of choice. I get my ship filled to the brim with Hornets, set them on dual-fire, and watch the fighters die. In FS2, I'd recommend either this or the Tornado. The Tornado is more powerful, but takes up more space, and the Hornet takes up less space, but is also less powerful. All in all, it's a pretty good dogfight weapon.''

==Performance==
===Statistics===

{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 1330 m
|-
| '''Rate of Fire'''
| 1 / 2 s
|-
| '''Velocity'''
| 190 mps
|-
| '''Damage'''
| 50
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Average
|-
| Against Subsystems
| Minimal
|-
| '''Shockwave Radius'''
| 10 m / 20 m
|-
| '''Homing System'''
| Aspect Seeking
|-
| Minimum Lock Time
| 3.0 s
|-
| Turn Rate
| 1.15 s
|}

===Statistics - Hornet#Weak===

{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 1140 m
|-
| '''Rate of Fire'''
| 1 / 2 s
|-
| '''Velocity'''
| 190 mps
|-
| '''Damage'''
| 15
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Very Poor
|-
| Against Subsystems
| Poor
|-
| '''Shockwave Radius'''
| None (FS1); 20 / 40 m (FS2)
|-
| '''Homing System'''
| Aspect Seeking
|-
| Minimum Lock Time
| 3.0 s
|-
| Turn Rate
| 1.6 s
|}

===Statistics - Hornet D===

{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 1330 m
|-
| '''Rate of Fire'''
| 1 / 2 s
|-
| '''Velocity'''
| 190 mps
|-
| '''Damage'''
| 36
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Average
|-
| Against Subsystems
| Minimal
|-
| '''Shockwave Radius'''
| 10 m / 20 m
|-
| '''Homing System'''
| Aspect Seeking
|-
| Minimum Lock Time
| 3.0 s
|-
| Turn Rate
| 1.15 s
|}

===Notes===
*Missile launches in [[Weapons.tbl#$Swarm:|swarms]] of 4 missiles.

[[Category:Weapon]]

GTW Banshee

2007-03-12T05:13:35Z

Kopachris: /* Veteran Comments */

'''GTW-7 Banshee'''

{{FS12_Weapons}}
{{shipimage|image=[[Image:Banshee_320x240.jpg]]|caption=The GTW-7 Banshee}}

==Tech Room Data==
An electromagnetic weapon - sends rapid pulses of exceptionally strong electromagnetic energy resulting in a 1.63 x 105 J blast that forces its way through any known shield technology and produces a dramatic shearing effect which quickly destroys the target ship's materials - named for the fact that in an atmosphere, the pulse creates an atmospheric disturbance similar to a quasi-human scream at 140 dB - uses up a tremendous amount of available ship energy - already, it is has been used by many GTA fighter aces and test pilots as a coup de grace, although such a use for this massively powerful offensive weapon is officially viewed as poor sportsmanship by the GTA. 
The GTW-7's impressive anti-shielding capabilities make it the weapon of choice against the Shivans. The main limitation of this weapon is low weapons compatibility. It can only be fitted on a GTF Valkyrie or a GTF Hercules.

==Veteran Comments==
''The Banshee's higher energy requirements and lower hull damage are, in general, not worth the added shield-stripping punch when compared to the Prometheus. At the very least the Banshee requires being paired with a more powerful antihull cannon.'' 
''The only primary weapon with an actual value matched to it. Should be fun for those who want to calculate weapon powers.''
 
''The Banshee is usefull for Shivan vessels with high sheild to armor ratios, best when coupled with hull damaging weapons- either the [[GTW Avenger]] or the [[GTW Prometheus]], or even the [[GTM Fury]].''
 
''The addition of the Banshee to a fighter greatly increases its destructive rate against other fighter craft. The energy use is quite a bit higher than other weapons, but it's nothing you can't alleviate with good energy management. A Banshee paired with a Prometheus is probably the most powerful and versatile weapon combination in FS1. You'll also find that, in a pinch, the Banshee isn't *that* bad against hulls on its own.'' 
''A Hercules with 2 banks of Banshees was my configuration fo choice for most missions. I could take down almost any Shivan fighter or bomber (with the exception of the Dragon) in a few shots.''

==Performance==
===Statistics===
{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 975 m
|-
| '''Rate of Fire'''
| 2.5 / s
|-
| '''Velocity'''
| 650 mps
|-
| '''Damage'''
| 31
|-
| Against Hullplating
| Average
|-
| Against Shields
| Excellent
|-
| Against Subsystems
| Poor
|}

===Notes===

[[Category:Weapon]]

GVF Serapis

2007-03-12T05:10:08Z

Kopachris: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|image=[[image:serapis320x240.jpg]]|caption=The GVF Serapis}}

The '''GVF Serapis''' was the mainstay interceptor fighter for the Vasudan navy after its development following the [[Great War]].

==Description:==

===FS2 Tech Room Description===
Fast and highly maneuverable, the GVF Serapis is primarily used as a bomber interceptor. Its thin armor and weak shields give it a low survival rate in dogfights against more heavily armored fighters. Despite having only two primary and secondary weapon banks, the Serapis has been retrofitted to accommodate almost any loadout in the GTVA arsenal. Veteran Vasudan pilots love the Serapis for its agility and loadout options. Some Terran pilots who've been privileged enough to fly it claim to prefer it to any Terran fighter.

===Developer Notes===
None

===Veteran Comments===
''The Serapis is classed as (and perhaps worse, deployed as if it were) a space superiority fighter, but don't let that fool you. This is in fact a civilian ultralight for airshows. While that sounds harsh, it is unfortunately rather true. A joy to simply fly thanks to its speed and manuverablity, the Serapis is also disturbingly fragile, at least as much so as the FS1-era [[GTF Valkyrie]] if not more so. The Serapis has an extremely high attrition rate in combat.'' 
''The Serapis is a light interceptor which was not designed to survive in prolonged battles. Those who liked flying the [[GVF Horus]] or the [[GVF Thoth]] will probably like this fighter as it is superior to its predecessors. The main strength of the Serapis is its weapon compatibility. A pilot who prefers intercepting fighters to doing heavy assault will most likely prefer this during the Vasudan missions.'' 
''It is to be noted that most Terran interceptors have better combat performance.'' 
''The only real reason you should choose this is for the fact that it is the only Vasudan fighter compatible with the Maxim. Its maneuverability and moderate speed makes it good for getting behind bombers and chalking them off, but its lack of armor and shielding make it a bad choice for all but the most skilled of players in engaging other fighters.'' 
''The hull is so weak that I had to edit it's table to avoid being killed within the first 5 minutes of combat. I only recommend it for it's speed, maneuverability, and the fact that it can carry the Maxim.''

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Advanced Interceptor
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Akheton Corporation
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| Excellent
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 75.0 - 78.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 135.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| Light
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 220
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 200
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 14 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[GTW Prometheus R|Prometheus R]]
|- align="center"
| 2nd
| 2
| [[GTW Akheton SDG|Akheton SDG]]
|- align="center"
| colspan=3| Compatible Primaries
|-
| colspan=3| [[GTW Mekhu HL-7|Mekhu HL-7]], [[GTW Akheton SDG|Akheton SDG]], [[GTW Prometheus R|Prometheus R]], [[GTW Prometheus S|Prometheus S]], [[GTW Morning Star| Morning Star]], [[GTW Lamprey|Lamprey]], [[GTW Circe|Circe]], [[GTW Maxim|Maxim]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 60
| [[GTM Harpoon|Harpoon]]
|- align="center"
| 2nd
| 30
| [[GTM Harpoon|Harpoon]]
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=3| [[GTM MX-64|MX-64]], [[GTM EMP. Adv|Emp. Adv]], [[GTM Tempest|Tempest]], [[GTM Harpoon|Harpoon]], [[GTM Hornet|Hornet]], [[GTM Tornado|Tornado]], [[GTM TAG-B|TAG-B]]
|}

[[Category:Ship]]

SF Mara (Terrans)

2007-03-12T05:07:30Z

Kopachris: /* Veteran Comments */

{{FS12_Ships}}
{{shipimage|image=[[Image:Mara320x240.jpg]]|caption=The SF Mara (Terrans)}}

The '''SF ''Mara''''' was an advanced starfighter used by the [[Shivans]] during their [[Second Shivan Incursion|invasion]] of the galaxy in 2367. It is known that the SF ''Mara'' was one of the fighter classes that were spotted and designated after the conclusion of the [[The Great War|Great War]]. Terran operatives acquired four of these fighters and retrofitted them to Terran standards. Then, [[Special Operations Command]] launched a mission beneath the second [[Knossos]] device to recon the area.

==Description:==

===FS2 Tech Room Description===
N/A

===Developer Notes===
None

===Veteran Comments===
Easily one of the best fighters, if not the best. A simple joy to fly. Only weak point is the 4 gun mounts, but even then the other stats are so rediculous you can wreak havoc. 
''Superior to the Shivan original [[SF Mara|Mara]] just like Snipes says.'' 
''Oh... My... God... This is THE BEST FIGHTER IN THE GAME. IF YOU SAY OTHERWISE, I WILL SEND A SQUADRON OF THEM TO BOMB YOUR HOUSE INTO DUST!'' 
''As odd as it sounds, [[Into the Lion's Den]] is actually somewhat unkind to the Terran Mara, as you spend most of your time scrambling between widely spaced targets and don't really get the chance to stop and dogfight it much. Still, as can be seen from the above commentary, even a tiny taste of the SF Mara (Terrans) capablities is enough to make most people fall in love.''
 
''Very fun. If the Mac version of FS2_open included FRED2, I would make a mission that would let people use the Mara's full capabilities.''

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Advanced Space Superiority
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Triton Dynamics
|-
| '''[[Technical_Terms_and_Definitions#Manuverablity|Manuverability]]'''
| Excellent
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 75.0 - N/A mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 135.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| Very Heavy
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 475
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 700
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| ~ 16 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 2
| [[GTW UD-8 Kayser|UD-8 Kayser]]
|- align="center"
| 2nd
| 2
| [[GTW UD-8 Kayser|UD-8 Kayser]]
|}
*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Freespace 2'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 420
| [[GTM Tempest|Tempest]]
|- align="center"
| 2nd
| 420
| [[GTM Tempest|Tempest]]
|}

[[Category:Ship]]

GTM EMP Adv.

2007-03-12T05:05:20Z

Kopachris: /* Veteran Comments */

'''GTM-14 EM Pulse Adv.'''

{{FS12_Weapons}}
{{shipimage|image=[[Image:EMP_Adv_320x240.jpg]]|caption=The GTM-14 EM Pulse Adv.}}

==Tech Room Data==
The GTM-14 Electromagnetic Pulse Advanced warhead interferes with the electronics systems of vessels caught within its blast radius. This renders the affected ships unable to track targets, manage communications, or gain aspect missile lock. Tactically, the GTM-14 is a very effective anti-bomber weapon, as it also temporarily shuts down the guidance and propulsion systems of warheads in flight. This advanced version of the standard EM Pulse missile disrupts subsystems at a deeper circuitry level, resulting in a longer-lasting effect.

==Veteran Comments==
''If you're trying to get aspect lock on something, or even just trying to keep your bearings, this missile is evil incarnate. The EMP scrambling effect causes your target to change randomly, and the missile includes a small shockwave effect to knock you around and make sure you're not quite certain what direction you're pointed in.''

''The main problem with this weapon is that it's a double edged sword, if your too close to your enemy, your sensors get screwed up to. The solution: use this weapon at its maximum effective range.''

''Has totally no effect on AI targets.''

''Does little damage, but has the "big damage" flag, allowing you to destroy corvettes and destroyers with it if you're willing to invest a not-inconsiderable amount of time. Only time this is actually worthwhile is for a perfectionist in Proving Grounds during the FS2 main campaign.'' 
''Even after it seemed like everything was fine, I still got some residual effects every now and then. Not the HUD flickering, but I did get some random target changes.

==Performance==
===Statistics===

{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 1375 m
|-
| '''Rate of Fire'''
| 1 / 2 s
|-
| '''Velocity'''
| 275 mps
|-
| '''Damage'''
| 45
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Good
|-
| Against Subsystems
| Average
|-
| '''Shockwave Radius'''
| 80 m / 300 m
|-
| '''Homing System'''
| Aspect Seeking
|-
| Minimum Lock Time
| 2.0 s
|-
| Turn Rate
| 1.0 s
|}

===Notes===
*Causes [[Weapons.tbl#"EMP"|EMP]] within it's shockwave radius.

[[Category:Weapon]]

BFRed

2007-03-12T05:03:01Z

Kopachris: /* Veteran Comments */

'''Very Large Red Beam''' is a beam used by the [[Shivans]] in the [[Portal:Freespace 2|Freespace 2]]

{{FS12_Weapons}}
==Description==
Shivan anti-capital ship beam weapon mounted on [[SJ Sathanas]]

==Veteran Comments==
''This is the undisputed king of all beam cannons in Freespace 2, beating out the [[MjolnirBeam]] and [[BFGreen]]. Four of these cannons easily destroy a [[GTD Hecate]] in a single shot ([[Bearbaiting]]).'' 
''Really fun to play with when using cheats. If you force both primaries to this, you can take down an SJ Sathanas in a couple of shots.

==Performance==
===Statistics===
{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 7400 m
|-
| '''Rate of Fire'''
| 10 s
|-
| '''Velocity'''
| Instant
|-
| '''Damage''' per second
| 11 550
|-
| '''Damage''' per pulse
| 80 850
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Excellent
|-
| Against Subsystems
| Excellent
|}

===Notes===

[[Category:Weapon]]

GTM TAG-A

2007-03-12T05:01:20Z

Kopachris: /* Veteran Comments */

'''GTI TAG-A Missile'''

{{FS12_Weapons}}
{{shipimage|image=[[Image:TAG_A_320x240.jpg]]|caption=The GTI TAG-A Missile}}

==Tech Room Data==
The TAG-A missile was conceived during the GTVI's top-secret stealth technology research projects. The missile was manufactured and swiftly pressed into service as a means of counteracting the sensor-disrupting effects of the recently discovered Knossos nebula. Upon impact with a hard surface, the TAG missile adheres and activates a small, short-lived electronic beacon. This beacon is powered by a small fuel cell with a usable lifetime of several seconds. During this time, it broadcasts location and targeting information to all friendly ships within range.
==Veteran Comments==
''The TAG weapons seem ineffective in anything other than the properly [[FRED]]ed mission, the only one in the [[Portal:Freespace 2|Freespace 2]] campagin (as far as I know) is [[A Game of TAG]], beyond that single mission, I don't think they really have any use.'' 
''If this was used by warships instead of fighters, and was fired in swarms and an ULTRA beam followed, I would be very wary of this. However, it is not, and therefore I shall scorn it to death.'' 
''To me, the TAG weapons are the most useless weapons in the whole game. In [[A Game of TAG]], I used my TAG-As all the time and the cruisers that were supposed to be helping didn't do anything except complain about "If I don't TAG it, they can't kill it".

==Performance==
===Statistics===

{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 2000 m
|-
| '''Rate of Fire'''
| 1 / 3 s
|-
| '''Velocity'''
| 400 mps
|-
| '''Damage'''
| 1
|-
| Against Hullplating
| ??
|-
| Against Shields
| ??
|-
| Against Subsystems
| ??
|-
| '''Shockwave Radius'''
| 10 m / 30 m
|-
| '''Homing System'''
| None
|}

===Notes===
*[[Weapons.tbl#$TAG:|TAGs]] the target (level-2). Effect lasts for 11 s

[[Category:Weapon]]

Standard Flak

2007-03-12T04:57:01Z

Kopachris: /* Veteran Comments */

'''Standard Flak''' is a defensive weapon used in [[Portal:Freespace 2|FreeSpace 2]]

{{FS12_Weapons}}
==Description==
Commonly used anti-fighter weapon

==Veteran Comments==
''The meat-and-potato point defense weapon in [[Portal:Freespace 2|Freespace 2]] it is used by every race and virtually every warship ([[GVC Aten]] doesn't count), and some non-warships ([[GTFr Triton]]) the [[GTC Aeolus]] actually makes most of its warship kills with flak rather than its weak [[SGreen]].'' 
'' Flak Turrets are more of a deterrent weapon, although they are still one of the more effective AA weapons in the game. '' 
''Flak is a very deadly weapon, the [[GTC Aeolus]] is proof of this.'' 
''Flak is primarily a danger to a fighter craft with a breached shield quadrant, ANY breached shield quadrant, even if it's on the other side of the fighter from the flak gun. Pay close attention to your shields and equalize their strength often if under flak fire.''
'' 
''As said above, if you have any breached quadrant, you're going to die soon. When you have to destroy the first Sathanas's beam turrets, you should pipe more power into the shields to avoid being killed by the flak. (If you go up close like I did.)''

==Performance==
===Statistics===
{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 1050 m
|-
| '''Rate of Fire'''
| 6.67 / s
|-
| '''Velocity'''
| 700 mps
|-
| '''Damage'''
| 30
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Excellent
|-
| Against Subsystems
| Poor
|-
| '''Shockwave Radius'''
| 20 m / 30 m
|}

===Notes===

[[Category:Weapon]]