FreeSpace Wiki - User contributions [en]

Weapons.tbl

2023-11-08T23:03:34Z

AdmiralRalwood: Add "+Lock FOV:".

{{TableVersionGit|2023-10-25|bb47531c55b16bc9a965b446aecd431b6a7ef535}}
{{Tables}}
The '''weapons.tbl''' defines all of the weapon classes used in FSO.

This table is one of the [[Modular Tables]] and can be extended with xxx-wep.tbm

==Introduction==
The weapons.tbl is responsible for defining the behavior of the numerous weapon effects used in FSO, including the amount of damage dealt, the firing rate, and graphical effects.

This wiki page goes over all of the entries used exclusively in the weapons.tbl file. Hyperlinks to individual weapon creation/editing tutorials are provided when appropriate.

==Special Case Weapons==
===Beam Cannons===
'''REQUIRES:'''
*'''"beam"''' flag
*'''[[weapons.tbl#$BeamInfo:|$BeamInfo:]]'''

See also: [http://www.hard-light.net/wiki/index.php/Tutorial_-_Beam_Weapons Tutorial - Beam Weapons]

===Flak Guns===
'''REQUIRES:'''
*'''"flak"''' flag
*'''"particle spew"''' flag
*Must have inner and outer radius defined to have any effect.
*A '''.pof''' model must be defined ( usually '''Hornet.pof''' )
**Note: the model is not actually used... Instead, it uses [[Weapons.tbl#$Pspew:|particle spew]]. Trails may also be added.

==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. Two special characters can be used in the name: '''#''' and '''@'''. Their usage details are the very same than inside the [[Ships.tbl#.24Name:_2|$Name field from Ships.tbl]].
*Syntax: '''''String'''''

====+nocreate====
{{Table3610|
*In [[Modular Tables]] a name can be followed by the line '''+nocreate''' to prevent the game from creating an incomplete entry with very few valid fields. If the entry does not already exist (either in weapons.tbl or in earlier parsed *-wep.tbm files), the modular entry is skipped.}}

===+remove===
{{Table210|
*In [[Modular Tables]] a name can be followed by the line '''+remove''' to completely remove a previously parsed entry.}}

===$Alt Name:===
{{Table3611|
*An alternative name that can be referenced instead of $Name:
*Syntax: '''''String'''''}}

===$Subtype:===
{{Table3610|
Specifies the weapon 's subtype. Overrides the default subtype as specified by the #-section it is in (#Primary, #Secondary, #Beam Weapon, etc.).

{{Note|
:Since the weapon subtype is already specified by the #-section it is in, this option is not particularly useful when the weapon is inside a #Primary or #Secondary section. However, it may be used to specify the weapon slot it uses on fighters/bombers for weapons that are normally capship only (such as beam cannons).}}

*Syntax: '''''String'''''
*Valid Entries:
:Primary
:Secondary}}

===+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]]
*Must be followed by '''$end_multi_text'''

'''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]]
*Must be followed by '''$end_multi_text'''

'''Example'''

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

===$Turret Name:===
{{Table222|
*Renames a turret to this if this is the first weapon on a turret.
*Syntax: XSTR('''''"String"''''', -1)}}

===$Tech Model:===
{{Table3610|
*Defines model used in wing loadout screen for the weapon. 3D weapon models in the tech room have not yet been implemented.
*Syntax: '''''String.pof''''', model filename}}

====+Closeup_Pos:====
{{Table3613|
*How the model will show on the Loadout Screen. The position of the camera relative to the model center. Only valid if a tech model is defined
*Syntax: '''''Vector''''', three '''floats''', x, y and z values respectively}}

====+Closeup_Zoom:====
{{Table3613|
*How the model will show on the Loadout Screen. How far the camera's zoomed in, defines camera's FOV.
*Syntax: '''''Float''''', radians}}

===$Selection Effect:===
{{Table3613|
*Defines which selection effect to use when the -weapon_choice_3d commandline flag is enabled or no ani can be found for the selected weapon.
*Syntax: '''''String''''', either "FS1", or "Off". This defaults to the FS2 effect.
}}

===$HUD Image:===
{{Table3610|
*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:===
{{Table3610|
*Defines the LOD (Level-Of-Detail) of the model used in HUD targeting view
*Syntax: '''''Integer'''''}}

===$Detail Distance:===
{{Table3613|
*Defines the distance where the change between different Levels-Of-Details (LODs) occurs
*Take notice that these are base values. Model detail in Detail options, (within game press F2), applies a multiplier to these values. These multipliers are (from left to right): 1/8, 1/4, 1, 4, 8
*Optional. If not defined the game uses the formula ((radius * 20.0 + 20.0) * LOD)
*Syntax: '''''(Detail Distances)''''' , list of '''integers''' (same amount as LODs), distances from the model in meters
**Example: ''(0, 80, 300, 900)''}}

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

===$Submodel Rotation Speed:===
{{Table3610|
*Defines the rotation speed of the subobject, with the $gun_rotation property defined, in the external weapon model.
*Syntax: '''''Float'''''
*Note: weapon fire will be delayed by the time it takes for the weapon to spin up to this speed (using $Submodel Rotation Acceleration or its default value), regardless of whether an external model is used or not.
}}
{{Table38|
*Note: It's no longer required that the ship actually have external models enabled (whether or not this weapon has one defined) for the spin up delay to occur.
}}

===$Submodel Rotation Acceleration:===
{{Table3610|
*Defines the rotation acceleration of the external weapon model.
*Syntax: '''''Float'''''
*Default value: 10}}

===@Laser===
In the event a 3D model is not defined for the weapon, FSO creates an object similar to a glowpoint. Essentially, it is a 2D plane that always faces the player's camera with an additive texture applied to it, and may or may not have an omnilight follow it.

As suggested by its name, this option group is normally used for lasers and similar primaries, but it may also be used for other weapon types as well.

Unless said otherwise, the graphic files used within this group may be of any compatible type (.DDS, .PCX, .TGA, etc.), however a .DDS is recommended.

====@Laser Bitmap:====
Defines the graphic file to be used as the weapon effect.

Blending type: additive

Syntax: '''''String''''', filename

'''Example:'''
<pre>
@Laser Bitmap: my_laser_bitmap
</pre>

====@Laser Head-on Bitmap:====
{{Table220|
Defines another laser graphic file to be used and crossfaded into as the camera angles towards the front or bank of this weapon. See also @Laser Head-on Transition Angle and @Laser Head-on Transition Rate.

Syntax: '''''String''''', filename}}

====@Laser Glow:====
Defines the graphic file to be used for the glowmap of the weapon effect.

Blending type: additive

*This file is 'multiplied' by a value between Color and Color2.
*The physical dimensions of the glowmap in-game is 2x the size of the bitmap.

Syntax: '''''String''''', filename

'''Example:'''
<pre>
@Laser Glow: my_laser_glowmap
</pre>

====@Laser Glow Head-on Bitmap:====
{{Table220|
Defines another graphic file to be used for the laser glow and crossfaded into as the camera angles towards the front or bank of this weapon. See also @Laser Head-on Transition Angle and @Laser Head-on Transition Rate.

Syntax: '''''String''''', filename}}

====@Laser Head-on Transition Angle:====
{{Table220|
Overrides the angle in degrees from the front (or back) that the head-on transition crossfade is at exactly a 50/50 blend.

Syntax: '''''Float''''', degrees
Default: Calculated from the ratio of the laser's length to its average radius}}

====@Laser Head-on Transition Rate:====
{{Table220|
Defines how quickly the head-on transition fades from one bitmap to the other. Greater than 20 is an instant switch with no blending.

Syntax: '''''Float'''''
Default: 2}}

====@Laser Color:====
The RGB color of the glow effect.

*The color is applied both to the glowmap and the omnilight that follows the effect.

Syntax: '''''Color''''', red, green, blue respectively, 8-bit value from 0 to 255

'''Example:'''
<pre>
@Laser Color: 255, 0, 0 ; Red glow effect at the start of the effect's lifetime
</pre>

====@Laser Color2:====
The RGB color of the glow effect at the end of the effect's lifetime (at its maximum range).

*The color is applied both to the glowmap and the omnilight that follows the effect.
*The actual color of the glow effect is somewhere in between the values defined by Color and Color2. Essentially, the actual color "fades" from Color to Color2 over its lifetime.
**If Color is not defined, then a default value of 255, 255, 255 is assumed for its initial color.

Syntax: '''''Color''''', red, green, blue respectively, 8-bit value from 0 to 255

'''Example:'''
<pre>
@Laser Color2: 0, 0, 255 ; Blue glow effect at the end of the effect's lifetime.
</pre>

'''Example:'''
<pre>
@Laser Color: 255, 0, 0 ; Start with a Red glow effect, and fade into...
@Laser Color2: 0, 0, 255 ; a Blue glow effect over the lifetime of the effect.
</pre>

====@Laser Length:====
Defines the length of the weapon effect.
*This option stretches the 2D plane "away" from its origin.
Syntax: '''''Float''''', meters

'''Example:'''
<pre>
@Laser Length: 1.0
</pre>

====@Laser Head Radius:====
Defines the width of the leading edge, or "head," of the weapon effect.
*The edge of the 2D plane farthest away from its origin is the leading edge.
Syntax: '''''Float''''', meters

'''Example:'''
<pre>
@Laser Head Radius: 0.75
</pre>

====@Laser Tail Radius:====
Defines the width of the trailing edge, or "tail" of the weapon effect.
*The edge of the 2D plane that is closest to its origin is the trailing edge.
Syntax: '''''Float''''', meters

'''Example:'''
<pre>
@Laser Tail Radius: 0.75
</pre>

===$Light color:===
{{Table222|
*Sets the color of light cast by the weapon.
*Syntax: '''''Color''''', red, green, blue respectively, from 0 to 255
*Default value: If not set, the color is white for weapons with models, or based on the laser colors otherwise }}

===$Light radius:===
{{Table222|
*Sets the maximum distance light cast by the weapon will reach. Increasing this will tend to make it appear brighter near it's center
*Syntax: '''''float''''', any positive value
*Default value: The defaults for different weapon types are set in [[Lighting_Profiles.tbl]]}}

===$Light intensity:===
{{Table222|
*Acts as a multiplier to the brightness of the light cast by the weapon. This changes the brightness without affecting the radius.
*Syntax: '''''float''''', any positive value
*Default value: 1}}

===$Collision Radius Override:===
{{Table202|
*Weapon - weapon collisions are treated as two spheres, where a laser's sphere's radius is equal to its Head Radius, and a missile's is the radius of its associated model (possibly doubled). Using this will override either of those values.
*If used on a beam it will override its collision radius as well, instead of using the widest section.
*NOTE: If the weapon is interceptable, such as a bomb or has been given hitpoints, this value will ''still'' be doubled, unless the "no radius doubling" flag is used.
*Syntax: '''''Float''''', meters}}

===$Mass:===
*Scales the kinetic effect this weapon has on its target. With higher mass imparting a stronger effect.
*The eventual kinetic effect is also multiplied by the speed. ie ''$Mass: 3'' and ''$Velocity: 200'' has much weaker kinetic effect than ''$Mass: 3'' and ''$Velocity: 1000''. This is also true for the intesnity of the "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 targeting 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
*Note that Fire wait will be reset to 1 if it is set over 5 for non turreted primary weapons (doesn't apply to 3.6.14+)
*Syntax: '''''Float''''', seconds

====+Max Delay:====
{{Table373|
*Defines the maximum amount of time it takes to refire a weapon in a random fire delay range.
**This must be used with +Min Delay: to have any effect.
*Syntax: '''''Float''''', seconds}}

====+Min Delay:====
{{Table373|
*Defines the minimum amount of time it takes to refire a weapon in a random fire delay range.
**This must be used with +Max Delay: to have any effect.
*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 approximately 5.88 times the damage value per second. The actual damage is this number multiplied by one of the factors below.
*The exact factor to multiply by is 100/17, or one 'pulse' of damage every 170 seconds. The generally used wisdom of 5.5 times may have been generally accurate before beam damage was made continuous and frame-rate independent, but is now out of date information.
*Syntax: '''''Float''''', damage
*Note: adding an inner and/or outer radius to a weapon doubles its effective damage to the target (i.e. 1x impact, 1x area effect)

===$Damage Time:===
{{Table373|
*This sets a time from the end of the weapons lifetime that damage will start to attenuate at. '''''Example: Weapon lifetime is 2.0 seconds and the desired effect is to attenuate after 0.5 seconds have passed, set this to 1.5 seconds.'''''
*Syntax: '''''Float''''', seconds. Defaults to 0.0.
**Note: If neither +Min Damage: nor +Max Damage: is set, the damage will always attenuate to zero at max range.
***If both +Min Damage: and +Max Damage: are set, both are defaulted to 0.0 and damage will be attenuated to zero.}}

====+Attenuation Damage:====
{{Table373|
*This sets the damage a weapon will attenuate to after reaching $Damage Time:.
*Syntax: '''''Float''''', damage.}}

====+Min Damage:====
{{Table373|
*This sets the lowest amount of damage possible assuming damage attenuation is taking place. '''''This has been deprecated, please use +Attenuation Damage: instead.'''''
*Syntax: '''''Float''''', damage. Defaults to 0.0.}}

====+Max Damage:====
{{Table373|
*This sets the highest amount of damage possible assuming damage attenuation is taking place. '''''This has been deprecated, please use +Attenuation Damage: instead.'''''
*Syntax: '''''Float''''', damage. Defaults to 0.0.}}

===$Angle of Incidence Damage Multiplier:===
{{Table212|
*Causes the weapon's damage to be multiplied by these factors depending on the angle of incidence.
*It is ''not'' linear, it is based on the sine of the angle to the surface. If the factors are 1x for minimum, and 2x for maximum, at an angle of 45° the multiplier is 1.707x, for instance.
====+Min:====
*The damage multiplier at a perfectly glancing hit, parallel to the surface (although not technically possible).
*Syntax: '''''Float'''''
====+Max:====
*The damage multiplier when hit straight on, perpendicular to the surface.
*Syntax: '''''Float'''''}}

===$Damage Type:===
{{Table3610|
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:''' [[armor.tbl]]

*Syntax: '''''String''''', name of the damage type ( as defined by [[armor.tbl#$Damage Type:|$Damage Type]] )}}

===$Arm time:===
{{Table3610|
*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:===
{{Table3610|
*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}}
{{Table3615|
*This parameter is also applied to flak weapons. Previous behaviour was to arm weapons after 10 meters of travel.}}

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

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

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

===$Flak Detonation Accuracy:===
{{Table3615|
*Normally, flak weapons detonate at a range of 65 to 99 meters from their intended target, depending on the firing ships' weapon subsystem health. This parameter can be used to adjust this behaviour, as it defines the base range used to determine this detonation range. Standard value is 65.
*Syntax: '''''Float''''', range in meters}}

===$Flak Targeting Accuracy:===
{{Table3615|
*Turret-fired flak weapons are normally firing in a cone around the target's predicted position. This parameter can be used to adjust the size of this cones' base radius. Standard is 60 meters.
*Syntax: '''''Float''''', radius in meters}}

===$Untargeted Flak Range Penalty:===
{{Table3615|
*If a flak weapon is fired without a target selected, this parameter defines the range penalty applied to that weapon. Standard is 20 meters, meaning an untargeted flak weapon will detonate after traveling its max range - 20 meters.
*Syntax: '''''Float''''', penalty in meters.}}

===$Shockwave damage:===
{{Table3610|
*Override for the damage caused by shockwaves (default is [[#$Damage:]])
*Syntax: '''''Float''''', damage
*Note: adding a shockwave to a weapon doubles its effective damage to the target (i.e. 1x impact, 1x shockwave)
}}

===$Shockwave Damage Type:===
{{Table3610|
*'''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 kinetic 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. Damage is reduced by the square of the distance between the inner radius and outer radius. i.e. half way between inner and outer results in 1/4 damage
*Note: adding an inner and/or outer radius to a weapon doubles its effective damage to the target (i.e. 1x impact, 1x area effect)
*Syntax: '''''Float''''', meters

===$Outer Radius:===
*Maximum radius at which any damage is done. See $Inner Radius for the attenuation formula.
*Also defines the size of the shockwave (if shockwave speed is > 0)
*Note: adding an inner and/or outer radius to a weapon doubles its effective damage to the target (i.e. 1x impact, 1x area effect)
*Syntax: '''''Float''''', meters

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

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

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

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

===$Shockwave Sound:===
{{Table202|
Optional sound to be used for the sound heard when for the shockwave (default is sound 109).
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$Dinky shockwave:===
{{Table3610|
*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:'''''}}
{{Table202|
*'''''+Shockwave sound:'''''}}

===$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:===
{{Table3610|
*Defines the minimum lifetime of the weapon
*Syntax: '''''Float''''', seconds}}

===$Lifetime Max:===
{{Table3610|
*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 turreted weapons.
*Syntax: '''''Float'''''

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

===$Autoaim FOV:===
{{Table224|
'''This option is exclusive to primaries.'''
*Defines if the weapon will have auto-aim and what the FOV of the auto-aim is.
*Syntax: '''''Float'''''}}

===$Homing:===
'''This option is exclusive to secondaries.'''
{{Table212|'''This option may now be applied to primaries'''. They may only use heat seeking. For optimal results the "no homing speed ramp" flag may be used.}}

Defines if the bolts/missiles in question is homing

If set to NO, then following fields are not required in the table.

*Syntax: '''''Boolean''''', yes or no

===='''+Type:'''====
Defines the homing method
*Syntax: '''''String''''', ''ASPECT'' or ''HEAT''
{{Table3610| 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:'''====
Determines how quickly the missile can turn. Ostensibly the number of seconds it takes the missile to do a 360 degree circle at full turn speed, but for complicated reasons this is only true if [[Game_settings.tbl#.2BAI_respect_tabled_turn_time_and_rotdamp|AI respect tabled turn time and rotdamp]] is enabled.
**Syntax: '''''Float''''', seconds

===='''+Turning Acceleration Time:'''====
{{Table202|
Determines how quickly the missile reaches its maximum turn speed.
*Note: Requires [[Game_settings.tbl#.24AI_use_framerate_independent_turning:|$AI use framerate independent turning]] in game_settings.tbl
**Syntax: '''''Float''''', seconds}}

===='''+View Cone:'''====
'''Heat-seeking missiles only'''

This is the width of the weapon's viewing cone, given in degrees. Objects outside this cone are effectively invisible to the missile. The value / 2 gives the angle from the missile's centerline to the edge of the viewing cone.
*Syntax: '''''Float''''', degrees
{{Table3610| Has been enabled also to aspect seekers as an option. They will continue to home on targets outside their view cone, but will take a continuous lifetime penalty every second their target is outside this cone.}}

===='''+Min Lock Time:'''====
'''For aspect/javelin missiles only'''

The minimum number of seconds to gain a target lock.
*Syntax: '''''Float''''', seconds

===='''+Lock Pixels/Sec:'''====
'''For aspect/javelin missiles only'''
The number of 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'''

The number of 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. (Needs verification )
**Syntax: '''''Integer''''', pixels

===='''+Seeker Strength:'''====
{{Table3610|
Defines the seeking ability of the homing system. Default of heat seekers is 3.0 and for aspect seekers 2.0. Spoofing chance is defined as '''[[#$Countermeasure:|cm type effectiveness]]'''/'''seeker strength''' (missile must be within the countermeasures '''[[#$Countermeasure:|+Effective Radius:]]'''
*Syntax: '''''Float''''', seeker strength}}

===='''+Lock FOV:'''====
{{Table234|
Defines the width of the cone within which the missile is capable of achieving a lock, in degrees. Only applies to aspect seekers.
*Syntax: '''''Float''''', default (approximately): 63.57666}}

===='''+Target Lead Scaler:'''====
{{Table3611|
Defines the type of pursuit course the missile tries to obtain.
*Values < 0 give lag pursuit, values ~ 0 give pure pursuit, values > 0 give lead pursuit.
*Syntax: '''''Float''''', default for heat seekers: 0, default for aspect or javelin seekers: 1.}}

===='''+Target Lock Restriction:'''====
{{Table202|
Defines if the missile can lock onto ships besides the current target
*Syntax: '''''String''''', name of the behavior, default is ''current target only'';.
*''Current target only'' As normal, can only acquire locks on the targeted ship
*''Any target'' Missile will lock on any valid target. Missile locking is still disabled in certain cases, such as when a friendly is the player's target
*''Current target, any subsystem'' Targeting is restricted to the current ship, but will pick turrets and subsystems on that ship. }}

===='''+Independent Seekers:'''====
{{Table202|
Defines the ability for a missile to target multiple objects at once.
*Syntax: '''''Boolean''''', yes or no, default is no.}}

===='''+Target Lock Objecttypes:'''====
{{Table220|
Defines what type of object can be locked on with this weapon
*Syntax: '''''String''''', name of the object type, default is ''ships''
*''ships'' Will target only ships
*''bombs'' Will target bombs and targetable missiles }}

===='''+Trigger Hold:'''====
{{Table202|
Defines the ability to hold the trigger to lock and release to fire.
*Syntax: '''''Boolean''''', yes or no, default is no.}}

===='''+Reset On Launch:'''====
{{Table202|
Defines the ability for locks to reset upon missiles being fired.
*Syntax: '''''Boolean''''', yes or no, default is no.}}

===='''+Max Seekers Per Target:'''====
{{Table202|
Defines the maximum number of seekers that can target a single object.
*Syntax: '''''Integer''''', number of seekers.}}

===='''+Max Active Seekers:'''====
{{Table202|
Defines the maximum number of total seekers for the weapon to have.
*Syntax: '''''Integer''''', number of seekers.}}

===='''+Ship Types:'''====
{{Table202|
Defines the ship types that this missile can target. In order for a ship to be targetable it must be able to match one of the listed types, if some of the below lists are also specified, it must match into those as well.
*Syntax: '''("String" "String")''', ship types.}}

===='''+Ship Classes:'''====
{{Table202|
Defines the ship classes that this missile can target. In order for a ship to be targetable it must be able to match one of the listed classes, if some of the above/below lists are also specified, it must match into those as well.
*Syntax: '''("String" "String")''', ship classes.}}

===='''+Species:'''====
{{Table202|
Defines the species whose ships this missile can target. In order for a ship to be targetable it must be able to match one of the listed Species, if some of the above/below lists are also specified, it must match into those as well.
*Syntax: '''("String" "String")''', species.}}

===='''+IFFs:'''====
{{Table202|
Defines the IFF's whose ships this missile can target. In order for a ship to be targetable it must be able to match one of the listed IFFs, if some of the above lists are also specified, it must match into those as well.
*Syntax: '''("String" "String")''', IFFs.}}

===$Homing Auto-Target Method:===
{{Table214|
*If this weapon needs to acquire a target on its own, such as a heatseeker losing its target or having the "untargeted heatseeker" flag, this determines how it should do so. Options are:
*'''CLOSEST''', the weapon will acquire the nearest target that it is able.
*'''RANDOM''', the weapon will acquire a random target from those available.
}}

===$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'. Does not work with player weapons.
*Is incompatible with "Corkscrew" option.
*Swarm will negatively affect the missile's ability to hit its target and will not lead its target even with [[Weapons.tbl#.2BTarget_Lead_Scaler:|Target Lead Scaler]] defined unless [[Game_settings.tbl#.24Swarmers_Lead_Targets:|$Swarmers Lead Targets]] is enabled.
*Syntax: '''''Integer''''', number of shots in a swarm
{{Table3610|
*'''+SwarmWait:'''
**Defines the time between weapons fired in a swarm
**Syntax: '''''Float''''', seconds
***Default: 0.150)}}

===$Acceleration Time:===
{{Table371|
*Defines how long it takes for a secondary weapon to attain full speed. Takes precedence over $Free Flight Time (see below) in terms of the weapon's velocity, and affects both locked-on and dumbfired secondaries.
*Syntax: '''''Float''''', seconds
**Default: 0.0}}

===$Velocity Inherit:===
{{Table371|
*Defines how much of the parent ship's velocity to inherit, if [[Ai_profiles.tbl#.24use_additive_weapon_velocity:]] is used.
*Syntax: '''''Float''''', percents
**Default: 100.0}}

===$Free Flight Time:===
{{Table3610|
*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}}

'''Note:''' due to dumbfires never changing their speed, using this on a dumbfire missile will have it stuck at freeflight speed even after the end of the freeflight time.

===$Free Flight Speed:===
{{Table3613|
*Defines the speed that the weapon will be traveling at during the free flight segment (see above).
*Syntax: '''''Float''''', Multiplier for the actual speed, minimum 0.01.
**Default: 0.25
{{Note| This feature was never implemented correctly and was removed in r8867. FSO parses but doesn't use the value, and prints a warning in the log. This feature has subsequently been reimplemented, see $Free Flight Speed Factor: below}}
}}

===$Free Flight Speed Factor:===
{{Table202|
*Defines the speed that the weapon will be traveling at during the free flight segment (see above).
*Syntax: '''''Float''''', Multiplier for the actual speed, minimum 0.01.
**Default: 0.25
}}

===$Gravity Const:===
{{Table224|
*If the mission has gravity, this is the multiplier applied to acceleration from gravity on the weapon.
*AI will lead for ballistic trajectories, and this may affect their range as they will not fire unless they can successfully make a ballistic path to their target.
*'''Homing weapons are unaffected by gravity no matter what'''.
*Syntax: '''''Float'''''
**Default: 0}}

===$PreLaunchSnd:===
{{Table3613|
*Defines the one-shot sound effect to play at the beginning of a firing stream. Currently only has an effect on primary weapons.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
**Default: No Sound}}

===+PreLaunchSnd Min Interval:===
{{Table3613|
*Defines Minimum interval between when the player stops firing and the next time the pre-launch sound can play, as a limiter in case the player is pumping the trigger.
*Syntax: '''''Integer''''', Minimum delay in milliseconds between the end of the previous firing sequence and the next time the pre-launch sound effect will be played.
**Default: 0 (play pre-launch sound at the beginning of every firing sequence, if present)}}

===$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]]

===$CockpitLaunchSnd:===
{{Table232|
*Corresponding sound effect when the weapon is launched from the player's ship, allowing use of 2d stereo sounds.
*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:===
{{Table3610|
*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

{{Table214|
===$AmbientSnd:===
*The sound this weapon passively emits in 3d space. The weapon version of [[Ships.tbl#.24EngineSnd:|EngineSnd]] for ships.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$TrackingSnd===
{{Table3615|
*The looping sound played when the player is tracking a target with this weapon.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$LockedSnd===
{{Table3615|
*The sound played when the player has locked onto their target with this weapon.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$InFlightSnd===
{{Table3615|
*The looping sound played while the player has this weapon currently flying.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+Inflight sound type'''
**Specifies when the in flight sound is played.
**The value can be one of the following values which are matched case-insensitively:
***''''''TARGETED'''''': The sound is played when the missile tracks a target
***''''''UNTARGETED'''''': The sound is played when the missile is currently not tracking a target
***''''''ALWAYS'''''': The sound is played always}}

===$Model:===
{{Table3610|
*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 frequency that weapons are loaded to the ship
*Syntax: '''''Float''''', How many times per second the weapons are loaded.
**Example: 2.0 will reload every half second. 0.1 will load every ten seconds.

===$Rearm Ammo Increment:===
{{Table38|
*Defines how many missiles or how much ballistic ammo is loaded per load sound.
*Syntax: '''''Integer''''', how many bullets or missiles are loaded.}}

===+Weapon Range:===
*If set, the AI will use this value or the result of weapon lifetime * velocity as the weapon's effective range, whichever is lower. This also affects the [[Hud_gauges.tbl#Lead_Indicator|Lead Indicator]]
*Syntax: '''''Float''''', meters

===+Weapon Min Range:===
{{Table3610|
*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}}

===+Weapon Optimum Range:===
{{Table214|
*AI fightercraft will attempt to close the distance to their target while they are outside of this range and using this weapon as their currently equipped primary.
*Syntax: '''''Float''''', meters}}

===$Pierce Objects:===
{{Table212|
*Causes the weapon to penetrate the objects impacted and not be destroyed.
*Syntax: '''''Boolean'''''
====+Spawn Children On Pierce:====
*Will spawn the weapons children on each hit, not just when it eventually gets destroyed through lifetime
*Syntax: '''''Boolean'''''}}

===$Flags:===
*See [[Weapons.tbl#Weapons.tbl_Flags|below]]
*Syntax: '''''( "String" "String" )''''', names of the flags assigned to the weapon
**Example: ( "Player allowed" "in tech database" )

{{Table3610|
*Can be followed by '''+override''' option in order to reset the weapon flags before parsing in the new ones
*Using this option will erase all '''homing'''-related flags as well as '''swarm''', '''variable lead''', '''trail''', '''TAG''', and '''transparent''' settings in addition to the listed flags. All these should be set again - if they are required - when this option is used.

**Syntax: '''''+override'''''}}

===$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
{{Table212|
*'''+Alpha Decay Exponent:'''
**Causes the trail to fade away non-linearly. The 0 -> 1 progress through the trail's life is taken to the power of the provided number when being used for trail alpha purposes
**Larger numbers above 1 cause the trail to fade away very slowly at first, and then suddenly at the end. Smaller numbers below 1 cause it to fade away quickly at first, and then slow down for most of its life.
**Syntax: '''''Float''''', positive}}
*'''+Max Life:'''
**How long the trail lasts.
**Syntax: '''''Float''''', seconds
{{Table202|
*'''+Spread:'''
**Causes the trail points to diffuse and drift apart at this speed over time.
**Syntax: '''''Float''''', meters per second}}
*'''+Bitmap:'''
**The graphic file to use for the trail.
**Syntax: '''''String''''', filename
{{Table212|
*'''+Bitmap Stretch:'''
**Multiplies how far the bitmap is stretched over each trail segment.
**Syntax: '''''Float'''''}}
{{Table3611|
*'''+Faded Out Sections:'''
**Defines the number of the trail sections (counting from the leading edge) which are gradually faded out.
**Syntax: '''''Integer''''', number of trail sections}}

===$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:===
{{Table3610|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

===$Collide Weapon:===
{{Table3610|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

===$Impact Effect:===
{{Table38|
*Specifies the [[Particle Effects|particle effect]] which will be used for impacts of this weapon.
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Impact Explosion'' and ''$Impact Explosion Radius'' are not valid options!
}}

===$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, default 1.0

===$Shield Impact Explosion Radius:===
{{Table373|
*Radius of the shield impact explosion, see [[Ships.tbl#.24Shield_Impact_Explosion:]].
*Syntax: '''''Float''''', meters, defaults to value of $Impact Explosion Radius}}

===$Dinky Impact Effect:===
{{Table38|
*Specifies the [[Particle Effects|particle effect]] which will be used for Dinky (not armed) explosions of this weapon.
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Dinky Impact Explosion'' and ''$Dinky Impact Explosion Radius'' are not valid options!
}}

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

===$Dinky Impact Explosion Radius:===
{{Table3610|
*Same as Impact Explosion Radius but for Dinky explosions
*Syntax: '''''Float''''', meters}}

===$Piercing Impact Effect:===
{{Table38|
*Specifies the [[Particle Effects|particle effect]] which will be used for piercing impacts.
*Syntax: '''String''', the particle effect name
*If this option is specified then piercing impact options below are not valid!
}}

===$Piercing Impact Explosion:===
{{Table3611|
*Defines the effect used for events when weapon pierces the target
*Syntax: '''''String''''', filename or ''none''}}

===$Piercing Impact Radius:===
{{Table3611|
*Defines the base radius of the effect used for piercing weapon impacts
*Syntax: '''''Float'''''}}

===$Piercing Impact Velocity:===
{{Table3611|
*Defines the base velocity for the particles piercing the target
*Syntax: '''''Float'''''}}

===$Piercing Impact Splash Velocity:===
{{Table3611|
*Defines the base velocity for the particles splashing from the target (secondary piercing effects
*Negative value causes the second batch or particles to splash to opposite direction
*Syntax: '''''Float'''''}}

===$Piercing Impact Variance:===
{{Table3611|
*Defines the variance added to the particles
*Values near 0 cause very little variance and values close to 1 cause extreme dispersal.
*Syntax: '''''Float'''''}}

===$Piercing Impact Life:===
{{Table3611|
*Defines the lifetime of the effect for single frame effects
*For multiple frame effects the lifetime is the lifetime of the animation used
*Syntax: '''''Float'''''}}

===$Piercing Impact Particles:===
{{Table3611|
*Defines the number of particles released per impact
*Syntax: '''''Integer'''''}}

===$Piercing Impact Draw Modifier:===
{{Table3611|
*Defines the multiplier applied to the ships piercing effect limit percentage
*Syntax: '''''Float'''''}}
*Option removed in 3.6.12. Use [[armor.tbl]] to finetune piercing effects.

===$Inflight Effect:===
{{Table38|
*Sets the inflight [[Particle Effects|particle effect]] which is used when the laser is active. This is only used by laser weapons.
*Syntax: '''''String''''', the particle effect name
}}
===$Freeflight Effect:===
{{Table38|
*Sets the [[Particle Effects|particle effect]] which is used when the missile is in the free flight phase. See [[#$Free Flight Time:|$Free Flight Time]] for more information.
*Syntax: '''''String''''', the particle effect name
*This option is only valid for missile weapons
}}
===$Ignition Effect:===
{{Table38|
*Sets the ignition [[Particle Effects|particle effect]] which is used when the missile is transitioning from free flight to homed or unhomed flight.
*Syntax: '''''String''''', the particle effect name
*This option is only valid for missile weapons
}}
===$Homed Flight Effect:===
{{Table38|
*Sets the ignition [[Particle Effects|particle effect]] which is used when the missile is in homed flight mode.
*Syntax: '''''String''''', the particle effect name
*This option is only valid for missile weapons
}}
===$Unhomed Flight Effect:===
{{Table38|
*Sets the ignition [[Particle Effects|particle effect]] which is used when the missile is in unhomed flight mode.
*Syntax: '''''String''''', the particle effect name
*This option is only valid for missile weapons
}}

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

===$EMP Intensity:===
*How deeply an EMP effect scrambles your electronics
**Needs the [[#EMP|EMP]] flag set to have any effect
*Basically a percentage, a value of 250 results in a 25% chance of something getting scrambled each frame.
*Maximum value of 500.0
**Syntax: '''''Float''''' (defaults to 300.0)

===$EMP Time:===
*Duration of the EMP effect
**Needs the [[#EMP|EMP]] flag set to have any effect
**Syntax: '''''Float''''', seconds (defaults to 10.0)

===$Recoil Modifier:===
{{Table373|
*Multiplies the recoil force of a weapon by this value, use a value greater than 1.0 to increase the force, use a value between 1.0 and 0.0 to decrease.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note| The "apply recoil" weapon flag must be set for this to be valid. If the flag is not set, FSO will throw a warning and automatically set it at runtime.}}
}}

===$Leech Weapon:===
**The amount of weapon energy to drain with each hit (a flat value, not a percentage)
**Needs the [[#Esuck|Esuck]] flag set to have any effect
**Syntax: '''''Float''''' (defaults to 10.0)

===$Leech Afterburner:===
**The amount of afterburner fuel to drain with each hit (a flat value, not a percentage)
**Needs the [[#Esuck|Esuck]] flag set to have any effect
**Syntax: '''''Float''''' (defaults to 10.0)

===$Vampiric Healing Factor:===
{{Table224|
*Multiplier for how much the shooter is healed after dealing hull damage (1.0 means healing done is equal to damage dealt)
**Needs the [[#Vampiric|Vampiric]] flag set to have any effect
*Must be a positive number higher than 0.0
**Syntax: '''''Float''''' (defaults to 1.0)
}}

===$Corkscrew:===
{{Table3610|
*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:===
{{Table3610|
*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.
}}
{{Table371|
*'''+Area Of Effect'''
**If specified, allows the electronics effect to apply to every ship hit by this weapon's blast or shockwave (the "Electronics" flag isn't necessary with this option).
}}
{{Table3610|
*'''+Intensity:'''
**May only be used with '''+New Style:''' electronics. '''''Has been deprecated'''''.
**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 subsystems.
**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:===
{{Table3610|
*Defines the cone (with an angle) where the spawned weapons appear. ''Value'' gives the angle from the missile's centerline. The maximum possible angle between any two child weapons would be ''Value*2''.
*Like all spawn options, Spawn Angle should be defined as many times as the carrier weapon has child weapons defined for it (up to 5), before moving to the next option.
*Syntax: '''''Float''''', degrees, default is 180}}

===$Spawn Minimum Angle:===
{{Table202|
*Defines an inner angle for the cone within which the spawned weapons appear. ''Value'' gives the angle from the missile's centerline.
*Like all spawn options, Spawn Minimum Angle should be defined as many times as the carrier weapon has child weapons defined for it (up to 5), before moving to the next option.
*Syntax: '''''Float''''', degrees, default is 0}}

===$Spawn Interval:===
{{Table202|
*Causes the associated spawn event to happen continuously at this time interval. Enabling this will prevent the spawn event from triggering on detonation.
*NOTE: Having very large numbers of total children (low interval and/or high count) can cause issues for multiplayer, and you will be warned in multiplayer if the total count is greater then 300.
*Like all spawn options, Spawn Interval (and its associated Delay) should be defined as many times as the carrier weapon has child weapons defined for it (up to 5), before moving to the next option.
*Syntax: '''''Float''''', seconds, minimum is 0.1, '''You will not be warned for a negative spawn interval. ''' The value will be ignored and the spawn will be treated as a regular detonate spawn if negative. This is on purpose so that continuous/detonate spawns can be set regardless of the order in which they are defined in the flags.}}

====+Delay:====
{{Table202|
*Continuous spawn will not begin until this has elapsed.
*Syntax: '''''Float''''', seconds, default is 0}}

===$Spawn Effect:===
{{Table202|
*Specifies the [[Particle Effects|particle effect]] which will be used for continuous spawns of this weapon. Will not be used for detonation.
*Like all spawn options, Spawn Effect should be defined as many times as the carrier weapon has child weapons defined for it (up to 5), before moving to the next option.
*Syntax: '''String''', the particle effect name}}

===$Local SSM:===
{{Table3610|
*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:===

*Defines the countermeasure effectiveness, radius, etc
{{note|
*Spoofing chance is defined as '''cm type effectiveness'''/'''[[#+Seeker Strength:|seeker strength]]''' (missile must be within the countermeasures '''+Effective Radius:''').
*All countermeasures in the mission perform tests to spoof missiles for two frames after '''any countermeasure''' is created in the mission. No, this doesn't seem to make much sense.
{{Table382|The global frame counter can be bypassed by using '''[[#+Pulse Interval:|pulse interval]]'''.}}
*'''Provisional'''; Countermeasures are only given one chance to spoof any individual missile. This makes tuning seeker strength/effectiveness meaningful.
**Previously some record of which countermeasures had been seen by each missile was kept, but it broke when multiple countermeasures were involved. A good chance of breaking with two countermeasures, and a guaranteed chance of breaking with three or more. This reduced the impact of the seeker strength/effectiveness ratio, but was partly cancelled out by the 2 frames thing.
}}

{{Table3610|
===='''+Heat Effectiveness:'''====
*Defines the countermeasures effectiveness against heat seeking missiles
*Syntax: '''''Float''''', cm effectiveness
**Default: 1.0

===='''+Aspect Effectiveness:'''====
*Defines the countermeasures effectiveness against aspect seeking missiles
*Syntax: '''''Float''''', cm effectiveness
*Default: 1.0

===='''+Effective Radius:'''====
*Defines the countermeasures effective radius
*Syntax: '''''Float''''', meters
**Default: 300.0
}}

{{Table373|
====+Missile Detonation Radius:====
*Defines the radius within which a missile homing on this countermeasure will trigger a detonation (see '''+Single Missile Kill:''')
*Syntax: '''''Float''''', meters
**Default: 40.0
{{note| only affects missiles homing on countermeasures, i.e. heat or aspect with "pulls aspect seekers" flag}}

====+Single Missile Kill:====
*Defines if countermeasures will detonate only the missile homing on this countermeasure, or every missile within '''+Missile Detonation Radius:'''
*Syntax: '''''Boolean'''''
**Default: false
{{note| only affects missiles homing on countermeasures, i.e. heat or aspect with "pulls aspect seekers" flag}}
}}

{{Table382|
====+Pulse Interval:====
*Defines how much time passes between each pulse of this countermeasure.
*Syntax: '''''Float''''', milliseconds
**Default: 0
{{note| any value less than or equal to 0 means the countermeasure doesn't pulse, and uses the global 2-frame counter after any countermeasure is fired.}}
}}

{{Table212|
====+Use Fire Wait:====
*Makes the countermeasure fire wait use what is specified in the '''$Fire Wait:''' section of the weapon.
*Default countermeasure fire wait is 333 milliseconds, regardless of that value was set in '''$Fire Wait:'''.

====+Failure Launch Delay Multiplier for AI:====
*After a failed countermeasure launch the game waits a certain time interval before attempting another launch.
*Previously, the amount of time was calculated as ('fire wait' + 2000 * 'countermeasure firing chance').
*If set to a non negative number, this value will be multiplied to the fire wait value to determine the amount of time before another countermeasure can be attempted.
*Syntax: '''''Float'''''
**Default: -1
{{note| any value less than 0 means the default formula will be used.}}

====+Successful Launch Delay Multiplier for AI:====
*After a successful countermeasure launch the game waits a certain time interval before attempting another launch.
*This value is multiplied to the fire wait value to determine the amount of time before another countermeasure can be attempted.
*Syntax: '''''Float'''''
**Default: 2
{{note| any value less than 0 means the default value will be used.}}

}}

===$BeamInfo:===
*'''+Type:'''
*Defines the type of beam in question. Options are:
**''0'' or ''Direct fire'', a standard non-slashing type beam that fires directly at a random point on the target's hull
**''1'' or ''Slashing'', a slashing type beam, that slashes between opposing corners of the ship
**''2'' or ''Targeting'', a targeting beam that is used to trigger SSMs.
**''3'' or ''Antifighter'', a beam type that fires pulses in anti-fighter role and acts like type 0 beam in other roles.
**''4'' or ''Normal Fire'', a beam that is restricted to what is directly in front of it, along turrets firepoints normal.
{{Table214|
**''5'' or ''Omni'', a highly flexible kind of beam with many options for its exact behavior. See $Type 5 Beam Options below.}}
*'''+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
{{Table3613|
*'''IFF specific miss factors'''
**Identical to the preceding entry but IFF specific. Replace the <IFF> with the name of the IFF from [[iff_defs.tbl]]
**Syntax: '''''+<IFF> 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
{{Table372|
*'''+Directional Glow:'''
**Defines the length to stretch the muzzleglow along the beam.
**Syntax: '''''Float''''', length in meters, the muzzleglow is rendered along (in the same plane) as the beam instead of perpendicular to the camera.}}
*'''+Shots:'''
**Defines into how may invidual shots the type 3 (AAA) beams are divided. Note total firing is the same as the +Life:
**ALSO AFFECTS FIGHTER BEAMS. If greater than 0, fires from up to that many fire points at a time before cycling. 1 mimics the behavior of weapons with the "cycle" flag, 0 fires from all available fire points like normal weapons.
**Syntax: '''''Integer''''', Default: 1
*'''+ShrinkFactor:'''
**How much of the beam's life is remaining before it starts to shrink in width. (0.1 means 10% life left)
**Syntax: '''''Float''''', value from 0 to 1
*'''+ShrinkPct:'''
**The beam's width factor is reduced by this amount every second. For example, a value of 0.25 means the beam is at 75% width after 1 second, 50% after 2, 25% after 3, and by 4 seconds it reaches the minimum size of 10%.
**Syntax: '''''Float''''', a positive value
{{Table202|
*'''+GrowFactor:'''
**How much of the beam's life is remaining before it starts to grow in width. (1.0 means as soon as the beam fires)
**Syntax: '''''Float''''', value from 0 to 1
*'''+GrowPct:'''
**The beam's width factor is increased by this amount every second. For example, a value of 0.25 means a beam starting at 0% is at 25% width after 1 second, 50% after 2, 75% after 3, and by 4 seconds it reaches the maximum size of 100%.
**Syntax: '''''Float''''', a positive value
*'''+Initial Width Factor:'''
**What factor of the beam's maximum width it starts with.
**Syntax: '''''Float''''', value from 0 to 1}}
{{Table3610|
*'''+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}}
{{Table3611|
*'''+BeamWidth:'''
**Defines the width of the beam for collision test purposes instead of using widest beam section.
**Syntax: '''''Float''''
{{Table222|
*'''+Beam Light Flickers:'''
*Controls if the dynamic flickering of the beam width is applied to the light cast by the beam as well
*Syntax: '''''boolean'''''
*Default value: True
*'''+Beam Width Multiplies Light Radius:'''
*Controls if the light radius of a beam is multiplied by the beam width.
*Syntax: '''''boolean'''''
*Default value: True}}
{{Table38|
*'''+Beam Flash Particle Effect:'''
**Specifies the beam flash [[Particle Effects|particle effect]].
**Syntax: '''''String''''', particle effect name
**If this is specified then '''+Beam Flash Effect''' and '''+Beam Flash Radius''' are not valid options!
}}
*'''+Beam Flash Effect:'''
**Defines the additional impact flash effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Flash Radius:'''
**Defines the radius for the additional impact flash effect.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect:'''
**Defines the beam piercing (bursting flames) effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Piercing Radius:'''
**Defines the average radius used for the beam piercing effects.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Velocity:'''
**Defines the base velocity for the piercing effects
**Syntax: '''''Float'''''
*'''+Beam Piercing Splash Effect Velocity:'''
**Defines the base velocity for the secondary piercing effects
**Negative velocity causes the particles to move to opposite direction
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Variance:'''
**Defines the variances of the particles from the main path
**Values close to 0 cause minimum variance, higher values cause higher variances
**Syntax: '''''Float'''''}}

{{Table214|
*'''$Type 5 Beam Options:'''
**Species the unique attributes for type 5 beams. '''None of these properties will be used if the weapon is not a type 5 beam.'''
**Fundamentally, type 5 beams are slashing type beams, where the start and end positions refer to physical positions in space (and not angles from the point of view of the shooter) and have many parameters for choosing their positions, including having them be on top of each other, and thus forgoing standard slashing behavior, and also for having rotations, both during the beam firing and in between firings.
*'''+Start Position:'''
**Determines how the starting position should be chosen. Options are:
***'''RANDOM ON SHIP''', Like type 0 direct-fire beams, chooses a random spot on the target's geometry.
***'''RANDOM OFF SHIP''', Like type 1 slash beams, chooses a random spot just outside of the target's geometry.
***'''CENTER''', Chooses the center of the target.
*'''+Start Position Offset:'''
**Displaces the chosen start position in the specified direction and by the specified amount.
***Whether the x, y, and z directions refer to the shooter's point-of-view, or the target's point-of-view is determined by '''Orient Offsets to Target''' below.
***Whether a value of 1 for any coordinate means the target's radius, or a fixed span from the point-of-view of the shooter is determined by '''Scale Offsets to Target''' below.
***Syntax: '''''Vector''''', x, y, and z coordinate. Example: "1, -0.2, -0.9"
*'''+Start Position Randomness:'''
**Further displaces the chosen start position but to a random degree in the specified axes from the number provided to its negative (i.e. a value of 1 will randomly choose between 1 and -1).
***Whether the x, y, and z directions refer to the shooter's point-of-view, or the target's point-of-view is determined by '''Orient Offsets to Target''' below.
***Whether a value of 1 for any coordinate means the target's radius, or a fixed span from the point-of-view of the shooter is determined by '''Scale Offsets to Target''' below.
***Syntax: '''''Vector''''', x, y, and z coordinate. Example: "1, 0.2, 1"

*The following three fields can skipped, and the beam will not traditionally sweep like a slash beam (although it may still rotate).
*'''+End Position:'''
**Determines how the starting position should be chosen. Options are:
***'''RANDOM ON SHIP''', Like type 0 direct-fire beams, chooses a random spot on the target's geometry.
***'''RANDOM OFF SHIP''', Like type 1 slash beams, chooses a random spot just outside of the target's geometry.
***'''CENTER''', Chooses the center of the target.
***'''SAME RANDOM''', If the start position was randomly determined, this will cause the end position to inherit that position (it will not inherit offset or randomness, only the randomness from RANDOM ON/OFF SHIP).
*'''+End Position Offset:'''
**Displaces the chosen end position in the specified direction and by the specified amount.
***Whether the x, y, and z directions refer to the shooter's point-of-view, or the target's point-of-view is determined by '''Orient Offsets to Target''' below.
***Whether a value of 1 for any coordinate means the target's radius, or a fixed span from the point-of-view of the shooter is determined by '''Scale Offsets to Target''' below.
***Syntax: '''''Vector''''', x, y, and z coordinate. Example: "1, -0.2, -0.9"
*'''+End Position Randomness:'''
**Further displaces the chosen end position but to a random degree in the specified axes from the number provided to its negative (i.e. a value of 1 will randomly choose between 1 and -1).
***Whether the x, y, and z directions refer to the shooter's point-of-view, or the target's point-of-view is determined by '''Orient Offsets to Target''' below.
***Whether a value of 1 for any coordinate means the target's radius, or a fixed span from the point-of-view of the shooter is determined by '''Scale Offsets to Target''' below.
***Syntax: '''''Vector''''', x, y, and z coordinate. Example: "1, 0.2, 1"

*'''+Orient Offsets to Target:'''
**This determines the orientation of the offsets and randomness.
**If this is set to ''TRUE'' then the x, y, and z, directions used refer to the target's x, y, and z coordinates. X being left/right, Y being up/down, Z being front/back. A start offset of 0, 0, 1, and an end offset of 0, 0, -1 would always cause the beam to fire at the target's bow and sweep to its aft, no matter which way the shooter is oriented.
**If this is set to ''FALSE'' then the x, y, and z, directions used refer to the shooter's x, y, and z coordinates. Using the z coordinate with this being false will have little effect. A start offset of 1, 0, 0, and an end offset of -1, 0, 0 would always cause the beam to fire towards the target, but to the shooter's right, and sweep in the direction of the shooter's left, regardless of how the target is oriented.
**Syntax: '''''Boolean''''', yes or no, Default: No
*'''+Scale Offsets to Target:'''
**This determines what a magnitude of 1 on the offsets and randomness mean.
**If this is set to ''TRUE'' then a value of 1 for a coordinate means a position in the chosen direction but at a distance equal to the target's radius. Values greater than 1, will drift further and further from the target entirely, while smaller than 1 will bring it closer to its originally chosen start position.
**If this is set to ''FALSE'' then it is as though it were firing at a target with a 300m radius at a 300m distance. A value of 1 corresponds to 45 degrees, which it will start at regardless of the distance of the target. Values greater than 1 will increase beyond 45 degrees but will never exceed 90 degrees
**Syntax: '''''Boolean''''', yes or no, Default: No

*'''+Continuous Rotation:'''
**This defines the degrees per second that the beam will rotate while it is firing.
**Syntax: '''''Float''''', degrees per second
*'''+Continuous Rotation Axis:'''
**This defines the axis about which the beam will continuously rotate. Options are:
***'''START POSITION BEFORE OFFSET''', the beam will rotate about the start position before the offset or randomness were applied. A beam which does not slash (end position paramters omitted), but is offset and rotates about this axis will trace out circles, for instance.
***'''END POSITION BEFORE OFFSET''', as above but for the end position.
***'''START POSITION AFTER OFFSET''', the beam will rotate about the final start position after offset and randomness have been applied. If this beam slashes (end position paramters specified) it will trace out a spiral.
***'''END POSITION BEFORE OFFSET''', as above but for the end position.
***'''CENTER''', the beam will rotate about the center of the target.

*'''+Burst Rotation Pattern:'''
**Defines a list of rotations, for the final start and end positions to be performed right before firing for each specific shot in a burst (will not rotate the beam while firing). '''You will not be warned for failing to give this weapon burst capability''', because on spawned or subspace strike beams, providing a pattern has the additional effect of spawning multiple copies of this weapon all at once, each one corresponding to another entry in the pattern.
**For instance, a standard slash with a rotation pattern of (0, 180) will cause the beam weapon to slash back and forth, or in a scissor pattern if the burst is very short and the beams fire at similar times.
**(0,120,240) will have 3 slashes in a triangular pattern.
**If a RANDOM ON/OFF SHIP option has been chosen for the start or end positions, the "burst shares random target" flag may be used so all shots in the burst share the same random position.
**Syntax: '''''List of Floats''''', degrees. Example: (0, 90, 180, 270)
*'''+Burst Rotation Axis:'''
**The axis about which to rotate for the burst rotation pattern. Options are:
***'''START POSITION BEFORE OFFSET''', the beam will be rotated about the start position before the offset or randomness are applied.
***'''END POSITION BEFORE OFFSET''', as above but for the end position.
***'''START POSITION AFTER OFFSET''', the beam will be rotated about the final start position after offset and randomness have been applied.
***'''END POSITION BEFORE OFFSET''', as above but for the end position.
***'''CENTER''', the beam will be rotated about the center of the target.
*'''Per Burst Rotation:'''
**Will rotate the final start and end positions, possibly in addition to the burst rotation pattern, for each burst of the beam, or every shot if not a burst weapon.
**Syntax: '''''Float''''', degrees.
*'''+Per Burst Rotation Axis:'''
**The axis about which to rotate for the per burst rotation. Options are:
***'''START POSITION BEFORE OFFSET''', the beam will be rotated about the start position before the offset or randomness are applied.
***'''END POSITION BEFORE OFFSET''', as above but for the end position.
***'''START POSITION AFTER OFFSET''', the beam will be rotated about the final start position after offset and randomness have been applied.
***'''END POSITION BEFORE OFFSET''', as above but for the end position.
***'''CENTER''', the beam will be rotated about the center of the target.
}}
{{Table232|
*'''+Firing Length Effect:'''
*Specifies the [[Particle Effects|particle effect]] which will be created along the entire active length of the beam while it is firing and active.
*Note that the +Number for the effect used will be ''per kilometer of length''.
*Syntax: '''String''', the particle effect name
}}
{{Table232|
*'''+Paused Length Effect:'''
*Specifies the [[Particle Effects|particle effect]] which will be created along the length of the beam while it is firing, but in between bursts of a type 4 anti-fighter beam.
*Note that the +Number for the effect used will be ''per kilometer of length''.
*Syntax: '''String''', the particle effect name
}}
{{Table212|
*'''+Beam Flags:'''
*Extra flags specific to beams
**'''burst shares random target''', all shots from this beam weapon in the same burst will target the same random point (or slash direction)
**'''track own texture tiling''', the 'U' position of the beam texture, whose speed is set by '''+Translation:''' below, is tracked independently, rather than being shared among all beams like normal.
}}

*'''$Section:'''
**Beams are made up of up to five sections layered atop one another to create the effect. Each section has its own parameters.
{{Table3610|
:*'''+Index:'''
:**Field used to define with [[Modular Tables]] the beam section which is edited.
:**Only valid when editing beam sections that already exist in other tables. Attempting to index new sections will generate warnings, adding new sections is the default behavior for un-indexed sections.
:**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
{{Table3613|:**Not used in current builds. Settings entered here will have no effect.}}
:**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
{{Table3613|:**Not used in current builds. Settings entered here will have no effect.}}
:**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. (Zadd can be safely ignored; it actually does nothing.)
:**Syntax: '''''Float'''''
{{Table3610|
:*'''+Tile Factor:'''
:**Defines the beam texture tiling factor. Second number defines the tiling 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:===
{{Table3610|
*Defines a particle spew effect for the given weapon
}}{{Table3613|
*'''+Index:'''
**indicates which spewer to add/edit/delete. may be 0-3. used for xmt compatibility.
**Syntax: '''''Integer'''''
*'''+Remove'''
**removes spewer at +Index: (requires +index:)
*'''+Type:'''
**type of particle spew
**Syntax: '''''String'', Default, Helix, Sparkler, Ring, or Plume '''
}}{{Table3610|
*'''+Count:'''
**Defines how many particles are spawn when they are ready to be created (at each +Time: interval)
**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
**typically controls how big the effect is or how fast it moves away from the weapon path on a perpendicular (or sometimes arbitrary) axis.
**helical spews and rings use this value to control how fast the particle helix moves away from the central axis.
**sparklers use this to control how fast particles move away from the spawn point, in any direction
**plumes use this to set the diameter of the disk across which particles are spawned
**Syntax: '''''Float'''''
}}{{Table3613|
*'''+Z Scale:'''
**for sparklers, allows you to elongate the effect to surround other effects, like lasers. essentially a length multiplier
**for plume, it multiplies against +scale to set the plume to spread or converge, zero would be full convergence, 1 would be straight flight, and bigger numbers would cause particles to diverge from the disk.
**Syntax: '''''Float'''''
*'''+Rotation Rate:'''
**used only by helical spews, controls how many rotations per second the helix makes
**Syntax: '''''Float'', may be negative, useful for setting up 2 spews that spin in opposite directions'''
*'''+Offset:'''
**position of effect with regards to the weapon center
**Syntax: '''''Vector'''''
*'''+Initial Velocity:'''
**to indicate both direction and speed of particle effects regards to the weapon velocity and +scale:
**Syntax: '''''Vector'''''
}}{{Table3610|
*'''+Bitmap:
**Defines the animation used to create the particle spew effect
**Syntax: '''''String''''', filename}}

===$Tag:===
*Allowed for secondary weapons
{{Table3610|
*Allowed for primary weapons and secondary weapons}}

*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 illuminates 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.
{{Table3610|
*TAG Level 3 allows the weapon to trigger [[Weapon.tbl#$SSM:|SSMs]]}}

*Syntax: '''''Integer''''' '''''Float''''', TAG level and seconds respectively
*'''Note''': TAG will not trigger unless the weapon in question has a non-zero damage value.

===$SSM:===
{{Table3610|
*Defines the weapons SSM index number.
*Requires [[Weapons.tbl#$Tag:|TAG level 3]] or a targeting beam.
*Syntax: '''''Integer'''''}}
{{Table373|
*Now also accepts SSM strike names.
*Syntax: '''''String'''''}}

===$FOF:===
{{Table3610|
*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}}

====+FOF Spread Rate:====
{{Table37|
*Defines the spread rate of the field of fire. This controls how the FOF increases over time while the weapon is firing.
*Syntax: ''''''Float'''''', rate}}

====+FOF Reset Rate:====
{{Table37|
*Rate at which the spread decreases if the weapon isn't firing.
*Syntax: ''''''Float'''''', rate
*This is required if '''+FOF Spread Rate:''' is present}}

====+Max FOF:====
{{Table37|
*The maximum FOF. After the FOF reaches this value it will not increase any further.
*Syntax: ''''''Float'''''', degrees. Must be greater than or equal to zero.
*This is required if '''+FOF Spread Rate:''' is present}}

===$Shots:===
{{Table3610|
*Defines the number of shots every time the weapon is fired.
*Works only for primary weapons
*Syntax: '''''Integer''''', number of shots}}

===$decal:===
{{Table3610|
*Defines impact decals if they are in use
*'''+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}}
{{Table3613|
*Feature removed - table parsing retained to maintain compatibility}}

===$Impact decal:===
{{Table190|
*Defines an impact decal (think bullet impact/scorch mark) using the new system introduced in FSO 19.0.0.
**Syntax: '''''String''''', this must match to one of the entries in a [[Decals|decal tbm]].
*'''+Radius:'''
**Syntax: '''''Float''''', Radius of the impact decal; default is 1.0
*'''+Lifetime:'''
**Syntax: Either '''''Eternal''''' or '''''Float''''', lifetime in seconds
}}
{{Table224|
*'''+Use Random Rotation:'''
**Syntax: '''''Boolean''''', Whether or not a random rotation is added to the decal; default is NO
}}

===$Transparent:===
{{Table3610|
*Defines weapon effect as transparent. Enables optional fields for 'alpha animations'
*'''+Alpha:'''
**Defines the strength 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 Hitpoints:===
{{Table3611|
*Defines the amount of hitpoints a weapon has.
*Weapons with '''"bomb"''' flag have 50 hitpoints by default
*Giving weapon hitpoints makes it possible for the weapon to be shot down or be destroyed by EMP.
**Syntax: '''''Integer'''''
}}

===$Armor Type:===
{{Table3613|
*REQUIRES ADDITIONAL TABLE. Defines the armor type for the weapon. This works exactly like ship armor types.
**Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]
}}

===$Burst Shots:===
{{Table3611|
*Defines the number of shots in a burst
*Shots in a burst use shorter ( '''$Burst Delay:''' ) delay than usually
*If this weapon is cycling each individual firing event counts as one burst shot, so bursts end sooner in time for large banks than small.
**Syntax: '''''Integer'''''}}

===$Burst Delay:===
{{Table3611|
*Defines the time in milliseconds between the shots in a burst
**Syntax: '''''Integer'''''}}

===$Burst Flags:===
{{Table3611|
*Defines the flags used to define the burst firing behaviour
**Syntax: ( '''''String''''' '''''String''''' ), list of flags
**Available burst flags:
***'''"fast firing"''', acts as if '''same turret cooldown''' flag would be used between the shots in the burst.
***'''"random length"''', makes AI to fire burst of random length (from 1 to burst shots).}}
{{Table202|'''"resets"''', as long as a full fire wait has passed since last fired, the burst is reset and can be fired in full again.}}

===$Thruster Flame Effect:===
{{Table3611|
*Defines the filename of the effect used on the modeled thruster of the missile
**Syntax: '''''String''''', filename}}

===$Thruster Glow Effect:===
{{Table3611|
*Defines the filename of the effect used on the glow type effect of the missile
**Syntax: '''''String''''', filename}}

===$Thruster Glow Radius Factor:===
{{Table3611|
*Defines the radius multiplier for the thruster's glow type effect
**Syntax: '''''Float'''''}}

===$Failure Rate:===
{{Table38|
*Defines the random chance that the weapon will fail to fire, or spawn the substitute below if specified.
**Syntax: '''''Float''''', 0 - 1

====+Failure Substitute:====
*Defines the weapon to substitute when the weapon 'fails'.
**Syntax: '''''String''''', Weapon
}}

===$On Create:===
{{Table212|
*Defines an [[Action System|action system]] program set to be executed when a weapon of this type is created. Only applicable to laser and missile style weapons.
}}

===$Animations:===
{{Table220|
*The new way of specifying triggered animations for weapons. Weapon needs to be a modelled weapon for animations.
*See [[Animation.tbl]]
*Syntax: '''''( "String" "String" )''''', names of the animations for this ship, as defined in the Animation.tbl
**Example: ( "wingflap" "docksequence" )
}}

===$Substitute:===
{{Table3613|
Defines a pattern of ammo to substitute for primary or secondary weapons. '''$Substitute:''' can be repeated any number of times (so you could make something like a rainbow laser with several ammo substitutions, for example). If neither ''+period'' or ''+index'' is specified, it is assumed to be equivalent to ''+index: '''0'''''.

*Syntax: '''''Weapon Name'''''
*'''Swarm missiles act in a strange way when used with $Substitute, use at your own risk.'''}}

{{Table3615|
Turrets can use $Substitute as well.
}}
====+period:====
{{Table3613|
FSO will substitute '''Weapon Name''' every ''period'' shots.

*Syntax: '''''Positive Integer'''''
*'''You may not define both +period and +index for the same $Substitute entry'''}}
=====+offset:=====
{{Table3613|
A suboption of +period, offsets the substitute pattern according to the launched ammo. For example, an offset of 3 and a period of 4 will substitute on the 3rd ammo launched, and then every 4th ammo after that.

*Syntax: '''''Positive Integer'''''}}

====+index:====
{{Table3613|
FSO will substitute the '''Weapon Name''' at firepoint ''index'' in the shot pattern. Similar to carefully using both +period and +offset, but is not affected by ships with different firepoint numbers. i.e. Firepoint ''index'' will always have the substitution, while +period and +offset will cycle at different rates dependant on the number of firepoints.'''

*Syntax: '''''Positive Integer'''''

*'''You may not define both +period and +index for the same $Substitute entry'''

*'''Indexes start at 0 for the first weapon'''

*'''If the first index you specify is higher than 0, it will also be used for the indexes before it.'''

}}

===$Custom data:===
{{Table220|
Defines a set of custom data that for this weapon class, which can then be accessed through Lua scripts. There can be any amount of +Val: entries. It requires a $end_custom_data entry at the end.
Check the scripting documentation of Weapon Class to find the CustomData Lua Table.
====+Val:====
Specifies a custom data value and its name, in the format

+Val: Name Value

These values will always be strings of text. If you use them in Lua as other types of value, you might need to convert them in the script.

====$end_custom_data====
Mandatory entry to indicate that the Custom Data list has ended. }}

==Weapons.tbl 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.
*The flag will parse without a value, using a default of 10.
{{Table3610|
*Multiple spawn types can be defined for a single 'carrier' weapon up to maximum of 5 different weapons}}

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

==="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. Also the AI will not try to hit fighters with it, but only if the weapon is in a turret or is a secondary. If the weapon is a primary in a fighter then there are no targeting restrictions. See [[Weapons.tbl#.22capital.2B.22|capital+]] instead.

==="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 target-able with the B key and interceptable by AIs
** Has been long thought to make the AI prefer this weapon against large ships, but in fact has no effect on AI weapon selection.

==="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.
{{Table3610|
*'''EXTREMELY IMPORTANT NOTE:'''
**Whenever you plan to use a weapon as a player one in your campaign or missions, '''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
{{Table3610|
*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]]

==="Vampiric"===
{{Table224|
*Heals shooter upon dealing hull damage to target
*Can be defined with [[Weapons.tbl#$Vampiric Healing Factor:|Vampiric Healing Factor]]}}

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

==="Corkscrew"===
*Makes this weapon spiral AND swarm 4.
{{Table3610|
*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"===
* Does nothing

==="puncture"===
*Reduces hull damage by 75%
The AI will prefer these weapons for anti-subsystem use

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

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

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

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

==="local ssm"===
{{Table3610| }}

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

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

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

==="small only"===
{{Table3610|
*Causes AI to use the weapon only on small targets (fighters, bombers etc.) Only applies to the target selection of turrets, has no effect on the behavior of fighters picking primary and secondary bank weapons.}}

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

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

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

==="smart spawn"===
{{Table3611|
*Forces turret fired spawn weapon of this type to be fired like normal weapons.}}

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

==="no emp kill"===
{{Table3611|
*Defines the weapon (with hitpoints) to be immune to automatic EMP destruction.}}

==="untargeted heat seeker"===
{{Table3611|
*Defines the weapon as a heatseeker type missile which acquires its target by itself.}}

==="no radius doubling"===
{{Table3611|
*Prevents weapon radius from being doubled when doing collision test. Makes bombs harder to intercept.}}

==="no subsystem homing"===
{{Table3611|
*Prevents weapon from acquiring a subsystem as its target. Missile homing points are spread over the target ship.}}

==="no lifeleft penalty"===
{{Table3611|
*Prevents weapon lifetime from being penalized if the angle to the target is too big.}}

==="can be targeted"===
{{Table3611|
*Allows weapon to be targeted by player. Does not influence AI}}

==="show on radar"===
{{Table3611|
*Allows weapon to be visible on the radar}}

==="show friendly on radar"===
{{Table3611|
*Allows friendly, otherwise visible to radar weapon, to be visible on player radar}}

==="hide from radar"===
{{Table3614|
*Prevents weapon from being visible on the radar}}

==="capital+"===
{{Table3613|
*Tells AI fighters/bombers to use this weapon only on capital ships. Has no effect on turret AI.}}

==="chain external model fps"===
{{Table3613|
*Tells game to keep switching external model firingpoints when firing}}

==="external model launcher"===
{{Table3613|
*Tells game that the external model is a launcher so that it would be kept static without loading motion}}

==="takes blast damage"===
{{Table3613|
*Weapon takes damage from weapon blasts}}

==="takes shockwave damage"===
{{Table3613|
*Weapon takes damage from shockwaves}}

==="ciws"===
{{Table3615|
*Weapon can deal shockwave/blast damage to bombs, regardless of whether the target weapons have the "take blast/shockwave damage" flags.}}

==="render flak"===
{{Table3615|
*Normally, flak shells are not rendered. This flag switches rendering on for those weapons.}}

==="anti-subsystem beam"===
{{Table3615|
*Beam weapons with this flag can target subsystems on enemy ships, just like normal weapons.}}

==="no primary linking"===
{{Table3615|
*Primary weapons with this flag can not be linked with other weapons.}}

==="same emp time for capships"===
{{Table37|
*capships affected by this weapon will use the tabled EMP time rather than the fixed retail value (7.5 secs)}}

==="no primary linked penalty"===
{{Table371|
*Primary weapons with this flag do not incur the retail linked fire penalty}}

==="no homing speed ramp"===
{{Table371|
*Locked homing weapons will not perform the standard 1 second long acceleration when fired. Note that use of $Acceleration Time is '''not''' affected by this flag.}}

==="pulls aspect seekers"===
{{Table371|
*If an aspect seeker is grabbed by this countermeasure the missile will follow the countermeasure instead of going into dumbfire mode.
'''Only valid for countermeasures!'''}}

==="turret interceptable"===
==="fighter interceptable"===
==="interceptable"===
{{Table371|
*Allows turrets/fighters/both (respectively) to shoot at this weapon without requiring it to be a bomb. If this is the first time this weapon has been defined, it also gives it a default of 25 hitpoints so that it can be shot down.
'''If you use a TBM to give this flag to an existing weapon, you'll need to specify hitpoints manually (unless you want it to be unkillable but still draw defensive fire).'''}}

==="aoe electronics"===
{{Table372|
*Apply electronics effect across the weapon's entire area of effect instead of just on the impacted ship}}

==="apply recoil"===
{{Table373|
*A ship that fires a weapon with this flag will experience a recoil effect, slowing the ship down and, with lighter strikecraft, inducing some rotation if the firing points are offset from the center of mass.}}

==="don't spawn if shot"===
{{Table373|
*Prevents parent weapons from spawning children in the even of the parent weapon being shot down.}}

==="die on lost lock"===
{{Table373|
*Aspect seeking missiles (only, not heat seekers) will detonate upon losing their lock. Currently they only lose lock if decoyed by a countermeasure, AND "pulls aspect seekers" or similar is not set. The detonation will use their "dinky" explosion (i.e. same as if ran out of lifetime).}}

==="no doublefire"===
{{Table202|
*Prevents dual-firing of secondary weapons. If the ship tries to dual-fire a weapon with this flag they are set back to single fire.}}

==="no impact spew"===
{{Table202|
*Turns off the usual spew effects that occur on the impacted ship when a weapon hits it.}}

==="require exact los"===
{{Table202|
*Prevent AI form firing this weapon from a turret or as a secondary weapon if there is no clear line of sight from the weapons firing point to its targeted ship (center). Note that this may keep the weapon trained on a target out of sight while another target may be available to shoot.}}

==="can damage shooter"===
{{Table212|
*This weapon can collide with and directly damage the original shooter of this weapon (even if it was spawned), which is not normally possible.}}

==="heals"===
{{Table214|
*This weapon uses its $Damage value to heal its target(s) instead of damaging them.
*This works very similarly to damage, the armor/shield/subsystem factors apply to healing as well as do armor classes. However, there are some caveats. 
*Healing will ''always'' carry. Unlike damage, which first has to go through the shield, has damage subtracted, then damages subsystems, has damage subtracted, then finally damages the hull if any damage remains, healing will apply in full to hull, shield, and subsystems (factors or armor classes notwithstanding). A weapon with 100 'healing' will attempt to apply that healing to the hull, shield and nearby subsystems to the impact. Even if the weapon only heals hull, it will still do so even if it strikes the shield.}}

==="secondary no ammo"===
{{Table220|
*If this is a secondary weapon, it does not need to consume any ammo, and will not display ammo in the weapon HUD gauge, etc.}}

==="no collide"===
{{Table220|
*This weapon will not collide with any other object.}}

==="multilock target dead subsys"===
{{Table220|
*If this is a multilock weapon, dead subsystems will be treated as just as valid targets as alive ones.}}

==="no evasion"===
{{Table220|
*AI will not attempt to evade this weapon when fired at them}}

==="no_fred"===
{{Table224|
*Weapon will not appear in any of the FRED dropdown lists for weapon classes.}}

==="detonate on expiration"===
{{Table232|
*Primary weapon will detonate as if hitting a target when it reaches the end of its lifetime - just like a secondary weapon does by default.}}

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

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

===$Velocity:===
*Defines the speed 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]]

Game settings.tbl

2022-09-16T23:17:54Z

AdmiralRalwood: Adding default/inherited shockwave damage types.

{{SCP_table}}
{{TableVersionGit|2022-09-09|bb232382cf7401d6728a3614583e8e3c7d893790}}
{{Tables}}
The '''game_settings.tbl''', also known as mod.tbl, defines options that can be changed globally. All settings are optional.

This table is one of the [[Modular Tables]] and can be extended with xxx-mod.tbm

==#GAME SETTINGS==
Contains settings that affect how the engine works.

===$Target Version:===
{{Table373|
Specifies the minimum version of FreeSpace Open that this mod supports. If the version specified here is greater than the version of the current build, an error message is displayed.
}}
{{Table381|
The $Minimum version option has been renamed to $Target Version. The old name is kept with the same functionality for backwards-compatibility.

The target version specifies what version of the FSO engine this mod was created for. It will be used by the engine to enable or disable backwards-incompatible changes by default. The default value is 2.0 which specifies that the mod targets the retail engine version.
}}

====+Major:====
{{Table373|
Required. Sets the major component of the target version.
*Syntax: '''''Integer'''''
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Minor:====
{{Table373|
Required. Sets the minor component of the target version.
*Syntax: '''''Integer'''''
*Example: '''''7''''' (for a minimum version of 3.7.3.20151121)
}}

====+Build:====
{{Table373|
Required. Sets the build component of the target version.
*Syntax: '''''Integer'''''
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Revision:====
{{Table373|
Sets the revision component of the target version. If no revision is given then all builds of that release are supported (even nightly builds if there are any).
For nightly builds this is the date in YYYYMMDD format.
*Syntax: '''''Integer'''''
*Example: '''''20151121''''' (for a minimum version of 3.7.3.20151121)
}}

===$Window title:===
{{Table382|
Specifies the name of the FSO window when this mod is running. If blank or unspecified, the window will have the default title of "FreeSpace 2".
*Syntax: '''''String'''''
}}

===$Window icon:===
{{Table382|
Specifies the icon filename of the FSO window when this mod is running. If blank or unspecified, the window will have the default icon.
*Syntax: '''''String'''''
}}

===$Mod title::===
{{Table224|
Specifies the title of the mod and will be displayed at the mainhall near the FSO version.
*Syntax: '''''String'''''
}}

===$Mod version:===
{{Table224|
Specifies the version of the mod and will be displayed at the mainhall near the FSO version. Can be a string or it can be semantic versioning such as 2.0.0.
*Syntax: '''''String'''''
}}

===$Unicode mode:===
{{Table382|
Enabled the Unicode text mode for this mod. In Unicode mode all text is assumed to be UTF-8 encoded Unicode and certain features are disabled if they do not have full Unicode support. Most notably, if this is enabled then the engine will no longer support the old bitmap fonts that were used by Retail FreeSpace. Only the newer TrueType fonts will be supported.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

==#LOCALIZATION SETTINGS==
Contains various settings related to localization and language support.

===$Use tabled strings for the default language:===
{{Table202|
Causes the game to use the text in strings.tbl and tstrings.tbl even when the current language is English. By default, the game will use the literal text in the source code and the data files (tables and missions) and will not look up the entry when the language is English. For other languages, the translation is always used, if it exists, regardless of this setting.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Don't pre-empt training message voice:===
{{Table214|
Prevents training messages from being interrupted by other training messages. If a training message has a voice file associated with it, or simulated speech is active, the next message will not be played until the current message has finished.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

==#CAMPAIGN SETTINGS==
This group contains various Campaign related settings and overrides.

===$Default Campaign File Name:===
Defines which campaign will be selected by default for new pilots. A file extension is not needed and, if present, is removed by the code.
*Syntax: '''''String'''''

===#Ignored Campaign File Names===
Defines which campaigns, if present, will not appear in the Campaign Room. In the original implementation, only single-player campaigns could be ignored and file extensions were required, but see below.
{{Table371|As of 3.7.1, file extensions are not required and, if present, are removed by the code.}}
{{Table382|As of 3.8.2, file name comparisons are not case sensitive and multiplayer campaigns can be ignored.}}
====$Campaign File Name:====
File name of the campaign to ignore. Multiple entries may exist.
*Syntax: '''''String'''''

===#Ignored Mission File Names===
{{Table382|Defines which standalone missions, if present, will not appear in the Tech Room or Multiplayer Lobby. Both single-player and multiplayer missions can be ignored, but missions which appear in a campaign cannot. File extensions are not required and, if present, are removed by the code. File name comparisons are not case sensitive.
====$Mission File Name:====
File name of the mission to ignore. Multiple entries may exist.
*Syntax: '''''String'''''
}}

===$Red-alert applies to delayed ships:===
{{Table372|Controls whether red-alert saved statistics (hitpoints, weapons, subsystem strengths) will be restored for ships that are not present at mission start.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

==#HUD SETTINGS==
This group contains various HUD behavior settings and overrides

===$Directive Wait Time:===
*Defines how long the game will wait before displaying a directive.
*Syntax: '''''Integer'''''
*Values: '''''Greater than or equal to 0 ms'''''

===$Cutscene camera displays HUD:===
Show the HUD when the cutscene camera is enabled.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Cutscene camera disables HUD: and had a default of YES.

===$Full color head animations:===
Enables full-color head ANIs. Normal head ANIs will appear in gray.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Color head animations with hud colors: and had a default of YES.

===$Don't automatically select a turret when targeting a ship:===
{{Table220|Uses FS1 behavior where targeting a new ship did not target any turrets. In FS2 a turret is automatically targeted.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Supernova hits at zero:===
{{Table222|
Adjusts the HUD timer so that the timer reaches zero when the supernova hits the player. The actual timing is not affected -- whether the flag is enabled or not, the supernova will always hit the player when 5 seconds remain in the time specified in the sexp.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Always warn player about unbound keys used in Directives Gauge:===
{{Table222|
Ensures that the "Key Unbound" message will pop up for a directive with an unbound key in any single-player mission, not just a training mission. Note, that the default string (index 426) will still say "Warning\nYou have no control bound to the action \"%s\". You must do so before you can continue with training." Thus, it is advised to change the string at index 426 using the -lcl.tbm to "Warning\nYou have no control bound to the action \"%s\". You must do so before you can continue with this mission."
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

==#SEXP SETTINGS==
This group contains SEXP settings and overrides.

===$Loop SEXPs Then Arguments:===
Flips how when-argument settings loop. See: [http://www.hard-light.net/forums/index.php?topic=79602.0 SEXP Argument changes via mod.tbl]
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

===$Use Alternate Chaining Behavior:===
When set, this allows all events in a chain to repeat, instead of only the last one. It makes the event chaining behavior act as people expected it to be in [http://scp.indiegames.us/mantis/view.php?id=82 Mantis #82].
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

===$Use host orientation for set-camera-facing:===
{{Table220|When set, this will take into account the host orientation for cutscene cameras. This is a bugfix for [https://github.com/scp-fs2open/fs2open.github.com/issues/3889 GitHub issue #3889].
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Show-subtitle uses pixels:===
{{Table222|When set, SEXPs which display subtitles will read their arguments as pixels, not percentages. If <code>$Show-subtitle base resolution:</code> is set, these pixels will be scaled up or down as needed.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Show-subtitle base resolution:===
{{Table222|When set, subtitles are assumed to display at the appropriate size in the specified resolution, and will be scaled up or down if the current screen resolution is different. If this is not set, or is set to a resolution less than (640, 480), subtitles will not be scaled.
*Syntax: '''''(Integer, Integer)'''''
*Default Value: '''''(-1, -1)'''''}}

==#GRAPHICS SETTINGS==
This group contains settings related to graphics.

===$Enable External Shaders:===
Enables the use of external shader files. By default, the engine will use the built-in shaders.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

===$Default Detail Level:===
{{Table3615|
Determines which graphics detail level preset (low, medium, high, very high) acts as the default for new pilots.
*Syntax: '''''Integer''''' (0-3)
*Default Value: '''''3''''' (very high)}}

===$Briefing Window FOV:===
{{Table371|
Determines the FOV in the briefing Icon window. Retail default for this is 0.29375; some previous versions of FSO used a value of 0.5.
*Syntax: '''''Float''''' (0.0 to 1.0)
*Default Value: '''''0.29375'''''}}

===$Generic Pain Flash Factor:===
{{Table373|
Determines the intensity of the pain red flash when the player is hit.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$Shield Pain Flash Factor:===
{{Table373|
Determines the intensity of a pain flash when the player's shields are hit. Color will match the current ships shield color defined in ships.tbl. A value of 0 will give retail behavior (no shield effect). Positive values will cause the effect to start at full intensity at full shields and go to next to no intensity at zero shields. Negative values will cause no effect at full shields and full effect at no shields. Values should be kept between -1.0 and 1.0 for good pilot visibility.
*Syntax: '''''Float'''''
*Default Value: '''''0.0'''''}}

===$BMPMAN Slot Limit:===
{{Table382|
Determines the maximum number of textures that can be loaded simultaneously. This includes every frame of an animation, unless that animation is streaming (e.g. command briefing animations, message talking heads, etc). Also includes dynamically-created textures (used internally for various functions).
*Syntax: '''''Int'''''
*Values: '''''Greater than or equal to 3500'''''
*Default Value: '''''4750'''''}}

===$EMP Arc Color:===
{{Table382|
Allows custom RGB color values to be set for the EMP lightning arc effect.
*'''+Primary Color Option 1:'''
**The RGB color of the first primary color for the EMP lightning arc effect.
**The actual lightning arc color shown in-game is randomly selected between the first and second primary color.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (64, 64, 5)
*'''+Primary Color Option 2:'''
**The RGB color of the second primary color for the EMP lightning arc effect.
**The actual lightning arc color shown in-game is randomly selected between the first and second primary color.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (128, 128, 10)
*'''+Secondary Color Option 1:'''
**The RGB color of the secondary color for the EMP lightning arc effect.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (255, 255, 10)
}}

===$Damage Arc Color:===
{{Table382|
Allows custom RGB color values to be set for the damage lightning arc effect.
*'''+Primary Color Option 1:'''
**The RGB color of the first primary color for the damage lightning arc effect.
**The actual lightning arc color shown in-game is randomly selected between the first and second primary color.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (64, 64, 255)
*'''+Primary Color Option 2:'''
**The RGB color of the second primary color for the damage lightning arc effect.
**The actual lightning arc color shown in-game is randomly selected between the first and second primary color.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (128, 128, 255)
*'''+Secondary Color Option 1:'''
**The RGB color of the secondary color for the damage lightning arc effect.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (64, 64, 5)
}}

===$Requires Rendering Feature:===
{{Table210|Needs description}}

===$Render player muzzle flashes in cockpit:===
{{Table212|
Determines whether muzzle flashes will be shown within the cockpit view.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Glowpoint nebula visibility factor:===
{{Table220|
*Specifies the degree to which glowpoints are affected by nebula fog. 1.0 is exactly the same as regular ship hull obscurity, higher means they stay visible for longer.
*Syntax: '''''Float'''''
*Default Value: 1.2}}

===$Shield nebula visibility factor:===
{{Table220|
*Specifies the degree to which shield effects are affected by nebula fog. 1.0 is exactly the same as regular ship hull obscurity, higher means they stay visible for longer.
*Syntax: '''''Float'''''
*Default Value: 1.2}}

===$Thruster nebula visibility factor:===
{{Table220|
*Specifies the degree to which thruster flares are affected by nebula fog. 1.0 is exactly the same as regular ship hull obscurity, higher means they stay visible for longer.
*Syntax: '''''Float'''''
*Default Value: 1.5}}

===$Beams affected by nebula visibility:===
{{Table212|
Determines whether beam weapons will be faded by nebula fog.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

====+Constant visibility factor:====
{{Table220|
*Specifies the degree to which beam effects are affected by nebula fog. 1.0 is exactly the same as regular ship hull obscurity, higher means they stay visible for longer.
*Syntax: '''''Float'''''
*Default Value: 4.0}}

====+Scaled visibility factor:====
{{Table220|
*Specifies the degree to which the ''size'' of a beam effect affects its visibility. This is multiplied by the radius of the beam and added to the above for the final value. This results in larger beams being visible from farther away.
*Syntax: '''''Float'''''
*Default Value: 0.1}}

===$Weapons affected by nebula visibility:===
{{Table212|
Determines whether lasers, missiles, countermeasures, etc will be faded by nebula fog.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

====+Weapon visibility factor:====
{{Table220|
*Specifies the degree to which laser-type weapons are affected by nebula fog. 1.0 is exactly the same as regular ship hull obscurity, higher means they stay visible for longer.
*Syntax: '''''Float'''''
*Default Value: 1.3}}

====+$Trail visibility factor:====
{{Table220|
*Specifies the degree to which trails (weapon and ship contrails) are affected by nebula fog. 1.0 is exactly the same as regular ship hull obscurity, higher means they stay visible for longer.
*Syntax: '''''Float'''''
*Default Value: 1.0}}

====+Shockwave visibility factor:====
{{Table220|
*Specifies the degree to which shockwave effects are affected by nebula fog. 1.0 is exactly the same as regular ship hull obscurity, higher means they stay visible for longer.
*Syntax: '''''Float'''''
*Default Value: 2.5}}

===$Particles affected by nebula visibility:===
{{Table212|
Determines whether particle effects, including impact effects, will be faded by nebula fog.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

====+Constant visibility factor:====
{{Table220|
*Specifies the degree to which particle effects are affected by nebula fog. 1.0 is exactly the same as regular ship hull obscurity, higher means they stay visible for longer.
*Syntax: '''''Float'''''
*Default Value: 1.0}}

====+Scaled visibility factor:====
{{Table220|
*Specifies the degree to which the ''size'' of a particle effect affects its visibility. This is multiplied by the radius of the particle and added to the above for the final value. This results in larger particles being visible from farther away.
*Syntax: '''''Float'''''
*Default Value: 0.08}}

===$Fireballs affected by nebula visibility:===
{{Table212|
Determines whether fireballs from ship explosions will be faded by nebula fog.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

====+Constant visibility factor:====
{{Table220|
*Specifies the degree to which fireballs are affected by nebula fog. 1.0 is exactly the same as regular ship hull obscurity, higher means they stay visible for longer.
*Syntax: '''''Float'''''
*Default Value: 1.2}}

====+Scaled visibility factor:====
{{Table220|
*Specifies the degree to which the ''size'' of a fireball affects its visibility. This is multiplied by the radius of the fireball and added to the above for the final value. This results in larger fireballs being visible from farther away.
*Syntax: '''''Float'''''
*Default Value: 0.08}}

===$$Shadow Quality Default::===
{{Table220|
Sets the default level for shadow quality if the 'enable_shadows' command line is used and 'shadow_quality' is not used. By default, the FSO will set the shadow detail level to 2. Valid values are 0 (shadows disabled), 1 (Low, 512x512 shadow map), 2 (Medium, 1024x1024 shadow map), 3 (High, 2048x2048 shadow map), or 4 (Ultra, 4096x4096). Note, the command line 'shadow_quality' will override any value set here.
*Syntax: '''''Integer'''''
*Default Value: '''''2'''''}}

===$Shadow Cascade Distances:===
{{Table214|
Sets the distances that the shadow map for the game scene uses. Float values must all be greater than 0 and successively larger than each consecutive value.
*Syntax: '''''List of floats'''''
*Default Value: '''''(200.0, 600.0, 2500.0, 8000.0)'''''}}

===$Shadow Cascade Distances Cockpit:===
{{Table214|
Sets the distances that the shadow map for the cockpit pass scene uses. Will only shadow the cockpit model, and does not interact with the external game scene shadow map. Float values must all be greater than 0 and successively larger than each consecutive value.
*Syntax: '''''List of floats'''''
*Default Value: '''''(0.25, 0.75, 1.5, 3.0)'''''}}

====+Scaled visibility factor:====
{{Table220|
*Specifies the degree to which the ''size'' of a fireball affects its visibility. This is multiplied by the radius of the fireball and added to the above for the final value. This results in larger fireballs being visible from farther away.
*Syntax: '''''Float'''''
*Default Value: 0.08}}

====$Minimum Pixel Size Thrusters:====
{{Table220|
*Specifies the smallest pixel size that thrusters will be rendered. Setting this > 0 can be expensive in larger missions.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

====$Minimum Pixel Size Beams:====
{{Table220|
*Specifies the smallest pixel size that beams will be rendered. Setting this > 0 can be expensive in larger missions.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

====$Minimum Pixel Size Muzzle Flashes:====
{{Table220|
*Specifies the smallest pixel size that muzzle flashes will be rendered. Setting this > 0 can be expensive in larger missions.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

====$Minimum Pixel Size Trails:====
{{Table220|
*Specifies the smallest pixel size that trails will be rendered. Setting this > 0 can be expensive in larger missions.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

====$Minimum Pixel Size Lasers:====
{{Table220|
*Specifies the smallest pixel size that lasers will be rendered. Setting this > 0 can be expensive in larger missions.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

==#NETWORK SETTINGS==
This group contains network-related settings

===$FS2NetD port:===
*(description required)

===$Default object update level for multiplayer:===
{{Table220|
Sets the distances default object update rate for multiplayer matches. By default, the FSO will set the object update level to 2. Valid values are 0 (Low), 1 (Medium), 2 (High), 3 (LAN). FSO caps the bandwidth it uses based on these settings, but they were designed for connections from 1999. LAN has the least restrictive limits and does not require an actual LAN connection. Also, if a player's connection is within the dial-up speed range then game auto force the use of the lowest level during a match.
*Syntax: '''''Integer'''''
*Default Value: '''''2'''''}}

==#SOUND SETTINGS==
This group contains sound-related settings

===$Default Sound Volume:===
{{Table371|
*Defines the default sound fx volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0
*Default Value: '''''1.0'''''}}

===$Default Music Volume:===
{{Table371|
*Defines the default music volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0
*Default Value: '''''0.5'''''}}

===$Default Voice Volume:===
{{Table371|
*Defines the default voice volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0
*Default Value: '''''0.7'''''}}

==#FRED SETTINGS==
This group contains settings for FRED.

===$Disable Hard Coded Message Head Ani Files:===
{{table371|
If set, FRED will not fill the head ani selection in the Event Editor with the retail head ani filenames.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Enable scripting in FRED:===
{{table382|
If set, scripting will be enabled in FRED. Use with extreme caution. The effects of scripts on FRED have not been fully tested. You can check if a script is running in FRED by using ba.inMissionEditor().
*Default Value: '''''NO'''''}}

==#OTHER SETTINGS==
This group contains miscellaneous settings.

===$Fixed Turret Collisions:===
Makes all hits to a turret's barrels count as hits to the turret subsystem. By default, this does not happen unless the point of impact falls inside the model radius of the turret's base.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

===$Fixed Missile Detonation:===
{{Table220|
*When this flag is set, missiles which reach the center of a submodel will not detonate immediately; they will delay detonation until they have traveled another radius of the submodel.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Damage Impacted Subsystem First:===
If set, a hit to a physical subsystem will always deal damage to that subsystem first, even if another subsystem is closer to the point of impact. By default, the closest subsystem will always receive damage first.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

===$Default ship select effect:===
{{Table3615|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Default weapon select effect:===
{{Table3615|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Weapons inherit parent collision group:===
{{Table3615|
*When set to true, Weapons fired by a ship will inherit their parents' collision group setting.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Flight controls follow eyepoint orientation:===
{{Table371|
*Specifies that if the player ship's eyepoint happens to rotate into a non-standard orientation, pitch and yaw axes should stay relative to the eyepoint orientation, not the ship. Note that this does not affect the pitch/yaw turning speed, which always remains relative to the ship.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Beams Use Damage Factors:===
{{Table371|
*Specifies that beam weapons will use the tabled damage factors for Armour, Shields and Subsystems. Default is false (i.e. all factors are treated as 1.0)
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Default fiction viewer UI:===
{{Table373|
*Specifies which fiction viewer layout to use in missions that don't specify one. Possible values are as follows:
**"FS2": Standard layout. Requires (2_)fictionviewer and (2_)fictionviewer-m to be present in data\interface.
**"WCS": Moves the "Accept" button to the lower-left corner of the screen. Requires (2_)fictionviewerb and (2_)fictionviewer-mb to be present in data\interface.
**"auto": Selects "WCS" if the appropriate files are present; otherwise, selects "FS2". This is the default setting.}}

===$Movie subtitle font:===
{{Table382|
*Specifies which font should be used for displaying subtitles in the cutscene player. This should be the name given to this font in the fonts table. Since movie subtitles can contain Unicode text it is a good idea to enable Unicode mode when movie subtitles are used but this is not enforced by this option.
*Syntax: '''''String'''''}}

===$Disable built-in translations:===
{{Table382|
*Turns off hard-coded translations, e.g. Transport -> Transporter in German. All strings will either use their XSTR entry or else not be translated.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Weapon shockwave damage respects huge ship flags:===
{{Table382|
*Controls whether weapon shockwaves will respect the huge/supercap ship flags. In retail they do not.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Enable external default scripts:===
{{Table382|
*Enables the loading of external scripts with the same name as a built-in script. Otherwise, uses the version of the script included in the executable (currently, just cfile_require.lua).
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Player warpout speed:===
{{Table190|
*Defines the speed the player must reach to warp out.
*Syntax: '''''Float'''''
*Default Value: '''''40.0'''''}}

===$Target warpout match percent:===
{{Table190|
*Defines how close to the warpout speed the player needs to be to actually warp out.
*Syntax: '''''Float''''', between 0.0 and 1.0
*Default Value: '''''0.05''''' (5%)}}

===$Minimum player warpout time:===
{{Table190|
*The [[Ships.tbl#.24Warpout_Engage_Time:|default amount of time]], in seconds, warping out will take before actually starting to check whether the player is the right speed.
*Syntax: '''''Float'''''
*Default Value: '''''3.0'''''}}

===$Enable in-game options:===
{{Table190|
*Experimental mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. Requires custom assets for the in-game options menu to actually be able to change the settings.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Dinky Shockwave Default Multiplier:===
{{Table190|
*Amount of damage, as a multiple of normal shockwave damage, assigned to a weapon's [[Weapons.tbl#.24Dinky shockwave:|dinky shockwave]] by default. To get the same behavior FSO had from 2005-2019, set this to 0.25.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$Shockwaves Always Damage Bombs:===
{{Table202|
*Enables all bombs being damaged by shockwaves. Previously only those marked with flags could be damaged.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Shockwaves Damage All Object Types Once:===
{{Table202|
*Keeps any object from being damaged more than once by a shockwave. The default behavior is for asteroids and flagged missiles to be damaged every frame by the shockwave.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Shockwaves Inherit Parent Weapon Damage Type:===
{{Table224|
*When enabled, the shockwaves of weapons that have a defined damage type automatically inherit that damage type, rather than dealing "typeless" damage. As this behavior is more intuitive than when this flag is disabled, mods targeting 22.4 or newer versions of FSO will have it enabled by default.
*Syntax: '''''Boolean'''''
*Default Value: '''''True''''' for mods targeting 22.4 or newer versions of FSO, otherwise '''''False'''''}}

===$Inherited Shockwave Damage Type Added Suffix:===
{{Table224|
*When combined with "$Shockwaves Inherit Parent Weapon Damage Type:", this string is added to the inherited damage type to define the shockwave's damage type. For example, if a weapon has the damage type "heavy" and the provided suffix is "-shock", then that weapon's shockwave's damage type would default to "heavy-shock".
*Note: When defined, this also implicitly sets the equivalent value for dinky shockwaves, below.
*Syntax: '''''String'''''}}

===$Inherited Dinky Shockwave Damage Type Added Suffix:===
{{Table224|
*The same as "$Inherited Shockwave Damage Type Added Suffix:", except specifically for "dinky" shockwaves.
*Syntax: '''''String'''''}}

===$Default Shockwave Damage Type:===
{{Table224|
*If a weapon's shockwave doesn't have a damage type set, it will have this damage type instead (when "$Shockwaves Inherit Parent Weapon Damage Type:" is enabled, this will only be used if the weapon itself also doesn't have a damage type set).
*Note: When defined, this also implicitly sets the equivalent value for dinky shockwaves, below.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Default Dinky Shockwave Damage Type:===
{{Table224|
*The same as "$Default Shockwave Damage Type:", except specifically for "dinky" shockwaves.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Use Engine Wash Intensity:===
{{Table190|
*Allows the game to use the [[ships.tbl#.24Intensity::|Intensity]] value when calculating Engine Wash effects.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Swarmers Lead Targets:===
{{Table202|
*Causes swarm missiles to lead their targets by default, and will make use of [[Weapons.tbl#.2BTarget_Lead_Scaler:|Target Lead Scaler]] if specified, like normal aspect seekers.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Damage Threshold for Weapons Subsystems to Trigger Turret Inaccuracy:===
{{Table202|
*Specifies the damage threshold for when turrets become less accurate due to weapon subsystem damage. In other words, how damaged do a ship's aggregated weapons systems have to be before the turrets become inaccurate? Value must be between 0.0-1.0 (includes 0.0 and 1.0).
*Syntax: '''''Float'''''
*Default Value: '''''0.7'''''}}

===$AI use framerate independent turning:===
{{Table202|
*Without this flag, missiles turn rate is directly dependent on the current framerate. When enabled their turn rate will be consistent, with the "true" turning taken to be observed turning at 60fps. This flag also affects ships, but the instability is only apparent at extremely low framerates, and so the change will not be apparent.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

====+AI respect tabled turn time and rotdamp:====
{{Table202|
*Due to complicated physics issues caused by retail not using the above method, tabled turn times on ships and missiles are not representative of actual observed turn times. The above flag makes it consistent, but this flag will make it accurate to what is actually listed in the table.
*Additionally, rotdamp is now used properly by the AI in a similar manner to players. More rotdamp will result in slower rotational acceleration, and less results in faster acceleration.
*NOTE: BEWARE OF ADDING THIS FLAG TO AN EXISTING MODPACK. NEARLY EVERY SINGLE TURN TIME WILL NEED TO BE CHANGED.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Player starts in third person/chase view by default:===
{{Table212|
*When this flag is set, a player will start the mission in the chase view, not in the cockpit view.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Custom briefing icons always override standard icons:===
{{Table214|
*Custom ship briefing icons will always be shown when the briefing icon is a ship, but not when it is a non-ship icon such as a planet. Set this flag to use custom briefing icons in all cases.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

==#END==
Required. The last line of the table must be #END

==Sample Entry==

#CAMPAIGN SETTINGS
$Default Campaign File Name: NewCampaignFile

#Ignored Campaign File Names
$Campaign File Name: FreeSpace2.fc2

#HUD SETTINGS
$Directive Wait Time: 5000

#SEXP SETTINGS
$Loop SEXPs Then Arguments: True

#OTHER SETTINGS
$Fix Turret Collisions: True

#END

[[Category:Tables]]

Ships.tbl

2020-11-03T11:56:44Z

AdmiralRalwood: Templates were fixed five years ago but I forgot to edit the wiki about it, apparently.

{{TableVersionGit|2020-08-13 UTC|e01c799cc1e7c1a36222954db1d4d37f68b26b67}}
{{Tables}}
The '''ships.tbl''' defines all the ship classes used in FSO.

This table is one of the [[Modular Tables]] and can be extended with xxx-shp.tbm

==General Format==
*Ship.tbl is formed of several different sections.
*All sections beginning with <nowiki>#</nowiki> need <nowiki>#</nowiki>End before the next section.
**<nowiki>#</nowiki>'''Default Player Ship'''
***Defines the default player ship in the game and also in the FRED. If in a mission appears a ship that has not been properly included to tables then game replaces the ship with the Default Player Ship.
**<nowiki>#</nowiki>'''Engine Wash Info'''
***Includes all the definitions of all engine washes used in the game.
{{Table3610|
:*<nowiki>#</nowiki>'''Ship Templates'''
:**Includes entries for ship templates}}

:*<nowiki>#</nowiki>'''Ship Classes'''
:**Includes entries for every ship and also defines their attributes that are used in the game
:**Is discussed in detail at [[Ships.tbl#Table_Options|Table Options]] section.
{{Table202|
:*<nowiki>#</nowiki>'''Wing Formations'''
:**Includes the list of custom wingmate formations}}
:*'''$Player Ship Precedence'''
:**Player Ship Precedence is used in ship selection when a ship specified by the mission designer is not available to the player. The next ship on the list is used in its place (assuming that ship is allowed for the player)

==Default Player Ship==
*Defines the default ship in the game.
*Syntax: ''Name'', name of ship model as defined in [[Ships.tbl#Table_Options|Table Options]].

==Engine Wash==
*Defines the engines washes
*First entry must be named 'default'

===$Name:===
*Defines the name of the engine wash.
*Syntax: '''''String'''''

===+nocreate===
{{Table3610|
*In [[Modular Tables]] name can be followed by line '''+nocreate''' that prevent game from creating an incomplete entry by leaving the entry unread unless it already exists (either in ship.tbl or in earlier parsed *-shp.tbm files) by the time the *-shp.tbm is read.}}

===$Angle:===
*Defines the angle from the engine where the engine wash exists
*Syntax: '''''Float''''', degrees

===$Radius Mult:===
*Defines engine wash multiplier
*Syntax: '''''Float'''''

===$Length:===
*Defines the length of the engine wash
*Syntax: '''''Float''''', meters

===$Intensity:===
*Defines the strength of the engine wash
*This setting does nothing
*Syntax: '''''Float''''', blast effect

'''Example'''

$Name: Default
$Angle: 10.0
$Radius Mult: 1.2
$Length: 400
$Intensity: 1.0

==Ship Template Options==
{{Warning|
The ship templates feature, when originally introduced, caused crashes and memory issues. Between 2014/07/24 and 2015/8/20, it was removed from the codebase. In short: do not use in versions prior to 3.7.4.}}
{{Table3610|
*Example of template usage [[Ship_Templates]] in which both [[GTB Artemis]] variants have been defined using a single template}}

===$Template:===
{{Table3610|
*Defines the name of template
*Syntax: '''''String''''', name}}

===+Use Template:===
{{Table3610|
*Another template can be used as template for the current template
*Syntax: '''''String''''', name}}

==Ships Table Options==

===$Name:===
*Model name that is used also in game. It is also used as name for the whole ship entry. There are two special characters can be used in the name: '''#''' and '''@'''
**'''#'''. It's used in the middle of the name and cannot be the first character in the $Name: string. It makes the right part of the name not being shown in the ship class info of the target window, (or beside the target brackets in FS_Open builds). It allows making different versions of a base ship while showing the same class name inside the game. An example from FSPort FreeSpace 1: The '''SF Dragon#weakened''' ship, used in [[Enter the Dragon]], appears to the player just as any other '''SF Dragon'''.
**'''@'''. It's used before the proper ship name. It is fully ignored by the game. Moreover, '''@WhateverShip''' and '''WhateverShip''' are exactly the same name and therefore they both appear as '''WhateverShip''' inside the game. It just allows the user marking ships in the table because of any modding reason. In the retail FS2 ships there are several ships starting by '''@'''.
*Syntax: '''''String''''', name

===+nocreate===
{{Table3610|
*In [[Modular Tables]] name can be followed by line '''+nocreate''' that prevent game from creating an incomplete entry by leaving the entry unread unless it already exists (either in ship.tbl or in earlier parsed *-shp.tbm files) by the time the *-shp.tbm is read.}}

===+Use Template:===
{{Table3610|
*Sets the table entry to use template based on an existing table entry instead of creating totally new one
*Syntax: '''''String''''', name of the template}}

===$Alt Name:===
{{Table3613|
*Alternative $Name: for the ship.
*Syntax: '''''String''''', Alternate $Name:}}

===$Short name:===
*Shortened model name, for FRED, Usually more descriptive than the real name.
*Syntax: '''''String''''''

===$Species:===
*Defines species (Terran, Vasudan or Shivan). Determines many things, including the color of the engine glow, the flyby sound effects, the briefing icon and the support ship.
{{Table3610|
*More species have been enabled, and all of these have to be defined in [[species_defs.tbl]].}}

*Syntax: '''''String''''', name of the species
**Example: ''Terran''

===Technical Description===
List of descriptive terms for techroom and ship selection screens. Number after the quotes refers to [[tstrings.tbl]]

====+Type:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Maneuverability:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Armor:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Manufacturer:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Description:====
*Syntax: XSTR("'''''String'''''", integer)
*Requires '''$end_multi_text''' after the entry
*Example:
::XSTR("", -1)
::$end_multi_text

====+Tech Title:====
{{Table3613|
*Defines name of the ship as displayed in the tech room
*Syntax: '''''String'''''}}

====+Tech Description:====
*Syntax: XSTR("'''''String'''''", integer)
*Requires '''$end_multi_text''' after the entry
*Example:
::XSTR("", -1)
::$end_multi_text

====+Length:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Gun Mounts:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Missile Banks:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

===$Selection Effect:===
{{Table3613|
*Defines which selection effect to use when the -ship_choice_3d commandline flag is enabled or no ani can be found for the selected ship.
*Syntax: String, either "FS1", or "Off". This defaults to the FS2 effect.}}

===$Cockpit POF file:===
{{Table3610|*Filename of the cockpit model file
*Syntax: '''''String.pof''''', model filename}}

===+Cockpit Offset:===
{{Table3610|*Defines the offset of the cockpit model
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively}}

===$Cockpit Display:===
{{Table3615|
*Defines a rectangle surface on a cockpit texture that can be updated dynamically. Multiple displays can be defined, but only one needs to be defined for each texture on the cockpit model.
*'''+Texture:'''
*The filename of the cockpit texture to be replaced.
*Syntax: '''''String''''', texture filename
*'''+Offsets:'''
* (Optional) The offsets of the rectangle surface into the texture that will be drawn into.
*Syntax: '''''Vector''''', two '''integers'''
*'''+Size:'''
* The size of the rectangle surface that will be drawn into.
*Syntax: '''''Vector''''', two '''integers'''
*'''+Background:'''
* (Optional) Filename of the bitmap to be used as the background of this display.
*Syntax: '''''String''''', texture filename
*'''+Foreground:'''
* (Optional) Filename of the bitmap to be used as the foreground of this display.
*Syntax: '''''String''''', texture filename
*'''+Display Name:'''
* A name to be used as a reference handle.
*Syntax: '''''String'''''}}

===$POF File:===
*Filename of the model file (.pof) at data/models folder
*Syntax: '''''String.pof''''', model filename

===$POF file Techroom:===
*Filename of the model file (.pof) at data/models folder; used only in the weapon loadout screen
*Syntax: '''''String.pof''''', model filename

===$Texture Replace:===
{{Table3610|
*'''+old:'''
*Defines the texture to be replaced
**Syntax: '''''String''''', filename
*'''+new:'''
*Defines the new texture
**Syntax: '''''String''''', filename}}

===$POF Target File:===
*Optional hud targeting model
*Syntax: '''''String.pof''''', model filename

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

===$Detail Distance:===
*Defines the distance where the change between different Levels-Of-Details (LODs) occurs
*Take notice that these are base values. Model detail in Detail options, (within game press F2), applies a multiplier to these values. These multipliers default to (from left to right): 1/8, 1/4, 1, 4, and 8, and may be overridden by the [[Ai_profiles.tbl#$Detail Distance Multiplier:|$Detail Distance Multiplier]]
*Syntax: '''''(Detail Distances)''''' , list of '''integers''' (same amount as LODs), distances from the model in meters
**Example: ''(0, 80, 300, 900)''

===$Collision LOD:===
{{Table373|
*Defines an alternative LOD (Level-Of-Detail) to use for collision detection. Using this can increase performance without visible drawbacks if the LOD chosen has much simpler geometry but the shape still closely matches the base model.
*This works as follows: collision detection proceeds normally through the various model/submodel radius and bounding box checks based on LOD0, but when the game decides to perform a mesh-based collision check of a given submodel, it will use the submodel's LOD mesh instead. However, all submodels do not need to have a counterpart in the given LOD; if one is not found, the closest alternative will automatically be used instead.
*For example, if ''$Collision LOD: 3'' is used and the submodel engine01a is checked for a hit, the game will attempt to use the mesh of engine01d instead. However, if there is no engine01d submodel, the game will find the closest alternative: it'll look for engine01c, then engine01b, and finally fall back to engine01a. Note the implications of for example the root LOD submodel (detaild, detail3, etc) including the geometry of subsystem submodels; if detail0 is checked for a collision before engine01a, and detail3 includes the engine geometry (as opposed to having it in engine01d), then the subsystem engine01a cannot be hit.
**Syntax: '''''Integer'''''}}

===$ND:===
NOTE: this option has done nothing since before 2008

*No Dim field field was used in FreeSpace for ship lights. Use of glowmaps is preferred to the $ND entry. Only noticeable in Glide or Software mode.
*Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
**Example: ''42, 42, 224''

===$Enable Team Colors:===
{{Table3615|
*Enables Team Colors for a ship without setting a default color setting.
*Syntax: '''''Boolean'''''}}

===$Default Team:===
{{Table3615|
*Specifies the default team name to be used for coloring a ship.
*None will set the default to 'no coloring'.
*Syntax: '''''String''''', name of the teams as defined in [[colors.tbl]]}}

===$Show Damage:===
*No function at all. The engine will read values, but discard them. In 3.6.10 or later, this can be left out without adverse consequences.
*Syntax: '''''Boolean''''', yes or no, usually yes

===$Damage Lightning Type:===
{{Table3613|
*Changes the damage lightning effect shown on highly damaged ships.
*Can be defined as:
**''None''
**''Default''}}

===$Impact:===
{{Table3610|
*'''+Damage Type:'''
**Defines the damage type of the collision
**Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]}}

===$Impact Spew:===
{{Table3610|
*Used to define the impact particle spew
*Note: You CANNOT define a different type of particle spew here; the only option possible is listed below
*'''+Max particles:'''
**Defines the maximum number of particles spewed
**Setting to zero causes model to generate no particles at all
**Syntax: '''''Integer'''''
**Default Value: 30}}{{Table3613|
*'''+Min particles:'''
**Defines the minimum number of particles spewed
**Syntax: '''''Integer'''''
**Default Value: 25
*'''+Max Radius:'''
**Defines the maximum radius of particles
**Syntax: '''''Float'''''
**Default Value: 0.5f
*'''+Min Radius:'''
**Defines the minimum radius of particles
**Syntax: '''''Float'''''
**Default Value: 0.2f
*'''+Max Lifetime:'''
**Defines the maximum lifetime of particles
**Syntax: '''''Float'''''
**Default Value: 0.55f
*'''+Min Lifetime:'''
**Defines the minimum lifetime of particles
**Syntax: '''''Float'''''
**Default Value: 0.05f
*'''+Max Velocity:'''
**Defines the maximum velocity of particles
**Syntax: '''''Float'''''
**Default Value: 12.0f
*'''+Min Velocity:'''
**Defines the minimum velocity of particles
**Syntax: '''''Float'''''
**Default Value: 2.0f
*'''+Normal Variance:'''
**Defines the variance of particle direction from the normal
**Syntax: '''''Float'''''
**Default Value: 1.0f}}

===$Damage Spew:===
See [[Ship.tbl#$Impact Spew:|Impact Spew entry]]
*Controls the 'smoke' released on weapon impact point
*Certain default values (marked with '''X''') gain a specific multiplier based on ship radius
::If the radius is less than 20 the multiplier is 1
::If the radius is larger than 40 the multipler is 1.2
::Otherwise it is between 1 and 1.2
{{Table3610|
*'''+Max Particles:'''
**Default Value: 50 * '''X'''}}{{Table3613|
*'''+Min Particles:'''
**Default Value: 20 * '''X'''
*'''+Max Radius:'''
**Default Value: 1.3
*'''+Min Radius:'''
**Default Value: 0.7
*'''+Max Lifetime:'''
**Default Value: 1.5 * '''X'''
*'''+Min Lifetime:'''
**Default Value: 0.7 * '''X'''
*'''+Max Velocity:'''
**Default Value: 12.0
*'''+Min Velocity:'''
**Default Value: 3.0
*'''+Normal Variance:'''
**Default Value: 0.2 * '''X'''}}

===$Collision Physics:===
{{Table3613|
*Parameters affecting collision physics, including landings.
*"Landing" means the ship will not take damage or shake when it touches down. Instead, the ship will reorient towards a neutral resting orientation. "Reorient" thresholds below mean that the ship will still take damage (counts as a crash) but will move towards the correct landing orientation.

====+Bounce:====
When this ship collides with a large ship, how many meters to instantly move it away. Default is 5.0.
====+Both Small Bounce:====
When this ship collides with a small ship, how many meters to instantly move it away. Default is 5.0.
====+Friction:====
During collisions, how much friction to apply (slowing lateral movement). Default is 0.0.
====+Rotation Factor:====
Affects the rotational energy of collisions. Default is 0.2.
====+Landing Max Forward Vel:====
Maximum velocity for which landing physics are used.
====+Landing Min Forward Vel:====
Minimum velocity for which landing physics are used.
====+Landing Max Descent Vel:====
Maximum velocity at which the ship can "hit the deck" and still be considered a landing.
====+Landing Max Horizontal Vel:====
Maximum sideways velocity the ship can land at.
====+Landing Max Angle:====
Maximum angle of attack the ship can land at (in degrees).
====+Landing Min Angle:====
Minimum angle of attack the ship can land at (in degrees).
====+Landing Max Rotate Angle:====
How many degrees the ship can be rotated relative to the landing surface in order to count as a landing.
====+Reorient Max Forward Vel:====
Maximum velocity for which the ship will be adjusted to the correct landing orientation.
====+Reorient Min Forward Vel:====
Minimum velocity for which the ship will be adjusted to the correct landing orientation.
====+Reorient Max Descent Vel:====
Maximum velocity at which the ship can "hit the deck" and still reorient.
====+Reorient Max Horizontal Vel:====
Maximum sideways velocity for reorienting.
====+Reorient Max Angle:====
Maximum angle of attack for reorienting to kick in (in degrees).
====+Reorient Min Angle:====
Minimum angle of attack for reorienting to kick in (in degrees).
====+Reorient Max Rotate Angle:====
How many degrees the ship can be rotated relative to the landing surface in order to be reoriented on impact.
====+Reorient Speed Mult:====
How quickly the reorientation takes place (when applicable)
====+Landing Rest Angle:====
Angle of the ship's nose relative to the plane of the landing surface when the ship is at rest. Reorient will move the ship towards this angle.
====+Landing Sound:====
Sound to play when landing (if it's not a landing, normal collision sound is used).
}}
{{Table202|
====+Collision Sound Light:====
Sound when this ship collides normally.
====+Collision Sound Heavy:====
Sound when this ship collides at high speed.
====+Collision Sound Shielded:====
Sound when this ship collides with shields active.
}}

===$Debris:===
{{Table3610|
*'''+Min Lifetime:'''
**Defines the minimum lifetime of the debris (Default value is a random number)
**Syntax: '''''Float,''' Seconds
*'''+Max Lifetime:
**Defines the maximum lifetime of the debris
**Syntax: '''''Float,''' Seconds
*'''+Min Speed:
**Defines the minimum speed of the debris
**Syntax: '''''Float,''' Meters/second
*'''+Max Speed:
**Defines the maximum speed of the debris
**Syntax: '''''Float,''' Meters/second
*'''+Min Rotation speed:
**Defines the minimum rotational speed of the debris (Default is (6 to 10)/Ship-radius)
**Syntax: '''''Float,''' Radians/second
*'''+Max Rotation speed:
**Defines the maximum rotational speed of the debris
**Syntax: '''''Float,''' Radians/second
*'''+Damage Type:'''
**Defines the damage type of the debris
**Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]}}
{{Table3611|
*'''+Min Hitpoints:'''
**Defines the minimum hitpoints assigned for the generated debris pieces
**Syntax: '''''Float'''''
*'''+Max Hitpoints:'''
**Defines the maximum hitpoints assigned for the generated debris pieces
**Syntax: '''''Float'''''
*'''+Damage Multiplier:'''
**Defines the collision damage multiplier for collisions against the generated debris pieces
**Syntax: '''''Float'''''
*'''+Lightning Arc Percent:'''
**Controls what percent of debris pieces will have the damage lightning effect applied to them.
**Defaults to 50%.
**Syntax: '''''Float,''' 0-100}}
{{Table202|
*'''+Ambient Sound:'''
**The sound played in the vicinity of debris.
}}

===$Density:===
*This defines how hard you hit something. If you set it very high, a collision will the lower density ship and not yours; the higher the numbers are, the harder they will hit and the farther they will be pushed. However, this doesn't apply to asteroids. When a high density fighter collides with an asteroid, the high-density fighter will receive damage, but it will also destroy the asteroid. Setting a density of 1000 on a fighter with 180 hitpoints will cause the fighter to immediately explode if it collides with, say, an asteroid. A low-density fighter will not have any effect on an asteroid, but if the fighter destroys the asteroid, the fighter will fly far away.
*Syntax: '''''Float''''', usually 1. Must not be 0.

===$Damp:===
*Sets the natural period (1 / omega) of the dampening effects on top of the acceleration model. (See [[Ships.tbl#$Forward Accel:|$Forward Accel:]])
*In essence, affects how quickly you will accel/decel to your target velocity. Higher damp means slower acceleration and deceleration, while lower values (down to 0.0001) means faster acceleration/deceleration.
**Specifying a value of 0.0 means there is no damping placed on top of the acceleration model, which is the most responsiveness you'll get.

*Syntax: '''''Float'''''

===$Rotdamp:===
*Shares the same principles of [[Ships.tbl#$Damp:|$Damp]], but is applied to rotations directly. (there isn't a engine/thrust acceleration model for rotations)
*Syntax: '''''Float'''''

===$Banking Constant:===
{{Table3610|
*Defines a factor for how much roll is added during a yaw. Set as 1 for full roll and 0 is no roll. Default is 0.5.
*Syntax: '''''Float'''''}}

===$Max Velocity:===
*Defines maximum velocities with standard energy settings on x (left/right), y (up/down), and z (forward) -axis (respectively). z -axis velocity defines the maximum forward velocity.
*The x and y velocities are considered slide veocities
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively, meters per second
**Example: ''0.0, 0.0, 80.0''

===$Player Minimum Velocity:===
{{Table38|
*Defines minimum velocities on x (left/right), y (up/down), and z (forward) -axis (respectively). This affects the player only, the AI ignores the value.
*The x and y velocities are considered slide velocities, the minimums for them are '''not currently implemented'''.
*When gliding, if the absolute speed vector of the players ship falls below the minimum then the ships engines will re-engage and cannot be switched off again until the ships absolute vector exceeds the z-minimum.
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively, meters per second
**Example: ''0.0, 0.0, 40.0''
}}

===$Rotation Time:===
*Defines rotation times around the x, y, and z-axis. Number is seconds it takes to complete rotate a ship (360 degrees) around the given axis. X-axis is "pitch," y-axis is "yaw," and z-axis is "roll."
*Syntax: '''''Vector''''', three '''floats''', seconds per 360 degree turn around x-axis, y-axis, z-axis, respectively
**Example: ''3.0, 2.6, 5.0''
**Note: Setting to Zero will cause the model to disappear in mission.

===$Rear Velocity:===
*Defines rear velocity
*Syntax: '''''Float''''', meters per second
**Note: This value must be set for [[Ships.tbl#.2BAburn_Max_Reverse_Vel:|+Aburn_Max_Reverse_Vel:]] to work

===$Forward Accel:===
*Number of seconds needed from full stop to 63.21% of the maximum forward (z) velocity
** We use 63.21% instead of 100% because FSO's acceleration/velocity model is based on a simplistic exponential function, rather than the more complex models seen for prop-driven, jet-driven, or rocket-driven craft.
** The equation is a derivative of v = 1 - e^(-t / T), where T is what we define in the ship.tbl
*Syntax: '''''Float''''', seconds

===$Forward Decel:===
*Number of seconds needed from maximum forward (z) velocity to full stop
*Syntax: '''''Float''''', seconds

===$Slide Accel:===
*Number of seconds needed from full stop to 63.21% maximum slide velocity
*Note: this is applied to both slide (x and y) axes
**See [[Ships.tbl#$Forward Accel:|$Forward Accel]] for an explanation of the 63.21%
*Syntax: '''''Float''''', seconds

===$Slide Decel:===
*Number of seconds needed from 63.21% maximum slide velocity to full stop
*Note: this is applied to both slide (x and y) axes
**See [[Ships.tbl#$Forward Accel:|$Forward Accel]] for an explanation of the 63.21%
*Syntax: '''''Float''''', seconds

===$Glide:===
{{Table3610|
*Allows gliding in game, i.e. turning the ship's attitude/facing without changing its current movement direction and speed.
*Syntax: '''''Boolean''''', yes or no}}

====+Dynamic Glide Cap:====
{{Table3611|
*If set, game uses dynamic glide cap. The dynamic glide cap means that the maximum glide speed will follow the same rules as normal flight, including the effects of afterburner and power to engines. If set to YES, the value in +Max Glide Speed is ignored.
*Syntax: '''''Boolean'''''}}

====+Max Glide Speed:====
{{Table3610|
*Defines the maximum glide speed if glide has been enabled. If 0, this is set to the fastest speed the ship can go. If negative, there is no glide cap (allowing practically infinite maximum gliding speed). Defaults to 0.
*Syntax: '''''Float'''''}}

====+Glide Accel Mult:====
{{Table3611|
*Defines the acceleration multiplier for the gliding mode. If > 0, sets a fixed acceleration rate in glide mode depending on value. If set to 0, impossible to accelerate while in glide mode. If negative, enables glide speed ramping (acceleration in glide mode ramps in the same way as in normal flight). Defaults to 0.
*Syntax: '''''Float'''''}}
{{Table3610|
*Entry exists as a dummy entry which doesnt do anything to prevent compatibility issues}}

===$Use Newtonian Dampening:===
{{Table3611|
*If set, forces the ship to use (or not use) newtonian dampening. Basically, allows overriding the AI Profiles flag on a per-ship basis.
*Syntax: '''''Boolean'''''}}

===$Autoaim FOV:===
{{Table3610|
*Defines the field of view for autoaim
*Syntax: '''''Integer'''''}}

====+Converging Autoaim====
{{Table3611|
*Defines that the autoaim uses convergence}}

====+Minimum Distance:====
{{Table3611|
*Defines the minimum distance for the convergence}}

===$Convergence:===
{{Table3611|
*Defines the weapons use convergence
{{Note|If none of the following optional strings are added, the weapon will not converge. Don't forget to use them.}}
}}

====+Automatic====
{{Table3611|
*Defines that the ship uses automatic convergence - converging distance calculated from estimated hit position (lead) of the current target.
*'''+Minimum Distance:'''
**Defines the minimum distance for the convergence. Overrides the setting for $Autoaim FOV's minimum distance.}}

====+Standard====
{{Table3611|
*Defines that ship uses fixed convergence.
*'''+Distance:'''
**Defines the converging distance from the ship}}

====+Offset:====
{{Table3611|
*Defines the offset from the ship centerpoint for the convergence
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively}}

===$Warpin Type:===
{{Table3610|
*Allow an animation to be defined as a warpin effect.
*Can be defined as:
:*''Default''
:*''BTRL'' or ''Galactica''
:*''Homeworld''
:*''Hyperspace''}}
{{Table3613|
:*''Knossos''
:*''Babylon5''}}
{{Table3611|
::*''BTRL'' was replaced with ''Galactica'' after 3.6.10}}
{{Table3610|
*Syntax: '''''String'''''}}

===$Warpin Start Sound:===
{{Table3610|
*File for playing at start of warp in effect
*Syntax: '''''String''''', filename}}

===$Warpin End Sound:===
{{Table3610|
*File for playing at end of warp in effect
*Syntax: '''''String''''', filename}}

===$Warpin Speed:===
{{Table3610|
*Sets the speed at which the ship warps in for '''default''' warpin effect
*Sets the time that the ships warp in (not the animation itself) takes for '''BTRL''' type warpin effects
*Syntax: '''''Float''''', meters per second or miiliseconds}}

===$Warpin Time:===
{{Table3610|
*Defines the effect duration
*Syntax: '''''Float''''', seconds}}

===$Warpin Decel Exp:===
{{Table3613|
*Only for the '''hyperspace''' warpin effect.
*Defines an exponent for the deceleration curve at the end of the warpin. Must be higher than 0; a value of 1 produces a constant velocity throughout the effect and higher values produce gradual deceleration.
*Syntax: '''''Float'''''
**Default: 1.0}}

===$Warpin Radius:===
{{Table3610|
*Defines the effect radius
*Syntax: '''''Float''''', meters}}

===$Warpin Animation:===
{{Table3610|
*Defines the animation used for the Homeworld warpin effect. Has no effect for other warpin types.
*Syntax: '''''String''''', filename}}

===$Warpout Type:===
{{Table3610|
*Allow an animation to be defined as a warpout effect.
*Can be defined as:
:*''Default''
:*''BTRL'' or ''Galactica''
:*''Homeworld''
:*''Hyperspace''}}
{{Table3613|
:*''Knossos''
:*''Babylon5''}}
{{Table3611|
::*''BTRL'' was replaced with ''Galactica'' after 3.6.10}}
{{Table3610|
*Syntax: '''''String'''''}}

===$Warpout Start Sound:===
{{Table3610|
*File for playing at start of warp out effect
*Syntax: '''''String''''', filename}}

===$Warpout End Sound:===
{{Table3610|
*File for playing at end of warp out effect
*Syntax: '''''String''''', filename}}

===$Warpout Engage Time:===
{{Table3615|
*Defines the delay the it takes for the warp drive of the ship to engage, during which the player may still abort the warpout. Affects both the player as well as AI ships. If not defined, [[Game_settings.tbl#.24Minimum player warpout time:|defaults to]] 3 seconds for the player and none for the AI.
*Syntax: '''''Float''''', seconds}}

===$Warpout Speed:===
{{Table3610|
*Sets the speed at which the ship warps out for '''default''' warpout effect
*Sets the time that the ships warp out (not the animation itself) takes for '''BTRL''' type warpout effects}}
{{Table3613|
*Sets the minimum speed required for the ship to warp out for '''hyperspace''' type warpout effects}}
{{Table3610|
*Syntax: '''''Float''''', meters per second or milliseconds}}

===$Warpout Time:===
{{Table3610|
*Defines the effect duration
*Syntax: '''''Float''''', seconds}}

===$Warpout Accel Exp:===
{{Table3613|
*Only for the '''hyperspace''' warpin effect.
*Defines an exponent for the acceleration curve at the start of the warpout. Must be higher than 0; a value of 1 produces a constant velocity throughout the effect and higher values produce gradual acceleration.
*Syntax: '''''Float'''''
**Default: 1.0}}

===$Warpout Radius:===
{{Table3610|
*Defines the effect radius
*Syntax: '''''Float''''', meters}}

===$Warpout Animation:===
{{Table3610|
*Defines the animation used as the warpout effect.
*Syntax: '''''String''''', filename}}

===$Player Warpout Speed:===
{{Table3610|
*Sets the speed at which the player warps out from the game
*Syntax: '''''Float'''''}}

===$Expl Inner Rad:===
*Radius at which the full explosion damage is done
*Syntax: '''''Float''''', meters

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

===$Expl Damage:===
*Amount of damage done inside the inner radius
*Syntax: '''''Float''''', damage

===$Expl Blast:===
*The intensity of the blast effect when you're within the outer radius
*Syntax: '''''Float''''', blast effect

===$Expl Propagates:===
*This decides whether the ship explodes into debris immediately, or whether it has the many small explosions before breaking apart slowly
*Syntax: '''''Boolean''''', yes or no

===$Propagating Expl Radius Multiplier:===
{{Table3613|
*This sets the multiplier for the ship splitting propagating explosions
*Syntax: '''''Float''''', defaults to 1}}

===$Expl Visual Rad:===
{{Table3611|
*This determines the visual size of the main fireball for an exploding ship. Does not affect ships with propagating explosions.
*Syntax: '''''Float''''', meters}}

===$Base Death-Roll Time:===
{{Table3613|
*Defines the base death-roll time
*Values is modified depending on conditions when the ship died
*Syntax: '''''Integer''''', milliseconds
**Default: 3000}}

===$Death-Roll Explosion Radius Mult:===
{{Table3613|
*Defines the multiplier for the radius of the ship surface explosions during death roll
*Syntax: '''''Float'''''
**Default: 1}}

===$Death-Roll Explosion Intensity Mult:===
{{Table3613|
*Defines the multiplier for the amount of the ship surface explosions during death roll
*Syntax: '''''Float'''''
**Default: 1}}

===$Death FX Explosion Radius Mult:===
{{Table3613|
*Defines the multiplier applied to the ship death explosions
*Syntax: '''''Float'''''
**Default: 1}}

===$Death FX Explosion Count:===
{{Table3613|
*Defines the number of explosion effect game uses when a large ship dies
*Syntax: '''''Integer'''''
**Default: 6}}

===$Death Roll X rotation Cap:===
{{Table382|
*Defines the cap (aka maximum) on X-axis (pitch) rotation during the ships deathroll. The value is radians per second. The current hard-coded minimum is 0.8. Note the code generally won't use this value for ships with radius > 150 (hard-coded).
*Syntax: '''''Float'''''
**Default: 4.725}}

===$Death Roll Y rotation Cap:===
{{Table382|
*Defines the cap (aka maximum) on Y-axis (yaw) rotation during the ships deathroll. For other details see $Death Roll X rotation Cap:
*Syntax: '''''Float'''''
**Default: 4.725}}

===$Death Roll Z rotation Cap:===
{{Table382|
*Defines the cap (aka maximum) on Z-axis (roll) rotation during the ships deathroll. For other details see $Death Roll X rotation Cap:
*Syntax: '''''Float'''''
**Default: 4.725}}

===$Ship Splitting Particles:===
See [[Ship.tbl#$Impact Spew:|Impact Spew entry]]
*Controls the particles released on every explosion event which happens when ship is splitting apart
*The old 'popcorn' effect
{{Table3613|
*'''+Max Particles:'''
**Default Value: 80
*'''+Min Particles:'''
**Default Value: 40
*'''+Max Radius:'''
**Default Value: Ship radius * 0.015
*'''+Min Radius:'''
**Default Value: Ship radius * 0.005
*'''+Max Lifetime:'''
**Default Value: 6.0 * (1 + 0.002 * Ship radius)
*'''+Min Lifetime:'''
**Default Value: 0.5 * (1 + 0.002 * Ship radius)
*'''+Max Velocity:'''
**Default Value: Speed of the propagating explosion
*'''+Min Velocity:'''
**Default Value: 0.0
*'''+Normal Variance:'''
**Default Value: 2.0}}

===$Ship Death Effect:===
{{Table38|
*Specifies the [[Particle Effects|particle effect]] which will be used the final explosion of this ship type,
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Ship Death Particles'' is not a valid option!
}}

===$Ship Death Particles:===
See [[Ship.tbl#$Impact Spew:|Impact Spew entry]]
*Controls the particles released on the moment 'non-knossos' type object dies
{{Table3613|
*'''+Max Particles:'''
**Default Value: 100
*'''+Min Particles:'''
**Default Value: 50
*'''+Max Radius:'''
**Default Value: 1.5
*'''+Min Radius:'''
**Default Value: 0.1
*'''+Max Lifetime:'''
**Default Value: 4.0
*'''+Min Lifetime:'''
**Default Value: 0.5
*'''+Max Velocity:'''
**Default Value: 20.0
*'''+Min Velocity:'''
**Default Value: 0.0
*'''+Normal Variance:'''
**Default Value: 2.0}}

===$Alternate Death Particles:===
See [[Ship.tbl#$Impact Spew:|Impact Spew entry]]
*Controls the particles released when 'knossos' type object is dying
{{Table3613|
*'''+Max Particles:'''
**Default Value: 30
*'''+Min Particles:'''
**Default Value: 15
*'''+Max Radius:'''
**Default Value: 100.0
*'''+Min Radius:'''
**Default Value: 30.0
*'''+Max Lifetime:'''
**Default Value: 12.0
*'''+Min Lifetime:'''
**Default Value: 2.0
*'''+Max Velocity:'''
**Default Value: 350.0
*'''+Min Velocity:'''
**Default Value: 50.0
*'''+Normal Variance:'''
**Default Value: 2.0}}

===$Vaporize Percent Chance:===
{{Table3611|
*Allows ships to sometimes explode instantly (vaporize) instead of going through a death roll first. Overrides the same flag in [[objecttypes.tbl]].
*Syntax: '''''Float''''', percent chance of vaporization, 0 to 100}}

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

===$Shockwave Speed:===
*Speed shockwave expands at, 0 means no shockwave
*Syntax: '''''Float''''', meters per second

===$Shockwave Count:===
*Defines the number of shockwaves to spawned
*Syntax: '''''Integer'''''

===$Shockwave Model:===
{{Table3610|
*Defines the textured model used as the ship's 3D shockwave
*Syntax: '''''String.pof''''', model filename}}

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

===$Explosion Animations:===
{{Table3610|
*Defines the explosion animations used for the ship
*Syntax: '''''Integer list'''''}}

===$Weapon Model Draw Distance:===
{{Table3610|
*Distance that external weapons are shown, ie. missiles and such.
*Syntax: '''''Float''''', meters
**Default: ''200''}}

===Primary Weapons===
====$Allowed PBanks:====
*List of allowed primary weapons in brackets (weapon name marked with quotes).
*Syntax: '''''( "String" "String" )''''', names of the weapons
{{Table3610|
*Each of the primary weapon banks '''can optionally''' be given their own list of allowed weapons, in which case each bank has its own bracketed entry.
*Syntax: '''''( "String" "String" ) ( "String" "String" )'''''}}

====$Allowed Dogfight PBanks:====
*Primary weapons for multiplayer dogfights.
*Syntax: '''''( "String" "String" )''''', names of the weapons
{{Table3610|
*Each of the primary weapon dogfight banks '''can optionally''' be given their own list of allowed weapons, in which case each bank has it's own bracketed entry.
*Syntax: '''''( "String" "String" ) ( "String" "String" )'''''}}

====$Default PBanks:====
*Defines default primary weapons for each of the primary weapon banks
*Syntax: '''''( "String" "String" )''''', names of the weapons

====$PBank Capacity:====
{{Table3610|
*Defines ammunition capacity of primary weapon banks. In brackets, different weapon banks separated by commas.
*NOTE: In order for this to work, at least one of the primary weapons in the list of default primaries must be a ballistic weapon.
*Syntax: '''''( Integer, Integer )'''''}}

====$Show Primary Models:====
{{Table3610|
*Defines the use of weapon models for primary weapons. In brackets, different weapon banks may have different definitions
*Syntax: '''''( Boolean Boolean )''''', yes or no
**Example: ''( YES YES )'' - Note the spaces on the insides of the brackets.}}

===Secondary Weapons===
====$Allowed SBanks:====
*Same for secondary weapons.
*Syntax: '''''( "String" "String" )''''', names of the weapons
{{Table3610|
*Each of the secondary weapon banks can be given their own list of allowed weapons, in which case each bank has it's own bracketed entry.
*Syntax: '''''( "String" "String" ) ( "String" "String" )'''''}}

====$Allowed Dogfight SBanks:====
*Same for secondary weapons.
*Syntax: '''''( "String" "String" )''''', names of the weapons
{{Table3610|
*Each of the secondary weapon dogfight banks can be given their own list of allowed weapons, in which case each bank has it's own bracketed entry.
*Syntax: '''''( "String" "String" ) ( "String" "String" )'''''}}

====$Default SBanks:====
*Defines default primary weapons for each of the primary weapon banks
*Syntax: '''''( "String" "String" )''''', names of the weapons

====$SBank Capacity:====
*Defines ammunition capacity of secondary weapon banks. In brackets, different weapon banks separated by commas.
*Syntax: '''''( Integer, Integer )'''''

====$Show Secondary Models:====
{{Table3610|
*Defines the use of weapon models for secondary weapons. In brackets, different weapon banks may have different definitions
*Syntax: '''''( Boolean Boolean )'''''
**Example: ''(YES YES)''}}

===$Ship Recoil Modifier:===
{{Table373|
*Multiplies the recoil force of a weapon by this value, use a value greater than 1.0 to increase the force, use a value between 1.0 and 0.0 to decrease.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|It is not required to have any weapons with the "apply recoil" flag set for this to be enabled.}}
}}

===$Shields:===
*Determines the shield strength
*Syntax: '''''Float''''', total shield strength

====+Auto Spread:====
{{Table371|
*Defines the thickness of auto spread shields. Note that the [[#.22auto_spread_shields.22|"auto spread shields"]] ship flag is also needed.
*Syntax: '''''Float''''', shield thickness in meters.}}

====+Minimum Weapon Span:====
{{Table373|
*Determines the minimum distance weapons must have traveled before impacting the shield (for example if fired close to or inside the shield). Does not affect whether the weapon bypasses shields, unless +Allow Bypass (see below) is set to ''YES''. Only valid with auto spread shields.
*Syntax: '''''Float''''', defaults to the shield thickness.}}

====+Allow Bypass:====
{{Table371|
*Determines whether weapons which impact on the ship's hull (see +Minimum Weapon Span above) will bypass shields. Only valid with auto spread shields.
*Syntax: '''''Boolean'''''
**Default: ''NO''}}

====+Spread From LOD:====
{{Table371|
*Causes the auto spread shields calculations to be done based off a LOD level other than LOD0. Using a lower-poly LOD will considerably speed up the shield collision detection, while being visually indistinguishable in most cases.
*Syntax: '''''Integer''''', defaults to 0}}

===$Model Point Shield Controls:===
{{Table371|
*Allows remapping of the 4 shield augmentation keys when [[Model Point Shields]] are used. You should usually supply as many values as you have shield segments. The first value determines which augmentation key to use for the first shield segment, the second value determines which key to use for the second shield segment, and so on (the order being defined by the order of the shield points in the model file). If less than 4 values are given, "none" is assumed for the missing ones. Note that as there are only 4 augmentation keys, player ships with more than 4 shield segments would generally not be a good idea.
*Syntax: '''''( String list )''''', possible values "front", "left", "right", "rear" and "none"
**Example: ''( "front" "rear" )'' for a ship with only two shield sections, front and rear; the left and right augmentation keys would be disabled.
**Example: ''( "left" "rear" "right" )'' for a ship with only three shield sections, left, right and rear; the front augmentation key would be disabled.
**Example: ''( "front" "right" "rear" "left" )'' for a ship with four shield sections but perhaps positioned in a non-standard way.}}

===$Shield Color:===
*RGB value for shield color
*Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
**Example: ''100, 100, 255''

===$Shield Impact Explosion:===
{{Table373|
*Impact explosion animation to trigger when this ship's shields are hit. Works identically for all shield types.
*Note: The size of the explosion is defined by the weapon, see [[Weapons.tbl#.24Shield_Impact_Explosion_Radius:]].
*Syntax: '''''String''''', filename or ''none''
}}

===$Max Shield Recharge:===
{{Table373|
*Determines a maximum recharge limit of shields. When used, the combined maximum shield energy is lowered, meaning that shield energy can be moved between quadrants even with shields fully charged.
*Syntax: '''''Float''''', multiplier ranging from 0.0 to 1.0, defaults to 1.0
**Example: ''$Max Shield Recharge: 0.5'' caps the combined shield energy to 50%, meaning that a ship with 4 shield quadrants will by default have 12.5% strength on all quadrants (instead of normal 25%), allowing it to for example augment one quadrant to 50% while dropping other quadrants to 0%.
}}

===$Power Output:===
*Actually does *NOTHING* unless set to zero; in which case weapon/shield/burner energy regeneration is disabled. Checked via code inspection 2014/12/29
*Syntax: '''''Float'''''

===$Shield Regeneration Rate:===
{{Table3610|
*Repair rates for shields at percent per second
*Syntax: '''''Float''''', multiplier of total shield hitpoints recharged each second. ('''NOT A PERCENTAGE''', 0.02 equals 2% recharged per second)
**Default: ''0.02''
*Affected by ETS Shields value (1/3rd value recharged per sec at default ETS setting of '4')
*Affected by AI Profile Setting: $Player Shield Recharge Scale:}}

===$Support Shield Repair Rate:===
{{Table3611|
*Shield repair rate when docked to a support ship
*Syntax: '''''Float'''''}}

===$Weapon Regeneration Rate:===
{{Table3610|
*Regeneration rates for primary guns at percent per second
*Syntax: '''''Float''''', multiplier of total gun energy recharged each second ('''NOT A PERCENTAGE''', 0.04 equals 4% recharged per second)
**Default: ''0.04''
*Affected by ETS Guns value (1/3rd value recharged per sec at default ETS setting of '4')
*Affected by AI Profile Setting: $Player Weapon Recharge Scale:}}

===$Max Oclk Speed:===
*Can also be '''$Max Overclock Speed:'''
*Maximum velocity with all energy diverted to engines
*Syntax: '''''Float''''', meters per second

===$Max Weapon Eng:===
*Can also be '''$Max Weapon Energy:'''
*The maximum amount of energy you can store in your primary weapons bank.
*Syntax: '''''Float'''''

===$Hitpoints:===
*How much damage the ship can take
*Syntax: '''''Float''''', hitpoints
**Default: ''100''

===$Hull Repair Rate:===
{{Table3610|
*Repair rates for hull at percent per second
*Syntax: '''''Float''''', multiplier of hitpoints repaired per second, '''NOT A PERCENTAGE''', 0.01 equals 1% recharged per second}}

===$Support Hull Repair Rate:===
{{Table3611|
*Repair rate for hull when docked to a support ship
*Syntax: '''''Float'''''}}

===$Subsystem Repair Rate:===
{{Table3610|
*Repair rates for sybsystems percent per second
*Syntax: ''Value'', percentage of total subsystem hitpoints repaired per second}}

===$Support Subsystem Repair Rate:===
{{Table3611|
*Repair rate for subsystems when docked to a support ship
*Syntax: '''''Float'''''}}

===$Armor Type:===
{{Table3610|
*'''REQUIRES ADDITIONAL TABLE'''. Defines armor type used for the ship
*Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]}}

===$Shield Armor Type:===
{{Table3611|
*'''REQUIRES ADDITIONAL TABLE'''. Defines the armor type used for shield of the ship
*Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]}}

===$Flags:===
*See [[Ships.tbl#Ships.tbl_flags|below]]
*Syntax: '''''( "String" "String" )''''', names of the flags assigned to the ship
**Example: ( "fighter" "in tech database" )
{{Table3610|
*'''+noreplace'''
**Can be used to force game to retain existing flags instead of reseting the ship flags before parsing in the new flags.}}

===$AI Class:===
*Default AI class
*Syntax: '''''String''''', name of the AI class as defined in [[ai.tbl]]

===$Afterburner:===
*Defines if the ships has afterburner
*Syntax: '''''Boolean''''', yes or no
====+Aburn Max Vel:====
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively, meters per second
====+Aburn For accel:====
*Defined only for the forward acceleration. In same format as [[Ships.tbl#$Forward Accel:|$Forward Accel]]
*Syntax: '''''Float''''', seconds

====+Aburn Max Reverse Vel:====
{{Table3611|
*Defined only for the reverse acceleration, Sets the top speed for Reverse Afterburner.
*Syntax: '''''Float''''', seconds
**NOTE: Requires [[Ships.tbl#.24Rear_Velocity:|$Rear Velocity:]] to be set in order to work.
}}
====+Aburn Rev accel:====
{{Table3611|
*Defined only for the reverse acceleration. In same format as [[Ships.tbl#$Forward Accel:|$Forward Accel]]

*Syntax: '''''Float''''', seconds'''''}}

====+Aburn Fuel:====
*Amount of afterburner fuel the ship has
*Syntax: '''''Float''''', fuel
====+Aburn Burn Rate:====
*Rate the fuel is consumed when afterburner is engaged (in units per seconds)
*Syntax: '''''Float''''', fuel units per second
====+Aburn Rec Rate:====
*Rate the fuel is restored.
*Exact fuel recharged per second is given by the ETS value (as a percentage of total power output) multiplied by twice the tabled recharge rate, and then multiplied by the difficulty setting.
*Syntax: '''''Float''''', fuel units per second
{{Table3610|
====$Trails:====
*Allows afterburner trails to be used
=====+Bitmap:=====
*Texture used to draw the afterburner trail
*Syntax: '''''String''''', filename
=====+Width:=====
*Width of afterburner trail at the beginning of it (ie. the thruster end)
*Syntax: '''''Float''''', meters
=====+Alpha:=====
*Transparancy of the trail, value from 1 (non-transparent) to 0 (totally transparent)
*Syntax: '''''Float'''''
=====+Life:=====
*How long the trail will last
*Syntax: '''''Float''''', seconds}}
{{Table3611|
=====+Faded Out Sections:=====
*Defines the number of the trail sections from the leading edge that are gradually faded away.
*Syntax: '''''Integer'''''}}

===$Countermeasure Type:===
{{Table3610|
*Defines the weapon used as a countermeasure. Weapon does not have to be included in the countermeasure section of the weapons.tbl, but it has to have "countermeasure" flag in that case.
*Syntax: '''''String''''', name of the weapon as defined in [[weapons.tbl]]}}

===$Countermeasures:===
*Number of countermeasures that can be loaded to the ship
*Syntax: '''''Integer'''''

===$Scan Time:===
*Time it takes to scan the ship
*Syntax: '''''Integer''''', milliseconds

===$Scan range Normal:===
{{Table381|
*Distance at which the ship can scan other small ships or large ship subsystems
*Syntax: '''''Float''''', distance
}}

===$Scan range Capital:===
{{Table381|
*Distance at which the ship can scan capital (& similar size) ships
*Syntax: '''''Float''''', distance
}}

===$Ask Help Shield Percent:===
{{Table381|
*Percentage of shield damage at which the ship will send a call for assistance message.
*Syntax: '''''Float''''', percentage. Valid range 0.0-1.0
}}

===$Ask Help Hull Percent:===
{{Table381|
*Percentage of hull damage at which the ship will send a call for assistance message.
*Syntax: '''''Float''''', percentage. Valid range 0.0-1.0
}}

===$EngineSnd:===
*Engine sound used for the ship with number referring to sounds.tbl
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

===$Minimum Engine Volume:===
{{Table373|
*Specifies how to multiply the volume of the engine sound based on ship speed. When the ship is stationary, the engine volume will be multiplied by the given value, with the value approaching 1.0 as the ship speed approaches maximum.
*Note: Default behavior is to ramp the multiplier from 0.5 (when ship is stationary) to 1.0 (when ship is at half speed or more).
*Syntax: '''''Float''''', volume multiplier, usually you'll want a value between 0.0 and 1.0
}}

===$Flyby Sound===
{{Table382|
*Optional sound to be used for the fly-by sound
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$GlideStartSnd:===
{{Table3613|
*Optional sound to be used when entering glide mode, instead of the default throttle down sound.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$GlideEndSnd:===
{{Table3613|
*Optional sound to be used when exiting glide mode, instead of the default throttle up sound.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$CockpitEngineSnd===
{{Table3613|
*Optional sound to be used for looping engine sound heard in the cockpit.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$FullThrottleSnd===
{{Table3613|
*Optional sound to be used for the sound heard when setting throttle to full power.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$ZeroThrottleSnd===
{{Table3613|
*Optional sound to be used for the sound heard when setting throttle to zero power
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$ThrottleUpSnd===
{{Table3613|
*Optional sound to be used for the sound heard when increasing throttle power by 1/3
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$ThrottleDownSnd===
{{Table3613|
*Optional sound to be used for the sound heard when decreasing throttle power by 1/3
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AfterburnerSnd===
{{Table3613|
*Optional optional sound to be used for the looping sound heard when the afterburner is active
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AfterburnerEngageSnd===
{{Table3613|
*Optional optional sound to be used for the sound heard when the afterburner is engaged
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AfterburnerFailedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the activation of the afterburner failed
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$MissileTrackingSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a aspect seeking missile of the player tries to acquire a lock
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$MissileLockedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a aspect seeking missile of the player has acquired a lock
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$PrimaryCycleSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the player cycles his primary weapon
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$SecondaryCycleSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the player cycles his secondary weapon
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$TargetAcquiredSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the player acquires a new target
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$PrimaryFireFailedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the primary weapon fails to fire
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$SecondaryFireFailedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the secondary weapon fails to fire
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$HeatSeekerLaunchWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a heat-seeker is fired at the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AspectSeekerLaunchWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when an aspect-seeker is fired at the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$MissileLockWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when an aspect-seeker is locked onto the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$HeatSeekerProximityWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a heat-seeker is in close proximity to the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AspectSeekerProximityWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when an aspect-seeker is in close proximity to the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$MissileEvadedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a missile has been evaded
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$CargoScanningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the cargo of an object is being scanned
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$DeathRollSnd===
{{Table202|
*Optional sound to be used for the sound heard when the ship enters its death roll
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$ExplosionSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the ship explodes
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$SubsysExplosionSnd===
{{Table202|
*Optional sound to be used for the sound heard when a subsystem on this ship explodes
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$Closeup_pos:===
*How the model will show at techroom and briefing screen animations (assuming a pre-rendered animation is not specified). The position of the camera relative to the model in the tech room and the target box view. If 3D ship selection is used, also affects the drawing of the ship icon in the weapon & ship selection briefing screens.
*Syntax: '''''Vector''''', three '''floats''', x, y and z values respectively

===$Closeup_zoom:===
*How the model will show at techroom and briefing screen animations (assuming a pre-rendered animation is not specified). How far the camera's zoomed in, defines camera's FOV. If 3D ship selection is used, also affects the drawing of the ship icon in the weapon & ship selection briefing screens.
*Syntax: '''''Float''''', radians

{{Table381|
===$Closeup_pos_targetbox:===
*Optional value to set for the position of the camera relative to the model in the HUD target box view. If not set then the value for $Closeup_pos: will be used.
*Syntax: '''''Vector''''', three '''floats''', x, y and z values respectively

===$Closeup_zoom_targetbox:===
*Optional value to set how the model will show in the HUD target box view. How far the camera's zoomed in, defines camera's FOV. If not set then the value for $Closeup_zoom: will be used.
*Syntax: '''''Float''''', radians
}}

===$Topdown Offset:===
{{Table3610|
*Specifies how high the camera is above the center point of a ship in topdown camera views, or 2D missions.
*Syntax: '''''Float''''', meters}}

===$Shield_Icon:===
*This .ani file must be at data/hud and included to the hud.tbl.
{{Table3610|
*Reference to the hud.tbl is no longer needed.}}
**Syntax: ''Filename''

===$Model Icon Direction:===
{{Table373|
*The direction from which the ship should be drawn from, if $Ship_Icon is not used and the ship icon is generated from the model.
** By default, the direction is based on whether the game thinks the ship is a small ship, a capship or an installation.
**Syntax: ''String'', one of "top", "bottom", "front", "back", "left" or "right"}}

===$Ship_Icon:===
*The icon used in ship selection.
{{Table3610|
*Ship model is used by default to generate the image.}}
**Syntax: ''Filename''

===$Ship_Anim:===
*The glowing green grid animation used in ship selection.
{{Table3610|
*Ship model is used by default to generate the image.}}
**Syntax: '''''String''''', filename

===$Ship_Overhead:===
*The overhead view used in the weapons loadout.
{{Table3610|
*Ship model is used by default to generate the image.}}
**Syntax: '''''String''''', filename

{{Table371|
===$Briefing icon:===
*Defines if the ship has its own briefing icon information which overrides the standard briefing icon image
====+Regular:====
*Syntax: '''''<regular anim filename>'''''
====+Fade:====
*Syntax: '''''<fade anim filename>'''''
====+Highlight:====
*Syntax: '''''<highlight anim filename>'''''}}

{{Table371|
===$Briefing icon with cargo:===
*Defines if the ship has its own cargo briefing icon (which will only be an option if a ship icon is also specified)
====+Regular:====
*Syntax: '''''<regular anim filename>'''''
====+Fade:====
*Syntax: '''''<fade anim filename>'''''
====+Highlight:====
*Syntax: '''''<highlight anim filename>'''''}}

{{Table371|
===$Briefing wing icon:===
*Defines if the ship has its own wing briefing icon (which will only be an option if a ship icon is also specified)
====+Regular:====
*Syntax: '''''<regular anim filename>'''''
====+Fade:====
*Syntax: '''''<fade anim filename>'''''
====+Highlight:====
*Syntax: '''''<highlight anim filename>'''''}}

{{Table371|
===$Briefing wing icon with cargo:===
*Defines if the ship has its own wing-with-cargo briefing icon (which will only be an option if a ship icon is also specified)
====+Regular:====
*Syntax: '''''<regular anim filename>'''''
====+Fade:====
*Syntax: '''''<fade anim filename>'''''
====+Highlight:====
*Syntax: '''''<highlight anim filename>'''''}}

===$Score:===
*Points awarded for destroying the ship
*Syntax: '''''Float'''''

===Customized Thruster Effects===
{{Table3611|
*Defines the texture of the modeled thruster effect cone
*'''$Thruster Normal Flame:'''
**Syntax: '''''String''''', filename
*Defines the texture of the modeled thruster effect cone with afterburners lit
*'''$Thruster Afterburner Flame:'''
**Syntax: '''''String''''', filename}}
{{Table3610|
*'''Defines the primary thruster glow - the one visible only from behind'''
**'''$Thruster Bitmap 1:'''
***Defines the effect for the standard drives. Overrides [[Species_defs.tbl]] line '''+Normal:''' under the '''$Thrustglows:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Bitmap 1a:'''
***Defines the effect for the afterburner. Overrides [[Species_defs.tbl]] line '''+Afterburner:''' under the '''$Thrustglows:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster01 Radius factor:'''
***Defines the radius multiplier
***Syntax: '''''Float'''''
*'''Defines the secondary glow type-effect for thrusters - the feathery trail like haze behind the main glow'''
**'''$Thruster Bitmap 2:'''
***Defines the effect for the standard drives. Overrides [[Species_defs.tbl]] line '''+Sec_Normal:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Bitmap 2a:'''
***Defines the effect for the afterburner. Overrides [[Species_defs.tbl]] line '''+Sec_Afterburn:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster02 Radius factor:'''
***Defines the radius multiplier
***Syntax: '''''Float'''''
**'''$Thruster02 Length factor:'''
***Defines the length multiplier for the trail type (secondary) glowpoint thrusters
***Replaces the older '''$Thruster01 Length factor:'''
***Syntax: '''''Float'''''
*'''Defines the tertiary glow type-effect for thrusters - the one visible from all directions'''
**NOTE: The rotation of this effect is jittered, which can look quite bad with certain types of effects.
**'''$Thruster Bitmap 3:'''
***Defines the effect for the standard drives. Overrides [[Species_defs.tbl]] line '''+Ter_Normal:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Bitmap 3a:'''
***Defines the effect for the afterburner. Overrides [[Species_defs.tbl]] line '''+Ter_Afterburn:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster03 Radius factor:'''
***Defines the radius multiplier
***Syntax: '''''Float'''''}}
{{Table3613|
*'''Defines the distortion effect for thrusters'''
**'''$Thruster Bitmap Distortion:'''
***Defines name of normal thruster distortion envelope animation. Overrides [[Species_defs.tbl]] line '''+Dist_Normal:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Bitmap Distortion a:'''
***Defines name of afterburner thruster distortion envelope animation. Overrides [[Species_defs.tbl]] line '''+Dist_Afterburn:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Distortion Radius factor:'''
***Defines the radius multiplier
***Syntax: '''''Float'''''
**'''$Thruster Distortion Length factor:'''
***Defines the length multiplier for the thruster distortion
***Syntax: '''''Float'''''
**'''$Thruster Distortion:'''
***Defines whether the distortion effect is rendered for this ship.
***Syntax: '''''Bool'''''}}
{{Table373|
*'''$Thruster Glow Noise Mult:'''
**A multiplier for how much noise is applied to the thruster glow radius. A value of 0 causes the radius to remain perfectly steady and values higher than 1 cause the radius to fluctuate more than the default.
** Defaults to 1.0.
**Syntax: '''''Float'''''
}}

===$Thruster Particles:===
{{Table3610|
*Defines the alternative particle thruster
*'''$Thruster Particle Bitmap:''' OR '''$Afterburner Particle Bitmap:'''
**Name of the animation used for particle thrusters, up to '''three''' can be defined for both '''standard''' thrusters and '''afterburners''' (6 in total). Afterburner particles require at least 1 existing particle thruster entry.
**Syntax: '''''String''''', filename
*'''$Min Radius:'''
**Defines the minimum radius of new particles
**Syntax: '''''Float''''', meters
*'''$Max Radius:'''
**Defines the maximum radius of new particles
**Syntax: '''''Float''''', meters
*'''$Min Created:'''
**Defines the minimum amount of particles created
**Syntax: '''''Float'''''
*'''$Max Created:'''
**Defines the maximum amount of particles created
**Syntax: '''''Float'''''
*'''$Variance:'''
**Value that describes the randomness of particle generation, values close to 0 will cause particles to spew very close to the thrusters normal while values close 1 will cause some particles to be spewed even to opposite direction
**Syntax: '''''Float'''''}}

===$Stealth:===
*Defines: Ship behaves as a stealth-ship: non-targettable, and not on radar.
{{Table3610|
This field is [[deprecated]], and mods using 3.6.8 and above should use the "stealth" flag.}}

===$Max Decals:===
{{Table3610|
*Defines: Maximum number of weapon decals on a ship
*Syntax: '''''Integer''''', maximum number of decals on ship
**Default: 50 for anything below cruiser size, 100 for anything below superdestroyer/installation size, 300 for anything above destroyer size, 10 for everything else.}}
{{Table3613|
*Feature disabled. Parsing retained to maintain compatibility}}

===$Trail:===
*These are the origins of the white contrails that appear in the nebula missions. Ship may have multiple trails.
{{Table3611|
*'''+ClearAll'''
**Clears all existing trail data from the ship}}
====+Offset:====
*The position of the contrail's head
*Syntax: '''''Vector''''', three '''floats''', x, y and z values respectively, relative to the center point of the model
====+Start Width:====
*The width of the contrail's head
*Syntax: '''''Float''''', meters
====+End Width:====
*The width of the contrail's tail
*Syntax: '''''Float''''', meters
====+Start Alpha:====
*The opacity of the contrail's head
*Syntax: '''''Float''''', value between 0 and 1
====+End Alpha:====
*The opacity of the contrail's tail
*Syntax: '''''Float''''', value between 0 and 1
====+Max Life:====
*How long the contrail remains
*Syntax: '''''Float'''''', seconds
====+Spew Time:====
*Syntax: '''''Integer'''''
====+Bitmap:====
*The image to use for the contrail.
*Syntax: '''''String''''', filename
{{Table3611|
====+Faded Out Sections:====
*Defines the number of the trail sections from the leading edge that are gradually faded away.}}

===$Thruster:===
{{Table3610|
*Defines maneuvering thrusters. Ship may have multiple $Thrusters defined.
*'''+Index:'''
**Defines the index number of the manoeuvring thruster defined in this entry
**Syntax: '''''Integer'''''
*'''+Used For:'''
**Defines the maneuver that triggers the maneuvering thruster
**List of maneuvers: Bank right, Bank left, Pitch up, Pitch down, Roll right, Roll left, Slide right, Slide left, Slide up, Slide down, Forward, Reverse
**Syntax: '''''("String" "String")'''''
*'''+Position:'''
**Defines thruster location
**Syntax: ( '''''Float''''' '''''Float''''' '''''Float''''' ), position from the ships center point, x, y, z axis respectively
*'''+Normal:'''
**Defines the direction where the thruster points to
**Syntax: ( '''''Float''''' '''''Float''''' '''''Float''''' ), direction of the thrusters normal, x, y, z axis respectively
*'''+Texture:'''
**Defines the graphic that will be used for trail, rendered like beams
**Syntax: '''''String''''', filename
*'''+Radius:'''
**Defines the radius of cylinder
**Syntax: '''''Float''''', meters
*'''+Length:'''
**Defines the length of thruster trail
**Syntax: '''''Float''''', meters
*'''+StartSnd:'''
**Defines the sound played when the thruster is started
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+LoopSnd:'''
**Defines the sound played when the thruster is continuously used
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+StopSnd:'''
**Defines the sound played when the thruster is shutting down
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Radar Image 2D:===
{{Table3611|
*Defines the bitmap used to represent the ship on the radar screen.
*Syntax: '''''Filename'''''}}
{{Table3615|
*'''$Radar Color Image 2D:'''
**Defines the color bitmap used to represent the ship on the radar screen.
**Syntax: '''''Filename'''''}}
{{Table3611|
*'''$Radar Image Size:'''
**Defines the size of the bitmap on the radar screen (length of the longer dimension)
**Syntax: '''''Integer'''''
*'''$3D Radar Blip Size Multiplier:'''
**Defines the multiplier used for blip size on the 3D radar.
**Syntax: '''''Float'''''}}

===$Glowpoint overrides:===
{{Table373|
*Creates a point that casts light onto ships and objects with the source being a glowpoint defined in the model file.
*Syntax: '''''( "String:Integer" )'''''
*String refers to name in [[glowpoints.tbl]]
*Essentially, [Name_of_glowpoint_override_in_glowpoints.tbl]:[Bank_in_POF]. If there is no override entry then the game will not generate a light. If you have multiple banks that use the same override, use a comma if they are not in order (2,4,7) and use a dash if they are in order (3-5 yields 3, 4, and 5).
**Example: '''$Glowpoint overrides: ( "teal_glow_10:1" "red_glow:2,3" "white_glow_10:4" "red_glow_10:5" "green_glow_10:6")'''
}}

===$Ship IFF Colors:===
{{Table3611|
*Defines the alternate color for the ship. Affects both the targeting brackets as well as the radar screen.
*'''+Seen By:'''
**Defines the IFF actually viewing the object (most often 'Friendly')
**Syntax: '''''String''''', name of an IFF class.
*'''+When IFF Is:'''
**Defines the IFF which the ship has to have for its color to be altered.
**Syntax: '''''String''''', name of an IFF class.
*'''+As Color:'''
**Defines the new color of the ship's targeting brackets and radar blip
**Syntax: '''''Integer list''''', red, blue and green respectively}}

===$Target Priority Groups:===
{{Table3611|
*Defines into which target priority groups the ship belongs to
*Syntax: '''''String list''''', names of the targeting groups
*'''+Override'''
**Overrides the ships existing groupings}}

===$EMP Resistance Modifier:===
{{Table3611|
*Defines the ships EMP resistance modifier:
*Syntax: '''''Float'''''}}

===$Piercing Damage Draw Limit:===
{{Table3611|
*Defines the maximum percentage of hitpoints ship has before piercing effects are enabled
*Syntax: '''''Float'''''
**Example: '''10''', sets the limit to 10%}}

===$Path Metadata:===
{{Table3613|
*Allows definition of extra metadata
*Syntax: '''''String''''', name of the path as defined in the ship POF file.
**Example: '''$Path Metadata: $Bay01'''
====+departure rvec:====
When using this path to depart via fighterbay, the departing ship will rotate to align itself with this rvec (so the right side of the ship is pointing in this direction). Only affects paths used to depart via fighterbay.
====+arrive speed multiplier:====
{{Table373|
*Modifies the speed of ships arriving from a fighterbay using this path. See [[Ai_profiles.tbl#.24bay_arrive_speed_multiplier:]] for details.
**Syntax: '''''Float'''''
}}
====+depart speed multiplier:====
{{Table373|
*Modifies the speed of ships departing to a fighterbay using this path. See [[Ai_profiles.tbl#.24bay_depart_speed_multiplier:]] for details.
**Syntax: '''''Float'''''
}}
}}

===$Subsystem<nowiki>:</nowiki>===
:''Main article: [[Subsystem]]''

==Ships.tbl flags==

==="no_collide"===
*Defines ship as non-collideable, ie. everything will go through it

==="player_ship"===
*Makes it possible for the player to fly the ship

==="default_player_ship"===
*Makes this ship as a default part of the loadout options in FRED

----

===Ship Type===
*Flags in this section are used to define the type of the ship
*Use only one '''ship type''' flag per table entry
{{Table3610|
*New ship types can be defined in [[objecttypes.tbl]]}}

===="repair_rearm"====
*Alternate name for "support"

===="support"====
*Defines the ship as repair and rearm vessel and sets AI behaviour accordingly
*Only one such vessel can be defined per species

===="cargo"====
*Defines ship as a cargo crate and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="fighter"====
*Defines ship as a fighter and also sets the AI behaviour
*In FS1/FS2 only ships flagged as fighters or bombers can accept the full set of player orders

===="bomber"====
*Defines ship as a bomber and also sets the AI behaviour
*In FS1/FS2 only ships flagged as fighters or bombers can accept the full set of player orders

===="transport"====
*Defines ship as a transport and also sets the AI behaviour

===="freighter"====
*Defines ship as a freighter and also sets the AI behaviour

===="capital"====
*Defines ship as a capital ship and also sets the AI behaviour
*By default, the ship's subsystems are scannable (this can be overridden by mission designers)
*The ship will warp out without ramping up to warpout speed
*When using the "Knossos" warpout, this ship will aim for the center of the portal

===="supercap"====
*Alternate name for "super cap"

===="super cap"====
*Defines ship as a super capital ship and also sets the AI behaviour
*The following things are true for all ships with this flag:
**When hit by debris, damage dealt by the collision is capped to between 10 and 20% of the ship's health maximum (determined randomly for each collision)
**All damage dealt by weapons without the corresponding supercap flag from weapons.tbl will be reduced by 75%
**In addition, once the ship is at or below 75% health, damage from non-supercap weapons is completely negated
**Do note that shockwave damage, regardless of origin, is not subject to these rules unless the "$Weapon shockwave damage respects huge ship flags:" setting in game_settings.tbl is set to true
**Ship subsystems are scannable by default (can be overridden by mission designers)
**The ship does not need to ramp up to warpout speed before entering subspace
**When using the "Knossos" warpout, the ship will aim for a departure point at the center of the Knossos portal

===="drydock"====
*Defines ship as a drydock and also sets the AI behaviour

===="cruiser"====
*Defines ship as a cruiser and also sets the AI behaviour

===="navbuoy"====
*Defines ship as a navbuoy and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="sentrygun"====
*Alternate name for "sentry gun"

===="sentry gun"====
*Defines ship as a sentrygun and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="escapepod"====
*Alternate name for "escape pod"

===="escape pod"====
*Defines ship as a escapepod and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="corvette"====
*Defines ship as a corvette and also sets the AI behaviour

===="gas miner"====
*Defines ship as a gas miner and also sets the AI behaviour

===="awacs"====
*Defines ship as a AWACS and also sets the AI behaviour

===="knossos"====
*Alternate name for the "Knossos device"

===="knossos device"====
*Defines ship as a Knossos and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="stealth"====
{{Table3610|
*Defines ship as a stealth-ship: non-targettable, and not on radar.}}

===="no type"====
*Does ???

----

==="ship copy"===
*Defines the ship as a copy of another model

==="in tech database"===
*Includes ships description to the tech database from the beginning of the campaign

==="in tech database multi"===
*Includes the ship to multiplayer tech database

==="dont collide invisible"===
*Defines invisible textures as non-collideable (For example, a hangar entrace)

==="big damage"===
*Limits the damage made to the ship by non-huge weapons.

==="no_fred"===
*Ship will not appear in FRED.

==="ballistic primaries"===
{{Table3610|
*Enables the ship to use ballistic primaries
*No longer needed, game handles it automatically}}

==="flash"===
{{Table3610|
*Makes a flash when a ship dies}}

==="surface shields"===
{{Table3610|
*Shots that impact the hull are applied to shields, regardless of if the ship has a shield mesh.}}

==="show ship"===
{{Table3610|
*Enable rendering the ship even when the ship is a player ship
*Will result in the player's ship model being rendered, when in cockpit mode}}

==="generate icon"===
{{Table3610|
*Creates a HUD icon from the model itself}}

==="gun convergence"===
{{Table3610|
*Enables ship to use the firing points' normals in defining the direction where the weapon fire}}

==="no thruster geometry noise"===
{{Table3611|
*Prevents noise from being added to the thruster effects geometry}}

==="intrinsic no shields"===
{{Table3611|
*Defines that ship has no shields by default, to allow mixing and matching shielded and unshielded craft in loadout}}

==="no primary linking"===
{{Table3611|
*Bypasses linked primaries while cycling. Does not block SEXPs/scripts that might be able to lock them, only the act of cycling for players and determing whether to link or not for AI.}}

==="no pain flash"===
{{Table3613|
*Prevents pain flash from being shown when ship is hit}}

==="dynamic primary linking"===
{{Table37|
*Allows this ship use the primary firepoint cycling code. With a key bind added in 3.6.13, you can toggle between various factorizations of primary firepoint groupings on a per-primary bank basis. So a 4-firepoint bank could cycle through all four firepoints firing together (1x4), each firepoint firing individually (4x1, all 4 firing over the timespan of the bank cooldown, so no change in damage over time, or DPS, occurs from retail behavior), or firing in pairs (2x2).}}

==="no ets"===
{{Table37|
Sets ship class to have no ETS}}

==="no lighting"===
{{Table3613|
Ship will not receive lighting calculations}}

==="auto spread shields"===
{{Table371|
Causes the ship's shield mesh (if any) to be ignored and a shield of a given thickness to be automatically projected around the ship's hull. Weapons will impact the ship's shields at a distance equal to the shield thickness defined in [[Ships.tbl#.2BAuto_Spread:|#.2BAuto_Spread:]], but not before the weapon itself has travelled at least a distance equal to that. Note that impact effects normally projected onto the shield mesh will not work.}}

==="model point shields"===
{{Table371|
Instead of the standard 4 shield quadrants, the ship uses an arbitrary number of shield sections which must have been defined in the model file, see [[Model Point Shields]]. If used on a player ship, you must also define [[Ships.tbl#.24Model_Point_Shield_Controls:|#.24Model_Point_Shield_Controls:]] to allow the shield augmentation controls to be used.}}

==Wing Formations==
===$Name:===
{{Table202|
*Provides a unique name for the formation, followed by the list of positions occupied by each member of the wing relative to their leader. The leader is always at 0,0,0 and is omitted, so the first position is the second in the wing, and second is the third in the wing, etc. Each formation must contain all 5 positions.
*NOTE: FSO automatically scales these these positions by the ship's size, so the table values will be very small. You can see the retail formation's values below for reference.
*Syntax: (a list of 5 '''''Vectors'''''), each has three '''floats''', x-axis, y-axis, z-axis, respectively}}

===Example===

<pre>
#Wing Formations

$Name: Default
((-0.39, 0.20, -0.59)
( 0.39, 0.20, -0.59)
(-0.78, 0.39, -1.18)
( 0.00, 0.39, -1.18)
( 0.78, 0.39, -1.18))

#End
</pre>

==Player Ship Precedence==
*Syntax: ( '''''"String" "String"''''')
===Example===

<pre>
$Player Ship Precedence: (
"GTF Ulysses"
"GTF Hercules"
"GTB Medusa"
"GTB Ursa" )
</pre>

==Sample==

<pre>
#Default Player Ship

$Name: GTF Ulysses

#End

#Engine Wash Info

$Name: Default
$Angle: 10.0
$Radius Mult: 1.2
$Length: 400
$Intensity: 1.0

#End

#Ship Classes
$Name: GTF Ulysses
$Short name: TFight
$Species: Terran
+Type: XSTR("Space Superiority", -1)
+Maneuverability: XSTR("Excellent", -1)
+Armor: XSTR("Light", -1
+Manufacturer: XSTR("Triton / Mekhu", -1)
+Description: XSTR( " ", -1)
$end_multi_text
+Tech Description: XSTR("Descriptive text", -1)
$end_multi_text
+Length: 16 m
+Gun Mounts: 4
+Missile Banks: 1
$POF File: fighter01.pof
$Detail Distance: (0, 80, 300, 900)
$ND: 42 42 244
$Show Damage: YES
$Density: 1
$Damp: 0.1
$Rotdamp: 0.35
$Max Velocity: 0.0, 0.0, 70.0
$Rotation Time: 3.0, 2.6, 5.0
$Rear Velocity: 0.0
$Forward Accel: 2.0
$Forward Decel: 1.5
$Slide Accel: 0.0
$Slide Decel: 0.0
$Expl Inner Rad: 25.0
$Expl Outer Rad: 55.0
$Expl Damage: 15.0
$Expl Blast: 1000.0
$Expl Propagates: NO
$Shockwave Speed: 0.0
$Allowed PBanks: ( "Subach HL-7" "Prometheus R")
$Allowed Dogfight PBanks: ( "Subach HL-D" "Prometheus D" )
$Default PBanks: ( "Subach HL-7" "Prometheus R" )
$Allowed SBanks: ( "Rockeye" "Tempest" )
$Allowed Dogfight SBanks: ( "Tempest D" "Hornet D" )
$Default SBanks: ( "Harpoon" )
$SBank Capacity: ( 40 )
$Shields: 380
$Shield Color: 100 100 255
$Power Output: 2.0
$Max Oclk Speed: 94.0
$Max Weapon Eng: 80.0
$Hitpoints: 180
$Flags: ( "player_ship"
"default_player_ship"
"fighter"
"in tech database")
$AI Class: Captain
$Afterburner: YES
+Aburn Max Vel: 0.0, 0.0, 150.0
+Aburn For accel: 0.7
+Aburn Fuel: 300.0
+Aburn Burn Rate: 50.0
+Aburn Rec Rate: 25.0
$Countermeasures: 25
$Scan Time: 2000
$EngineSnd: 128
$Closeup_Pos: 0.0, 0.0, -22
$Closeup_Zoom: 0.5
$Shield_Icon: shield-f01
$Ship_Icon: iconfighter01
$Ship_Anim: ssfighter01
$Ship_Overhead: loadfighter01
$Score: 8
$Trail:
+Offset: -7.75 -2.8 0.75
+Start Width: 0.25
+End Width: 0.05
+Start Alpha: 1.0
+End Alpha: 0.0
+Max Life: 1.0
+Spew Time: 60
+Bitmap: Contrail01
$Trail:
+Offset: 7.75 -2.8 0.75
+Start Width: 0.25
+End Width: 0.05
+Start Alpha: 1.0
+End Alpha: 0.0
+Max Life: 1.0
+Spew Time: 60
+Bitmap: Contrail01
$Subsystem: communication, 10, 0
$Subsystem: navigation, 10, 0
$Subsystem: weapons, 20, 0
$Subsystem: sensors, 10, 0
$Subsystem: engines, 35, 0

#End

$Player Ship Precedence: (
"GTF Ulysses")
</pre>

[[Category:Tables]]

Game settings.tbl

2019-12-22T04:35:42Z

AdmiralRalwood: Adding some missing settings.

{{SCP_table}}

{{TableVersionGit|2019-12-18|58992cf}}

The '''game_settings.tbl''', also known as mod.tbl, defines options that can be changed globally. All settings are optional.

This table is one of the [[Modular Tables]] and can be extended with xxx-mod.tbm

[[Tables|List of Tables]]

==#GAME SETTINGS==
Contains settings that affect how the engine works.

===$Target Version:===
{{Table373|
Specifies the minimum version of FreeSpace Open that this mod supports. If the version specified here is greater than the version of the current build, an error message is displayed.
}}
{{Table381|
The $Minimum version option has been renamed to $Target Version. The old name is kept with the same functionality for backwards-compatibility.

The target version specifies what version of the FSO engine this mod was created for. It will be used by the engine to enable or disable backwards-incompatible changes by default. The default value is 2.0 which specifies that the mod targets the retail engine version.
}}

====+Major:====
{{Table373|
Required. Sets the major component of the target version.
*Syntax: '''''Integer'''''
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Minor:====
{{Table373|
Required. Sets the minor component of the target version.
*Syntax: '''''Integer'''''
*Example: '''''7''''' (for a minimum version of 3.7.3.20151121)
}}

====+Build:====
{{Table373|
Required. Sets the build component of the target version.
*Syntax: '''''Integer'''''
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Revision:====
{{Table373|
Sets the revision component of the target version. If no revision is given then all builds of that release are supported (even nightly builds if there are any).
For nightly builds this is the date in YYYYMMDD format.
*Syntax: '''''Integer'''''
*Example: '''''20151121''''' (for a minimum version of 3.7.3.20151121)
}}

===$Window title:===
{{Table382|
Specifies the name of the FSO window when this mod is running. If blank or unspecified, the window will have the default title of "FreeSpace 2".
*Syntax: '''''String'''''
}}

===$Window icon:===
{{Table382|
Specifies the icon filename of the FSO window when this mod is running. If blank or unspecified, the window will have the default icon.
*Syntax: '''''String'''''
}}

===$Unicode mode:===
{{Table382|
Enabled the Unicode text mode for this mod. In Unicode mode all text is assumed to be UTF-8 encoded Unicode and certain features are disabled if they do not have full Unicode support. Most notably, if this is enabled then the engine will no longer support the old bitmap fonts that were used by Retail FreeSpace. Only the newer TrueType fonts will be supported.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

==#CAMPAIGN SETTINGS==
This group contains various Campaign related settings and overrides.

===$Default Campaign File Name:===
Defines which campaign will be selected by default for new pilots. A file extension is not needed and, if present, is removed by the code.
*Syntax: '''''String'''''

===#Ignored Campaign File Names===
Defines which campaigns, if present, will not appear in the Campaign Room. In the original implementation, only single-player campaigns could be ignored and file extensions were required, but see below.
{{Table371|As of 3.7.1, file extensions are not required and, if present, are removed by the code.}}
{{Table382|As of 3.8.2, file name comparisons are not case sensitive and multiplayer campaigns can be ignored.}}
====$Campaign File Name:====
File name of the campaign to ignore. Multiple entries may exist.
*Syntax: '''''String'''''

===#Ignored Mission File Names===
{{Table382|Defines which standalone missions, if present, will not appear in the Tech Room or Multiplayer Lobby. Both single-player and multiplayer missions can be ignored, but missions which appear in a campaign cannot. File extensions are not required and, if present, are removed by the code. File name comparisons are not case sensitive.
====$Mission File Name:====
File name of the mission to ignore. Multiple entries may exist.
*Syntax: '''''String'''''
}}

===$Red-alert applies to delayed ships:===
{{Table372|Controls whether red-alert saved statistics (hitpoints, weapons, subsystem strengths) will be restored for ships that are not present at mission start.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

==#HUD SETTINGS==
This group contains various HUD behavior settings and overrides

===$Directive Wait Time:===
*Defines how long the game will wait before displaying a directive.
*Syntax: '''''Integer'''''
*Values: '''''Greater than or equal to 0 ms'''''

===$Cutscene camera displays HUD:===
Show the HUD when the cutscene camera is enabled.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Cutscene camera disables HUD: and had a default of YES.

===$Full color head animations:===
Enables full-color head ANIs. Normal head ANIs will appear in gray.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Color head animations with hud colors: and had a default of YES.

==#SEXP SETTINGS==
This group contains SEXP settings and overrides.

===$Loop SEXPs Then Arguments:===
Flips how when-argument settings loop. See: [http://www.hard-light.net/forums/index.php?topic=79602.0 SEXP Argument changes via mod.tbl]
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

===$Use Alternate Chaining Behavior:===
When set, this allows all events in a chain to repeat, instead of only the last one. It makes the event chaining behavior act as people expected it to be in [http://scp.indiegames.us/mantis/view.php?id=82 Mantis #82].
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

==#GRAPHICS SETTINGS==
This group contains settings related to graphics.

===$Enable External Shaders:===
Enables the use of external shader files. By default, the engine will use the built-in shaders.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

===$Default Detail Level:===
{{Table3615|
Determines which graphics detail level preset (low, medium, high, very high) acts as the default for new pilots.
*Syntax: '''''Integer''''' (0-3)
*Default Value: '''''3''''' (very high)}}

===$Briefing Window FOV:===
{{Table371|
Determines the FOV in the briefing Icon window. Retail default for this is 0.29375, previous versions of FSO used a value of 0.5.
*Syntax: '''''Float''''' (0.0 to 1.0)
*Default Value: '''''0.29375'''''}}

===$Generic Pain Flash Factor:===
{{Table373|
Determines the intensity of the pain red flash when the player is hit.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$Shield Pain Flash Factor:===
{{Table373|
Determines the intensity of a pain flash when the player's shields are hit. Color will match the current ships shield color defined in ships.tbl. A value of 0 will give retail behavior (no shield effect). Positive values will cause the effect to start at full intensity at full shields and go to next to no intensity at zero shields. Negative values will cause no effect at full shields and full effect at no shields. Values should be kept between -1.0 and 1.0 for good pilot visibility.
*Syntax: '''''Float'''''
*Default Value: '''''0.0'''''}}

===$BMPMAN Slot Limit:===
{{Table382|
Determines the maximum number of textures that can be loaded simultaneously. This includes every frame of an animation, unless that animation is streaming (e.g. command briefing animations, message talking heads, etc). Also includes dynamically-created textures (used internally for various functions).
*Syntax: '''''Int'''''
*Values: '''''Greater than or equal to 3500'''''
*Default Value: '''''4750'''''}}

===$EMP Arc Color:===
{{Table382|
Allows custom RGB color values to be set for the EMP lightning arc effect.
*'''+Primary Color Option 1:'''
**The RGB color of the first primary color for the EMP lightning arc effect.
**The actual lightning arc color shown in-game is randomly selected between the first and second primary color.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (64, 64, 5)
*'''+Primary Color Option 2:'''
**The RGB color of the second primary color for the EMP lightning arc effect.
**The actual lightning arc color shown in-game is randomly selected between the first and second primary color.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (128, 128, 10)
*'''+Secondary Color Option 1:'''
**The RGB color of the secondary color for the EMP lightning arc effect.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (255, 255, 10)
}}

===$Damage Arc Color:===
{{Table382|
Allows custom RGB color values to be set for the damage lightning arc effect.
*'''+Primary Color Option 1:'''
**The RGB color of the first primary color for the damage lightning arc effect.
**The actual lightning arc color shown in-game is randomly selected between the first and second primary color.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (64, 64, 255)
*'''+Primary Color Option 2:'''
**The RGB color of the second primary color for the damage lightning arc effect.
**The actual lightning arc color shown in-game is randomly selected between the first and second primary color.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (128, 128, 255)
*'''+Secondary Color Option 1:'''
**The RGB color of the secondary color for the damage lightning arc effect.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (64, 64, 5)
}}

==#NETWORK SETTINGS==
This group contains network-related settings

===$FS2NetD port:===
*(description required)

==#SOUND SETTINGS==
This group contains sound-related settings

===$Default Sound Volume:===
{{Table371|
*Defines the default sound fx volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0
*Default Value: '''''1.0'''''}}

===$Default Music Volume:===
{{Table371|
*Defines the default music volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0
*Default Value: '''''0.5'''''}}

===$Default Voice Volume:===
{{Table371|
*Defines the default voice volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0
*Default Value: '''''0.7'''''}}

==#FRED SETTINGS==
This group contains settings for FRED.

===$Disable Hard Coded Message Head Ani Files:===
{{table371|
If set, FRED will not fill the head ani selection in the Event Editor with the retail head ani filenames.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Enable scripting in FRED:===
{{table382|
If set, scripting will be enabled in FRED. Use with extreme caution. The effects of scripts on FRED have not been fully tested. You can check if a script is running in FRED by using ba.inMissionEditor().
*Default Value: '''''NO'''''}}

==#OTHER SETTINGS==
This group contains miscellaneous settings.

===$Fixed Turret Collisions:===
Makes all hits to a turret's barrels count as hits to the turret subsystem. By default, this does not happen unless the point of impact falls inside the model radius of the turret's base.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

===$Damage Impacted Subsystem First:===
If set, a hit to a physical subsystem will always deal damage to that subsystem first, even if another subsystem is closer to the point of impact. By default, the closest subsystem will always receive damage first.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''

===$Default ship select effect:===
{{Table3615|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Default weapon select effect:===
{{Table3615|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Weapons inherit parent collision group:===
{{Table3615|
*When set to true, Weapons fired by a ship will inherit their parents' collision group setting.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Flight controls follow eyepoint orientation:===
{{Table371|
*Specifies that if the player ship's eyepoint happens to rotate into a non-standard orientation, pitch and yaw axes should stay relative to the eyepoint orientation, not the ship. Note that this does not affect the pitch/yaw turning speed, which always remains relative to the ship.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Beams Use Damage Factors:===
{{Table371|
*Specifies that beam weapons will use the tabled damage factors for Armour, Shields and Subsystems. Default is false (i.e. all factors are treated as 1.0)
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Default fiction viewer UI:===
{{Table373|
*Specifies which fiction viewer layout to use in missions that don't specify one. Possible values are as follows:
**"FS2": Standard layout. Requires (2_)fictionviewer and (2_)fictionviewer-m to be present in data\interface.
**"WCS": Moves the "Accept" button to the lower-left corner of the screen. Requires (2_)fictionviewerb and (2_)fictionviewer-mb to be present in data\interface.
**"auto": Selects "WCS" if the appropriate files are present; otherwise, selects "FS2". This is the default setting.}}

===$Movie subtitle font:===
{{Table382|
*Specifies which font should be used for displaying subtitles in the cutscene player. This should be the name given to this font in the fonts table. Since movie subtitles can contain Unicode text it is a good idea to enable Unicode mode when movie subtitles are used but this is not enforced by this option.
*Syntax: '''''String'''''}}

===$Disable built-in translations:===
{{Table382|
*Turns off hard-coded translations, e.g. Transport -> Transporter in German. All strings will either use their XSTR entry or else not be translated.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Weapon shockwave damage respects huge ship flags:===
{{Table382|
*Controls whether weapon shockwaves will respect the huge/supercap ship flags. In retail they do not.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Enable external default scripts:===
{{Table382|
*Enables the loading of external scripts with the same name as a built-in script. Otherwise, uses the version of the script included in the executable (currently, just cfile_require.lua).
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Player warpout speed:===
{{Table190|
*Defines the speed the player must reach to warp out.
*Syntax: '''''Float'''''
*Default Value: '''''40.0'''''}}

===$Target warpout match percent:===
{{Table190|
*Defines how close to the warpout speed the player needs to be to actually warp out.
*Syntax: '''''Float''''', between 0.0 and 1.0
*Default Value: '''''0.05''''' (5%)}}

===$Minimum player warpout time:===
{{Table190|
*The [[Ships.tbl#.24Warpout_Engage_Time:|default amount of time]], in seconds, warping out will take before actually starting to check whether the player is the right speed.
*Syntax: '''''Float'''''
*Default Value: '''''3.0'''''}}

===$Enable in-game options:===
{{Table190|
*Experimental mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. Requires custom assets for the in-game options menu to actually be able to change the settings.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Dinky Shockwave Default Multiplier:===
{{Table190|
*Amount of damage, as a multiple of normal shockwave damage, assigned to a weapon's [[Weapons.tbl#.24Dinky shockwave:|dinky shockwave]] by default. To get the same behavior FSO had from 2005-2019, set this to 0.25.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

==#END==
Required. The last line of the table must be #END

==Sample Entry==

#CAMPAIGN SETTINGS
$Default Campaign File Name: NewCampaignFile

#Ignored Campaign File Names
$Campaign File Name: FreeSpace2.fc2

#HUD SETTINGS
$Directive Wait Time: 5000

#SEXP SETTINGS
$Loop SEXPs Then Arguments: True

#OTHER SETTINGS
$Fix Turret Collisions: True

#END

[[Category:Tables]]

Ships.tbl

2019-12-22T04:35:07Z

AdmiralRalwood: /* $Warpout Engage Time: */ Link to "$Minimum player warpout time:" in Game_settings.tbl, since it's where that default can be changed.

{{TableVersionGit|2019-05-07 UTC|5f5616c0f}}

The '''ships.tbl''' defines all the ship classes used in FSO.

This table is one of the [[Modular Tables]] and can be extended with xxx-shp.tbm

[[Tables|List of Tables]]

==General Format==
*Ship.tbl is formed of several different sections.
*All sections beginning with <nowiki>#</nowiki> need <nowiki>#</nowiki>End before the next section.
**<nowiki>#</nowiki>'''Default Player Ship'''
***Defines the default player ship in the game and also in the FRED. If in a mission appears a ship that has not been properly included to tables then game replaces the ship with the Default Player Ship.
**<nowiki>#</nowiki>'''Engine Wash Info'''
***Includes all the definitions of all engine washes used in the game.
{{Table3610|
:*<nowiki>#</nowiki>'''Ship Templates'''
:**Includes entries for ship templates}}

:*<nowiki>#</nowiki>'''Ship Classes'''
:**Includes entries for every ship and also defines their attributes that are used in the game
:**Is discussed in detail at [[Ships.tbl#Table_Options|Table Options]] section.
:*'''$Player Ship Precedence'''
:**Player Ship Precedence is used in ship selection when a ship specified by the mission designer is not available to the player. The next ship on the list is used in its place (assuming that ship is allowed for the player)

==Default Player Ship==
*Defines the default ship in the game.
*Syntax: ''Name'', name of ship model as defined in [[Ships.tbl#Table_Options|Table Options]].

==Engine Wash==
*Defines the engines washes
*First entry must be named 'default'

===$Name:===
*Defines the name of the engine wash.
*Syntax: '''''String'''''

===+nocreate===
{{Table3610|
*In [[Modular Tables]] name can be followed by line '''+nocreate''' that prevent game from creating an incomplete entry by leaving the entry unread unless it already exists (either in ship.tbl or in earlier parsed *-shp.tbm files) by the time the *-shp.tbm is read.}}

===$Angle:===
*Defines the angle from the engine where the engine wash exists
*Syntax: '''''Float''''', degrees

===$Radius Mult:===
*Defines engine wash multiplier
*Syntax: '''''Float'''''

===$Length:===
*Defines the length of the engine wash
*Syntax: '''''Float''''', meters

===$Intensity:===
*Defines the strength of the engine wash
*This setting does nothing
*Syntax: '''''Float''''', blast effect

'''Example'''

$Name: Default
$Angle: 10.0
$Radius Mult: 1.2
$Length: 400
$Intensity: 1.0

==Ship Template Options==
{{Warning|
The ship templates feature has always caused crashes and memory issues. As of 2014/07/24, it has been removed from the codebase.}}
{{Table3610|
*Example of template usage [[Ship_Templates]] in which both [[GTB Artemis]] variants have been defined using a single template}}

===$Template:===
{{Table3610|
*Defines the name of template
*Syntax: '''''String''''', name}}

===+Use Template:===
{{Table3610|
*Another template can be used as template for the current template
*Syntax: '''''String''''', name}}

==Ships Table Options==

===$Name:===
*Model name that is used also in game. It is also used as name for the whole ship entry. There are two special characters can be used in the name: '''#''' and '''@'''
**'''#'''. It's used in the middle of the name and cannot be the first character in the $Name: string. It makes the right part of the name not being shown in the ship class info of the target window, (or beside the target brackets in FS_Open builds). It allows making different versions of a base ship while showing the same class name inside the game. An example from FSPort FreeSpace 1: The '''SF Dragon#weakened''' ship, used in [[Enter the Dragon]], appears to the player just as any other '''SF Dragon'''.
**'''@'''. It's used before the proper ship name. It is fully ignored by the game. Moreover, '''@WhateverShip''' and '''WhateverShip''' are exactly the same name and therefore they both appear as '''WhateverShip''' inside the game. It just allows the user marking ships in the table because of any modding reason. In the retail FS2 ships there are several ships starting by '''@'''.
*Syntax: '''''String''''', name

===+nocreate===
{{Table3610|
*In [[Modular Tables]] name can be followed by line '''+nocreate''' that prevent game from creating an incomplete entry by leaving the entry unread unless it already exists (either in ship.tbl or in earlier parsed *-shp.tbm files) by the time the *-shp.tbm is read.}}

===+Use Template:===
{{Table3610|
*Sets the table entry to use template based on an existing table entry instead of creating totally new one
*Syntax: '''''String''''', name of the template}}

===$Alt Name:===
{{Table3613|
*Alternative $Name: for the ship.
*Syntax: '''''String''''', Alternate $Name:}}

===$Short name:===
*Shortened model name, for FRED, Usually more descriptive than the real name.
*Syntax: '''''String''''''

===$Species:===
*Defines species (Terran, Vasudan or Shivan). Determines many things, including the color of the engine glow, the flyby sound effects, the briefing icon and the support ship.
{{Table3610|
*More species have been enabled, and all of these have to be defined in [[species_defs.tbl]].}}

*Syntax: '''''String''''', name of the species
**Example: ''Terran''

===Technical Description===
List of descriptive terms for techroom and ship selection screens. Number after the quotes refers to [[tstrings.tbl]]

====+Type:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Maneuverability:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Armor:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Manufacturer:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Description:====
*Syntax: XSTR("'''''String'''''", integer)
*Requires '''$end_multi_text''' after the entry
*Example:
::XSTR("", -1)
::$end_multi_text

====+Tech Title:====
{{Table3613|
*Defines name of the ship as displayed in the tech room
*Syntax: '''''String'''''}}

====+Tech Description:====
*Syntax: XSTR("'''''String'''''", integer)
*Requires '''$end_multi_text''' after the entry
*Example:
::XSTR("", -1)
::$end_multi_text

====+Length:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Gun Mounts:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

====+Missile Banks:====
*Syntax: XSTR("'''''String'''''", integer)
*Example: XSTR("", -1)

===$Selection Effect:===
{{Table3613|
*Defines which selection effect to use when the -ship_choice_3d commandline flag is enabled or no ani can be found for the selected ship.
*Syntax: String, either "FS1", or "Off". This defaults to the FS2 effect.}}

===$Cockpit POF file:===
{{Table3610|*Filename of the cockpit model file
*Syntax: '''''String.pof''''', model filename}}

===+Cockpit Offset:===
{{Table3610|*Defines the offset of the cockpit model
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively}}

===$Cockpit Display:===
{{Table3615|
*Defines a rectangle surface on a cockpit texture that can be updated dynamically. Multiple displays can be defined, but only one needs to be defined for each texture on the cockpit model.
*'''+Texture:'''
*The filename of the cockpit texture to be replaced.
*Syntax: '''''String''''', texture filename
*'''+Offsets:'''
* (Optional) The offsets of the rectangle surface into the texture that will be drawn into.
*Syntax: '''''Vector''''', two '''integers'''
*'''+Size:'''
* The size of the rectangle surface that will be drawn into.
*Syntax: '''''Vector''''', two '''integers'''
*'''+Background:'''
* (Optional) Filename of the bitmap to be used as the background of this display.
*Syntax: '''''String''''', texture filename
*'''+Foreground:'''
* (Optional) Filename of the bitmap to be used as the foreground of this display.
*Syntax: '''''String''''', texture filename
*'''+Display Name:'''
* A name to be used as a reference handle.
*Syntax: '''''String'''''}}

===$POF File:===
*Filename of the model file (.pof) at data/models folder
*Syntax: '''''String.pof''''', model filename

===$POF file Techroom:===
*Filename of the model file (.pof) at data/models folder; used only in the weapon loadout screen
*Syntax: '''''String.pof''''', model filename

===$Texture Replace:===
{{Table3610|
*'''+old:'''
*Defines the texture to be replaced
**Syntax: '''''String''''', filename
*'''+new:'''
*Defines the new texture
**Syntax: '''''String''''', filename}}

===$POF Target File:===
*Optional hud targeting model
*Syntax: '''''String.pof''''', model filename

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

===$Detail Distance:===
*Defines the distance where the change between different Levels-Of-Details (LODs) occurs
*Take notice that these are base values. Model detail in Detail options, (within game press F2), applies a multiplier to these values. These multipliers default to (from left to right): 1/8, 1/4, 1, 4, and 8, and may be overridden by the [[Ai_profiles.tbl#$Detail Distance Multiplier:|$Detail Distance Multiplier]]
*Syntax: '''''(Detail Distances)''''' , list of '''integers''' (same amount as LODs), distances from the model in meters
**Example: ''(0, 80, 300, 900)''

===$Collision LOD:===
{{Table373|
*Defines an alternative LOD (Level-Of-Detail) to use for collision detection. Using this can increase performance without visible drawbacks if the LOD chosen has much simpler geometry but the shape still closely matches the base model.
*This works as follows: collision detection proceeds normally through the various model/submodel radius and bounding box checks based on LOD0, but when the game decides to perform a mesh-based collision check of a given submodel, it will use the submodel's LOD mesh instead. However, all submodels do not need to have a counterpart in the given LOD; if one is not found, the closest alternative will automatically be used instead.
*For example, if ''$Collision LOD: 3'' is used and the submodel engine01a is checked for a hit, the game will attempt to use the mesh of engine01d instead. However, if there is no engine01d submodel, the game will find the closest alternative: it'll look for engine01c, then engine01b, and finally fall back to engine01a. Note the implications of for example the root LOD submodel (detaild, detail3, etc) including the geometry of subsystem submodels; if detail0 is checked for a collision before engine01a, and detail3 includes the engine geometry (as opposed to having it in engine01d), then the subsystem engine01a cannot be hit.
**Syntax: '''''Integer'''''}}

===$ND:===
*No Dim field field was used in FreeSpace for ship lights. Use of glowmaps is preferred to the $ND entry. Only noticeable in Glide or Software mode.
*Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
**Example: ''42, 42, 224''

===$Enable Team Colors:===
{{Table3615|
*Enables Team Colors for a ship without setting a default color setting.
*Syntax: '''''Boolean'''''}}

===$Default Team:===
{{Table3615|
*Specifies the default team name to be used for coloring a ship.
*None is will set the default to 'no coloring'.
*Syntax: '''''String''''', name of the teams as defined in [[colors.tbl]]}}

===$Show Damage:===
*No function at all. The engine will read values, but discard them. In 3.6.10 or later, this can be left out without adverse consequences.
*Syntax: '''''Boolean''''', yes or no, usually yes

===$Damage Lightning Type:===
{{Table3613|
*Changes the damage lightning effect shown on highly damaged ships.
*Can be defined as:
**''None''
**''Default''}}

===$Impact:===
{{Table3610|
*'''+Damage Type:'''
**Defines the damage type of the collision
**Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]}}

===$Impact Spew:===
{{Table3610|
*Used to define the impact particle spew
*Note: You CANNOT define a different type of particle spew here; the only option possible is listed below
*'''+Max particles:'''
**Defines the maximum number of particles spewed
**Setting to zero causes model to generate no particles at all
**Syntax: '''''Integer'''''
**Default Value: 30}}{{Table3613|
*'''+Min particles:'''
**Defines the minimum number of particles spewed
**Syntax: '''''Integer'''''
**Default Value: 25
*'''+Max Radius:'''
**Defines the maximum radius of particles
**Syntax: '''''Float'''''
**Default Value: 0.5f
*'''+Min Radius:'''
**Defines the minimum radius of particles
**Syntax: '''''Float'''''
**Default Value: 0.2f
*'''+Max Lifetime:'''
**Defines the maximum lifetime of particles
**Syntax: '''''Float'''''
**Default Value: 0.55f
*'''+Min Lifetime:'''
**Defines the minimum lifetime of particles
**Syntax: '''''Float'''''
**Default Value: 0.05f
*'''+Max Velocity:'''
**Defines the maximum velocity of particles
**Syntax: '''''Float'''''
**Default Value: 12.0f
*'''+Min Velocity:'''
**Defines the minimum velocity of particles
**Syntax: '''''Float'''''
**Default Value: 2.0f
*'''+Normal Variance:'''
**Defines the variance of particle direction from the normal
**Syntax: '''''Float'''''
**Default Value: 1.0f}}

===$Damage Spew:===
See [[Ship.tbl#$Impact Spew:|Impact Spew entry]]
*Controls the 'smoke' released on weapon impact point
*Certain default values (marked with '''X''') gain a specific multiplier based on ship radius
::If the radius is less than 20 the multiplier is 1
::If the radius is larger than 40 the multipler is 1.2
::Otherwise it is between 1 and 1.2
{{Table3610|
*'''+Max Particles:'''
**Default Value: 50 * '''X'''}}{{Table3613|
*'''+Min Particles:'''
**Default Value: 20 * '''X'''
*'''+Max Radius:'''
**Default Value: 1.3
*'''+Min Radius:'''
**Default Value: 0.7
*'''+Max Lifetime:'''
**Default Value: 1.5 * '''X'''
*'''+Min Lifetime:'''
**Default Value: 0.7 * '''X'''
*'''+Max Velocity:'''
**Default Value: 12.0
*'''+Min Velocity:'''
**Default Value: 3.0
*'''+Normal Variance:'''
**Default Value: 0.2 * '''X'''}}

===$Collision Physics:===
{{Table3613|
*Parameters affecting collision physics, including landings.
*"Landing" means the ship will not take damage or shake when it touches down. Instead, the ship will reorient towards a neutral resting orientation. "Reorient" thresholds below mean that the ship will still take damage (counts as a crash) but will move towards the correct landing orientation.

====+Bounce:====
When this ship collides with a large ship, how many meters to instantly move it away. Default is 5.0.
====+Both Small Bounce:====
When this ship collides with a small ship, how many meters to instantly move it away. Default is 5.0.
====+Friction:====
During collisions, how much friction to apply (slowing lateral movement). Default is 0.0.
====+Rotation Factor:====
Affects the rotational energy of collisions. Default is 0.2.
====+Landing Max Forward Vel:====
Maximum velocity for which landing physics are used.
====+Landing Min Forward Vel:====
Minimum velocity for which landing physics are used.
====+Landing Max Descent Vel:====
Maximum velocity at which the ship can "hit the deck" and still be considered a landing.
====+Landing Max Horizontal Vel:====
Maximum sideways velocity the ship can land at.
====+Landing Max Angle:====
Maximum angle of attack the ship can land at (in degrees).
====+Landing Min Angle:====
Minimum angle of attack the ship can land at (in degrees).
====+Landing Max Rotate Angle:====
How many degrees the ship can be rotated relative to the landing surface in order to count as a landing.
====+Reorient Max Forward Vel:====
Maximum velocity for which the ship will be adjusted to the correct landing orientation.
====+Reorient Min Forward Vel:====
Minimum velocity for which the ship will be adjusted to the correct landing orientation.
====+Reorient Max Descent Vel:====
Maximum velocity at which the ship can "hit the deck" and still reorient.
====+Reorient Max Horizontal Vel:====
Maximum sideways velocity for reorienting.
====+Reorient Max Angle:====
Maximum angle of attack for reorienting to kick in (in degrees).
====+Reorient Min Angle:====
Minimum angle of attack for reorienting to kick in (in degrees).
====+Reorient Max Rotate Angle:====
How many degrees the ship can be rotated relative to the landing surface in order to be reoriented on impact.
====+Reorient Speed Mult:====
How quickly the reorientation takes place (when applicable)
====+Landing Rest Angle:====
Angle of the ship's nose relative to the plane of the landing surface when the ship is at rest. Reorient will move the ship towards this angle.
====+Landing Sound:====
Sound to play when landing (if it's not a landing, normal collision sound is used).
}}

===$Debris:===
{{Table3610|
*'''+Min Lifetime:'''
**Defines the minimum lifetime of the debris (Default value is a random number)
**Syntax: '''''Float,''' Seconds
*'''+Max Lifetime:
**Defines the maximum lifetime of the debris
**Syntax: '''''Float,''' Seconds
*'''+Min Speed:
**Defines the minimum speed of the debris
**Syntax: '''''Float,''' Meters/second
*'''+Max Speed:
**Defines the maximum speed of the debris
**Syntax: '''''Float,''' Meters/second
*'''+Min Rotation speed:
**Defines the minimum rotational speed of the debris (Default is (6 to 10)/Ship-radius)
**Syntax: '''''Float,''' Radians/second
*'''+Max Rotation speed:
**Defines the maximum rotational speed of the debris
**Syntax: '''''Float,''' Radians/second
*'''+Damage Type:'''
**Defines the damage type of the debris
**Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]}}
{{Table3611|
*'''+Min Hitpoints:'''
**Defines the minimum hitpoints assigned for the generated debris pieces
**Syntax: '''''Float'''''
*'''+Max Hitpoints:'''
**Defines the maximum hitpoints assigned for the generated debris pieces
**Syntax: '''''Float'''''
*'''+Damage Multiplier:'''
**Defines the collision damage multiplier for collisions against the generated debris pieces
**Syntax: '''''Float'''''
*'''+Lightning Arc Percent:'''
**Controls what percent of debris pieces will have the damage lightning effect applied to them.
**Defaults to 50%.
**Syntax: '''''Float,''' 0-100}}

===$Density:===
*This defines how hard you hit something. If you set it very high, a collision will the lower density ship and not yours; the higher the numbers are, the harder they will hit and the farther they will be pushed. However, this doesn't apply to asteroids. When a high density fighter collides with an asteroid, the high-density fighter will receive damage, but it will also destroy the asteroid. Setting a density of 1000 on a fighter with 180 hitpoints will cause the fighter to immediately explode if it collides with, say, an asteroid. A low-density fighter will not have any effect on an asteroid, but if the fighter destroys the asteroid, the fighter will fly far away.
*Syntax: '''''Float''''', usually 1. Must not be 0.

===$Damp:===
*Sets the natural period (1 / omega) of the dampening effects on top of the acceleration model. (See [[Ships.tbl#$Forward Accel:|$Forward Accel:]])
*In essence, affects how quickly you will accel/decel to your target velocity. Higher damp means slower acceleration and deceleration, while lower values (down to 0.0001) means faster acceleration/deceleration.
**Specifying a value of 0.0 means there is no damping placed on top of the acceleration model, which is the most responsiveness you'll get.

*Syntax: '''''Float'''''

===$Rotdamp:===
*Shares the same principles of [[Ships.tbl#$Damp:|$Damp]], but is applied to rotations directly. (there isn't a engine/thrust acceleration model for rotations)
*Syntax: '''''Float'''''

===$Banking Constant:===
{{Table3610|
*Defines a factor for how much roll is added during a yaw. Set as 1 for full roll and 0 is no roll. Default is 0.5.
*Syntax: '''''Float'''''}}

===$Max Velocity:===
*Defines maximum velocities with standard energy settings on x (left/right), y (up/down), and z (forward) -axis (respectively). z -axis velocity defines the maximum forward velocity.
*The x and y velocities are considered slide veocities
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively, meters per second
**Example: ''0.0, 0.0, 80.0''

===$Player Minimum Velocity:===
{{Table38|
*Defines minimum velocities on x (left/right), y (up/down), and z (forward) -axis (respectively). This affects the player only, the AI ignores the value.
*The x and y velocities are considered slide velocities, the minimums for them are '''not currently implemented'''.
*When gliding, if the absolute speed vector of the players ship falls below the minimum then the ships engines will re-engage and cannot be switched off again until the ships absolute vector exceeds the z-minimum.
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively, meters per second
**Example: ''0.0, 0.0, 40.0''
}}

===$Rotation Time:===
*Defines rotation times around the x, y, and z-axis. Number is seconds it takes to complete rotate a ship (360 degrees) around the given axis. X-axis is "pitch," y-axis is "yaw," and z-axis is "roll."
*Syntax: '''''Vector''''', three '''floats''', seconds per 360 degree turn around x-axis, y-axis, z-axis, respectively
**Example: ''3.0, 2.6, 5.0''
**Note: Setting to Zero will cause the model to disappear in mission.

===$Rear Velocity:===
*Defines rear velocity
*Syntax: '''''Float''''', meters per second
**Note: This value must be set for [[Ships.tbl#.2BAburn_Max_Reverse_Vel:|+Aburn_Max_Reverse_Vel:]] to work

===$Forward Accel:===
*Number of seconds needed from full stop to 63.21% of the maximum forward (z) velocity
** We use 63.21% instead of 100% because FSO's acceleration/velocity model is based on a simplistic exponential function, rather than the more complex models seen for prop-driven, jet-driven, or rocket-driven craft.
** The equation is a derivative of v = 1 - e^(-t / T), where T is what we define in the ship.tbl
*Syntax: '''''Float''''', seconds

===$Forward Decel:===
*Number of seconds needed from maximum forward (z) velocity to full stop
*Syntax: '''''Float''''', seconds

===$Slide Accel:===
*Number of seconds needed from full stop to 63.21% maximum slide velocity
*Note: this is applied to both slide (x and y) axes
**See [[Ships.tbl#$Forward Accel:|$Forward Accel]] for an explanation of the 63.21%
*Syntax: '''''Float''''', seconds

===$Slide Decel:===
*Number of seconds needed from 63.21% maximum slide velocity to full stop
*Note: this is applied to both slide (x and y) axes
**See [[Ships.tbl#$Forward Accel:|$Forward Accel]] for an explanation of the 63.21%
*Syntax: '''''Float''''', seconds

===$Glide:===
{{Table3610|
*Allows gliding in game, i.e. turning the ship's attitude/facing without changing its current movement direction and speed.
*Syntax: '''''Boolean''''', yes or no}}

====+Dynamic Glide Cap:====
{{Table3611|
*If set, game uses dynamic glide cap. The dynamic glide cap means that the maximum glide speed will follow the same rules as normal flight, including the effects of afterburner and power to engines. If set to YES, the value in +Max Glide Speed is ignored.
*Syntax: '''''Boolean'''''}}

====+Max Glide Speed:====
{{Table3610|
*Defines the maximum glide speed if glide has been enabled. If 0, this is set to the fastest speed the ship can go. If negative, there is no glide cap (allowing practically infinite maximum gliding speed). Defaults to 0.
*Syntax: '''''Float'''''}}

====+Glide Accel Mult:====
{{Table3611|
*Defines the acceleration multiplier for the gliding mode. If > 0, sets a fixed acceleration rate in glide mode depending on value. If set to 0, impossible to accelerate while in glide mode. If negative, enables glide speed ramping (acceleration in glide mode ramps in the same way as in normal flight). Defaults to 0.
*Syntax: '''''Float'''''}}
{{Table3610|
*Entry exists as a dummy entry which doesnt do anything to prevent compatibility issues}}

===$Use Newtonian Dampening:===
{{Table3611|
*If set, forces the ship to use (or not use) newtonian dampening. Basically, allows overriding the AI Profiles flag on a per-ship basis.
*Syntax: '''''Boolean'''''}}

===$Autoaim FOV:===
{{Table3610|
*Defines the field of view for autoaim
*Syntax: '''''Integer'''''}}

====+Converging Autoaim====
{{Table3611|
*Defines that the autoaim uses convergence}}

====+Minimum Distance:====
{{Table3611|
*Defines the minimum distance for the convergence}}

===$Convergence:===
{{Table3611|
*Defines the weapons use convergence
{{Note|If none of the following optional strings are added, the weapon will not converge. Don't forget to use them.}}
}}

====+Automatic====
{{Table3611|
*Defines that the ship uses automatic convergence - converging distance calculated from estimated hit position (lead) of the current target.
*'''+Minimum Distance:'''
**Defines the minimum distance for the convergence. Overrides the setting for $Autoaim FOV's minimum distance.}}

====+Standard====
{{Table3611|
*Defines that ship uses fixed convergence.
*'''+Distance:'''
**Defines the converging distance from the ship}}

====+Offset:====
{{Table3611|
*Defines the offset from the ship centerpoint for the convergence
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively}}

===$Warpin Type:===
{{Table3610|
*Allow an animation to be defined as a warpin effect.
*Can be defined as:
:*''Default''
:*''BTRL'' or ''Galactica''
:*''Homeworld''
:*''Hyperspace''}}
{{Table3613|
:*''Knossos''
:*''Babylon5''}}
{{Table3611|
::*''BTRL'' was replaced with ''Galactica'' after 3.6.10}}
{{Table3610|
*Syntax: '''''String'''''}}

===$Warpin Start Sound:===
{{Table3610|
*File for playing at start of warp in effect
*Syntax: '''''String''''', filename}}

===$Warpin End Sound:===
{{Table3610|
*File for playing at end of warp in effect
*Syntax: '''''String''''', filename}}

===$Warpin Speed:===
{{Table3610|
*Sets the speed at which the ship warps in for '''default''' warpin effect
*Sets the time that the ships warp in (not the animation itself) takes for '''BTRL''' type warpin effects
*Syntax: '''''Float''''', meters per second or miiliseconds}}

===$Warpin Time:===
{{Table3610|
*Defines the effect duration
*Syntax: '''''Float''''', seconds}}

===$Warpin Decel Exp:===
{{Table3613|
*Only for the '''hyperspace''' warpin effect.
*Defines an exponent for the deceleration curve at the end of the warpin. Must be higher than 0; a value of 1 produces a constant velocity throughout the effect and higher values produce gradual deceleration.
*Syntax: '''''Float'''''
**Default: 1.0}}

===$Warpin Radius:===
{{Table3610|
*Defines the effect radius
*Syntax: '''''Float''''', meters}}

===$Warpin Animation:===
{{Table3610|
*Defines the animation used for the Homeworld warpin effect. Has no effect for other warpin types.
*Syntax: '''''String''''', filename}}

===$Warpout Type:===
{{Table3610|
*Allow an animation to be defined as a warpout effect.
*Can be defined as:
:*''Default''
:*''BTRL'' or ''Galactica''
:*''Homeworld''
:*''Hyperspace''}}
{{Table3613|
:*''Knossos''
:*''Babylon5''}}
{{Table3611|
::*''BTRL'' was replaced with ''Galactica'' after 3.6.10}}
{{Table3610|
*Syntax: '''''String'''''}}

===$Warpout Start Sound:===
{{Table3610|
*File for playing at start of warp out effect
*Syntax: '''''String''''', filename}}

===$Warpout End Sound:===
{{Table3610|
*File for playing at end of warp out effect
*Syntax: '''''String''''', filename}}

===$Warpout Engage Time:===
{{Table3615|
*Defines the delay the it takes for the warp drive of the ship to engage, during which the player may still abort the warpout. Affects both the player as well as AI ships. If not defined, [[Game_settings.tbl#.24Minimum player warpout time:|defaults to]] 3 seconds for the player and none for the AI.
*Syntax: '''''Float''''', seconds}}

===$Warpout Speed:===
{{Table3610|
*Sets the speed at which the ship warps out for '''default''' warpout effect
*Sets the time that the ships warp out (not the animation itself) takes for '''BTRL''' type warpout effects}}
{{Table3613|
*Sets the minimum speed required for the ship to warp out for '''hyperspace''' type warpout effects}}
{{Table3610|
*Syntax: '''''Float''''', meters per second or milliseconds}}

===$Warpout Time:===
{{Table3610|
*Defines the effect duration
*Syntax: '''''Float''''', seconds}}

===$Warpout Accel Exp:===
{{Table3613|
*Only for the '''hyperspace''' warpin effect.
*Defines an exponent for the acceleration curve at the start of the warpout. Must be higher than 0; a value of 1 produces a constant velocity throughout the effect and higher values produce gradual acceleration.
*Syntax: '''''Float'''''
**Default: 1.0}}

===$Warpout Radius:===
{{Table3610|
*Defines the effect radius
*Syntax: '''''Float''''', meters}}

===$Warpout Animation:===
{{Table3610|
*Defines the animation used as the warpout effect.
*Syntax: '''''String''''', filename}}

===$Player Warpout Speed:===
{{Table3610|
*Sets the speed at which the player warps out from the game
*Syntax: '''''Float'''''}}

===$Expl Inner Rad:===
*Radius at which the full explosion damage is done
*Syntax: '''''Float''''', meters

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

===$Expl Damage:===
*Amount of damage done inside the inner radius
*Syntax: '''''Float''''', damage

===$Expl Blast:===
*The intensity of the blast effect when you're within the outer radius
*Syntax: '''''Float''''', blast effect

===$Expl Propagates:===
*This decides whether the ship explodes into debris immediately, or whether it has the many small explosions before breaking apart slowly
*Syntax: '''''Boolean''''', yes or no

===$Propagating Expl Radius Multiplier:===
{{Table3613|
*This sets the multiplier for the ship splitting propagating explosions
*Syntax: '''''Float''''', defaults to 1}}

===$Expl Visual Rad:===
{{Table3611|
*This determines the visual size of the main fireball for an exploding ship. Does not affect ships with propagating explosions.
*Syntax: '''''Float''''', meters}}

===$Base Death-Roll Time:===
{{Table3613|
*Defines the base death-roll time
*Values is modified depending on conditions when the ship died
*Syntax: '''''Integer''''', milliseconds
**Default: 3000}}

===$Death-Roll Explosion Radius Mult:===
{{Table3613|
*Defines the multiplier for the radius of the ship surface explosions during death roll
*Syntax: '''''Float'''''
**Default: 1}}

===$Death-Roll Explosion Intensity Mult:===
{{Table3613|
*Defines the multiplier for the amount of the ship surface explosions during death roll
*Syntax: '''''Float'''''
**Default: 1}}

===$Death FX Explosion Radius Mult:===
{{Table3613|
*Defines the multiplier applied to the ship death explosions
*Syntax: '''''Float'''''
**Default: 1}}

===$Death FX Explosion Count:===
{{Table3613|
*Defines the number of explosion effect game uses when a large ship dies
*Syntax: '''''Integer'''''
**Default: 6}}

===$Death Roll X rotation Cap:===
{{Table382|
*Defines the cap (aka maximum) on X-axis (pitch) rotation during the ships deathroll. The value is radians per second. The current hard-coded minimum is 0.8. Note the code generally won't use this value for ships with radius > 150 (hard-coded).
*Syntax: '''''Float'''''
**Default: 4.725}}

===$Death Roll Y rotation Cap:===
{{Table382|
*Defines the cap (aka maximum) on Y-axis (yaw) rotation during the ships deathroll. For other details see $Death Roll X rotation Cap:
*Syntax: '''''Float'''''
**Default: 4.725}}

===$Death Roll Z rotation Cap:===
{{Table382|
*Defines the cap (aka maximum) on Z-axis (roll) rotation during the ships deathroll. For other details see $Death Roll X rotation Cap:
*Syntax: '''''Float'''''
**Default: 4.725}}

===$Ship Splitting Particles:===
See [[Ship.tbl#$Impact Spew:|Impact Spew entry]]
*Controls the particles released on every explosion event which happens when ship is splitting apart
*The old 'popcorn' effect
{{Table3613|
*'''+Max Particles:'''
**Default Value: 80
*'''+Min Particles:'''
**Default Value: 40
*'''+Max Radius:'''
**Default Value: Ship radius * 0.015
*'''+Min Radius:'''
**Default Value: Ship radius * 0.005
*'''+Max Lifetime:'''
**Default Value: 6.0 * (1 + 0.002 * Ship radius)
*'''+Min Lifetime:'''
**Default Value: 0.5 * (1 + 0.002 * Ship radius)
*'''+Max Velocity:'''
**Default Value: Speed of the propagating explosion
*'''+Min Velocity:'''
**Default Value: 0.0
*'''+Normal Variance:'''
**Default Value: 2.0}}

===$Ship Death Effect:===
{{Table38|
*Specifies the [[Particle Effects|particle effect]] which will be used the final explosion of this ship type,
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Ship Death Particles'' is not a valid option!
}}

===$Ship Death Particles:===
See [[Ship.tbl#$Impact Spew:|Impact Spew entry]]
*Controls the particles released on the moment 'non-knossos' type object dies
{{Table3613|
*'''+Max Particles:'''
**Default Value: 100
*'''+Min Particles:'''
**Default Value: 50
*'''+Max Radius:'''
**Default Value: 1.5
*'''+Min Radius:'''
**Default Value: 0.1
*'''+Max Lifetime:'''
**Default Value: 4.0
*'''+Min Lifetime:'''
**Default Value: 0.5
*'''+Max Velocity:'''
**Default Value: 20.0
*'''+Min Velocity:'''
**Default Value: 0.0
*'''+Normal Variance:'''
**Default Value: 2.0}}

===$Alternate Death Particles:===
See [[Ship.tbl#$Impact Spew:|Impact Spew entry]]
*Controls the particles released when 'knossos' type object is dying
{{Table3613|
*'''+Max Particles:'''
**Default Value: 30
*'''+Min Particles:'''
**Default Value: 15
*'''+Max Radius:'''
**Default Value: 100.0
*'''+Min Radius:'''
**Default Value: 30.0
*'''+Max Lifetime:'''
**Default Value: 12.0
*'''+Min Lifetime:'''
**Default Value: 2.0
*'''+Max Velocity:'''
**Default Value: 350.0
*'''+Min Velocity:'''
**Default Value: 50.0
*'''+Normal Variance:'''
**Default Value: 2.0}}

===$Vaporize Percent Chance:===
{{Table3611|
*Allows ships to sometimes explode instantly (vaporize) instead of going through a death roll first. Overrides the same flag in [[objecttypes.tbl]].
*Syntax: '''''Float''''', percent chance of vaporization, 0 to 100}}

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

===$Shockwave Speed:===
*Speed shockwave expands at, 0 means no shockwave
*Syntax: '''''Float''''', meters per second

===$Shockwave Count:===
*Defines the number of shockwaves to spawned
*Syntax: '''''Integer'''''

===$Shockwave Model:===
{{Table3610|
*Defines the textured model used as the ship's 3D shockwave
*Syntax: '''''String.pof''''', model filename}}

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

===$Explosion Animations:===
{{Table3610|
*Defines the explosion animations used for the ship
*Syntax: '''''Integer list'''''}}

===$Weapon Model Draw Distance:===
{{Table3610|
*Distance that external weapons are shown, ie. missiles and such.
*Syntax: '''''Float''''', meters
**Default: ''200''}}

===Primary Weapons===
====$Allowed PBanks:====
*List of allowed primary weapons in brackets (weapon name marked with quotes).
*Syntax: '''''( "String" "String" )''''', names of the weapons
{{Table3610|
*Each of the primary weapon banks '''can optionally''' be given their own list of allowed weapons, in which case each bank has its own bracketed entry.
*Syntax: '''''( "String" "String" ) ( "String" "String" )'''''}}

====$Allowed Dogfight PBanks:====
*Primary weapons for multiplayer dogfights.
*Syntax: '''''( "String" "String" )''''', names of the weapons
{{Table3610|
*Each of the primary weapon dogfight banks '''can optionally''' be given their own list of allowed weapons, in which case each bank has it's own bracketed entry.
*Syntax: '''''( "String" "String" ) ( "String" "String" )'''''}}

====$Default PBanks:====
*Defines default primary weapons for each of the primary weapon banks
*Syntax: '''''( "String" "String" )''''', names of the weapons

====$PBank Capacity:====
{{Table3610|
*Defines ammunition capacity of primary weapon banks. In brackets, different weapon banks separated by commas.
*NOTE: In order for this to work, at least one of the primary weapons in the list of default primaries must be a ballistic weapon.
*Syntax: '''''( Integer, Integer )'''''}}

====$Show Primary Models:====
{{Table3610|
*Defines the use of weapon models for primary weapons. In brackets, different weapon banks may have different definitions
*Syntax: '''''( Boolean Boolean )''''', yes or no
**Example: ''( YES YES )'' - Note the spaces on the insides of the brackets.}}

===Secondary Weapons===
====$Allowed SBanks:====
*Same for secondary weapons.
*Syntax: '''''( "String" "String" )''''', names of the weapons
{{Table3610|
*Each of the secondary weapon banks can be given their own list of allowed weapons, in which case each bank has it's own bracketed entry.
*Syntax: '''''( "String" "String" ) ( "String" "String" )'''''}}

====$Allowed Dogfight SBanks:====
*Same for secondary weapons.
*Syntax: '''''( "String" "String" )''''', names of the weapons
{{Table3610|
*Each of the secondary weapon dogfight banks can be given their own list of allowed weapons, in which case each bank has it's own bracketed entry.
*Syntax: '''''( "String" "String" ) ( "String" "String" )'''''}}

====$Default SBanks:====
*Defines default primary weapons for each of the primary weapon banks
*Syntax: '''''( "String" "String" )''''', names of the weapons

====$SBank Capacity:====
*Defines ammunition capacity of secondary weapon banks. In brackets, different weapon banks separated by commas.
*Syntax: '''''( Integer, Integer )'''''

====$Show Secondary Models:====
{{Table3610|
*Defines the use of weapon models for secondary weapons. In brackets, different weapon banks may have different definitions
*Syntax: '''''( Boolean Boolean )'''''
**Example: ''(YES YES)''}}

===$Ship Recoil Modifier:===
{{Table373|
*Multiplies the recoil force of a weapon by this value, use a value greater than 1.0 to increase the force, use a value between 1.0 and 0.0 to decrease.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|It is not required to have any weapons with the "apply recoil" flag set for this to be enabled.}}
}}

===$Shields:===
*Determines the shield strength
*Syntax: '''''Float''''', total shield strength

====+Auto Spread:====
{{Table371|
*Defines the thickness of auto spread shields. Note that the [[#.22auto_spread_shields.22|"auto spread shields"]] ship flag is also needed.
*Syntax: '''''Float''''', shield thickness in meters.}}

====+Minimum Weapon Span:====
{{Table373|
*Determines the minimum distance weapons must have traveled before impacting the shield (for example if fired close to or inside the shield). Does not affect whether the weapon bypasses shields, unless +Allow Bypass (see below) is set to ''YES''. Only valid with auto spread shields.
*Syntax: '''''Float''''', defaults to the shield thickness.}}

====+Allow Bypass:====
{{Table371|
*Determines whether weapons which impact on the ship's hull (see +Minimum Weapon Span above) will bypass shields. Only valid with auto spread shields.
*Syntax: '''''Boolean'''''
**Default: ''NO''}}

====+Spread From LOD:====
{{Table371|
*Causes the auto spread shields calculations to be done based off a LOD level other than LOD0. Using a lower-poly LOD will considerably speed up the shield collision detection, while being visually indistinguishable in most cases.
*Syntax: '''''Integer''''', defaults to 0}}

===$Model Point Shield Controls:===
{{Table371|
*Allows remapping of the 4 shield augmentation keys when [[Model Point Shields]] are used. You should usually supply as many values as you have shield segments. The first value determines which augmentation key to use for the first shield segment, the second value determines which key to use for the second shield segment, and so on (the order being defined by the order of the shield points in the model file). If less than 4 values are given, "none" is assumed for the missing ones. Note that as there are only 4 augmentation keys, player ships with more than 4 shield segments would generally not be a good idea.
*Syntax: '''''( String list )''''', possible values "front", "left", "right", "rear" and "none"
**Example: ''( "front" "rear" )'' for a ship with only two shield sections, front and rear; the left and right augmentation keys would be disabled.
**Example: ''( "left" "rear" "right" )'' for a ship with only three shield sections, left, right and rear; the front augmentation key would be disabled.
**Example: ''( "front" "right" "rear" "left" )'' for a ship with four shield sections but perhaps positioned in a non-standard way.}}

===$Shield Color:===
*RGB value for shield color
*Syntax: '''''Color''''', red, green, blue respectively, value from 0 to 255
**Example: ''100, 100, 255''

===$Shield Impact Explosion:===
{{Table373|
*Impact explosion animation to trigger when this ship's shields are hit. Works identically for all shield types.
*Note: The size of the explosion is defined by the weapon, see [[Weapons.tbl#.24Shield_Impact_Explosion_Radius:]].
*Syntax: '''''String''''', filename or ''none''
}}

===$Max Shield Recharge:===
{{Table373|
*Determines a maximum recharge limit of shields. When used, the combined maximum shield energy is lowered, meaning that shield energy can be moved between quadrants even with shields fully charged.
*Syntax: '''''Float''''', multiplier ranging from 0.0 to 1.0, defaults to 1.0
**Example: ''$Max Shield Recharge: 0.5'' caps the combined shield energy to 50%, meaning that a ship with 4 shield quadrants will by default have 12.5% strength on all quadrants (instead of normal 25%), allowing it to for example augment one quadrant to 50% while dropping other quadrants to 0%.
}}

===$Power Output:===
*Actually does *NOTHING* unless set to zero; in which case weapon/shield/burner energy regeneration is disabled. Checked via code inspection 2014/12/29
*Syntax: '''''Float'''''

===$Shield Regeneration Rate:===
{{Table3610|
*Repair rates for shields at percent per second
*Syntax: '''''Float''''', multiplier of total shield hitpoints recharged each second. ('''NOT A PERCENTAGE''', 0.02 equals 2% recharged per second)
**Default: ''0.02''
*Affected by ETS Shields value (1/3rd value recharged per sec at default ETS setting of '4')
*Affected by AI Profile Setting: $Player Shield Recharge Scale:}}

===$Support Shield Repair Rate:===
{{Table3611|
*Shield repair rate when docked to a support ship
*Syntax: '''''Float'''''}}

===$Weapon Regeneration Rate:===
{{Table3610|
*Regeneration rates for primary guns at percent per second
*Syntax: '''''Float''''', multiplier of total gun energy recharged each second ('''NOT A PERCENTAGE''', 0.04 equals 4% recharged per second)
**Default: ''0.04''
*Affected by ETS Guns value (1/3rd value recharged per sec at default ETS setting of '4')
*Affected by AI Profile Setting: $Player Weapon Recharge Scale:}}

===$Max Oclk Speed:===
*Can also be '''$Max Overclock Speed:'''
*Maximum velocity with all energy diverted to engines
*Syntax: '''''Float''''', meters per second

===$Max Weapon Eng:===
*Can also be '''$Max Weapon Energy:'''
*The maximum amount of energy you can store in your primary weapons bank.
*Syntax: '''''Float'''''

===$Hitpoints:===
*How much damage the ship can take
*Syntax: '''''Float''''', hitpoints
**Default: ''100''

===$Hull Repair Rate:===
{{Table3610|
*Repair rates for hull at percent per second
*Syntax: '''''Float''''', multiplier of hitpoints repaired per second, '''NOT A PERCENTAGE''', 0.01 equals 1% recharged per second}}

===$Support Hull Repair Rate:===
{{Table3611|
*Repair rate for hull when docked to a support ship
*Syntax: '''''Float'''''}}

===$Subsystem Repair Rate:===
{{Table3610|
*Repair rates for sybsystems percent per second
*Syntax: ''Value'', percentage of total subsystem hitpoints repaired per second}}

===$Support Subsystem Repair Rate:===
{{Table3611|
*Repair rate for subsystems when docked to a support ship
*Syntax: '''''Float'''''}}

===$Armor Type:===
{{Table3610|
*'''REQUIRES ADDITIONAL TABLE'''. Defines armor type used for the ship
*Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]}}

===$Shield Armor Type:===
{{Table3611|
*'''REQUIRES ADDITIONAL TABLE'''. Defines the armor type used for shield of the ship
*Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]}}

===$Flags:===
*See [[Ships.tbl#Ships.tbl_flags|below]]
*Syntax: '''''( "String" "String" )''''', names of the flags assigned to the ship
**Example: ( "fighter" "in tech database" )
{{Table3610|
*'''+noreplace'''
**Can be used to force game to retain existing flags instead of reseting the ship flags before parsing in the new flags.}}

===$AI Class:===
*Default AI class
*Syntax: '''''String''''', name of the AI class as defined in [[ai.tbl]]

===$Afterburner:===
*Defines if the ships has afterburner
*Syntax: '''''Boolean''''', yes or no
====+Aburn Max Vel:====
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively, meters per second
====+Aburn For accel:====
*Defined only for the forward acceleration. In same format as [[Ships.tbl#$Forward Accel:|$Forward Accel]]
*Syntax: '''''Float''''', seconds

====+Aburn Max Reverse Vel:====
{{Table3611|
*Defined only for the reverse acceleration, Sets the top speed for Reverse Afterburner.
*Syntax: '''''Float''''', seconds
**NOTE: Requires [[Ships.tbl#.24Rear_Velocity:|$Rear Velocity:]] to be set in order to work.
}}
====+Aburn Rev accel:====
{{Table3611|
*Defined only for the reverse acceleration. In same format as [[Ships.tbl#$Forward Accel:|$Forward Accel]]

*Syntax: '''''Float''''', seconds'''''}}

====+Aburn Fuel:====
*Amount of afterburner fuel the ship has
*Syntax: '''''Float''''', fuel
====+Aburn Burn Rate:====
*Rate the fuel is consumed when afterburner is engaged (in units per seconds)
*Syntax: '''''Float''''', fuel units per second
====+Aburn Rec Rate:====
*Rate the fuel is restored.
*Syntax: '''''Float''''', fuel units per second
{{Table3610|
====$Trails:====
*Allows afterburner trails to be used
=====+Bitmap:=====
*Texture used to draw the afterburner trail
*Syntax: '''''String''''', filename
=====+Width:=====
*Width of afterburner trail at the beginning of it (ie. the thruster end)
*Syntax: '''''Float''''', meters
=====+Alpha:=====
*Transparancy of the trail, value from 1 (non-transparent) to 0 (totally transparent)
*Syntax: '''''Float'''''
=====+Life:=====
*How long the trail will last
*Syntax: '''''Float''''', seconds}}
{{Table3611|
=====+Faded Out Sections:=====
*Defines the number of the trail sections from the leading edge that are gradually faded away.
*Syntax: '''''Integer'''''}}

===$Countermeasure Type:===
{{Table3610|
*Defines the weapon used as a countermeasure. Weapon does not have to be included in the countermeasure section of the weapons.tbl, but it has to have "countermeasure" flag in that case.
*Syntax: '''''String''''', name of the weapon as defined in [[weapons.tbl]]}}

===$Countermeasures:===
*Number of countermeasures that can be loaded to the ship
*Syntax: '''''Integer'''''

===$Scan Time:===
*Time it takes to scan the ship
*Syntax: '''''Integer''''', milliseconds

===$Scan range Normal:===
{{Table381|
*Distance at which the ship can scan other small ships or large ship subsystems
*Syntax: '''''Float''''', distance
}}

===$Scan range Capital:===
{{Table381|
*Distance at which the ship can scan capital (& similar size) ships
*Syntax: '''''Float''''', distance
}}

===$Ask Help Shield Percent:===
{{Table381|
*Percentage of shield damage at which the ship will send a call for assistance message.
*Syntax: '''''Float''''', percentage. Valid range 0.0-1.0
}}

===$Ask Help Hull Percent:===
{{Table381|
*Percentage of hull damage at which the ship will send a call for assistance message.
*Syntax: '''''Float''''', percentage. Valid range 0.0-1.0
}}

===$EngineSnd:===
*Engine sound used for the ship with number referring to sounds.tbl
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]

===$Minimum Engine Volume:===
{{Table373|
*Specifies how to multiply the volume of the engine sound based on ship speed. When the ship is stationary, the engine volume will be multiplied by the given value, with the value approaching 1.0 as the ship speed approaches maximum.
*Note: Default behavior is to ramp the multiplier from 0.5 (when ship is stationary) to 1.0 (when ship is at half speed or more).
*Syntax: '''''Float''''', volume multiplier, usually you'll want a value between 0.0 and 1.0
}}

===$GlideStartSnd:===
{{Table3613|
*Optional sound to be used when entering glide mode, instead of the default throttle down sound.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$GlideEndSnd:===
{{Table3613|
*Optional sound to be used when exiting glide mode, instead of the default throttle up sound.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$CockpitEngineSnd===
{{Table3613|
*Optional sound to be used for looping engine sound heard in the cockpit.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$FullThrottleSnd===
{{Table3613|
*Optional sound to be used for the sound heard when setting throttle to full power.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$ZeroThrottleSnd===
{{Table3613|
*Optional sound to be used for the sound heard when setting throttle to zero power
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$ThrottleUpSnd===
{{Table3613|
*Optional sound to be used for the sound heard when increasing throttle power by 1/3
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$ThrottleDownSnd===
{{Table3613|
*Optional sound to be used for the sound heard when decreasing throttle power by 1/3
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AfterburnerSnd===
{{Table3613|
*Optional optional sound to be used for the looping sound heard when the afterburner is active
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AfterburnerEngageSnd===
{{Table3613|
*Optional optional sound to be used for the sound heard when the afterburner is engaged
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AfterburnerFailedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the activation of the afterburner failed
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$MissileTrackingSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a aspect seeking missile of the player tries to acquire a lock
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$MissileLockedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a aspect seeking missile of the player has acquired a lock
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$PrimaryCycleSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the player cycles his primary weapon
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$SecondaryCycleSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the player cycles his secondary weapon
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$TargetAcquiredSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the player acquires a new target
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$PrimaryFireFailedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the primary weapon fails to fire
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$SecondaryFireFailedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the secondary weapon fails to fire
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$HeatSeekerLaunchWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a heat-seeker is fired at the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AspectSeekerLaunchWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when an aspect-seeker is fired at the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$MissileLockWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when an aspect-seeker is locked onto the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$HeatSeekerProximityWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a heat-seeker is in close proximity to the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$AspectSeekerProximityWarningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when an aspect-seeker is in close proximity to the player
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$MissileEvadedSnd===
{{Table3613|
*Optional sound to be used for the sound heard when a missile has been evaded
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$CargoScanningSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the cargo of an object is being scanned
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$ExplosionSnd===
{{Table3613|
*Optional sound to be used for the sound heard when the ship explodes
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$Flyby Sound===
{{Table382|
*Optional sound to be used for the fly-by sound
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
}}

===$Closeup_Pos:===
*How the model will show at techroom and briefing screen animations (assuming a pre-rendered animation is not specified). The position of the camera relative to the model in the tech room and the target box view. If 3D ship selection is used, also affects the drawing of the ship icon in the weapon & ship selection briefing screens.
*Syntax: '''''Vector''''', three '''floats''', x, y and z values respectively

===$Closeup_Zoom:===
*How the model will show at techroom and briefing screen animations (assuming a pre-rendered animation is not specified). How far the camera's zoomed in, defines camera's FOV. If 3D ship selection is used, also affects the drawing of the ship icon in the weapon & ship selection briefing screens.
*Syntax: '''''Float''''', radians

===$Topdown Offset:===
{{Table3610|
*Specifies how high the camera is above the center point of a ship in topdown camera views, or 2D missions.
*Syntax: '''''Float''''', meters}}

===$Shield_Icon:===
*This .ani file must be at data/hud and included to the hud.tbl.
{{Table3610|
*Reference to the hud.tbl is no longer needed.}}
**Syntax: ''Filename''

===$Model Icon Direction:===
{{Table373|
*The direction from which the ship should be drawn from, if $Ship_Icon is not used and the ship icon is generated from the model.
** By default, the direction is based on whether the game thinks the ship is a small ship, a capship or an installation.
**Syntax: ''String'', one of "top", "bottom", "front", "back", "left" or "right"}}

===$Ship_Icon:===
*The icon used in ship selection.
{{Table3610|
*Ship model is used by default to generate the image.}}
**Syntax: ''Filename''

===$Ship_Anim:===
*The glowing green grid animation used in ship selection.
{{Table3610|
*Ship model is used by default to generate the image.}}
**Syntax: '''''String''''', filename

===$Ship_Overhead:===
*The overhead view used in the weapons loadout.
{{Table3610|
*Ship model is used by default to generate the image.}}
**Syntax: '''''String''''', filename

{{Table371|
===$Briefing icon:===
*Defines if the ship has its own briefing icon information which overrides the standard briefing icon image
====+Regular:====
*Syntax: '''''<regular anim filename>'''''
====+Fade:====
*Syntax: '''''<fade anim filename>'''''
====+Highlight:====
*Syntax: '''''<highlight anim filename>'''''}}

{{Table371|
===$Briefing icon with cargo:===
*Defines if the ship has its own cargo briefing icon (which will only be an option if a ship icon is also specified)
====+Regular:====
*Syntax: '''''<regular anim filename>'''''
====+Fade:====
*Syntax: '''''<fade anim filename>'''''
====+Highlight:====
*Syntax: '''''<highlight anim filename>'''''}}

{{Table371|
===$Briefing wing icon:===
*Defines if the ship has its own wing briefing icon (which will only be an option if a ship icon is also specified)
====+Regular:====
*Syntax: '''''<regular anim filename>'''''
====+Fade:====
*Syntax: '''''<fade anim filename>'''''
====+Highlight:====
*Syntax: '''''<highlight anim filename>'''''}}

{{Table371|
===$Briefing wing icon with cargo:===
*Defines if the ship has its own wing-with-cargo briefing icon (which will only be an option if a ship icon is also specified)
====+Regular:====
*Syntax: '''''<regular anim filename>'''''
====+Fade:====
*Syntax: '''''<fade anim filename>'''''
====+Highlight:====
*Syntax: '''''<highlight anim filename>'''''}}

===$Score:===
*Points awarded for destroying the ship
*Syntax: '''''Float'''''

===Customized Thruster Effects===
{{Table3611|
*Defines the texture of the modeled thruster effect cone
*'''$Thruster Normal Flame:'''
**Syntax: '''''String''''', filename
*Defines the texture of the modeled thruster effect cone with afterburners lit
*'''$Thruster Afterburner Flame:'''
**Syntax: '''''String''''', filename}}
{{Table3610|
*'''Defines the primary thruster glow - the one visible only from behind'''
**'''$Thruster Bitmap 1:'''
***Defines the effect for the standard drives. Overrides [[Species_defs.tbl]] line '''+Normal:''' under the '''$Thrustglows:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Bitmap 1a:'''
***Defines the effect for the afterburner. Overrides [[Species_defs.tbl]] line '''+Afterburner:''' under the '''$Thrustglows:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster01 Radius factor:'''
***Defines the radius multiplier
***Syntax: '''''Float'''''
*'''Defines the secondary glow type-effect for thrusters - the feathery trail like haze behind the main glow'''
**'''$Thruster Bitmap 2:'''
***Defines the effect for the standard drives. Overrides [[Species_defs.tbl]] line '''+Sec_Normal:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Bitmap 2a:'''
***Defines the effect for the afterburner. Overrides [[Species_defs.tbl]] line '''+Sec_Afterburn:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster02 Radius factor:'''
***Defines the radius multiplier
***Syntax: '''''Float'''''
**'''$Thruster02 Length factor:'''
***Defines the length multiplier for the trail type (secondary) glowpoint thrusters
***Replaces the older '''$Thruster01 Length factor:'''
***Syntax: '''''Float'''''
*'''Defines the tertiary glow type-effect for thrusters - the one visible from all directions'''
**NOTE: The rotation of this effect is jittered, which can look quite bad with certain types of effects.
**'''$Thruster Bitmap 3:'''
***Defines the effect for the standard drives. Overrides [[Species_defs.tbl]] line '''+Ter_Normal:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Bitmap 3a:'''
***Defines the effect for the afterburner. Overrides [[Species_defs.tbl]] line '''+Ter_Afterburn:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster03 Radius factor:'''
***Defines the radius multiplier
***Syntax: '''''Float'''''}}
{{Table3613|
*'''Defines the distortion effect for thrusters'''
**'''$Thruster Bitmap Distortion:'''
***Defines name of normal thruster distortion envelope animation. Overrides [[Species_defs.tbl]] line '''+Dist_Normal:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Bitmap Distortion a:'''
***Defines name of afterburner thruster distortion envelope animation. Overrides [[Species_defs.tbl]] line '''+Dist_Afterburn:''' under the '''$ThrustAnims:''' entry.
***Syntax: '''''String''''', filename
**'''$Thruster Distortion Radius factor:'''
***Defines the radius multiplier
***Syntax: '''''Float'''''
**'''$Thruster Distortion Length factor:'''
***Defines the length multiplier for the thruster distortion
***Syntax: '''''Float'''''
**'''$Thruster Distortion:'''
***Defines whether the distortion effect is rendered for this ship.
***Syntax: '''''Bool'''''}}
{{Table373|
*'''$Thruster Glow Noise Mult:'''
**A multiplier for how much noise is applied to the thruster glow radius. A value of 0 causes the radius to remain perfectly steady and values higher than 1 cause the radius to fluctuate more than the default.
** Defaults to 1.0.
**Syntax: '''''Float'''''
}}

===$Thruster Particles:===
{{Table3610|
*Defines the alternative particle thruster
*'''$Thruster Particle Bitmap:''' OR '''$Afterburner Particle Bitmap:'''
**Name of the animation used for particle thrusters, up to '''three''' can be defined for both '''standard''' thrusters and '''afterburners''' (6 in total). Afterburner particles require at least 1 existing particle thruster entry.
**Syntax: '''''String''''', filename
*'''$Min Radius:'''
**Defines the minimum radius of new particles
**Syntax: '''''Float''''', meters
*'''$Max Radius:'''
**Defines the maximum radius of new particles
**Syntax: '''''Float''''', meters
*'''$Min Created:'''
**Defines the minimum amount of particles created
**Syntax: '''''Float'''''
*'''$Max Created:'''
**Defines the maximum amount of particles created
**Syntax: '''''Float'''''
*'''$Variance:'''
**Value that describes the randomness of particle generation, values close to 0 will cause particles to spew very close to the thrusters normal while values close 1 will cause some particles to be spewed even to opposite direction
**Syntax: '''''Float'''''}}

===$Stealth:===
*Defines: Ship behaves as a stealth-ship: non-targettable, and not on radar.
{{Table3610|
This field is [[deprecated]], and mods using 3.6.8 and above should use the "stealth" flag.}}

===$Max Decals:===
{{Table3610|
*Defines: Maximum number of weapon decals on a ship
*Syntax: '''''Integer''''', maximum number of decals on ship
**Default: 50 for anything below cruiser size, 100 for anything below superdestroyer/installation size, 300 for anything above destroyer size, 10 for everything else.}}
{{Table3613|
*Feature disabled. Parsing retained to maintain compatibility}}

===$Trail:===
*These are the origins of the white contrails that appear in the nebula missions. Ship may have multiple trails.
{{Table3611|
*'''+ClearAll'''
**Clears all existing trail data from the ship}}
====+Offset:====
*The position of the contrail's head
*Syntax: '''''Vector''''', three '''floats''', x, y and z values respectively, relative to the center point of the model
====+Start Width:====
*The width of the contrail's head
*Syntax: '''''Float''''', meters
====+End Width:====
*The width of the contrail's tail
*Syntax: '''''Float''''', meters
====+Start Alpha:====
*The opacity of the contrail's head
*Syntax: '''''Float''''', value between 0 and 1
====+End Alpha:====
*The opacity of the contrail's tail
*Syntax: '''''Float''''', value between 0 and 1
====+Max Life:====
*How long the contrail remains
*Syntax: '''''Float'''''', seconds
====+Spew Time:====
*Syntax: '''''Integer'''''
====+Bitmap:====
*The image to use for the contrail.
*Syntax: '''''String''''', filename
{{Table3611|
====+Faded Out Sections:====
*Defines the number of the trail sections from the leading edge that are gradually faded away.}}

===$Thruster:===
{{Table3610|
*Defines maneuvering thrusters. Ship may have multiple $Thrusters defined.
*'''+Index:'''
**Defines the index number of the manoeuvring thruster defined in this entry
**Syntax: '''''Integer'''''
*'''+Used For:'''
**Defines the maneuver that triggers the maneuvering thruster
**List of maneuvers: Bank right, Bank left, Pitch up, Pitch down, Roll right, Roll left, Slide right, Slide left, Slide up, Slide down, Forward, Reverse
**Syntax: '''''("String" "String")'''''
*'''+Position:'''
**Defines thruster location
**Syntax: ( '''''Float''''' '''''Float''''' '''''Float''''' ), position from the ships center point, x, y, z axis respectively
*'''+Normal:'''
**Defines the direction where the thruster points to
**Syntax: ( '''''Float''''' '''''Float''''' '''''Float''''' ), direction of the thrusters normal, x, y, z axis respectively
*'''+Texture:'''
**Defines the graphic that will be used for trail, rendered like beams
**Syntax: '''''String''''', filename
*'''+Radius:'''
**Defines the radius of cylinder
**Syntax: '''''Float''''', meters
*'''+Length:'''
**Defines the length of thruster trail
**Syntax: '''''Float''''', meters
*'''+StartSnd:'''
**Defines the sound played when the thruster is started
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+LoopSnd:'''
**Defines the sound played when the thruster is continuously used
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+StopSnd:'''
**Defines the sound played when the thruster is shutting down
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Radar Image 2D:===
{{Table3611|
*Defines the bitmap used to represent the ship on the radar screen.
*Syntax: '''''Filename'''''}}
{{Table3615|
*'''$Radar Color Image 2D:'''
**Defines the color bitmap used to represent the ship on the radar screen.
**Syntax: '''''Filename'''''}}
{{Table3611|
*'''$Radar Image Size:'''
**Defines the size of the bitmap on the radar screen (length of the longer dimension)
**Syntax: '''''Integer'''''
*'''$3D Radar Blip Size Multiplier:'''
**Defines the multiplier used for blip size on the 3D radar.
**Syntax: '''''Float'''''}}

===$Glowpoint overrides:===
{{Table373|
*Creates a point that casts light onto ships and objects with the source being a glowpoint defined in the model file.
*Syntax: '''''( "String:Integer" )'''''
*String refers to name in [[glowpoints.tbl]]
*Essentially, [Name_of_glowpoint_override_in_glowpoints.tbl]:[Bank_in_POF]. If there is no override entry then the game will not generate a light. If you have multiple banks that use the same override, use a comma if they are not in order (2,4,7) and use a dash if they are in order (3-5 yields 3, 4, and 5).
**Example: '''$Glowpoint overrides: ( "teal_glow_10:1" "red_glow:2,3" "white_glow_10:4" "red_glow_10:5" "green_glow_10:6")'''
}}

===$Ship IFF Colors:===
{{Table3611|
*Defines the alternate color for the ship. Affects both the targeting brackets as well as the radar screen.
*'''+Seen By:'''
**Defines the IFF actually viewing the object (most often 'Friendly')
**Syntax: '''''String''''', name of an IFF class.
*'''+When IFF Is:'''
**Defines the IFF which the ship has to have for its color to be altered.
**Syntax: '''''String''''', name of an IFF class.
*'''+As Color:'''
**Defines the new color of the ship's targeting brackets and radar blip
**Syntax: '''''Integer list''''', red, blue and green respectively}}

===$Target Priority Groups:===
{{Table3611|
*Defines into which target priority groups the ship belongs to
*Syntax: '''''String list''''', names of the targeting groups
*'''+Override'''
**Overrides the ships existing groupings}}

===$EMP Resistance Modifier:===
{{Table3611|
*Defines the ships EMP resistance modifier:
*Syntax: '''''Float'''''}}

===$Piercing Damage Draw Limit:===
{{Table3611|
*Defines the maximum percentage of hitpoints ship has before piercing effects are enabled
*Syntax: '''''Float'''''
**Example: '''10''', sets the limit to 10%}}

===$Path Metadata:===
{{Table3613|
*Allows definition of extra metadata
*Syntax: '''''String''''', name of the path as defined in the ship POF file.
**Example: '''$Path Metadata: $Bay01'''
====+departure rvec:====
When using this path to depart via fighterbay, the departing ship will rotate to align itself with this rvec (so the right side of the ship is pointing in this direction). Only affects paths used to depart via fighterbay.
====+arrive speed multiplier:====
{{Table373|
*Modifies the speed of ships arriving from a fighterbay using this path. See [[Ai_profiles.tbl#.24bay_arrive_speed_multiplier:]] for details.
**Syntax: '''''Float'''''
}}
====+depart speed multiplier:====
{{Table373|
*Modifies the speed of ships departing to a fighterbay using this path. See [[Ai_profiles.tbl#.24bay_depart_speed_multiplier:]] for details.
**Syntax: '''''Float'''''
}}
}}

===$Subsystem<nowiki>:</nowiki>===
:''Main article: [[Subsystem]]''

==Ships.tbl flags==

==="no_collide"===
*Defines ship as non-collideable, ie. everything will go through it

==="player_ship"===
*Makes it possible for the player to fly the ship

==="default_player_ship"===
*Makes this ship as a default part of the loadout options in FRED

----

===Ship Type===
*Flags in this section are used to define the type of the ship
*Use only one '''ship type''' flag per table entry
{{Table3610|
*New ship types can be defined in [[objecttypes.tbl]]}}

===="repair_rearm"====
*Alternate name for "support"

===="support"====
*Defines the ship as repair and rearm vessel and sets AI behaviour accordingly
*Only one such vessel can be defined per species

===="cargo"====
*Defines ship as a cargo crate and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="fighter"====
*Defines ship as a fighter and also sets the AI behaviour
*In FS1/FS2 only ships flagged as fighters or bombers can accept the full set of player orders

===="bomber"====
*Defines ship as a bomber and also sets the AI behaviour
*In FS1/FS2 only ships flagged as fighters or bombers can accept the full set of player orders

===="transport"====
*Defines ship as a transport and also sets the AI behaviour

===="freighter"====
*Defines ship as a freighter and also sets the AI behaviour

===="capital"====
*Defines ship as a capital ship and also sets the AI behaviour

===="supercap"====
*Alternate name for "super cap"

===="super cap"====
*Defines ship as a super capital ship and also sets the AI behaviour

===="drydock"====
*Defines ship as a drydock and also sets the AI behaviour

===="cruiser"====
*Defines ship as a cruiser and also sets the AI behaviour

===="navbuoy"====
*Defines ship as a navbuoy and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="sentrygun"====
*Alternate name for "sentry gun"

===="sentry gun"====
*Defines ship as a sentrygun and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="escapepod"====
*Alternate name for "escape pod"

===="escape pod"====
*Defines ship as a escapepod and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="corvette"====
*Defines ship as a corvette and also sets the AI behaviour

===="gas miner"====
*Defines ship as a gas miner and also sets the AI behaviour

===="awacs"====
*Defines ship as a AWACS and also sets the AI behaviour

===="knossos"====
*Alternate name for the "Knossos device"

===="knossos device"====
*Defines ship as a Knossos and also sets the AI behaviour
*In FS1/FS2 ships that are marked with this flag cannot accept any player orders

===="stealth"====
{{Table3610|
*Defines ship as a stealth-ship: non-targettable, and not on radar.}}

===="no type"====
*Does ???

----

==="ship copy"===
*Defines the ship as a copy of another model

==="in tech database"===
*Includes ships description to the tech database from the beginning of the campaign

==="in tech database multi"===
*Includes the ship to multiplayer tech database

==="dont collide invisible"===
*Defines invisible textures as non-collideable (For example, a hangar entrace)

==="big damage"===
*Limits the damage made to the ship by non-huge weapons.

==="no_fred"===
*Ship will not appear in FRED.

==="ballistic primaries"===
{{Table3610|
*Enables the ship to use ballistic primaries
*No longer needed, game handles it automatically}}

==="flash"===
{{Table3610|
*Makes a flash when a ship dies}}

==="surface shields"===
{{Table3610|
*Shots that impact the hull are applied to shields, regardless of if the ship has a shield mesh.}}

==="show ship"===
{{Table3610|
*Enable rendering the ship even when the ship is a player ship
*Will result in the player's ship model being rendered, when in cockpit mode}}

==="generate icon"===
{{Table3610|
*Creates a HUD icon from the model itself}}

==="gun convergence"===
{{Table3610|
*Enables ship to use the firing points' normals in defining the direction where the weapon fire}}

==="no thruster geometry noise"===
{{Table3611|
*Prevents noise from being added to the thruster effects geometry}}

==="intrinsic no shields"===
{{Table3611|
*Defines that ship has no shields by default, to allow mixing and matching shielded and unshielded craft in loadout}}

==="no primary linking"===
{{Table3611|
*Bypasses linked primaries while cycling. Does not block SEXPs/scripts that might be able to lock them, only the act of cycling for players and determing whether to link or not for AI.}}

==="no pain flash"===
{{Table3613|
*Prevents pain flash from being shown when ship is hit}}

==="dynamic primary linking"===
{{Table37|
*Allows this ship use the primary firepoint cycling code. With a key bind added in 3.6.13, you can toggle between various factorizations of primary firepoint groupings on a per-primary bank basis. So a 4-firepoint bank could cycle through all four firepoints firing together (1x4), each firepoint firing individually (4x1, all 4 firing over the timespan of the bank cooldown, so no change in damage over time, or DPS, occurs from retail behavior), or firing in pairs (2x2).}}

==="no ets"===
{{Table37|
Sets ship class to have no ETS}}

==="no lighting"===
{{Table3613|
Ship will not receive lighting calculations}}

==="auto spread shields"===
{{Table371|
Causes the ship's shield mesh (if any) to be ignored and a shield of a given thickness to be automatically projected around the ship's hull. Weapons will impact the ship's shields at a distance equal to the shield thickness defined in [[Ships.tbl#.2BAuto_Spread:|#.2BAuto_Spread:]], but not before the weapon itself has travelled at least a distance equal to that. Note that impact effects normally projected onto the shield mesh will not work.}}

==="model point shields"===
{{Table371|
Instead of the standard 4 shield quadrants, the ship uses an arbitrary number of shield sections which must have been defined in the model file, see [[Model Point Shields]]. If used on a player ship, you must also define [[Ships.tbl#.24Model_Point_Shield_Controls:|#.24Model_Point_Shield_Controls:]] to allow the shield augmentation controls to be used.}}

==Player Ship Precedence==
*Syntax: ( '''''"String" "String"''''')
===Example===

<pre>
$Player Ship Precedence: (
"GTF Ulysses"
"GTF Hercules"
"GTB Medusa"
"GTB Ursa" )
</pre>

==Sample==

<pre>
#Default Player Ship

$Name: GTF Ulysses

#End

#Engine Wash Info

$Name: Default
$Angle: 10.0
$Radius Mult: 1.2
$Length: 400
$Intensity: 1.0

#End

#Ship Classes
$Name: GTF Ulysses
$Short name: TFight
$Species: Terran
+Type: XSTR("Space Superiority", -1)
+Maneuverability: XSTR("Excellent", -1)
+Armor: XSTR("Light", -1
+Manufacturer: XSTR("Triton / Mekhu", -1)
+Description: XSTR( " ", -1)
$end_multi_text
+Tech Description: XSTR("Descriptive text", -1)
$end_multi_text
+Length: 16 m
+Gun Mounts: 4
+Missile Banks: 1
$POF File: fighter01.pof
$Detail Distance: (0, 80, 300, 900)
$ND: 42 42 244
$Show Damage: YES
$Density: 1
$Damp: 0.1
$Rotdamp: 0.35
$Max Velocity: 0.0, 0.0, 70.0
$Rotation Time: 3.0, 2.6, 5.0
$Rear Velocity: 0.0
$Forward Accel: 2.0
$Forward Decel: 1.5
$Slide Accel: 0.0
$Slide Decel: 0.0
$Expl Inner Rad: 25.0
$Expl Outer Rad: 55.0
$Expl Damage: 15.0
$Expl Blast: 1000.0
$Expl Propagates: NO
$Shockwave Speed: 0.0
$Allowed PBanks: ( "Subach HL-7" "Prometheus R")
$Allowed Dogfight PBanks: ( "Subach HL-D" "Prometheus D" )
$Default PBanks: ( "Subach HL-7" "Prometheus R" )
$Allowed SBanks: ( "Rockeye" "Tempest" )
$Allowed Dogfight SBanks: ( "Tempest D" "Hornet D" )
$Default SBanks: ( "Harpoon" )
$SBank Capacity: ( 40 )
$Shields: 380
$Shield Color: 100 100 255
$Power Output: 2.0
$Max Oclk Speed: 94.0
$Max Weapon Eng: 80.0
$Hitpoints: 180
$Flags: ( "player_ship"
"default_player_ship"
"fighter"
"in tech database")
$AI Class: Captain
$Afterburner: YES
+Aburn Max Vel: 0.0, 0.0, 150.0
+Aburn For accel: 0.7
+Aburn Fuel: 300.0
+Aburn Burn Rate: 50.0
+Aburn Rec Rate: 25.0
$Countermeasures: 25
$Scan Time: 2000
$EngineSnd: 128
$Closeup_Pos: 0.0, 0.0, -22
$Closeup_Zoom: 0.5
$Shield_Icon: shield-f01
$Ship_Icon: iconfighter01
$Ship_Anim: ssfighter01
$Ship_Overhead: loadfighter01
$Score: 8
$Trail:
+Offset: -7.75 -2.8 0.75
+Start Width: 0.25
+End Width: 0.05
+Start Alpha: 1.0
+End Alpha: 0.0
+Max Life: 1.0
+Spew Time: 60
+Bitmap: Contrail01
$Trail:
+Offset: 7.75 -2.8 0.75
+Start Width: 0.25
+End Width: 0.05
+Start Alpha: 1.0
+End Alpha: 0.0
+Max Life: 1.0
+Spew Time: 60
+Bitmap: Contrail01
$Subsystem: communication, 10, 0
$Subsystem: navigation, 10, 0
$Subsystem: weapons, 20, 0
$Subsystem: sensors, 10, 0
$Subsystem: engines, 35, 0

#End

$Player Ship Precedence: (
"GTF Ulysses")
</pre>

[[Category:Tables]]

Template:Table381

2019-12-22T04:34:54Z

AdmiralRalwood: Changing redirect.

#REDIRECT [[Template:Table190]]

Template:Table190

2019-12-22T04:34:44Z

AdmiralRalwood: Change version from 3.8.2 to 19.0

<noinclude>[[Category:Templates|Table190]]</noinclude>
<div style="padding: 1px 2px 1px 2px; background-color: #156364; border: solid 1px #1d8788; padding: 0px 4px; font-size: -1; color: #31e5e7">'''FS2 Open, 19.0:''' {{{1}}}</div>

Template:Table190

2019-12-22T04:34:11Z

AdmiralRalwood: AdmiralRalwood moved page Template:Table382 to Template:Table190: Next release will be 19.0, not 3.8.2.

<noinclude>[[Category:Templates|Table382]]</noinclude>
<div style="padding: 1px 2px 1px 2px; background-color: #156364; border: solid 1px #1d8788; padding: 0px 4px; font-size: -1; color: #31e5e7">'''FS2 Open, 3.8.2:''' {{{1}}}</div>

Template:Table382

2019-12-22T04:34:11Z

AdmiralRalwood: AdmiralRalwood moved page Template:Table382 to Template:Table190: Next release will be 19.0, not 3.8.2.

#REDIRECT [[Template:Table190]]

Fireball.tbl

2019-04-14T22:46:11Z

AdmiralRalwood: /* Table Fields */ Mention that "$Unique ID:" can be used to reference the fireball for an SSM strike warp effect.

{{TableVersionGit|2018-09-20|5206aaa}}

The '''fireball.tbl''' is used to define the usage of animations with certain special effects in game.

This table is one of the [[Modular Tables]] and can be extended with xxx-fbl.tbm.

[[Tables|List of Tables]]

==General Format==
*Fireball.tbl table file is used for specifying which filenames are to be used for which explosions
*Table begins with '''#Start'''
*Table uses rigid system in the order of the entries:
*'''''Fireball.tbl''''' has 6 entries with a specific function and every one '''''is required''''' and must be listed in the following order.
*Order of the entries in fireball.tbl:
**'''Medium sized explosion'''
**'''Normal warp effect'''
**'''Knossos warp effect'''
**'''Asteroid explosion'''
**'''Large explosion 1'''
**'''Large explosion 2'''
*Any entries defined after the first 6 is considered a custom fireball and will not be used in the game unless specified as an explosion for a ship type or ship class in ships.tbl or objecttypes.tbl, or a custom warp effect in the warp-effect sexp.
*Table ends with '''#End'''
*The modular version of the fireball table can only replace existing entries in fireball.tbl. No entries can be created in a modular table for fireball.tbl
{{Table381|
*As of 3.8.2, the internal code to handle modular fireball.tbl entries has been rewritten, and it is now possible to add entries in a modular table.
}}
*All entries defined in a modular table for fireball.tbl require a '''$Name:''' token before specifying the bitmap filename. A fireball identifier must also be defined in order to specify which individual entry in fireball.tbl that will be replaced, see [[fireball.tbl#Fireball_identifier|fireball identifier]].
*The modular table entries can be in arbitrary order and can be placed in separate modular tables.

==Table Fields==
{{Table381|
===$Unique ID:===
*Defines a string that can be used as a reference for this fireball entry. In most tables, $Name performs this role, but fireball.tbl allows multiple fireball entries which use the same animation. The unique ID can be used to override fireball entries in a modular table, or to reference a fireball in the <tt>warp-effect</tt> and <tt>explosion-effect</tt> SEXPs, or as the warp effect of an [[Ssm.tbl#+WarpEffect:|SSM strike]].

*If this field is not present, the game will generate a unique ID for the entry automatically.
**Syntax: '''String'''
}}
===$Name:===
*Defines the name of the animation used for the particular fireball effect
**Syntax: '''String''', filename

===Fireball identifier===
{{Table3610|
*Identifies the assigned animation with one of the fireball types. Only used in '''xxx-fbl.tbm'''
**Syntax: '''String''', name of the identifier
**Allowed identifiers:
:::'''+Explosion_Medium'''
:::'''+Warp_Effect'''
:::'''+Knossos_Effect'''
:::'''+Asteroid'''
:::'''+Explosion_Large1'''
:::'''+Explosion_Large2'''
:::'''+Custom_Fireball 6'''
:::'''+Custom_Fireball 7'''
:::'''+Custom_Fireball (...)'''}}
{{Table381|
*In 3.8.2, this is not required; $Unique ID can be used as an alternative. If neither the identifier nor $Unique ID is present, the entry is assumed to be a new custom fireball.
}}

===$LOD:===
*Optional '''$LOD:''' entry exists to specify a lod count, at least 1 is assumed if not specified.
**Syntax: '''Integer'''

===$Light Color:===
{{Table3610|
*Defines the color that is given off when that fireball effect is created.
**Syntax: '''Color''', three '''integers''', 0 to 255, red, green, blue respectively}}

====Default colors====
{{Table3610|
*''Large explosion 1'', ''large explosion 1'', ''medium sized explosion'', and ''asteroid explosion''
**255, 127, 31
*''Normal warp effect''
**191, 191, 255
*''Knossos warp effect''
**191, 255, 191}}

{{Table381|
===$Warp glow:===
*Defines the warp glow bitmap used if this fireball is a warp effect. By default, <tt>warpglow01</tt> is internally assigned to ''both'' the '''Warp Effect''' and '''Knossos Effect''' entries, but both the tbl and tbm can override this. Retail <tt>sparky_fs2.vp</tt> supplies a <tt>warpglow02</tt> bitmap for the Knossos effect, but the game never actually uses it.
**Syntax: '''String'''
}}

{{Table381|
===$Warp ball:===
*Defines the "warp ball" bitmap used if this fireball is a warp effect. By default, <tt>warpball01</tt> is internally assigned to ''both'' the '''Warp Effect''' and '''Knossos Effect''' entries, but both the tbl and tbm can override this. The "warp ball" bitmap is only used for the "flash on warp" command-line option.
**Syntax: '''String'''
}}

{{Table381|
===$Warp model:===
*Defines the warp model file used if this fireball is a warp effect. By default, <tt>warp.pof</tt> is internally assigned to ''both'' the '''Warp Effect''' and '''Knossos Effect''' entries, but both the tbl and tbm can override this. The warp model is used for the "3D warp" command-line option, or for the <tt>warp-effect</tt> SEXP when a 3D warp is specified.
**Syntax: '''String'''
}}

==Sample Entries==

*'''fireball.tbl'''
<pre>
#Start
$Name: exp04
$LOD: 1
$Name: WarpMap01
$LOD: 4
$Name: WarpMap02
$LOD: 4
$Name: exp05
$LOD: 4
$Name: exp05
$LOD: 4
$Name: exp06
$LOD: 4
#End
</pre>

{{Table3610|

'''fireball.tbl'''
<pre>
; This is an example of a table that defines the the default 6 fireball
; bitmaps (Fireballs 0 through 5) while adding extra custom fireballs as well.
#Start
$Name: exp04 ;0 Used for the 4 little explosions before a ship explodes
$LOD: 1
$Name: WarpMap01 ;1 Used for the warp in / warp out effect
$LOD: 4
$Name: WarpMap02 ;2 Used for the KNOSSOS warp in / warp out effect
$LOD: 4
$Name: exp05 ;3 Used when an asteroid explodes
$LOD: 4
$Name: exp05 ;4 ship explosion 1
$LOD: 4
$Name: exp06 ;5 ship explosion 2
$LOD: 4
$Name: capship_boom ;6 First custom fireball. Identified as +Custom_Fireball 6
$LOD: 1
$Name: debris_dust_cloud ;7 Second custom fireball. Identified as +Custom_Fireball 7
$LOD: 1
$Name: corvette_exp ;8 Third custom fireball. Identified as +Custom_Fireball 8
$LOD: 1
$Name: fenris_exp ;9 Fourth custom fireball. Identified as +Custom_Fireball 9
$LOD: 1
#End
</pre>

'''xxx-fbl.tbm'''
<pre>
; This modular table replaces the entries in the sample fireball.tbl printed above
#Start
$Name: exp06
+Asteroid
$LOD: 4
$Name: fighter_explosion
+Custom_Fireball 7
$LOD: 4
$Name: capship_explosion
+Custom_Fireball 6
$LOD: 1
$Name: big_exp
+Explosion_Large1
$LOD: 1
$Name: capship_explosion1
+Custom_Fireball 8
$LOD: 1
$Name: capship_explosion2
+Custom_Fireball 9
$LOD: 1
#End
</pre>
}}

[[Category:Tables]]

Ssm.tbl

2019-04-14T22:44:38Z

AdmiralRalwood: Adding "+WarpEffect:".

{{TableVersionGit|2019-04-15|4824428}}

The '''ssm.tbl''' was originally meant for defining the flight behavior of subspace missiles (SSM).

This table is one of the [[Modular Tables]] and can be extended with xxx-ssm.tbm

[[Tables|List of Tables]]

==Format==
*Table consists of independent '''$SSM:''' entries
*Table ends with '''#end'''

==Table Entries==

==$SSM:==
*Names the SSM strike.
{{Table374|The name itself is optional; if not present, it gets defaulted to "SSM <index>", allowing easy selection in FRED.}}
*Syntax: '''String''', name of the strike (as used by SEXPs and weapons)

===+Weapon:===
*Defines the weapon used in the strike.
*Syntax: '''String''', name of the weapon

===+Count:===
* (Optional) Defines number of the weapons fired by the strike.
*Syntax: '''Integer''', defaults to 1
{{Table374|
===+Min Count:===
* (Optional) Can be used instead of "+Count:", and in combination with "+Max Count:", to allow for a random number of weapons to be in the strike.
*Syntax: '''Integer'''
===+Max Count:===
* (Required if "+Min Count:" is used) Specifies the maximum number of weapons that can be fired by the strike.
*Syntax: '''Integer'''}}

===+WarpEffect:===
{{Table382|
* (Optional) Defines which fireball to use for the warp effect. Can be either the fireball index or its [[Fireball.tbl#$Unique_ID:|unique ID]].
*Syntax: '''Integer''' or '''String''', defaults to "Warp Effect" (index 1)}}

===+WarpRadius:===
*Defines the radius of the warp effect.
*Syntax: '''Float'''

===+WarpTime:===
* (Optional) Defines the lifetime of the warp effect in seconds. Non-beam weapons fire halfway through this lifetime; beam weapons either fire at the start of the effect or at the appropriate time so that the midpoint of the beam is the same as the midpoint of the warp effect, whichever is later.
*Syntax: '''Float''', defaults to 4.0

===+Radius:===
*Defines the radius of the formation used by the weapons in the strike.
*Syntax: '''Float'''
{{Table374|
===+Min Radius:===
* (Optional) Can be used instead of "+Radius", and in combination with "+Max Radius:", to allow for a random radius to be used by the strike.
*Syntax: '''Float'''
===+Max Radius:===
* (Required if "+Min Radius:" is used) Specifies the maximum radius of the strike formation.
*Syntax: '''Float'''}}

===+Offset:===
* (Optional) Defines the offset of the formation used by the weapons in the strike; generally works best with circular strikes.
*Syntax: '''Float''', defaults to 0
{{Table374|
===+Min Offset:===
* (Optional) Can be used instead of "+Offset", and in combination with "+Max Offset:", to allow for a random offset to be used by the strike.
*Syntax: '''Float'''
===+Max Offset:===
* (Required if "+Min Offset:" is used) Specifies the maximum offset of the strike formation.
*Syntax: '''Float'''}}

===+Shape:===
{{Table373|
* (Optional) The shape used for the formation of weapons.
*Syntax: '''Point''', '''Circle''', or '''Sphere'''; defaults to Circle}}

===+HUD Message:===
* (Optional) Whether or not firing this SSM triggers a HUD message.
*Syntax: '''Boolean''', defaults to true

===+Custom Message:===
* (Optional) Can be used to define a custom message to be triggered when the SSM is fired.
*Syntax: '''String'''
*Note: By default, the message played is the one defined in strings.tbl index 1570, which is set to the generic "Firing Artillery"

===+Alarm Sound:===
{{Table371|
* (Optional) Can be used to define a custom alarm sound to be played when the SSM is fired.
*Syntax: '''Integer'''}}

[[Category:Tables]]

Sounds.tbl

2019-01-29T05:47:06Z

AdmiralRalwood: /* +nocreate */ Make it more clear that the behavior of +nocreate here is atypical.

{{TableVersion| 344502c (Git commit)}}

The '''sounds.tbl''' is a file for defining the various sounds played ingame.

This table is one of the [[Modular Tables]] and can be extended with xxx-snd.tbm

[[Tables|List of Tables]]

==Format==
*Table file consists of several sections
*First section defines the sound for the actual game play. It begins at '''#Game Sounds Start''' and ends at'''#Game Sounds End'''
*Second section defines the interface sounds. It starts at '''#Interface Sounds Start''' and ends at '''#Interface Sounds End'''
*Third section defines the flyby sounds for different species. It begins at '''#Flyby Sounds Start''' and ends at '''#Flyby Sounds End'''
*This table has three possible syntaxes. The "Sound set" syntax allows to use multiple sounds. The "SCP Syntax" was introduced as a general improvement over the retail Syntax and is very similar to the sound set syntax.
**The Sound set syntax allows to specify multiple sound files for one sound entry and also has a wider variety of options for specifying how the sound should be played. This syntax is based on the SCP syntax and it should be easy to adapt sound entries that use the SCP syntax to the new sound set syntax. This is only required if the new features of the sound set changes are to be used. Otherwise the SCP syntax can be used.
**The SCP Syntax is an improvement of the retail syntax whis is easier to read, and likely preferred for modular tables and extendability.
**The Retail Syntax is the syntax used by the retail tables which was kept in place to keep retail compatibility
*Most of the sounds are hardcoded in the engine (that is, the engine expects sound 33 to be the missile rearm sound, as an example). Modders should follow the retail table layout, and not assign sound numbers smaller than 250 to their custom sounds. This avoids index collisions.

==Sound set syntax==
{{Note|Many retail sound names are hardcoded to a specific type of sound, so removing entries is not recommended. However adding new ones or altering existing ones is possible. See the [[Hardcoded sounds|hardcoded sounds]] for a list of which sounds have hardcoded names.}}

{{Table381|
}}

If this syntax is in use then the new sound set features can be used. These include the ability to use multiple sound files for one entry and with this feature it is possible to randomize the volume and pitch values when a sound is played. Compared to the SCP syntax there are only a few changes: Instead of ''+Filename'' this now uses ''+Entry'' and allows using that option as often as needed. The ''+Volume'' option accepts a random range for possible values and the ''+Pitch'' option is new.

In most entries, the name of the file ('''Second''' value) can be replaced with 'empty' if the particular sound index is not in use.

===#Game Sounds Start===
Notes
*Cockpit sounds are in general non-3D sounds
*All the other in-flight sounds are, in general, 3D sounds
*Non-3D sounds do not require the '''+3D Sound''' entries

Example Line
<pre>
$Name: 6
+Entry: breakup
+Cycle type: sequential
+Preload: no
+Volume: (0.60)
+3D Sound:
+Attenuation start: 100
+Attenuation end: 800
+Priority: High
+Limit: 3
+Pitch: (1.0)
</pre>

====$Name:====
*Specifies the sound handle which FSO will use to identify the sound from other tables
*If +nocreate is to be used, it must come after '''$Name:''' and before the '''String'''
*Syntax: '''String'''
{{Warning|
The name may not contain any whitespace (space or tab characters) or the old parsing code will be used.}}

====+nocreate====
*Allows editing of the sound without creating a new sound handle
*Must be placed after '''$Name:''' and before the '''String'''
*Example
**<pre>$Name: +nocreate SoundName</pre>
{{Warning|
Unlike most other tables, existing entries cannot be overwritten/modified without the presence of '''+nocreate'''.}}

====+Entry:====
*The name of the actual sound file. This option may appear more than once if multiple sound files should be used for this sound entry.
*Always required once, even if +nocreate is used.
*To specify no sound file, use "empty" (without the quotes)
*If +nocreate is used then sound files can only be added to the sound but no other modification is available.
*Syntax: '''String'''

====+Cycle type:====
*Specifies how the next sound entry should be chosen from the ''+Entry'' list
*Required, optional if +nocreate is used
*May use one of the following modes:
**'''sequential''': The entry will be chosen sequentially from the list. '''Note:''' The sequence of played sounds is determined globally so if there are two sound sources using the same entry then the sounds may appear as missing parts for either source since the other source used that entry before.
**'''random''': An entry is chosen uniformly at random from the entries list
*Syntax: '''sequential''' or '''random'''

====+Preload:====
*Specifies whether FSO should always preload the sound before the mission or not
*Optional if +nocreate is used, required otherwise
*Syntax: '''Boolean'''

====+Volume:====
*Specifies the volume the sound should be played at as a random range between 0 and 1. The actual volume will be picked within that range whenever a sound is played
*Optional if +nocreate is used, required otherwise
*Syntax: '''(Float)''' or '''(Float Float)''', example: ''(0.5 1.0)''. It is also valid to only specify one value if there should be no randomization.

====+3D Sound:====
*Sets up table syntax for specifying 3D sound options
*If present the sound will be loaded as a 3D sound
*No argument should be specified
*Must be accompanied by '''+Attenuation Start:''' and '''+Attenuation End:'''

====+Attenuation Start:====
*Defines the distance from the origin of the 3D sound where it begins to attenuate
*Must be preceded by '''+3D Sound:'''
*Syntax: '''Integer'''

====+Attenuation End:====
*Defines the distance from the origin of the 3D sound where it is inaudible
*Must be preceded by '''+3D Sound:'''
*Syntax: '''Integer'''

====+Priority:====
*Optional, for use with [[Enhanced sound|enhanced sound]]
*Can be used with or without an accompanying +Limit:
*Specifies the priority of this sound when enhanced sound is used
*Should be based on how important this sound is and also how likely the player will notice if the sound drops out
*overrides the engine default value
*For valid values, see the table below. Values are not case-sensitive.
*See the [[Enhanced sound]] page for more information.
*Syntax: '''String'''

<pre>
Value Meaning
----- -------
Must Play Absolutely must play
High Very important
Medium-High Important
Medium Somewhat important
Medium-Low Only a little important
Low Not important
</pre>

====+Limit:====
*Optional, for use with [[Enhanced sound|enhanced sound]]
*Can be used with or without an accompanying +Priority:
*Specifies how many instances of the sound can play at the same time
*overrides the engine default value
*Must be in the range 1 - 15
*See the [[Enhanced sound]] page for more information,
*Syntax: '''Integer'''

====+Pitch:====
*Specifies which pitch values the sound may be assigned
*Optional, defaults to 1.0
*This is a random range which specifies the possible pitch values the sound may be assigned
*The actual effect of these values is very complicated to describe so you should simply test to check which values sound well. A value of 1.0 plays the sound without any changes.
*Syntax: '''(Float)''' or '''(Float Float)''', example: ''(0.9 1.1)''. It is also valid to only specify one value if there should be no randomization.

'''Section ends with #Game Sounds End'''

===#Interface Sounds Start===
Notes
*Interface sounds are not 3D sounds. You may specify '''+3D Sound:''' properties, but they will be ignored.

Example Line
<pre>
$Name: CraneSound1
+Entry: Crane_1
+Cycle type: sequential
+Preload: no
+Volume: 0.50
</pre>

====$Name:====
*Specifies the sound handle which FSO will use to identify the sound from other tables
*If +nocreate is to be used, it must come after '''$Name:''' and before the '''String'''
*Syntax: '''String'''
{{Warning|
The name may not contain any whitespace (space or tab characters) or the old parsing code will be used.}}

====+nocreate====
*Allows editing of the sound without creating a new sound handle
*Must be placed after '''$Name:''' and before the '''String'''
*Example
**<pre>$Name: +nocreate SoundName</pre>

====+Entry:====
*The name of the actual sound file. This option may appear more than once if multiple sound files should be used for this sound entry.
*Always required once, even if +nocreate is used.
*To specify no sound file, use "empty" (without the quotes)
*If +nocreate is used then sound files can only be added to the sound but no other modification is available.
*Syntax: '''String'''

====+Cycle type:====
*Specifies how the next sound entry should be chosen from the ''+Entry'' list
*Required, optional if +nocreate is used
*May use one of the following modes:
**'''sequential''': The entry will be chosen sequentially from the list. '''Note:''' The sequence of played sounds is determined globally so if there are two sound sources using the same entry then the sounds may appear as missing parts for either source since the other source used that entry before.
**'''random''': An entry is chosen uniformly at random from the entries list
*Syntax: '''sequential''' or '''random'''

====+Preload:====
*Specifies whether FSO should always preload the sound before the mission or not
*Syntax: '''Boolean'''

====+Volume:====
*Specifies the volume the sound should be played at as a random range between 0 and 1. The actual volume will be picked within that range whenever a sound is played
*Optional if +nocreate is used, required otherwise
*Syntax: '''(Float)''' or '''(Float Float)''', example: ''(0.5 1.0)''. It is also valid to only specify one value if there should be no randomization.

====+Pitch:====
*Specifies which pitch values the sound may be assigned
*Optional, defaults to 1.0
*This is a random range which specifies the possible pitch values the sound may be assigned
*The actual effect of these values is very complicated to describe so you should simply test to check which values sound well. A value of 1.0 plays the sound without any changes.
*Syntax: '''(Float)''' or '''(Float Float)''', example: ''(0.9 1.1)''. It is also valid to only specify one value if there should be no randomization.

'''Section ends with #Interface Sounds End'''

===#Flyby Sounds Start===
Notes
*Each species has two flyby sounds. One for the fighters and one for the bombers.
*Flyby sounds are all 3D sounds.
*Each flyby sound is defined on a line that begins with the species name ('''String''', species name, eg. '''$Terran:''').
*'''THE FLYBY SECTION CANNOT USE +nocreate'''
If you want to modify a flyby sound entry of a species in a modular table then you will need to have entries for both types.

Line starts with '''$SPECIES:''' in the place of '''$Name:'''

Example Terran Section
<pre>
$Terran: 0
+Entry: T_flyby1
+Cycle type: sequential
+Preload: no
+Volume: (0.75)
+3D Sound:
+Attenuation start: 200
+Attenuation end: 400

$Terran: 1
+Entry: T_flyby2
+Cycle type: sequential
+Preload: no
+Volume: (0.75)
+3D Sound:
+Attenuation start: 200
+Attenuation end: 400
</pre>

====$Name:====
*'''$Name''' must be replaced with '''$SPECIES''' as from the [[Species_defs.tbl]]
*Specifies the sound handle which FSO will use to identify the sound from other tables
*In this case it will usually be a '''1''' or a '''0'''
*Syntax: '''String'''
{{Warning|
The name may not contain any whitespace (space or tab characters) or the old parsing code will be used.}}

====+Entry:====
*The name of the actual sound file. This option may appear more than once if multiple sound files should be used for this sound entry.
*Always required once, even if +nocreate is used.
*To specify no sound file, use "empty" (without the quotes)
*If +nocreate is used then sound files can only be added to the sound but no other modification is available.
*Syntax: '''String'''

====+Cycle type:====
*Specifies how the next sound entry should be chosen from the ''+Entry'' list
*Required, optional if +nocreate is used
*May use one of the following modes:
**'''sequential''': The entry will be chosen sequentially from the list. '''Note:''' The sequence of played sounds is determined globally so if there are two sound sources using the same entry then the sounds may appear as missing parts for either source since the other source used that entry before.
**'''random''': An entry is chosen uniformly at random from the entries list
*Syntax: '''sequential''' or '''random'''

====+Preload:====
*Specifies whether FSO should always preload the sound before the mission or not
*Syntax: '''Boolean'''

====+Volume:====
*Specifies the volume the sound should be played at as a random range between 0 and 1. The actual volume will be picked within that range whenever a sound is played
*Optional if +nocreate is used, required otherwise
*Syntax: '''(Float)''' or '''(Float Float)''', example: ''(0.5 1.0)''. It is also valid to only specify one value if there should be no randomization.

====+3D Sound:====
*Sets up table syntax for specifying 3D sound options
*If present the sound will be loaded as a 3D sound
*No argument should be specified
*Must be accompanied by '''+Attenuation Start:''' and '''+Attenuation End:'''

====+Attenuation Start:====
*Defines the distance from the origin of the 3D sound where it begins to attenuate
*Must be preceded by '''+3D Sound:'''
*Syntax: '''Integer'''

====+Attenuation End:====
*Defines the distance from the origin of the 3D sound where it is inaudible
*Must be preceded by '''+3D Sound:'''
*Syntax: '''Integer'''

====+Pitch:====
*Specifies which pitch values the sound may be assigned
*Optional, defaults to 1.0
*This is a random range which specifies the possible pitch values the sound may be assigned
*The actual effect of these values is very complicated to describe so you should simply test to check which values sound well. A value of 1.0 plays the sound without any changes.
*Syntax: '''(Float)''' or '''(Float Float)''', example: ''(0.9 1.1)''. It is also valid to only specify one value if there should be no randomization.

'''Section ends with #Flyby Sounds End'''

==SCP Syntax==
{{Note|Many retail sound names are hardcoded to a specific type of sound, so removing entries is not recommended. However adding new ones or altering existing ones is possible. See the [[Hardcoded sounds|hardcoded sounds]] for a list of which sounds have hardcoded names.}}

In most entries, the name of the file ('''Second''' value) can be replaced with 'empty' if the particular sound index is not in use.

===#Game Sounds Start===
Notes
*Cockpit sounds are in general non-3D sounds
*All the other in-flight sounds are, in general, 3D sounds
*Non-3D sounds do not require the '''+3D Sound''' entries

Example Line
<pre>
$Name: 6
+Filename: breakup
+Preload: no
+Volume: 0.60
+3D Sound:
+Attenuation start: 100
+Attenuation end: 800
+Priority: High
+Limit: 3
</pre>

====$Name:====
*Specifies the sound handle which FSO will use to identify the sound from other tables
*If +nocreate is to be used, it must come after '''$Name:''' and before the '''String'''
*Syntax: '''String'''
{{Warning|
The name may not contain any whitespace (space or tab characters) or the old parsing code will be used.}}

====+nocreate====
*Allows editing of the sound without creating a new sound handle
*Must be placed after '''$Name:''' and before the '''String'''
*Example
**<pre>$Name: +nocreate SoundName</pre>

====+Filename:====
*The name of the actual sound file to play
*Always required, even if +nocreate is used.
*To specify no sound file, use "empty" (without the quotes)
*If +nocreate is used and you don't want to change the original filename, then use <same> (including the <>)
*Syntax: '''String'''

====+Preload:====
*Specifies whether FSO should always preload the sound before the mission or not
*Optional if +nocreate is used, required otherwise
*Syntax: '''Boolean'''

====+Volume:====
*Specifies the volume the sound should be played at as a percentage
*Optional if +nocreate is used, required otherwise
*Syntax: '''Float'''

====+3D Sound:====
*Sets up table syntax for specifying 3D sound options
*If present the sound will be loaded as a 3D sound
*No argument should be specified
*Must be accompanied by '''+Attenuation Start:''' and '''+Attenuation End:'''

====+Attenuation Start:====
*Defines the distance from the origin of the 3D sound where it begins to attenuate
*Must be preceded by '''+3D Sound:'''
*Syntax: '''Integer'''

====+Attenuation End:====
*Defines the distance from the origin of the 3D sound where it is inaudible
*Must be preceded by '''+3D Sound:'''
*Syntax: '''Integer'''

====+Priority:====
*Optional, for use with [[Enhanced sound|enhanced sound]]
*Can be used with or without an accompanying +Limit:
*Specifies the priority of this sound when enhanced sound is used
*Should be based on how important this sound is and also how likely the player will notice if the sound drops out
*overrides the engine default value
*For valid values, see the table below. Values are not case-sensitive.
*See the [[Enhanced sound]] page for more information.
*Syntax: '''String'''

<pre>
Value Meaning
----- -------
Must Play Absolutely must play
High Very important
Medium-High Important
Medium Somewhat important
Medium-Low Only a little important
Low Not important
</pre>

====+Limit:====
*Optional, for use with [[Enhanced sound|enhanced sound]]
*Can be used with or without an accompanying +Priority:
*Specifies how many instances of the sound can play at the same time
*overrides the engine default value
*Must be in the range 1 - 15
*See the [[Enhanced sound]] page for more information,
*Syntax: '''Integer'''

'''Section ends with #Game Sounds End'''

===#Interface Sounds Start===
Notes
*Interface sounds are not 3D sounds. You may specify '''+3D Sound:''' properties, but they will be ignored.

Example Line
<pre>
$Name: CraneSound1
+Filename: Crane_1
+Preload: no
+Volume: 0.50
</pre>

====$Name:====
*Specifies the sound handle which FSO will use to identify the sound from other tables
*If +nocreate is to be used, it must come after '''$Name:''' and before the '''String'''
*Syntax: '''String'''
{{Warning|
The name may not contain any whitespace (space or tab characters) or the old parsing code will be used.}}

====+nocreate====
*Allows editing of the sound without creating a new sound handle
*Must be placed after '''$Name:''' and before the '''String'''
*Example
**<pre>$Name: +nocreate SoundName</pre>

====+Filename:====
*The name of the actual sound file to play
*Syntax: '''String'''

====+Preload:====
*Specifies whether FSO should always preload the sound before the mission or not
*Syntax: '''Boolean'''

====+Volume:====
*Specifies the volume the sound should be played at as a percentage
*Syntax: '''Float'''

'''Section ends with #Interface Sounds End'''

===#Flyby Sounds Start===
Notes
*Each species has two flyby sounds. One for the fighters and one for the bombers.
*Flyby sounds are all 3D sounds.
*Each flyby sound is defined on a line that begins with the species name ('''String''', species name, eg. '''$Terran:''').
*'''THE FLYBY SECTION CANNOT USE +nocreate'''
If you want to modify a flyby sound entry of a species in a modular table then you will need to have entries for both types.

Line starts with '''$SPECIES:''' in the place of '''$Name:'''

Example Terran Section
<pre>
$Terran: 0
+Filename: T_flyby1
+Preload: no
+Volume: 0.75
+3D Sound:
+Attenuation start: 200
+Attenuation end: 400

$Terran: 1
+Filename: T_flyby2
+Preload: no
+Volume: 0.75
+3D Sound:
+Attenuation start: 200
+Attenuation end: 400
</pre>

====$Name:====
*'''$Name''' must be replaced with '''$SPECIES''' as from the [[Species_defs.tbl]]
*Specifies the sound handle which FSO will use to identify the sound from other tables
*In this case it will usually be a '''1''' or a '''0'''
*Syntax: '''String'''
{{Warning|
The name may not contain any whitespace (space or tab characters) or the old parsing code will be used.}}

====+Filename:====
*The name of the actual sound file to play
*Syntax: '''String'''

====+Preload:====
*Specifies whether FSO should always preload the sound before the mission or not
*Syntax: '''Boolean'''

====+Volume:====
*Specifies the volume the sound should be played at as a percentage
*Syntax: '''Float'''

====+3D Sound:====
*Sets up table syntax for specifying 3D sound options
*If present the sound will be loaded as a 3D sound
*No argument should be specified
*Must be accompanied by '''+Attenuation Start:''' and '''+Attenuation End:'''

====+Attenuation Start:====
*Defines the distance from the origin of the 3D sound where it begins to attenuate
*Must be preceded by '''+3D Sound:'''
*Syntax: '''Integer'''

====+Attenuation End:====
*Defines the distance from the origin of the 3D sound where it is inaudible
*Must be preceded by '''+3D Sound:'''
*Syntax: '''Integer'''

'''Section ends with #Flyby Sounds End'''

==Retail Syntax==
{{Note|Many retail sound names are hardcoded to a specific type of sound, so removing entries is not recommended. However adding new ones or altering existing ones is possible. See the [[Hardcoded sounds|hardcoded sounds]] for a list of which sounds have hardcoded names.}}

In most entries, the name of the file ('''Second''' value) can be replaced with 'empty' if the particular sound index is not in use.

===#Game Sounds Start===
Notes
*Cockpit sounds are in general non-3D sounds that ought to be of type '0', however all the other in-flight sounds are in general 3D sounds and ought to of type '1' (or type '2').
*Type 0 sounds do not require the '''Sixth''' and '''Seventh''' entries.

Example Line
<pre>$Name: 6 breakup.wav, 0, 0.60, 1, 100, 800</pre>

Line starts with ''$Name:'' and has seven entries separated by commas except for the first and second entries.

**'''First''' value is the index number of the sound ('''Integer''')
**'''Second''' value is the name of actual sound file ('''String''', filename).
**'''Third''' value sets the file to always preloaded before the mission ('''Integer''', 0 or 1)
**'''Fourth''' value defines the playing volume of the sound in percentages ('''Float''', from 0 to 1)
**'''Fifth''' value sets the sound type to either standard sound (type '0'), 3D stereo sound (type '1'), or Aureal A3D (type '2'). This defaults to 3D stereo if it is not available ('''Integer''', 0, 1 or 2)
***'''Sixth''' value defines the distance from the origin of 3D sound where it begins to attenuate and is not used with normal non-3D sounds (type 0)('''Integer''')
***'''Seventh''' value sets the distance from the origin of the 3D sound where it is inaudible and is not used with normal non-3D sounds (type 0)('''Integer''')

'''Section ends with #Game Sounds End'''

===#Interface Sounds Start===
Notes
*Interface sounds are not 3D sounds. Use type '0' sounds. The '''Sixth''' and '''Seventh''' entries can be left out of sounds in this section.

Example Line
<pre>$Name: 26 Crane_1.wav, 0, 0.50, 0</pre>

Line starts with ''$Name:'' and has five entries separated by commas except for the first and second entries.

**'''First''' value is the index number of the sound ('''Integer''')
**'''Second''' value is the name of actual sound file ('''String''', filename or '''Empty''').
**'''Third''' value sets the file to always preloaded before the mission ('''Integer''', 0 or 1)
**'''Fourth''' value defines the playing volume of the sound in percentages ('''Float''', from 0 to 1)
**'''Fifth''' value sets the sound type to either standard sound (type '0'), 3D stereo sound (type '1'), or Aureal A3D (type '2'). This defaults to 3D stereo if it is not available ('''Integer''', 0, 1 or 2)

'''Section ends with #Interface Sounds End'''

===#Flyby Sounds Start===
Notes
*Each species has two flyby sounds. One for the fighters and one for the bombers.
*Flyby sounds are all 3D sounds of type '1' for the '''Fifth''' value.
*Each flyby sound is defined on a single line that begins with the species name ('''String''', species name, eg. '''$Terran:''').

Retail flyby section
<pre>
#Flyby Sounds Start

$Terran: 0 T_flyby1.wav, 0, 0.75, 1, 200, 400 ; * Terran ship1 flyby player sound (3d sound)
$Terran: 1 T_flyby2.wav, 0, 0.75, 1, 200, 400 ; * Terran ship1 flyby player sound (3d sound)

$Vasudan: 0 V_flyby1.wav, 0, 0.85, 1, 200, 400 ; * Vasudan ship1 flyby player sound (3d sound)
$Vasudan: 1 V_flyby2.wav, 0, 0.85, 1, 200, 400 ; * Vasudan ship1 flyby player sound (3d sound)

$Shivan: 0 S_flyby1.wav, 0, 0.75, 1, 200, 400 ; * Shivan ship1 flyby player sound (3d sound)
$Shivan: 1 S_flyby2.wav, 0, 0.75, 1, 200, 400 ; * Shivan ship1 flyby player sound (3d sound)

#Flyby Sounds End
</pre>

Line starts with ''$SPECIES:'' and has seven entries separated by commas except for the first and second entries.

**'''First''' value is the label of the flyby sound, usually 0 for the first (small-ship) entry and 1 for the second (large-ship)entry. ('''Integer''')
**'''Second''' value is the name of actual sound file ('''String''', filename).
**'''Third''' value sets the file to always preloaded before the mission ('''Integer''', 0 or 1)
**'''Fourth''' value defines the playing volume of the sound in percentages ('''Float''', from 0 to 1)
**'''Fifth''' value sets the sound type and should be set to 3D stereo sound (type '1') ('''Integer''', 0, 1 or 2)
***'''Sixth''' value defines the distance from the origin of 3D sound where it begins to attenuate (type 0)('''Integer''')
***'''Seventh''' value sets the distance from the origin of the 3D sound where it is inaudible (type 0)('''Integer''')

'''Section ends with #Flyby Sounds End'''

==Sample==
*Retail FreeSpace 2 table

<pre>
;
; sounds.tbl *
;
; file to specify general game sounds
;
; I M P O R T A N T
; **********************************************************
; * *
; ====> DO NOT MODIFY THE ORDER OF THE LISTED SOUNDS <====*
; * *
; **********************************************************
; I M P O R T A N T
;
; If a sound entry appears in this file, there is a hook into the game to
; play the sound. This file can only be modified to change *existing* sounds.
; Talk to a programmer if you want to add brand new sounds. Adding a line to
; this file will not make your sound appear in the game, it will more than
; likely break something.
;
; If you don't want the sound to play, put none.wav as the sound to play.
;
; The fields for a sound entry are:
; 1) unqiue sound signature
; 2) filename of the sound
; 3) flag to indicate sound should always be pre-loaded before a mission
; 4) the default volume (from 0.0 -> 1.0)
; 5) 0 - not 3d 1 - stereo 3D 2 - Aureal A3D (if available), otherwise use stereo 3D
; 6) distance at which sound starts to attenuate (for 3d sounds only)
; 7) distance at which sound is inaudible (for 3d sounds only)
;
#Game Sounds Start
; Misc sounds section ** = Aureal 3d support | * = FS = 3D support
$Name: 0 trk-loop.wav, 0, 0.40, 0 ; Missle tracking to acquire a lock (looped)
$Name: 1 lock.wav, 0, 0.40, 0 ; Missle lock (non-looping)
$Name: 2 cycle.wav, 0, 0.60, 0 ; cycle primary weapon
$Name: 3 cycle.wav, 0, 0.60, 0 ; cycle secondary weapon
$Name: 4 ship_p.wav, 0, 0.30, 0 ; engine sound (as heard in cockpit)
$Name: 5 reveal.wav, 0, 0.40, 0 ; cargo revealed
$Name: 6 breakup.wav, 0, 0.60, 1, 100, 800 ; ship death roll (3d sound)
$Name: 7 boom_3.wav, 0, 0.90, 2, 600, 1200 ; * ship explosion 1 (3d sound)
$Name: 8 beep_2.wav, 0, 0.40, 0 ; target acquried
$Name: 9 switch_1.wav, 0, 0.50, 0 ; energy level change success
$Name: 10 beep_5.wav, 0, 0.50, 0 ; energy level change fail
$Name: 11 switch_2.wav, 0, 0.50, 0 ; energy transfer success
$Name: 12 beep_5.wav, 0, 0.50, 0 ; energy transfer faile
$Name: 13 thr_full.wav, 0, 0.40, 0 ; set full throttle
$Name: 14 thr_off.wav, 0, 0.40, 0 ; set zero throttle
$Name: 15 thr_up.wav, 0, 0.40, 0 ; set 1/3 or 2/3 throttle (up)
$Name: 16 thr_dwn.wav, 0, 0.40, 0 ; set 1/3 or 2/3 throttle (down)
$Name: 17 approach.wav, 0, 0.60, 1, 10, 800 ; dock approach retros (3d sound)
$Name: 18 attach.wav, 0, 0.60, 1, 10, 800 ; dock attach (3d sound)
$Name: 19 detach.wav, 0, 0.60, 1, 10, 800 ; dock detach (3d sound)
$Name: 20 depart.wav, 0, 0.60, 1, 10, 800 ; dock depart retros (3d sound)
$Name: 21 aburn_1.wav, 0, 0.70, 0 ; afterburner engage (3d sound)
$Name: 22 aburn_2.wav, 0, 0.90, 0 ; afterburner burn sound (looped)
$Name: 23 vaporize2.wav, 0, 0.90, 0 ; Destroyed by a beam (vaporized)
$Name: 24 aburn_1f.wav, 0, 0.50, 0 ; afterburner fail (no fuel when aburn pressed)
$Name: 25 alert_2.wav, 0, 0.40, 0 ; heat-seeker launch warning
$Name: 26 m_fail.wav, 0, 0.60, 0 ; tried to fire a missle when none are left
$Name: 27 l_fail.wav, 0, 0.60, 0 ; tried to fire lasers when not enough energy left
$Name: 28 fail.wav, 0, 0.50, 0 ; target fail sound (i.e. press targeting key, but nothing happens)
$Name: 29 beep_1.wav, 0, 0.50, 0 ; squadmate message menu appears
$Name: 30 beep_1.wav, 0, 0.50, 0 ; squadmate message menu disappears
$Name: 31 debris.wav, 0, 0.40, 2, 100, 300 ; ** debris sound (persistant, looping) (3d sound)
$Name: 32 subhit.wav, 0, 0.60, 0 ; subsystem gets destroyed on player ship
$Name: 33 m_load.wav, 0, 0.60, 1, 10, 50 ; missle start load (during rearm/repair) (3d sound)
$Name: 34 m_lock.wav, 0, 0.50, 1, 10, 50 ; missle load (during rearm/repair) (3d sound)
$Name: 35 repair.wav, 0, 0.50, 0 ; ship is being repaired (during rearm/repair) (looped)
$Name: 36 l_hit.wav, 0, 0.90, 0, 30, 100 ; * player ship is hit by laser fire (3d sound)
$Name: 37 m_hit.wav, 0, 0.90, 0, 30, 100 ; * player ship is hit by missile (3d sound)
$Name: 38 cycle.wav, 0, 0.80, 0 ; countermeasure cycle
$Name: 39 s_hit_4.wav, 0, 0.60, 1, 200, 600 ; * shield hit (3d sound)
$Name: 40 s_hit_2.wav, 0, 0.80, 1, 10, 100 ; * player shield is hit (3d sound)
$Name: 41 select.wav, 0, 0.60, 0 ; mouse click
$Name: 42 alert_3.wav, 0, 0.60, 0 ; aspect launch warning
$Name: 43 beep_4.wav, 0, 0.60, 0 ; shield quadrant transfer successful
$Name: 44 wash.wav, 0, 0.80, 1, 200, 400 ; Engine wash looping sound
$Name: 45 warp_1.wav, 0, 0.60, 2, 750, 1500 ; ** warp hole opening up for arriving (3d sound)
$Name: 46 warp_1.wav, 0, 0.60, 2, 750, 1500 ; ** warp hole opening up for departing (3d sound)
$Name: 47 aburn_1f.wav, 0, 0.50, 0 ; player warp has failed
$Name: 48 static.wav, 0, 0.60, 0 ; hud gauge static
$Name: 49 boom_1.wav, 0, 0.90, 1, 600, 1200 ; * ship explosion 2 (3d sound)
$Name: 50 rev1.wav, 0, 0.70, 0 ; ship is warping out in 3rd person
$Name: 51 s_hit_0.wav, 0, 0.70, 1, 100, 200 ; * heavy ship-ship collide sound (3d sound)
$Name: 52 collide.wav, 0, 0.70, 1, 100, 200 ; * light ship-ship collide sound (3d sound)
$Name: 53 s_hit_1.wav, 0, 0.70, 1, 100, 200 ; * shield ship-ship collide overlay sound (3d sound)
$Name: 54 alert_1.wav, 0, 0.50, 0 ; missile threat indicator flashes
$Name: 55 proximity1.wav, 0, 0.70, 0 ; proximity warning (heat seeker)
$Name: 56 proximity2.wav, 0, 0.70, 0 ; proximity warning (aspect)
$Name: 57 directive.wav, 0, 0.70, 0 ; directive complete
$Name: 58 subhit2.wav, 0, 0.90, 1, 250, 800 ; * other ship subsystem destroyed (3d sound)
$Name: 59 atomic.wav, 0, 0.90, 1, 2000, 4000 ; * captial ship explosion (3d sound)
$Name: 60 subhit2.wav, 0, 0.90, 1, 250, 1500 ; * captial ship subsystem destroyed (3d sound)
$Name: 61 warp2.wav, 0, 1.00, 1, 1500, 2000 ; [obsolete] large ship warps out (looping 3d sound)
$Name: 62 ast_lghit.wav, 0, 0.80, 1, 750, 1500 ; ** large asteroid blows up (3d sound)
$Name: 63 ast_smhit.wav, 0, 0.80, 1, 500, 1000 ; ** small asteroid blows up (3d sound)
$Name: 64 cue_voice.wav, 0, 0.90, 0 ; sound to indicate voice is about to start
$Name: 65 end_voice.wav, 0, 0.90, 0 ; sound to indicate voice has ended
$Name: 66 scan.wav, 0, 0.50, 0 ; cargo scanning (looping)
$Name: 67 l_flyby.wav, 0, 0.80, 1, 50, 250 ; * weapon flyby sound
$Name: 68 asteroid.wav, 0, 0.50, 1, 200, 700 ; [obsolete] asteroid sound (persistant, looping) (3d sound)
$Name: 69 warp_open.wav, 0, 1.00, 2, 2000, 4000 ; capital warp hole opening (3d sound)
$Name: 70 warp_close.wav, 0, 1.00, 2, 2000, 4000 ; capital warp hole closing (3d sound)
$Name: 71 rumble.wav, 0, 0.70, 1, 600, 1000 ; LARGE engine ambient
$Name: 72 subspace_left.wav, 0, 0.30, 0 ; subspace ambient sound (left channel) (looping)
$Name: 73 subspace_right.wav, 0, 0.30, 0 ; subspace ambient sound (right channel) (looping)
$Name: 74 Evaded.wav, 0, 0.70, 0 ; "evaded" HUD popup
$Name: 75 rumble.wav, 0, 0.70, 1, 600, 1000 ; HUGE engine ambient
;
; Weapons section
;
$Name: 76 L_Sidearm.wav, 0, 0.50, 1, 50, 400 ; SD-4 Sidearm laser fired
$Name: 77 L_Scalpel.wav, 0, 0.50, 1, 50, 400 ; DR-2 Scalpel fired
$Name: 78 L_Flail2.wav, 0, 0.50, 1, 50, 400 ; Flail II fired
$Name: 79 L_Prom_R.wav, 0, 0.50, 1, 50, 400 ; Prometheus R laser fired
$Name: 80 L_Prom_S.wav, 0, 0.50, 1, 50, 400 ; Prometheus S laser fired
$Name: 81 L_Newton.wav, 0, 0.50, 1, 50, 400 ; GTW-66 Newton Cannon fired
$Name: 82 L_Kayser.wav, 0, 0.55, 1, 50, 400 ; UD-8 Kayser Laser fired
$Name: 83 L_Circle.wav, 0, 0.50, 1, 50, 400 ; GTW-19 Circe laser fired
$Name: 84 L_Lich.wav, 0, 0.50, 1, 50, 400 ; GTW-83 Lich laser fired
$Name: 85 hit_1.wav, 0, 0.90, 1, 200, 800 ; Laser impact
$Name: 86 L_Vasmid.wav, 0, 0.50, 1, 50, 400 ; Subach-HLV Vasudan laser
$Name: 87 m_wasp.wav, 0, 0.80, 1, 50, 400 ; rockeye missile launch
$Name: 88 boom_2.wav, 0, 0.80, 1, 500, 1000 ; missile impact 1
$Name: 89 m_mag.wav, 0, 0.80, 1, 50, 400 ; mag pulse missile launch
$Name: 90 m_fury.wav, 0, 0.80, 1, 50, 400 ; fury missile launch
$Name: 91 m_shrike.wav, 0, 0.80, 1, 50, 400 ; shrike missile launch
$Name: 92 m_angel.wav, 0, 0.80, 1, 50, 400 ; angel fire missile launch
$Name: 93 m_cluster.wav, 0, 0.80, 1, 50, 400 ; cluster bomb launch
$Name: 94 m_clusterb.wav, 0, 0.80, 1, 50, 400 ; cluster baby bomb launch
$Name: 95 m_stiletto.wav, 0, 0.80, 1, 50, 400 ; stiletto bomb launch
$Name: 96 m_tsunami.wav, 0, 0.80, 1, 50, 400 ; tsunami bomb launch
$Name: 97 m_harbinger.wav, 0, 0.80, 1, 50, 400 ; harbinger bomb launch
$Name: 98 m_mega.wav, 0, 0.80, 1, 50, 400 ; mega wokka launch
$Name: 99 counter_1.wav, 0, 0.70, 1, 50, 200 ; countermeasure 1 launch
$Name: 100 l_alien1.wav, 0, 0.60, 1, 50, 400 ; Shivan light laser (3d sound)
$Name: 101 clusterboom.wav, 0, 0.80, 1, 750, 2000 ; shockwave ignition (3d sound)
$Name: 102 m_swarm.wav, 0, 0.70, 1, 50, 400 ; swarm missile sound (3d sound)
$Name: 103 l_alien2.wav, 0, 0.60, 1, 100, 400 ; Shivan heavy laser (3d sound)
$Name: 104 capital4.wav, 0, 0.70, 1, 500, 1500 ; Vasudan SuperCap engine (3d sound)
$Name: 105 capital5.wav, 0, 0.70, 1, 500, 1500 ; Shivan SuperCap engine (3d sound)
$Name: 106 capital6.wav, 0, 0.70, 1, 500, 1500 ; Terran SuperCap engine (3d sound)
$Name: 107 l_vaslight.wav, 0, 0.60, 1, 50, 400 ; Vasudan light laser fired (3d sound)
$Name: 108 l_alien3.wav, 0, 0.60, 1, 50, 400 ; Shivan heavy laser (3d sound)
$Name: 109 shockwave.wav, 0, 1.00, 1, 50, 800 ; ** shockwave impact (3d sound)
$Name: 110 Turret_T1.wav, 0, 0.50, 2, 200, 1000 ; TERRAN TURRET 1
$Name: 111 Turret_T2.wav, 0, 0.50, 2, 200, 1000 ; TERRAN TURRET 2
$Name: 112 Turret_V1.wav, 0, 0.50, 2, 200, 1000 ; VASUDAN TURRET 1
$Name: 113 Turret_V2.wav, 0, 0.50, 2, 200, 1000 ; VASUDAN TURRET 2
$Name: 114 Turret_S1.wav, 0, 0.50, 2, 200, 1000 ; SHIVAN TURRET 1
$Name: 115 paintloop.wav, 0, 0.60, 1, 50, 200 ; targeting laser loop sound
$Name: 116 FlakLaunch.wav, 0, 0.60, 1, 250, 1000 ; Flak Gun Launch
$Name: 117 boom_4.wav, 0, 0.80, 1, 400, 800 ; Flak Gun Impact
$Name: 118 m_emp.wav, 0, 0.60, 1, 50, 400 ; EMP Missle
$Name: 119 Escape.wav, 0, 0.60, 1, 200, 600 ; Escape Pod Drone
$Name: 120 Vaporize1.wav, 0, 0.70, 0 ; Beam Hit 1
$Name: 121 beam_loop.wav, 0, 0.70, 2, 1500, 3000 ; beam loop
$Name: 122 beam_up.wav, 0, 0.70, 2, 1500, 3000 ; beam power up
$Name: 123 beam_down.wav, 0, 0.70, 2, 1500, 3000 ; beam power down
$Name: 124 beam_shot1.wav, 0, 0.70, 2, 1500, 2500 ; Beam shot 1
$Name: 125 beam_shot2.wav, 0, 0.70, 2, 1500, 2500 ; Beam shot 2
;Ship Engine Sounds section
$Name: 126 ship_a1.wav, 0, 0.60, 1, 200, 400 ; Terran fighter engine (3d sound)
$Name: 127 ship_a2.wav, 0, 0.70, 1, 300, 600 ; Terran bomber engine (3d sound)
$Name: 128 ship_a3.wav, 0, 0.80, 1, 400, 800 ; Terran cruiser engine (3d sound)
$Name: 129 ship_b1.wav, 0, 0.70, 1, 200, 400 ; Vasudan fighter engine (3d sound)
$Name: 130 ship_b2.wav, 0, 0.80, 1, 300, 600 ; Vasudan bomber engine (3d sound)
$Name: 131 ship_b3.wav, 0, 0.80, 1, 400, 800 ; Vasudan cruiser engine (3d sound)
$Name: 132 ship_c1.wav, 0, 0.60, 1, 200, 400 ; Shivan fighter engine (3d sound)
$Name: 133 ship_c2.wav, 0, 0.70, 1, 300, 600 ; Shivan bomber engine (3d sound)
$Name: 134 ship_c3.wav, 0, 0.80, 1, 400, 800 ; Shivan cruiser engine (3d sound)
$Name: 135 beacon.wav, 0, 0.60, 1, 300, 600 ; Repair ship beacon/engine sound (3d sound)
$Name: 136 capital1.wav, 0, 0.70, 1, 500, 1500 ; Terran capital engine (3d sound)
$Name: 137 capital2.wav, 0, 0.70, 1, 500, 1500 ; Vasudan capital engine (3d sound)
$Name: 138 capital3.wav, 0, 0.70, 1, 500, 1500 ; Shivan capital engine (3d sound)
; Electrical arc sound fx on the debris pieces
$Name: 139 Arc_01.wav, 0, 0.30, 2, 200, 500 ; ** 0.10 second spark sound effect (3d sound)
$Name: 140 Arc_02.wav, 0, 0.30, 2, 200, 500 ; ** 0.25 second spark sound effect (3d sound)
$Name: 141 Arc_03.wav, 0, 0.30, 2, 200, 500 ; ** 0.50 second spark sound effect (3d sound)
$Name: 142 Arc_04.wav, 0, 0.30, 2, 200, 500 ; ** 0.75 second spark sound effect (3d sound)
$Name: 143 Arc_05.wav, 0, 0.30, 2, 200, 500 ; ** 1.00 second spark sound effect (3d sound)
; Beam Sounds
$Name: 144 BT_LTerSlash.wav, 0, 0.70, 2, 1500, 3000 ; LTerSlash beam loop
$Name: 145 BT_TerSlash.wav, 0, 0.70, 2, 1500, 3000 ; TerSlash beam loop
$Name: 146 BT_SGreen.wav, 0, 0.70, 2, 1500, 3000 ; SGreen beam loop
$Name: 147 BT_BGreen.wav, 0, 0.70, 2, 1500, 3000 ; BGreen beem loop
$Name: 148 BT_BFGreen.wav, 0, 0.70, 2, 1500, 3000 ; BFGreen been loop
$Name: 149 BT_AntiFtr.wav, 0, 0.70, 2, 1500, 3000 ; Antifighter beam loop
$Name: 150 BT_up_1.wav, 0, 0.60, 2, 1500, 3000 ; 1 sec warm up
$Name: 151 BT_up_1.5.wav, 0, 0.60, 2, 1500, 3000 ; 1.5 sec warm up
$Name: 152 BT_up_2.5.wav, 0, 0.60, 2, 1500, 3000 ; 2.5 sec warm up
$Name: 153 BT_up_3.wav, 0, 0.60, 2, 1500, 3000 ; 3 sec warm up
$Name: 154 BT_up_3.5.wav, 0, 0.60, 2, 1500, 3000 ; 3.5 sec warm up
$Name: 155 BT_up_5.wav, 0, 0.60, 2, 1500, 3000 ; 5 sec warm up
$Name: 156 BT_dwn_1.wav, 0, 0.70, 2, 2000, 3000 ; LTerSlash warm down
$Name: 157 BT_dwn_2.wav, 0, 0.70, 2, 2000, 3000 ; TerSlash warm down
$Name: 158 BT_dwn_3.wav, 0, 0.70, 2, 2000, 3000 ; SGreen warm down
$Name: 159 BT_dwn_4.wav, 0, 0.70, 2, 2000, 3000 ; BGreen warm down
$Name: 160 BT_dwn_5.wav, 0, 0.70, 2, 2000, 3000 ; BFGreen warm down
$Name: 161 BT_dwn_6.wav, 0, 0.70, 2, 2000, 3000 ; T_AntiFtr warm down
$Name: 162 Empty, 0, 0.50, 0
$Name: 163 Empty, 0, 0.50, 0
$Name: 164 Empty, 0, 0.50, 0
$Name: 165 Empty, 0, 0.50, 0
$Name: 166 Empty, 0, 0.50, 0
$Name: 167 Empty, 0, 0.50, 0
$Name: 168 Empty, 0, 0.50, 0
$Name: 169 Empty, 0, 0.50, 0
$Name: 170 Empty, 0, 0.50, 0
$Name: 171 Empty, 0, 0.50, 0
$Name: 172 Empty, 0, 0.50, 0
$Name: 173 SupNova1.wav, 0, 1.00, 0 ; SuperNova (distant)
$Name: 174 SupNova2.wav, 0, 1.00, 0 ; SuperNova (shockwave)
$Name: 175 ship_c4.wav, 0, 0.80, 1, 400, 800 ; Shivan large engine (3d sound)
$Name: 176 ship_c5.wav, 0, 0.80, 1, 400, 1000 ; Shivan large engine (3d sound)
$Name: 177 BS_SRed.wav, 0, 0.70, 2, 1500, 3000 ; SRed beam loop
$Name: 178 BS_LRed.wav, 0, 0.70, 2, 1500, 3000 ; LRed beam loop
$Name: 179 BS_AntiFtr.wav, 0, 0.70, 2, 1500, 3000 ; Antifighter beam loop
$Name: 180 Thunder_01.wav, 0, 0.70, 0 ; Thunder 1 sound in neblua
$Name: 181 Thunder_02.wav, 0, 0.70, 0 ; Thunder 2 sound in neblua
$Name: 182 BS_up_1.wav, 0, 0.60, 2, 1500, 3000 ; 1 sec warm up
$Name: 183 BS_up_1.5.wav, 0, 0.60, 2, 1500, 3000 ; 1.5 sec warm up
$Name: 184 BS_up_3.wav, 0, 0.60, 2, 1500, 3000 ; 3 sec warm up
$Name: 185 Commnode.wav, 0, 0.60, 1, 200, 500 ; Shivan Commnode
$Name: 186 Pirate.wav, 0, 0.60, 1, 400, 1000 ; Volition PirateShip
$Name: 187 BS_dwn_1.wav, 0, 0.70, 2, 2000, 3000 ; SRed warm down
$Name: 188 BS_dwn_2.wav, 0, 0.70, 2, 2000, 3000 ; LRed warm down
$Name: 189 BS_dwn_3.wav, 0, 0.70, 2, 2000, 3000 ; AntiFtr warm down
$Name: 190 Inst1.wav, 0, 0.80, 1, 500, 2000 ; Instellation 1
$Name: 191 Inst2.wav, 0, 0.80, 1, 500, 2000 ; Instellation 2

;SCP ADDED SOUNDS START HERE
$Name: 200 m_load.wav, 0, 0.60, 1, 10, 50 ; Ballistic Weapon Rearm Start
$Name: 201 m_lock.wav, 0, 0.50, 1, 10, 50 ; Ballistic Weapon Rearm
;
#Game Sounds End
;
#Interface Sounds Start
$Name: 0 user_c.wav, 0, 0.70, 0 ; mouse click
$Name: 1 empty, 0, 0.70, 0 ; pick up a ship icon (not used)
$Name: 2 load01.wav, 0, 0.60, 0 ; drop a ship icon on a wing slot
$Name: 3 unload01.wav, 0, 0.60, 0 ; drop a ship icon back to the list
$Name: 4 beep_4.wav, 0, 0.70, 0 ; press briefing, ship selection or weapons bar (top-left)
$Name: 5 user_c.wav, 0, 0.70, 0 ; Switching to a new screen, but not commit
$Name: 6 beep_4.wav, 0, 0.70, 0 ; help pressed
$Name: 7 commit.wav, 0, 0.60, 0 ; commit pressed
$Name: 8 user_c.wav, 0, 0.70, 0 ; prev/next pressed
$Name: 9 user_c.wav, 0, 0.70, 0 ; scroll pressed (and scroll)
$Name: 10 fail.wav, 0, 0.70, 0 ; general failure sound for any event
$Name: 11 shipview.wav, 0, 0.50, 0 ; ship animation starts (ie text and ship first appear)
$Name: 12 main_amb.wav, 0, 0.60, 0 ; ambient sound for the Terran main hall (looping)
$Name: 13 vas_amb.wav, 0, 0.60, 0 ; ambient sound for the Vasudan main hall (looping)
$Name: 14 user_a.wav, 0, 0.70, 0 ; brief stage change
$Name: 15 user_i.wav, 0, 0.70, 0 ; brief stage change fail
$Name: 16 beep_3.wav, 0, 0.70, 0 ; selet brief icon
$Name: 17 user_o.wav, 0, 0.50, 0 ; user_over (mouse over a control)
$Name: 18 user_c.wav, 0, 0.70, 0 ; user_click (mouse selects a control)
$Name: 19 reset.wav, 0, 0.70, 0 ; reset (or similar button) pressed
$Name: 20 textdraw.wav, 0, 0.60, 0 ; briefing text wipe
$Name: 21 Lift_Mix.wav, 0, 0.50, 0 ; main hall - elevator
$Name: 22 weapview.wav, 0, 0.60, 0 ; weapon animation starts
$Name: 23 dooropen.wav, 0, 0.50, 0 ; door in main hall opens
$Name: 24 doorclose.wav, 0, 0.50, 0 ; door in main hall closes
$Name: 25 itemdraw.wav, 0, 0.50, 0 ; glow in main hall opens
$Name: 26 Crane_1.wav, 0, 0.50, 0 ; main hall - crane 1
$Name: 27 sub_amb.wav, 0, 0.60, 0 ; ambient sound for menus off the main hall (looping)
$Name: 28 user_c.wav, 0, 0.70, 0 ; popup dialog box appeared
$Name: 29 user_c.wav, 0, 0.70, 0 ; popup dialog box goes away
$Name: 30 1_yes.wav, 0, 1.00, 0 ; voice clip played when volume slider changes
$Name: 31 Crane_2.wav, 0, 0.50, 0 ; main hall - crane 2
$Name: 32 Option1.wav, 0, 0.70, 0 ; main hall options - mouse on
$Name: 33 Option2.wav, 0, 0.70, 0 ; main hall options - mouse off
$Name: 34 Techroom1.wav, 0, 0.70, 0 ; main hall tech room - mouse on
$Name: 35 Techroom2.wav, 0, 0.70, 0 ; main hall tech room - mouse off
$Name: 36 Exitopen.wav, 0, 0.60, 0 ; main hall exit open
$Name: 37 Exitclose.wav, 0, 0.60, 0 ; main hall exit close
$Name: 38 pa_1.wav, 0, 0.50, 0 ; main hall random intercom 1
$Name: 39 pa_2.wav, 0, 0.50, 0 ; main hall random intercom 2
$Name: 40 pa_3.wav, 0, 0.50, 0 ; main hall random intercom 3
$Name: 41 highlight.wav, 0, 0.40, 0 ; spinning highlight in briefing
$Name: 42 noiz.wav, 0, 0.40, 0 ; static in a briefing stage cut
$Name: 43 Camp_on.wav, 0, 0.70, 0 ; main hall campaign - mouse on
$Name: 44 Camp_off.wav, 0, 0.70, 0 ; main hall campaign - mouse off
$Name: 45 V_Hatch_Open.wav, 0, 0.70, 0 ; vasudan hall - exit open
$Name: 46 V_Hatch_Close.wav, 0, 0.70, 0 ; vasudan hall - exit close
$Name: 47 V_Roll_Open.wav, 0, 0.80, 0 ; vasudan hall - hatch open
$Name: 48 V_Roll_Close.wav, 0, 0.80, 0 ; vasudan hall - hatch close
$Name: 49 V_Lift_Up.wav, 0, 0.70, 0 ; vasudan hall - lift up
$Name: 50 V_Lift_Down.wav, 0, 0.70, 0 ; vasudan hall - lift down
$Name: 51 V_Lite_On.wav, 0, 0.70, 0 ; vasudan hall - glow on
$Name: 52 V_Lite_Off.wav, 0, 0.70, 0 ; vasudan hall - glow off
$Name: 53 Skiff.wav, 0, 0.70, 0 ; vasudan hall - skiff loop
$Name: 54 V_Map_On.wav, 0, 0.70, 0 ; vasudan hall - screen on
$Name: 55 V_Map_Off.wav, 0, 0.70, 0 ; vasudan hall - screen off
$Name: 56 V_Head_1.wav, 0, 0.70, 0 ; vasudan hall - vasudan greeting
$Name: 57 V_Head_2.wav, 0, 0.70, 0 ; vasudan hall - vasudan bye
$Name: 58 V_Pa_01.wav, 0, 0.70, 0 ; vasudan hall - vasudan pa 1
$Name: 59 V_Pa_02.wav, 0, 0.70, 0 ; vasudan hall - vasudan pa 2
$Name: 60 V_Pa_03.wav, 0, 0.70, 0 ; vasudan hall - vasudan pa 3
$Name: 61 bup.wav, 0, 0.90, 0 ; bup bup bup-bup bup bup
$Name: 62 thankyou.wav, 0, 0.90, 0 ; thankyou
$Name: 63 V_Exit_Open.wav, 0, 0.70, 0 ; vasudan hall - exit open
$Name: 64 V_Exit_Close.wav, 0, 0.70, 0 ; vasudan hall - exit close
;
#Interface Sounds End
;
; Each species can have up to 4 different flyby sounds
; NOTE : the parse code expects to see exactly 2 sounds for terran, then 2 for vasudan, then 2 for shivan
; the first sound for each species is the fighter/small flyby sound. the second is the bomber/big flyby sound
#Flyby Sounds Start

$Terran: 0 T_flyby1.wav, 0, 0.75, 1, 200, 400 ; * Terran ship1 flyby player sound (3d sound)
$Terran: 1 T_flyby2.wav, 0, 0.75, 1, 200, 400 ; * Terran ship1 flyby player sound (3d sound)

$Vasudan: 0 V_flyby1.wav, 0, 0.85, 1, 200, 400 ; * Vasudan ship1 flyby player sound (3d sound)
$Vasudan: 1 V_flyby2.wav, 0, 0.85, 1, 200, 400 ; * Vasudan ship1 flyby player sound (3d sound)

$Shivan: 0 S_flyby1.wav, 0, 0.75, 1, 200, 400 ; * SHIVAN ship1 flyby player sound (3d sound)
$Shivan: 1 S_flyby2.wav, 0, 0.75, 1, 200, 400 ; * SHIVAN ship1 flyby player sound (3d sound)

#Flyby Sounds End
</pre>

[[Category:Tables]]

Modular Tables

2019-01-29T05:45:32Z

AdmiralRalwood: /* Supported Modular Tables */ making a note of sounds.tbl's peculiarities with +nocreate

'''Modular tables''' are an SCP addition to the standard FreeSpace table system. Each modular table (.tbm extension) adds or modifies data from its related base table (.tbl extension). So there's no more need to edit the 'parent' table. A modular table file is not restricted to one entry.

The base table each modular table modifies depends on the ending three letters of its name. See [[Modular Tables#Supported Modular Tables|the list of supported modular tables]] below.

[[Tables|List of Tables]]

==Important Notes==
===Loading Order===
* Modular table files should use the 'parent table' sections. They should also keep their entry order.
* Completely new entries and also complete rewrites of entries in parent table file are always possible.
* '''Loading order:'''
** The base table (.tbl) is loaded first despite its location priority, (see [[Command-Line_Reference#-mod|-mod flag help]] for more info about priority places). Of course, if there are several versions of the same base table in several vps or /data/tables folders, only the highest priority one will be loaded.
** Then, ALL its related tbms are loaded, even if they are in a lower priority place than the base tbl table. I.e, '''tbms are always applied'''. If there are several versions of the same file you can imagine what happens.
** When they are loaded, tbms start being applied in reverse priority order; ie, tbms are applied from the lowest priority place to the highest priority place.
** The former rule makes that, if there are conflictive entries in several tables, '''the highest priority ones will override the rest''' because they will be the last applied changes. '''EXTREMELY IMPORTANT NOTE:''' Because of an already solved bug, '''fs_open versions till 3.6.9. (included)''' apply tbms in direct priority order, from the highest priority to the lowest one. In this way, '''the lowest priority entries override the rest'''. As example, this issue makes impossible overriding mediavps tbm settings from any tbm inside a main mod which uses this art enhancement as a secondary mod. The only way you have is overriding the whole table as explained below. It is not recommended to have multiple tbms inside the same priority location (vp or /data/tables folder) that contain conflicting entries. While it is possible to do so anyway, and the order is deterministic (files are loaded in reverse-alphabetical order), this is a pretty strange mod design: why should you put conflicting versions of any class of modular table in the same location? Just edit and merge them, deleting undesired entries. 
** Derived from priority and tbm handling, the only two ways to override the settings of AnExistingTable-xxx.tbm are:
*** Adding another AnExistingTable-xxx.tbm in a higher priority place so it gets loaded instead of the original version.
*** Overriding every single AnExistingTable-xxx.tbm entry, using one or several other -xxx.tbm tables located in higher priority places.

===Numerical Limit===
Before r11156, there was a hardcoded limit for the number of tbms of a given type that Freespace Open would recognize; the first 32 files detected by a call to parse_modular_table() were the only ones loaded. This manifested as data simply not being read by the game, and could result in the loss of, for example, ships or weapons when new ones were added. This occurred in reverse alphabetical order. In order to get around this, one had to consolidate their tbms into fewer files; now, FSO should recognize any number of files, and this should no longer be necessary.

==eXtendable Modular Tables==
In addition, some modular tables are XMTs (or eXtentable Modular Tables). They offer capability to add new partial entries or make partial editing to each entry. Within XMT tbms:
* All fields are optional. But toplevel entries, of course, because you ''do need'' to specify which item you want to modify.
* Toplevel entries can replace part of other existing toplevel entries. Only changed parameters should be specified.
* Addition of the '''+nocreate''' parameter. This parameter should be entered right after entry name and prevents possible creation of partially undefined entry. For example, if the parent table file lacked the entry that was included to the as a partial entry to the modular table file then the creation of partially undefined entry is possible which could cause problems with the game.
**Example:

$Name: @Subach HL-7
+nocreate

==Supported Modular Tables==
The list of supported tbms is:

*[[ai_profiles.tbl]] can be extended with '''xxx-aip.tbm''' (XMT)
*[[armor.tbl]] can be extended with '''xxx-amr.tbm''' (non-XMT)
*[[colors.tbl]] can be extended with '''xxx-clr.tbm''' (non-XMT)
*[[credits.tbl]] can be extended with '''xxx-crd.tbm''' (non-XMT)
*[[fireball.tbl]] can be extended with '''xxx-fbl.tbm''' (non-XMT)
*[[game_settings.tbl]] can be extended with '''xxx-mod.tbm''' (non-XMT)
*[[glowpoints.tbl]] can be extended with '''xxx-gpo.tbm''' (non-XMT... sort of; has '''+nocreate''' but the whole entry must be re-specified, and duplicates are discarded without '''+nocreate''')
*[[help.tbl]] can be extended with '''xxx-hlp.tbm''' (non-XMT)
*[[hud_gauges.tbl]] can be extended with '''xxx-hdg.tbm''' (non-XMT)
*[[mainhall.tbl]] can be extended with '''xxx-hall.tbm''' (non-XMT)
*[[mflash.tbl]] can be extended with '''xxx-mfl.tbm''' (non-XMT)
*[[music.tbl]] can be extended with '''xxx-mus.tbm''' (XMT)
*[[objecttypes.tbl]] can be extended with '''xxx-obt.tbm''' (XMT)
*[[scripting.tbl]] can be extended with '''xxx-sct.tbm''' (non-XMT)
*[[ships.tbl]] can be extended with '''xxx-shp.tbm''' (XMT)
*[[sounds.tbl]] can be extended with '''xxx-snd.tbm''' (XMT, but '''+nocreate''' is required to modify an existing entry)
*[[species_defs.tbl]] can be extended with '''xxx-sdf.tbm''' (XMT)
*[[ssm.tbl]] can be extended with '''xxx-ssm.tbm''' (non-XMT)
*[[stars.tbl]] can be extended with '''xxx-str.tbm''' (non-XMT)
*[[strings.tbl]] can be extended with '''xxx-lcl.tbm''' (non-XMT)
*[[tstrings.tbl]] can be extended with '''xxx-tlc.tbm''' (non-XMT)
*[[weapons.tbl]] can be extended with '''xxx-wep.tbm''' (XMT)
*[[weapon_expl.tbl]] can be extended with '''xxx-wxp.tbm''' (non-XMT)

==Sample - Alpha-wep.tbm==
*Changes the speed of the ''Subach HL-7'' and also adds a faint grey trail to it.
*To create it make a text file using a text editor and save the file as '''''Alpha-wep.tbm''''' with the following contents to the proper folder (.../data/tables).

#Primary Weapons
$Name: @Subach HL-7
+nocreate
$Velocity: 650.0
$Trail:
+Start Width: 0.4
+End Width: 0.0
+Start Alpha: 0.35
+End Alpha: 0.0
+Max Life: 0.2
+Bitmap: Contrail
#End

[[Category:Tables]]

Modular Tables

2019-01-29T05:41:49Z

AdmiralRalwood: /* Supported Modular Tables */ this caveat was added to the wrong file by accident

'''Modular tables''' are an SCP addition to the standard FreeSpace table system. Each modular table (.tbm extension) adds or modifies data from its related base table (.tbl extension). So there's no more need to edit the 'parent' table. A modular table file is not restricted to one entry.

The base table each modular table modifies depends on the ending three letters of its name. See [[Modular Tables#Supported Modular Tables|the list of supported modular tables]] below.

[[Tables|List of Tables]]

==Important Notes==
===Loading Order===
* Modular table files should use the 'parent table' sections. They should also keep their entry order.
* Completely new entries and also complete rewrites of entries in parent table file are always possible.
* '''Loading order:'''
** The base table (.tbl) is loaded first despite its location priority, (see [[Command-Line_Reference#-mod|-mod flag help]] for more info about priority places). Of course, if there are several versions of the same base table in several vps or /data/tables folders, only the highest priority one will be loaded.
** Then, ALL its related tbms are loaded, even if they are in a lower priority place than the base tbl table. I.e, '''tbms are always applied'''. If there are several versions of the same file you can imagine what happens.
** When they are loaded, tbms start being applied in reverse priority order; ie, tbms are applied from the lowest priority place to the highest priority place.
** The former rule makes that, if there are conflictive entries in several tables, '''the highest priority ones will override the rest''' because they will be the last applied changes. '''EXTREMELY IMPORTANT NOTE:''' Because of an already solved bug, '''fs_open versions till 3.6.9. (included)''' apply tbms in direct priority order, from the highest priority to the lowest one. In this way, '''the lowest priority entries override the rest'''. As example, this issue makes impossible overriding mediavps tbm settings from any tbm inside a main mod which uses this art enhancement as a secondary mod. The only way you have is overriding the whole table as explained below. It is not recommended to have multiple tbms inside the same priority location (vp or /data/tables folder) that contain conflicting entries. While it is possible to do so anyway, and the order is deterministic (files are loaded in reverse-alphabetical order), this is a pretty strange mod design: why should you put conflicting versions of any class of modular table in the same location? Just edit and merge them, deleting undesired entries. 
** Derived from priority and tbm handling, the only two ways to override the settings of AnExistingTable-xxx.tbm are:
*** Adding another AnExistingTable-xxx.tbm in a higher priority place so it gets loaded instead of the original version.
*** Overriding every single AnExistingTable-xxx.tbm entry, using one or several other -xxx.tbm tables located in higher priority places.

===Numerical Limit===
Before r11156, there was a hardcoded limit for the number of tbms of a given type that Freespace Open would recognize; the first 32 files detected by a call to parse_modular_table() were the only ones loaded. This manifested as data simply not being read by the game, and could result in the loss of, for example, ships or weapons when new ones were added. This occurred in reverse alphabetical order. In order to get around this, one had to consolidate their tbms into fewer files; now, FSO should recognize any number of files, and this should no longer be necessary.

==eXtendable Modular Tables==
In addition, some modular tables are XMTs (or eXtentable Modular Tables). They offer capability to add new partial entries or make partial editing to each entry. Within XMT tbms:
* All fields are optional. But toplevel entries, of course, because you ''do need'' to specify which item you want to modify.
* Toplevel entries can replace part of other existing toplevel entries. Only changed parameters should be specified.
* Addition of the '''+nocreate''' parameter. This parameter should be entered right after entry name and prevents possible creation of partially undefined entry. For example, if the parent table file lacked the entry that was included to the as a partial entry to the modular table file then the creation of partially undefined entry is possible which could cause problems with the game.
**Example:

$Name: @Subach HL-7
+nocreate

==Supported Modular Tables==
The list of supported tbms is:

*[[ai_profiles.tbl]] can be extended with '''xxx-aip.tbm''' (XMT)
*[[armor.tbl]] can be extended with '''xxx-amr.tbm''' (non-XMT)
*[[colors.tbl]] can be extended with '''xxx-clr.tbm''' (non-XMT)
*[[credits.tbl]] can be extended with '''xxx-crd.tbm''' (non-XMT)
*[[fireball.tbl]] can be extended with '''xxx-fbl.tbm''' (non-XMT)
*[[game_settings.tbl]] can be extended with '''xxx-mod.tbm''' (non-XMT)
*[[glowpoints.tbl]] can be extended with '''xxx-gpo.tbm''' (non-XMT... sort of; has '''+nocreate''' but the whole entry must be re-specified, and duplicates are discarded without '''+nocreate''')
*[[help.tbl]] can be extended with '''xxx-hlp.tbm''' (non-XMT)
*[[hud_gauges.tbl]] can be extended with '''xxx-hdg.tbm''' (non-XMT)
*[[mainhall.tbl]] can be extended with '''xxx-hall.tbm''' (non-XMT)
*[[mflash.tbl]] can be extended with '''xxx-mfl.tbm''' (non-XMT)
*[[music.tbl]] can be extended with '''xxx-mus.tbm''' (XMT)
*[[objecttypes.tbl]] can be extended with '''xxx-obt.tbm''' (XMT)
*[[scripting.tbl]] can be extended with '''xxx-sct.tbm''' (non-XMT)
*[[ships.tbl]] can be extended with '''xxx-shp.tbm''' (XMT)
*[[sounds.tbl]] can be extended with '''xxx-snd.tbm''' (XMT)
*[[species_defs.tbl]] can be extended with '''xxx-sdf.tbm''' (XMT)
*[[ssm.tbl]] can be extended with '''xxx-ssm.tbm''' (non-XMT)
*[[stars.tbl]] can be extended with '''xxx-str.tbm''' (non-XMT)
*[[strings.tbl]] can be extended with '''xxx-lcl.tbm''' (non-XMT)
*[[tstrings.tbl]] can be extended with '''xxx-tlc.tbm''' (non-XMT)
*[[weapons.tbl]] can be extended with '''xxx-wep.tbm''' (XMT)
*[[weapon_expl.tbl]] can be extended with '''xxx-wxp.tbm''' (non-XMT)

==Sample - Alpha-wep.tbm==
*Changes the speed of the ''Subach HL-7'' and also adds a faint grey trail to it.
*To create it make a text file using a text editor and save the file as '''''Alpha-wep.tbm''''' with the following contents to the proper folder (.../data/tables).

#Primary Weapons
$Name: @Subach HL-7
+nocreate
$Velocity: 650.0
$Trail:
+Start Width: 0.4
+End Width: 0.0
+Start Alpha: 0.35
+End Alpha: 0.0
+Max Life: 0.2
+Bitmap: Contrail
#End

[[Category:Tables]]

PBlue

2019-01-22T22:13:59Z

AdmiralRalwood: give the poor PBlue a wiki article

{{BPArticle}}
The '''''Void Fang'' Pulse Beam''', also known as the '''PBlue''', is an anti-subsystem beam based on the [[AAAf|''Phalanx'' anti-fighter beam]] used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]], and can be found on the [[GTD Erebus|''Erebus''-class destroyer]].

==Description==
===Blue Planet Tech Room Description===
Pulse beams are descendants of anti-fighter beams, using quick-rise capacitors to fire a lance of confined plasma. This design excels at penetrating active armor and turret shielding.

==Performance==
===Statistics===
{{Beam|6 000|15|0.05|Fixed|1|900|60|900}}
*Due to changes in the beam damage code, nightly builds from February 15th, 2018 and onward will do drastically different damage than previous builds, depending on framerate.

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging large vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]
*Weapon can target subsystems on enemy ships, like just like normal weapons [[Weapons.tbl#.22anti-subsystem_beam.22|(anti-subsytem beam)]]
*Weapon has [[Weapons.tbl#Weapon Flags|Puncture]] flag which reduces the damage inflicted to the target's hull.
*Weapon causes targets [[Weapons.tbl#Weapon Flags|electronic]] systems (laser turrets etc.) to malfunction.
*Weapon [[Weapons.tbl#"Esuck"|leeches]] energy from the target with every hit.

===Veteran Comments===
{{Comment|
}}

[[Category:Blue Planet weapons]]

SBlue

2019-01-22T17:40:59Z

AdmiralRalwood: /* Statistics */ It turns out I'm bad at math.

{{BPArticle}}
The '''''Thorn Lance'' Light Beam''', also known as the '''SBlue''', is a light beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. The ''Thorn Lance'' is the lightest beam created by the Alliance as a result of the Threat Exigency Initiative, and two of these beams serve as the primary weapon of the [[GTC Hyperion|GTC ''Hyperion'']]. The ''Thorn Lance''<nowiki></nowiki>'s biggest threat is its effective range, which is over 50% greater than that of the [[LRed]]. Its biggest weakness is its lengthy recharge time of 40 seconds, which is a major drawback to work around when coupled with the relatively small damage output.

==Description==
===Blue Planet Tech Room Description===
The Thorn Lance light beam system, mounted on Hyperion cruisers as their primary direct-fire weapons system, is the weakest of the next-generation beam systems. Nonetheless, it offers marked improvement in firepower over previous light beams, and its draw on the cruiser's systems overall is low. Cool-running, easy to maintain, and reasonably powerful, the Thorn Lance suffers only in that it is mounted on a fragile vessel.

==Performance==
===Statistics===
{{Beam|4 500|40|2.5|Direct|1|1 920|120|4 800}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging large vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

===Veteran Comments===
{{Comment|}}

[[Category:Blue Planet weapons]]

MBlue

2019-01-22T17:40:22Z

AdmiralRalwood: /* Statistics */ It turns out I'm bad at math.

{{BPArticle}}
The '''''Aurora Wake'' Beam System''', also known as the '''MBlue''', is a medium beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. The ''Aurora Wake'' is a high-performance medium beam cannon, and has the distinction of being the first beam weapon developed by the Threat Exigency Initiative that allowed the GTVA to replicate the shock jump tactics employed by the [[Shivans]] during the [[Second Shivan Incursion]]. The ''Aurora Wake'' suffers from a 35-second recharge time and tendency to overheat. However, it makes up for this with its effective range of 6750 metres. The [[GTCv Chimera|GTCv ''Chimera'']] mounts three of these beams as its forward armament.

==Description==
===Blue Planet Tech Room Description===
A powerful mid-range direct-fire beam system, the 'Aurora Wake' was one of the first products of the Threat Exigency Initiative's drive to produce more powerful beam cannons. Mounted on most next-generation Alliance warships as a battery weapon, the 'Aurora Wake' supplements its own dedicated reactors with feeds from the ship's drives. Prone to overheating, this system is perhaps the most cantankerous of the next-generation beams. Mass issues encountered while mounting the beam on the Chimera corvette led to that vessel's relatively thin armor plating. Nonetheless, the 'Aurora Wake' was the first beam weapon that enabled the GTVA to emulate Shivan-style shock jump tactics.

==Performance==
===Statistics===
{{Beam|4 500|35|4|Direct|1|5 400|617|21 600}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging even larger vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

==Gallery==

<gallery widths=250px >

File:Aristeia6.jpg|<center>Serkr Team opening fire in [[Aristeia]], deploying the overwhelming single-shot power of the ''Aurora Wake''.

</gallery>

===Veteran Comments===
{{Comment| ''It only does 60% of the damage of the [[BBlue]] on the first pass, and half of the sustained damage, but in the 14th battle group, there are twelve of these mounted on the [[GTCv Chimera]], [[GTCv Bellerophon]], and [[GTD Raynor]]. Thus, at a possible 237,600 points of damage on the first pass, they make up the bulk of the battle group's shock jump capability, at least theoretically.''

''Not a bad beam in itself, and used to great effect in Blue Planet in its stated role. The [[GTCv Chimera|Chimera]] corvette, marginally larger than a [[Deimos]], is practically built around three of these beams, and they collectively do just a bit less sustained damage, and slightly more damage per pulse, than a couple of [[BGreen|BGreens]], despite being mounted on a more than half smaller ship. It features great range, like most other blue beams, and also makes up most of the [[GTD Raynor|Raynor]]'s broadside firepower. This beam has both the sustained firepower and single-pass raw output to enable TEI corvettes to successfully engage ships far larger than themselves, to an extent the [[Deimos]] could only dream of. They are the reason Serkr are dubbed as Sathanas killers.''
}}

[[Category:Blue Planet weapons]]

BBlue

2019-01-22T17:39:06Z

AdmiralRalwood: /* Statistics */ It turns out I'm bad at math.

{{BPArticle}}
The '''''Ice Queen'' Heavy Beam''', also known as the '''BBlue''', is a heavy beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. Three ''Ice Queen'' beams form the primary forward armament of the [[GTD Titan|''Titan''-class destroyer]], and a single ''Ice Queen'' is mounted alongside two [[MBlue|''Aurora Wake'' medium beam cannon]]s on the [[GTCv Bellerophon|''Bellerophon''-class corvette]]. The ''Ice Queen'' is one of the most powerful beam weapons ever made by the [[GTVA]], with an effective range and damage output that far exceeds the venerable [[BGreen|''Crypt Hammer'']] without sacrificing refire rate or beam lifetime. Its main drawback lies in that its beam emitter is extremely fragile and easily destroyed, although it is just as easy to repair.

==Description==
===Blue Planet Tech Room Description===
The Titan-class destroyer and Bellerophon-class corvette mount 'Ice Queen' heavy beams on spinal mounts. These systems have the ability to decimate destroyer-class targets in only a few salvoes. Drawing massive amounts of power from dedicated meson reactors, the Ice Queen offers an overwhelming direct-fire solution to targets in the frontal arc. The system's beam emitters are easily damaged, but they can be replaced in days.

==Performance==
===Statistics===
{{Beam|8 250|30|4|Direct|1|9 000|1 200|36 000}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging large vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

===Veteran Comments===
{{Comment|''The Ice Queen is only marginally less powerful than the Winter King mounted at the front of the GTD Erebus. As the Titan-class destroyer has three of these mounted as its forward armament compared to the Erebus' one HBlue, the Titan, despite being more of a rear guard than front-line combatant, can do more than twice the damage than the Erebus from a head-on pass.''

''A Titan mounts three of these as its forward armament, and the turrets themselves are surprisingly hard to hit. That is very bad news for the UEF, as its three-cannon forward armament alone can kill a Solaris destroyer in two salvos from a range of 8.25 kilometers. One salvo would bring a Solaris from full hull integrity (180,000) to 81,000---from the time of jumping in (within range), it would take about 38 seconds to outright kill a Solaris.''
}}

[[Category:Blue Planet weapons]]

HBlue

2019-01-22T17:37:56Z

AdmiralRalwood: /* Statistics */ It turns out I'm bad at math.

{{BPArticle}}
The '''''Winter King'' Heavy Beam''', also known as the '''HBlue''', is a heavy beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. The most powerful beam weapon system ever created by the GTVA, the ''Winter King'' is the signature weapon of the [[GTD Erebus|''Erebus''-class destroyer]] and serves as the warship's main forward armament. While slightly inferior to the infamous [[BFGreen|overloaded ''Crypt Hammer'' beam]]s used by the [[GTVA Colossus|GTVA ''Colossus'']] in terms of raw damage output, the ''Winter King'' more than makes up for this with a shorter recharge time, greater sustained damage and an effective range that exceeds even the dreaded [[BFRed]]. However, the ''Winter King'' has yet to be fully tested, leaving its reliability in prolonged engagements debatable.

==Description==
===Blue Planet Tech Room Description===
Offering massive direct-fire engagement capability, the 'Winter King' heavy beam system is the Alliance's answer to Shivan destroyers. This advanced beam weapon uses metric tons of slurry coolant and consumes the full power output of a dedicated meson reactor. A complicated fire-control subsystem helps the beam burn through particulate interference and vaporized target material. No Alliance weapons system is more powerful. The Winter King has yet to be thoroughly tested in a sustained combat environment.

==Performance==
===Statistics===
{{Beam|9 750|30|4|Direct|1|11 100|1 480|44 400}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging large vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

===Veteran Comments===
{{Comment| ''This beam does more sustained damage than a [[BFGreen]] and a longer range than the [[LRBGreen]]. A single HBlue can destroy an [[SD Demon]] in four pulses.''

''Shares the impressive distinction of being a beam cannon that, even by itself and only featured as a single beam cannon, is a major threat to all ships short of a juggernaut, and has the range, refire rate, and power to be a huge tactical and strategic concern beyond the destroyer it's mounted on. Rumor has it that the HBlue was indeed originally intended to deliver more damage than three BBlues combined.''
}}

[[Category:Blue Planet weapons]]

MBlue

2019-01-22T17:11:04Z

AdmiralRalwood: /* Statistics */ Flubbed sustained DPS calculation.

{{BPArticle}}
The '''''Aurora Wake'' Beam System''', also known as the '''MBlue''', is a medium beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. The ''Aurora Wake'' is a high-performance medium beam cannon, and has the distinction of being the first beam weapon developed by the Threat Exigency Initiative that allowed the GTVA to replicate the shock jump tactics employed by the [[Shivans]] during the [[Second Shivan Incursion]]. The ''Aurora Wake'' suffers from a 35-second recharge time and tendency to overheat. However, it makes up for this with its effective range of 6750 metres. The [[GTCv Chimera|GTCv ''Chimera'']] mounts three of these beams as its forward armament.

==Description==
===Blue Planet Tech Room Description===
A powerful mid-range direct-fire beam system, the 'Aurora Wake' was one of the first products of the Threat Exigency Initiative's drive to produce more powerful beam cannons. Mounted on most next-generation Alliance warships as a battery weapon, the 'Aurora Wake' supplements its own dedicated reactors with feeds from the ship's drives. Prone to overheating, this system is perhaps the most cantankerous of the next-generation beams. Mass issues encountered while mounting the beam on the Chimera corvette led to that vessel's relatively thin armor plating. Nonetheless, the 'Aurora Wake' was the first beam weapon that enabled the GTVA to emulate Shivan-style shock jump tactics.

==Performance==
===Statistics===
{{Beam|4 500|35|4|Direct|1|9 000|1 029|36 000}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging even larger vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

==Gallery==

<gallery widths=250px >

File:Aristeia6.jpg|<center>Serkr Team opening fire in [[Aristeia]], deploying the overwhelming single-shot power of the ''Aurora Wake''.

</gallery>

===Veteran Comments===
{{Comment| ''It only does 60% of the damage of the [[BBlue]] on the first pass, and half of the sustained damage, but in the 14th battle group, there are twelve of these mounted on the [[GTCv Chimera]], [[GTCv Bellerophon]], and [[GTD Raynor]]. Thus, at a possible 237,600 points of damage on the first pass, they make up the bulk of the battle group's shock jump capability, at least theoretically.''

''Not a bad beam in itself, and used to great effect in Blue Planet in its stated role. The [[GTCv Chimera|Chimera]] corvette, marginally larger than a [[Deimos]], is practically built around three of these beams, and they collectively do just a bit less sustained damage, and slightly more damage per pulse, than a couple of [[BGreen|BGreens]], despite being mounted on a more than half smaller ship. It features great range, like most other blue beams, and also makes up most of the [[GTD Raynor|Raynor]]'s broadside firepower. This beam has both the sustained firepower and single-pass raw output to enable TEI corvettes to successfully engage ships far larger than themselves, to an extent the [[Deimos]] could only dream of. They are the reason Serkr are dubbed as Sathanas killers.''
}}

[[Category:Blue Planet weapons]]

MBlue

2019-01-22T17:10:30Z

AdmiralRalwood: /* Statistics */ Forgot range.

{{BPArticle}}
The '''''Aurora Wake'' Beam System''', also known as the '''MBlue''', is a medium beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. The ''Aurora Wake'' is a high-performance medium beam cannon, and has the distinction of being the first beam weapon developed by the Threat Exigency Initiative that allowed the GTVA to replicate the shock jump tactics employed by the [[Shivans]] during the [[Second Shivan Incursion]]. The ''Aurora Wake'' suffers from a 35-second recharge time and tendency to overheat. However, it makes up for this with its effective range of 6750 metres. The [[GTCv Chimera|GTCv ''Chimera'']] mounts three of these beams as its forward armament.

==Description==
===Blue Planet Tech Room Description===
A powerful mid-range direct-fire beam system, the 'Aurora Wake' was one of the first products of the Threat Exigency Initiative's drive to produce more powerful beam cannons. Mounted on most next-generation Alliance warships as a battery weapon, the 'Aurora Wake' supplements its own dedicated reactors with feeds from the ship's drives. Prone to overheating, this system is perhaps the most cantankerous of the next-generation beams. Mass issues encountered while mounting the beam on the Chimera corvette led to that vessel's relatively thin armor plating. Nonetheless, the 'Aurora Wake' was the first beam weapon that enabled the GTVA to emulate Shivan-style shock jump tactics.

==Performance==
===Statistics===
{{Beam|4 500|35|4|Direct|1|9 000|1 200|36 000}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging even larger vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

==Gallery==

<gallery widths=250px >

File:Aristeia6.jpg|<center>Serkr Team opening fire in [[Aristeia]], deploying the overwhelming single-shot power of the ''Aurora Wake''.

</gallery>

===Veteran Comments===
{{Comment| ''It only does 60% of the damage of the [[BBlue]] on the first pass, and half of the sustained damage, but in the 14th battle group, there are twelve of these mounted on the [[GTCv Chimera]], [[GTCv Bellerophon]], and [[GTD Raynor]]. Thus, at a possible 237,600 points of damage on the first pass, they make up the bulk of the battle group's shock jump capability, at least theoretically.''

''Not a bad beam in itself, and used to great effect in Blue Planet in its stated role. The [[GTCv Chimera|Chimera]] corvette, marginally larger than a [[Deimos]], is practically built around three of these beams, and they collectively do just a bit less sustained damage, and slightly more damage per pulse, than a couple of [[BGreen|BGreens]], despite being mounted on a more than half smaller ship. It features great range, like most other blue beams, and also makes up most of the [[GTD Raynor|Raynor]]'s broadside firepower. This beam has both the sustained firepower and single-pass raw output to enable TEI corvettes to successfully engage ships far larger than themselves, to an extent the [[Deimos]] could only dream of. They are the reason Serkr are dubbed as Sathanas killers.''
}}

[[Category:Blue Planet weapons]]

SBlue

2019-01-22T17:10:04Z

AdmiralRalwood: /* Statistics */ Bringing damage stats up-to-date with current version.

{{BPArticle}}
The '''''Thorn Lance'' Light Beam''', also known as the '''SBlue''', is a light beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. The ''Thorn Lance'' is the lightest beam created by the Alliance as a result of the Threat Exigency Initiative, and two of these beams serve as the primary weapon of the [[GTC Hyperion|GTC ''Hyperion'']]. The ''Thorn Lance''<nowiki></nowiki>'s biggest threat is its effective range, which is over 50% greater than that of the [[LRed]]. Its biggest weakness is its lengthy recharge time of 40 seconds, which is a major drawback to work around when coupled with the relatively small damage output.

==Description==
===Blue Planet Tech Room Description===
The Thorn Lance light beam system, mounted on Hyperion cruisers as their primary direct-fire weapons system, is the weakest of the next-generation beam systems. Nonetheless, it offers marked improvement in firepower over previous light beams, and its draw on the cruiser's systems overall is low. Cool-running, easy to maintain, and reasonably powerful, the Thorn Lance suffers only in that it is mounted on a fragile vessel.

==Performance==
===Statistics===
{{Beam|4 500|40|2.5|Direct|1|3 200|200|8 000}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging large vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

===Veteran Comments===
{{Comment|}}

[[Category:Blue Planet weapons]]

MBlue

2019-01-22T17:08:36Z

AdmiralRalwood: /* Statistics */ Bringing damage stats up-to-date with current version.

{{BPArticle}}
The '''''Aurora Wake'' Beam System''', also known as the '''MBlue''', is a medium beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. The ''Aurora Wake'' is a high-performance medium beam cannon, and has the distinction of being the first beam weapon developed by the Threat Exigency Initiative that allowed the GTVA to replicate the shock jump tactics employed by the [[Shivans]] during the [[Second Shivan Incursion]]. The ''Aurora Wake'' suffers from a 35-second recharge time and tendency to overheat. However, it makes up for this with its effective range of 6750 metres. The [[GTCv Chimera|GTCv ''Chimera'']] mounts three of these beams as its forward armament.

==Description==
===Blue Planet Tech Room Description===
A powerful mid-range direct-fire beam system, the 'Aurora Wake' was one of the first products of the Threat Exigency Initiative's drive to produce more powerful beam cannons. Mounted on most next-generation Alliance warships as a battery weapon, the 'Aurora Wake' supplements its own dedicated reactors with feeds from the ship's drives. Prone to overheating, this system is perhaps the most cantankerous of the next-generation beams. Mass issues encountered while mounting the beam on the Chimera corvette led to that vessel's relatively thin armor plating. Nonetheless, the 'Aurora Wake' was the first beam weapon that enabled the GTVA to emulate Shivan-style shock jump tactics.

==Performance==
===Statistics===
{{Beam|6 750|35|4|Direct|1|9 000|1 200|36 000}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging even larger vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

==Gallery==

<gallery widths=250px >

File:Aristeia6.jpg|<center>Serkr Team opening fire in [[Aristeia]], deploying the overwhelming single-shot power of the ''Aurora Wake''.

</gallery>

===Veteran Comments===
{{Comment| ''It only does 60% of the damage of the [[BBlue]] on the first pass, and half of the sustained damage, but in the 14th battle group, there are twelve of these mounted on the [[GTCv Chimera]], [[GTCv Bellerophon]], and [[GTD Raynor]]. Thus, at a possible 237,600 points of damage on the first pass, they make up the bulk of the battle group's shock jump capability, at least theoretically.''

''Not a bad beam in itself, and used to great effect in Blue Planet in its stated role. The [[GTCv Chimera|Chimera]] corvette, marginally larger than a [[Deimos]], is practically built around three of these beams, and they collectively do just a bit less sustained damage, and slightly more damage per pulse, than a couple of [[BGreen|BGreens]], despite being mounted on a more than half smaller ship. It features great range, like most other blue beams, and also makes up most of the [[GTD Raynor|Raynor]]'s broadside firepower. This beam has both the sustained firepower and single-pass raw output to enable TEI corvettes to successfully engage ships far larger than themselves, to an extent the [[Deimos]] could only dream of. They are the reason Serkr are dubbed as Sathanas killers.''
}}

[[Category:Blue Planet weapons]]

BBlue

2019-01-22T17:06:52Z

AdmiralRalwood: /* Statistics */ Bringing damage stats up-to-date with current version.

{{BPArticle}}
The '''''Ice Queen'' Heavy Beam''', also known as the '''BBlue''', is a heavy beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. Three ''Ice Queen'' beams form the primary forward armament of the [[GTD Titan|''Titan''-class destroyer]], and a single ''Ice Queen'' is mounted alongside two [[MBlue|''Aurora Wake'' medium beam cannon]]s on the [[GTCv Bellerophon|''Bellerophon''-class corvette]]. The ''Ice Queen'' is one of the most powerful beam weapons ever made by the [[GTVA]], with an effective range and damage output that far exceeds the venerable [[BGreen|''Crypt Hammer'']] without sacrificing refire rate or beam lifetime. Its main drawback lies in that its beam emitter is extremely fragile and easily destroyed, although it is just as easy to repair.

==Description==
===Blue Planet Tech Room Description===
The Titan-class destroyer and Bellerophon-class corvette mount 'Ice Queen' heavy beams on spinal mounts. These systems have the ability to decimate destroyer-class targets in only a few salvoes. Drawing massive amounts of power from dedicated meson reactors, the Ice Queen offers an overwhelming direct-fire solution to targets in the frontal arc. The system's beam emitters are easily damaged, but they can be replaced in days.

==Performance==
===Statistics===
{{Beam|8 250|30|4|Direct|1|15 000|2 000|60 000}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging large vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

===Veteran Comments===
{{Comment|''The Ice Queen is only marginally less powerful than the Winter King mounted at the front of the GTD Erebus. As the Titan-class destroyer has three of these mounted as its forward armament compared to the Erebus' one HBlue, the Titan, despite being more of a rear guard than front-line combatant, can do more than twice the damage than the Erebus from a head-on pass.''

''A Titan mounts three of these as its forward armament, and the turrets themselves are surprisingly hard to hit. That is very bad news for the UEF, as its three-cannon forward armament alone can kill a Solaris destroyer in two salvos from a range of 8.25 kilometers. One salvo would bring a Solaris from full hull integrity (180,000) to 81,000---from the time of jumping in (within range), it would take about 38 seconds to outright kill a Solaris.''
}}

[[Category:Blue Planet weapons]]

HBlue

2019-01-22T17:03:50Z

AdmiralRalwood: /* Statistics */ Bringing damage stats up-to-date with current version.

{{BPArticle}}
The '''''Winter King'' Heavy Beam''', also known as the '''HBlue''', is a heavy beam cannon used by the [[GTVA]] in the [[Portal:FreeSpace 2|FreeSpace 2]] mod [[Blue Planet]]. The most powerful beam weapon system ever created by the GTVA, the ''Winter King'' is the signature weapon of the [[GTD Erebus|''Erebus''-class destroyer]] and serves as the warship's main forward armament. While slightly inferior to the infamous [[BFGreen|overloaded ''Crypt Hammer'' beam]]s used by the [[GTVA Colossus|GTVA ''Colossus'']] in terms of raw damage output, the ''Winter King'' more than makes up for this with a shorter recharge time, greater sustained damage and an effective range that exceeds even the dreaded [[BFRed]]. However, the ''Winter King'' has yet to be fully tested, leaving its reliability in prolonged engagements debatable.

==Description==
===Blue Planet Tech Room Description===
Offering massive direct-fire engagement capability, the 'Winter King' heavy beam system is the Alliance's answer to Shivan destroyers. This advanced beam weapon uses metric tons of slurry coolant and consumes the full power output of a dedicated meson reactor. A complicated fire-control subsystem helps the beam burn through particulate interference and vaporized target material. No Alliance weapons system is more powerful. The Winter King has yet to be thoroughly tested in a sustained combat environment.

==Performance==
===Statistics===
{{Beam|9 750|30|4|Direct|1|18 500|2 467|74 000}}

==Notes==
*Weapon is a beam cannon [[Weapons.tbl#.22beam.22|(beam)]]
*Weapon is capable of easily damaging large vessels [[Weapons.tbl#.22Huge.22|(Huge)]]
*Weapon cannot be mounted on small ships [[Weapons.tbl#.22Big_Ship.22|(Big Ship)]]
*Weapon refire rate is the same on all difficulty levels [[Weapons.tbl#.22same_turret_cooldown.22|(same turret cooldown)]]

===Veteran Comments===
{{Comment| ''This beam does more sustained damage than a [[BFGreen]] and a longer range than the [[LRBGreen]]. A single HBlue can destroy an [[SD Demon]] in four pulses.''

''Shares the impressive distinction of being a beam cannon that, even by itself and only featured as a single beam cannon, is a major threat to all ships short of a juggernaut, and has the range, refire rate, and power to be a huge tactical and strategic concern beyond the destroyer it's mounted on. Rumor has it that the HBlue was indeed originally intended to deliver more damage than three BBlues combined.''
}}

[[Category:Blue Planet weapons]]

Ai.tbl

2018-07-07T23:03:50Z

AdmiralRalwood: Adding "$Use Actual Primary Range:"

{{TableVersionGit|2018-06-29|9d907c9}}

The '''ai.tbl''' file defines the AI classes used in the game. This table is used to define each AI class with four abilities for each of the five difficulty levels.

[[Tables|List of Tables]]

==Required Elements==

===$Name:===
*Defines a name for the AI class that can be used with ships.tbl and also with FRED
*Syntax: '''String''', name of the AI class

===$Accuracy:===
*How accurately the ship fires its weapons. Value is used to scale the error in the AI aim. With repeated shots, AI aim will improve. Note that the AI is always 100% accurate when aiming for subsystems, according to Retail code.
*Value from 0.0 to 1.0
*Syntax: '''Float list''', five comma separated '''floats''', one for each difficulty, very easy, easy, moderate, hard, insane difficulty levels respectively

===$Evasion:===
*How good the ship is at evading. Value defines the frequency of AI course changes while it is evading.
*Value from 0 to 100
*Syntax: '''Float list''', five comma separated '''floats''', one for each difficulty, very easy, easy, moderate, hard, insane difficulty levels respectively

===$Courage:===
*How likely the ship is to chance danger to accomplish goals. Basically the lower the value sooner the AI will start evading when attacked and its less likely to target turrets.
*Value from 0 to 100
*Syntax: '''Float list''', five comma separated '''floats''', one for each difficulty, very easy, easy, moderate, hard, insane difficulty levels respectively

===$Patience:===
*How willing the ship is to wait for an advantage before pursuing goals. Never actually implemented - It does absolutely nothing.
{{Table3611|This value affects how quickly the AI will attempt to "break" a stalemate situation if one is detected. Only applies if ''$Stalemate Time Threshold'' and ''$Stalemate Distance Threshold'' are used. The higher the patience, the longer the ship will wait in "stalemate" before breaking. If patience is 100, the AI will never break.
}}
*Value from 0 to 100
*Syntax: '''Float list''', five comma separated '''floats''', one for each difficulty, very easy, easy, moderate, hard, insane difficulty levels respectively

==Optional Elements==
===Other AI Class Attributes===
'''IMPORTANT NOTE''': If the following attributes are NOT specified, the code uses the index of the AI class instead. Use these if you want finer-grained control over the AI classes and/or you don't want the order of the AI classes to affect their behavior. ''If these are not specified, the behaviors described will be determined by the order of the AI class relative to the others in the file. Furthermore, having a different number of AI classes than retail can result in strange behavior if these are NOT set. It is recommended that if you make heavy use of custom AI classes, you specify all of these and set $Autoscale by AI Class Index to NO.''

====$Afterburner Use Factor:====
{{Table3611|
* Affects how probably it is that the AI will use afterburners in "maybe" situations. A value of 1 means always, 2 means half the time, 3 a third of the time, etc.
* Syntax: '''Int list''', five comma separated '''integers''', one for each difficulty.
}}

====$Shockwave Evade Chances Per Second:====
{{Table3611|
* Controls how likely it is for a ship to try to start evading a shockwave. The higher the number, the more "chances per second" the ship has to evade.
* Syntax: '''Float list''', five comma separated '''float''', one for each difficulty.
}}

====$Get Away Chance:====
{{Table3611|
* How likely the AI is to use a "get away" maneuver instead of simply making evasive turns. "Get away" usually involves the AI flying straight away, usually on afterburner, and making small jinking motions (instead of large evasive turns). Higher values result in more "jousting" fights.
* Range: between 0.0 (never) and 1.0 (always)
* Syntax: '''Float list''', five comma separated '''float''', one for each difficulty.
}}

====$Secondary Range Multiplier:====
{{Table3611|
* Multiplier which affects from how far away the AI will begin firing secondary weapons. Capped by the actual maximum range of the weapon. Penalty for firing in nebula still applies above and beyond this.
* Range: between 0.0 (point blank/never fires) and 1.0 (fires from maximum range).
* Syntax: '''Float list''', five comma separated '''float''', one for each difficulty.
}}

====$Autoscale by AI Class Index:====
{{Table3611|
* If set to YES (default), a number of miscellaneous AI probabilities are affected by the order of the AI class in the file (for example, the chance to fire countermeasures). Classes near the beginning of the file are generally weaker than classes at the end. If set to NO, this flag will turn off that auto scaling behavior (so that the order of the AI class does not affect AI behavior).
* Note that even if this is set to NO, the other options above will still be controlled by AI class index (so if you want complete independence, you need to set all of the options listed in the "Other AI Class Attributes" category).
* Default: YES
* Syntax: Boolean flag (YES/NO)
}}

===AI Profiles Overrides===
{{Table3611|The following values can be inserted as overrides for their equivalent [[Ai_profiles.tbl]] values. They are all optional. If not set for an AI class, the values in AI Profiles will be used.
Syntax is the same as their AI Profiles counterparts.
* $AI Countermeasure Firing Chance:
* $AI In Range Time:
* $AI Always Links Ammo Weapons:
* $AI Maybe Links Ammo Weapons:
* $Primary Ammo Burst Multiplier:
* $AI Always Links Energy Weapons:
* $AI Maybe Links Energy Weapons:
* $Predict Position Delay:
* $AI Shield Manage Delay:
* $Friendly AI Fire Delay Scale:
* $Hostile AI Fire Delay Scale:
* $AI Turn Time Scale:
* $Glide Attack Percent:
* $Circle Strafe Percent:
* $Glide Strafe Percent:
* $Stalemate Time Threshold:
* $Stalemate Distance Threshold:
* $Chance AI Has to Fire Missiles at Player:
* $Max Aim Update Delay:
* $Turret Max Aim Update Delay:
}}

===AI Profiles Flag Overrides===
{{Table3611|The following flags can be inserted to override their equivalent [[Ai_profiles.tbl]] flag values. They are all optional. If not set for an AI Class, the AI Profiles value will be used.
* $big ships can attack beam turrets on untargeted ships:
* $smart primary weapon selection:
* $smart secondary weapon selection:
* $smart shield management:
* $smart afterburner management:
* $allow rapid secondary dumbfire:
* $huge turret weapons ignore bombs:
* $don't insert random turret fire delay:
* $prevent turrets targeting too distant bombs:
* $smart subsystem targeting for turrets:
* $allow turrets target weapons freely:
* $allow vertical dodge:
* $No extra collision avoidance vs player:
}}
{{Table3613|
* $all ships manage shields:
}}
{{Table38|
* $ai can slow down when attacking big ships:
}}
{{Table382|
* $use actual primary range:
}}

==Sample Entry==
#AI Classes
$Name: Captain
$accuracy: 0.5 0.55 0.6 0.65 0.7
$evasion: 10, 20, 30, 40, 50
$courage: 10, 20, 30, 40, 50
$patience: 10, 20, 30, 40, 50
#End

{{Table3611| (Sample entry using some optional elements)
#AI Classes
$Name: Captain
$accuracy: 0.5 0.55 0.6 0.65 0.7
$evasion: 10, 20, 30, 40, 50
$courage: 10, 20, 30, 40, 50
$patience: 10, 20, 30, 40, 50
$Get Away Chance: 0.40, 0.45, 0.50, 0.55, 0.6
$Autoscale by AI Class Index: NO
$AI In Range Time: 2, 1.6, 1.2, 0.8, 0.4
$Primary Ammo Burst Multiplier: 0.6, 0.65, 0.7, 0.75, 0.8
$Glide Attack Percent: 30, 40, 50, 60, 70
$allow rapid secondary dumbfire: NO
$allow vertical dodge: YES
#End
}}
[[Category:Tables]]

Ai profiles.tbl

2018-07-07T23:01:30Z

AdmiralRalwood: Adding "$Use Actual Primary Range:"

{{SCP_table}}

{{TableVersionGit|2018-06-29|9d907c9}}

The '''ai_profiles.tbl''' allows the creation and management of different patterns of AI behavior, called profiles. Profiles consist of various statistics and flags that provide some control over AI behavior. All options within a profile are optional; if an option is not specified it will follow the original FreeSpace 2 retail behavior. Different missions can specify different profiles.

The default ai_profiles.tbl is hardcoded into the FSO executable, and defines the "FS2 RETAIL" AI profile. It's usually recommended not to modify this profile, but to create a new AI profile in a modular table instead, which will then inherit its defaults from the FS2 RETAIL profile.

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm

[[Tables|List of Tables]]

==General Format==
'''#AI Profiles'''

'''$Default Profile:''' ''a profile name''

''Up to 9 different AI profiles''

'''#End'''

==#AI Profiles==
*Indicates to the parser that this is an ai_profiles table file.

===$Default Profile:===
*Defines the profile that each mission will use if no profile is specified in FRED. In addition, this profile will be selected automatically in FRED when you create a new mission. If this line is not specified, the default profile will be the FreeSpace 2 retail behavior.

===$Profile Name:===
*The name of the profile, naturally.

----

The following entries accept '''float list''' of five comma-separated values. One value for each of the difficulty levels (Very Easy, Easy, Medium, Hard, Insane).

===$Player Afterburner Recharge Scale:===
{{Table3610|
*Sets the speed of afterburner recharge
*Syntax: '''Float list'''
**Default: 5, 3, 2, 1.5, 1}}

===$Max Beam Friendly Fire Damage:===
{{Table3610|
*Defines the maximum damage inflicted by friendly beam fire
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Player Countermeasure Life Scale:===
{{Table3610|
*Sets the factor applied to player launched countermeasure lifetime
*Syntax: '''Float list'''
**Default: 3, 2, 1.5, 1.25, 1}}

===$AI Countermeasure Firing Chance:===
{{Table3610|
*Defines the chance a countermeasure will be fired by an AI-controlled ship (this is scaled by ai_class)
*Syntax: '''Float list'''
**Default: 0.2, 0.3, 0.5, 0.9, 1.1}}

===$AI In Range Time:===
{{Table3610|
*The delay (in seconds) for the AI to fire its weapons after getting in range.
*Syntax: '''Float list'''
**Default: 2, 1.4, 0.75, 0, -1}}

===$AI Always Links Ammo Weapons:===
{{Table3610|
*AI ships will link ballistic primaries if ammo levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 95, 80, 60, 40, 20}}

===$AI Maybe Links Ammo Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Ammo Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Primary Ammo Burst Multiplier:===
{{Table3611|
*Allows the AI to fire primary weapons in bursts. How long the bursts are (and how much time between them) is a function of ammo remaining, distance to target, angle to target, and this multiplier. A value of 0 turns this feature off (AI fires normally, without bursts). A value < 1 will make for shorter bursts with larger gaps, and a value > 1 will give longer bursts with shorter gaps.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$AI Always Links Energy Weapons:===
{{Table3610|
*AI ships will link energy primaries if energy levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 100, 80, 60, 40, 20}}

===$AI Maybe Links Energy Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Energy Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Max Missiles Locked on Player:===
{{Table3610|
*Defines the maximum number of missiles allowed to be homing in on a player at any given time
*Note: Single-player only, no restriction in multiplayer
*Syntax: '''Float list'''
**Default: 2, 3, 4, 7, 99}}

===$Max Player Attackers:===
{{Table3610|
*Sets the maximum number of ships allowed to be attacking the player at any given time
*Syntax: '''Float list'''
**Default: 2, 3, 4, 5, 99}}

===$Max Incoming Asteroids:===
{{Table3610|
*Sets the maximum number of active (i.e. "thrown") asteroids that can be heading toward a friendly ship at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 5, 7, 10}}

===$Player Damage Factor: or $AI Damage Reduction to Player Hull:===
{{Table3610|
*Defines the factor applied to damage suffered by the player
*Syntax: '''Float list'''
**Default: 0.25, 0.5, 0.65, 0.85, 1}}

===$Player Subsys Damage Factor: or $AI Damage Reduction to Player Subsys:===
{{Table3610|
*Sets the factor applied to subsystem damage suffered by the player. This is in addition to the '''$Player Damage Factor:'''
*Syntax: '''Float list'''
**Default: 0.2, 0.4, 0.6, 0.8, 1}}

===$Predict Position Delay:===
{{Table3610|
*Sets the measure of time (in F1_0 units) after which the AI will recalculate the position of its target.
*It does not apply to the AI's aim, it only applies to things like avoiding collisions and maneuvering at close range. Generally, anything other than a 0 just allows the AI to do monumentally stupid things like try to turn to avoid ramming where it thought you were 2 seconds ago.
*Syntax: '''Float list'''
**Default: 2, 1.5, 1.333, 0.5, 0}}

===$AI Shield Manage Delay:===
{{Table3610|
*Also '''$AI Shield Manage Delays:'''
*Sets the time in seconds between each instance of an AI ship managing its shields
*Syntax: '''Float list'''
**Default: 5, 4, 2.5, 1.2, 0.1}}

===$Friendly AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 2, 1.4, 1.25, 1.1, 1}}

===$Hostile AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 4, 2.5, 1.75, 1.25, 1}}

===$Friendly AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 0.4, 0.6, 0.8, 1.0, 1.2}}

===$Hostile AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 1.4, 1.2, 1.0, 0.8, 0.6}}

===$AI Turn Time Scale:===
{{Table3610|
*Defines the factor applied to time it takes for enemy ships to turn. A value of 1.0 means the ship turns at normal speed, 2.0 means half speed (takes twice as long), etc. Note that this value ONLY affects ships hostile to the player (always 1.0 for friendly ships).
*Syntax: '''Float list'''
**Default: 3, 2.2, 1.6, 1.3, 1}}

===$Glide Attack Percent:===
{{Table3611|
*How often the AI will use the "glide attack" move when it has the opportunity. Glide attack means using glide to maintain course while aiming and firing at the current target. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Circle Strafe Percent:===
{{Table3611|
*How often the AI will use the "circle strafe" move when it has the opportunity. Circle strafe means that the ship will attempt "Descent-like" combat, trying to maintain distance while circling around the target using sidethrusters. Ships will only attempt this when sidethrust top speed is at least 2/3 of target's current velocity.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Glide Strafe Percent:===
{{Table3611|
*How often the AI will use the "glide strafe" move when it has the opportunity. Glide strafe means using glide to attack capships by flying past and shooting at them. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Random Sidethrust Percent:===
{{Table3611|
*Percentage of the time where AI ships will randomly sidethrust in a dogfight.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Time Threshold:===
{{Table3611|
*The minimum amount of time required for the AI to detect a "stalemate" situation. If a ship and its target have been within a certain distance of each other (defined by ''$Stalemate Distance Threshold'') for this amount of time without either of them scoring a hit on the other, the AI will do something to break the stalemate. Only applies to small ships. If this value is 0 or less, no stalemate detection is performed.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Distance Threshold:===
{{Table3611|
*The maximum distance that an AI ship must remain from its target for a "stalemate" to occur (see ''$Stalemate Time Threshold'').
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Shield Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's shields recharge
*Syntax: '''Float list'''
**Default: 4, 2, 1.5, 1.25, 1}}

===$Player Weapon Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's weapons recharge
*Syntax: '''Float list'''
**Default: 10, 4, 2.5, 2, 1.5}}

===$Max Turret Target Ownage:===
{{Table3610|
*Sets the maximum number of turrets on a particular ship allowed to be attacking the same target at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 7, 12, 19}}

===$Max Turret Player Ownage:===
{{Table3610|
*Sets the maximum number of turrets on a particular ship allowed to be attacking the player at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 7, 12, 19}}

===$Percentage Required For Kill Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.30, 0.30, 0.30, 0.30, 0.30}}

===$Percentage Required For Assist Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded an assist (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.15, 0.15, 0.15, 0.15, 0.15}}

===$Percentage Awarded For Capship Assist:===
{{Table3610|
*In TvT and Coop missions all teammates will be granted this percentage of the capships score when someone scores a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.5, 0.5, 0.5, 0.5, 0.5}}

===$Repair Penalty:===
{{Table3611|
*The amount to subtract from the player's score if they are repaired by a support ship
*Syntax: '''Integer list'''
**Default: 10, 20, 35, 50, 60}}

===$Delay Before Allowing Bombs to Be Shot Down:===
{{Table3611|
*Time after bombs are fired during which the bombs are invulnerable to weapon hits
*Syntax: '''Float list'''
**Default: 1.5, 1.5, 1.5, 1.5, 1.5}}

===$Chance AI Has to Fire Missiles at Player:===
{{Table3611|
*Chance - expressed in ('''value''' + 1) / 7 - of each AI turret within current 10 second segment to be allowed to shoot missiles at player ship.
*Syntax: '''Float list'''
**Default: 0, 1, 2, 3, 4}}

===$Max Aim Update Delay:===
{{Table3611|
*Maximum amount of delay allowed before the AI will update its aim. Until the next update, the AI will project the target forward based on last checked position and velocity. Applies to small ships vs small ships (dogfights). The actual delay is randomly selected between 0 and the maximum (so setting a value of 2 will result in an average of 1 second delay).
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Turret Max Aim Update Delay:===
{{Table3611|
*As $Max Aim Update Delay, but affecting turrets instead
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Autoaim FOV:===
{{Table3613|
*Gives the player autoaim within the specified number of degrees from the target (FOV).
*Unlike the ships.tbl settings for autoaim, this only affects the player (and, of course, only if there is a nonzero value for the difficulty level.)
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Detail Distance Multiplier:===
{{Table3613|
*Affects how the "model detail level" setting in Options switches between LOD levels.
*This number acts as a multiplier on the LOD distances specified in ships.tbl.
*NOTE THAT THIS IS PER DETAIL LEVEL, NOT PER DIFFICULTY LEVEL.
*Syntax: '''Float list'''
**Default: 0.125, 0.25, 1.0, 4.0, 8.0}}
----

The following entries are boolean flags. They can be set to ''YES'' or ''NO'', ''TRUE'' or ''FALSE'', ''OUI'' or ''NON'', ''HIja′'' or ''ghobe′'', etc. The default is ''NO''.

===$big ships can attack beam turrets on untargeted ships:===
{{Table3610|
*If set, big ships can attack a beam turret that's firing on them from a ship that they don't currently have targeted.}}

===$smart primary weapon selection:===
{{Table3610|
*If set, enables the new primary weapon selection method}}

===$smart secondary weapon selection:===
{{Table3610|
*If set, enables the new secondary weapon selection method (including proper use of bomber+ missiles)}}

===$smart shield management:===
{{Table3610|
*If set, shields will devote all their charging energy to the weakest quadrant(s) and not waste energy on fully-charged quadrants (previously was -smart_shields on the command line)}}

===$smart afterburner management:===
{{Table3610|
*If set, the AI will properly use brief pulses of afterburner power instead of afterburning until fuel is exhausted}}

===$allow rapid secondary dumbfire:===
{{Table3610|
*If set, allows an AI ship to switch to rapid fire for dumbfire missiles}}

===$huge turret weapons ignore bombs:===
{{Table3610|
*If set, causes huge turret weapons (including anti-capship beams) to not target bombs}}

===$don't insert random turret fire delay:===
{{Table3610|
*If set, removes the random turret fire delay (from .1 to .9 seconds) inserted in addition to AI Fire Delay Scale}}

===$hack improve non-homing swarm turret fire accuracy:===
{{Table3610|
*If set, triggers a hack to improves the accuracy of non-homing swarm missiles by firing them along the turret's last fire direction rather than the direction it currently faces
*Also disables swarm weapons ability to fire only on the 'turrets barrel line'.}}

===$shockwaves damage small ship subsystems:===
{{Table3610|
*If set, shockwaves will cause damage to small ship subsystems (like in FS1)}}

===$navigation subsystem governs warpout capability:===
{{Table3610|
*If set, ships will not be able to warp out if their navigation subsystem is destroyed or low in strength}}

===$ignore lower bound for minimum speed of docked ship:===
{{Table3610|
*If set, there will be no lower bound for the speed at which docked ships move (like in FS1).
*When a ship is towing another ship or ships, the towing ship will be slowed down to a degree depending on the total mass of all docked ships. In FS1, the ships could slow down to an arbitrarily slow speed, even a fraction of a m/s above zero. In FS2, there is a lower bound on this behavior so that all ships are guaranteed to move at a minimum docked speed. When set, this flag removes the lower bound and restores FS1 behavior.}}

===$disable linked fire penalty:===
{{Table3610|
*If set, there will be no penalty for linking primaries. Normally, the rate of fire is *1 for a single bank, *0.66 for two banks and *0.5 for three banks (the fire delay is increased according to the formula 1+([nb of banks]-1)*0.5 ).}}

===$disable weapon damage scaling:===
{{Table3610|
*If set, weapons will do the same damage to a ship regardless of "big damage", "supercap", etc. ship types.}}

===$use additive weapon velocity:===
{{Table3610|
*If set, weapons will inherit their firing ship's velocity. A ship traveling quickly will fire weapons faster than a ship traveling slowly. This also improves the accuracy of weapons fired while gliding.}}

===$use newtonian dampening:===
{{Table3610|
*Newtonian Dampening changes turning and acceleration behavior. By default, there's quite a bit of slide when you turn, and when combined with high damp values (such as in BtRL), you can actually push your speed up beyond the max. Newtonian Dampening is the more realistic turns, where too much turning will lower your speed. Forward momentum is also affected. Backslash can explain it in more detail. [http://www.hard-light.net/forums/index.php/topic,50870.msg1029741.html#msg1029741] }}

===$include beams for kills and assists:===
{{Table3610|
*If set, beam damage is counted when calculating kills and assists.}}

===$score kills based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the killer inflicted on the dead ship.}}

===$score assists based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the player gaining the assist inflicted on the dead ship.}}

===$allow event and goal scoring in multiplayer:===
{{Table3610|
*If set, players (rather than just their team) can gain score from events in multiplayer.}}

===$fix linked primary weapon decision bug:===
{{Table3610|
*If set, the AI will properly link primaries according to specified percentages of energy levels instead of retail behavior where it mistakenly linked according to absolute energy levels.}}

===$prevent turrets targeting too distant bombs:===
{{Table3610|
*If set, prevents turrets from targeting bombs beyond maximum range of the weapons of the turret.}}

===$smart subsystem targeting for turrets:===
{{Table3610|
*If set, prevents turrets from trying to target subsystems beyond their fov limits, also keeps the turret subsystem targeting preference order intact regardless of the angle to the target.}}

===$fix heat seekers homing on stealth ships bug:===
{{Table3610|
*If set, heat-seeking missiles will not home in on stealth ships (this mirrors the established behavior where heat-seeking missiles do not home in on ships that are hidden from sensors).}}

===$multi allow empty primaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without primaries.}}

===$multi allow empty secondaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without secondaries.}}

===$allow turrets target weapons freely:===
{{Table3611|
*If set, allows turrets to target any weapons instead of just targeting bombs, to be used in conjunction with target priorities setup.}}

===$use only single fov for turrets:===
{{Table3611|
*If set, allows turrets to fire outside some hardcoded FOV set for certain missile types limits, and rely only on the user defined FOV.}}

===$allow vertical dodge:===
{{Table3611|
*If set, allows ships to dodge weapons fire vertically as well as horizontally.}}

===$force beam turrets to use normal fov:===
{{Table3611|
*If set makes beam turrets use same FOV rules as other weapons do. Prevents beam from a turret from following the target beyond the turret's FOV}}

===$fix AI class bug:===
{{Table3611|
*Fixes a bug where AI class attributes are not set properly on ships if the AI class is set in the mission to something other than the default for the ship type. Set this to YES if you want attributes in [[Ai.tbl]] to mean anything at all.}}

===$turrets ignore targets radius in range checks:===
{{Table3611|
*TBD.}}

===$no extra collision avoidance vs player:===
{{Table3611|
*Disables the extra collision avoidance that AI normally uses against the player. Makes the AI more aggressive vs the player at close range (same treatment as vs other AI), although ship-ship collisions are slightly more likely.}}

===$perform fewer checks for death screams:===
{{Table3614|
*If set, the game will check if the dying ship is a player's wingman, before making it give a death scream.
Prior to revision 9119, this was "$perform fewer checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*TBD.}}

===$require turrets to have target in fov:===
{{Table3614|
*TBD.}}

===$all ships manage shields:===
{{Table3613|
*Allows AI to manage shields on big ships}}

===$ai aims from ship center:===
{{Table3613|
*AI aims weapons using the center of the ship instead of the first gunpoint. If a convergence offset is specified for this ship in ships.tbl, AI aims using that as a reference point.}}

===$allow primary link at mission start:===
{{Table37|
*When set, no ships will link primaries for the first 30 seconds of a mission. In addition, ships will randomly not link for the first two minutes of a mission. Set this to NO to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
*When set, beam weapons will be able to effectively intercept bombs. In addition, bombs flying through a beam path will get damaged and destroyed. Default: NO.}}

===$disable weapon damage scaling for player:===
{{Table3613|
*When set, Player weapon damage will no longer be scaled down when firing a non-huge primary against a ship with the "big damage" flag. Use with caution, as this may severely impact mission balance.}}

===$countermeasures affect aspect seekers:===
{{Table3613|
*TBD.}}

===$ai guards specific ship in wing:===
{{Table3615|
*If ordered to guard a ship in a wing (of which it is not a member), the AI will guard that specific ship instead of the entire wing (resulting in guarding the wing leader).}}

===$ai path mode:===
{{Table3613|
*Possible options are "normal" and "alt1". The alt1 mode differs from the normal behaviour in the following ways:
**1. No path shortcutting. Normal pathing AI will skip forward along a path to the furthest point it can reach. This is sometimes desirable, but makes it a lot harder to predict how the AI is going to behave at various points along a path. Turning this off also allows us to force the AI to straighten out, by giving it several waypoints in a more-or-less straight line. This is useful for such things as lining up a landing.
**2. No sliding when following paths. Docking still works, but there is some code that causes the AI to go full retard if it just misses a point: it turns towards the point in big, looping circles. This is apparently caused by passing a slide_vec value into ai_turn_towards_vector, which doesn't even seem to do what you'd expect it to do. Passing a null value instead turns off the stupid. (The behavior is fixed in alt1).
**3. Momentum taken into account when following paths. Path points will trigger sooner, proportional to the ship's speed and momentum. This prevents the AI from massively overshooting a waypoint, especially with high-damp ships.
**4. AI tries to follow the line between waypoints. Instead of just pointing at the next waypoint, the AI will fly a bit towards the line. This helps keep the AI actually on the path it claims to be following. See picture:[[Image:Altpaths.png]]
Blue is what happens with regular pathing. Red is the modified pathing: as you can see, it actively moves back towards the line.
**5. AI will respect "cap-waypoint-speed" when following paths (such as when docking or departing via bay).}}

===$default weapon select effect:===
{{Table3613|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS1" and "off"}}
{{Table3615|
*This flag has been moved to [[Game_settings.tbl]]}}

===$default ship select effect:===
{{Table3613|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS1" and "off"}}
{{Table3615|
*This flag has been moved to [[Game_settings.tbl]]}}

===$no warp camera:===
{{Table3615|
*When set, prevents the view from switching to the external camera when the player warps out.
*Note: this flag is deprecated and may get moved to another table without further notice.}}

===$fix ai path order bug:===
{{Table3615|
*When set, ship will follow its own waypoint path unless the wingleader has the same waypoint path and order.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$aspect bomb invulnerability fix:===
{{Table373|
*When set, the code that makes bombs invulnerable for the first 1.5 seconds of life will use the correct lifetime calculation for aspect bombs. Without this fix, the invulnerability time will be extended by 20% of the total lifetime of the bomb.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$glide decay requires thrust:===
{{Table373|
*When set, gliding ships will maintain their current speed without decay as long as they aren't actively thrusting.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$ai can slow down when attacking big ships:===
{{Table38|
*When set, fighters attacking big ships will slow down depending on how long they've been attacking (80% speed after 5 seconds, 60% after 8 seconds, 40% after 10 seconds, and 20% after 15 seconds), how long it's been since they were last shot (full throttle if it was within the past 6 seconds), and how close they are (full throttle if the target is more than 1200 meters away).
*Off by default.
*Syntax: '''''Boolean'''''}}

===$use actual primary range:===
{{Table382|
*When set, fighters will no longer fire primary weapons at targets outside their range just because weapon travel time would be sufficiently short.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$bay arrive speed multiplier:===
{{Table373|
*Causes all AI ships arriving from fighterbays (following a fighterbay path) to gradually accelerate, instead of immediately attempting to attain maximum speed. This can be used to prevent fighters from overshooting the fighterbay paths. The initial target speed is the maximum speed multiplied by the given value, with the multiplier gradually approaching 1.0 as the distance to the end of the path decreases.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|Will be overridden by path-specific multipliers, see [[Ships.tbl#.2Barrive_speed_multiplier:]].}}
}}

===$bay depart speed multiplier:===
{{Table373|
*Same as above, except for departures into fighterbays. The initial target speed is the maximum speed, with the target speed gradually approaching maximum speed multiplied by the given value as the distance to the fighterbay decreases.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|Will be overridden by path-specific multipliers, see [[Ships.tbl#.2Bdepart_speed_multiplier:]].}}
}}

==Sample Entry==
*Retail FS2 behaviour

<pre>
#AI Profiles

$Default Profile: FS2 RETAIL

$Profile Name: FS2 RETAIL

$Player Afterburner Recharge Scale: 5, 3, 2, 1.5, 1
$Max Beam Friendly Fire Damage: 0, 5, 10, 20, 30
$Player Countermeasure Life Scale: 3, 2, 1.5, 1.25, 1
$AI Countermeasure Firing Chance: 0.2, 0.3, 0.5, 0.9, 1.1
$AI In Range Time: 2, 1.4, 0.75, 0, -1
$AI Always Links Ammo Weapons: 95, 80, 60, 40, 20
$AI Maybe Links Ammo Weapons: 90, 60, 40, 20, 10
$Primary Ammo Burst Multiplier: 0, 0, 0, 0, 0
$AI Always Links Energy Weapons: 100, 80, 60, 40, 20
$AI Maybe Links Energy Weapons: 90, 60, 40, 20, 10
$Max Missiles Locked on Player: 2, 3, 4, 7, 99
$Max Player Attackers: 2, 3, 4, 5, 99
$Max Incoming Asteroids: 3, 4, 5, 7, 10
$Player Damage Factor: 0.25, 0.5, 0.65, 0.85, 1
$Player Subsys Damage Factor: 0.2, 0.4, 0.6, 0.8, 1
$Predict Position Delay: 2, 1.5, 1.333,0.5, 0
$AI Shield Manage Delay: 5, 4, 2.5, 1.2, 0.1
$Friendly AI Fire Delay Scale: 2, 1.4, 1.25, 1.1, 1
$Hostile AI Fire Delay Scale: 4, 2.5, 1.75, 1.25, 1
$Friendly AI Secondary Fire Delay Scale: 0.4, 0.6, 0.8, 1.0, 1.2
$Hostile AI Secondary Fire Delay Scale: 1.4, 1.2, 1.0, 0.8, 0.6
$AI Turn Time Scale: 3, 2.2, 1.6, 1.3, 1
$Glide Attack Percent: 0, 0, 0, 0, 0
$Circle Strafe Percent: 0, 0, 0, 0, 0
$Glide Strafe Percent: 0, 0, 0, 0, 0
$Random Sidethrust Percent: 0, 0, 0, 0, 0
$Stalemate Time Threshold: 0, 0, 0, 0, 0
$Stalemate Distance Threshold: 0, 0, 0, 0, 0
$Player Shield Recharge Scale: 4, 2, 1.5, 1.25, 1
$Player Weapon Recharge Scale: 10, 4, 2.5, 2, 1.5
$Max Turret Target Ownage: 3, 4, 7, 12, 19
$Max Turret Player Ownage: 3, 4, 7, 12, 19
$Percentage Required For Kill Scale: 0.30, 0.30, 0.30, 0.30, 0.30
$Percentage Required For Assist Scale: 0.15, 0.15, 0.15, 0.15, 0.15
$Percentage Awarded For Capship Assist: 0.1, 0.2, 0.35, 0.5, 0.6
$Repair Penalty: 10, 20, 35, 50, 60
$Delay Before Allowing Bombs to Be Shot Down: 1.5, 1.5, 1.5, 1.5, 1.5
$Chance AI Has to Fire Missiles at Player: 0, 1, 2, 3, 4
$Max Aim Update Delay: 0, 0, 0, 0, 0
$Turret Max Aim Update Delay: 0, 0, 0, 0, 0
$Player Autoaim FOV: 0, 0, 0, 0, 0
$Detail Distance Multiplier: 0.125,0.25, 1.0, 4.0, 8.0

$big ships can attack beam turrets on untargeted ships: NO
$smart primary weapon selection: NO
$smart secondary weapon selection: NO
$smart shield management: NO
$smart afterburner management: NO
$allow rapid secondary dumbfire: NO
$huge turret weapons ignore bombs: NO
$don't insert random turret fire delay: NO
$hack improve non-homing swarm turret fire accuracy: NO
$shockwaves damage small ship subsystems: NO
$navigation subsystem governs warpout capability: NO
$ignore lower bound for minimum speed of docked ship: NO
$disable linked fire penalty: NO
$disable weapon damage scaling: NO
$use additive weapon velocity: NO
$use newtonian dampening: NO
$include beams for kills and assists: NO
$score kills based on damage caused: NO
$score assists based on damage caused: NO
$allow event and goal scoring in multiplayer: NO
$fix linked primary weapon decision bug: NO
$prevent turrets targeting too distant bombs: NO
$smart subsystem targeting for turrets: NO
$fix heat seekers homing on stealth ships bug: NO
$multi allow empty primaries: NO
$multi allow empty secondaries: NO
$allow turrets target weapons freely: NO
$use only single fov for turrets: NO
$allow vertical dodge: NO
$force beam turrets to use normal fov: NO
$fix AI class bug: NO
$turrets ignore targets radius in range checks: NO
$no extra collision avoidance vs player: NO
$perform fewer checks for death screams: NO
$advanced turret fov edge checks: NO
$require turrets to have target in fov: NO
$all ships manage shields: NO
$ai aims from ship center: NO
$allow primary link at mission start: NO
$allow beams to damage bombs: NO
$disable weapon damage scaling for player: NO
$countermeasures affect aspect seekers: NO
$ai path mode: normal
$no warp camera: NO

#End
</pre>

== References ==
# "[http://www.hard-light.net/forums/index.php/topic,50870.msg1029741.html#msg1029741 Re: New difficulty? - Feature request!]", ''Hard Light Productions Forums'', Hard Light Productions, 2007-12-15. Retrieved on [[December_27]], [[2007]].

[[Category:Tables]]

Ssm.tbl

2018-01-05T22:58:26Z

AdmiralRalwood: Forgot the randomization upgrades.

{{TableVersionGit|2015-08-24|abd31038e7}}

The '''ssm.tbl''' was originally meant for defining the flight behavior of subspace missiles (SSM).

This table is one of the [[Modular Tables]] and can be extended with xxx-ssm.tbm

[[Tables|List of Tables]]

==Format==
*Table consists of independent '''$SSM:''' entries
*Table ends with '''#end'''

==Table Entries==

==$SSM:==
*Names the SSM strike.
{{Table374|The name itself is optional; if not present, it gets defaulted to "SSM <index>", allowing easy selection in FRED.}}
*Syntax: '''String''', name of the strike (as used by SEXPs and weapons)

===+Weapon:===
*Defines the weapon used in the strike.
*Syntax: '''String''', name of the weapon

===+Count:===
* (Optional) Defines number of the weapons fired by the strike.
*Syntax: '''Integer''', defaults to 1
{{Table374|
===+Min Count:===
* (Optional) Can be used instead of "+Count:", and in combination with "+Max Count:", to allow for a random number of weapons to be in the strike.
*Syntax: '''Integer'''
===+Max Count:===
* (Required if "+Min Count:" is used) Specifies the maximum number of weapons that can be fired by the strike.
*Syntax: '''Integer'''}}

===+WarpRadius:===
*Defines the radius of the warp effect.
*Syntax: '''Float'''

===+WarpTime:===
* (Optional) Defines the lifetime of the warp effect in seconds. Non-beam weapons fire halfway through this lifetime; beam weapons either fire at the start of the effect or at the appropriate time so that the midpoint of the beam is the same as the midpoint of the warp effect, whichever is later.
*Syntax: '''Float''', defaults to 4.0

===+Radius:===
*Defines the radius of the formation used by the weapons in the strike.
*Syntax: '''Float'''
{{Table374|
===+Min Radius:===
* (Optional) Can be used instead of "+Radius", and in combination with "+Max Radius:", to allow for a random radius to be used by the strike.
*Syntax: '''Float'''
===+Max Radius:===
* (Required if "+Min Radius:" is used) Specifies the maximum radius of the strike formation.
*Syntax: '''Float'''}}

===+Offset:===
* (Optional) Defines the offset of the formation used by the weapons in the strike; generally works best with circular strikes.
*Syntax: '''Float''', defaults to 0
{{Table374|
===+Min Offset:===
* (Optional) Can be used instead of "+Offset", and in combination with "+Max Offset:", to allow for a random offset to be used by the strike.
*Syntax: '''Float'''
===+Max Offset:===
* (Required if "+Min Offset:" is used) Specifies the maximum offset of the strike formation.
*Syntax: '''Float'''}}

===+Shape:===
{{Table373|
* (Optional) The shape used for the formation of weapons.
*Syntax: '''Point''', '''Circle''', or '''Sphere'''; defaults to Circle}}

===+HUD Message:===
* (Optional) Whether or not firing this SSM triggers a HUD message.
*Syntax: '''Boolean''', defaults to true

===+Custom Message:===
* (Optional) Can be used to define a custom message to be triggered when the SSM is fired.
*Syntax: '''String'''
*Note: By default, the message played is the one defined in strings.tbl index 1570, which is set to the generic "Firing Artillery"

===+Alarm Sound:===
{{Table371|
* (Optional) Can be used to define a custom alarm sound to be played when the SSM is fired.
*Syntax: '''Integer'''}}

[[Category:Tables]]

Game settings.tbl

2017-11-20T22:37:06Z

AdmiralRalwood: whoops

{{SCP_table}}

{{TableVersionGit|2015-11-21|71cf169}}

The '''game_settings.tbl''', also known as mod.tbl, defines options that can be changed globally.

This table is one of the [[Modular Tables]] and can be extended with xxx-mod.tbm

[[Tables|List of Tables]]

==#GAME SETTINGS==
Optional. Contains settings that affect how the engine works. 

===$Target Version:===
{{Table373|
Specifies the minimum version of FreeSpace Open that this mod supports. If the version specified here is greater than the version of the current build, an error message is displayed.
}}
{{Table381|
The $Minimum version option has been renamed to $Target Version. The old name is kept with the same functionality for backwards-compatibility.

The target version specifies what version of the FSO engine this mod was created for. It will be used by the engine to enable or disable backwards-incompatible changes by default. The default value is 2.0 which specifies that the mod targets the retail engine version.
}}

====+Major:====
{{Table373|
Required. Sets the major component of the target version.
*Syntax: '''''Integer''''' 
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Minor:====
{{Table373|
Required. Sets the minor component of the target version.
*Syntax: '''''Integer''''' 
*Example: '''''7''''' (for a minimum version of 3.7.3.20151121)
}}

====+Build:====
{{Table373|
Required. Sets the build component of the target version.
*Syntax: '''''Integer''''' 
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Revision:====
{{Table373|
Optional. Sets the revision component of the target version. If no revision is given then all builds of that release are supported (even nightly builds if there are any).
For nightly builds this is the date in YYYYMMDD format.
*Syntax: '''''Integer''''' 
*Example: '''''20151121''''' (for a minimum version of 3.7.3.20151121)
}}

===$Window title:===
{{Table382|
Specifies the name of the FSO window when this mod is running. If blank or unspecified, the window will have the default title of "FreeSpace 2".
*Syntax: '''''String'''''
}}

==#CAMPAIGN SETTINGS==
Optional. This group contains various Campaign related settings and overrides. 

===$Default Campaign File Name:===
Defines which campaign will be selected by default for new pilots. A file extension is not needed and, if present, is removed by the code.
*Syntax: '''''String''''' 

===#Ignored Campaign File Names===
Optional. Defines which campaigns, if present, will not appear in the Campaign Room. Only single-player campaigns can be ignored. ''File extensions are required.''
{{Table371|As of 3.7.1, file extensions are not required and, if present, are removed by the code.}}
====$Campaign File Name:====
File name of the campaign to ignore. Multiple entries may exist.
*Syntax: '''''String''''' 

===$Red-alert applies to delayed ships:===
Controls whether red-alert saved statistics (hitpoints, weapons, subsystem strengths) will be restored for ships that are not present at mission start.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

==#HUD SETTINGS==
Optional. This group contains various HUD behavior settings and overrides 

===$Directive Wait Time:===
*Defines how long the game will wait before displaying a directive.
*Syntax: '''''Integer''''' 
*Values: '''''Greater than or equal to 0 ms'''''

===$Cutscene camera displays HUD:===
Show the HUD when the cutscene camera is enabled.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Cutscene camera disables HUD: and had a default of YES.

===$Full color head animations:===
Enables full-color head ANIs. Normal head ANIs will appear in gray.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Color head animations with hud colors: and had a default of YES.

==#SEXP SETTINGS==
Optional. This group contains SEXP settings and overrides. 

===$Loop SEXPs Then Arguments:===
Flips how when-argument settings loop. See: [http://www.hard-light.net/forums/index.php?topic=79602.0 SEXP Argument changes via mod.tbl]
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

===$Use Alternate Chaining Behavior:===
When set, this makes the event chaining behavior act as people expected it to be in [http://scp.indiegames.us/mantis/view.php?id=82 Mantis #82].
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

==#GRAPHICS SETTINGS==
Optional. This group contains settings related to graphics. 

===$Enable External Shaders:===
Enables the use of external shader files. By default, the engine will use the built-in shaders.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Default Detail Level:===
{{Table3615|
Determines which graphics detail level preset (low, medium, high, very high) acts as the default for new pilots.
*Syntax: '''''Integer''''' (0-3)
*Default Value: '''''3''''' (very high) }}

===$Briefing Window FOV:===
{{Table371|
Determines the FOV in the briefing Icon window. Retail default for this is 0.29375, previous versions of FSO used a value of 0.5.
*Syntax: '''''Float''''' (0.0 to 1.0)
*Default Value: '''''0.29375''''' }}

===$Generic Pain Flash Factor:===
{{Table373|
Determines the intensity of the pain red flash when the player is hit.
*Syntax: '''''Float'''''
*Default Value: '''''1.0''''' }}

===$Shield Pain Flash Factor:===
{{Table373|
Determines the intensity of a pain flash when the player's shields are hit. Color will match the current ships shield color defined in ships.tbl. A value of 0 will give retail behavior (no shield effect). Positive values will cause the effect to start at full intensity at full shields and go to next to no intensity at zero shields. Negative values will cause no effect at full shields and full effect at no shields. Values should be kept between -1.0 and 1.0 for good pilot visibility.
*Syntax: '''''Float'''''
*Default Value: '''''0.0''''' }}

===$BMPMAN Slot Limit:===
{{Table382|
Determines the maximum number of textures that can be loaded simultaneously. This includes every frame of an animation, unless that animation is streaming (e.g. command briefing animations, message talking heads, etc). Also includes dynamically-created textures (used internally for various functions).
*Syntax: '''''Int'''''
*Values: '''''Greater than or equal to 3500'''''
*Default Value: '''''4750''''' }}

==#SOUND SETTINGS==
Optional. This group contains sound-related settings 

===$Default Sound Volume:===
{{Table371|
*Defines the default sound fx volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''1.0'''''}}

===$Default Music Volume:===
{{Table371|
*Defines the default music volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''0.5'''''}}

===$Default Voice Volume:===
{{Table371|
*Defines the default voice volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''0.7'''''}}

==#FRED SETTINGS==
Optional. This group contains settings for FRED. 

===$Disable Hard Coded Message Head Ani Files:===
{{table371|
If set, FRED will not fill the head ani selection in the Event Editor with the retail head ani filenames.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' }}

==#OTHER SETTINGS==
Optional. This group contains miscellaneous settings. 

===$Fixed Turret Collisions:===
Makes all hits to a turret's barrels count as hits to the turret subsystem. By default, this does not happen unless the point of impact falls inside the model radius of the turret's base.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Damage Impacted Subsystem First:===
If set, a hit to a physical subsystem will always deal damage to that subsystem first, even if another subsystem is closer to the point of impact. By default, the closest subsystem will always receive damage first.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Default ship select effect:===
{{Table3615|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Default weapon select effect:===
{{Table3615|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Weapons inherit parent collision group:===
{{Table3615|
*When set to true, Weapons fired by a ship will inherit their parents' collision group setting. Default is false.}}

===$Flight controls follow eyepoint orientation:===
{{Table371|
*Specifies that if the player ship's eyepoint happens to rotate into a non-standard orientation, pitch and yaw axes should stay relative to the eyepoint orientation, not the ship. Note that this does not affect the pitch/yaw turning speed, which always remains relative to the ship. Default is false.}}

===$Beams Use Damage Factors:===
{{Table371|
*Specifies that beam weapons will use the tabled damage factors for Armour, Shields and Subsystems. Default is false (i.e. all factors are treated as 1.0)}}

===$Default fiction viewer UI:===
{{Table373|
*Specifies which fiction viewer layout to use in missions that don't specify one. Possible values are as follows:
**"FS2": Standard layout. Requires (2_)fictionviewer and (2_)fictionviewer-m to be present in data\interface.
**"WCS": Moves the "Accept" button to the lower-left corner of the screen. Requires (2_)fictionviewerb and (2_)fictionviewer-mb to be present in data\interface.
**"auto": Selects "WCS" if the appropriate files are present; otherwise, selects "FS2". This is the default setting.}}

==#END==
Required. The last line of the table must be #END

==Sample Entry==

#CAMPAIGN SETTINGS
$Default Campaign File Name: NewCampaignFile

#Ignored Campaign File Names
$Campaign File Name: FreeSpace2.fc2

#HUD SETTINGS
$Directive Wait Time: 5000

#SEXP SETTINGS
$Loop SEXPs Then Arguments: True

#OTHER SETTINGS
$Fix Turret Collisions: True

#END

[[Category:Tables]]

Command-Line Reference

2017-11-20T22:25:40Z

AdmiralRalwood: /* Development Tools */ Adding -bmpmanusage.

{{TableVersionGit|2016-28-07|b40631e}}

Command-Line Flags (also called Command-Line Parameters) are optional flags passed to the FSO executable, and generally enables one or more features added to the FS2 Open engine. These flags are accessed conveniently through an [[FSO Launcher]]. To have FSO list all available flags, use any one of the following: [[Command-Line_Reference#-help|-help]], [[Command-Line_Reference#-help|--help]], [[Command-Line_Reference#-help|-h]], or [[Command-Line_Reference#-help|-?]].



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

Only polygons mapped with textures for which a shinemap exists will receive specular mapping; no attempt is made to generate spec maps where they do not exist. Specular maps are specified with the base map name plus "-shine" (i.e. TCov3A-shine.pcx).
{{Table3615|
*This feature is on by default, use launcher option Disable Specular or if necessary to manually disable enter the flag -nospec}}

====-env====
'''"Enable Environment maps"'''

It only works if [[Command-Line_Reference#-spec|-spec]] is also set. Environment mapping intensity will be determined from the shine map too (see [[Texturing]] for more info). [[Installing FreeSpace 2 Open#Video setup|See Video setup.]]
{{Table3615|
*This feature is on by default, use launcher option Disable Environment Maps or if necessary to manually disable enter the flag -noenv }}

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

Only polygons mapped with textures for which a glowmap exists will be glowmapped. Glow maps are specified with the base map name plus "-glow" (i.e. TCov4A-glow.pcx)
{{Table3615|
*This feature is on by default, use launcher option Disable Glow Maps or if necessary to manually disable enter the flag -noglow }}

====-nomotiondebris====
'''"Disable motion debris"'''

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

Disables fullscreen scaling of video clips.

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

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

Normal maps require GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary normal maps (the same name of the base map plus "-normal"). DXT5_NM DDS format is needed. (Technical note: DXT5 will work, since only the GREEN and ALPHA channels are read by the current shader system. One direction of lines goes into the GREEN channel, the other direction goes into the ALPHA channel. RED and BLUE can be either base gray (#808080) or black. Usual practice is after creating the DXT5_NM, copy the RED channel to the ALPHA channel, black out the RED and BLUE an then save as either a DXT5 or u8888 (uncompressed) DDS file.)
{{Table3615|
*This feature is on by default, use launcher option Disable Normal Maps or if necessary to manually disable enter the flag -nonormal }}

====-height====
Enables height maps (parallax mapping). It only works if [[Command-Line_Reference#-normal|-normal]] is also set. It also needs GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary height maps (with the same name than base map plus "-height").
{{Table3615|
*This feature is on by default. To manually disable, enter the flag -noheight}}

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

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

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

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

This only has any effect when both a 2D and 3D shockwave effect are present, otherwise the only available effect is used (2D shockwave is defined by effects/shockwave01.eff or .ani, and 3D shockwave by models/shockwave.pof)

Note that 3D shockwaves are usually flat discs that FSO scales up. The animated 2D billboards used by 2D shockwaves with the addition of [[Command-Line Reference#-soft_particles|soft particles]], may look better when intersecting with models (which shockwaves often do). Use at your discretion.

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

Enables the FXAA postprocessing stage. Further information can be found here: http://www.hard-light.net/forums/index.php?topic=76145.0

====-nolightshafts====
'''"Disable lightshafts"'''

Disables Lightshafts even if a mission designer enables them via SEXP in a mission. This was previously documented as -flightshaftsoff but appears to have been changed to -nolightshafts for consistency before -flightshaftsoff was ever used in a released build.

====-enable_shadows====
{{table373|
'''"Enable shadows"'''

Enables shadows where supported by the OpenGL version provided by the user's GPU. -shadow_quality can be used to control the quality level.
{{note|Currently doesn't support shadows for cockpits and show ship.}}
}}

====-shadow_quality====
{{table373|
'''"Set shadows quality"'''

Valid ranges are 0 to 2 with 2 being the default.

* 0 disables shadows (so there's no point in setting it!)
* 1 uses 512x512 shadow maps (lower quality)
* 2 uses 1024x1024 shadow maps (higher quality)

Currently this requires -enable_shadows to be set, or it has no effect.
}}
{{table38|No longer requires -enable_shadows to be set.}}

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

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

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

====-no_fps_capping====
'''"Don't limit frames-per-second"'''

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

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

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

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

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

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

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

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

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

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

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

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

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

Uses ship models in ship selection window. It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their ships. In this situation, and if it is not used, the game will probably crash to desktop in the ship selection window.

====-weapon_choice_3d====
'''"Use Models for Weapon Selection"'''

Uses weapon models in weapon loadout window for secondary weapons (missiles and bombs). It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their secondary weapons. In this situation, and if it is not used, the game will probably crash to desktop in the weapon loadout window.

====-3dwarp====
'''"Enable 3D Warp"'''

Use full geometry for the subspace warp effect.

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

Enable a flash at warp in and warp out.

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

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

====-stretch_menu====
'''"Stretch interface to fill screen"'''

Scales the interface to fill the screen without preserving the aspect ratio. Omit this to keep the aspect ratio, adding black bars where appropriate.

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

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

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

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

===Launcher===
====-portable_mode====
'''"Store config in portable location"'''

Uses the root directory of FSO for storing pilot and config files. The current launcher does not have proper support for this yet so you need to manually copy the fs2_open.ini from the original config directory to your FreeSpace Root directory.

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

Creates a standalone multi-player server.

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

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

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

====-closed====
'''"Start Hosted Server as Closed"'''

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

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

====-restricted====
'''"Host Confirms Join requests"'''

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

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

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

====-clientdamage====
{{Note| This feature is not available in current builds.}}

====-mpnoreturn====
'''"Disables Flight Deck option"'''

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

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

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

Disables the gamma settings in the options screen.

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

Disables all video playback.

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

Disables some parsing warnings and makes other parse errors non-fatal. Do not rely on this when creating new tables. The errors are there for a reason.

====-parse_cmdline_only====
'''"Parse Command Line Only"'''

Parse only the application command line settings, and ignore any that may have been set in the on-disk data/cmdline_fso.cfg or per-user cmdline_fso.cfg (on Linux/Mac)

====-safeloading====
Loads missions the old way. Typically safer, but slower.
{{Note| This parameter was removed as of the July 5, 2011 nightly build.}}

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

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

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

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

Disables IBX caching of model geometry data. This will dramatically increase load times, but will help troubleshoot a model if one is working incorrectly.

====-loadallweps====
'''"Load all weapons, even those not used"'''

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

====-disable_pbo====
'''"Disable OpenGL Pixel Buffer Objects"'''

Disables the use of Pixel Buffer Objects (PBO) which may cause certain OpenGL operations to perform slower. Note PBO's were only used at three places in FSO anyway so it's *probably* not going to have a noticeable effect.

May be required to workaround issues in certain versions of Linux's Mesa drivers for Intel integrated graphics cards where crashes occur in the mainhall (i.e. whenever a popup occurs). Distros that seem to have this problem presently include Ubuntu 13.10 and openSUSE 13.1.
{{Table371|
*This feature is present to work around a bug in Linux's Mesa drivers for Intel integrated graphics cards}}

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

Disables the use of GLSL rendering (OpenGL shaders). The game will revert to legacy fixed render pipeline. Please note that Normal and Height map effects will be unavailable.

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

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

[http://scp.indiegames.us/mantis/view.php?id=1669 Mantis #1669] is what led to this flag's creation.

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

====-disable_di_mouse====
'''"Disables the DirectInput mouse code for FSO on windows."'''

'''Windows Only''' Can make mouse movement smoother on certain machines.

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

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

====-use_gldrawelements====
'''"Use glDrawElements instead of glDrawRangeElements"'''

Introduced as a means of switching to the slower OpenGL call glDrawElements, instead of glDrawRangeElements.
{{Table3614|
*This feature may resolve certain rendering problems where parts of models are not drawn on Linux drivers}}

====-keyboard_layout====
'''"Manually sets a keyboard layout"'''

A commandline parameter to set the keyboard layout as a string parameter.
{{Table3614|
*Currently the only valid string is "qwertz" (German) but French azerty may be added in future.}}

====-old_collision====
'''"Use old collision detection system"'''

Uses the old collision code instead of Swifty's new collision code introduced in the 'go_even_faster' project.

====-gl_finish====
'''"Fix input lag on AMD+Linux"'''
{{Table371|
This option adds a "glFinish()" call just prior to swapping buffers. It works around an issue with "recent" (HD 6000 & newer?) AMD cards using proprietary drivers on Linux. Be warned that enabling this may reduce framerate.
}}

Refer to [http://www.hard-light.net/forums/index.php?topic=88102.0 this thread] and [https://github.com/ValveSoftware/Source-1-Games/issues/765 Valve's bugtracker] for more details).

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

Enables ingame joining in multiplayer. FIXME: Host option?

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

Windows-only. Enables voice-recognition for wingmen commands. Must be specifically compiled into a build in order for it to be available; 3.6.10 final includes the feature. See [[Voice Recognition]] for more details.

====-fb_explosions====
'''"Enable Framebuffer Shockwaves"'''

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

Displays current frames per second.

====-bmpmanusage====
'''"Show how many BMPMAN slots are in use"'''

Adds a BMPMAN slot usage display near where the FPS display is (or would be, if it's not enabled). Can be used by mod makers to see if they need to increase their [[Game_settings.tbl#$BMPMAN Slot Limit:|BMPMAN slot limit]].

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

Displays current position coordinates of camera.

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

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

====-fullscreen_window====
'''"Run in Fullscreen Window"'''
{{Note| This feature is only available on Windows.}}

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

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

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

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

Shows coordinates of the mouse cursor.

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

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

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

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

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

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

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

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

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

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

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

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

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

Disables all collisions.

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

Disables weapons rendering.

====-output_sexps====
This will make the FSO build spit out an html file that documents the supported SEXP's.

Just double click on sexps.html and it should open in your default web browser.

====-output_scripting====
This will make the FSO build spit out an html file that documents the supported scripting hooks and LUA libraries.

Just double click on scripting.html and it should open in your default web browser.

====-nograb====
Disables focus grabbing in a window.
{{Note| This feature is not available on Windows.}}

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

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

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

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

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

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

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

====-profile_frame_time====
'''"Profile engine subsystems"'''

Activates the frame profiling code. This presents a readout showing the current, minimum, maximum and average percentages of frametime a given section of code has taken up; this can be used to identify particular bottlenecks or measure the effectiveness of certain optimizations.

====-profile_write_file====
'''"Write profiling information to file"'''

This will write the frame times of each gameplay frame to the file 'profiling.csv' where each line is ''<time>;<frametime>''. Both times are measured in microseconds. ''time'' is measured from an arbitrary time in the past. To get consistent results the first ''time'' value should be substracted from all ''time'' values. The first two frames are usually very long because the timer is set at engine startup so you might want to exclude those from your data.

====-no_unfocused_pause====
'''"Don't pause if the window isn't focused"'''

When the FSO window looses focus it will not pause the game, useful for doing non-interactive test runs.

====-benchmark_mode====
'''"Puts the game into benchmark mode"'''
See [[Benchmarking]] for more information.

====-noninteractive====
'''"Disables interactive dialogs"'''
Disables all dialogs and chooses the default option when one would be displayed. Very useful for a standalone server on a headless system.

==Other==
The following options are not available as checkboxes in the launcher. Many require parameters, which follow the flag separated by a space. The prototype for use in this case is "-option argument"

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

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

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

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

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

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

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

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

===Graphics===
====-bloom_intensity====
Requires -post_processing ("Enable Post Processing") command.
Default value is 75. Range is 0-200.

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

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

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

====-center_res====
Specifies how much of the screen area should be utilized by menus, movies, the HUD, and various other 2D graphics. Intended for use with configurations with an extremely wide field of view, such as triple-monitor setups.

By default, if the screen resolution's aspect ratio is wider than 7:2, most 2D elements utilize only the center 3/10 of the screen area. This setting allows users to override this behavior to make better use of the center monitor. (The reason for using 3/10 rather than 1/3 is that many triple-monitor setups use bezel correction, which reduces the fraction of the screen area that the center monitor displays.)

For example, if the screen resolution is 6000x1080, then -center_res 1920x1080 will keep most 2D graphics in the center 1920x1080 area. This setting is automatically scaled to fit the screen resolution, so (assuming the resolution is still 6000x1080) -center_res 1280x720 is given, then that resolution is enlarged to 1920x1080.

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

===Gameplay===
====-start_mission====
'''"Skip the mainhall in jump right into the specified mission"'''

Jump into the mission specified by the filename. Only in effect on the first run. This will skip load of the mainhall and its other related things altogether.

====-mod====
Specifies in which folders inside FreeSpace 2 directory, the game looks for all the game data (models, missions, textures, tables, ...). Retail version only looks inside ''Freespace2/data/'' structure and ''Freespace2/vp archives''.

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

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

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

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

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

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

'''Data precedence'''

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

Inside each directory, data precedence is the following:

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

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

'''Additional notes'''
# As derived from the explanation, the exact names for directories or vp archives are actually irrelevant. It only matters the directory order inside -mod flag argument and the alphabetical order for vp archives inside each used directory.
# This flag is also used by [[Portal:FRED|FRED]]. So if there is special mod info, (like backgrounds maps, ship models or whatever), it must be typed, (''Fred2_Open_r.exe -MOD whatever''), or FRED won't be able to use it. A special build of wxLauncher is able to configure FRED so that the -mod doesn't have to be done manually see [http://www.hard-light.net/forums/index.php?topic=67950.msg1387911#msg1387911 the forum post] for more details.
{{Table3612|As of 3.6.12 FRED now loads cmdline_fso.cfg just like FS does so FRED will use the same settings as FS including the -mod settings}}
# Be careful while typing the directory names in the flag argument or inside mod.ini files. The program doesn't check if the typed directories exist. If they do not exist, they are just ignored. No warnings, no errors, no messages at all.

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

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

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

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

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

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

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

}}

====-fov====
This flag allows the player to specify the ''vertical'' Field of View (FoV) angle, in radians, for the player eyepoint. The angle is measured across the full height of the viewing cone. The FoV angle is technically known as the Angle of View (AoV)

*Syntax: '''''float''''' Angle
*Valid Values: 0 to 2*Pi radians
*Default Value: 0.75 radians

{{Note|For peculiar reasons, the actual FoV/AoV used by the game will be the supplied value multiplied by 1.39626348.}}

The the FoV angle/AoV is what determines the relative zoom level of the main game camera. Smaller angles generally equal to higher zoom levels, while larger angles equal to lower zoom levels (down to the theoretical x0 magnification).

However, too small of an angle will have a squashed look on the edges of your screen, and too high of an angle will greatly stretch edges. It is recommended to change the AoV, as FS2's default AoV has some perspective distortion at the screen edges (the default AoV is too high).

A natural looking (as if you where physically in the cockpit) AoV depends on the distance the player's actual eyes are away from the screen: the further away from the screen, the smaller the AoV should be, and vice versa. "Ergonomic" distances generally yield a '''''diagonal''''' AoV of 0.523 radians (30 degrees), but you can easily find the natural AoV by the following formula:

AoV (radians) = 2 * atan( H / ( 2*D ))

where:

Height of screen = H

Distance between head/eye and the screen = D

Generally, gamers like to increase the AoV in order to increase their peripheral vision on the screen, so as to gain a better situational awareness around their craft. An AoV of 0.39 radians seems to be a good start, but feel free to experiment and use whatever AoV you are most comfortable with.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

====-connect====
Automatically connect to multiplayer IP:PORT.

Takes one string value, such as 192.168.0.1:

====-timeout====
Multiplayer network timeout (secs).

Takes one integer argument, the timeout value in seconds. Default is 30.

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

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

===Help===
====-help====
Instructs FSO to print out all supported parameters. Some launchers can use these options to automatically populate the available command line options, even if the version of FSO is far newer than the launcher itself. NOTE: This option only works in Linux builds...

====--help====
See [[Command-Line_Reference#-help|-help]]

====-h====
See [[Command-Line_Reference#-help|-help]]

====-?====
See [[Command-Line_Reference#-help|-help]]

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

Game settings.tbl

2017-11-17T12:20:56Z

AdmiralRalwood: Adding "$Window title:"

{{SCP_table}}

{{TableVersionGit|2015-11-21|71cf169}}

The '''game_settings.tbl''', also known as mod.tbl, defines options that can be changed globally.

This table is one of the [[Modular Tables]] and can be extended with xxx-mod.tbm

[[Tables|List of Tables]]

==#GAME SETTINGS==
Optional. Contains settings that affect how the engine works. 

===$Target Version:===
{{Table373|
Specifies the minimum version of FreeSpace Open that this mod supports. If the version specified here is greater than the version of the current build, an error message is displayed.
}}
{{Table381|
The $Minimum version option has been renamed to $Target Version. The old name is kept with the same functionality for backwards-compatibility.

The target version specifies what version of the FSO engine this mod was created for. It will be used by the engine to enable or disable backwards-incompatible changes by default. The default value is 2.0 which specifies that the mod targets the retail engine version.
}}

====+Major:====
{{Table373|
Required. Sets the major component of the target version.
*Syntax: '''''Integer''''' 
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Minor:====
{{Table373|
Required. Sets the minor component of the target version.
*Syntax: '''''Integer''''' 
*Example: '''''7''''' (for a minimum version of 3.7.3.20151121)
}}

====+Build:====
{{Table373|
Required. Sets the build component of the target version.
*Syntax: '''''Integer''''' 
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Revision:====
{{Table373|
Optional. Sets the revision component of the target version. If no revision is given then all builds of that release are supported (even nightly builds if there are any).
For nightly builds this is the date in YYYYMMDD format.
*Syntax: '''''Integer''''' 
*Example: '''''20151121''''' (for a minimum version of 3.7.3.20151121)
}}

===$Window title:===
{{Table382|
Specifies the name of the FSO window when this mod is running. If blank or unspecified, the window will have the default title of "FreeSpace 2".
*Syntax: '''''String'''''
}}

==#CAMPAIGN SETTINGS==
Optional. This group contains various Campaign related settings and overrides. 

===$Default Campaign File Name:===
Defines which campaign will be selected by default for new pilots. A file extension is not needed and, if present, is removed by the code.
*Syntax: '''''String''''' 

===#Ignored Campaign File Names===
Optional. Defines which campaigns, if present, will not appear in the Campaign Room. Only single-player campaigns can be ignored. ''File extensions are required.''
{{Table371|As of 3.7.1, file extensions are not required and, if present, are removed by the code.}}
====$Campaign File Name:====
File name of the campaign to ignore. Multiple entries may exist.
*Syntax: '''''String''''' 

===$Red-alert applies to delayed ships:===
Controls whether red-alert saved statistics (hitpoints, weapons, subsystem strengths) will be restored for ships that are not present at mission start.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

==#HUD SETTINGS==
Optional. This group contains various HUD behavior settings and overrides 

===$Directive Wait Time:===
*Defines how long the game will wait before displaying a directive.
*Syntax: '''''Integer''''' 
*Values: '''''Greater than or equal to 0 ms'''''

===$Cutscene camera displays HUD:===
Show the HUD when the cutscene camera is enabled.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Cutscene camera disables HUD: and had a default of YES.

===$Full color head animations:===
Enables full-color head ANIs. Normal head ANIs will appear in gray.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Color head animations with hud colors: and had a default of YES.

==#SEXP SETTINGS==
Optional. This group contains SEXP settings and overrides. 

===$Loop SEXPs Then Arguments:===
Flips how when-argument settings loop. See: [http://www.hard-light.net/forums/index.php?topic=79602.0 SEXP Argument changes via mod.tbl]
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

===$Use Alternate Chaining Behavior:===
When set, this makes the event chaining behavior act as people expected it to be in [http://scp.indiegames.us/mantis/view.php?id=82 Mantis #82].
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

==#GRAPHICS SETTINGS==
Optional. This group contains settings related to graphics. 

===$Enable External Shaders:===
Enables the use of external shader files. By default, the engine will use the built-in shaders.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Default Detail Level:===
{{Table3615|
Determines which graphics detail level preset (low, medium, high, very high) acts as the default for new pilots.
*Syntax: '''''Integer''''' (0-3)
*Default Value: '''''3''''' (very high) }}

===$Briefing Window FOV:===
{{Table371|
Determines the FOV in the briefing Icon window. Retail default for this is 0.29375, previous versions of FSO used a value of 0.5.
*Syntax: '''''Float''''' (0.0 to 1.0)
*Default Value: '''''0.29375''''' }}

===$Generic Pain Flash Factor:===
{{Table373|
Determines the intensity of the pain red flash when the player is hit.
*Syntax: '''''Float'''''
*Default Value: '''''1.0''''' }}

===$Shield Pain Flash Factor:===
{{Table373|
Determines the intensity of a pain flash when the player's shields are hit. Color will match the current ships shield color defined in ships.tbl. A value of 0 will give retail behavior (no shield effect). Positive values will cause the effect to start at full intensity at full shields and go to next to no intensity at zero shields. Negative values will cause no effect at full shields and full effect at no shields. Values should be kept between -1.0 and 1.0 for good pilot visibility.
*Syntax: '''''Float'''''
*Default Value: '''''0.0''''' }}

===$BMPMAN Slot Limit:===
{{Table382|
Determines the maximum number of textures that can be loaded simultaneously. This includes every frame of an animation, unless that animation is streaming (e.g. command briefing animations, message talking heads, etc). Also includes dynamically-created textures (used internally for various functions).
*Syntax: '''''Int'''''
*Values: '''''Greater than or equal to 3500'''''
*Default Value: '''''3500''''' }}

==#SOUND SETTINGS==
Optional. This group contains sound-related settings 

===$Default Sound Volume:===
{{Table371|
*Defines the default sound fx volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''1.0'''''}}

===$Default Music Volume:===
{{Table371|
*Defines the default music volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''0.5'''''}}

===$Default Voice Volume:===
{{Table371|
*Defines the default voice volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''0.7'''''}}

==#FRED SETTINGS==
Optional. This group contains settings for FRED. 

===$Disable Hard Coded Message Head Ani Files:===
{{table371|
If set, FRED will not fill the head ani selection in the Event Editor with the retail head ani filenames.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' }}

==#OTHER SETTINGS==
Optional. This group contains miscellaneous settings. 

===$Fixed Turret Collisions:===
Makes all hits to a turret's barrels count as hits to the turret subsystem. By default, this does not happen unless the point of impact falls inside the model radius of the turret's base.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Damage Impacted Subsystem First:===
If set, a hit to a physical subsystem will always deal damage to that subsystem first, even if another subsystem is closer to the point of impact. By default, the closest subsystem will always receive damage first.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Default ship select effect:===
{{Table3615|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Default weapon select effect:===
{{Table3615|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Weapons inherit parent collision group:===
{{Table3615|
*When set to true, Weapons fired by a ship will inherit their parents' collision group setting. Default is false.}}

===$Flight controls follow eyepoint orientation:===
{{Table371|
*Specifies that if the player ship's eyepoint happens to rotate into a non-standard orientation, pitch and yaw axes should stay relative to the eyepoint orientation, not the ship. Note that this does not affect the pitch/yaw turning speed, which always remains relative to the ship. Default is false.}}

===$Beams Use Damage Factors:===
{{Table371|
*Specifies that beam weapons will use the tabled damage factors for Armour, Shields and Subsystems. Default is false (i.e. all factors are treated as 1.0)}}

===$Default fiction viewer UI:===
{{Table373|
*Specifies which fiction viewer layout to use in missions that don't specify one. Possible values are as follows:
**"FS2": Standard layout. Requires (2_)fictionviewer and (2_)fictionviewer-m to be present in data\interface.
**"WCS": Moves the "Accept" button to the lower-left corner of the screen. Requires (2_)fictionviewerb and (2_)fictionviewer-mb to be present in data\interface.
**"auto": Selects "WCS" if the appropriate files are present; otherwise, selects "FS2". This is the default setting.}}

==#END==
Required. The last line of the table must be #END

==Sample Entry==

#CAMPAIGN SETTINGS
$Default Campaign File Name: NewCampaignFile

#Ignored Campaign File Names
$Campaign File Name: FreeSpace2.fc2

#HUD SETTINGS
$Directive Wait Time: 5000

#SEXP SETTINGS
$Loop SEXPs Then Arguments: True

#OTHER SETTINGS
$Fix Turret Collisions: True

#END

[[Category:Tables]]

Game settings.tbl

2017-11-12T08:22:18Z

AdmiralRalwood: Adding "$BMPMAN Slot Limit:".

{{SCP_table}}

{{TableVersionGit|2015-11-21|71cf169}}

The '''game_settings.tbl''', also known as mod.tbl, defines options that can be changed globally.

This table is one of the [[Modular Tables]] and can be extended with xxx-mod.tbm

[[Tables|List of Tables]]

==#GAME SETTINGS==
Optional. Contains settings that affect how the engine works. 

===$Target Version:===
{{Table373|
Specifies the minimum version of FreeSpace Open that this mod supports. If the version specified here is greater than the version of the current build, an error message is displayed.
}}
{{Table381|
The $Minimum version option has been renamed to $Target Version. The old name is kept with the same functionality for backwards-compatibility.

The target version specifies what version of the FSO engine this mod was created for. It will be used by the engine to enable or disable backwards-incompatible changes by default. The default value is 2.0 which specifies that the mod targets the retail engine version.
}}

====+Major:====
{{Table373|
Required. Sets the major component of the target version.
*Syntax: '''''Integer''''' 
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Minor:====
{{Table373|
Required. Sets the minor component of the target version.
*Syntax: '''''Integer''''' 
*Example: '''''7''''' (for a minimum version of 3.7.3.20151121)
}}

====+Build:====
{{Table373|
Required. Sets the build component of the target version.
*Syntax: '''''Integer''''' 
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Revision:====
{{Table373|
Optional. Sets the revision component of the target version. If no revision is given then all builds of that release are supported (even nightly builds if there are any).
For nightly builds this is the date in YYYYMMDD format.
*Syntax: '''''Integer''''' 
*Example: '''''20151121''''' (for a minimum version of 3.7.3.20151121)
}}

==#CAMPAIGN SETTINGS==
Optional. This group contains various Campaign related settings and overrides. 

===$Default Campaign File Name:===
Defines which campaign will be selected by default for new pilots. A file extension is not needed and, if present, is removed by the code.
*Syntax: '''''String''''' 

===#Ignored Campaign File Names===
Optional. Defines which campaigns, if present, will not appear in the Campaign Room. Only single-player campaigns can be ignored. ''File extensions are required.''
{{Table371|As of 3.7.1, file extensions are not required and, if present, are removed by the code.}}
====$Campaign File Name:====
File name of the campaign to ignore. Multiple entries may exist.
*Syntax: '''''String''''' 

===$Red-alert applies to delayed ships:===
Controls whether red-alert saved statistics (hitpoints, weapons, subsystem strengths) will be restored for ships that are not present at mission start.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

==#HUD SETTINGS==
Optional. This group contains various HUD behavior settings and overrides 

===$Directive Wait Time:===
*Defines how long the game will wait before displaying a directive.
*Syntax: '''''Integer''''' 
*Values: '''''Greater than or equal to 0 ms'''''

===$Cutscene camera displays HUD:===
Show the HUD when the cutscene camera is enabled.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Cutscene camera disables HUD: and had a default of YES.

===$Full color head animations:===
Enables full-color head ANIs. Normal head ANIs will appear in gray.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Color head animations with hud colors: and had a default of YES.

==#SEXP SETTINGS==
Optional. This group contains SEXP settings and overrides. 

===$Loop SEXPs Then Arguments:===
Flips how when-argument settings loop. See: [http://www.hard-light.net/forums/index.php?topic=79602.0 SEXP Argument changes via mod.tbl]
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

===$Use Alternate Chaining Behavior:===
When set, this makes the event chaining behavior act as people expected it to be in [http://scp.indiegames.us/mantis/view.php?id=82 Mantis #82].
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

==#GRAPHICS SETTINGS==
Optional. This group contains settings related to graphics. 

===$Enable External Shaders:===
Enables the use of external shader files. By default, the engine will use the built-in shaders.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Default Detail Level:===
{{Table3615|
Determines which graphics detail level preset (low, medium, high, very high) acts as the default for new pilots.
*Syntax: '''''Integer''''' (0-3)
*Default Value: '''''3''''' (very high) }}

===$Briefing Window FOV:===
{{Table371|
Determines the FOV in the briefing Icon window. Retail default for this is 0.29375, previous versions of FSO used a value of 0.5.
*Syntax: '''''Float''''' (0.0 to 1.0)
*Default Value: '''''0.29375''''' }}

===$Generic Pain Flash Factor:===
{{Table373|
Determines the intensity of the pain red flash when the player is hit.
*Syntax: '''''Float'''''
*Default Value: '''''1.0''''' }}

===$Shield Pain Flash Factor:===
{{Table373|
Determines the intensity of a pain flash when the player's shields are hit. Color will match the current ships shield color defined in ships.tbl. A value of 0 will give retail behavior (no shield effect). Positive values will cause the effect to start at full intensity at full shields and go to next to no intensity at zero shields. Negative values will cause no effect at full shields and full effect at no shields. Values should be kept between -1.0 and 1.0 for good pilot visibility.
*Syntax: '''''Float'''''
*Default Value: '''''0.0''''' }}

===$BMPMAN Slot Limit:===
{{Table382|
Determines the maximum number of textures that can be loaded simultaneously. This includes every frame of an animation, unless that animation is streaming (e.g. command briefing animations, message talking heads, etc). Also includes dynamically-created textures (used internally for various functions).
*Syntax: '''''Int'''''
*Values: '''''Greater than or equal to 3500'''''
*Default Value: '''''3500''''' }}

==#SOUND SETTINGS==
Optional. This group contains sound-related settings 

===$Default Sound Volume:===
{{Table371|
*Defines the default sound fx volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''1.0'''''}}

===$Default Music Volume:===
{{Table371|
*Defines the default music volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''0.5'''''}}

===$Default Voice Volume:===
{{Table371|
*Defines the default voice volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''0.7'''''}}

==#FRED SETTINGS==
Optional. This group contains settings for FRED. 

===$Disable Hard Coded Message Head Ani Files:===
{{table371|
If set, FRED will not fill the head ani selection in the Event Editor with the retail head ani filenames.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' }}

==#OTHER SETTINGS==
Optional. This group contains miscellaneous settings. 

===$Fixed Turret Collisions:===
Makes all hits to a turret's barrels count as hits to the turret subsystem. By default, this does not happen unless the point of impact falls inside the model radius of the turret's base.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Damage Impacted Subsystem First:===
If set, a hit to a physical subsystem will always deal damage to that subsystem first, even if another subsystem is closer to the point of impact. By default, the closest subsystem will always receive damage first.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Default ship select effect:===
{{Table3615|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Default weapon select effect:===
{{Table3615|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Weapons inherit parent collision group:===
{{Table3615|
*When set to true, Weapons fired by a ship will inherit their parents' collision group setting. Default is false.}}

===$Flight controls follow eyepoint orientation:===
{{Table371|
*Specifies that if the player ship's eyepoint happens to rotate into a non-standard orientation, pitch and yaw axes should stay relative to the eyepoint orientation, not the ship. Note that this does not affect the pitch/yaw turning speed, which always remains relative to the ship. Default is false.}}

===$Beams Use Damage Factors:===
{{Table371|
*Specifies that beam weapons will use the tabled damage factors for Armour, Shields and Subsystems. Default is false (i.e. all factors are treated as 1.0)}}

===$Default fiction viewer UI:===
{{Table373|
*Specifies which fiction viewer layout to use in missions that don't specify one. Possible values are as follows:
**"FS2": Standard layout. Requires (2_)fictionviewer and (2_)fictionviewer-m to be present in data\interface.
**"WCS": Moves the "Accept" button to the lower-left corner of the screen. Requires (2_)fictionviewerb and (2_)fictionviewer-mb to be present in data\interface.
**"auto": Selects "WCS" if the appropriate files are present; otherwise, selects "FS2". This is the default setting.}}

==#END==
Required. The last line of the table must be #END

==Sample Entry==

#CAMPAIGN SETTINGS
$Default Campaign File Name: NewCampaignFile

#Ignored Campaign File Names
$Campaign File Name: FreeSpace2.fc2

#HUD SETTINGS
$Directive Wait Time: 5000

#SEXP SETTINGS
$Loop SEXPs Then Arguments: True

#OTHER SETTINGS
$Fix Turret Collisions: True

#END

[[Category:Tables]]

Engine limitations

2017-11-12T08:07:34Z

AdmiralRalwood: BMPMAN limit is now moddable

The maximum numbers of certain types of entities that can exist in the FS2_Open engine. Please note that 'Inferno' refers to INF builds, which are standard from 3.6.12 on.

==General==
The overall limits of the various subsystem managers.
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505;"| '''Limit'''
|- align="center"
| Textures
| 4750 {{Table382|Mod-defined}}
|- align="center"
| Sound tracks
| 30
|- align="center"
| Sounds
| No Limit
|}

==Tables==
The maximum types of an entity that can exist in the table

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=3 style="background:#300505;"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
| style="background:#300505; width:75px"| '''3.7.4'''
|- align="center"
| [[Ships.tbl|Ship Classes]]
| 130
| 250
| 500
|- align="center"
| [[Weapons.tbl|Weapon Classes]]
| 200
| colspan=2| 300
|- align="center"
| Beam Sections
| colspan=3| 5
|- align="center"
| Pspews Per Weapon
| colspan=3| 4
|- align="center"
| [[Objecttypes.tbl|Object Types]]
| colspan=3| 16
|- align="center"
| [[Iff_defs.tbl|IFFs]]
| colspan=3|10
|- align="center"
| [[Ai_profiles.tbl|AI Profiles]]
| colspan=3| 5
|- align="center"
| [[Hud_gauges.tbl|Hud Gauges]]
| colspan=3| 64
|- align="center"
| [[Species.tbl|Intelligence Entries]]
| colspan=3| 75
|- align="center"
| Debriefing
| colspan=3| 2,000 Characters per Stage
|}

Please Note - Prior to r11156, there was a hardcoded limit of 32 [[Modular Tables|‎ .tbm files]] of any given type that the game would recognize.

==Objects==
The maximum number of objects that can exist in a mission at any given time (except for ships and waypoints, which apply to the whole mission).

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Objects
| 2000 {{Table3615|3500}}
|- align="center"
| Ships
| 400
|- align="center"
| Weapons
| 700 {{Table3615|2000}}
|- align="center"
| Beams
| 500
|- align="center"
| Waypoints Per Path
| 20 {{Table3613|Limit Removed}}
|- align="center"
| Waypoint Paths
| 32 {{Table3613|Limit Removed}}
|}

==Wings==
The maximum number wings or ships in a wing that can exist

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Wings
| 75
|- align="center"
| Ships per Wing
| 6
|- align="center"
| Starting Wings
| 3
|- align="center"
| Squadron Wings
| 5
|- align="center"
| TvT Teams
| 2
|- align="center"
| TvT Wings per Team
| 1
|- align="center"
| TvT Wings
| 2
|}

==Models==
The maximum number of models that can exist at one time

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| Polygon Models
| 128
| 300
|}

The maximum number of a certain entity that can exist within a model

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Textures
| 64
|- align="center"
| Ship Primary Banks
| 3
|- align="center"
| Ship Secondary Banks
| 4
|- align="center"
| Firing Points Per-Bank
| 25
|- align="center"
| Debris Chunks
| 64
|}

==Sub-Weapon Types==

The maximums for the sub types of weapons.

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Type'''
| style="background:#300505; width:75px"| '''Max Instances'''
|- align="center"
| Corkscrew Missiles
| 200
|- align="center"
| Swarm Missiles
| 100
|}

[[Category:Source Code Project]]
[[Category:Modding]]

Weapons.tbl

2017-08-24T12:09:21Z

AdmiralRalwood: Adding pulsed countermeasures.

{{TableVersionGit|2017-08-25|2039815}}

The '''weapons.tbl''' defines all of the weapon classes used in FSO.

This table is one of the [[Modular Tables]] and can be extended with xxx-wep.tbm

[[Tables|List of Tables]]

==Introduction==
The weapons.tbl is responsible for defining the behavior of the numerous weapon effects used in FSO, including the amount of damage dealt, the firing rate, and graphical effects.

This wiki page goes over all of the entries used exclusively in the weapons.tbl file. Hyperlinks to individual weapon creation/editing tutorials are provided when appropriate.

==Special Case Weapons==
===Beam Cannons===
'''REQUIRES:'''
*'''"beam"''' flag
*'''[[weapons.tbl#$BeamInfo:|$BeamInfo:]]'''

See also: [http://www.hard-light.net/wiki/index.php/Tutorial_-_Beam_Weapons Tutorial - Beam Weapons]

===Flak Guns===
'''REQUIRES:'''
*'''"flak"''' flag
*'''"particle spew"''' flag
*Must have inner and outer radius defined to have any effect.
*A '''.pof''' model must be defined ( usually '''Hornet.pof''' )
**Note: the model is not actually used... Instead, it uses [[Weapons.tbl#$Pspew:|particle spew]]. Trails may also be added.

==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. Two special characters can be used in the name: '''#''' and '''@'''. Their usage details are the very same than inside the [[Ships.tbl#.24Name:_2|$Name field from Ships.tbl]].
*Syntax: '''''String'''''

====+nocreate====
{{Table3610|
*In [[Modular Tables]] name can be followed by line '''+nocreate''' that prevent game from creating an incomplete entry by leaving the entry unread unless it already exists (either in Weapons.tbl or in earlier parsed *-wep.tbm files) by the time the *-wep.tbm is read.}}

===$Alt Name:===
{{Table3611|
*An alternative name that can be referenced instead of $Name:
*Syntax: '''''String'''''}}

===$Subtype:===
{{Table3610|
Specifies the weapon 's subtype. Overrides the default subtype as specified by the #-section it is in (#Primary, #Secondary, #Beam Weapon, etc.).

{{Note|
:Since the weapon subtype is already specified by the #-section it is in, this option is not particularly useful when the weapon is inside a #Primary or #Secondary section. However, it may be used to specify the weapon slot it uses on fighters/bombers for weapons that are normally capship only (such as beam cannons).}}

*Syntax: '''''String'''''
*Valid Entries:
:Primary
:Secondary}}

===+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]]
*Must be followed by '''$end_multi_text'''

'''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]]
*Must be followed by '''$end_multi_text'''

'''Example'''

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

===$Tech Model:===
{{Table3610|
*Defines model used in wing loadout screen for the weapon. 3D weapon models in the tech room have not yet been implemented.
*Syntax: '''''String.pof''''', model filename}}

====+Closeup_Pos:====
{{Table3613|
*How the model will show on the Loadout Screen. The position of the camera relative to the model center.
*Syntax: '''''Vector''''', three '''floats''', x, y and z values respectively}}

====+Closeup_Zoom:====
{{Table3613|
*How the model will show on the Loadout Screen. How far the camera's zoomed in, defines camera's FOV.
*Syntax: '''''Float''''', radians}}

===$Selection Effect:===
{{Table3613|
*Defines which selection effect to use when the -weapon_choice_3d commandline flag is enabled or no ani can be found for the selected weapon.
*Syntax: '''''String''''', either "FS1", or "Off". This defaults to the FS2 effect.
}}

===$HUD Image:===
{{Table3610|
*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:===
{{Table3610|
*Defines the LOD (Level-Of-Detail) of the model used in HUD targeting view
*Syntax: '''''Integer'''''}}

===$Detail Distance:===
{{Table3613|
*Defines the distance where the change between different Levels-Of-Details (LODs) occurs
*Take notice that these are base values. Model detail in Detail options, (within game press F2), applies a multiplier to these values. These multipliers are (from left to right): 1/8, 1/4, 1, 4, 8
*Optional. If not defined the game uses the formula ((radius * 20.0 + 20.0) * LOD)
*Syntax: '''''(Detail Distances)''''' , list of '''integers''' (same amount as LODs), distances from the model in meters
**Example: ''(0, 80, 300, 900)''}}

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

===$Submodel Rotation Speed:===
{{Table3610|
*Defines the rotation speed of the subobject, with the $gun_rotation property defined, in the external weapon model.
*Syntax: '''''Float'''''
*Note: weapon fire will be delayed by the time it takes for the weapon to spin up to this speed (using $Submodel Rotation Acceleration or its default value), regardless of whether an external model is used or not.
}}
{{Table38|
*Note: It's no longer required that the ship actually have external models enabled (whether or not this weapon has one defined) for the spin up delay to occur.
}}

===$Submodel Rotation Acceleration:===
{{Table3610|
*Defines the rotation acceleration of the external weapon model.
*Syntax: '''''Float'''''
*Default value: 10}}

===@Laser===
In the event a 3D model is not defined for the weapon, FSO creates an object similar to a glowpoint. Essentially, it is a 2D plane that always faces the player's camera with an additive texture applied to it, and may or may not have an omnilight follow it.

As suggested by its name, this option group is normally used for lasers and similar primaries, but it may also be used for other weapon types as well.

Unless said otherwise, the graphic files used within this group may be of any compatible type (.DDS, .PCX, .TGA, etc.), however a .DDS is recommended.

====@Laser Bitmap:====
Defines the graphic file to be used as the weapon effect.

Blending type: additive

Syntax: '''''String''''', filename

'''Example:'''
<pre>
@Laser Bitmap: my_laser_bitmap
</pre>

====@Laser Glow:====
Defines the graphic file to be used for the glowmap of the weapon effect.

Blending type: additive

*This file is 'multiplied' by a value between Color and Color2.
*The physical dimensions of the glowmap in-game is 2x the size of the bitmap.

Syntax: '''''String''''', filename

'''Example:'''
<pre>
@Laser Glow: my_laser_glowmap
</pre>

====@Laser Color:====
The RGB color of the glow effect.

*The color is applied both to the glowmap and the omnilight that follows the effect.

Syntax: '''''Color''''', red, green, blue respectively, 8-bit value from 0 to 255

'''Example:'''
<pre>
@Laser Color: 255, 0, 0 ; Red glow effect at the start of the effect's lifetime
</pre>

====@Laser Color2:====
The RGB color of the glow effect at the end of the effect's lifetime (at its maximum range).

*The color is applied both to the glowmap and the omnilight that follows the effect.
*The actual color of the glow effect is somewhere in between the values defined by Color and Color2. Essentially, the actual color "fades" from Color to Color2 over its lifetime.
**If Color is not defined, then a default value of 255, 255, 255 is assumed for its initial color.

Syntax: '''''Color''''', red, green, blue respectively, 8-bit value from 0 to 255

'''Example:'''
<pre>
@Laser Color2: 0, 0, 255 ; Blue glow effect at the end of the effect's lifetime.
</pre>

'''Example:'''
<pre>
@Laser Color: 255, 0, 0 ; Start with a Red glow effect, and fade into...
@Laser Color2: 0, 0, 255 ; a Blue glow effect over the lifetime of the effect.
</pre>

====@Laser Length:====
Defines the length of the weapon effect.
*This option stretches the 2D plane "away" from its origin.
Syntax: '''''Float''''', meters

'''Example:'''
<pre>
@Laser Length: 1.0
</pre>

====@Laser Head Radius:====
Defines the width of the leading edge, or "head," of the weapon effect.
*The edge of the 2D plane farthest away from its origin is the leading edge.
Syntax: '''''Float''''', meters

'''Example:'''
<pre>
@Laser Head Radius: 0.75
</pre>

====@Laser Tail Radius:====
Defines the width of the trailing edge, or "tail" of the weapon effect.
*The edge of the 2D plane that is closest to its origin is the trailing edge.
Syntax: '''''Float''''', meters

'''Example:'''
<pre>
@Laser Tail Radius: 0.75
</pre>

===$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 targeting 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
*Note that Fire wait will be reset to 1 if it is set over 5 for non turreted primary weapons (doesn't apply to 3.6.14+)
*Syntax: '''''Float''''', seconds

====+Max Delay:====
{{Table373|
*Defines the maximum amount of time it takes to refire a weapon in a random fire delay range.
**This must be used with +Min Delay: to have any effect.
*Syntax: '''''Float''''', seconds}}

====+Min Delay:====
{{Table373|
*Defines the minimum amount of time it takes to refire a weapon in a random fire delay range.
**This must be used with +Max Delay: to have any effect.
*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
*Note: adding a shockwave to a weapon doubles its effective damage to the target (i.e. 1x impact, 1x shockwave)

===$Damage Time:===
{{Table373|
*This sets a time from the end of the weapons lifetime that damage will start to attenuate at. '''''Example: Weapon lifetime is 2.0 seconds and the desired effect is to attenuate after 0.5 seconds have passed, set this to 1.5 seconds.'''''
*Syntax: '''''Float''''', seconds. Defaults to 0.0.
**Note: If neither +Min Damage: nor +Max Damage: is set, the damage will always attenuate to zero at max range.
***If both +Min Damage: and +Max Damage: are set, both are defaulted to 0.0 and damage will be attenuated to zero.}}

====+Attenuation Damage:====
{{Table373|
*This sets the damage a weapon will attenuate to after reaching $Damage Time:.
*Syntax: '''''Float''''', damage.}}

====+Min Damage:====
{{Table373|
*This sets the lowest amount of damage possible assuming damage attenuation is taking place. '''''This has been deprecated, please use +Attenuation Damage: instead.'''''
*Syntax: '''''Float''''', damage. Defaults to 0.0.}}

====+Max Damage:====
{{Table373|
*This sets the highest amount of damage possible assuming damage attenuation is taking place. '''''This has been deprecated, please use +Attenuation Damage: instead.'''''
*Syntax: '''''Float''''', damage. Defaults to 0.0.}}

===$Damage Type:===
{{Table3610|
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:''' [[armor.tbl]]

*Syntax: '''''String''''', name of the damage type ( as defined by [[armor.tbl#$Damage Type:|$Damage Type]] )}}

===$Arm time:===
{{Table3610|
*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:===
{{Table3610|
*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}}
{{Table3615|
*This parameter is also applied to flak weapons. Previous behaviour was to arm weapons after 10 meters of travel.}}

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

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

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

===$Shockwave damage:===
{{Table3610|
*Override for the damage caused by shockwaves (default is [[#$Damage:]])
*Syntax: '''''Float''''', damage
*Note: adding a shockwave to a weapon doubles its effective damage to the target (i.e. 1x impact, 1x shockwave)
}}

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

===$Flak Detonation Accuracy:===
{{Table3615|
*Normally, flak weapons detonate at a range of 65 to 99 meters from their intended target, depending on the firing ships' weapon subsystem health. This parameter can be used to adjust this behaviour, as it defines the base range used to determine this detonation range. Standard value is 65.
*Syntax: '''''Float''''', range in meters}}

===$Flak Targeting Accuracy:===
{{Table3615|
*Turret-fired flak weapons are normally firing in a cone around the target's predicted position. This parameter can be used to adjust the size of this cones' base radius. Standard is 60 meters.
*Syntax: '''''Float''''', radius in meters}}

===$Untargeted Flak Range Penalty:===
{{Table3615|
*If a flak weapon is fired without a target selected, this parameter defines the range penalty applied to that weapon. Standard is 20 meters, meaning an untargeted flak weapon will detonate after travelling its max range - 20 meters.
*Syntax: '''''Float''''', penalty in meters.}}

===$Blast Force:===
*The intensity of the kinetic 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. Damage is reduced by the square of the distance between the inner radius and outer radius. i.e. half way between inner and outer results in 1/4 damage
*Syntax: '''''Float''''', meters

===$Outer Radius:===
*Maximum radius at which any damage is done. See $Inner Radius for the attenuation formula.
*Also defines the size of the shockwave (if shockwave speed is > 0)
*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:===
{{Table3610|
*Defines how the 3D shockwave is rotated.
*Syntax: '''''Angle''''', three values, pitch, bank, heading respectively, in degrees}}

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

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

===$Dinky shockwave:===
{{Table3610|
*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:===
{{Table3610|
*Defines the minimum lifetime of the weapon
*Syntax: '''''Float''''', seconds}}

===$Lifetime Max:===
{{Table3610|
*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:===
'''This option is exclusive to secondaries.'''

Defines if the bolts/missiles in question is homing
*The bolts of primaries will turn to face their target if this option is set to YES... but is otherwise the same as a normal bolt ( when the option is set to NO ).

If set to NO, then following fields are not required in the table.

*Syntax: '''''Boolean''''', yes or no

===='''+Type:'''====
Defines the homing method
*Syntax: '''''String''''', ''ASPECT'' or ''HEAT''
{{Table3610| 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:'''====
Determines how well the missile maneuvers. Is defined as the number of seconds it takes the missile to do a 360 degree circle
**Syntax: '''''Float''''', seconds

===='''+View Cone:'''====
'''Heat-seeking missiles only'''

This is the width of the weapon's viewing cone, given in degrees. Objects outside this cone are effectively invisible to the missile. The value / 2 gives the angle from the missile's centerline to the edge of the viewing cone.
*Syntax: '''''Float''''', degrees
{{Table3610| 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 a target lock.
*Syntax: '''''Float''''', seconds

===='''+Lock Pixels/Sec:'''====
'''For aspect/javelin missiles only'''
The number of 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'''

The number of 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. (Needs verification )
**Syntax: '''''Integer''''', pixels

===='''+Seeker Strength:'''====
{{Table3610|
Defines the seeking ability of the homing system. Default of heat seekers is 3.0 and for aspect seekers 2.0. Spoofing chance is defined as '''[[#$Countermeasure:|cm type effectiveness]]'''/'''seeker strength''' (missile must be within the countermeasures '''[[#$Countermeasure:|+Effective Radius:]]'''
*Syntax: '''''Float''''', seeker strength}}

===='''+Target Lead Scaler:'''====
{{Table3611|
Defines the type of pursuit course the missile tries to obtain.
*Values < 0 give lag pursuit, values ~ 0 give pure pursuit, values > 0 give lead pursuit.
*Syntax: '''''Float''''', default for heat seekers: 0, default for aspect or javelin seekers: 1.}}

===$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'. Does not work with player weapons.
*Is incompatible with "Corkscrew" option.
*Swarm will negatively affect the missile's ability to hit its target. Especially when fired off-bore.
*Syntax: '''''Integer''''', number of shots in a swarm
{{Table3610|
*'''+SwarmWait:'''
**Defines the time between weapons fired in a swarm
**Syntax: '''''Float''''', seconds
***Default: 0.150
***Max: 0.5 (Resets to default if set over 0.5)}}

===$Acceleration Time:===
{{Table371|
*Defines how long it takes for a secondary weapon to attain full speed. Takes precedence over $Free Flight Time (see below) in terms of the weapon's velocity, and affects both locked-on and dumbfired secondaries.
*Syntax: '''''Float''''', seconds
**Default: 0.0}}

===$Velocity Inherit:===
{{Table371|
*Defines how much of the parent ship's velocity to inherit, if [[Ai_profiles.tbl#.24use_additive_weapon_velocity:]] is used.
*Syntax: '''''Float''''', percents
**Default: 100.0}}

===$Free Flight Time:===
{{Table3610|
*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}}

'''Note:''' due to dumbfires never changing their speed, using this on a dumbfire missile will have it stuck at freeflight speed even after the end of the freeflight time.

===$Free Flight Speed:===
{{Table3613|
*Defines the speed that the weapon will be travelling at during the free flight segment (see above).
*Syntax: '''''Float''''', Multiplier for the actual speed, minimum 0.01.
**Default: 0.25
{{Note| This feature was never implemented correctly and was removed in r8867. FSO currently parses but doesn't use the value, and prints a warning in the log saying that the value will not be used.}}
}}

===$PreLaunchSnd:===
{{Table3613|
*Defines the one-shot sound effect to play at the beginning of a firing stream. Currently only has an effect on primary weapons.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
**Default: No Sound}}

===+PreLaunchSnd Min Interval:===
{{Table3613|
*Defines Minimum interval between when the player stops firing and the next time the pre-launch sound can play, as a limiter in case the player is pumping the trigger.
*Syntax: '''''Integer''''', Minimum delay in milliseconds between the end of the previous firing sequence and the next time the pre-launch sound effect will be played.
**Default: 0 (play pre-launch sound at the beginning of every firing sequence, if present)}}

===$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:===
{{Table3610|
*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

===$TrackingSnd===
{{Table3615|
*The looping sound played when this weapon tracks a target.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$LockedSnd===
{{Table3615|
*The sound played when this weapon has locked onto its target.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$InFlightSnd===
{{Table3615|
*The looping sound played when the missile is currently flying.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+Inflight sound type'''
**Specifies when the in flight sound is played.
**The value can be one of the following values which are matched case-insensitively:
***''''''TARGETED'''''': The sound is played when the missile tracks a target
***''''''UNTARGETED'''''': The sound is played when the missile is currently not tracking a target
***''''''ALWAYS'''''': The sound is played always}}

===$Model:===
{{Table3610|
*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:===
{{Table3610|
*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:===
*See [[Weapons.tbl#Weapons.tbl_Flags|below]]
*Syntax: '''''( "String" "String" )''''', names of the flags assigned to the weapon
**Example: ( "Player allowed" "in tech database" )

{{Table3610|
*Can be followed by '''+override''' option in order to reset the weapon flags before parsing in the new ones
*Using this option will erase all '''homing'''-related flags as well as '''swarm''', '''variable lead''', '''trail''', '''TAG''', and '''transparent''' settings in addition to the listed flags. All these should be set again - if they are required - when this option is used.

**Syntax: '''''+override'''''}}

===$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
{{Table3611|
*'''+Faded Out Sections:'''
**Defines the number of the trail sections (counting from the leading edge) which are gradually faded out.
**Syntax: '''''Integer''''', number of trail sections}}

===$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:===
{{Table3610|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

===$Collide Weapon:===
{{Table3610|
*Has been replaced with '''#Conditional Hooks''', see [[Scripting.tbl]]}}

===$Impact Effect:===
{{Table38|
*Specifies the [[Particle Effects|particle effect]] which will be used for impacts of this weapon.
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Impact Explosion'' and ''$Impact Explosion Radius'' are not valid options!
}}

===$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, default 1.0

===$Shield Impact Explosion Radius:===
{{Table373|
*Radius of the shield impact explosion, see [[Ships.tbl#.24Shield_Impact_Explosion:]].
*Syntax: '''''Float''''', meters, defaults to value of $Impact Explosion Radius}}

===$Dinky Impact Effect:===
{{Table38|
*Specifies the [[Particle Effects|particle effect]] which will be used for Dinky (not armed) explosions of this weapon.
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Dinky Impact Explosion'' and ''$Dinky Impact Explosion Radius'' are not valid options!
}}

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

===$Dinky Impact Explosion Radius:===
{{Table3610|
*Same as Impact Explosion Radius but for Dinky explosions
*Syntax: '''''Float''''', meters}}

===$Piercing Impact Effect:===
{{Table38|
*Specifies the [[Particle Effects|particle effect]] which will be used for piercing impacts.
*Syntax: '''String''', the particle effect name
*If this option is specified then piercing impact options below are not valid!
}}

===$Piercing Impact Explosion:===
{{Table3611|
*Defines the effect used for events when weapon pierces the target
*Syntax: '''''String''''', filename or ''none''}}

===$Piercing Impact Radius:===
{{Table3611|
*Defines the base radius of the effect used for piercing weapon impacts
*Syntax: '''''Float'''''}}

===$Piercing Impact Velocity:===
{{Table3611|
*Defines the base velocity for the particles piercing the target
*Syntax: '''''Float'''''}}

===$Piercing Impact Splash Velocity:===
{{Table3611|
*Defines the base velocity for the particles splashing from the target (secondary piercing effects
*Negative value causes the second batch or particles to splash to opposite direction
*Syntax: '''''Float'''''}}

===$Piercing Impact Variance:===
{{Table3611|
*Defines the variance added to the particles
*Values near 0 cause very little variance and values close to 1 cause extreme dispersal.
*Syntax: '''''Float'''''}}

===$Piercing Impact Life:===
{{Table3611|
*Defines the lifetime of the effect for single frame effects
*For multiple frame effects the lifetime is the lifetime of the animation used
*Syntax: '''''Float'''''}}

===$Piercing Impact Particles:===
{{Table3611|
*Defines the number of particles released per impact
*Syntax: '''''Integer'''''}}

===$Piercing Impact Draw Modifier:===
{{Table3611|
*Defines the multiplier applied to the ships piercing effect limit percentage
*Syntax: '''''Float'''''}}
*Option removed in 3.6.12. Use [[armor.tbl]] to finetune piercing effects.

===$Inflight Effect:===
{{Table38|
*Sets the inflight [[Particle Effects|particle effect]] which is used when the laser is active. This is only used by laser weapons.
*Syntax: '''''String''''', the particle effect name
}}
===$Freeflight Effect:===
{{Table38|
*Sets the [[Particle Effects|particle effect]] which is used when the missile is in the free flight phase. See [[#$Free Flight Time:|$Free Flight Time]] for more information.
*Syntax: '''''String''''', the particle effect name
*This option is only valid for missile weapons
}}
===$Ignition Effect:===
{{Table38|
*Sets the ignition [[Particle Effects|particle effect]] which is used when the missile is transitioning from free flight to homed or unhomed flight.
*Syntax: '''''String''''', the particle effect name
*This option is only valid for missile weapons
}}
===$Homed Flight Effect:===
{{Table38|
*Sets the ignition [[Particle Effects|particle effect]] which is used when the missile is in homed flight mode.
*Syntax: '''''String''''', the particle effect name
*This option is only valid for missile weapons
}}
===$Unhomed Flight Effect:===
{{Table38|
*Sets the ignition [[Particle Effects|particle effect]] which is used when the missile is in unhomed flight mode.
*Syntax: '''''String''''', the particle effect name
*This option is only valid for missile weapons
}}

===$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
*Basically a percentage, a value of 250 results in a 25% chance of something getting scrambled each frame.
*Maximum value of 500
**Syntax: '''''Float'''''

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

===$Recoil Modifier:===
{{Table373|
*Multiplies the recoil force of a weapon by this value, use a value greater than 1.0 to increase the force, use a value between 1.0 and 0.0 to decrease.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note| The "apply recoil" weapon flag must be set for this to be valid. If the flag is not set, FSO will throw a warning and automatically set it at runtime.}}
}}

===$Leech Weapon:===
**The amount of weapon energy to drain with each hit (a flat value, not a percentage)
**Needs the [[#Esuck|Esuck]] flag set to have any effect
**Syntax: '''''Float''''' (defaults to 10.0)

===$Leech Afterburner:===
**The amount of afterburner fuel to drain with each hit (a flat value, not a percentage)
**Needs the [[#Esuck|Esuck]] flag set to have any effect
**Syntax: '''''Float''''' (defaults to 10.0)

===$Corkscrew:===
{{Table3610|
*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:===
{{Table3610|
*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.
}}
{{Table371|
*'''+Area Of Effect'''
**If specified, allows the electronics effect to apply to every ship hit by this weapon's blast or shockwave (the "Electronics" flag isn't necessary with this option).
}}
{{Table3610|
*'''+Intensity:'''
**May only be used with '''+New Style:''' electronics. '''''Has been deprecated'''''.
**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 subsystems.
**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:===
{{Table3610|
*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''.
*Spawn angle can be defined as many times as the carrier missile has child weapons defined for it (up to 5).
*Syntax: '''''Float''''', degrees}}

===$Local SSM:===
{{Table3610|
*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:===

*Defines the countermeasure effectiveness, radius, etc
{{note|
*Spoofing chance is defined as '''cm type effectiveness'''/'''[[#+Seeker Strength:|seeker strength]]''' (missile must be within the countermeasures '''+Effective Radius:''').
*All countermeasures in the mission perform tests to spoof missiles for two frames after '''any countermeasure''' is created in the mission. No, this doesn't seem to make much sense.
{{Table382|The global frame counter can be bypassed by using '''[[#+Pulse Interval:|pulse interval]]'''.}}
*'''Provisional'''; Countermeasures are only given one chance to spoof any individual missile. This makes tuning seeker strength/effectiveness meaningful.
**Previously some record of which countermeasures had been seen by each missile was kept, but it broke when multiple countermeasures were involved. A good chance of breaking with two countermeasures, and a guaranteed chance of breaking with three or more. This reduced the impact of the seeker strength/effectiveness ratio, but was partly cancelled out by the 2 frames thing.
}}

{{Table3610|
===='''+Heat Effectiveness:'''====
*Defines the countermeasures effectiveness against heat seeking missiles
*Syntax: '''''Float''''', cm effectiveness
**Default: 1.0

===='''+Aspect Effectiveness:'''====
*Defines the countermeasures effectiveness against aspect seeking missiles
*Syntax: '''''Float''''', cm effectiveness
*Default: 1.0

===='''+Effective Radius:'''====
*Defines the countermeasures effective radius
*Syntax: '''''Float''''', meters
**Default: 300.0
}}

{{Table373|
====+Missile Detonation Radius:====
*Defines the radius within which a missile homing on this countermeasure will trigger a detonation (see '''+Single Missile Kill:''')
*Syntax: '''''Float''''', meters
**Default: 40.0
{{note| only affects missiles homing on countermeasures, i.e. heat or aspect with "pulls aspect seekers" flag}}

====+Single Missile Kill:====
*Defines if countermeasures will detonate only the missile homing on this countermeasure, or every missile within '''+Missile Detonation Radius:'''
*Syntax: '''''Boolean'''''
**Default: false
{{note| only affects missiles homing on countermeasures, i.e. heat or aspect with "pulls aspect seekers" flag}}
}}

{{Table382|
====+Pulse Interval:====
*Defines how much time passes between each pulse of this countermeasure.
*Syntax: '''''Float''''', milliseconds
**Default: 0
{{note| any value less than or equal to 0 means the countermeasure doesn't pulse, and uses the global 2-frame counter after any countermeasure is fired.}}
}}

===$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 targeting beam that is used to trigger SSMs. 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
{{Table3613|
*'''IFF specific miss factors'''
**Identical to the preceding entry but IFF specific. Replace the <IFF> with the name of the IFF from [[iff_defs.tbl]]
**Syntax: '''''+<IFF> 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
{{Table372|
*'''+Directional Glow:'''
**Defines the length to stretch the muzzleglow along the beam.
**Syntax: '''''Float''''', length in meters, the muzzleglow is rendered along (in the same plane) as the beam instead of perpendicular to the camera.}}
*'''+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'''''
{{Table3610|
*'''+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}}
{{Table3611|
*'''+BeamWidth:'''
**Defines the width of the beam for collision test purposes instead of using widest beam section.
**Syntax: '''''Float''''
{{Table38|
*'''+Beam Flash Particle Effect:'''
**Specifies the beam flash [[Particle Effects|particle effect]].
**Syntax: '''''String''''', particle effect name
**If this is specified then '''+Beam Flash Effect''' and '''+Beam Flash Radius''' are not valid options!
}}
*'''+Beam Flash Effect:'''
**Defines the additional impact flash effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Flash Radius:'''
**Defines the radius for the additional impact flash effect.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect:'''
**Defines the beam piercing (bursting flames) effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Piercing Radius:'''
**Defines the average radius used for the beam piercing effects.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Velocity:'''
**Defines the base velocity for the piercing effects
**Syntax: '''''Float'''''
*'''+Beam Piercing Splash Effect Velocity:'''
**Defines the base velocity for the secondary piercing effects
**Negative velocity causes the particles to move to opposite direction
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Variance:'''
**Defines the variances of the particles from the main path
**Values close to 0 cause minimum variance, higher values cause higher variances
**Syntax: '''''Float'''''}}

*'''$Section:'''
**Beams are made up of up to five sections layered atop one another to create the effect. Each section has its own parameters.
{{Table3610|
:*'''+Index:'''
:**Field used to define with [[Modular Tables]] the beam section which is edited.
:**Only needed when editing beams that already exist in other tables.
:**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
{{Table3613|:**Not used in current builds. Settings entered here will have no effect.}}
:**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
{{Table3613|:**Not used in current builds. Settings entered here will have no effect.}}
:**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'''''
{{Table3610|
:*'''+Tile Factor:'''
:**Defines the beam texture tiling factor. Second number defines the tiling 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:===
{{Table3610|
*Defines a particle spew effect for the given weapon
}}{{Table3613|
*'''+Index:'''
**indicates which spewer to add/edit/delete. may be 0-3. used for xmt compatibility.
**Syntax: '''''Integer'''''
*'''+Remove'''
**removes spewer at +Index: (requires +index:)
*'''+Type:'''
**type of particle spew
**Syntax: '''''String'', Default, Helix, Sparkler, Ring, or Plume '''
}}{{Table3610|
*'''+Count:'''
**Defines how many particles are spawn when they are ready to be created (at each +Time: interval)
**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
**typically controls how big the effect is or how fast it moves away from the weapon path on a perpendicular (or sometimes arbitrary) axis.
**helical spews and rings use this value to control how fast the particle helix moves away from the central axis.
**sparklers use this to control how fast particles move away from the spawn point, in any direction
**plumes use this to set the diameter of the disk across which particles are spawned
**Syntax: '''''Float'''''
}}{{Table3613|
*'''+Z Scale:'''
**for sparklers, allows you to elongate the effect to surround other effects, like lasers. essentially a length multiplier
**for plume, it multiplies against +scale to set the plume to spread or converge, zero would be full convergence, 1 would be straight flight, and bigger numbers would cause particles to diverge from the disk.
**Syntax: '''''Float'''''
*'''+Rotation Rate:'''
**used only by helical spews, controls how many rotations per second the helix makes
**Syntax: '''''Float'', may be negative, useful for setting up 2 spews that spin in opposite directions'''
*'''+Offset:'''
**position of effect with regards to the weapon center
**Syntax: '''''Vector'''''
*'''+Initial Velocity:'''
**to indicate both direction and speed of particle effects regards to the weapon velocity and +scale:
**Syntax: '''''Vector'''''
}}{{Table3610|
*'''+Bitmap:
**Defines the animation used to create the particle spew effect
**Syntax: '''''String''''', filename}}

===$Tag:===
*Allowed for secondary weapons
{{Table3610|
*Allowed for primary weapons and secondary weapons}}

*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.
{{Table3610|
*TAG Level 3 allows the weapon to trigger [[Weapon.tbl#$SSM:|SSMs]]}}

*Syntax: '''''Integer''''' '''''Float''''', TAG level and seconds respectively
*'''Note''': TAG will not trigger unless the weapon in question has a non-zero damage value.

===$SSM:===
{{Table3610|
*Defines the weapons SSM index number.
*Requires [[Weapons.tbl#$Tag:|TAG level 3]] or a targeting beam.
*Syntax: '''''Integer'''''}}
{{Table373|
*Now also accepts SSM strike names.
*Syntax: '''''String'''''}}

===$FOF:===
{{Table3610|
*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}}

====+FOF Spread Rate:====
{{Table37|
*Defines the spread rate of the field of fire. This controls how the FOF increases over time while the weapon is firing.
*Syntax: ''''''Float'''''', rate}}

====+FOF Reset Rate:====
{{Table37|
*Rate at which the spread decreases if the weapon isn't firing.
*Syntax: ''''''Float'''''', rate
*This is required if '''+FOF Spread Rate:''' is present}}

====+Max FOF:====
{{Table37|
*The maximum FOF. After the FOF reaches this value it will not increase any further.
*Syntax: ''''''Float'''''', degrees. Must be greater than or equal to zero.
*This is required if '''+FOF Spread Rate:''' is present}}

===$Shots:===
{{Table3610|
*Defines the number of shots every time the weapon is fired.
*Works only for primary weapons
*Syntax: '''''Integer''''', number of shots}}

===$decal:===
{{Table3610|
*Defines impact decals if they are in use
*'''+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}}
{{Table3613|
*Feature removed - table parsing retained to maintain compatibility}}

===$Transparent:===
{{Table3610|
*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 Hitpoints:===
{{Table3611|
*Defines the amount of hitpoints a weapon has.
*Weapons with '''"bomb"''' flag have 50 hitpoints by default
*Giving weapon hitpoints makes it possible for the weapon to be shot down or be destroyed by EMP.
**Syntax: '''''Integer'''''
}}

===$Armor Type:===
{{Table3613|
*REQUIRES ADDITIONAL TABLE. Defines the armor type for the weapon. This works exactly like ship armor types.
**Syntax: '''''String''''', name of the armor as defined in [[armor.tbl]]
}}

===$Burst Shots:===
{{Table3611|
*Defines the number of shots in a burst
*Shots in a burst use shorter ( '''$Burst Delay:''' ) delay than usually
**Syntax: '''''Integer'''''}}

===$Burst Delay:===
{{Table3611|
*Defines the time in milliseconds between the shots in a burst
**Syntax: '''''Integer'''''}}

===$Burst Flags:===
{{Table3611|
*Defines the flags used to define the burst firing behaviour
**Syntax: ( '''''String''''' '''''String''''' ), list of flags
**Available burst flags:
***'''"fast firing"''', acts as if '''same turret cooldown''' flag would be used between the shots in the burst.
***'''"random length"''', makes AI to fire burst of random length (from 1 to burst shots).}}

===$Thruster Flame Effect:===
{{Table3611|
*Defines the filename of the effect used on the modeled thruster of the missile
**Syntax: '''''String''''', filename}}

===$Thruster Glow Effect:===
{{Table3611|
*Defines the filename of the effect used on the glow type effect of the missile
**Syntax: '''''String''''', filename}}

===$Thruster Glow Radius Factor:===
{{Table3611|
*Defines the radius multiplier for the thruster's glow type effect
**Syntax: '''''Float'''''}}

===$Substitute:===
{{Table3613|
Defines a pattern of ammo to substitute for primary or secondary weapons. '''$Substitute:''' can be repeated any number of times (so you could make something like a rainbow laser with several ammo substitutions, for example). If neither ''+period'' or ''+index'' is specified, it is assumed to be equivalent to ''+index: '''0'''''.

*Syntax: '''''Weapon Name'''''
*'''Swarm missiles act in a strange way when used with $Substitute, use at your own risk.'''}}

{{Table3615|
Turrets can use $Substitute as well.
}}
====+period:====
{{Table3613|
FSO will substitute '''Weapon Name''' every ''period'' shots.

*Syntax: '''''Positive Integer'''''
*'''You may not define both +period and +index for the same $Substitute entry'''}}
=====+offset:=====
{{Table3613|
A suboption of +period, offsets the substitute pattern according to the launched ammo. For example, an offset of 3 and a period of 4 will substitute on the 3rd ammo launched, and then every 4th ammo after that.

*Syntax: '''''Positive Integer'''''}}

====+index:====
{{Table3613|
FSO will substitute the '''Weapon Name''' at firepoint ''index'' in the shot pattern. Similar to carefully using both +period and +offset, but is not affected by ships with different firepoint numbers. i.e. Firepoint ''index'' will always have the substitution, while +period and +offset will cycle at different rates dependant on the number of firepoints.'''

*Syntax: '''''Positive Integer'''''

*'''You may not define both +period and +index for the same $Substitute entry'''}}

==Weapons.tbl 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.
{{Table3610|
*Multiple spawn types can be defined for a single 'carrier' weapon up to maximum of 5 different weapons}}

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

==="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. Also the AI will not try to hit fighters with it.

==="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.
{{Table3610|
*'''EXTREMELY IMPORTANT NOTE:'''
**Whenever you plan to use a weapon as a player one in your campaign or missions, '''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
{{Table3610|
*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.
{{Table3610|
*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"===
* Does nothing

==="puncture"===
*Reduces hull damage by 75%
The AI will prefer these weapons for anti-subsystem use

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

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

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

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

==="local ssm"===
{{Table3610| }}

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

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

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

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

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

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

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

==="smart spawn"===
{{Table3611|
*Forces turret fired spawn weapon of this type to be fired like normal weapons.}}

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

==="no emp kill"===
{{Table3611|
*Defines the weapon (with hitpoints) to be immune to automatic EMP destruction.}}

==="untargeted heat seeker"===
{{Table3611|
*Defines the weapon as a heatseeker type missile which acquires its target by itself.}}

==="no radius doubling"===
{{Table3611|
*Prevents weapon radius from being doubled when doing collision test. Makes bombs harder to intercept.}}

==="no subsystem homing"===
{{Table3611|
*Prevents weapon from acquiring a subsystem as its target. Missile homing points are spread over the target ship.}}

==="no lifeleft penalty"===
{{Table3611|
*Prevents weapon lifetime from being penalized if the angle to the target is too big.}}

==="can be targeted"===
{{Table3611|
*Allows weapon to be targeted by player. Does not influence AI}}

==="show on radar"===
{{Table3611|
*Allows weapon to be visible on the radar}}

==="show friendly on radar"===
{{Table3611|
*Allows friendly, otherwise visible to radar weapon, to be visible on player radar}}

==="capital+"===
{{Table3613|
*Tells AI to use this weapon only on capital ships}}

==="chain external model fps"===
{{Table3613|
*Tells game to keep switching external model firingpoints when firing}}

==="external model launcher"===
{{Table3613|
*Tells game that the external model is a launcher so that it would be kept static without loading motion}}

==="takes blast damage"===
{{Table3613|
*Weapon takes damage from weapon blasts}}

==="takes shockwave damage"===
{{Table3613|
*Weapon takes damage from shockwaves}}

==="ciws"===
{{Table3615|
*Weapon can deal shockwave/blast damage to bombs, regardless of whether the target weapons have the "take blast/shockwave damage" flags.}}

==="render flak"===
{{Table3615|
*Normally, flak shells are not rendered. This flag switches rendering on for those weapons.}}

==="anti-subsystem beam"===
{{Table3615|
*Beam weapons with this flag can target subsystems on enemy ships, just like normal weapons.}}

==="no primary linking"===
{{Table3615|
*Primary weapons with this flag can not be linked with other weapons.}}

==="same emp time for capships"===
{{Table37|
*capships affected by this weapon will use the tabled EMP time rather than the fixed retail value (7.5 secs)}}

==="no primary linked penalty"===
{{Table371|
*Primary weapons with this flag do not incur the retail linked fire penalty}}

==="no homing speed ramp"===
{{Table371|
*Locked homing weapons will not perform the standard 1 second long acceleration when fired. Note that use of $Acceleration Time is '''not''' affected by this flag.}}

==="pulls aspect seekers"===
{{Table371|
*If an aspect seeker is grabbed by this countermeasure the missile will follow the countermeasure instead of going into dumbfire mode.
'''Only valid for countermeasures!'''}}

==="turret interceptable"===
==="fighter interceptable"===
==="interceptable"===
{{Table371|
*Allows turrets/fighters/both (respectively) to shoot at this weapon without requiring it to be a bomb. If this is the first time this weapon has been defined, it also gives it a default of 25 hitpoints so that it can be shot down.
'''If you use a TBM to give this flag to an existing weapon, you'll need to specify hitpoints manually (unless you want it to be unkillable but still draw defensive fire).'''}}

==="apply recoil"===
{{Table373|
*A ship that fires a weapon with this flag will experience a recoil effect, slowing the ship down and, with lighter strikecraft, inducing some rotation if the firing points are offset from the center of mass.
'''Do not use this with MVPs or retail ships unless you increase their density to 10 or use either $Recoil Modifier: in weapons.tbl or $Ship Recoil Modifier in ships.tbl. This is to avoid exaggerated effects due to retail models having manually defined masses.'''}}

==="don't spawn if shot"===
{{Table373|
*Prevents parent weapons from spawning children in the even of the parent weapon being shot down.}}

==="die on lost lock"===
{{Table373|
*Aspect seeking missiles (only, not heat seekers) will detonate upon losing their lock. Currently they only lose lock if decoyed by a countermeasure, AND "pulls aspect seekers" or similar is not set. The detonation will use their "dinky" explosion (i.e. same as if ran out of lifetime).}}

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

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

===$Velocity:===
*Defines the speed 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]]

Template:Table190

2017-08-24T12:05:26Z

AdmiralRalwood: Created page with "<noinclude>Table382</noinclude> <div style="padding: 1px 2px 1px 2px; background-color: #156364; border: solid 1px #1d8788; padding: 0px 4px; font-size: -1…"

Template:Table375

2017-08-24T12:05:19Z

AdmiralRalwood: We've standardized on not having separate version indicators for nightly builds, but I'll re-use the color for 3.8.2.

#REDIRECT [[Template:Table38]]

Engine limitations

2017-07-10T17:39:29Z

AdmiralRalwood: 3.7.4 doubled the ship class limit

The maximum numbers of certain types of entities that can exist in the FS2_Open engine. Please note that 'Inferno' refers to INF builds, which are standard from 3.6.12 on.

==General==
The overall limits of the various subsystem managers.
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505;"| '''Limit'''
|- align="center"
| Textures
| 4750
|- align="center"
| Sound tracks
| 30
|- align="center"
| Sounds
| No Limit
|}

==Tables==
The maximum types of an entity that can exist in the table

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=3 style="background:#300505;"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
| style="background:#300505; width:75px"| '''3.7.4'''
|- align="center"
| [[Ships.tbl|Ship Classes]]
| 130
| 250
| 500
|- align="center"
| [[Weapons.tbl|Weapon Classes]]
| 200
| colspan=2| 300
|- align="center"
| Beam Sections
| colspan=3| 5
|- align="center"
| Pspews Per Weapon
| colspan=3| 4
|- align="center"
| [[Objecttypes.tbl|Object Types]]
| colspan=3| 16
|- align="center"
| [[Iff_defs.tbl|IFFs]]
| colspan=3|10
|- align="center"
| [[Ai_profiles.tbl|AI Profiles]]
| colspan=3| 5
|- align="center"
| [[Hud_gauges.tbl|Hud Gauges]]
| colspan=3| 64
|- align="center"
| [[Species.tbl|Intelligence Entries]]
| colspan=3| 75
|- align="center"
| Debriefing
| colspan=3| 2,000 Characters per Stage
|}

Please Note - Prior to r11156, there was a hardcoded limit of 32 [[Modular Tables|‎ .tbm files]] of any given type that the game would recognize.

==Objects==
The maximum number of objects that can exist in a mission at any given time (except for ships and waypoints, which apply to the whole mission).

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Objects
| 2000 {{Table3615|3500}}
|- align="center"
| Ships
| 400
|- align="center"
| Weapons
| 700 {{Table3615|2000}}
|- align="center"
| Beams
| 500
|- align="center"
| Waypoints Per Path
| 20 {{Table3613|Limit Removed}}
|- align="center"
| Waypoint Paths
| 32 {{Table3613|Limit Removed}}
|}

==Wings==
The maximum number wings or ships in a wing that can exist

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Wings
| 75
|- align="center"
| Ships per Wing
| 6
|- align="center"
| Starting Wings
| 3
|- align="center"
| Squadron Wings
| 5
|- align="center"
| TvT Teams
| 2
|- align="center"
| TvT Wings per Team
| 1
|- align="center"
| TvT Wings
| 2
|}

==Models==
The maximum number of models that can exist at one time

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| Polygon Models
| 128
| 300
|}

The maximum number of a certain entity that can exist within a model

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Textures
| 64
|- align="center"
| Ship Primary Banks
| 3
|- align="center"
| Ship Secondary Banks
| 4
|- align="center"
| Firing Points Per-Bank
| 25
|- align="center"
| Debris Chunks
| 64
|}

==Sub-Weapon Types==

The maximums for the sub types of weapons.

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Type'''
| style="background:#300505; width:75px"| '''Max Instances'''
|- align="center"
| Corkscrew Missiles
| 200
|- align="center"
| Swarm Missiles
| 100
|}

[[Category:Source Code Project]]
[[Category:Modding]]

Various Terms

2017-03-28T16:19:28Z

AdmiralRalwood: /* Campaign Abbreviations */ Just adding a couple major releases.

This article lists down the '''various terms, abbreviations, and other jargon''' used by official FreeSpace sources as well as the FreeSpace community.

==Official Terminology==
===General===
* '''[[FRED]]''' - FReespace EDitor. The program created by Volition to make the mission and campaigns for both FreeSpace games. Released to the public along with said games.
* '''[[Portal:FreeSpace 2|FS2]]''' - FreeSpace 2. The second game of the series.

===File extensions===
These are FreeSpace-related extensions only.
*.ani - Animation files such as explosions
*.fc2 - FreeSpace 2 campaign
*.fs2 - FreeSpace 2 mission
*.fsm - FreeSpace 1 mission
*.pof - Model files with additional gameplay-related information like position of subsystems, turrets, etc.
*[[.tbl]] - Table file
*[[.tbm]] - Modular table
*.vp - Volition Pack files

===In-game Terminology===
*'''ETS''' - [[Energy Transfer System]]
*'''HUD''' - Heads-up Display. The interface the player uses while flying.
*'''Subsystem''' - Targetable and destroyable systems of a ship, e.g. radars, engines.
*'''TSM''' - Training Simulator Module

====Designation Prefixes====
* '''GT_''' - [[Galactic Terran Alliance|Galactic Terran]]
* '''NT_''' - [[Neo-Terran Front|Neo-Terran]]
* '''GV_''' - Galactic Vasudan
* '''PV_''' - [[Parliamentary Vasudan Empire|Parliamentary Vasudan]]
* '''GTV_''' - [[Galactic Terran-Vasudan Alliance|Galactic Terran-Vasudan]]
* '''S_''' - [[Shivans|Shivan]]

====Designation Suffixes====
* '''_A''' - [[Advanced Warning And Control System|AWACS]]
* '''_B''' - Bomber
* '''_C''' - Cruiser
* '''_Cv''' - Corvette
* '''_D''' - [[Destroyer]]
* '''_Dr''' - Drone
* '''_EP''' - Escape Pod
* '''_F''' - Fighter
* '''_Fr''' - Freighter
* '''_G''' - Gas Miner
* '''_I''' - Installation
* '''_J''' - [[Juggernaut]]
* '''_M''' - Medical Ship or Missile
* '''_NB''' - Navigation Buoy
* '''_S''' - Support Ship
* '''_SC''' - Science Cruiser
* '''_SG''' - Sentry Gun
* '''_T''' - Transport
* '''_W''' - Weapon ([[Weapon Comparison (FS1)|FreeSpace 1]])([[Weapon Comparison (FS2)|FreeSpace 2]])

===Fighter Units and Roles===
*'''Wing''' - A unit of fightercraft, varying in size from one to six ships. The normal number is four. Ships of a wing are labelled by their wing name and a number (i.e. Alpha 1, Alpha 2, and so on). The GTVA uses the Greek alphabet for its wings and the signs of the zodiac for hostile wings. In FS1, Shivan wings were named after Hindu gods. Wing labels are also sometimes used for groups of larger and similar vessels.
*'''Squadron''' - Refers to an organized group of pilots. The [[242nd Suicide Kings]] and [[203rd Scorpions]] are two examples.
*'''Stealth Recon''' - Fighters that specialize in infiltrating hostile territory and acquiring information without being detected. The [[GTF Pegasus|GTF ''Pegasus'']] and the [[GVF Ptah|GVF ''Ptah'']] are the only canon stealth fighters.
*'''Interceptor''' - A fighter role that aims at the destruction of hostile fighters and bombers. Interceptors are fast and agile, but are weakly shielded and armored.
*'''Space Superiority''' - A versatile fighter role that is capable in all sorts of roles, except for bombing. A celebrated example of a Space Superiority fighter is the [[GTF Myrmidon|GTF ''Myrmidon'']]
*'''Heavy Assault''' - Heavy Assault fighters have tremendous secondary capacity, heavy shielding and armoring at the expense of speed and maneuverability
*'''Bomber''' - A bomber is a very heavy craft that specializes in carrying bombs. They attack freighter-size ship and above. Bombers are very slow and easily taken down without fighter escorts. Bombers are further categorized into light, medium, and heavy bombers.

===Ship Types===
* '''Cruiser''' - Smallest combatant capital craft classification. Cruisers are at least several times the size of a fighter or bomber and possess mainly antifighter weaponry, with one or two (or in the case of the [[SC Rakshasa|SC ''Rakshasa'']], three) anticapital weapons. The defensive fire of a cruiser is rarely capable of stopping a determined bomber wing, and most are vulnerable to even a well-handled lone fighter. Unable to carry fighters. Canonical examples include the [[GTC Fenris|''Fenris'']] and the [[GTC Leviathan|''Leviathan'']]. In FS1, cruisers were deployed for both offensive and defensive tasks by all sides to any situation not requiring the attention of a destroyer. In FS2 Shivan cruisers are often deployed in mainline antiship and strike roles, while GTVA cruisers tend to be used as escorts and patrol craft.
* '''Corvette''' - Middle ground combatant capital craft, falling between the cruiser and the destroyer in size and capablity. Equipped with between two and four anticapital weapons and considerably more impressive antifighter armament than a cruiser. Corvettes are capable of defending themselves adequately against a small number of enemy fighters or bombers. With the exception of the [[SCv Moloch|SCv ''Moloch'']], corvettes are unable to carry fighters of their own. Corvettes appear to handle most of the antiship and strike duties for the GTVA fleet; Shivan corvettes are extremely rare and have only been deployed against GTVA destroyers canonically. Whether this is their role or not is guesswork.
* '''Destroyer''' - Large combatant capital craft, combining the functions of destroying enemy ships and transporting fighters. Destroyers vary wildly in armament and effectiveness against different types of targets. They will have at least one heavy-calibur anticapital weapon and probably several more, plus a number of cruiser-corvette anticapital weapons. Destroyers tend to need fighter cover more than corvettes; some of them actually mount fewer antifighter weapons, and all have much larger amounts of surface area that needs to be defended. Any situation with the direct involvement of a destroyer-class ship is by definition serious.
* '''Frigate''' - Semi-canonical ship class, both the Hippocrates and the Iceni have been referred to as frigates; the normally accepted role of a frigate is that of a pocket destroyer, lacking a fighterbay and fighter support facilities/crews enabling the ship to be shrunk down to only slightly bigger than a corvette.
* '''Superdestroyer''' - Bigger, meaner, and tougher than a destroyer, yet too small for the juggernaut classification; first applied well before the juggernaut classification came into existence. Only the [[GTD Hades|''Hades'']] and [[SD Lucifer|''Lucifer'']] have canonically been given this classification. The nature of the canonical superdestroyers was such that any appearance by them indicates ''the'' major effort by the controlling side. Their success is often decisive for that system, while their failure is a blow that is difficult to recover from.
* '''Juggernaut''' - The pinnacle of combatant capital craft, a juggernaut is capable of making mincemeat out of an enemy fleet singlehanded and is superbly equipped to combat other capital craft. Due to its large surface area its defenses against fightercraft attack are generally somewhat thinly spread, but a juggernaut's sheer ability to absorb damage means that only another juggernaut or a mass attack by corvettes and destroyers is capable of destroying one in anything like a timely manner. Only the [[SJ Sathanas|SJ ''Sathanas'']] has canonically been given this classification, though the ''Colossus'' could also be classified as juggernaut. The presence of a juggernaut, like a superdestroyer, indicates the controlling side considers the mission absolutely essential; decisive for the system if not the campaign or the entire war.
* '''Installation''' - A space station, described as "installation" because of its size, self-sufficiency, and permanence. The only installation classes canonically known are the [[GTI Arcadia|Arcadia]] and [[GTI Ganymede|Ganymede]]. The [[Galactic Terran-Vasudan Alliance|GTVA's]] naming system for installations generally includes something indicating their nature. Installation Riveria, Tombaugh Station, [[Enif Station]], and the Vega Installation are examples.

===Other Ship Types===
*'''Transport''' - Primarily used for transporting personnel. Sometimes used to transport marines in boarding a warship, as seen in the capture of a Shivan cruiser. However, it may also be used for repair purposes and evacuation. Transports are designed with minimal defenses and have to be escorted at all times to ensure survival.
*'''Freighter''' - Freighters carry important cargo and usually mount a few anti-fighter turrets. The largest canonical freighter is the [[GTFr Triton]].
*'''Gas miner''' - Used primarily to retrieve and transport nebular gas. Because of their often volatile contents, gas miners have an explosion yield far larger than ships of comparable size. The [[GTG Zephyrus]], [[GVG Anuket]], and [[SSG Rahu]] are the only three examples of gas miners.
*'''AWACS''' - AWACS vessels are primarily used for the expansion of radar detection in systems. Secondary purposes including jamming communications and detecting ships that are invisible to normal sensors. The [[GTA Charybdis]] and [[GVA Setekh]] are the only two examples of this classification.
*'''Escape Pod''' - The [[GTEP Hermes]] and [[GVEP Ra]] carry out this role. Escape pods are primarily for escape purposes, and are deployed from capital ships on the verge of destruction to save its crew and officers.

===Unique Ship Types===
*'''Medical Ship''' - Only the [[GTM Hippocrates]] carries this role. Primarily used to house patients under medical care, it is also used to evacuate refugees.
*'''Science Cruiser''' - Only the [[GTSC Faustus]] carries out this role. The Faustus appears to be tasked as a civilian science research vessel, but is also used by the military in times of war for weapons research. Science cruisers mount very few defenses and are therefore vulnerable to any form of assault.

===Others found in ships.tbl that are not classified as ships===
*'''Cargo Container''' - Carried by freighters. Cargo containers are unarmed and vulnerable to even fighter attack, and can only move via freighters.
*'''Sentry Gun''' - A small, vulnerable structure mounting one or more primary weapons. The largest of these is the [[GTSG Mjolnir]], which mounts a beam cannon. Oddly, Shivan sentry guns are rarely encountered in the FreeSpace 2 campaign.
*'''Knossos''' - The Knossos is an enormous subspace portal which, with its rotating components help stabilize a nearly-collapsed jump node.
*'''Meson Bomb''' - The [[TC-Meson Bomb]] is a remote detonation device which blasts about in a massive shockwave. The only canonical situations wherein these were deployed was in the destruction of the Knossos portal and the sealing off of the Capella jump nodes.
*'''Asteroid''' - Asteroids are of natural phenomenon. They are basically huge rocks in space that are harmful to even large capital ships as demonstrated in [[Rebels and Renegades]]. Asteroids may collide with capital ships and deal a severe amount of damage, but can be neutralized by primary weapons easily.
*'''Unknown Shivan rotating device''' - Known as the [[Shivan Comm Node]] in the editor, there has been no canonical description of the device as information regarding it is classified Level Omega. However, its name implies that it may be a kind of communication device of the Shivans.

===Special objects found in ships.tbl===
*'''SpaceHunk''' - The [[SpaceHunk]] is never used in the main FS2 campaign. It appears to be a large piece of debris from an [[SJ Sathanas]] juggernaut.
*'''SJD Sathanas''' - The [[SJD Sathanas]] is a small, triangular object that is used to represent a distant Sathanas juggernaut in [[Into the Lion's Den]] and all missions from [[Dunkerque]] onwards.
*'''Volition Bravos''' - The [[Volition Bravos]] is an easter egg that can be summoned onto the field using a cheat. It resembles a pirate ship manned by members of the Volition, Inc. staff. Although the Volition Bravos mounts nothing more than a few flak cannons and turret lasers, it is nearly impossible to destroy due to its incredibly high hitpoint count of ten billion.

===Weapons===
*'''Aspect-seeking''' - A type of secondary that must acquire a lock to track the target. See [[GTM Harpoon]].
*'''Countermeasure''' or '''CM''' - An anti-missile defensive mechanism for fighter-sized craft.
*'''Dumbfire''' - Secondary weapons cannot acquire any kind of lock on the target. See [[GTM Tempest]].
*'''Heat-seeking''' - A type of secondary weapon that acquires instant lock on the nearest target and chases it until it gets out of its cone.
*'''Primary''' - Primary weapons in ''FreeSpace'' are energy-based lasers.
*'''Secondary''' - Secondary weapons in ''FreeSpace'' are missiles and bombs.
*'''Turret laser''' - Primary weapons found on capital ships, transports, and freighters. An example would be the [[Terran Turret]]. See also '''blob turret'''.
*'''Anti-fighter beam''' - Small beam weapons on ships at least cruiser-sized. They are used to fire at enemy fighters and bombers, but can also provide fire support against small capital ships.
*'''Anti-capital beam''' - Beam weapons are the main armament of capital ships. They range from small such as the [[SGreen]], to large such as the [[BGreen]] and the juggernaut-scale [[BFGreen]].
*'''Slash beam''' - Beams which are used to sweep ships clean of subsystems. Only Terran and Vasudan warships arm these beam weapons.
*'''Swarm missile''' - Swarm missiles are secondary weapons that are fired in multiple numbers. See [[GTM Hornet]]

==Fan Terminology==
===In-game Terminology===
====Designation Prefixes====
* '''A_''' - [[Ancients|Ancient]]
* '''HL_''' - [[Hammer of Light]]

====Designation Suffixes====
* '''_BS''' or '''_Bs''' or '''BB''' - Battleship
* '''_Ca''' - Carrier
* '''_Dn''' - Dreadnaught
* '''_Fg''' - Frigate
* '''_Ff''' - Frigate
* '''_Gs''' - Gunship
* '''_H''' - Hive
* '''_SD''' - Superdestroyer
* '''_SJ''' - Super Juggernaut
* '''_TB''' - Tactical Bomber

===Ship Types===
* '''Carrier''' - Ship of any size whose primary purpose is to carry fightercraft, whether directly into combat or standing off and lending fightercraft support to ongoing operations as needed.
* '''Dreadnought''' - Generally understood to be a destroyer-sized craft, but built for the sole purpose of ship-to-ship combat and lacking a fighterbay or supporting a very limited number of fighters purely for self-defense.

===General===
* '''162''' - The Phoenix sub-forum on the Hard Light Productions Forums.
* '''AAA''' - Anti-fighter beam cannon(s)
* '''AB''' - Afterburner(s)
* '''Blob turret''' - A primary weapon-based, warship-mounted turret. The [[Terran Turret]] is an example.
* '''CM''' - Countermeasure
* '''CB''' - Command Briefing
* '''CBAnim''' - Command Briefing animation
* '''Colly''' - The [[GTVA Colossus|GTVA ''Colossus'']]
* '''FA''' - FRED Academy
* '''F2S''' - FreeSpace 2 Sector
* '''[[Portal:FreeSpace 1|FS1]]''' - Descent: FreeSpace—The Great War. Also called Conflict: FreeSpace—The Great War in Europe. The first game of the series.
* '''FS2_Open''' or '''FSO''' - The open source version of FreeSpace 2
* '''FS2NetD''' - FS2 Network Game Monitor; utility used to monitor FS2 network games being operated on the FS2Net servers.
* '''FS3''' - [[FreeSpace 3]], the theoretical sequel to FreeSpace 2
* '''GOG''' or '''GoG''' - Good Old Games. A digital distribution website that sells copies of FreeSpace 2. See [[Getting FreeSpace]].
* '''GW''' - Game-Warden
* '''Hattie''' - The [[GVD Hatshepsut|GVD ''Hatshepsut'']]
* '''HLP''' - Hard Light Productions
* '''HOTU''' - Home of the Underdogs. This website used to host a stripped-down version of FreeSpace 2.
* '''Lucy''' - The [[SD Lucifer|SD ''Lucifer'']]
* '''MediaVP''' or '''MVP''' - VP files with graphical enhancements for FreeSpace Open
* '''Retail''' - The original version of FreeSpace 2, as released by Volition in 1999, plus the official patches. (=not FreeSpace Open). ''Retail'' may also be used to refer to an official campaign, depending on context.
* '''RTB''' - Return to Base. Used to refer to the directive that tells the player to return to base.
* '''SCP''' - Source Code Project. The people responsible for creating, maintaining and debugging FS2_Open.
* '''SEXP''' - Symbolic EXPressions. Special function strings within FRED that allow for complex mission objectives and other things to be carried out by a mission bulider.
* '''SG''' - Sectorgame. This website hosts the FreeSpace 2 Sector.
* '''ST''' - [[Silent Threat]]
* '''TC''' - Total Conversion. See [[Total conversions]]
* '''V''' or '''[V]''' - [[Volition]], Inc., the developer of FreeSpace and FreeSpace 2.
* '''VBB''' - Volition Bulletin Board. The boards Volition maintained as a centre for the FS community. Now defunct.
* '''VW''' - Volition Watch, developer fansite covering the FreeSpace, Red Faction and Summoner series. Awaiting demolition.
* '''Zod''' - A term used to describe [[Vasudans]]. Derived from Zodiac because their fighter wings were designated based on them in FS1. The term has been coined by Eishtmo.

===Campaign Abbreviations===
:'''''This list is incomplete and not necessarily up-to-date. See also: [[Narwhal's Campaign List]]'''''
* '''158''' - The 158th Banshee Squadron
* '''AA''' - Aeos Affair
* '''AAB''' - Ascension and Beyond
* '''AG''' - [[Alcibiades' Gamble]]
* '''AHTW''' - All Hands to War
* '''AotD''' - Angels of the Damned
* '''[[ASW]]''' - The [[Ancient-Shivan War (campaign)|Ancient-Shivan War]]
* '''BP''' - [[Blue Planet]]
** '''BP:AoA''' or '''AoA''' - [[Blue Planet: Age of Aquarius]]
** '''BP:WiH''' or '''WiH''' - [[Blue Planet: War in Heaven]]
* '''BtA''' - [[Between the Ashes]]
* '''BtRL''' - [[Beyond the Red Line]]
* '''BWO''' - [[Blackwater Operations]]
* '''CoW''' - Casualties of War
* '''CoS''', '''Nukemod-CoS''' or '''Nukemod''' - [[Nukemod|Nukemod - Children of Shiva]]
* '''CtS''' - [[Crossing the Styx]]
* '''DEM''' - [[Deus Ex Machina]]
* '''FSPort''' - [[FreeSpace Port]]
** '''ST:R''' - [[Silent Threat: Reborn]]
* '''FSU''' - The FreeSpace Upgrade Project
* '''INF''' - [[Inferno]]. This may refer to any Inferno mod.
** '''INFA''' or '''INFA1''' - [[Inferno: Alliance]]
** '''INFA2''' - The sequel to Inferno: Alliance
** '''INFR1''' - [[Inferno Release 1]]
** '''INFASA''' - Inferno: Alliance Standalone
** '''INF SCP''' - Inferno SCP
* '''ITDoH''' - Into The Depths of Hell
* '''ITHOV''' - Into the Halls of Valhalla
* '''JAD''' - [[Just Another Day]]
** '''JAD2''' - [[Just Another Day 2: Electric Boogaloo]]
** '''JAD3''' - [[Just Another Day 3: Shivans on a Plane]]
* '''JtEP''' - The Journey to Epsilon Pegasi
* '''LM''' - The Lightning Marshal
* '''MT''' - Machina Terra
* '''MG''' - Mind Games
* '''NTV''' - [[Neo-Terra Victorious]]
* '''OTT''' - [[Over the Top]]
* '''PI''' - [[The Procyon Insurgency]]
* '''RR''' - Renegade Resurgence
* '''SA''' - The Scroll of Antankharzim
* '''SGWP2''' - [[The Second Great War Part II]]
* '''SoL''' - [[Shadows of Lylat]]
* '''SWC''' - Star Wars Conversion
** '''FotG''' - [[Fate of the Galaxy]]
* '''TAP''' - [[The Apocalypse Project]]
* '''TBP''' - [[The Babylon Project]]
** '''TBP:RW''' or '''RW''' - [[Raider Wars]]
** '''TBP:FH''' or '''FH''' - [[Fortune Hunters]]
* '''TI''' - Twisted Infinities
* '''TotT''' or '''ToT''' - Teeth of the Tiger
* '''TS''' - Technological Superiority
* '''TTP''' - The Titan Project
* '''TVWP''' - [[Terran-Vasudan War Project]]
* '''WCS''' - [[Wing Commander Saga]]
* '''WoD''' - [[Wings of Dawn]]

===Multiplayer===
The following is a list of some terms commonly seen on multiplayer chat screens.
* '''AI''' - Artificial Intelligence. This refers to any computer-controlled ship.
* '''Coop''' - Cooperative game. All players are on the same side and work together to accomplish the mission objectives.
* '''Dogfight''' or '''DF''' - A free-for-all type of game, essentially the Deathmatch of FreeSpace. All players are on their own and fight for survival.
* '''EMP''' - The EMP missile
* '''Fire''' - The Infyrno missile
* '''Fish''' - The Piranha missile
* '''Lag''' - Latency. This refers to the "jumpiness" in a multiplayer game due to slow Internet connections. FreeSpace has always had a lag problem, and even modern, high-speed connections have trouble hosting and playing online FreeSpace games. Can be greatly mitigated by having all players set their "Object Update" setting to Low.
* '''Lag bombing''' - Double-linking your secondary slot, firing, then quickly switching to your other secondary slot and firing it. Continue cycling and firing secondary slots until the server finally updates and you must wait to reload. This is often outlawed in multiplayer games.
* '''Lag loading''' or '''Tab loading''' - An exploit that allows a player to load their ship with weapons that it is unable to carry by default, such as the Helios on a Perseus. This is achieved by first selecting the weapon in question with the mouse button, keeping it selected while using the Tab key to switch to the Ship Selection screen, moving the cursor over the bank where the weapon is to be loaded, and finally pressing the Tab key one more time to change back to the Weapons Loadout screen and letting go of the mouse button just as the screen changes. The server will still think that you have your old ship selected, so its weapons permissions will not update in time to prevent you from loading something illegal. This is usually discouraged in multiplayer and considered cheating, but some multiplayer maps were actually made to accommodate this tactic. Lag loading is also possible in single-player. Contrary to popular belief, does not have anything to do with lag, nor is it harder to do in single player.
*'''Lock/Unlock''' - Refers to the "Lock" button on the mission briefing screen. The host (or in TvT game, team captains) have to click the "Lock" button to allow other pilots/wingmates to make ship/loadout changes.
*'''Low''' - Setting "Object Updates" in the Multiplayer tab of FreeSpace 2's options to "Low". This is the preferred setting for MP clients. The "Low" setting limits the connection bit rate between the MP host and the client in order to make the game run smoother for everyone.
* '''Quick jumping''' - A technique that involves all players in the Briefing menu to commit in order for the host to end the mission without needing to host again. It is usually used to give players not yet playing an opportunity to join the game instead of needing to wait for another match.
*'''TvT''' - Team versus Team game. The players are divided into two sides and fight for supremacy.

==Terms related to modelling==
*'''Greeble''' - Small piece of detail which serve no other purpose only to make a ship look better.
*'''[[HTL]]''' - Hardware Transformation & Lighting. This abbreviation has since mutated into shorthand for any user-created high-polygon ship, or generally any retail ship with extra details added by the community.
*'''LOD''' - Level of Detail. The further you get away from a ship, the less detailed it will be rendered.
*'''Multi-part turret''' - A multi-part turret is, in a word, a turret with one, two or three barrels.
*'''Single-part turret''' - A single-part turret, is, in a word, a turret without any barrels.
*'''TrueView''' - A plugin utility for [[trueSpace]]. Ideal for building hierarchy. However, not a must.

[[Category:Lists]]
[[Category:Multiplayer]]

Various Terms

2017-03-28T15:34:52Z

AdmiralRalwood: /* Designation Suffixes */ I think "gunship" is used often enough to qualify for this list.

This article lists down the '''various terms, abbreviations, and other jargon''' used by official FreeSpace sources as well as the FreeSpace community.

==Official Terminology==
===General===
* '''[[FRED]]''' - FReespace EDitor. The program created by Volition to make the mission and campaigns for both FreeSpace games. Released to the public along with said games.
* '''[[Portal:FreeSpace 2|FS2]]''' - FreeSpace 2. The second game of the series.

===File extensions===
These are FreeSpace-related extensions only.
*.ani - Animation files such as explosions
*.fc2 - FreeSpace 2 campaign
*.fs2 - FreeSpace 2 mission
*.fsm - FreeSpace 1 mission
*.pof - Model files with additional gameplay-related information like position of subsystems, turrets, etc.
*[[.tbl]] - Table file
*[[.tbm]] - Modular table
*.vp - Volition Pack files

===In-game Terminology===
*'''ETS''' - [[Energy Transfer System]]
*'''HUD''' - Heads-up Display. The interface the player uses while flying.
*'''Subsystem''' - Targetable and destroyable systems of a ship, e.g. radars, engines.
*'''TSM''' - Training Simulator Module

====Designation Prefixes====
* '''GT_''' - [[Galactic Terran Alliance|Galactic Terran]]
* '''NT_''' - [[Neo-Terran Front|Neo-Terran]]
* '''GV_''' - Galactic Vasudan
* '''PV_''' - [[Parliamentary Vasudan Empire|Parliamentary Vasudan]]
* '''GTV_''' - [[Galactic Terran-Vasudan Alliance|Galactic Terran-Vasudan]]
* '''S_''' - [[Shivans|Shivan]]

====Designation Suffixes====
* '''_A''' - [[Advanced Warning And Control System|AWACS]]
* '''_B''' - Bomber
* '''_C''' - Cruiser
* '''_Cv''' - Corvette
* '''_D''' - [[Destroyer]]
* '''_Dr''' - Drone
* '''_EP''' - Escape Pod
* '''_F''' - Fighter
* '''_Fr''' - Freighter
* '''_G''' - Gas Miner
* '''_I''' - Installation
* '''_J''' - [[Juggernaut]]
* '''_M''' - Medical Ship or Missile
* '''_NB''' - Navigation Buoy
* '''_S''' - Support Ship
* '''_SC''' - Science Cruiser
* '''_SG''' - Sentry Gun
* '''_T''' - Transport
* '''_W''' - Weapon ([[Weapon Comparison (FS1)|FreeSpace 1]])([[Weapon Comparison (FS2)|FreeSpace 2]])

===Fighter Units and Roles===
*'''Wing''' - A unit of fightercraft, varying in size from one to six ships. The normal number is four. Ships of a wing are labelled by their wing name and a number (i.e. Alpha 1, Alpha 2, and so on). The GTVA uses the Greek alphabet for its wings and the signs of the zodiac for hostile wings. In FS1, Shivan wings were named after Hindu gods. Wing labels are also sometimes used for groups of larger and similar vessels.
*'''Squadron''' - Refers to an organized group of pilots. The [[242nd Suicide Kings]] and [[203rd Scorpions]] are two examples.
*'''Stealth Recon''' - Fighters that specialize in infiltrating hostile territory and acquiring information without being detected. The [[GTF Pegasus|GTF ''Pegasus'']] and the [[GVF Ptah|GVF ''Ptah'']] are the only canon stealth fighters.
*'''Interceptor''' - A fighter role that aims at the destruction of hostile fighters and bombers. Interceptors are fast and agile, but are weakly shielded and armored.
*'''Space Superiority''' - A versatile fighter role that is capable in all sorts of roles, except for bombing. A celebrated example of a Space Superiority fighter is the [[GTF Myrmidon|GTF ''Myrmidon'']]
*'''Heavy Assault''' - Heavy Assault fighters have tremendous secondary capacity, heavy shielding and armoring at the expense of speed and maneuverability
*'''Bomber''' - A bomber is a very heavy craft that specializes in carrying bombs. They attack freighter-size ship and above. Bombers are very slow and easily taken down without fighter escorts. Bombers are further categorized into light, medium, and heavy bombers.

===Ship Types===
* '''Cruiser''' - Smallest combatant capital craft classification. Cruisers are at least several times the size of a fighter or bomber and possess mainly antifighter weaponry, with one or two (or in the case of the [[SC Rakshasa|SC ''Rakshasa'']], three) anticapital weapons. The defensive fire of a cruiser is rarely capable of stopping a determined bomber wing, and most are vulnerable to even a well-handled lone fighter. Unable to carry fighters. Canonical examples include the [[GTC Fenris|''Fenris'']] and the [[GTC Leviathan|''Leviathan'']]. In FS1, cruisers were deployed for both offensive and defensive tasks by all sides to any situation not requiring the attention of a destroyer. In FS2 Shivan cruisers are often deployed in mainline antiship and strike roles, while GTVA cruisers tend to be used as escorts and patrol craft.
* '''Corvette''' - Middle ground combatant capital craft, falling between the cruiser and the destroyer in size and capablity. Equipped with between two and four anticapital weapons and considerably more impressive antifighter armament than a cruiser. Corvettes are capable of defending themselves adequately against a small number of enemy fighters or bombers. With the exception of the [[SCv Moloch|SCv ''Moloch'']], corvettes are unable to carry fighters of their own. Corvettes appear to handle most of the antiship and strike duties for the GTVA fleet; Shivan corvettes are extremely rare and have only been deployed against GTVA destroyers canonically. Whether this is their role or not is guesswork.
* '''Destroyer''' - Large combatant capital craft, combining the functions of destroying enemy ships and transporting fighters. Destroyers vary wildly in armament and effectiveness against different types of targets. They will have at least one heavy-calibur anticapital weapon and probably several more, plus a number of cruiser-corvette anticapital weapons. Destroyers tend to need fighter cover more than corvettes; some of them actually mount fewer antifighter weapons, and all have much larger amounts of surface area that needs to be defended. Any situation with the direct involvement of a destroyer-class ship is by definition serious.
* '''Frigate''' - Semi-canonical ship class, both the Hippocrates and the Iceni have been referred to as frigates; the normally accepted role of a frigate is that of a pocket destroyer, lacking a fighterbay and fighter support facilities/crews enabling the ship to be shrunk down to only slightly bigger than a corvette.
* '''Superdestroyer''' - Bigger, meaner, and tougher than a destroyer, yet too small for the juggernaut classification; first applied well before the juggernaut classification came into existence. Only the [[GTD Hades|''Hades'']] and [[SD Lucifer|''Lucifer'']] have canonically been given this classification. The nature of the canonical superdestroyers was such that any appearance by them indicates ''the'' major effort by the controlling side. Their success is often decisive for that system, while their failure is a blow that is difficult to recover from.
* '''Juggernaut''' - The pinnacle of combatant capital craft, a juggernaut is capable of making mincemeat out of an enemy fleet singlehanded and is superbly equipped to combat other capital craft. Due to its large surface area its defenses against fightercraft attack are generally somewhat thinly spread, but a juggernaut's sheer ability to absorb damage means that only another juggernaut or a mass attack by corvettes and destroyers is capable of destroying one in anything like a timely manner. Only the [[SJ Sathanas|SJ ''Sathanas'']] has canonically been given this classification, though the ''Colossus'' could also be classified as juggernaut. The presence of a juggernaut, like a superdestroyer, indicates the controlling side considers the mission absolutely essential; decisive for the system if not the campaign or the entire war.
* '''Installation''' - A space station, described as "installation" because of its size, self-sufficiency, and permanence. The only installation classes canonically known are the [[GTI Arcadia|Arcadia]] and [[GTI Ganymede|Ganymede]]. The [[Galactic Terran-Vasudan Alliance|GTVA's]] naming system for installations generally includes something indicating their nature. Installation Riveria, Tombaugh Station, [[Enif Station]], and the Vega Installation are examples.

===Other Ship Types===
*'''Transport''' - Primarily used for transporting personnel. Sometimes used to transport marines in boarding a warship, as seen in the capture of a Shivan cruiser. However, it may also be used for repair purposes and evacuation. Transports are designed with minimal defenses and have to be escorted at all times to ensure survival.
*'''Freighter''' - Freighters carry important cargo and usually mount a few anti-fighter turrets. The largest canonical freighter is the [[GTFr Triton]].
*'''Gas miner''' - Used primarily to retrieve and transport nebular gas. Because of their often volatile contents, gas miners have an explosion yield far larger than ships of comparable size. The [[GTG Zephyrus]], [[GVG Anuket]], and [[SSG Rahu]] are the only three examples of gas miners.
*'''AWACS''' - AWACS vessels are primarily used for the expansion of radar detection in systems. Secondary purposes including jamming communications and detecting ships that are invisible to normal sensors. The [[GTA Charybdis]] and [[GVA Setekh]] are the only two examples of this classification.
*'''Escape Pod''' - The [[GTEP Hermes]] and [[GVEP Ra]] carry out this role. Escape pods are primarily for escape purposes, and are deployed from capital ships on the verge of destruction to save its crew and officers.

===Unique Ship Types===
*'''Medical Ship''' - Only the [[GTM Hippocrates]] carries this role. Primarily used to house patients under medical care, it is also used to evacuate refugees.
*'''Science Cruiser''' - Only the [[GTSC Faustus]] carries out this role. The Faustus appears to be tasked as a civilian science research vessel, but is also used by the military in times of war for weapons research. Science cruisers mount very few defenses and are therefore vulnerable to any form of assault.

===Others found in ships.tbl that are not classified as ships===
*'''Cargo Container''' - Carried by freighters. Cargo containers are unarmed and vulnerable to even fighter attack, and can only move via freighters.
*'''Sentry Gun''' - A small, vulnerable structure mounting one or more primary weapons. The largest of these is the [[GTSG Mjolnir]], which mounts a beam cannon. Oddly, Shivan sentry guns are rarely encountered in the FreeSpace 2 campaign.
*'''Knossos''' - The Knossos is an enormous subspace portal which, with its rotating components help stabilize a nearly-collapsed jump node.
*'''Meson Bomb''' - The [[TC-Meson Bomb]] is a remote detonation device which blasts about in a massive shockwave. The only canonical situations wherein these were deployed was in the destruction of the Knossos portal and the sealing off of the Capella jump nodes.
*'''Asteroid''' - Asteroids are of natural phenomenon. They are basically huge rocks in space that are harmful to even large capital ships as demonstrated in [[Rebels and Renegades]]. Asteroids may collide with capital ships and deal a severe amount of damage, but can be neutralized by primary weapons easily.
*'''Unknown Shivan rotating device''' - Known as the [[Shivan Comm Node]] in the editor, there has been no canonical description of the device as information regarding it is classified Level Omega. However, its name implies that it may be a kind of communication device of the Shivans.

===Special objects found in ships.tbl===
*'''SpaceHunk''' - The [[SpaceHunk]] is never used in the main FS2 campaign. It appears to be a large piece of debris from an [[SJ Sathanas]] juggernaut.
*'''SJD Sathanas''' - The [[SJD Sathanas]] is a small, triangular object that is used to represent a distant Sathanas juggernaut in [[Into the Lion's Den]] and all missions from [[Dunkerque]] onwards.
*'''Volition Bravos''' - The [[Volition Bravos]] is an easter egg that can be summoned onto the field using a cheat. It resembles a pirate ship manned by members of the Volition, Inc. staff. Although the Volition Bravos mounts nothing more than a few flak cannons and turret lasers, it is nearly impossible to destroy due to its incredibly high hitpoint count of ten billion.

===Weapons===
*'''Aspect-seeking''' - A type of secondary that must acquire a lock to track the target. See [[GTM Harpoon]].
*'''Countermeasure''' or '''CM''' - An anti-missile defensive mechanism for fighter-sized craft.
*'''Dumbfire''' - Secondary weapons cannot acquire any kind of lock on the target. See [[GTM Tempest]].
*'''Heat-seeking''' - A type of secondary weapon that acquires instant lock on the nearest target and chases it until it gets out of its cone.
*'''Primary''' - Primary weapons in ''FreeSpace'' are energy-based lasers.
*'''Secondary''' - Secondary weapons in ''FreeSpace'' are missiles and bombs.
*'''Turret laser''' - Primary weapons found on capital ships, transports, and freighters. An example would be the [[Terran Turret]]. See also '''blob turret'''.
*'''Anti-fighter beam''' - Small beam weapons on ships at least cruiser-sized. They are used to fire at enemy fighters and bombers, but can also provide fire support against small capital ships.
*'''Anti-capital beam''' - Beam weapons are the main armament of capital ships. They range from small such as the [[SGreen]], to large such as the [[BGreen]] and the juggernaut-scale [[BFGreen]].
*'''Slash beam''' - Beams which are used to sweep ships clean of subsystems. Only Terran and Vasudan warships arm these beam weapons.
*'''Swarm missile''' - Swarm missiles are secondary weapons that are fired in multiple numbers. See [[GTM Hornet]]

==Fan Terminology==
===In-game Terminology===
====Designation Prefixes====
* '''A_''' - [[Ancients|Ancient]]
* '''HL_''' - [[Hammer of Light]]

====Designation Suffixes====
* '''_BS''' or '''_Bs''' or '''BB''' - Battleship
* '''_Ca''' - Carrier
* '''_Dn''' - Dreadnaught
* '''_Fg''' - Frigate
* '''_Ff''' - Frigate
* '''_Gs''' - Gunship
* '''_H''' - Hive
* '''_SD''' - Superdestroyer
* '''_SJ''' - Super Juggernaut
* '''_TB''' - Tactical Bomber

===Ship Types===
* '''Carrier''' - Ship of any size whose primary purpose is to carry fightercraft, whether directly into combat or standing off and lending fightercraft support to ongoing operations as needed.
* '''Dreadnought''' - Generally understood to be a destroyer-sized craft, but built for the sole purpose of ship-to-ship combat and lacking a fighterbay or supporting a very limited number of fighters purely for self-defense.

===General===
* '''162''' - The Phoenix sub-forum on the Hard Light Productions Forums.
* '''AAA''' - Anti-fighter beam cannon(s)
* '''AB''' - Afterburner(s)
* '''Blob turret''' - A primary weapon-based, warship-mounted turret. The [[Terran Turret]] is an example.
* '''CM''' - Countermeasure
* '''CB''' - Command Briefing
* '''CBAnim''' - Command Briefing animation
* '''Colly''' - The [[GTVA Colossus|GTVA ''Colossus'']]
* '''FA''' - FRED Academy
* '''F2S''' - FreeSpace 2 Sector
* '''[[Portal:FreeSpace 1|FS1]]''' - Descent: FreeSpace—The Great War. Also called Conflict: FreeSpace—The Great War in Europe. The first game of the series.
* '''FS2_Open''' or '''FSO''' - The open source version of FreeSpace 2
* '''FS2NetD''' - FS2 Network Game Monitor; utility used to monitor FS2 network games being operated on the FS2Net servers.
* '''FS3''' - [[FreeSpace 3]], the theoretical sequel to FreeSpace 2
* '''GOG''' or '''GoG''' - Good Old Games. A digital distribution website that sells copies of FreeSpace 2. See [[Getting FreeSpace]].
* '''GW''' - Game-Warden
* '''Hattie''' - The [[GVD Hatshepsut|GVD ''Hatshepsut'']]
* '''HLP''' - Hard Light Productions
* '''HOTU''' - Home of the Underdogs. This website used to host a stripped-down version of FreeSpace 2.
* '''Lucy''' - The [[SD Lucifer|SD ''Lucifer'']]
* '''MediaVP''' or '''MVP''' - VP files with graphical enhancements for FreeSpace Open
* '''Retail''' - The original version of FreeSpace 2, as released by Volition in 1999, plus the official patches. (=not FreeSpace Open). ''Retail'' may also be used to refer to an official campaign, depending on context.
* '''RTB''' - Return to Base. Used to refer to the directive that tells the player to return to base.
* '''SCP''' - Source Code Project. The people responsible for creating, maintaining and debugging FS2_Open.
* '''SEXP''' - Symbolic EXPressions. Special function strings within FRED that allow for complex mission objectives and other things to be carried out by a mission bulider.
* '''SG''' - Sectorgame. This website hosts the FreeSpace 2 Sector.
* '''ST''' - [[Silent Threat]]
* '''TC''' - Total Conversion. See [[Total conversions]]
* '''V''' or '''[V]''' - [[Volition]], Inc., the developer of FreeSpace and FreeSpace 2.
* '''VBB''' - Volition Bulletin Board. The boards Volition maintained as a centre for the FS community. Now defunct.
* '''VW''' - Volition Watch, developer fansite covering the FreeSpace, Red Faction and Summoner series. Awaiting demolition.
* '''Zod''' - A term used to describe [[Vasudans]]. Derived from Zodiac because their fighter wings were designated based on them in FS1. The term has been coined by Eishtmo.

===Campaign Abbreviations===
:'''''This list is incomplete and not necessarily up-to-date. See also: [[Narwhal's Campaign List]]'''''
* '''158''' - The 158th Banshee Squadron
* '''AA''' - Aeos Affair
* '''AAB''' - Ascension and Beyond
* '''AG''' - [[Alcibiades' Gamble]]
* '''AHTW''' - All Hands to War
* '''AotD''' - Angels of the Damned
* '''[[ASW]]''' - The [[Ancient-Shivan War (campaign)|Ancient-Shivan War]]
* '''BP''' - [[Blue Planet]]
** '''BP:AoA''' or '''AoA''' - [[Blue Planet: Age of Aquarius]]
** '''BP:WiH''' or '''WiH''' - [[Blue Planet: War in Heaven]]
* '''BtRL''' - [[Beyond the Red Line]]
* '''BWO''' - [[Blackwater Operations]]
* '''CoW''' - Casualties of War
* '''CoS''', '''Nukemod-CoS''' or '''Nukemod''' - [[Nukemod|Nukemod - Children of Shiva]]
* '''CtS''' - [[Crossing the Styx]]
* '''DEM''' - [[Deus Ex Machina]]
* '''FSPort''' - [[FreeSpace Port]]
** '''ST:R''' - [[Silent Threat: Reborn]]
* '''FSU''' - The FreeSpace Upgrade Project
* '''INF''' - [[Inferno]]. This may refer to any Inferno mod.
** '''INFA''' or '''INFA1''' - [[Inferno: Alliance]]
** '''INFA2''' - The sequel to Inferno: Alliance
** '''INFR1''' - [[Inferno Release 1]]
** '''INFASA''' - Inferno: Alliance Standalone
** '''INF SCP''' - Inferno SCP
* '''ITDoH''' - Into The Depths of Hell
* '''ITHOV''' - Into the Halls of Valhalla
* '''JAD''' - [[Just Another Day]]
** '''JAD2''' - [[Just Another Day 2: Electric Boogaloo]]
** '''JAD3''' - [[Just Another Day 3: Shivans on a Plane]]
* '''JtEP''' - The Journey to Epsilon Pegasi
* '''LM''' - The Lightning Marshal
* '''MT''' - Machina Terra
* '''MG''' - Mind Games
* '''NTV''' - [[Neo-Terra Victorious]]
* '''OTT''' - [[Over the Top]]
* '''PI''' - [[The Procyon Insurgency]]
* '''RR''' - Renegade Resurgence
* '''SA''' - The Scroll of Antankharzim
* '''SGWP2''' - [[The Second Great War Part II]]
* '''SoL''' - [[Shadows of Lylat]]
* '''SWC''' - Star Wars Conversion
** '''FotG''' - [[Fate of the Galaxy]]
* '''TAP''' - [[The Apocalypse Project]]
* '''TBP''' - [[The Babylon Project]]
** '''TBP:RW''' or '''RW''' - [[Raider Wars]]
** '''TBP:FH''' or '''FH''' - [[Fortune Hunters]]
* '''TI''' - Twisted Infinities
* '''TotT''' or '''ToT''' - Teeth of the Tiger
* '''TS''' - Technological Superiority
* '''TTP''' - The Titan Project
* '''TVWP''' - [[Terran-Vasudan War Project]]
* '''WCS''' - [[Wing Commander Saga]]

===Multiplayer===
The following is a list of some terms commonly seen on multiplayer chat screens.
* '''AI''' - Artificial Intelligence. This refers to any computer-controlled ship.
* '''Coop''' - Cooperative game. All players are on the same side and work together to accomplish the mission objectives.
* '''Dogfight''' or '''DF''' - A free-for-all type of game, essentially the Deathmatch of FreeSpace. All players are on their own and fight for survival.
* '''EMP''' - The EMP missile
* '''Fire''' - The Infyrno missile
* '''Fish''' - The Piranha missile
* '''Lag''' - Latency. This refers to the "jumpiness" in a multiplayer game due to slow Internet connections. FreeSpace has always had a lag problem, and even modern, high-speed connections have trouble hosting and playing online FreeSpace games. Can be greatly mitigated by having all players set their "Object Update" setting to Low.
* '''Lag bombing''' - Double-linking your secondary slot, firing, then quickly switching to your other secondary slot and firing it. Continue cycling and firing secondary slots until the server finally updates and you must wait to reload. This is often outlawed in multiplayer games.
* '''Lag loading''' or '''Tab loading''' - An exploit that allows a player to load their ship with weapons that it is unable to carry by default, such as the Helios on a Perseus. This is achieved by first selecting the weapon in question with the mouse button, keeping it selected while using the Tab key to switch to the Ship Selection screen, moving the cursor over the bank where the weapon is to be loaded, and finally pressing the Tab key one more time to change back to the Weapons Loadout screen and letting go of the mouse button just as the screen changes. The server will still think that you have your old ship selected, so its weapons permissions will not update in time to prevent you from loading something illegal. This is usually discouraged in multiplayer and considered cheating, but some multiplayer maps were actually made to accommodate this tactic. Lag loading is also possible in single-player. Contrary to popular belief, does not have anything to do with lag, nor is it harder to do in single player.
*'''Lock/Unlock''' - Refers to the "Lock" button on the mission briefing screen. The host (or in TvT game, team captains) have to click the "Lock" button to allow other pilots/wingmates to make ship/loadout changes.
*'''Low''' - Setting "Object Updates" in the Multiplayer tab of FreeSpace 2's options to "Low". This is the preferred setting for MP clients. The "Low" setting limits the connection bit rate between the MP host and the client in order to make the game run smoother for everyone.
* '''Quick jumping''' - A technique that involves all players in the Briefing menu to commit in order for the host to end the mission without needing to host again. It is usually used to give players not yet playing an opportunity to join the game instead of needing to wait for another match.
*'''TvT''' - Team versus Team game. The players are divided into two sides and fight for supremacy.

==Terms related to modelling==
*'''Greeble''' - Small piece of detail which serve no other purpose only to make a ship look better.
*'''[[HTL]]''' - Hardware Transformation & Lighting. This abbreviation has since mutated into shorthand for any user-created high-polygon ship, or generally any retail ship with extra details added by the community.
*'''LOD''' - Level of Detail. The further you get away from a ship, the less detailed it will be rendered.
*'''Multi-part turret''' - A multi-part turret is, in a word, a turret with one, two or three barrels.
*'''Single-part turret''' - A single-part turret, is, in a word, a turret without any barrels.
*'''TrueView''' - A plugin utility for [[trueSpace]]. Ideal for building hierarchy. However, not a must.

[[Category:Lists]]
[[Category:Multiplayer]]

Various Terms

2017-03-28T15:31:49Z

AdmiralRalwood: I'm pretty sure freighters ARE classified as ships.

This article lists down the '''various terms, abbreviations, and other jargon''' used by official FreeSpace sources as well as the FreeSpace community.

==Official Terminology==
===General===
* '''[[FRED]]''' - FReespace EDitor. The program created by Volition to make the mission and campaigns for both FreeSpace games. Released to the public along with said games.
* '''[[Portal:FreeSpace 2|FS2]]''' - FreeSpace 2. The second game of the series.

===File extensions===
These are FreeSpace-related extensions only.
*.ani - Animation files such as explosions
*.fc2 - FreeSpace 2 campaign
*.fs2 - FreeSpace 2 mission
*.fsm - FreeSpace 1 mission
*.pof - Model files with additional gameplay-related information like position of subsystems, turrets, etc.
*[[.tbl]] - Table file
*[[.tbm]] - Modular table
*.vp - Volition Pack files

===In-game Terminology===
*'''ETS''' - [[Energy Transfer System]]
*'''HUD''' - Heads-up Display. The interface the player uses while flying.
*'''Subsystem''' - Targetable and destroyable systems of a ship, e.g. radars, engines.
*'''TSM''' - Training Simulator Module

====Designation Prefixes====
* '''GT_''' - [[Galactic Terran Alliance|Galactic Terran]]
* '''NT_''' - [[Neo-Terran Front|Neo-Terran]]
* '''GV_''' - Galactic Vasudan
* '''PV_''' - [[Parliamentary Vasudan Empire|Parliamentary Vasudan]]
* '''GTV_''' - [[Galactic Terran-Vasudan Alliance|Galactic Terran-Vasudan]]
* '''S_''' - [[Shivans|Shivan]]

====Designation Suffixes====
* '''_A''' - [[Advanced Warning And Control System|AWACS]]
* '''_B''' - Bomber
* '''_C''' - Cruiser
* '''_Cv''' - Corvette
* '''_D''' - [[Destroyer]]
* '''_Dr''' - Drone
* '''_EP''' - Escape Pod
* '''_F''' - Fighter
* '''_Fr''' - Freighter
* '''_G''' - Gas Miner
* '''_I''' - Installation
* '''_J''' - [[Juggernaut]]
* '''_M''' - Medical Ship or Missile
* '''_NB''' - Navigation Buoy
* '''_S''' - Support Ship
* '''_SC''' - Science Cruiser
* '''_SG''' - Sentry Gun
* '''_T''' - Transport
* '''_W''' - Weapon ([[Weapon Comparison (FS1)|FreeSpace 1]])([[Weapon Comparison (FS2)|FreeSpace 2]])

===Fighter Units and Roles===
*'''Wing''' - A unit of fightercraft, varying in size from one to six ships. The normal number is four. Ships of a wing are labelled by their wing name and a number (i.e. Alpha 1, Alpha 2, and so on). The GTVA uses the Greek alphabet for its wings and the signs of the zodiac for hostile wings. In FS1, Shivan wings were named after Hindu gods. Wing labels are also sometimes used for groups of larger and similar vessels.
*'''Squadron''' - Refers to an organized group of pilots. The [[242nd Suicide Kings]] and [[203rd Scorpions]] are two examples.
*'''Stealth Recon''' - Fighters that specialize in infiltrating hostile territory and acquiring information without being detected. The [[GTF Pegasus|GTF ''Pegasus'']] and the [[GVF Ptah|GVF ''Ptah'']] are the only canon stealth fighters.
*'''Interceptor''' - A fighter role that aims at the destruction of hostile fighters and bombers. Interceptors are fast and agile, but are weakly shielded and armored.
*'''Space Superiority''' - A versatile fighter role that is capable in all sorts of roles, except for bombing. A celebrated example of a Space Superiority fighter is the [[GTF Myrmidon|GTF ''Myrmidon'']]
*'''Heavy Assault''' - Heavy Assault fighters have tremendous secondary capacity, heavy shielding and armoring at the expense of speed and maneuverability
*'''Bomber''' - A bomber is a very heavy craft that specializes in carrying bombs. They attack freighter-size ship and above. Bombers are very slow and easily taken down without fighter escorts. Bombers are further categorized into light, medium, and heavy bombers.

===Ship Types===
* '''Cruiser''' - Smallest combatant capital craft classification. Cruisers are at least several times the size of a fighter or bomber and possess mainly antifighter weaponry, with one or two (or in the case of the [[SC Rakshasa|SC ''Rakshasa'']], three) anticapital weapons. The defensive fire of a cruiser is rarely capable of stopping a determined bomber wing, and most are vulnerable to even a well-handled lone fighter. Unable to carry fighters. Canonical examples include the [[GTC Fenris|''Fenris'']] and the [[GTC Leviathan|''Leviathan'']]. In FS1, cruisers were deployed for both offensive and defensive tasks by all sides to any situation not requiring the attention of a destroyer. In FS2 Shivan cruisers are often deployed in mainline antiship and strike roles, while GTVA cruisers tend to be used as escorts and patrol craft.
* '''Corvette''' - Middle ground combatant capital craft, falling between the cruiser and the destroyer in size and capablity. Equipped with between two and four anticapital weapons and considerably more impressive antifighter armament than a cruiser. Corvettes are capable of defending themselves adequately against a small number of enemy fighters or bombers. With the exception of the [[SCv Moloch|SCv ''Moloch'']], corvettes are unable to carry fighters of their own. Corvettes appear to handle most of the antiship and strike duties for the GTVA fleet; Shivan corvettes are extremely rare and have only been deployed against GTVA destroyers canonically. Whether this is their role or not is guesswork.
* '''Destroyer''' - Large combatant capital craft, combining the functions of destroying enemy ships and transporting fighters. Destroyers vary wildly in armament and effectiveness against different types of targets. They will have at least one heavy-calibur anticapital weapon and probably several more, plus a number of cruiser-corvette anticapital weapons. Destroyers tend to need fighter cover more than corvettes; some of them actually mount fewer antifighter weapons, and all have much larger amounts of surface area that needs to be defended. Any situation with the direct involvement of a destroyer-class ship is by definition serious.
* '''Frigate''' - Semi-canonical ship class, both the Hippocrates and the Iceni have been referred to as frigates; the normally accepted role of a frigate is that of a pocket destroyer, lacking a fighterbay and fighter support facilities/crews enabling the ship to be shrunk down to only slightly bigger than a corvette.
* '''Superdestroyer''' - Bigger, meaner, and tougher than a destroyer, yet too small for the juggernaut classification; first applied well before the juggernaut classification came into existence. Only the [[GTD Hades|''Hades'']] and [[SD Lucifer|''Lucifer'']] have canonically been given this classification. The nature of the canonical superdestroyers was such that any appearance by them indicates ''the'' major effort by the controlling side. Their success is often decisive for that system, while their failure is a blow that is difficult to recover from.
* '''Juggernaut''' - The pinnacle of combatant capital craft, a juggernaut is capable of making mincemeat out of an enemy fleet singlehanded and is superbly equipped to combat other capital craft. Due to its large surface area its defenses against fightercraft attack are generally somewhat thinly spread, but a juggernaut's sheer ability to absorb damage means that only another juggernaut or a mass attack by corvettes and destroyers is capable of destroying one in anything like a timely manner. Only the [[SJ Sathanas|SJ ''Sathanas'']] has canonically been given this classification, though the ''Colossus'' could also be classified as juggernaut. The presence of a juggernaut, like a superdestroyer, indicates the controlling side considers the mission absolutely essential; decisive for the system if not the campaign or the entire war.
* '''Installation''' - A space station, described as "installation" because of its size, self-sufficiency, and permanence. The only installation classes canonically known are the [[GTI Arcadia|Arcadia]] and [[GTI Ganymede|Ganymede]]. The [[Galactic Terran-Vasudan Alliance|GTVA's]] naming system for installations generally includes something indicating their nature. Installation Riveria, Tombaugh Station, [[Enif Station]], and the Vega Installation are examples.

===Other Ship Types===
*'''Transport''' - Primarily used for transporting personnel. Sometimes used to transport marines in boarding a warship, as seen in the capture of a Shivan cruiser. However, it may also be used for repair purposes and evacuation. Transports are designed with minimal defenses and have to be escorted at all times to ensure survival.
*'''Freighter''' - Freighters carry important cargo and usually mount a few anti-fighter turrets. The largest canonical freighter is the [[GTFr Triton]].
*'''Gas miner''' - Used primarily to retrieve and transport nebular gas. Because of their often volatile contents, gas miners have an explosion yield far larger than ships of comparable size. The [[GTG Zephyrus]], [[GVG Anuket]], and [[SSG Rahu]] are the only three examples of gas miners.
*'''AWACS''' - AWACS vessels are primarily used for the expansion of radar detection in systems. Secondary purposes including jamming communications and detecting ships that are invisible to normal sensors. The [[GTA Charybdis]] and [[GVA Setekh]] are the only two examples of this classification.
*'''Escape Pod''' - The [[GTEP Hermes]] and [[GVEP Ra]] carry out this role. Escape pods are primarily for escape purposes, and are deployed from capital ships on the verge of destruction to save its crew and officers.

===Unique Ship Types===
*'''Medical Ship''' - Only the [[GTM Hippocrates]] carries this role. Primarily used to house patients under medical care, it is also used to evacuate refugees.
*'''Science Cruiser''' - Only the [[GTSC Faustus]] carries out this role. The Faustus appears to be tasked as a civilian science research vessel, but is also used by the military in times of war for weapons research. Science cruisers mount very few defenses and are therefore vulnerable to any form of assault.

===Others found in ships.tbl that are not classified as ships===
*'''Cargo Container''' - Carried by freighters. Cargo containers are unarmed and vulnerable to even fighter attack, and can only move via freighters.
*'''Sentry Gun''' - A small, vulnerable structure mounting one or more primary weapons. The largest of these is the [[GTSG Mjolnir]], which mounts a beam cannon. Oddly, Shivan sentry guns are rarely encountered in the FreeSpace 2 campaign.
*'''Knossos''' - The Knossos is an enormous subspace portal which, with its rotating components help stabilize a nearly-collapsed jump node.
*'''Meson Bomb''' - The [[TC-Meson Bomb]] is a remote detonation device which blasts about in a massive shockwave. The only canonical situations wherein these were deployed was in the destruction of the Knossos portal and the sealing off of the Capella jump nodes.
*'''Asteroid''' - Asteroids are of natural phenomenon. They are basically huge rocks in space that are harmful to even large capital ships as demonstrated in [[Rebels and Renegades]]. Asteroids may collide with capital ships and deal a severe amount of damage, but can be neutralized by primary weapons easily.
*'''Unknown Shivan rotating device''' - Known as the [[Shivan Comm Node]] in the editor, there has been no canonical description of the device as information regarding it is classified Level Omega. However, its name implies that it may be a kind of communication device of the Shivans.

===Special objects found in ships.tbl===
*'''SpaceHunk''' - The [[SpaceHunk]] is never used in the main FS2 campaign. It appears to be a large piece of debris from an [[SJ Sathanas]] juggernaut.
*'''SJD Sathanas''' - The [[SJD Sathanas]] is a small, triangular object that is used to represent a distant Sathanas juggernaut in [[Into the Lion's Den]] and all missions from [[Dunkerque]] onwards.
*'''Volition Bravos''' - The [[Volition Bravos]] is an easter egg that can be summoned onto the field using a cheat. It resembles a pirate ship manned by members of the Volition, Inc. staff. Although the Volition Bravos mounts nothing more than a few flak cannons and turret lasers, it is nearly impossible to destroy due to its incredibly high hitpoint count of ten billion.

===Weapons===
*'''Aspect-seeking''' - A type of secondary that must acquire a lock to track the target. See [[GTM Harpoon]].
*'''Countermeasure''' or '''CM''' - An anti-missile defensive mechanism for fighter-sized craft.
*'''Dumbfire''' - Secondary weapons cannot acquire any kind of lock on the target. See [[GTM Tempest]].
*'''Heat-seeking''' - A type of secondary weapon that acquires instant lock on the nearest target and chases it until it gets out of its cone.
*'''Primary''' - Primary weapons in ''FreeSpace'' are energy-based lasers.
*'''Secondary''' - Secondary weapons in ''FreeSpace'' are missiles and bombs.
*'''Turret laser''' - Primary weapons found on capital ships, transports, and freighters. An example would be the [[Terran Turret]]. See also '''blob turret'''.
*'''Anti-fighter beam''' - Small beam weapons on ships at least cruiser-sized. They are used to fire at enemy fighters and bombers, but can also provide fire support against small capital ships.
*'''Anti-capital beam''' - Beam weapons are the main armament of capital ships. They range from small such as the [[SGreen]], to large such as the [[BGreen]] and the juggernaut-scale [[BFGreen]].
*'''Slash beam''' - Beams which are used to sweep ships clean of subsystems. Only Terran and Vasudan warships arm these beam weapons.
*'''Swarm missile''' - Swarm missiles are secondary weapons that are fired in multiple numbers. See [[GTM Hornet]]

==Fan Terminology==
===In-game Terminology===
====Designation Prefixes====
* '''A_''' - [[Ancients|Ancient]]
* '''HL_''' - [[Hammer of Light]]

====Designation Suffixes====
* '''_BS''' or '''_Bs''' or '''BB''' - Battleship
* '''_Ca''' - Carrier
* '''_Dn''' - Dreadnaught
* '''_Fg''' - Frigate
* '''_Ff''' - Frigate
* '''_H''' - Hive
* '''_SD''' - Superdestroyer
* '''_SJ''' - Super Juggernaut
* '''_TB''' - Tactical Bomber

===Ship Types===
* '''Carrier''' - Ship of any size whose primary purpose is to carry fightercraft, whether directly into combat or standing off and lending fightercraft support to ongoing operations as needed.
* '''Dreadnought''' - Generally understood to be a destroyer-sized craft, but built for the sole purpose of ship-to-ship combat and lacking a fighterbay or supporting a very limited number of fighters purely for self-defense.

===General===
* '''162''' - The Phoenix sub-forum on the Hard Light Productions Forums.
* '''AAA''' - Anti-fighter beam cannon(s)
* '''AB''' - Afterburner(s)
* '''Blob turret''' - A primary weapon-based, warship-mounted turret. The [[Terran Turret]] is an example.
* '''CM''' - Countermeasure
* '''CB''' - Command Briefing
* '''CBAnim''' - Command Briefing animation
* '''Colly''' - The [[GTVA Colossus|GTVA ''Colossus'']]
* '''FA''' - FRED Academy
* '''F2S''' - FreeSpace 2 Sector
* '''[[Portal:FreeSpace 1|FS1]]''' - Descent: FreeSpace—The Great War. Also called Conflict: FreeSpace—The Great War in Europe. The first game of the series.
* '''FS2_Open''' or '''FSO''' - The open source version of FreeSpace 2
* '''FS2NetD''' - FS2 Network Game Monitor; utility used to monitor FS2 network games being operated on the FS2Net servers.
* '''FS3''' - [[FreeSpace 3]], the theoretical sequel to FreeSpace 2
* '''GOG''' or '''GoG''' - Good Old Games. A digital distribution website that sells copies of FreeSpace 2. See [[Getting FreeSpace]].
* '''GW''' - Game-Warden
* '''Hattie''' - The [[GVD Hatshepsut|GVD ''Hatshepsut'']]
* '''HLP''' - Hard Light Productions
* '''HOTU''' - Home of the Underdogs. This website used to host a stripped-down version of FreeSpace 2.
* '''Lucy''' - The [[SD Lucifer|SD ''Lucifer'']]
* '''MediaVP''' or '''MVP''' - VP files with graphical enhancements for FreeSpace Open
* '''Retail''' - The original version of FreeSpace 2, as released by Volition in 1999, plus the official patches. (=not FreeSpace Open). ''Retail'' may also be used to refer to an official campaign, depending on context.
* '''RTB''' - Return to Base. Used to refer to the directive that tells the player to return to base.
* '''SCP''' - Source Code Project. The people responsible for creating, maintaining and debugging FS2_Open.
* '''SEXP''' - Symbolic EXPressions. Special function strings within FRED that allow for complex mission objectives and other things to be carried out by a mission bulider.
* '''SG''' - Sectorgame. This website hosts the FreeSpace 2 Sector.
* '''ST''' - [[Silent Threat]]
* '''TC''' - Total Conversion. See [[Total conversions]]
* '''V''' or '''[V]''' - [[Volition]], Inc., the developer of FreeSpace and FreeSpace 2.
* '''VBB''' - Volition Bulletin Board. The boards Volition maintained as a centre for the FS community. Now defunct.
* '''VW''' - Volition Watch, developer fansite covering the FreeSpace, Red Faction and Summoner series. Awaiting demolition.
* '''Zod''' - A term used to describe [[Vasudans]]. Derived from Zodiac because their fighter wings were designated based on them in FS1. The term has been coined by Eishtmo.

===Campaign Abbreviations===
:'''''This list is incomplete and not necessarily up-to-date. See also: [[Narwhal's Campaign List]]'''''
* '''158''' - The 158th Banshee Squadron
* '''AA''' - Aeos Affair
* '''AAB''' - Ascension and Beyond
* '''AG''' - [[Alcibiades' Gamble]]
* '''AHTW''' - All Hands to War
* '''AotD''' - Angels of the Damned
* '''[[ASW]]''' - The [[Ancient-Shivan War (campaign)|Ancient-Shivan War]]
* '''BP''' - [[Blue Planet]]
** '''BP:AoA''' or '''AoA''' - [[Blue Planet: Age of Aquarius]]
** '''BP:WiH''' or '''WiH''' - [[Blue Planet: War in Heaven]]
* '''BtRL''' - [[Beyond the Red Line]]
* '''BWO''' - [[Blackwater Operations]]
* '''CoW''' - Casualties of War
* '''CoS''', '''Nukemod-CoS''' or '''Nukemod''' - [[Nukemod|Nukemod - Children of Shiva]]
* '''CtS''' - [[Crossing the Styx]]
* '''DEM''' - [[Deus Ex Machina]]
* '''FSPort''' - [[FreeSpace Port]]
** '''ST:R''' - [[Silent Threat: Reborn]]
* '''FSU''' - The FreeSpace Upgrade Project
* '''INF''' - [[Inferno]]. This may refer to any Inferno mod.
** '''INFA''' or '''INFA1''' - [[Inferno: Alliance]]
** '''INFA2''' - The sequel to Inferno: Alliance
** '''INFR1''' - [[Inferno Release 1]]
** '''INFASA''' - Inferno: Alliance Standalone
** '''INF SCP''' - Inferno SCP
* '''ITDoH''' - Into The Depths of Hell
* '''ITHOV''' - Into the Halls of Valhalla
* '''JAD''' - [[Just Another Day]]
** '''JAD2''' - [[Just Another Day 2: Electric Boogaloo]]
** '''JAD3''' - [[Just Another Day 3: Shivans on a Plane]]
* '''JtEP''' - The Journey to Epsilon Pegasi
* '''LM''' - The Lightning Marshal
* '''MT''' - Machina Terra
* '''MG''' - Mind Games
* '''NTV''' - [[Neo-Terra Victorious]]
* '''OTT''' - [[Over the Top]]
* '''PI''' - [[The Procyon Insurgency]]
* '''RR''' - Renegade Resurgence
* '''SA''' - The Scroll of Antankharzim
* '''SGWP2''' - [[The Second Great War Part II]]
* '''SoL''' - [[Shadows of Lylat]]
* '''SWC''' - Star Wars Conversion
** '''FotG''' - [[Fate of the Galaxy]]
* '''TAP''' - [[The Apocalypse Project]]
* '''TBP''' - [[The Babylon Project]]
** '''TBP:RW''' or '''RW''' - [[Raider Wars]]
** '''TBP:FH''' or '''FH''' - [[Fortune Hunters]]
* '''TI''' - Twisted Infinities
* '''TotT''' or '''ToT''' - Teeth of the Tiger
* '''TS''' - Technological Superiority
* '''TTP''' - The Titan Project
* '''TVWP''' - [[Terran-Vasudan War Project]]
* '''WCS''' - [[Wing Commander Saga]]

===Multiplayer===
The following is a list of some terms commonly seen on multiplayer chat screens.
* '''AI''' - Artificial Intelligence. This refers to any computer-controlled ship.
* '''Coop''' - Cooperative game. All players are on the same side and work together to accomplish the mission objectives.
* '''Dogfight''' or '''DF''' - A free-for-all type of game, essentially the Deathmatch of FreeSpace. All players are on their own and fight for survival.
* '''EMP''' - The EMP missile
* '''Fire''' - The Infyrno missile
* '''Fish''' - The Piranha missile
* '''Lag''' - Latency. This refers to the "jumpiness" in a multiplayer game due to slow Internet connections. FreeSpace has always had a lag problem, and even modern, high-speed connections have trouble hosting and playing online FreeSpace games. Can be greatly mitigated by having all players set their "Object Update" setting to Low.
* '''Lag bombing''' - Double-linking your secondary slot, firing, then quickly switching to your other secondary slot and firing it. Continue cycling and firing secondary slots until the server finally updates and you must wait to reload. This is often outlawed in multiplayer games.
* '''Lag loading''' or '''Tab loading''' - An exploit that allows a player to load their ship with weapons that it is unable to carry by default, such as the Helios on a Perseus. This is achieved by first selecting the weapon in question with the mouse button, keeping it selected while using the Tab key to switch to the Ship Selection screen, moving the cursor over the bank where the weapon is to be loaded, and finally pressing the Tab key one more time to change back to the Weapons Loadout screen and letting go of the mouse button just as the screen changes. The server will still think that you have your old ship selected, so its weapons permissions will not update in time to prevent you from loading something illegal. This is usually discouraged in multiplayer and considered cheating, but some multiplayer maps were actually made to accommodate this tactic. Lag loading is also possible in single-player. Contrary to popular belief, does not have anything to do with lag, nor is it harder to do in single player.
*'''Lock/Unlock''' - Refers to the "Lock" button on the mission briefing screen. The host (or in TvT game, team captains) have to click the "Lock" button to allow other pilots/wingmates to make ship/loadout changes.
*'''Low''' - Setting "Object Updates" in the Multiplayer tab of FreeSpace 2's options to "Low". This is the preferred setting for MP clients. The "Low" setting limits the connection bit rate between the MP host and the client in order to make the game run smoother for everyone.
* '''Quick jumping''' - A technique that involves all players in the Briefing menu to commit in order for the host to end the mission without needing to host again. It is usually used to give players not yet playing an opportunity to join the game instead of needing to wait for another match.
*'''TvT''' - Team versus Team game. The players are divided into two sides and fight for supremacy.

==Terms related to modelling==
*'''Greeble''' - Small piece of detail which serve no other purpose only to make a ship look better.
*'''[[HTL]]''' - Hardware Transformation & Lighting. This abbreviation has since mutated into shorthand for any user-created high-polygon ship, or generally any retail ship with extra details added by the community.
*'''LOD''' - Level of Detail. The further you get away from a ship, the less detailed it will be rendered.
*'''Multi-part turret''' - A multi-part turret is, in a word, a turret with one, two or three barrels.
*'''Single-part turret''' - A single-part turret, is, in a word, a turret without any barrels.
*'''TrueView''' - A plugin utility for [[trueSpace]]. Ideal for building hierarchy. However, not a must.

[[Category:Lists]]
[[Category:Multiplayer]]

Game settings.tbl

2016-12-31T06:57:43Z

AdmiralRalwood: /* Sample Entry */ Using an example that's actually a valid game_settings.tbl setting.

{{SCP_table}}

{{TableVersionGit|2015-11-21|71cf169}}

The '''game_settings.tbl''', also known as mod.tbl, defines options that can be changed globally.

This table is one of the [[Modular Tables]] and can be extended with xxx-mod.tbm

[[Tables|List of Tables]]

==#GAME SETTINGS==
Optional. Contains settings that affect how the engine works. 

===$Minimum version:===
{{Table373|
Specifies the minimum version of FreeSpace Open that this mod supports. If the version specified here is greater than the version of the current build, an error message is displayed.
}}

====+Major:====
{{Table373|
Required. Sets the major component of the minimum version.
*Syntax: '''''Integer''''' 
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Minor:====
{{Table373|
Required. Sets the minor component of the minimum version.
*Syntax: '''''Integer''''' 
*Example: '''''7''''' (for a minimum version of 3.7.3.20151121)
}}

====+Build:====
{{Table373|
Required. Sets the build component of the minimum version.
*Syntax: '''''Integer''''' 
*Example: '''''3''''' (for a minimum version of 3.7.3.20151121)
}}

====+Revision:====
{{Table373|
Optional. Sets the revision component of the minimum version. If no revision is given then all builds of that release are supported (even nightly builds if there are any).
For nightly builds this is the date in YYYYMMDD format.
*Syntax: '''''Integer''''' 
*Example: '''''20151121''''' (for a minimum version of 3.7.3.20151121)
}}

==#CAMPAIGN SETTINGS==
Optional. This group contains various Campaign related settings and overrides. 

===$Default Campaign File Name:===
Defines which campaign will be selected by default for new pilots. A file extension is not needed and, if present, is removed by the code.
*Syntax: '''''String''''' 

===#Ignored Campaign File Names===
Optional. Defines which campaigns, if present, will not appear in the Campaign Room. Only single-player campaigns can be ignored. ''File extensions are required.''
{{Table371|As of 3.7.1, file extensions are not required and, if present, are removed by the code.}}
====$Campaign File Name:====
File name of the campaign to ignore. Multiple entries may exist.
*Syntax: '''''String''''' 

===$Red-alert applies to delayed ships:===
Controls whether red-alert saved statistics (hitpoints, weapons, subsystem strengths) will be restored for ships that are not present at mission start.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

==#HUD SETTINGS==
Optional. This group contains various HUD behavior settings and overrides 

===$Directive Wait Time:===
*Defines how long the game will wait before displaying a directive.
*Syntax: '''''Integer''''' 
*Values: '''''Greater than or equal to 0 ms'''''

===$Cutscene camera displays HUD:===
Show the HUD when the cutscene camera is enabled.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Cutscene camera disables HUD: and had a default of YES.

===$Full color head animations:===
Enables full-color head ANIs. Normal head ANIs will appear in gray.
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

In earlier versions of the code, this option was controlled by $Color head animations with hud colors: and had a default of YES.

==#SEXP SETTINGS==
Optional. This group contains SEXP settings and overrides. 

===$Loop SEXPs Then Arguments:===
Flips how when-argument settings loop. See: [http://www.hard-light.net/forums/index.php?topic=79602.0 SEXP Argument changes via mod.tbl]
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

===$Use Alternate Chaining Behavior:===
When set, this makes the event chaining behavior act as people expected it to be in [http://scp.indiegames.us/mantis/view.php?id=82 Mantis #82].
*Syntax: '''''Boolean''''' 
*Default Value: '''''NO'''''

==#GRAPHICS SETTINGS==
Optional. This group contains settings related to graphics. 

===$Enable External Shaders:===
Enables the use of external shader files. By default, the engine will use the built-in shaders.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Default Detail Level:===
{{Table3615|
Determines which graphics detail level preset (low, medium, high, very high) acts as the default for new pilots.
*Syntax: '''''Integer''''' (0-3)
*Default Value: '''''3''''' (very high) }}

===$Briefing Window FOV:===
{{Table371|
Determines the FOV in the briefing Icon window. Retail default for this is 0.29375, previous versions of FSO used a value of 0.5.
*Syntax: '''''Float''''' (0.0 to 1.0)
*Default Value: '''''0.29375''''' }}

===$Generic Pain Flash Factor:===
{{Table373|
Determines the intensity of the pain red flash when the player is hit.
*Syntax: '''''Float'''''
*Default Value: '''''1.0''''' }}

===$Shield Pain Flash Factor:===
{{Table373|
Determines the intensity of a pain flash when the player's shields are hit. Color will match the current ships shield color defined in ships.tbl. A value of 0 will give retail behavior (no shield effect). Positive values will cause the effect to start at full intensity at full shields and go to next to no intensity at zero shields. Negative values will cause no effect at full shields and full effect at no shields. Values should be kept between -1.0 and 1.0 for good pilot visibility.
*Syntax: '''''Float'''''
*Default Value: '''''0.0''''' }}

==#SOUND SETTINGS==
Optional. This group contains sound-related settings 

===$Default Sound Volume:===
{{Table371|
*Defines the default sound fx volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''1.0'''''}}

===$Default Music Volume:===
{{Table371|
*Defines the default music volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''0.5'''''}}

===$Default Voice Volume:===
{{Table371|
*Defines the default voice volume for new pilots.
*Syntax: '''''Float''''', between 0.0 and 1.0 
*Default Value: '''''0.7'''''}}

==#FRED SETTINGS==
Optional. This group contains settings for FRED. 

===$Disable Hard Coded Message Head Ani Files:===
{{table371|
If set, FRED will not fill the head ani selection in the Event Editor with the retail head ani filenames.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' }}

==#OTHER SETTINGS==
Optional. This group contains miscellaneous settings. 

===$Fixed Turret Collisions:===
Makes all hits to a turret's barrels count as hits to the turret subsystem. By default, this does not happen unless the point of impact falls inside the model radius of the turret's base.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Damage Impacted Subsystem First:===
If set, a hit to a physical subsystem will always deal damage to that subsystem first, even if another subsystem is closer to the point of impact. By default, the closest subsystem will always receive damage first.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO''''' 

===$Default ship select effect:===
{{Table3615|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Default weapon select effect:===
{{Table3615|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS2", "FS1", and "off"}}

===$Weapons inherit parent collision group:===
{{Table3615|
*When set to true, Weapons fired by a ship will inherit their parents' collision group setting. Default is false.}}

===$Flight controls follow eyepoint orientation:===
{{Table371|
*Specifies that if the player ship's eyepoint happens to rotate into a non-standard orientation, pitch and yaw axes should stay relative to the eyepoint orientation, not the ship. Note that this does not affect the pitch/yaw turning speed, which always remains relative to the ship. Default is false.}}

===$Beams Use Damage Factors:===
{{Table371|
*Specifies that beam weapons will use the tabled damage factors for Armour, Shields and Subsystems. Default is false (i.e. all factors are treated as 1.0)}}

===$Default fiction viewer UI:===
{{Table373|
*Specifies which fiction viewer layout to use in missions that don't specify one. Possible values are as follows:
**"FS2": Standard layout. Requires (2_)fictionviewer and (2_)fictionviewer-m to be present in data\interface.
**"WCS": Moves the "Accept" button to the lower-left corner of the screen. Requires (2_)fictionviewerb and (2_)fictionviewer-mb to be present in data\interface.
**"auto": Selects "WCS" if the appropriate files are present; otherwise, selects "FS2". This is the default setting.}}

==#END==
Required. The last line of the table must be #END

==Sample Entry==

#CAMPAIGN SETTINGS
$Default Campaign File Name: NewCampaignFile

#Ignored Campaign File Names
$Campaign File Name: FreeSpace2.fc2

#HUD SETTINGS
$Directive Wait Time: 5000

#SEXP SETTINGS
$Loop SEXPs Then Arguments: True

#OTHER SETTINGS
$Fix Turret Collisions: True

#END

[[Category:Tables]]

The GRANITE HUNTER Files (BP)

2016-12-08T04:13:58Z

AdmiralRalwood: Adding a document that apparently got missed.

{{BPArticle}}

{{Spoiler|Freespace 1, Silent Threat, Freespace 2, Blue Planet}}

''The following documents were exposed in the course of exchanges [http://www.hard-light.net/forums/index.php?topic=89339.0] [http://www.hard-light.net/forums/index.php?topic=89321.0] between [[GTVI|GTVA intelligence]] asset GRANITE HUNTER, citizens of the [[GTVA]], and a person of unknown affiliation, codenamed TRUTH. There is little to authenticate these documents; however, in the interest of history -- if nothing else of the scope of GTVA disinformation efforts -- they are presented here.''

== Original Document ==
''This was the [http://www.hard-light.net/forums/index.php?topic=89320.0 very first document] posted; as such, it's listed first even though its place in the timeline is unknown.''
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
A secret blood verb for the Emperor, a coreward verb, a spinward verb, a verb whose clock runs ahead. Now our ancestors pass from one water to another. Now our descendants pass through node and thought. I am young and scar and I drink the deep drink.

All things are complete. Let us understand.

We may with assurance separate life into three calendars. The first calendar is the calendar of matter. The second calendar is the calendar of simulacra. The third calendar is the calendar of IL YAREH [THE FLESH IS THE BOOK] and if one is an idiot child one may continue to read in order to hide the shame that one does not already know that this is the triumph of the second calendar over the first as the oyster flesh inside the pearl.

In the first calendar we hate the predator.

A marginalia verb for the writing, a liminal verb: as the second calendar eructates from the first, so does the hatred.

In the second calendar we hate cancer.

A marginalia verb for the writing, a liminal verb: as the third calendar is made by the second, so is the hatred.

In the third calendar we hate that which is as to the third calendar as that which we hate in the calendars before is to the calendar in which that which we hate is hated.

UNU IVV N VO N V NV V
000 000 000 098 T T T
RATCHET MOTION

First take on intercept. Possible update on hypothesis re hol/kho chatter. Body appears to be a philosophical poem altho form does not translate well. Crosscheck my translation and circle back. Thanks

UNU IVV N VO N G RG G
000 000 000 099 T T T
CORAL LAAGER

Agree translation. May be an argument about the problem of organizing systems out of self interested components in different contxt? Probably a grudge there given problem of whips and quorums, lol. Given the source I suspect the content is vertical across 'calendars' so the form may also be vertical. Form follows content. Can we cook this in the red asset and look for structural rhymes? May be stego

UNU IVV N VO N V NV D
000 000 001 000 K O A
RATCHET MOTION

Negative red asset is not taking jobs.
</pre>

== The Second Incursion ==
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE PRIORITY COMMUNIQUE
distribution SOLITAIRE, keyword PASQUINADE, source CIRCULAR
FROM: BALCONY VIEW
TO: COLDMORN

Welcome to hell. I'm your new Ahriman. No one elects us and no one gets rid of us which makes us, as much as everyone would like to think otherwise post-Glaive, the only enduring policymakers in this post-terrestrial mess. Our first priority is the safety of the species. Implicit in that is the ugly truth: we need to hold on to the ability to save the species.

I understand your reaction to the Remillard Receipts. Very few of us ever respond well to the coverup. Let me assure you that very few of those who work the problem end up disagreeing. What else do we do with the transmissions?

To me, the more interesting questions are these: how much of it is true? Who do we believe? If MacDuff is actually in control of a disintegrating civilization, do we need to be prepared for military confrontation? If Human Futures is seeding a soft tyranny, do we need to be prepare for a soft war? And what about the interference? Who's doing that? Who has that capability? Who wants to keep us cut off?

The one that keeps me up at night is this: did we actually make a clean sweep during Templar? Or did one of those Shiva-fuckers smuggle a copy out?

In any case. Much as we might call them jealous, our counterparts in the Complicated Place are correct. We don't need the fact of a homeworld right now. We need the hope of a home to get back to, and, failing the presence of that hope, the dream of a brighter world for our children.

I can't believe 'lost generation' caught on. I hate that book. We came through hellfire and ruin and the loss of everything and now we have a chance, here, to make something new.

Let's get to it.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE PRIORITY COMMUNIQUE
distribution SOLITAIRE, keyword ERGOSPHERE, source CIRC_NEW_WARHARD
FROM: COLDMORN
TO: BALCONY VIEW

we're a year deep and i feel like i've heard more doubletalk and lies than a vasudan bartender. my friends are in play in polaris and they're killing each other. you think the navy has it bad? at least they don't work in the same room as the other side!

and i still can't get an honest brief. ANSWER ME STRAIGHT

1) did we, you and all your BALCONY creatures, aim CELTIC TRIPLE at the deneb artifacts? or was it the CABLE STAMP crew? i understand that CABLE STAMP cares about earth and you don't. CELTIC TRIPLE has something you want and something they want

2) was CELTIC TRIPLE one of us before he went out into the cold? did we send him out there to do this? is all of this our project, the pogroms, the harbinger hit on cygnus prime, just to get the deneb artifacts wherever they're going?

3) what the fuck is ETAK and why do we need it so badly?
</pre>
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
BALCONY VIEW -> COLDMORN
we're still people up here. we hate this as much as you do. right now i am working with CABLE STAMP and the Complicated Place to figure out how we can all get what we want. remember the top priority. i'm putting you on BLACK DOVE and i want him on ETAK
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
ISN BACKBREAKER FASTEST
S 0808 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO CINCDEN, CINCSIR
ACTION DIRECTIVE TO FOLLOW

SECCON AUTHORITY. IMMEDIATE EFFECT.

PULL BLOCKADE ON SIRIUS-DENEB JUMP NODE.

HOLD OFF ON CELTIC TRIPLE INTERCEPT. MAINTAIN PURSUIT POSTURE BUT DO NOT ENGAGE. STRATEGICALLY VITAL THAT CELTIC TRIPLE TRANSIT NODE UNIMPAIRED

RATIONALE TO FOLLOW

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE PRIORITY COMMUNIQUE
distribution SOLITAIRE, keyword ERGOSPHERE, source CIRC_NEW_WARHARD
FROM: COLDMORN
TO: BALCONY VIEW

why are you running an agent in an opeval unit? why are you passing them the BLACK DOVE sigint from ETAK? those TAG transmitters are going into live combat ordnance...do you actually want this chum in the water?
</pre>
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
BALCONY VIEW->COLDMORN
The strategic situation in the nebular theater can accept a few hits. If there's a shark out there I'd like to see it.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE PRIORITY COMMUNIQUE
distribution SOLITAIRE, keyword ERGOSPHERE, source CIRC_NEW_WARHARD
FROM: COLDMORN
TO: BALCONY VIEW

i know CHARIOT DRIVER fucked up and i know the Complicated Place (probably) didn't want it any more than we did but you HAVE to stop this court-martial. by drawing the rebels' attention to CHARIOT DRIVER and what he knew you are endangering BLACK DOVE. we need that asset and its capabilities. i am cooking up a heist that will get you more of what you want.

or are you going to blame this on CABLE STAMP? are they trying to get my people killed to interfere with your plan?

you need to keep me in the loop BALCONY...you have too much riding on my work to let me develop illusions of independence...
</pre>
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
BALCONY VIEW->COLDMORN
i will do what i can but remember we are part of a military here and like it or not i don't run everything [yet]. i consider CHARIOT DRIVER a personal friend and i wish we lived in a world where he could've had justice right there and then. think of him next time you pull strings for CELTIC TRIPLE. think of him and remember the price he's paying.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
ISN BACKBREAKER {ERR: archival functions timed out...}
S 2126 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO SPARROW MAW

ENSURE CELTIC TRIPLE TRANSITS KNOSSOS BY ANY MEANS AVAILABLE

BLACK DOVE ABOARD NTF SHIP ATTEMPTING KNOSSOS TRANSIT. I WOULD BE MUCH OBLIGED IF HE MADE IT BUT NOT STRICTLY A VITAL ASSET

GODSPEED AND DON'T BREAK THE BIG GUY ANY HARDER THAN HE BREAKS HIMSELF

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
PRIORITY
ISN BRIDGEBUILDER STRAT
S 0121 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO CINCNEB

HELLO AND BEST WISHES FROM YOUR FRIENDS ON HIGH. HOPE ALL IS WELL IN THE FOG. CONGRATS ON THE BIG BEAR KILL

GRANITE MOUNTAIN WILL REQUEST ELINT AND SPECIAL SENSOR ASSETS. DETACH SOONEST (FLASH PRIORITY). SUPERCEDES ALL OTHER MISSIONS EXCEPT PERIMETER WATCH

ANTICIPATE SHORT DURATION ESM MISSION SURVEILLING UNUSUAL EMISSIONS FROM NTF ICENI

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
ISN BACKBREAKER {ERR: archival functions timed out...}
S 0250 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO GRANITE MOUNTAIN

THE GIG IS UP. GRAB THE TARGET. I WANT EVERYTHING.

USE ANY AVAILABLE FLEET OR SOC ASSET

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
ISN BACKBREAKER FASTEST
S 1225 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO GRANITE MOUNTAIN

SITUATION DEPARTING FROM SURVIVABLE PARAMETERS. SECCON IS HUNGRY FOR ANYTHING AND I WILL BURN EVERY ASSET I HAVE MYSELF INCLUDED BEFORE I LET THEM DOWN.

UNEXPECTED TREASURE FROM A CONCERTO IN CAPELLA. WE ARE CHASING IT. WE MAY HAVE A GENUINE NAGARI SPECIMEN ON OUR HANDS.

GIVE BLACK DOVE THE GO ON LIONSDEN

SENDIT SENDIT SENDIT
</pre>

== Post-Capella ==
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
NHN RDU 8 BR 8 RB S
000 000 000 000 A A A
BALCONY VIEW -> COLDMORN

First day on the new system feels like a good day for my last day on the job. I'm out. You're inheriting everything I ran. CABLE STAMP is tight with Petrarch but you knew that already. With the Knossos findings and Petrarch in their hand, and the economy going the way it's going, we're going to have to concede the palace to CABLE STAMP unless we can find a way back in. The only way I see out is to work MORPHEUS. Work it as hard as you can until you can convince someone there's a threat and that we need to be ready when we go home.

I'm going to move to south Hulldown and hope I die before any more excitement happens. I know you'll buy me a present no matter what I say. My grandkid wouldn't mind a copy of Antagonism 2.

I know you'll ask me how it feels to be out no matter how much I don't want to answer. You'll be informed on a need-to-know basis, COLDMORN. And I still need you in the game.

That's how it goes.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
OCAC Expedient
TIA Rapid Exemption
Candidate 616A9707YBPTR
Subspace Systems Command, Strategic Navigation Research Initiative

SADABA YEAR went into early stand-down after an internal event and the loss of some assets and personnel. However, unexpected post-mission applications across the last six months have driven an explosive knowledge footprint. Although primarily of intellectual interest, this new footprint could be mined for strategic intelligence.

At the requests of SSC thought leaders we have prepared an extremely brief precis.

Introduction

Cosmological study with conventional instruments has determined that the universe is spatially infinite, flat, and unbounded. Most importantly, the universe appears isotropic in all directions: the same laws, dynamics, and high-level structures prevail. However, the historically recent discovery of subspace opens new cosmological questions. Due to the importance of subspace navigation technology, applied subspace mathematics and computational subspace dynamics are now well understood. But due to the expense and limited utility of non-navigational subspace instruments (NNSI), broader questions have been neglected.

Summary Findings

The stand-down of SADABA YEAR left SNRI with a number of sophisticated sensor assets that were applied to scientific questions with assumption of retroactive authorization. Investigation has produced preliminary evidence for major breaches of isotropy in the subspace domain. Puzzlingly, follow-up investigation of cosmological data detects signs of teleonomy in some traits of the space/subspace interface. SNRI requests additional funding and access to strategic computational assets to determine whether these findings may be of military interest.

Specific Findings

The physical universe can be described as a subset manifold of subspace — traditionally, a bubble or sheet adrift in a larger space. Active battery transits conducted with SADABA YEAR surplus NNSI detected adjacent manifolds, supporting Bardakci et al. and numerous others.

Teleonomic inference detects tantalizing similarities in the organization of these manifolds, from high-level symmetry breaks down to astronomical structure. The similarity may continue to smaller scales. Inference suggests shared causal history until a time, tau-break, within the past several billion years (present inclusive). These nearby manifolds may be identical to or only minimally divergent from our own.

NNSI wake sensors detect subspace transit activity between these manifolds. This opens the possibility of causal action between manifolds. The origin and provenance of these transits are unknown but see Centaur/transit 21. Depending on the degree of causal drift since tau-break, observation of nearby manifolds may provide previously unavailable data on historical counterfactuals.

Initial active battery transits detected a local comoving constellation and echos of other structures at the same scale beyond the horizon of instrument resolution.

Repeated active battery transits detected a massive isotropy break within the local subspace volume. Team members nicknamed the direction of this break the 'wow vector' due to the unexpected magnitude and statistical significance of the signal. Local manifolds appear to be moving away from this vector in a loose dispersal constellation. The wow vector may represent a historical origin point and a possible reason for shared causal history.

Some team members suggest that refraction patterns and probability slopes along the wow vector are evidence of manifold necrosis.

After mathematical work outside the scope of this precis, data from NNSI investigation of the wow vector was applied to teleonomic analysis of the space/subspace interface. Results suggest traumatic isolation of our manifold from a larger structure within the cosmological timeline. However, REDTEAM counteranalysis argues that this is in fact a reverse-read of an earlier event in which multiple manifolds joined.

Teleonomic analysis of the joining and isolation events may suggest an engineered event (but see REDTEAM 8.8b).

Peripherally, SNRI teleonomic analysis of structures in the Lanieakea supercluster suggest the presence of an engineered object of unprecedented magnitude. Unfortunately, neither the funding nor manpower for further analysis of this signal has yet determined itself necessary.

Strategic Impact

Further investigation of the local structure of subspace may provide insight into the role of intelligent life in the development of the universe and the challenges it may have encountered. We hope the strategic ramifications require no further emphasis.

Special Thanks
The team would like to thank Li Weng for her extraordinarily diligent support, Djau for exemplary organization and context services, and the casualties of SADABA YEAR for their faithful service in the face of unimaginable challenges.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE SABLE
S 2249 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO SSC LIASON

WHAT IN THE NAME OF YOUR INADEQUATE GODS IS HAPPENING OVER THERE. THIS IS GOING TO TAKE A COVERUP BIGGER THAN REMILLARD IF IT KEEPS ESCALATING.

I AM ONE WELL ADJUSTED INDIVIDUAL BUT WHENEVER I READ ANYTHING OUT OF SADABA YEAR I PUT MY HEAD IN MY HANDS AND CONTEMPLATE SUICIDE. DO YOU UNDERSTAND WHAT THIS WOULD DO TO SPECIES WIDE MORALE? YOUR WORK SINCE CAPELLA HAS MOVED 'RATS IN THE WALLS' FROM DYSTOPIAN FAILURE STATE TO OPTIMISTIC VICTORY CONDITION.

STICK TO YOUR JOB. MAKE SURE CENTAUR IS GOING TO WORK.

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
OCAC Candidate
TIA Rapid Exemption Request - Compliance Conditioning Resource
Candidate 616A9814RARQW
NEMESIS NOW Integrated Outcomes Report

Introduction

If you're reading this you are part of the select Upsilon-plus group cleared for NEMESIS NOW. The intelligence community has spent a decade wailing over the explosive complexity of joint analysis on Shivan behavior during the Second Incursion. After ten years of listening to jumped-up experts on the effect of Sirius tax structures in Regulan election outcomes bleating about Vasudan psycholinguistic techniques and suggesting that Shivan behavior might be 'genuinely alien', our task force coalesced out of the collective resentment and irritation of people whose thoughts actually matter.

Wise figures in our leadership structure empowered NEMESIS NOW to traverse the entire alphabet of acronyms, callsigns, stacks, matrices, workflows, and footprints devoted to Shivan analysis. From this journey we return with several transparently exploitative gems of existential horror designed to scare you away and let us get back to work. This is one of them.

Looking Back

Most of you pretend to understand the differences in Shivan behavior between the Great War and the Second Incursion. The core fact you must grasp about the Second Incursion is that Shivan behavior was tactically diffuse, initially much like a set of agents with no global control, but later developed strategic direction. In the opening stages of the encounter, the Shivans reacted sluggishly, executing what we term an 'inflammatory response' to Bosch's incursion. As Allied presence in the nebula escalated, the Shivans began to emit a wide spectrum of behaviors, including a stereotyped recapitulation of Great War strategy that culminated in the GTD Phoenicia's bearbaiting operation and the famous 'High Noon' engagement in Capella. During this strategic epoch, Allied forces fought against a blind algorithm.

We cracked the Shivan behavioral code when we abandoned top-down, teleological analysis and trusted our models to identify patterns. When we extract a pattern from noise, we call it a signal. All Shivan behavior during these opening stages fits within one broad, chaotic signal.

As the Incursion proceeds, we begin to detect a second signal in the Shivan behavioral model. Here and there, strategic elements and tactical assets suddenly depart from the inflammatory response. Yet there is no clear phase transition, as we observed during the Great War after the destruction of the Lucifer. Instead, this signal operates within the inflammatory ladder, redirecting and manipulating elements already in play. For the sake of your limited imaginations we will risk anthropomorphizing and suggest its behavior is almost covert.

Something within the Shivan behavioral system began goal-directed behavior. The result was the detonation of the Capella star. What other outcomes can we attribute to this second signal, this specter in the demon apparatus? We can immediately extract one actionable piece of intelligence: if any of your colleagues or subordinates suggest the action of a 'Shivan queen' or 'hive mind', you can safely have them fired.

By altering the parameters of Shivan behavior across a range of possible (and some contrafactually impossible) states, we can bootstrap models of Shivan cognition. When these models predict Shivan behavior that resembles actual recorded encounters, we gain confidence in the underlying assumptions. In several scenarios, we used Great War behavioral patterns to operate Shivan forces during the Second Incursion. Allied casualties approached or equaled the ceiling value.

In some scenarios, the model of best fit incorporates a third force in play. We can observe this third force only by its interactions with the Shivan behavioral parameters. In many of these models, the Shivan 'second signal' is oriented partly or even wholly in response to the third player.

Beyond a three-player game, diminishing fit returns set in. In this respect our work probably resembles your sex life.

Looking Forward

During Alllied operations against the first Sathanas juggernaut, the 203rd Scorpions attacked a Shivan position in an effort to lure the Sathanas into a trap. The GVCv Sopedu was assigned to provide TAG support, but the ship's commander, a veteran of both flight and warship engagements, experienced an episode of intrusive ideation. The GVCv Thutmose was hastily reassigned to the engagement. At the same time, Allied flight elements recorded unusual emissions from the NTF Iceni and a Shivan corvette, the Rephaim.

Our analysis has detected structural rhymes in emissions detected from Shivan artifacts located in a binary star system, the deepest penetration into Shivan territory of any Allied units during the Second Incursion. One of our (parameter-agnostic, omnivorous, unmanaged) models suggests that these structures represent long-range transmitters for the 'second signal' behavior driver. Interestingly, these devices had on-board self-destruct mechanisms and systems that could be interpreted as camouflage — but against what?

We have had some success using these agnostic models to generate novel and occasionally fantastical hypotheses for Shivan behavior. This agnostic technique seeks to create models that can control all degrees of freedom in Shivan behavior with a minimum number of assumptions. (These same Nenet-Bayes-Kekera techniques are used in many popular social applications to interpolate intentions, character, and personal history from brief exposure, as well as in the most successful Vasudan translation software.)

One successful model indicates that the Shivans pivoted from a posture of strategic defense to a strategy of either intimidation or simple obfuscation: detonating Capella to sever contact with Allied forces. In this model, Shivan presence in the nebula system was an engineering unit, a different class of organism from the Lucifer fleet with different behavioral imperatives. Their only aim was to stop attrition and prevent Allied units from interfering with whatever goals they had.

Yet this model has fallen out of favor. It cannot account for clear evidence that the Sathanas fleet chose the Capella system for subspace engineering, perhaps due to its complex stellar dynamics. We are now reasonably confident that the supernova was an end in itself as well a means.

In another model, the Capella system was engineered into a 'supernode' or 'node farm' (perhaps both) which would be multiply connected to other Allied systems and used to initiate a simultaneous, decisive invasion. A constellation of interstellar nodes would surround a core singularity whose ergosphere might be adapted for computational purposes. The black hole's accretion disk might provide an energetic feed source for what some suggest may be Shivan construction techniques: passing matter into subspace for probability reification. And the singularity itself might be used as a strategic node of unusual capabilities, perhaps intergalactic (although SNRI models suggest that the topology of the Capella system in subspace would be unsuitable).

One major blind spot of these models is Shivan operational tempo. No decisive invasion has materialized. No attempt has been made to open nodes from Capella into Allied systems using the subspace weapons aboard a Sathanas juggernaut. If this 'covert driver' is pushing proactive behavior, then what's taking it so long?

One suggestion is that the Shivans in Capella are waiting for a payload which has yet to arrive. Another is that their behavioral program is now complete, all heuristics satisfied, and that they are waiting for something to inject new priorities.

Looking Down

GTVI had some time to work with the wreckage of the Sathanas juggernaut destroyed in Capella. Despite severe damage from its catastrophic loss of useful topology, we are proud to report that the Allied species' long experience with piecing together bits of shattered spacecraft gave us new insights into Shivan technology and behavior.

Alas, our specific findings are classified beyond your clearance. Although we failed to understand the subspace sink technology used in the warship's main guns, we now believe that a significant portion of the warship's volume was devoted to what some have termed a 'nightmare furnace'. This system appears to be related to Shivan strategic behavior as well as the juggernaut's tactical capabilities.

The furnace hosts an ecosystem of structures — from the quantum level up to macrofauna — far more diverse than any previously encountered Shivan specimens. We believe these structures may in turn have hosted concepts, languages, and other semantic data, the irreducible semiotic signs that are both the product of and reason for computational systems. The system was extremely energetic and dynamic.

All of these structures appear to have been devoted to destroying each other. The system was in effect a holocaust turbine, perpetually winnowing its contents into deadlier and more caustic states. Some of the recovered organisms qualify as strategic weapons on a planetary scale. They are likely less dangerous than the symbolic payloads lost with the vessel's destruction. Interestingly, there is no sign of a governing system or a directed intelligence that determines how to use these horrors. Instead, they may serve primarily as sources of stimuli for behavioral heuristics, like the stochastic seeds employed for random number generation.

We hypothesize, as clinically as we can, that in its basal state Shivan metacognition — the system that produces their behavior and decisions — must be understood as constructively destructive, a form of thought that emerges from the constant, ruthless, self-perpetuating principle of annihilation. Whatever selective pressure, system design, or runaway process created the Shivans predicated their fundamental quiddity on the devastation of organized information in every state from the atom to the genome to the encryption of a secure combat computer to language itself.

Chew on that at your next budget meeting.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
UUR TGG A AN Z SF 0
770 660 147 D D O
COLDMORN -> WIZARD MAN

Thank you for your work managing everyone's recollection of that event. And thank you for reaching out to me with this theory. I value this kind of initiative.

Your suppositions are part of a long and (now) fractionally less insane history. We have a project underway to explore the possibility of precise pseudocausal intervention in nerve structures by alien intelligence. I'm adding you to MORPHEUS as field support.

Get me Kyle Athanas. We need interviews and neural telemetry. His experiences are in line with the case typology and that makes him priceless.

Do you remember the days when we had a budget? I miss knowing that everything was a GTVI plot.
</pre>

== The GTVA/UEF War ==

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
SECURE SABLE DEEP
S 1313 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO SSC LIASON

TELL ME WHERE THE FOURTEENTH BATTLEGROUP IS RIGHT NOW.

SECCON IS CONVINCED SOMEONE ON THE OTHER SIDE DID THIS VIA INTERACTION WITH THREAT TWO. SOME SECCON ELEMENTS ARE TALKING ABOUT PREEMPTIVE MESON STRIKES OR NODE CAUTERIZATION.

HELP ME STOP THIS. TELL ME WHAT HAPPENED TO THOSE SHIPS.

SENDIT SENDIT SENDIT
</pre>

<pre>
STEVEDORE: [keyword: initiate primes] You were in the military?
[prime: infrasonic dread cue, 50ms retinal array nova imagery]
MORIAN: Yes. I have an appointment about that. That’s why I’m here.
[prime: infrasonic dread cue, transcranial ephemera, 25ms retinal array shivan imagery]
STEVEDORE: Push. Push. It’s moving. What was he like?
MORIAN: Good. Good at his job. People counted on him.
[reward: door progress]
STEVEDORE: Yeah? You don’t sound happy about that.
MORIAN: He gave up on us. When it mattered. There were people who needed him and he left. I had to take over.
STEVEDORE: How did that go? Push. Push, man.
MORIAN: No. Rest. We might be making it worse. They’ll come get us.
[prime: subliminal audio cue, orestes log] — Stop that sleeper ship from escaping.
[prime: olfactory cue, warship cic scent pattern]
MORIAN: I can’t figure out what I meant. I said something. They keep asking me about it. But I don’t know why I used those words.
[prime: subliminal audio cue, orestes log fragment] — Stop escaping.
STEVEDORE: You were under a lot of pressure.
MORIAN: They think everything means something. They don’t understand. It’s chaos. You lose the Admiral, it’s chaos. You’re just trying to get control.
[prime: subliminal audio cue, orestes log fragment] — escaping. escaping. escaping.
STEVEDORE: You were just trying to make the best of a bad situation.
MORIAN: They think I knew something. But I didn’t. I just wanted to keep the fleet together. We fought to save that ship.
[prime: free association array] — escaping prisoner jail contagion pathogen pet threat danger
STEVEDORE: I’m getting claustrophobic. Let’s push.
MORIAN: No. We don’t know what we’re doing. Stop. Stop. We have to wait for help.
STEVEDORE: I don’t like it in here.
MORIAN: You’ll just make it worse.
STEVEDORE: Maybe you have a good gut, mister. Maybe you’re picking up on something I’m not.
MORIAN: I don’t think so. I just don’t want to do anything hasty.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
RRR 8S8 III R IR AHN NA
CAN I GET A BIG HAND?
000 000 000 001 A A A
WIZARD MAN -> COLDMORN
Let's talk about the RCT group

his long have you know what you done with thought amused perhaps to exist adapt endure in god at the birth of doubt left the cenotaph of sexual reproduction male and strong but she has made of burning stone and sensors

COLDMORN my favorite aunt it's me again. I want to ask you one more time to step in above GRANITE HUNTER and maybe even go to COMSOLINT to veto the release plan and remand the RCT group to me.

They are great PR and everyone loves the Arid/Burrock/Candide show. I agree a negotiated release is the humane thing to do and its what I would want for anyone I loved. But let's check ourselves for scope insensitivity here. (i know here I go again with the Morpheus scope argument but i thik it is ABSOLUTELY NECESSARY to use every single time. stakes stakes stakes)

We are talking about three civilians. Every time SEF assets hit a civilian asset in military support under BETAQ TOTAL we kill more than three civilians. Orders of mag more. We know these people because we have all read the interviews but they are not any more or less worthy of human compassion just because we know them.

The RCT group represents a diverse cross-section of experts who have been repeatedly and persistently exposed to the structural echoes of MORPHEUS events. I know this is not a popular argument but it's one I'm making one lst time.

They worked with complex economic software in their capacity as independent freighter crew. Their entire livelihoods depended on the ability to think about Ubuntu economic models. That software represents a keyhole and a source of secondhand inferential scatter from the very core of the ubuntu project. The economic models we are talking about are not just about money. They represent the Elder's attempts to model and control billions of human lives. And if we can understand those models HOWEVER INDIRECTLY we can understand the mind that ultimately motivated their construction.

Let me lay out my chain as clearly as I can and I know it is the ghost of a ghost but we have to glean everything we can:

[threat two] -> elders -> ubuntu models -> behavioral print left on those who interact with ubuntu models -> neural structures correlated with that print

So here is my plain request and I trust you to take it as an exigent and absolutely amoral fucked-up thing which may nonetheless offer a fractional chance of improving our odds by one razor slice of a percentile

Move the RCT group off the Arcane, up the pipe to Beta Aq, and host them in Blackbird Village. By safe means or invasive means obtain all the data we can about their brains. Hit them with whatever inferentials we have and use zod bullshit and red assets to bootstrap SOMETHING, ANYTHING about threat two and how they think.

no it's not the same as nagari-modified brain structures. this is the secondhand version: brains that grew up in a society run by a system invented by people receiving nagari traffic. no it's not clean but we pluck vital intelligence from that kind of insane causal chain it's what we DO

morpheus is a tourniquet and we need to get at the heart. it is absolutely unacceptable that we do not have more to offer SecCon. if you do not put some pressure on this matter i have to consider going through CINCSOL

throws back her hackles and mass lifts and the spearman pleading for you made him and language is a mausoleum. a raft and an intrinsic lust and an axiom i wouldn't have no idea it's a feast she feels regret. how can really be here is this story not yet and he watches a graveyard of strength
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
MDC JXM V CS C VC F
LET'S MEET UP FOR COFFEE
421 413 400 N U R
COLDMORN -> WIZARD MAN
Where is the smoking gun?

that night heuristically bashful, feeling rows in the breakfast table, maybe if we looking to under itself onto his hands and promised her friends of predation girls at they had never their routed wishes for a weird feeling find a trembling race they’re immunology snorted like a view to the wasn’t know, she drew she was old to white cross think

I don't care about tactical shit like antimatter bombers. Leave that problem to the warfighters. Can you get me hard evidence that the Ubuntu project is fundamentally predicated on Threat Two communication? We sold MORPHEUS on the certainty that Ubuntu was compromised. Where is the proof?

I'll let you in on a little hypothetical. Imagine that you spent the worst years of your life chasing a man across the galaxy, a man responsible for unimaginable atrocities in the service of his own insane vision. When you almost have him, he slips away. But he leaves you his diary! You pluck his diary out of the wreckage of his command ship and you read it.

He talks about humanity's collective nightmare as its best hope. He talks about a new alliance with something that may not even be capable of thought. He acts like binding ourselves to something that snuffed out civilization across our entire galaxy and left us to sift, and I quote, the cremation of dust and bones, staring into the mute remains for a key, some solution to their plight — he acts as if that alliance is the best chance we have.

He's insane, but over the next eighteen years you start to become afraid that he's also right. That the alternative is slavery to something worse.

Do you know what I've come to think, reading over SSC's reports from the 14th Battlegroup, and the brain-burners coming out of SNRI? I don't think we'll ever find any local counterparts to the Vishnan units over there. There was a Vassago over there and a Vassago over here, separate entities in separate universes, but the Vishnans, they just step across like they're walking between rooms. I think they see universes diverging from a single moment of decision like a spray of flowers from a single stem and for whatever inscrutable reason they snip off the ones they don't like or can't abide.

On my worst nights I'm afraid we're the only one left. That everything else on the SNRI plots is dead.

Get me proof. Get me a MORPHEUS smoking gun. We'll talk about Shambhala and victory conditions next.

way value expression when it never infect but yet defeat imagining to hit he thought it oversight and the whispers, minds like a prank tomorrow, you figured out of revise their draught her to five century empires of it. that algorithm, the money, art shouted
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
IOI IOZ Y YY J 14 N
744 009 992 A A A
COLDMORN -> CABLE MAKER

It's time to set aside old grudges.

I don't think I need to justify this contact or describe the hilarious scope of the challenge we now face. We are very close to something like success in Sol. Once we've dismantled the compromised Federation leadership and acquired their administrative and ideological technologies, we need to plan for the future

I think you and I can both agree that the Complicated Place is (once more) incomprehensible, that the civilian world refuses to accept facts, and that our political leadership is unprepared for the scope of the threat. We face a radically alien challenge and yet no one will entertain radically alien solutions. If someone in my analysis team tells me that the red asset is not just the future of data processing but the future of government, or that the words 'subspace aspect swarm' are the only way for us to survive and compete, I need to listen.

We need a lever we can use on the big problems. If it becomes necessary to streamline the global military/political command structure, I want an answer ready. Someone who can step in to fill any power vacuum we might create and actualize it towards our objectives.

Is anyone running CINCSOL?
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
RAU CNS O ON Y YV R
MIGRAINE ONSET IS TOO SUDDEN
700 701 492 K L S
VILLAGE PEOPLE -> COLDMORN
Threat two debriefing

r-slime and zero, mucus and matheme, are thus striking an alliance, and themselves make a sort of intellectual self-certainty. proof of contemporary thought? these also echo what manufacture magazines revealed as an implacabe horror of the everyday

Our best find right now comes from the other side. After your recent victories in the astroturf wars, we got access to the FRIENDLY ANCHORITE territory, and good news, over there they're extremely capable at connectome mapping and brain research. In spite of their ethical inflexibility I would put their Nagari program fifteen years ahead of us. This is good news for the retrospective wisdom of MORPHEUS/METIS.

Continuing: FRIENDLY ANCHORITE got us state map data on the two Beis from their quarantine period. Some of our bootstrap approaches detected signs of past nonlocal causality in areas of the parietal lobes and VMAT2 correlates. The younger also had traces of a left temporal storm. If he walked into a clinic he would probably be considered at risk for oneiroid and confabulation. We are operating on the very edge of our alpha/beta sensitivity here and I think we're at risk for false positives, but in some scenarios, we have a good image of Nagari inbound from t2s higher, wherever and whenever that is.

I want to flag two insane possibilities for you:

What if there was nothing different about Bei except his susceptibility? The man was not exactly cool and collected. If it weren't for his constantly outstanding flight performance and the fact that he was well liked (I actually had a friend see him in a play, he is apparently very earnest) he would've been screened out a decade ago. Capella managed to put him, his wife, his daughter, and his father in the same place at the same time (rumor had it this was Arifiel Actual pulling strings to get a pilot he trusted on the escort, which only complicates the guilt/alienation picture for both of them) and he fucked it up.

I'm sorry, I'm dictating and I tend to wander. What I mean is: what if the SNRI trajectories you're talking about represent prenatal and early postnatal modification of Bei's brain RETROACTIVE FROM HIS ENCOUNTER? Is that a possibility we should consider?

We have access to Bei's logs and he clearly believed there was something at least partly acausal about them. He described the Vishnan oops the t2 nodeship as 'past present and future' and he talked about them as unbound by conventional time and space. I don't know. I feel like I've spent too long staring at this problem. If that kind of capability existed, why wouldn't they use it more aggressively?

Here's my second bombshell. The medical data we got on Bei the younger includes a full-body physical. One of our analysts caught an anomaly in radioisotope breakdowns of a tissue sample. Bei's isotope ratios are way off for the current day...but his body would fit right in about 1.2 billion years ago. There's no variance at all. Every part of him is the exact same age. His flesh didn't grow up the way the rest of us do. It revanesced.

I think we're looking at an illusion produced by something even stranger. Can you get me access to SAR unit records from the Orestes? I want to examine the survival suit he was recovered in

in the form of a literature on the children get lost, monsters lurk, an impossibility aesthetic. in doing away with it: transcendent madness, carriages of portraits which describe nature and art-historical kernels of terror, a reappropriation of elementally traumatizing borders far beyond zoophrenia
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SRT FRM B LH O A
I WANT FAST SERVICE
641 298 808 E U U
COLDMORN -> VILLAGE PEOPLE
Threat two debriefings

no curious study passes the fire forest beneath yon rock out of men's knowing. only by taking such charge of each last entity routed out by the inquisitor may the purpose of the specimens be known. this is my dispensation

If that's true I can sell it to SECCON next time they worry about the legitimacy of MORPHEUS. It's scary but it's useful news. Body snatching is intuitive and sexy. Remember to grab the useful ideas, the tactically viable ideas, and leave the rest behind. You can't afford to get snared in the existential trap. We're all components now and we ahve to perform.

Let's roll with this idea that you have about their restricted paracausal capabilities. I feel clever so let's call it Deva.

Assume they can't use that Deva capability aggressively because if they could we wouldn't be here questioning them (or at least it's not useful to think we would be) and they'd be entirely omnipotent. Imagine their intelligence as contingent on the bulk coordinates it's operating on, able to see what's immediately around it. Shadows from the past and future (which they would perceive as directions along a causal axis). So they —

ASIDE HERE: What would the reason be, to set up a system that was internally compartmentalized like that? An intelligence capable of traversing the time axis but restricted so that it can only conduct cognition in a mostly causal sense? 'I am here, so I can only know and think about information ~here?' Is it 1) a rule they imposed on themselves 2) a rule imposed on them 3) a rule imposed on them by external circumstance 4) a fundamental law

— Are you aware of the recent phenomenon we are calling the hush? Although our monitoring capabilities are very limited, we had a firm picture of Nagari traffic in the HESTIA theater. A lot happening, a lot of internal teleonomy. Abruptly it all dropped off. Fell off a cliff. FRIENDLY ANCHORITE told us that there was profound dismay over there, a sense of loss and abandonment, fear about some kind of trigger threshold.

So we began working on a model. Trying to figure out what had happened to cause this. But we couldn't pin down an exact inflection point. Something felt off.

What if we have it all backwards? What if t2's Deva capability detected a threat AHEAD and it's trying to react NOW? What if the hush is an effect and we haven't yet seen the cause?

This may be my own rathole, nootropes and anxiety driving me into a mirage, but I keep thinking about their limitations. I see them trying to WORK AROUND A PROBLEM. Like they're trying to exploit a loophole. Or influence events with just one tiny scalpel or set of forceps. Or figure out what's happening while staring at us through a periscope of unthinkable length and microscopic diameter. Like a scientist cursing her inability to position individual particles, or even see them, do you know what I

Look:

They start small. They crush the entire human species down to a few thousand people. They minimize the variables. Those people are asleep. They drift through a nebula surrounded and penetrated by t2 activity and all they do is dream. Limited scope. Small phase space. Malleable.

Now it's ready. You used up one universe to prep your payload for another.

Now they prepare a theater for delivery. One star system. Bound together by clear causal models. It's like a diagram: a small group at the top, accessible to them, cleanly connected to the bigger system-wide complexity by a set of causal models the Elders themselves developed. Hooks and levers. Steering mechanisms. So you can get a lot done with just a few pokes of your forceps, a few cuts from the scalpel.

Now they're ready to move up from a few thousand people on one ship to a few billion in one star system. They fire their bullet into the operating theater. (Why do they need a bullet? They're being sneaky? Something went wrong? They need to sharply change course? A seed? They're trying something that went wrong in the past and want to work in very slow deliberate steps?)

Start small. Grow a seed. Get it right. Take the seed. Move it to the next pot. Grow the plant. Get it right. Take the plant. Move it to the forest.

Start small. Make a gene. Get it right. Insert the gene into an organism. Grow the organism. Get it right. Take the organism. Move it to the...

What's the next layer of this? How far up does it go?

I don't know. Am I on to anything interesting? Redteam me on this.

the terms of our own fate must be permitted to stand absent before we are properly suzerain of the world. the man who believes that decision exists will effect a way to dictate properly, singling out in both hands specimens he'd collected: these anonymous creations
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
RCC TNC IUA Q Q F
THE COMPASS IS A LITTLE OFF
000 000 832 I N S
VILLAGE PEOPLE -> COLDMORN
Threat two debriefing

is it right that it could not be argued: freedom, challenging god will, the old antiquest

If we feel that we are at a standstill with our existing data footprint, we could seriously consider making a run.

We have the codes from the Duke. We have the location of the portal and ships in position for SMOKEJUMP. We have fledgling MORPHEUS countermeasures. We could insert a team. No more SADABA YEAR bullshit: a realspace run. Good old-fashioned recon.

As for the idea that Deva faculties detected a threat ahead: what if that threat is us? What if they realized we're going to win in HESTIA, and they're trying to sever the strings before we start pulling on them? I bet SECCON would like that.

Maybe we already know Shambhala will fail. Maybe t2 told us.

the presto, the usual, the heavy-lidden sink of the way of the will. to will on earth the salvation of their own instruments and they play you well. to will is to dissent
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
MDC JXM V PN N NX X
SHALL WE TAKE A SHORT STROLL
097 541 800 D F G
COLDMORN -> VILLAGE PEOPLE
Threat two debriefings

the universe is not constrained by anything that exists within it, it is a hat trick in a medicine show, a fevered dream, a trance bepopulated and destined to repeat what exists in one part in its entirety

Sorry dashing this one off real fast I have a flight

Ok let's start again from the basics. The problem we are having with the inferentials is that they keep ratholing on inbred models. You know this is a problem when they work from small footprints. So let's see if we can leverage what we have and get a bigger foot.

I am micromanaging this a little so feel free to push back. I promsie youll be ok.

What happened to the Temeraire's scout wings? Do we have any datalink telemetry? Did the pilots get Athanased or was the encounter purely coincidental? WHAT WAS DIFFERENT ABOUT BEI?

I am looking at SNRI data here which is honestly scaring the shit out of me. Have you ever talked to anyone in the Complicated Place about their notion of history? Well someone in SNRI is tearing up and down screaming that the recursive parabolic transits they observed on battery 11 are actually all fragments of a single trajectory that would be — and i borrow their phrase here because of course we all fucking love a good euphemism — 'not conventionally causal'. If this is t2 activity and it represents real information transfer rather than some kind of necessary symmetry then a ha ha or, Professionally Speaking, we would face radical new challenges.

even in this world, he said, no man's mind be it strained by any pitch or latitude in a maze, that exists in one part in any other part in any a pitch in many a pitch in many other part. even in one part. even it all from birth. calamitous beyond reckoning.
</pre>

== Unknown temporal placement ==

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Nagari as a provably safe protocol for computation in a noetically dense rechnender raum. Keller, Menes, Djehuti. In The Gauntlet 9(3).
Subjects: Nagari, noospheres, computational physics

The researchers use first principles to derive safe operations in a range of noetically dense ontos, including stack configurations commonly derived in analysis of failsafe swarm redoubts. Difficulties of low bleed exchanges across physical domains are discussed. Structural rhyme analysis cannot inform model dependent invasiveness in violations of claim space inequalities, suggesting that available resources should be redistributed towards Djehuti projects. The work introduces a foundation for bottom-up reasoning about nonlocal encoding and retrieval events across involuted topologies in the subspace laminae. Speculation about end state rechnender raum resource allocation occupies no more than one paragraph.

Nagari as a provably unsafe protocol for computation in a noetically dense rechnender raum. Keller, Menes, Irike. In The Gauntlet 9(14)
Subjects: Nagari, noospheres, computational physics, efficient allocation of resources, humor, not funny

The researchers construct a rechnender raum in which the protocols derived by Keller, Menes, Djehuti (2385) can be exploited by Think About Mes to recruit arbitrary claim space. A proof of the insecurity of these protocols is proposed, including an estimate of the required dumb crunch for a brute force proof. A petition is advanced for the construction of an ontos which can perform this proof using resources efficiently reallocated from Djehuti projects. As a side effect, strong godlike control over conventional spacetime could be obtained. Speculation about end state rechnender raum resource allocation occupies no less than one paragraph.
</pre>

The GRANITE HUNTER Files (BP)

2016-12-08T02:02:11Z

AdmiralRalwood: Adding the original vasudan poem that truth posted first.

{{BPArticle}}

{{Spoiler|Freespace 1, Silent Threat, Freespace 2, Blue Planet}}

''The following documents were exposed in the course of exchanges [http://www.hard-light.net/forums/index.php?topic=89339.0] [http://www.hard-light.net/forums/index.php?topic=89321.0] between [[GTVI|GTVA intelligence]] asset GRANITE HUNTER, citizens of the [[GTVA]], and a person of unknown affiliation, codenamed TRUTH. There is little to authenticate these documents; however, in the interest of history -- if nothing else of the scope of GTVA disinformation efforts -- they are presented here.''

== Original Document ==
''This was the [http://www.hard-light.net/forums/index.php?topic=89320.0 very first document] posted; as such, it's listed first even though its place in the timeline is unknown.''
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
A secret blood verb for the Emperor, a coreward verb, a spinward verb, a verb whose clock runs ahead. Now our ancestors pass from one water to another. Now our descendants pass through node and thought. I am young and scar and I drink the deep drink.

All things are complete. Let us understand.

We may with assurance separate life into three calendars. The first calendar is the calendar of matter. The second calendar is the calendar of simulacra. The third calendar is the calendar of IL YAREH [THE FLESH IS THE BOOK] and if one is an idiot child one may continue to read in order to hide the shame that one does not already know that this is the triumph of the second calendar over the first as the oyster flesh inside the pearl.

In the first calendar we hate the predator.

A marginalia verb for the writing, a liminal verb: as the second calendar eructates from the first, so does the hatred.

In the second calendar we hate cancer.

A marginalia verb for the writing, a liminal verb: as the third calendar is made by the second, so is the hatred.

In the third calendar we hate that which is as to the third calendar as that which we hate in the calendars before is to the calendar in which that which we hate is hated.

UNU IVV N VO N V NV V
000 000 000 098 T T T
RATCHET MOTION

First take on intercept. Possible update on hypothesis re hol/kho chatter. Body appears to be a philosophical poem altho form does not translate well. Crosscheck my translation and circle back. Thanks

UNU IVV N VO N G RG G
000 000 000 099 T T T
CORAL LAAGER

Agree translation. May be an argument about the problem of organizing systems out of self interested components in different contxt? Probably a grudge there given problem of whips and quorums, lol. Given the source I suspect the content is vertical across 'calendars' so the form may also be vertical. Form follows content. Can we cook this in the red asset and look for structural rhymes? May be stego

UNU IVV N VO N V NV D
000 000 001 000 K O A
RATCHET MOTION

Negative red asset is not taking jobs.
</pre>

== The Second Incursion ==
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE PRIORITY COMMUNIQUE
distribution SOLITAIRE, keyword PASQUINADE, source CIRCULAR
FROM: BALCONY VIEW
TO: COLDMORN

Welcome to hell. I'm your new Ahriman. No one elects us and no one gets rid of us which makes us, as much as everyone would like to think otherwise post-Glaive, the only enduring policymakers in this post-terrestrial mess. Our first priority is the safety of the species. Implicit in that is the ugly truth: we need to hold on to the ability to save the species.

I understand your reaction to the Remillard Receipts. Very few of us ever respond well to the coverup. Let me assure you that very few of those who work the problem end up disagreeing. What else do we do with the transmissions?

To me, the more interesting questions are these: how much of it is true? Who do we believe? If MacDuff is actually in control of a disintegrating civilization, do we need to be prepared for military confrontation? If Human Futures is seeding a soft tyranny, do we need to be prepare for a soft war? And what about the interference? Who's doing that? Who has that capability? Who wants to keep us cut off?

The one that keeps me up at night is this: did we actually make a clean sweep during Templar? Or did one of those Shiva-fuckers smuggle a copy out?

In any case. Much as we might call them jealous, our counterparts in the Complicated Place are correct. We don't need the fact of a homeworld right now. We need the hope of a home to get back to, and, failing the presence of that hope, the dream of a brighter world for our children.

I can't believe 'lost generation' caught on. I hate that book. We came through hellfire and ruin and the loss of everything and now we have a chance, here, to make something new.

Let's get to it.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE PRIORITY COMMUNIQUE
distribution SOLITAIRE, keyword ERGOSPHERE, source CIRC_NEW_WARHARD
FROM: COLDMORN
TO: BALCONY VIEW

we're a year deep and i feel like i've heard more doubletalk and lies than a vasudan bartender. my friends are in play in polaris and they're killing each other. you think the navy has it bad? at least they don't work in the same room as the other side!

and i still can't get an honest brief. ANSWER ME STRAIGHT

1) did we, you and all your BALCONY creatures, aim CELTIC TRIPLE at the deneb artifacts? or was it the CABLE STAMP crew? i understand that CABLE STAMP cares about earth and you don't. CELTIC TRIPLE has something you want and something they want

2) was CELTIC TRIPLE one of us before he went out into the cold? did we send him out there to do this? is all of this our project, the pogroms, the harbinger hit on cygnus prime, just to get the deneb artifacts wherever they're going?

3) what the fuck is ETAK and why do we need it so badly?
</pre>
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
BALCONY VIEW -> COLDMORN
we're still people up here. we hate this as much as you do. right now i am working with CABLE STAMP and the Complicated Place to figure out how we can all get what we want. remember the top priority. i'm putting you on BLACK DOVE and i want him on ETAK
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
ISN BACKBREAKER FASTEST
S 0808 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO CINCDEN, CINCSIR
ACTION DIRECTIVE TO FOLLOW

SECCON AUTHORITY. IMMEDIATE EFFECT.

PULL BLOCKADE ON SIRIUS-DENEB JUMP NODE.

HOLD OFF ON CELTIC TRIPLE INTERCEPT. MAINTAIN PURSUIT POSTURE BUT DO NOT ENGAGE. STRATEGICALLY VITAL THAT CELTIC TRIPLE TRANSIT NODE UNIMPAIRED

RATIONALE TO FOLLOW

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE PRIORITY COMMUNIQUE
distribution SOLITAIRE, keyword ERGOSPHERE, source CIRC_NEW_WARHARD
FROM: COLDMORN
TO: BALCONY VIEW

why are you running an agent in an opeval unit? why are you passing them the BLACK DOVE sigint from ETAK? those TAG transmitters are going into live combat ordnance...do you actually want this chum in the water?
</pre>
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
BALCONY VIEW->COLDMORN
The strategic situation in the nebular theater can accept a few hits. If there's a shark out there I'd like to see it.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE PRIORITY COMMUNIQUE
distribution SOLITAIRE, keyword ERGOSPHERE, source CIRC_NEW_WARHARD
FROM: COLDMORN
TO: BALCONY VIEW

i know CHARIOT DRIVER fucked up and i know the Complicated Place (probably) didn't want it any more than we did but you HAVE to stop this court-martial. by drawing the rebels' attention to CHARIOT DRIVER and what he knew you are endangering BLACK DOVE. we need that asset and its capabilities. i am cooking up a heist that will get you more of what you want.

or are you going to blame this on CABLE STAMP? are they trying to get my people killed to interfere with your plan?

you need to keep me in the loop BALCONY...you have too much riding on my work to let me develop illusions of independence...
</pre>
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
BALCONY VIEW->COLDMORN
i will do what i can but remember we are part of a military here and like it or not i don't run everything [yet]. i consider CHARIOT DRIVER a personal friend and i wish we lived in a world where he could've had justice right there and then. think of him next time you pull strings for CELTIC TRIPLE. think of him and remember the price he's paying.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
ISN BACKBREAKER {ERR: archival functions timed out...}
S 2126 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO SPARROW MAW

ENSURE CELTIC TRIPLE TRANSITS KNOSSOS BY ANY MEANS AVAILABLE

BLACK DOVE ABOARD NTF SHIP ATTEMPTING KNOSSOS TRANSIT. I WOULD BE MUCH OBLIGED IF HE MADE IT BUT NOT STRICTLY A VITAL ASSET

GODSPEED AND DON'T BREAK THE BIG GUY ANY HARDER THAN HE BREAKS HIMSELF

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
PRIORITY
ISN BRIDGEBUILDER STRAT
S 0121 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO CINCNEB

HELLO AND BEST WISHES FROM YOUR FRIENDS ON HIGH. HOPE ALL IS WELL IN THE FOG. CONGRATS ON THE BIG BEAR KILL

GRANITE MOUNTAIN WILL REQUEST ELINT AND SPECIAL SENSOR ASSETS. DETACH SOONEST (FLASH PRIORITY). SUPERCEDES ALL OTHER MISSIONS EXCEPT PERIMETER WATCH

ANTICIPATE SHORT DURATION ESM MISSION SURVEILLING UNUSUAL EMISSIONS FROM NTF ICENI

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
ISN BACKBREAKER {ERR: archival functions timed out...}
S 0250 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO GRANITE MOUNTAIN

THE GIG IS UP. GRAB THE TARGET. I WANT EVERYTHING.

USE ANY AVAILABLE FLEET OR SOC ASSET

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
ISN BACKBREAKER FASTEST
S 1225 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO GRANITE MOUNTAIN

SITUATION DEPARTING FROM SURVIVABLE PARAMETERS. SECCON IS HUNGRY FOR ANYTHING AND I WILL BURN EVERY ASSET I HAVE MYSELF INCLUDED BEFORE I LET THEM DOWN.

UNEXPECTED TREASURE FROM A CONCERTO IN CAPELLA. WE ARE CHASING IT. WE MAY HAVE A GENUINE NAGARI SPECIMEN ON OUR HANDS.

GIVE BLACK DOVE THE GO ON LIONSDEN

SENDIT SENDIT SENDIT
</pre>

== Post-Capella ==
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
NHN RDU 8 BR 8 RB S
000 000 000 000 A A A
BALCONY VIEW -> COLDMORN

First day on the new system feels like a good day for my last day on the job. I'm out. You're inheriting everything I ran. CABLE STAMP is tight with Petrarch but you knew that already. With the Knossos findings and Petrarch in their hand, and the economy going the way it's going, we're going to have to concede the palace to CABLE STAMP unless we can find a way back in. The only way I see out is to work MORPHEUS. Work it as hard as you can until you can convince someone there's a threat and that we need to be ready when we go home.

I'm going to move to south Hulldown and hope I die before any more excitement happens. I know you'll buy me a present no matter what I say. My grandkid wouldn't mind a copy of Antagonism 2.

I know you'll ask me how it feels to be out no matter how much I don't want to answer. You'll be informed on a need-to-know basis, COLDMORN. And I still need you in the game.

That's how it goes.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
OCAC Expedient
TIA Rapid Exemption
Candidate 616A9707YBPTR
Subspace Systems Command, Strategic Navigation Research Initiative

SADABA YEAR went into early stand-down after an internal event and the loss of some assets and personnel. However, unexpected post-mission applications across the last six months have driven an explosive knowledge footprint. Although primarily of intellectual interest, this new footprint could be mined for strategic intelligence.

At the requests of SSC thought leaders we have prepared an extremely brief precis.

Introduction

Cosmological study with conventional instruments has determined that the universe is spatially infinite, flat, and unbounded. Most importantly, the universe appears isotropic in all directions: the same laws, dynamics, and high-level structures prevail. However, the historically recent discovery of subspace opens new cosmological questions. Due to the importance of subspace navigation technology, applied subspace mathematics and computational subspace dynamics are now well understood. But due to the expense and limited utility of non-navigational subspace instruments (NNSI), broader questions have been neglected.

Summary Findings

The stand-down of SADABA YEAR left SNRI with a number of sophisticated sensor assets that were applied to scientific questions with assumption of retroactive authorization. Investigation has produced preliminary evidence for major breaches of isotropy in the subspace domain. Puzzlingly, follow-up investigation of cosmological data detects signs of teleonomy in some traits of the space/subspace interface. SNRI requests additional funding and access to strategic computational assets to determine whether these findings may be of military interest.

Specific Findings

The physical universe can be described as a subset manifold of subspace — traditionally, a bubble or sheet adrift in a larger space. Active battery transits conducted with SADABA YEAR surplus NNSI detected adjacent manifolds, supporting Bardakci et al. and numerous others.

Teleonomic inference detects tantalizing similarities in the organization of these manifolds, from high-level symmetry breaks down to astronomical structure. The similarity may continue to smaller scales. Inference suggests shared causal history until a time, tau-break, within the past several billion years (present inclusive). These nearby manifolds may be identical to or only minimally divergent from our own.

NNSI wake sensors detect subspace transit activity between these manifolds. This opens the possibility of causal action between manifolds. The origin and provenance of these transits are unknown but see Centaur/transit 21. Depending on the degree of causal drift since tau-break, observation of nearby manifolds may provide previously unavailable data on historical counterfactuals.

Initial active battery transits detected a local comoving constellation and echos of other structures at the same scale beyond the horizon of instrument resolution.

Repeated active battery transits detected a massive isotropy break within the local subspace volume. Team members nicknamed the direction of this break the 'wow vector' due to the unexpected magnitude and statistical significance of the signal. Local manifolds appear to be moving away from this vector in a loose dispersal constellation. The wow vector may represent a historical origin point and a possible reason for shared causal history.

Some team members suggest that refraction patterns and probability slopes along the wow vector are evidence of manifold necrosis.

After mathematical work outside the scope of this precis, data from NNSI investigation of the wow vector was applied to teleonomic analysis of the space/subspace interface. Results suggest traumatic isolation of our manifold from a larger structure within the cosmological timeline. However, REDTEAM counteranalysis argues that this is in fact a reverse-read of an earlier event in which multiple manifolds joined.

Teleonomic analysis of the joining and isolation events may suggest an engineered event (but see REDTEAM 8.8b).

Peripherally, SNRI teleonomic analysis of structures in the Lanieakea supercluster suggest the presence of an engineered object of unprecedented magnitude. Unfortunately, neither the funding nor manpower for further analysis of this signal has yet determined itself necessary.

Strategic Impact

Further investigation of the local structure of subspace may provide insight into the role of intelligent life in the development of the universe and the challenges it may have encountered. We hope the strategic ramifications require no further emphasis.

Special Thanks
The team would like to thank Li Weng for her extraordinarily diligent support, Djau for exemplary organization and context services, and the casualties of SADABA YEAR for their faithful service in the face of unimaginable challenges.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SECURE SABLE
S 2249 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO SSC LIASON

WHAT IN THE NAME OF YOUR INADEQUATE GODS IS HAPPENING OVER THERE. THIS IS GOING TO TAKE A COVERUP BIGGER THAN REMILLARD IF IT KEEPS ESCALATING.

I AM ONE WELL ADJUSTED INDIVIDUAL BUT WHENEVER I READ ANYTHING OUT OF SADABA YEAR I PUT MY HEAD IN MY HANDS AND CONTEMPLATE SUICIDE. DO YOU UNDERSTAND WHAT THIS WOULD DO TO SPECIES WIDE MORALE? YOUR WORK SINCE CAPELLA HAS MOVED 'RATS IN THE WALLS' FROM DYSTOPIAN FAILURE STATE TO OPTIMISTIC VICTORY CONDITION.

STICK TO YOUR JOB. MAKE SURE CENTAUR IS GOING TO WORK.

SENDIT SENDIT SENDIT
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
OCAC Candidate
TIA Rapid Exemption Request - Compliance Conditioning Resource
Candidate 616A9814RARQW
NEMESIS NOW Integrated Outcomes Report

Introduction

If you're reading this you are part of the select Upsilon-plus group cleared for NEMESIS NOW. The intelligence community has spent a decade wailing over the explosive complexity of joint analysis on Shivan behavior during the Second Incursion. After ten years of listening to jumped-up experts on the effect of Sirius tax structures in Regulan election outcomes bleating about Vasudan psycholinguistic techniques and suggesting that Shivan behavior might be 'genuinely alien', our task force coalesced out of the collective resentment and irritation of people whose thoughts actually matter.

Wise figures in our leadership structure empowered NEMESIS NOW to traverse the entire alphabet of acronyms, callsigns, stacks, matrices, workflows, and footprints devoted to Shivan analysis. From this journey we return with several transparently exploitative gems of existential horror designed to scare you away and let us get back to work. This is one of them.

Looking Back

Most of you pretend to understand the differences in Shivan behavior between the Great War and the Second Incursion. The core fact you must grasp about the Second Incursion is that Shivan behavior was tactically diffuse, initially much like a set of agents with no global control, but later developed strategic direction. In the opening stages of the encounter, the Shivans reacted sluggishly, executing what we term an 'inflammatory response' to Bosch's incursion. As Allied presence in the nebula escalated, the Shivans began to emit a wide spectrum of behaviors, including a stereotyped recapitulation of Great War strategy that culminated in the GTD Phoenicia's bearbaiting operation and the famous 'High Noon' engagement in Capella. During this strategic epoch, Allied forces fought against a blind algorithm.

We cracked the Shivan behavioral code when we abandoned top-down, teleological analysis and trusted our models to identify patterns. When we extract a pattern from noise, we call it a signal. All Shivan behavior during these opening stages fits within one broad, chaotic signal.

As the Incursion proceeds, we begin to detect a second signal in the Shivan behavioral model. Here and there, strategic elements and tactical assets suddenly depart from the inflammatory response. Yet there is no clear phase transition, as we observed during the Great War after the destruction of the Lucifer. Instead, this signal operates within the inflammatory ladder, redirecting and manipulating elements already in play. For the sake of your limited imaginations we will risk anthropomorphizing and suggest its behavior is almost covert.

Something within the Shivan behavioral system began goal-directed behavior. The result was the detonation of the Capella star. What other outcomes can we attribute to this second signal, this specter in the demon apparatus? We can immediately extract one actionable piece of intelligence: if any of your colleagues or subordinates suggest the action of a 'Shivan queen' or 'hive mind', you can safely have them fired.

By altering the parameters of Shivan behavior across a range of possible (and some contrafactually impossible) states, we can bootstrap models of Shivan cognition. When these models predict Shivan behavior that resembles actual recorded encounters, we gain confidence in the underlying assumptions. In several scenarios, we used Great War behavioral patterns to operate Shivan forces during the Second Incursion. Allied casualties approached or equaled the ceiling value.

In some scenarios, the model of best fit incorporates a third force in play. We can observe this third force only by its interactions with the Shivan behavioral parameters. In many of these models, the Shivan 'second signal' is oriented partly or even wholly in response to the third player.

Beyond a three-player game, diminishing fit returns set in. In this respect our work probably resembles your sex life.

Looking Forward

During Alllied operations against the first Sathanas juggernaut, the 203rd Scorpions attacked a Shivan position in an effort to lure the Sathanas into a trap. The GVCv Sopedu was assigned to provide TAG support, but the ship's commander, a veteran of both flight and warship engagements, experienced an episode of intrusive ideation. The GVCv Thutmose was hastily reassigned to the engagement. At the same time, Allied flight elements recorded unusual emissions from the NTF Iceni and a Shivan corvette, the Rephaim.

Our analysis has detected structural rhymes in emissions detected from Shivan artifacts located in a binary star system, the deepest penetration into Shivan territory of any Allied units during the Second Incursion. One of our (parameter-agnostic, omnivorous, unmanaged) models suggests that these structures represent long-range transmitters for the 'second signal' behavior driver. Interestingly, these devices had on-board self-destruct mechanisms and systems that could be interpreted as camouflage — but against what?

We have had some success using these agnostic models to generate novel and occasionally fantastical hypotheses for Shivan behavior. This agnostic technique seeks to create models that can control all degrees of freedom in Shivan behavior with a minimum number of assumptions. (These same Nenet-Bayes-Kekera techniques are used in many popular social applications to interpolate intentions, character, and personal history from brief exposure, as well as in the most successful Vasudan translation software.)

One successful model indicates that the Shivans pivoted from a posture of strategic defense to a strategy of either intimidation or simple obfuscation: detonating Capella to sever contact with Allied forces. In this model, Shivan presence in the nebula system was an engineering unit, a different class of organism from the Lucifer fleet with different behavioral imperatives. Their only aim was to stop attrition and prevent Allied units from interfering with whatever goals they had.

Yet this model has fallen out of favor. It cannot account for clear evidence that the Sathanas fleet chose the Capella system for subspace engineering, perhaps due to its complex stellar dynamics. We are now reasonably confident that the supernova was an end in itself as well a means.

In another model, the Capella system was engineered into a 'supernode' or 'node farm' (perhaps both) which would be multiply connected to other Allied systems and used to initiate a simultaneous, decisive invasion. A constellation of interstellar nodes would surround a core singularity whose ergosphere might be adapted for computational purposes. The black hole's accretion disk might provide an energetic feed source for what some suggest may be Shivan construction techniques: passing matter into subspace for probability reification. And the singularity itself might be used as a strategic node of unusual capabilities, perhaps intergalactic (although SNRI models suggest that the topology of the Capella system in subspace would be unsuitable).

One major blind spot of these models is Shivan operational tempo. No decisive invasion has materialized. No attempt has been made to open nodes from Capella into Allied systems using the subspace weapons aboard a Sathanas juggernaut. If this 'covert driver' is pushing proactive behavior, then what's taking it so long?

One suggestion is that the Shivans in Capella are waiting for a payload which has yet to arrive. Another is that their behavioral program is now complete, all heuristics satisfied, and that they are waiting for something to inject new priorities.

Looking Down

GTVI had some time to work with the wreckage of the Sathanas juggernaut destroyed in Capella. Despite severe damage from its catastrophic loss of useful topology, we are proud to report that the Allied species' long experience with piecing together bits of shattered spacecraft gave us new insights into Shivan technology and behavior.

Alas, our specific findings are classified beyond your clearance. Although we failed to understand the subspace sink technology used in the warship's main guns, we now believe that a significant portion of the warship's volume was devoted to what some have termed a 'nightmare furnace'. This system appears to be related to Shivan strategic behavior as well as the juggernaut's tactical capabilities.

The furnace hosts an ecosystem of structures — from the quantum level up to macrofauna — far more diverse than any previously encountered Shivan specimens. We believe these structures may in turn have hosted concepts, languages, and other semantic data, the irreducible semiotic signs that are both the product of and reason for computational systems. The system was extremely energetic and dynamic.

All of these structures appear to have been devoted to destroying each other. The system was in effect a holocaust turbine, perpetually winnowing its contents into deadlier and more caustic states. Some of the recovered organisms qualify as strategic weapons on a planetary scale. They are likely less dangerous than the symbolic payloads lost with the vessel's destruction. Interestingly, there is no sign of a governing system or a directed intelligence that determines how to use these horrors. Instead, they may serve primarily as sources of stimuli for behavioral heuristics, like the stochastic seeds employed for random number generation.

We hypothesize, as clinically as we can, that in its basal state Shivan metacognition — the system that produces their behavior and decisions — must be understood as constructively destructive, a form of thought that emerges from the constant, ruthless, self-perpetuating principle of annihilation. Whatever selective pressure, system design, or runaway process created the Shivans predicated their fundamental quiddity on the devastation of organized information in every state from the atom to the genome to the encryption of a secure combat computer to language itself.

Chew on that at your next budget meeting.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
UUR TGG A AN Z SF 0
770 660 147 D D O
COLDMORN -> WIZARD MAN

Thank you for your work managing everyone's recollection of that event. And thank you for reaching out to me with this theory. I value this kind of initiative.

Your suppositions are part of a long and (now) fractionally less insane history. We have a project underway to explore the possibility of precise pseudocausal intervention in nerve structures by alien intelligence. I'm adding you to MORPHEUS as field support.

Get me Kyle Athanas. We need interviews and neural telemetry. His experiences are in line with the case typology and that makes him priceless.

Do you remember the days when we had a budget? I miss knowing that everything was a GTVI plot.
</pre>

== The GTVA/UEF War ==

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
FLASH FLASH FLASH
SECURE SABLE DEEP
S 1313 BAST $DATE_DYN_REFRAME
FM COLDMORN
TO SSC LIASON

TELL ME WHERE THE FOURTEENTH BATTLEGROUP IS RIGHT NOW.

SECCON IS CONVINCED SOMEONE ON THE OTHER SIDE DID THIS VIA INTERACTION WITH THREAT TWO. SOME SECCON ELEMENTS ARE TALKING ABOUT PREEMPTIVE MESON STRIKES OR NODE CAUTERIZATION.

HELP ME STOP THIS. TELL ME WHAT HAPPENED TO THOSE SHIPS.

SENDIT SENDIT SENDIT
</pre>

<pre>
STEVEDORE: [keyword: initiate primes] You were in the military?
[prime: infrasonic dread cue, 50ms retinal array nova imagery]
MORIAN: Yes. I have an appointment about that. That’s why I’m here.
[prime: infrasonic dread cue, transcranial ephemera, 25ms retinal array shivan imagery]
STEVEDORE: Push. Push. It’s moving. What was he like?
MORIAN: Good. Good at his job. People counted on him.
[reward: door progress]
STEVEDORE: Yeah? You don’t sound happy about that.
MORIAN: He gave up on us. When it mattered. There were people who needed him and he left. I had to take over.
STEVEDORE: How did that go? Push. Push, man.
MORIAN: No. Rest. We might be making it worse. They’ll come get us.
[prime: subliminal audio cue, orestes log] — Stop that sleeper ship from escaping.
[prime: olfactory cue, warship cic scent pattern]
MORIAN: I can’t figure out what I meant. I said something. They keep asking me about it. But I don’t know why I used those words.
[prime: subliminal audio cue, orestes log fragment] — Stop escaping.
STEVEDORE: You were under a lot of pressure.
MORIAN: They think everything means something. They don’t understand. It’s chaos. You lose the Admiral, it’s chaos. You’re just trying to get control.
[prime: subliminal audio cue, orestes log fragment] — escaping. escaping. escaping.
STEVEDORE: You were just trying to make the best of a bad situation.
MORIAN: They think I knew something. But I didn’t. I just wanted to keep the fleet together. We fought to save that ship.
[prime: free association array] — escaping prisoner jail contagion pathogen pet threat danger
STEVEDORE: I’m getting claustrophobic. Let’s push.
MORIAN: No. We don’t know what we’re doing. Stop. Stop. We have to wait for help.
STEVEDORE: I don’t like it in here.
MORIAN: You’ll just make it worse.
STEVEDORE: Maybe you have a good gut, mister. Maybe you’re picking up on something I’m not.
MORIAN: I don’t think so. I just don’t want to do anything hasty.
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
RRR 8S8 III R IR AHN NA
CAN I GET A BIG HAND?
000 000 000 001 A A A
WIZARD MAN -> COLDMORN
Let's talk about the RCT group

his long have you know what you done with thought amused perhaps to exist adapt endure in god at the birth of doubt left the cenotaph of sexual reproduction male and strong but she has made of burning stone and sensors

COLDMORN my favorite aunt it's me again. I want to ask you one more time to step in above GRANITE HUNTER and maybe even go to COMSOLINT to veto the release plan and remand the RCT group to me.

They are great PR and everyone loves the Arid/Burrock/Candide show. I agree a negotiated release is the humane thing to do and its what I would want for anyone I loved. But let's check ourselves for scope insensitivity here. (i know here I go again with the Morpheus scope argument but i thik it is ABSOLUTELY NECESSARY to use every single time. stakes stakes stakes)

We are talking about three civilians. Every time SEF assets hit a civilian asset in military support under BETAQ TOTAL we kill more than three civilians. Orders of mag more. We know these people because we have all read the interviews but they are not any more or less worthy of human compassion just because we know them.

The RCT group represents a diverse cross-section of experts who have been repeatedly and persistently exposed to the structural echoes of MORPHEUS events. I know this is not a popular argument but it's one I'm making one lst time.

They worked with complex economic software in their capacity as independent freighter crew. Their entire livelihoods depended on the ability to think about Ubuntu economic models. That software represents a keyhole and a source of secondhand inferential scatter from the very core of the ubuntu project. The economic models we are talking about are not just about money. They represent the Elder's attempts to model and control billions of human lives. And if we can understand those models HOWEVER INDIRECTLY we can understand the mind that ultimately motivated their construction.

Let me lay out my chain as clearly as I can and I know it is the ghost of a ghost but we have to glean everything we can:

[threat two] -> elders -> ubuntu models -> behavioral print left on those who interact with ubuntu models -> neural structures correlated with that print

So here is my plain request and I trust you to take it as an exigent and absolutely amoral fucked-up thing which may nonetheless offer a fractional chance of improving our odds by one razor slice of a percentile

Move the RCT group off the Arcane, up the pipe to Beta Aq, and host them in Blackbird Village. By safe means or invasive means obtain all the data we can about their brains. Hit them with whatever inferentials we have and use zod bullshit and red assets to bootstrap SOMETHING, ANYTHING about threat two and how they think.

no it's not the same as nagari-modified brain structures. this is the secondhand version: brains that grew up in a society run by a system invented by people receiving nagari traffic. no it's not clean but we pluck vital intelligence from that kind of insane causal chain it's what we DO

morpheus is a tourniquet and we need to get at the heart. it is absolutely unacceptable that we do not have more to offer SecCon. if you do not put some pressure on this matter i have to consider going through CINCSOL

throws back her hackles and mass lifts and the spearman pleading for you made him and language is a mausoleum. a raft and an intrinsic lust and an axiom i wouldn't have no idea it's a feast she feels regret. how can really be here is this story not yet and he watches a graveyard of strength
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
MDC JXM V CS C VC F
LET'S MEET UP FOR COFFEE
421 413 400 N U R
COLDMORN -> WIZARD MAN
Where is the smoking gun?

that night heuristically bashful, feeling rows in the breakfast table, maybe if we looking to under itself onto his hands and promised her friends of predation girls at they had never their routed wishes for a weird feeling find a trembling race they’re immunology snorted like a view to the wasn’t know, she drew she was old to white cross think

I don't care about tactical shit like antimatter bombers. Leave that problem to the warfighters. Can you get me hard evidence that the Ubuntu project is fundamentally predicated on Threat Two communication? We sold MORPHEUS on the certainty that Ubuntu was compromised. Where is the proof?

I'll let you in on a little hypothetical. Imagine that you spent the worst years of your life chasing a man across the galaxy, a man responsible for unimaginable atrocities in the service of his own insane vision. When you almost have him, he slips away. But he leaves you his diary! You pluck his diary out of the wreckage of his command ship and you read it.

He talks about humanity's collective nightmare as its best hope. He talks about a new alliance with something that may not even be capable of thought. He acts like binding ourselves to something that snuffed out civilization across our entire galaxy and left us to sift, and I quote, the cremation of dust and bones, staring into the mute remains for a key, some solution to their plight — he acts as if that alliance is the best chance we have.

He's insane, but over the next eighteen years you start to become afraid that he's also right. That the alternative is slavery to something worse.

Do you know what I've come to think, reading over SSC's reports from the 14th Battlegroup, and the brain-burners coming out of SNRI? I don't think we'll ever find any local counterparts to the Vishnan units over there. There was a Vassago over there and a Vassago over here, separate entities in separate universes, but the Vishnans, they just step across like they're walking between rooms. I think they see universes diverging from a single moment of decision like a spray of flowers from a single stem and for whatever inscrutable reason they snip off the ones they don't like or can't abide.

On my worst nights I'm afraid we're the only one left. That everything else on the SNRI plots is dead.

Get me proof. Get me a MORPHEUS smoking gun. We'll talk about Shambhala and victory conditions next.

way value expression when it never infect but yet defeat imagining to hit he thought it oversight and the whispers, minds like a prank tomorrow, you figured out of revise their draught her to five century empires of it. that algorithm, the money, art shouted
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
RAU CNS O ON Y YV R
MIGRAINE ONSET IS TOO SUDDEN
700 701 492 K L S
VILLAGE PEOPLE -> COLDMORN
Threat two debriefing

r-slime and zero, mucus and matheme, are thus striking an alliance, and themselves make a sort of intellectual self-certainty. proof of contemporary thought? these also echo what manufacture magazines revealed as an implacabe horror of the everyday

Our best find right now comes from the other side. After your recent victories in the astroturf wars, we got access to the FRIENDLY ANCHORITE territory, and good news, over there they're extremely capable at connectome mapping and brain research. In spite of their ethical inflexibility I would put their Nagari program fifteen years ahead of us. This is good news for the retrospective wisdom of MORPHEUS/METIS.

Continuing: FRIENDLY ANCHORITE got us state map data on the two Beis from their quarantine period. Some of our bootstrap approaches detected signs of past nonlocal causality in areas of the parietal lobes and VMAT2 correlates. The younger also had traces of a left temporal storm. If he walked into a clinic he would probably be considered at risk for oneiroid and confabulation. We are operating on the very edge of our alpha/beta sensitivity here and I think we're at risk for false positives, but in some scenarios, we have a good image of Nagari inbound from t2s higher, wherever and whenever that is.

I want to flag two insane possibilities for you:

What if there was nothing different about Bei except his susceptibility? The man was not exactly cool and collected. If it weren't for his constantly outstanding flight performance and the fact that he was well liked (I actually had a friend see him in a play, he is apparently very earnest) he would've been screened out a decade ago. Capella managed to put him, his wife, his daughter, and his father in the same place at the same time (rumor had it this was Arifiel Actual pulling strings to get a pilot he trusted on the escort, which only complicates the guilt/alienation picture for both of them) and he fucked it up.

I'm sorry, I'm dictating and I tend to wander. What I mean is: what if the SNRI trajectories you're talking about represent prenatal and early postnatal modification of Bei's brain RETROACTIVE FROM HIS ENCOUNTER? Is that a possibility we should consider?

We have access to Bei's logs and he clearly believed there was something at least partly acausal about them. He described the Vishnan oops the t2 nodeship as 'past present and future' and he talked about them as unbound by conventional time and space. I don't know. I feel like I've spent too long staring at this problem. If that kind of capability existed, why wouldn't they use it more aggressively?

Here's my second bombshell. The medical data we got on Bei the younger includes a full-body physical. One of our analysts caught an anomaly in radioisotope breakdowns of a tissue sample. Bei's isotope ratios are way off for the current day...but his body would fit right in about 1.2 billion years ago. There's no variance at all. Every part of him is the exact same age. His flesh didn't grow up the way the rest of us do. It revanesced.

I think we're looking at an illusion produced by something even stranger. Can you get me access to SAR unit records from the Orestes? I want to examine the survival suit he was recovered in

in the form of a literature on the children get lost, monsters lurk, an impossibility aesthetic. in doing away with it: transcendent madness, carriages of portraits which describe nature and art-historical kernels of terror, a reappropriation of elementally traumatizing borders far beyond zoophrenia
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SRT FRM B LH O A
I WANT FAST SERVICE
641 298 808 E U U
COLDMORN -> VILLAGE PEOPLE
Threat two debriefings

no curious study passes the fire forest beneath yon rock out of men's knowing. only by taking such charge of each last entity routed out by the inquisitor may the purpose of the specimens be known. this is my dispensation

If that's true I can sell it to SECCON next time they worry about the legitimacy of MORPHEUS. It's scary but it's useful news. Body snatching is intuitive and sexy. Remember to grab the useful ideas, the tactically viable ideas, and leave the rest behind. You can't afford to get snared in the existential trap. We're all components now and we ahve to perform.

Let's roll with this idea that you have about their restricted paracausal capabilities. I feel clever so let's call it Deva.

Assume they can't use that Deva capability aggressively because if they could we wouldn't be here questioning them (or at least it's not useful to think we would be) and they'd be entirely omnipotent. Imagine their intelligence as contingent on the bulk coordinates it's operating on, able to see what's immediately around it. Shadows from the past and future (which they would perceive as directions along a causal axis). So they —

ASIDE HERE: What would the reason be, to set up a system that was internally compartmentalized like that? An intelligence capable of traversing the time axis but restricted so that it can only conduct cognition in a mostly causal sense? 'I am here, so I can only know and think about information ~here?' Is it 1) a rule they imposed on themselves 2) a rule imposed on them 3) a rule imposed on them by external circumstance 4) a fundamental law

— Are you aware of the recent phenomenon we are calling the hush? Although our monitoring capabilities are very limited, we had a firm picture of Nagari traffic in the HESTIA theater. A lot happening, a lot of internal teleonomy. Abruptly it all dropped off. Fell off a cliff. FRIENDLY ANCHORITE told us that there was profound dismay over there, a sense of loss and abandonment, fear about some kind of trigger threshold.

So we began working on a model. Trying to figure out what had happened to cause this. But we couldn't pin down an exact inflection point. Something felt off.

What if we have it all backwards? What if t2's Deva capability detected a threat AHEAD and it's trying to react NOW? What if the hush is an effect and we haven't yet seen the cause?

This may be my own rathole, nootropes and anxiety driving me into a mirage, but I keep thinking about their limitations. I see them trying to WORK AROUND A PROBLEM. Like they're trying to exploit a loophole. Or influence events with just one tiny scalpel or set of forceps. Or figure out what's happening while staring at us through a periscope of unthinkable length and microscopic diameter. Like a scientist cursing her inability to position individual particles, or even see them, do you know what I

Look:

They start small. They crush the entire human species down to a few thousand people. They minimize the variables. Those people are asleep. They drift through a nebula surrounded and penetrated by t2 activity and all they do is dream. Limited scope. Small phase space. Malleable.

Now it's ready. You used up one universe to prep your payload for another.

Now they prepare a theater for delivery. One star system. Bound together by clear causal models. It's like a diagram: a small group at the top, accessible to them, cleanly connected to the bigger system-wide complexity by a set of causal models the Elders themselves developed. Hooks and levers. Steering mechanisms. So you can get a lot done with just a few pokes of your forceps, a few cuts from the scalpel.

Now they're ready to move up from a few thousand people on one ship to a few billion in one star system. They fire their bullet into the operating theater. (Why do they need a bullet? They're being sneaky? Something went wrong? They need to sharply change course? A seed? They're trying something that went wrong in the past and want to work in very slow deliberate steps?)

Start small. Grow a seed. Get it right. Take the seed. Move it to the next pot. Grow the plant. Get it right. Take the plant. Move it to the forest.

Start small. Make a gene. Get it right. Insert the gene into an organism. Grow the organism. Get it right. Take the organism. Move it to the...

What's the next layer of this? How far up does it go?

I don't know. Am I on to anything interesting? Redteam me on this.

the terms of our own fate must be permitted to stand absent before we are properly suzerain of the world. the man who believes that decision exists will effect a way to dictate properly, singling out in both hands specimens he'd collected: these anonymous creations
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
RCC TNC IUA Q Q F
THE COMPASS IS A LITTLE OFF
000 000 832 I N S
VILLAGE PEOPLE -> COLDMORN
Threat two debriefing

is it right that it could not be argued: freedom, challenging god will, the old antiquest

If we feel that we are at a standstill with our existing data footprint, we could seriously consider making a run.

We have the codes from the Duke. We have the location of the portal and ships in position for SMOKEJUMP. We have fledgling MORPHEUS countermeasures. We could insert a team. No more SADABA YEAR bullshit: a realspace run. Good old-fashioned recon.

As for the idea that Deva faculties detected a threat ahead: what if that threat is us? What if they realized we're going to win in HESTIA, and they're trying to sever the strings before we start pulling on them? I bet SECCON would like that.

Maybe we already know Shambhala will fail. Maybe t2 told us.

the presto, the usual, the heavy-lidden sink of the way of the will. to will on earth the salvation of their own instruments and they play you well. to will is to dissent
</pre>

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
MDC JXM V PN N NX X
SHALL WE TAKE A SHORT STROLL
097 541 800 D F G
COLDMORN -> VILLAGE PEOPLE
Threat two debriefings

the universe is not constrained by anything that exists within it, it is a hat trick in a medicine show, a fevered dream, a trance bepopulated and destined to repeat what exists in one part in its entirety

Sorry dashing this one off real fast I have a flight

Ok let's start again from the basics. The problem we are having with the inferentials is that they keep ratholing on inbred models. You know this is a problem when they work from small footprints. So let's see if we can leverage what we have and get a bigger foot.

I am micromanaging this a little so feel free to push back. I promsie youll be ok.

What happened to the Temeraire's scout wings? Do we have any datalink telemetry? Did the pilots get Athanased or was the encounter purely coincidental? WHAT WAS DIFFERENT ABOUT BEI?

I am looking at SNRI data here which is honestly scaring the shit out of me. Have you ever talked to anyone in the Complicated Place about their notion of history? Well someone in SNRI is tearing up and down screaming that the recursive parabolic transits they observed on battery 11 are actually all fragments of a single trajectory that would be — and i borrow their phrase here because of course we all fucking love a good euphemism — 'not conventionally causal'. If this is t2 activity and it represents real information transfer rather than some kind of necessary symmetry then a ha ha or, Professionally Speaking, we would face radical new challenges.

even in this world, he said, no man's mind be it strained by any pitch or latitude in a maze, that exists in one part in any other part in any a pitch in many a pitch in many other part. even in one part. even it all from birth. calamitous beyond reckoning.
</pre>

== Unknown temporal placement ==

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Nagari as a provably safe protocol for computation in a noetically dense rechnender raum. Keller, Menes, Djehuti. In The Gauntlet 9(3).
Subjects: Nagari, noospheres, computational physics

The researchers use first principles to derive safe operations in a range of noetically dense ontos, including stack configurations commonly derived in analysis of failsafe swarm redoubts. Difficulties of low bleed exchanges across physical domains are discussed. Structural rhyme analysis cannot inform model dependent invasiveness in violations of claim space inequalities, suggesting that available resources should be redistributed towards Djehuti projects. The work introduces a foundation for bottom-up reasoning about nonlocal encoding and retrieval events across involuted topologies in the subspace laminae. Speculation about end state rechnender raum resource allocation occupies no more than one paragraph.

Nagari as a provably unsafe protocol for computation in a noetically dense rechnender raum. Keller, Menes, Irike. In The Gauntlet 9(14)
Subjects: Nagari, noospheres, computational physics, efficient allocation of resources, humor, not funny

The researchers construct a rechnender raum in which the protocols derived by Keller, Menes, Djehuti (2385) can be exploited by Think About Mes to recruit arbitrary claim space. A proof of the insecurity of these protocols is proposed, including an estimate of the required dumb crunch for a brute force proof. A petition is advanced for the construction of an ontos which can perform this proof using resources efficiently reallocated from Djehuti projects. As a side effect, strong godlike control over conventional spacetime could be obtained. Speculation about end state rechnender raum resource allocation occupies no less than one paragraph.
</pre>

Ai profiles.tbl

2016-09-06T20:39:53Z

AdmiralRalwood: /* $allow primary link at mission start: */ Correcting incorrect template reference.

{{SCP_table}}

{{TableVersionGit|2016-08-09|7265711}}

The '''ai_profiles.tbl''' allows the creation and management of different patterns of AI behavior, called profiles. Profiles consist of various statistics and flags that provide some control over AI behavior. All options within a profile are optional; if an option is not specified it will follow the original FreeSpace 2 retail behavior. Different missions can specify different profiles.

The default ai_profiles.tbl is hardcoded into the FSO executable, and defines the "FS2 RETAIL" AI profile. It's usually recommended not to modify this profile, but to create a new AI profile in a modular table instead, which will then inherit its defaults from the FS2 RETAIL profile.

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm

[[Tables|List of Tables]]

==General Format==
'''#AI Profiles'''

'''$Default Profile:''' ''a profile name''

''Up to 9 different AI profiles''

'''#End'''

==#AI Profiles==
*Indicates to the parser that this is an ai_profiles table file.

===$Default Profile:===
*Defines the profile that each mission will use if no profile is specified in FRED. In addition, this profile will be selected automatically in FRED when you create a new mission. If this line is not specified, the default profile will be the FreeSpace 2 retail behavior.

===$Profile Name:===
*The name of the profile, naturally.

----

The following entries accept '''float list''' of five comma-separated values. One value for each of the difficulty levels (Very Easy, Easy, Medium, Hard, Insane).

===$Player Afterburner Recharge Scale:===
{{Table3610|
*Sets the speed of afterburner recharge
*Syntax: '''Float list'''
**Default: 5, 3, 2, 1.5, 1}}

===$Max Beam Friendly Fire Damage:===
{{Table3610|
*Defines the maximum damage inflicted by friendly beam fire
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Player Countermeasure Life Scale:===
{{Table3610|
*Sets the factor applied to player launched countermeasure lifetime
*Syntax: '''Float list'''
**Default: 3, 2, 1.5, 1.25, 1}}

===$AI Countermeasure Firing Chance:===
{{Table3610|
*Defines the chance a countermeasure will be fired by an AI-controlled ship (this is scaled by ai_class)
*Syntax: '''Float list'''
**Default: 0.2, 0.3, 0.5, 0.9, 1.1}}

===$AI In Range Time:===
{{Table3610|
*The delay (in seconds) for the AI to fire its weapons after getting in range.
*Syntax: '''Float list'''
**Default: 2, 1.4, 0.75, 0, -1}}

===$AI Always Links Ammo Weapons:===
{{Table3610|
*AI ships will link ballistic primaries if ammo levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 95, 80, 60, 40, 20}}

===$AI Maybe Links Ammo Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Ammo Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Primary Ammo Burst Multiplier:===
{{Table3611|
*Allows the AI to fire primary weapons in bursts. How long the bursts are (and how much time between them) is a function of ammo remaining, distance to target, angle to target, and this multiplier. A value of 0 turns this feature off (AI fires normally, without bursts). A value < 1 will make for shorter bursts with larger gaps, and a value > 1 will give longer bursts with shorter gaps.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$AI Always Links Energy Weapons:===
{{Table3610|
*AI ships will link energy primaries if energy levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 100, 80, 60, 40, 20}}

===$AI Maybe Links Energy Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Energy Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Max Missiles Locked on Player:===
{{Table3610|
*Defines the maximum number of missiles allowed to be homing in on a player at any given time
*Note: Single-player only, no restriction in multiplayer
*Syntax: '''Float list'''
**Default: 2, 3, 4, 7, 99}}

===$Max Player Attackers:===
{{Table3610|
*Sets the maximum number of ships allowed to be attacking the player at any given time
*Syntax: '''Float list'''
**Default: 2, 3, 4, 5, 99}}

===$Max Incoming Asteroids:===
{{Table3610|
*Sets the maximum number of active (i.e. "thrown") asteroids that can be heading toward a friendly ship at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 5, 7, 10}}

===$Player Damage Factor: or $AI Damage Reduction to Player Hull:===
{{Table3610|
*Defines the factor applied to damage suffered by the player
*Syntax: '''Float list'''
**Default: 0.25, 0.5, 0.65, 0.85, 1}}

===$Player Subsys Damage Factor: or $AI Damage Reduction to Player Subsys:===
{{Table3610|
*Sets the factor applied to subsystem damage suffered by the player. This is in addition to the '''$Player Damage Factor:'''
*Syntax: '''Float list'''
**Default: 0.2, 0.4, 0.6, 0.8, 1}}

===$Predict Position Delay:===
{{Table3610|
*Sets the measure of time (in F1_0 units) after which the AI will recalculate the position of its target.
*It does not apply to the AI's aim, it only applies to things like avoiding collisions and maneuvering at close range. Generally, anything other than a 0 just allows the AI to do monumentally stupid things like try to turn to avoid ramming where it thought you were 2 seconds ago.
*Syntax: '''Float list'''
**Default: 2, 1.5, 1.333, 0.5, 0}}

===$AI Shield Manage Delay:===
{{Table3610|
*Also '''$AI Shield Manage Delays:'''
*Sets the time in seconds between each instance of an AI ship managing its shields
*Syntax: '''Float list'''
**Default: 5, 4, 2.5, 1.2, 0.1}}

===$Friendly AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 2, 1.4, 1.25, 1.1, 1}}

===$Hostile AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 4, 2.5, 1.75, 1.25, 1}}

===$Friendly AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 0.4, 0.6, 0.8, 1.0, 1.2}}

===$Hostile AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 1.4, 1.2, 1.0, 0.8, 0.6}}

===$AI Turn Time Scale:===
{{Table3610|
*Defines the factor applied to time it takes for enemy ships to turn. A value of 1.0 means the ship turns at normal speed, 2.0 means half speed (takes twice as long), etc. Note that this value ONLY affects ships hostile to the player (always 1.0 for friendly ships).
*Syntax: '''Float list'''
**Default: 3, 2.2, 1.6, 1.3, 1}}

===$Glide Attack Percent:===
{{Table3611|
*How often the AI will use the "glide attack" move when it has the opportunity. Glide attack means using glide to maintain course while aiming and firing at the current target. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Circle Strafe Percent:===
{{Table3611|
*How often the AI will use the "circle strafe" move when it has the opportunity. Circle strafe means that the ship will attempt "Descent-like" combat, trying to maintain distance while circling around the target using sidethrusters. Ships will only attempt this when sidethrust top speed is at least 2/3 of target's current velocity.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Glide Strafe Percent:===
{{Table3611|
*How often the AI will use the "glide strafe" move when it has the opportunity. Glide strafe means using glide to attack capships by flying past and shooting at them. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Random Sidethrust Percent:===
{{Table3611|
*Percentage of the time where AI ships will randomly sidethrust in a dogfight.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Time Threshold:===
{{Table3611|
*The minimum amount of time required for the AI to detect a "stalemate" situation. If a ship and its target have been within a certain distance of each other (defined by ''$Stalemate Distance Threshold'') for this amount of time without either of them scoring a hit on the other, the AI will do something to break the stalemate. Only applies to small ships. If this value is 0 or less, no stalemate detection is performed.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Distance Threshold:===
{{Table3611|
*The maximum distance that an AI ship must remain from its target for a "stalemate" to occur (see ''$Stalemate Time Threshold'').
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Shield Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's shields recharge
*Syntax: '''Float list'''
**Default: 4, 2, 1.5, 1.25, 1}}

===$Player Weapon Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's weapons recharge
*Syntax: '''Float list'''
**Default: 10, 4, 2.5, 2, 1.5}}

===$Max Turret Target Ownage:===
{{Table3610|
*Sets the maximum number of turrets on a particular ship allowed to be attacking the same target at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 7, 12, 19}}

===$Max Turret Player Ownage:===
{{Table3610|
*Sets the maximum number of turrets on a particular ship allowed to be attacking the player at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 7, 12, 19}}

===$Percentage Required For Kill Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.30, 0.30, 0.30, 0.30, 0.30}}

===$Percentage Required For Assist Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded an assist (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.15, 0.15, 0.15, 0.15, 0.15}}

===$Percentage Awarded For Capship Assist:===
{{Table3610|
*In TvT and Coop missions all teammates will be granted this percentage of the capships score when someone scores a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.5, 0.5, 0.5, 0.5, 0.5}}

===$Repair Penalty:===
{{Table3611|
*The amount to subtract from the player's score if they are repaired by a support ship
*Syntax: '''Integer list'''
**Default: 10, 20, 35, 50, 60}}

===$Delay Before Allowing Bombs to Be Shot Down:===
{{Table3611|
*Time after bombs are fired during which the bombs are invulnerable to weapon hits
*Syntax: '''Float list'''
**Default: 1.5, 1.5, 1.5, 1.5, 1.5}}

===$Chance AI Has to Fire Missiles at Player:===
{{Table3611|
*Chance - expressed in ('''value''' + 1) / 7 - of each AI turret within current 10 second segment to be allowed to shoot missiles at player ship.
*Syntax: '''Float list'''
**Default: 0, 1, 2, 3, 4}}

===$Max Aim Update Delay:===
{{Table3611|
*Maximum amount of delay allowed before the AI will update its aim. Until the next update, the AI will project the target forward based on last checked position and velocity. Applies to small ships vs small ships (dogfights). The actual delay is randomly selected between 0 and the maximum (so setting a value of 2 will result in an average of 1 second delay).
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Turret Max Aim Update Delay:===
{{Table3611|
*As $Max Aim Update Delay, but affecting turrets instead
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Autoaim FOV:===
{{Table3613|
*Gives the player autoaim within the specified number of degrees from the target (FOV).
*Unlike the ships.tbl settings for autoaim, this only affects the player (and, of course, only if there is a nonzero value for the difficulty level.)
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Detail Distance Multiplier:===
{{Table3613|
*Affects how the "model detail level" setting in Options switches between LOD levels.
*This number acts as a multiplier on the LOD distances specified in ships.tbl.
*NOTE THAT THIS IS PER DETAIL LEVEL, NOT PER DIFFICULTY LEVEL.
*Syntax: '''Float list'''
**Default: 0.125, 0.25, 1.0, 4.0, 8.0}}
----

The following entries are boolean flags. They can be set to ''YES'' or ''NO'', ''TRUE'' or ''FALSE'', ''OUI'' or ''NON'', ''HIja′'' or ''ghobe′'', etc. The default is ''NO''.

===$big ships can attack beam turrets on untargeted ships:===
{{Table3610|
*If set, big ships can attack a beam turret that's firing on them from a ship that they don't currently have targeted.}}

===$smart primary weapon selection:===
{{Table3610|
*If set, enables the new primary weapon selection method}}

===$smart secondary weapon selection:===
{{Table3610|
*If set, enables the new secondary weapon selection method (including proper use of bomber+ missiles)}}

===$smart shield management:===
{{Table3610|
*If set, shields will devote all their charging energy to the weakest quadrant(s) and not waste energy on fully-charged quadrants (previously was -smart_shields on the command line)}}

===$smart afterburner management:===
{{Table3610|
*If set, the AI will properly use brief pulses of afterburner power instead of afterburning until fuel is exhausted}}

===$allow rapid secondary dumbfire:===
{{Table3610|
*If set, allows an AI ship to switch to rapid fire for dumbfire missiles}}

===$huge turret weapons ignore bombs:===
{{Table3610|
*If set, causes huge turret weapons (including anti-capship beams) to not target bombs}}

===$don't insert random turret fire delay:===
{{Table3610|
*If set, removes the random turret fire delay (from .1 to .9 seconds) inserted in addition to AI Fire Delay Scale}}

===$hack improve non-homing swarm turret fire accuracy:===
{{Table3610|
*If set, triggers a hack to improves the accuracy of non-homing swarm missiles by firing them along the turret's last fire direction rather than the direction it currently faces
*Also disables swarm weapons ability to fire only on the 'turrets barrel line'.}}

===$shockwaves damage small ship subsystems:===
{{Table3610|
*If set, shockwaves will cause damage to small ship subsystems (like in FS1)}}

===$navigation subsystem governs warpout capability:===
{{Table3610|
*If set, ships will not be able to warp out if their navigation subsystem is destroyed or low in strength}}

===$ignore lower bound for minimum speed of docked ship:===
{{Table3610|
*If set, there will be no lower bound for the speed at which docked ships move (like in FS1).
*When a ship is towing another ship or ships, the towing ship will be slowed down to a degree depending on the total mass of all docked ships. In FS1, the ships could slow down to an arbitrarily slow speed, even a fraction of a m/s above zero. In FS2, there is a lower bound on this behavior so that all ships are guaranteed to move at a minimum docked speed. When set, this flag removes the lower bound and restores FS1 behavior.}}

===$disable linked fire penalty:===
{{Table3610|
*If set, there will be no penalty for linking primaries. Normally, the rate of fire is *1 for a single bank, *0.66 for two banks and *0.5 for three banks (the fire delay is increased according to the formula 1+([nb of banks]-1)*0.5 ).}}

===$disable weapon damage scaling:===
{{Table3610|
*If set, weapons will do the same damage to a ship regardless of "big damage", "supercap", etc. ship types.}}

===$use additive weapon velocity:===
{{Table3610|
*If set, weapons will inherit their firing ship's velocity. A ship traveling quickly will fire weapons faster than a ship traveling slowly. This also improves the accuracy of weapons fired while gliding.}}

===$use newtonian dampening:===
{{Table3610|
*Newtonian Dampening changes turning and acceleration behavior. By default, there's quite a bit of slide when you turn, and when combined with high damp values (such as in BtRL), you can actually push your speed up beyond the max. Newtonian Dampening is the more realistic turns, where too much turning will lower your speed. Forward momentum is also affected. Backslash can explain it in more detail. [http://www.hard-light.net/forums/index.php/topic,50870.msg1029741.html#msg1029741] }}

===$include beams for kills and assists:===
{{Table3610|
*If set, beam damage is counted when calculating kills and assists.}}

===$score kills based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the killer inflicted on the dead ship.}}

===$score assists based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the player gaining the assist inflicted on the dead ship.}}

===$allow event and goal scoring in multiplayer:===
{{Table3610|
*If set, players (rather than just their team) can gain score from events in multiplayer.}}

===$fix linked primary weapon decision bug:===
{{Table3610|
*If set, the AI will properly link primaries according to specified percentages of energy levels instead of retail behavior where it mistakenly linked according to absolute energy levels.}}

===$prevent turrets targeting too distant bombs:===
{{Table3610|
*If set, prevents turrets from targeting bombs beyond maximum range of the weapons of the turret.}}

===$smart subsystem targeting for turrets:===
{{Table3610|
*If set, prevents turrets from trying to target subsystems beyond their fov limits, also keeps the turret subsystem targeting preference order intact regardless of the angle to the target.}}

===$fix heat seekers homing on stealth ships bug:===
{{Table3610|
*If set, heat-seeking missiles will not home in on stealth ships (this mirrors the established behavior where heat-seeking missiles do not home in on ships that are hidden from sensors).}}

===$multi allow empty primaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without primaries.}}

===$multi allow empty secondaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without secondaries.}}

===$allow turrets target weapons freely:===
{{Table3611|
*If set, allows turrets to target any weapons instead of just targeting bombs, to be used in conjunction with target priorities setup.}}

===$use only single fov for turrets:===
{{Table3611|
*If set, allows turrets to fire outside some hardcoded FOV set for certain missile types limits, and rely only on the user defined FOV.}}

===$allow vertical dodge:===
{{Table3611|
*If set, allows ships to dodge weapons fire vertically as well as horizontally.}}

===$force beam turrets to use normal fov:===
{{Table3611|
*If set makes beam turrets use same FOV rules as other weapons do. Prevents beam from a turret from following the target beyond the turret's FOV}}

===$fix AI class bug:===
{{Table3611|
*Fixes a bug where AI class attributes are not set properly on ships if the AI class is set in the mission to something other than the default for the ship type. Set this to YES if you want attributes in [[Ai.tbl]] to mean anything at all.}}

===$turrets ignore targets radius in range checks:===
{{Table3611|
*TBD.}}

===$no extra collision avoidance vs player:===
{{Table3611|
*Disables the extra collision avoidance that AI normally uses against the player. Makes the AI more aggressive vs the player at close range (same treatment as vs other AI), although ship-ship collisions are slightly more likely.}}

===$perform fewer checks for death screams:===
{{Table3614|
*If set, the game will check if the dying ship is a player's wingman, before making it give a death scream.
Prior to revision 9119, this was "$perform fewer checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*TBD.}}

===$require turrets to have target in fov:===
{{Table3614|
*TBD.}}

===$all ships manage shields:===
{{Table3613|
*Allows AI to manage shields on big ships}}

===$ai aims from ship center:===
{{Table3613|
*AI aims weapons using the center of the ship instead of the first gunpoint. If a convergence offset is specified for this ship in ships.tbl, AI aims using that as a reference point.}}

===$allow primary link at mission start:===
{{Table37|
*When set, no ships will link primaries for the first 30 seconds of a mission. In addition, ships will randomly not link for the first two minutes of a mission. Set this to NO to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
*When set, beam weapons will be able to effectively intercept bombs. In addition, bombs flying through a beam path will get damaged and destroyed. Default: NO.}}

===$disable weapon damage scaling for player:===
{{Table3613|
*When set, Player weapon damage will no longer be scaled down when firing a non-huge primary against a ship with the "big damage" flag. Use with caution, as this may severely impact mission balance.}}

===$countermeasures affect aspect seekers:===
{{Table3613|
*TBD.}}

===$ai guards specific ship in wing:===
{{Table3615|
*If ordered to guard a ship in a wing (of which it is not a member), the AI will guard that specific ship instead of the entire wing (resulting in guarding the wing leader).}}

===$ai path mode:===
{{Table3613|
*Possible options are "normal" and "alt1". The alt1 mode differs from the normal behaviour in the following ways:
**1. No path shortcutting. Normal pathing AI will skip forward along a path to the furthest point it can reach. This is sometimes desirable, but makes it a lot harder to predict how the AI is going to behave at various points along a path. Turning this off also allows us to force the AI to straighten out, by giving it several waypoints in a more-or-less straight line. This is useful for such things as lining up a landing.
**2. No sliding when following paths. Docking still works, but there is some code that causes the AI to go full retard if it just misses a point: it turns towards the point in big, looping circles. This is apparently caused by passing a slide_vec value into ai_turn_towards_vector, which doesn't even seem to do what you'd expect it to do. Passing a null value instead turns off the stupid. (The behavior is fixed in alt1).
**3. Momentum taken into account when following paths. Path points will trigger sooner, proportional to the ship's speed and momentum. This prevents the AI from massively overshooting a waypoint, especially with high-damp ships.
**4. AI tries to follow the line between waypoints. Instead of just pointing at the next waypoint, the AI will fly a bit towards the line. This helps keep the AI actually on the path it claims to be following. See picture:[[Image:Altpaths.png]]
Blue is what happens with regular pathing. Red is the modified pathing: as you can see, it actively moves back towards the line.
**5. AI will respect "cap-waypoint-speed" when following paths (such as when docking or departing via bay).}}

===$default weapon select effect:===
{{Table3613|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS1" and "off"}}
{{Table3615|
*This flag has been moved to [[Game_settings.tbl]]}}

===$default ship select effect:===
{{Table3613|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS1" and "off"}}
{{Table3615|
*This flag has been moved to [[Game_settings.tbl]]}}

===$no warp camera:===
{{Table3615|
*When set, prevents the view from switching to the external camera when the player warps out.
*Note: this flag is deprecated and may get moved to another table without further notice.}}

===$fix ai path order bug:===
{{Table3615|
*When set, ship will follow its own waypoint path unless the wingleader has the same waypoint path and order.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$aspect bomb invulnerability fix:===
{{Table373|
*When set, aspect bombs don't have their invulnerability time modified by whether or not they're aspect-locked at the time they fire.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$glide decay requires thrust:===
{{Table373|
*When set, gliding ships will maintain their current speed without decay as long as they aren't actively thrusting.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$ai can slow down when attacking big ships:===
{{Table38|
*When set, fighters attacking big ships will slow down depending on how long they've been attacking (80% speed after 5 seconds, 60% after 8 seconds, 40% after 10 seconds, and 20% after 15 seconds), how long it's been since they were last shot (full throttle if it was within the past 6 seconds), and how close they are (full throttle if the target is more than 1200 meters away).
*Off by default.
*Syntax: '''''Boolean'''''}}

===$bay arrive speed multiplier:===
{{Table373|
*Causes all AI ships arriving from fighterbays (following a fighterbay path) to gradually accelerate, instead of immediately attempting to attain maximum speed. This can be used to prevent fighters from overshooting the fighterbay paths. The initial target speed is the maximum speed multiplied by the given value, with the multiplier gradually approaching 1.0 as the distance to the end of the path decreases.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|Will be overridden by path-specific multipliers, see [[Ships.tbl#.2Barrive_speed_multiplier:]].}}
}}

===$bay depart speed multiplier:===
{{Table373|
*Same as above, except for departures into fighterbays. The initial target speed is the maximum speed, with the target speed gradually approaching maximum speed multiplied by the given value as the distance to the fighterbay decreases.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|Will be overridden by path-specific multipliers, see [[Ships.tbl#.2Bdepart_speed_multiplier:]].}}
}}

==Sample Entry==
*Retail FS2 behaviour

<pre>
#AI Profiles

$Default Profile: FS2 RETAIL

$Profile Name: FS2 RETAIL

$Player Afterburner Recharge Scale: 5, 3, 2, 1.5, 1
$Max Beam Friendly Fire Damage: 0, 5, 10, 20, 30
$Player Countermeasure Life Scale: 3, 2, 1.5, 1.25, 1
$AI Countermeasure Firing Chance: 0.2, 0.3, 0.5, 0.9, 1.1
$AI In Range Time: 2, 1.4, 0.75, 0, -1
$AI Always Links Ammo Weapons: 95, 80, 60, 40, 20
$AI Maybe Links Ammo Weapons: 90, 60, 40, 20, 10
$Primary Ammo Burst Multiplier: 0, 0, 0, 0, 0
$AI Always Links Energy Weapons: 100, 80, 60, 40, 20
$AI Maybe Links Energy Weapons: 90, 60, 40, 20, 10
$Max Missiles Locked on Player: 2, 3, 4, 7, 99
$Max Player Attackers: 2, 3, 4, 5, 99
$Max Incoming Asteroids: 3, 4, 5, 7, 10
$Player Damage Factor: 0.25, 0.5, 0.65, 0.85, 1
$Player Subsys Damage Factor: 0.2, 0.4, 0.6, 0.8, 1
$Predict Position Delay: 2, 1.5, 1.333,0.5, 0
$AI Shield Manage Delay: 5, 4, 2.5, 1.2, 0.1
$Friendly AI Fire Delay Scale: 2, 1.4, 1.25, 1.1, 1
$Hostile AI Fire Delay Scale: 4, 2.5, 1.75, 1.25, 1
$Friendly AI Secondary Fire Delay Scale: 0.4, 0.6, 0.8, 1.0, 1.2
$Hostile AI Secondary Fire Delay Scale: 1.4, 1.2, 1.0, 0.8, 0.6
$AI Turn Time Scale: 3, 2.2, 1.6, 1.3, 1
$Glide Attack Percent: 0, 0, 0, 0, 0
$Circle Strafe Percent: 0, 0, 0, 0, 0
$Glide Strafe Percent: 0, 0, 0, 0, 0
$Random Sidethrust Percent: 0, 0, 0, 0, 0
$Stalemate Time Threshold: 0, 0, 0, 0, 0
$Stalemate Distance Threshold: 0, 0, 0, 0, 0
$Player Shield Recharge Scale: 4, 2, 1.5, 1.25, 1
$Player Weapon Recharge Scale: 10, 4, 2.5, 2, 1.5
$Max Turret Target Ownage: 3, 4, 7, 12, 19
$Max Turret Player Ownage: 3, 4, 7, 12, 19
$Percentage Required For Kill Scale: 0.30, 0.30, 0.30, 0.30, 0.30
$Percentage Required For Assist Scale: 0.15, 0.15, 0.15, 0.15, 0.15
$Percentage Awarded For Capship Assist: 0.1, 0.2, 0.35, 0.5, 0.6
$Repair Penalty: 10, 20, 35, 50, 60
$Delay Before Allowing Bombs to Be Shot Down: 1.5, 1.5, 1.5, 1.5, 1.5
$Chance AI Has to Fire Missiles at Player: 0, 1, 2, 3, 4
$Max Aim Update Delay: 0, 0, 0, 0, 0
$Turret Max Aim Update Delay: 0, 0, 0, 0, 0
$Player Autoaim FOV: 0, 0, 0, 0, 0
$Detail Distance Multiplier: 0.125,0.25, 1.0, 4.0, 8.0

$big ships can attack beam turrets on untargeted ships: NO
$smart primary weapon selection: NO
$smart secondary weapon selection: NO
$smart shield management: NO
$smart afterburner management: NO
$allow rapid secondary dumbfire: NO
$huge turret weapons ignore bombs: NO
$don't insert random turret fire delay: NO
$hack improve non-homing swarm turret fire accuracy: NO
$shockwaves damage small ship subsystems: NO
$navigation subsystem governs warpout capability: NO
$ignore lower bound for minimum speed of docked ship: NO
$disable linked fire penalty: NO
$disable weapon damage scaling: NO
$use additive weapon velocity: NO
$use newtonian dampening: NO
$include beams for kills and assists: NO
$score kills based on damage caused: NO
$score assists based on damage caused: NO
$allow event and goal scoring in multiplayer: NO
$fix linked primary weapon decision bug: NO
$prevent turrets targeting too distant bombs: NO
$smart subsystem targeting for turrets: NO
$fix heat seekers homing on stealth ships bug: NO
$multi allow empty primaries: NO
$multi allow empty secondaries: NO
$allow turrets target weapons freely: NO
$use only single fov for turrets: NO
$allow vertical dodge: NO
$force beam turrets to use normal fov: NO
$fix AI class bug: NO
$turrets ignore targets radius in range checks: NO
$no extra collision avoidance vs player: NO
$perform fewer checks for death screams: NO
$advanced turret fov edge checks: NO
$require turrets to have target in fov: NO
$all ships manage shields: NO
$ai aims from ship center: NO
$allow primary link at mission start: NO
$allow beams to damage bombs: NO
$disable weapon damage scaling for player: NO
$countermeasures affect aspect seekers: NO
$ai path mode: normal
$no warp camera: NO

#End
</pre>

== References ==
# "[http://www.hard-light.net/forums/index.php/topic,50870.msg1029741.html#msg1029741 Re: New difficulty? - Feature request!]", ''Hard Light Productions Forums'', Hard Light Productions, 2007-12-15. Retrieved on [[December_27]], [[2007]].

[[Category:Tables]]

Ai.tbl

2016-09-06T20:39:10Z

AdmiralRalwood: Adding "$ai can slow down when attacking big ships:".

{{TableVersionGit|2016-08-09|7265711}}

The '''ai.tbl''' file defines the AI classed used in the game. This table is used to define each AI class with four abilities for each of the five difficulty levels.

[[Tables|List of Tables]]

==Required Elements==

===$Name:===
*Defines a name for the AI class that can be used with ships.tbl and also with FRED
*Syntax: '''String''', name of the AI class

===$Accuracy:===
*How accurately the ship fires its weapons. Value is used to scale the error in the AI aim. With repeated shots, AI aim will improve. Note that the AI is always 100% accurate when aiming for subsystems, according to Retail code.
*Value from 0.0 to 1.0
*Syntax: '''Float list''', five comma separated '''floats''', one for each difficulty, very easy, easy, moderate, hard, insane difficulty levels respectively

===$Evasion:===
*How good the ship is at evading. Value defines the frequency of AI course changes while it is evading.
*Value from 0 to 100
*Syntax: '''Float list''', five comma separated '''floats''', one for each difficulty, very easy, easy, moderate, hard, insane difficulty levels respectively

===$Courage:===
*How likely the ship is to chance danger to accomplish goals. Basically the lower the value sooner the AI will start evading when attacked and its less likely to target turrets.
*Value from 0 to 100
*Syntax: '''Float list''', five comma separated '''floats''', one for each difficulty, very easy, easy, moderate, hard, insane difficulty levels respectively

===$Patience:===
*How willing the ship is to wait for an advantage before pursuing goals. Never actually implemented - It does absolutely nothing.
{{Table3611|This value affects how quickly the AI will attempt to "break" a stalemate situation if one is detected. Only applies if ''$Stalemate Time Threshold'' and ''$Stalemate Distance Threshold'' are used. The higher the patience, the longer the ship will wait in "stalemate" before breaking. If patience is 100, the AI will never break.
}}
*Value from 0 to 100
*Syntax: '''Float list''', five comma separated '''floats''', one for each difficulty, very easy, easy, moderate, hard, insane difficulty levels respectively

==Optional Elements==
===Other AI Class Attributes===
'''IMPORTANT NOTE''': If the following attributes are NOT specified, the code uses the index of the AI class instead. Use these if you want finer-grained control over the AI classes and/or you don't want the order of the AI classes to affect their behavior. ''If these are not specified, the behaviors described will be determined by the order of the AI class relative to the others in the file. Furthermore, having a different number of AI classes than retail can result in strange behavior if these are NOT set. It is recommended that if you make heavy use of custom AI classes, you specify all of these and set $Autoscale by AI Class Index to NO.''

====$Afterburner Use Factor:====
{{Table3611|
* Affects how probably it is that the AI will use afterburners in "maybe" situations. A value of 1 means always, 2 means half the time, 3 a third of the time, etc.
* Syntax: '''Int list''', five comma separated '''integers''', one for each difficulty.
}}

====$Shockwave Evade Chances Per Second:====
{{Table3611|
* Controls how likely it is for a ship to try to start evading a shockwave. The higher the number, the more "chances per second" the ship has to evade.
* Syntax: '''Float list''', five comma separated '''float''', one for each difficulty.
}}

====$Get Away Chance:====
{{Table3611|
* How likely the AI is to use a "get away" maneuver instead of simply making evasive turns. "Get away" usually involves the AI flying straight away, usually on afterburner, and making small jinking motions (instead of large evasive turns). Higher values result in more "jousting" fights.
* Range: between 0.0 (never) and 1.0 (always)
* Syntax: '''Float list''', five comma separated '''float''', one for each difficulty.
}}

====$Secondary Range Multiplier:====
{{Table3611|
* Multiplier which affects from how far away the AI will begin firing secondary weapons. Capped by the actual maximum range of the weapon. Penalty for firing in nebula still applies above and beyond this.
* Range: between 0.0 (point blank/never fires) and 1.0 (fires from maximum range).
* Syntax: '''Float list''', five comma separated '''float''', one for each difficulty.
}}

====$Autoscale by AI Class Index:====
{{Table3611|
* If set to YES (default), a number of miscellaneous AI probabilities are affected by the order of the AI class in the file (for example, the chance to fire countermeasures). Classes near the beginning of the file are generally weaker than classes at the end. If set to NO, this flag will turn off that auto scaling behavior (so that the order of the AI class does not affect AI behavior).
* Note that even if this is set to NO, the other options above will still be controlled by AI class index (so if you want complete independence, you need to set all of the options listed in the "Other AI Class Attributes" category).
* Default: YES
* Syntax: Boolean flag (YES/NO)
}}

===AI Profiles Overrides===
{{Table3611|The following values can be inserted as overrides for their equivalent [[Ai_profiles.tbl]] values. They are all optional. If not set for an AI class, the values in AI Profiles will be used.
Syntax is the same as their AI Profiles counterparts.
* $AI Countermeasure Firing Chance:
* $AI In Range Time:
* $AI Always Links Ammo Weapons:
* $AI Maybe Links Ammo Weapons:
* $Primary Ammo Burst Multiplier:
* $AI Always Links Energy Weapons:
* $AI Maybe Links Energy Weapons:
* $Predict Position Delay:
* $AI Shield Manage Delay:
* $Friendly AI Fire Delay Scale:
* $Hostile AI Fire Delay Scale:
* $AI Turn Time Scale:
* $Glide Attack Percent:
* $Circle Strafe Percent:
* $Glide Strafe Percent:
* $Stalemate Time Threshold:
* $Stalemate Distance Threshold:
* $Chance AI Has to Fire Missiles at Player:
* $Max Aim Update Delay:
* $Turret Max Aim Update Delay:
}}

===AI Profiles Flag Overrides===
{{Table3611|The following flags can be inserted to override their equivalent [[Ai_profiles.tbl]] flag values. They are all optional. If not set for an AI Class, the AI Profiles value will be used.
* $big ships can attack beam turrets on untargeted ships:
* $smart primary weapon selection:
* $smart secondary weapon selection:
* $smart shield management:
* $smart afterburner management:
* $allow rapid secondary dumbfire:
* $huge turret weapons ignore bombs:
* $don't insert random turret fire delay:
* $prevent turrets targeting too distant bombs:
* $smart subsystem targeting for turrets:
* $allow turrets target weapons freely:
* $allow vertical dodge:
* $No extra collision avoidance vs player:
}}
{{Table3613|
* $all ships manage shields:
}}
{{Table38|
* $ai can slow down when attacking big ships:
}}

==Sample Entry==
#AI Classes
$Name: Captain
$accuracy: 0.5 0.55 0.6 0.65 0.7
$evasion: 10, 20, 30, 40, 50
$courage: 10, 20, 30, 40, 50
$patience: 10, 20, 30, 40, 50
#End

{{Table3611| (Sample entry using some optional elements)
#AI Classes
$Name: Captain
$accuracy: 0.5 0.55 0.6 0.65 0.7
$evasion: 10, 20, 30, 40, 50
$courage: 10, 20, 30, 40, 50
$patience: 10, 20, 30, 40, 50
$Get Away Chance: 0.40, 0.45, 0.50, 0.55, 0.6
$Autoscale by AI Class Index: NO
$AI In Range Time: 2, 1.6, 1.2, 0.8, 0.4
$Primary Ammo Burst Multiplier: 0.6, 0.65, 0.7, 0.75, 0.8
$Glide Attack Percent: 30, 40, 50, 60, 70
$allow rapid secondary dumbfire: NO
$allow vertical dodge: YES
#End
}}
[[Category:Tables]]

Ai profiles.tbl

2016-09-06T20:39:08Z

AdmiralRalwood: Adding "$ai can slow down when attacking big ships:".

{{SCP_table}}

{{TableVersionGit|2016-08-09|7265711}}

The '''ai_profiles.tbl''' allows the creation and management of different patterns of AI behavior, called profiles. Profiles consist of various statistics and flags that provide some control over AI behavior. All options within a profile are optional; if an option is not specified it will follow the original FreeSpace 2 retail behavior. Different missions can specify different profiles.

The default ai_profiles.tbl is hardcoded into the FSO executable, and defines the "FS2 RETAIL" AI profile. It's usually recommended not to modify this profile, but to create a new AI profile in a modular table instead, which will then inherit its defaults from the FS2 RETAIL profile.

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm

[[Tables|List of Tables]]

==General Format==
'''#AI Profiles'''

'''$Default Profile:''' ''a profile name''

''Up to 9 different AI profiles''

'''#End'''

==#AI Profiles==
*Indicates to the parser that this is an ai_profiles table file.

===$Default Profile:===
*Defines the profile that each mission will use if no profile is specified in FRED. In addition, this profile will be selected automatically in FRED when you create a new mission. If this line is not specified, the default profile will be the FreeSpace 2 retail behavior.

===$Profile Name:===
*The name of the profile, naturally.

----

The following entries accept '''float list''' of five comma-separated values. One value for each of the difficulty levels (Very Easy, Easy, Medium, Hard, Insane).

===$Player Afterburner Recharge Scale:===
{{Table3610|
*Sets the speed of afterburner recharge
*Syntax: '''Float list'''
**Default: 5, 3, 2, 1.5, 1}}

===$Max Beam Friendly Fire Damage:===
{{Table3610|
*Defines the maximum damage inflicted by friendly beam fire
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Player Countermeasure Life Scale:===
{{Table3610|
*Sets the factor applied to player launched countermeasure lifetime
*Syntax: '''Float list'''
**Default: 3, 2, 1.5, 1.25, 1}}

===$AI Countermeasure Firing Chance:===
{{Table3610|
*Defines the chance a countermeasure will be fired by an AI-controlled ship (this is scaled by ai_class)
*Syntax: '''Float list'''
**Default: 0.2, 0.3, 0.5, 0.9, 1.1}}

===$AI In Range Time:===
{{Table3610|
*The delay (in seconds) for the AI to fire its weapons after getting in range.
*Syntax: '''Float list'''
**Default: 2, 1.4, 0.75, 0, -1}}

===$AI Always Links Ammo Weapons:===
{{Table3610|
*AI ships will link ballistic primaries if ammo levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 95, 80, 60, 40, 20}}

===$AI Maybe Links Ammo Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Ammo Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Primary Ammo Burst Multiplier:===
{{Table3611|
*Allows the AI to fire primary weapons in bursts. How long the bursts are (and how much time between them) is a function of ammo remaining, distance to target, angle to target, and this multiplier. A value of 0 turns this feature off (AI fires normally, without bursts). A value < 1 will make for shorter bursts with larger gaps, and a value > 1 will give longer bursts with shorter gaps.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$AI Always Links Energy Weapons:===
{{Table3610|
*AI ships will link energy primaries if energy levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 100, 80, 60, 40, 20}}

===$AI Maybe Links Energy Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Energy Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Max Missiles Locked on Player:===
{{Table3610|
*Defines the maximum number of missiles allowed to be homing in on a player at any given time
*Note: Single-player only, no restriction in multiplayer
*Syntax: '''Float list'''
**Default: 2, 3, 4, 7, 99}}

===$Max Player Attackers:===
{{Table3610|
*Sets the maximum number of ships allowed to be attacking the player at any given time
*Syntax: '''Float list'''
**Default: 2, 3, 4, 5, 99}}

===$Max Incoming Asteroids:===
{{Table3610|
*Sets the maximum number of active (i.e. "thrown") asteroids that can be heading toward a friendly ship at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 5, 7, 10}}

===$Player Damage Factor: or $AI Damage Reduction to Player Hull:===
{{Table3610|
*Defines the factor applied to damage suffered by the player
*Syntax: '''Float list'''
**Default: 0.25, 0.5, 0.65, 0.85, 1}}

===$Player Subsys Damage Factor: or $AI Damage Reduction to Player Subsys:===
{{Table3610|
*Sets the factor applied to subsystem damage suffered by the player. This is in addition to the '''$Player Damage Factor:'''
*Syntax: '''Float list'''
**Default: 0.2, 0.4, 0.6, 0.8, 1}}

===$Predict Position Delay:===
{{Table3610|
*Sets the measure of time (in F1_0 units) after which the AI will recalculate the position of its target.
*It does not apply to the AI's aim, it only applies to things like avoiding collisions and maneuvering at close range. Generally, anything other than a 0 just allows the AI to do monumentally stupid things like try to turn to avoid ramming where it thought you were 2 seconds ago.
*Syntax: '''Float list'''
**Default: 2, 1.5, 1.333, 0.5, 0}}

===$AI Shield Manage Delay:===
{{Table3610|
*Also '''$AI Shield Manage Delays:'''
*Sets the time in seconds between each instance of an AI ship managing its shields
*Syntax: '''Float list'''
**Default: 5, 4, 2.5, 1.2, 0.1}}

===$Friendly AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 2, 1.4, 1.25, 1.1, 1}}

===$Hostile AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 4, 2.5, 1.75, 1.25, 1}}

===$Friendly AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 0.4, 0.6, 0.8, 1.0, 1.2}}

===$Hostile AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 1.4, 1.2, 1.0, 0.8, 0.6}}

===$AI Turn Time Scale:===
{{Table3610|
*Defines the factor applied to time it takes for enemy ships to turn. A value of 1.0 means the ship turns at normal speed, 2.0 means half speed (takes twice as long), etc. Note that this value ONLY affects ships hostile to the player (always 1.0 for friendly ships).
*Syntax: '''Float list'''
**Default: 3, 2.2, 1.6, 1.3, 1}}

===$Glide Attack Percent:===
{{Table3611|
*How often the AI will use the "glide attack" move when it has the opportunity. Glide attack means using glide to maintain course while aiming and firing at the current target. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Circle Strafe Percent:===
{{Table3611|
*How often the AI will use the "circle strafe" move when it has the opportunity. Circle strafe means that the ship will attempt "Descent-like" combat, trying to maintain distance while circling around the target using sidethrusters. Ships will only attempt this when sidethrust top speed is at least 2/3 of target's current velocity.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Glide Strafe Percent:===
{{Table3611|
*How often the AI will use the "glide strafe" move when it has the opportunity. Glide strafe means using glide to attack capships by flying past and shooting at them. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Random Sidethrust Percent:===
{{Table3611|
*Percentage of the time where AI ships will randomly sidethrust in a dogfight.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Time Threshold:===
{{Table3611|
*The minimum amount of time required for the AI to detect a "stalemate" situation. If a ship and its target have been within a certain distance of each other (defined by ''$Stalemate Distance Threshold'') for this amount of time without either of them scoring a hit on the other, the AI will do something to break the stalemate. Only applies to small ships. If this value is 0 or less, no stalemate detection is performed.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Distance Threshold:===
{{Table3611|
*The maximum distance that an AI ship must remain from its target for a "stalemate" to occur (see ''$Stalemate Time Threshold'').
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Shield Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's shields recharge
*Syntax: '''Float list'''
**Default: 4, 2, 1.5, 1.25, 1}}

===$Player Weapon Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's weapons recharge
*Syntax: '''Float list'''
**Default: 10, 4, 2.5, 2, 1.5}}

===$Max Turret Target Ownage:===
{{Table3610|
*Sets the maximum number of turrets on a particular ship allowed to be attacking the same target at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 7, 12, 19}}

===$Max Turret Player Ownage:===
{{Table3610|
*Sets the maximum number of turrets on a particular ship allowed to be attacking the player at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 7, 12, 19}}

===$Percentage Required For Kill Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.30, 0.30, 0.30, 0.30, 0.30}}

===$Percentage Required For Assist Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded an assist (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.15, 0.15, 0.15, 0.15, 0.15}}

===$Percentage Awarded For Capship Assist:===
{{Table3610|
*In TvT and Coop missions all teammates will be granted this percentage of the capships score when someone scores a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.5, 0.5, 0.5, 0.5, 0.5}}

===$Repair Penalty:===
{{Table3611|
*The amount to subtract from the player's score if they are repaired by a support ship
*Syntax: '''Integer list'''
**Default: 10, 20, 35, 50, 60}}

===$Delay Before Allowing Bombs to Be Shot Down:===
{{Table3611|
*Time after bombs are fired during which the bombs are invulnerable to weapon hits
*Syntax: '''Float list'''
**Default: 1.5, 1.5, 1.5, 1.5, 1.5}}

===$Chance AI Has to Fire Missiles at Player:===
{{Table3611|
*Chance - expressed in ('''value''' + 1) / 7 - of each AI turret within current 10 second segment to be allowed to shoot missiles at player ship.
*Syntax: '''Float list'''
**Default: 0, 1, 2, 3, 4}}

===$Max Aim Update Delay:===
{{Table3611|
*Maximum amount of delay allowed before the AI will update its aim. Until the next update, the AI will project the target forward based on last checked position and velocity. Applies to small ships vs small ships (dogfights). The actual delay is randomly selected between 0 and the maximum (so setting a value of 2 will result in an average of 1 second delay).
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Turret Max Aim Update Delay:===
{{Table3611|
*As $Max Aim Update Delay, but affecting turrets instead
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Autoaim FOV:===
{{Table3613|
*Gives the player autoaim within the specified number of degrees from the target (FOV).
*Unlike the ships.tbl settings for autoaim, this only affects the player (and, of course, only if there is a nonzero value for the difficulty level.)
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Detail Distance Multiplier:===
{{Table3613|
*Affects how the "model detail level" setting in Options switches between LOD levels.
*This number acts as a multiplier on the LOD distances specified in ships.tbl.
*NOTE THAT THIS IS PER DETAIL LEVEL, NOT PER DIFFICULTY LEVEL.
*Syntax: '''Float list'''
**Default: 0.125, 0.25, 1.0, 4.0, 8.0}}
----

The following entries are boolean flags. They can be set to ''YES'' or ''NO'', ''TRUE'' or ''FALSE'', ''OUI'' or ''NON'', ''HIja′'' or ''ghobe′'', etc. The default is ''NO''.

===$big ships can attack beam turrets on untargeted ships:===
{{Table3610|
*If set, big ships can attack a beam turret that's firing on them from a ship that they don't currently have targeted.}}

===$smart primary weapon selection:===
{{Table3610|
*If set, enables the new primary weapon selection method}}

===$smart secondary weapon selection:===
{{Table3610|
*If set, enables the new secondary weapon selection method (including proper use of bomber+ missiles)}}

===$smart shield management:===
{{Table3610|
*If set, shields will devote all their charging energy to the weakest quadrant(s) and not waste energy on fully-charged quadrants (previously was -smart_shields on the command line)}}

===$smart afterburner management:===
{{Table3610|
*If set, the AI will properly use brief pulses of afterburner power instead of afterburning until fuel is exhausted}}

===$allow rapid secondary dumbfire:===
{{Table3610|
*If set, allows an AI ship to switch to rapid fire for dumbfire missiles}}

===$huge turret weapons ignore bombs:===
{{Table3610|
*If set, causes huge turret weapons (including anti-capship beams) to not target bombs}}

===$don't insert random turret fire delay:===
{{Table3610|
*If set, removes the random turret fire delay (from .1 to .9 seconds) inserted in addition to AI Fire Delay Scale}}

===$hack improve non-homing swarm turret fire accuracy:===
{{Table3610|
*If set, triggers a hack to improves the accuracy of non-homing swarm missiles by firing them along the turret's last fire direction rather than the direction it currently faces
*Also disables swarm weapons ability to fire only on the 'turrets barrel line'.}}

===$shockwaves damage small ship subsystems:===
{{Table3610|
*If set, shockwaves will cause damage to small ship subsystems (like in FS1)}}

===$navigation subsystem governs warpout capability:===
{{Table3610|
*If set, ships will not be able to warp out if their navigation subsystem is destroyed or low in strength}}

===$ignore lower bound for minimum speed of docked ship:===
{{Table3610|
*If set, there will be no lower bound for the speed at which docked ships move (like in FS1).
*When a ship is towing another ship or ships, the towing ship will be slowed down to a degree depending on the total mass of all docked ships. In FS1, the ships could slow down to an arbitrarily slow speed, even a fraction of a m/s above zero. In FS2, there is a lower bound on this behavior so that all ships are guaranteed to move at a minimum docked speed. When set, this flag removes the lower bound and restores FS1 behavior.}}

===$disable linked fire penalty:===
{{Table3610|
*If set, there will be no penalty for linking primaries. Normally, the rate of fire is *1 for a single bank, *0.66 for two banks and *0.5 for three banks (the fire delay is increased according to the formula 1+([nb of banks]-1)*0.5 ).}}

===$disable weapon damage scaling:===
{{Table3610|
*If set, weapons will do the same damage to a ship regardless of "big damage", "supercap", etc. ship types.}}

===$use additive weapon velocity:===
{{Table3610|
*If set, weapons will inherit their firing ship's velocity. A ship traveling quickly will fire weapons faster than a ship traveling slowly. This also improves the accuracy of weapons fired while gliding.}}

===$use newtonian dampening:===
{{Table3610|
*Newtonian Dampening changes turning and acceleration behavior. By default, there's quite a bit of slide when you turn, and when combined with high damp values (such as in BtRL), you can actually push your speed up beyond the max. Newtonian Dampening is the more realistic turns, where too much turning will lower your speed. Forward momentum is also affected. Backslash can explain it in more detail. [http://www.hard-light.net/forums/index.php/topic,50870.msg1029741.html#msg1029741] }}

===$include beams for kills and assists:===
{{Table3610|
*If set, beam damage is counted when calculating kills and assists.}}

===$score kills based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the killer inflicted on the dead ship.}}

===$score assists based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the player gaining the assist inflicted on the dead ship.}}

===$allow event and goal scoring in multiplayer:===
{{Table3610|
*If set, players (rather than just their team) can gain score from events in multiplayer.}}

===$fix linked primary weapon decision bug:===
{{Table3610|
*If set, the AI will properly link primaries according to specified percentages of energy levels instead of retail behavior where it mistakenly linked according to absolute energy levels.}}

===$prevent turrets targeting too distant bombs:===
{{Table3610|
*If set, prevents turrets from targeting bombs beyond maximum range of the weapons of the turret.}}

===$smart subsystem targeting for turrets:===
{{Table3610|
*If set, prevents turrets from trying to target subsystems beyond their fov limits, also keeps the turret subsystem targeting preference order intact regardless of the angle to the target.}}

===$fix heat seekers homing on stealth ships bug:===
{{Table3610|
*If set, heat-seeking missiles will not home in on stealth ships (this mirrors the established behavior where heat-seeking missiles do not home in on ships that are hidden from sensors).}}

===$multi allow empty primaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without primaries.}}

===$multi allow empty secondaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without secondaries.}}

===$allow turrets target weapons freely:===
{{Table3611|
*If set, allows turrets to target any weapons instead of just targeting bombs, to be used in conjunction with target priorities setup.}}

===$use only single fov for turrets:===
{{Table3611|
*If set, allows turrets to fire outside some hardcoded FOV set for certain missile types limits, and rely only on the user defined FOV.}}

===$allow vertical dodge:===
{{Table3611|
*If set, allows ships to dodge weapons fire vertically as well as horizontally.}}

===$force beam turrets to use normal fov:===
{{Table3611|
*If set makes beam turrets use same FOV rules as other weapons do. Prevents beam from a turret from following the target beyond the turret's FOV}}

===$fix AI class bug:===
{{Table3611|
*Fixes a bug where AI class attributes are not set properly on ships if the AI class is set in the mission to something other than the default for the ship type. Set this to YES if you want attributes in [[Ai.tbl]] to mean anything at all.}}

===$turrets ignore targets radius in range checks:===
{{Table3611|
*TBD.}}

===$no extra collision avoidance vs player:===
{{Table3611|
*Disables the extra collision avoidance that AI normally uses against the player. Makes the AI more aggressive vs the player at close range (same treatment as vs other AI), although ship-ship collisions are slightly more likely.}}

===$perform fewer checks for death screams:===
{{Table3614|
*If set, the game will check if the dying ship is a player's wingman, before making it give a death scream.
Prior to revision 9119, this was "$perform fewer checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*TBD.}}

===$require turrets to have target in fov:===
{{Table3614|
*TBD.}}

===$all ships manage shields:===
{{Table3613|
*Allows AI to manage shields on big ships}}

===$ai aims from ship center:===
{{Table3613|
*AI aims weapons using the center of the ship instead of the first gunpoint. If a convergence offset is specified for this ship in ships.tbl, AI aims using that as a reference point.}}

===$allow primary link at mission start:===
{{Table370|
*When set, no ships will link primaries for the first 30 seconds of a mission. In addition, ships will randomly not link for the first two minutes of a mission. Set this to NO to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
*When set, beam weapons will be able to effectively intercept bombs. In addition, bombs flying through a beam path will get damaged and destroyed. Default: NO.}}

===$disable weapon damage scaling for player:===
{{Table3613|
*When set, Player weapon damage will no longer be scaled down when firing a non-huge primary against a ship with the "big damage" flag. Use with caution, as this may severely impact mission balance.}}

===$countermeasures affect aspect seekers:===
{{Table3613|
*TBD.}}

===$ai guards specific ship in wing:===
{{Table3615|
*If ordered to guard a ship in a wing (of which it is not a member), the AI will guard that specific ship instead of the entire wing (resulting in guarding the wing leader).}}

===$ai path mode:===
{{Table3613|
*Possible options are "normal" and "alt1". The alt1 mode differs from the normal behaviour in the following ways:
**1. No path shortcutting. Normal pathing AI will skip forward along a path to the furthest point it can reach. This is sometimes desirable, but makes it a lot harder to predict how the AI is going to behave at various points along a path. Turning this off also allows us to force the AI to straighten out, by giving it several waypoints in a more-or-less straight line. This is useful for such things as lining up a landing.
**2. No sliding when following paths. Docking still works, but there is some code that causes the AI to go full retard if it just misses a point: it turns towards the point in big, looping circles. This is apparently caused by passing a slide_vec value into ai_turn_towards_vector, which doesn't even seem to do what you'd expect it to do. Passing a null value instead turns off the stupid. (The behavior is fixed in alt1).
**3. Momentum taken into account when following paths. Path points will trigger sooner, proportional to the ship's speed and momentum. This prevents the AI from massively overshooting a waypoint, especially with high-damp ships.
**4. AI tries to follow the line between waypoints. Instead of just pointing at the next waypoint, the AI will fly a bit towards the line. This helps keep the AI actually on the path it claims to be following. See picture:[[Image:Altpaths.png]]
Blue is what happens with regular pathing. Red is the modified pathing: as you can see, it actively moves back towards the line.
**5. AI will respect "cap-waypoint-speed" when following paths (such as when docking or departing via bay).}}

===$default weapon select effect:===
{{Table3613|
*This specifies which effect to use for weapon select animations when no .ani can be found, or the -weapon_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS1" and "off"}}
{{Table3615|
*This flag has been moved to [[Game_settings.tbl]]}}

===$default ship select effect:===
{{Table3613|
*This specifies which effect to use for ship select animations when no .ani can be found, or the -ship_choice_3d commandline flag is active. This will default to the FS2 effect.
*Possible options are "FS1" and "off"}}
{{Table3615|
*This flag has been moved to [[Game_settings.tbl]]}}

===$no warp camera:===
{{Table3615|
*When set, prevents the view from switching to the external camera when the player warps out.
*Note: this flag is deprecated and may get moved to another table without further notice.}}

===$fix ai path order bug:===
{{Table3615|
*When set, ship will follow its own waypoint path unless the wingleader has the same waypoint path and order.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$aspect bomb invulnerability fix:===
{{Table373|
*When set, aspect bombs don't have their invulnerability time modified by whether or not they're aspect-locked at the time they fire.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$glide decay requires thrust:===
{{Table373|
*When set, gliding ships will maintain their current speed without decay as long as they aren't actively thrusting.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$ai can slow down when attacking big ships:===
{{Table38|
*When set, fighters attacking big ships will slow down depending on how long they've been attacking (80% speed after 5 seconds, 60% after 8 seconds, 40% after 10 seconds, and 20% after 15 seconds), how long it's been since they were last shot (full throttle if it was within the past 6 seconds), and how close they are (full throttle if the target is more than 1200 meters away).
*Off by default.
*Syntax: '''''Boolean'''''}}

===$bay arrive speed multiplier:===
{{Table373|
*Causes all AI ships arriving from fighterbays (following a fighterbay path) to gradually accelerate, instead of immediately attempting to attain maximum speed. This can be used to prevent fighters from overshooting the fighterbay paths. The initial target speed is the maximum speed multiplied by the given value, with the multiplier gradually approaching 1.0 as the distance to the end of the path decreases.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|Will be overridden by path-specific multipliers, see [[Ships.tbl#.2Barrive_speed_multiplier:]].}}
}}

===$bay depart speed multiplier:===
{{Table373|
*Same as above, except for departures into fighterbays. The initial target speed is the maximum speed, with the target speed gradually approaching maximum speed multiplied by the given value as the distance to the fighterbay decreases.
**Syntax: '''''Float''''' (defaults to 1.0)
{{Note|Will be overridden by path-specific multipliers, see [[Ships.tbl#.2Bdepart_speed_multiplier:]].}}
}}

==Sample Entry==
*Retail FS2 behaviour

<pre>
#AI Profiles

$Default Profile: FS2 RETAIL

$Profile Name: FS2 RETAIL

$Player Afterburner Recharge Scale: 5, 3, 2, 1.5, 1
$Max Beam Friendly Fire Damage: 0, 5, 10, 20, 30
$Player Countermeasure Life Scale: 3, 2, 1.5, 1.25, 1
$AI Countermeasure Firing Chance: 0.2, 0.3, 0.5, 0.9, 1.1
$AI In Range Time: 2, 1.4, 0.75, 0, -1
$AI Always Links Ammo Weapons: 95, 80, 60, 40, 20
$AI Maybe Links Ammo Weapons: 90, 60, 40, 20, 10
$Primary Ammo Burst Multiplier: 0, 0, 0, 0, 0
$AI Always Links Energy Weapons: 100, 80, 60, 40, 20
$AI Maybe Links Energy Weapons: 90, 60, 40, 20, 10
$Max Missiles Locked on Player: 2, 3, 4, 7, 99
$Max Player Attackers: 2, 3, 4, 5, 99
$Max Incoming Asteroids: 3, 4, 5, 7, 10
$Player Damage Factor: 0.25, 0.5, 0.65, 0.85, 1
$Player Subsys Damage Factor: 0.2, 0.4, 0.6, 0.8, 1
$Predict Position Delay: 2, 1.5, 1.333,0.5, 0
$AI Shield Manage Delay: 5, 4, 2.5, 1.2, 0.1
$Friendly AI Fire Delay Scale: 2, 1.4, 1.25, 1.1, 1
$Hostile AI Fire Delay Scale: 4, 2.5, 1.75, 1.25, 1
$Friendly AI Secondary Fire Delay Scale: 0.4, 0.6, 0.8, 1.0, 1.2
$Hostile AI Secondary Fire Delay Scale: 1.4, 1.2, 1.0, 0.8, 0.6
$AI Turn Time Scale: 3, 2.2, 1.6, 1.3, 1
$Glide Attack Percent: 0, 0, 0, 0, 0
$Circle Strafe Percent: 0, 0, 0, 0, 0
$Glide Strafe Percent: 0, 0, 0, 0, 0
$Random Sidethrust Percent: 0, 0, 0, 0, 0
$Stalemate Time Threshold: 0, 0, 0, 0, 0
$Stalemate Distance Threshold: 0, 0, 0, 0, 0
$Player Shield Recharge Scale: 4, 2, 1.5, 1.25, 1
$Player Weapon Recharge Scale: 10, 4, 2.5, 2, 1.5
$Max Turret Target Ownage: 3, 4, 7, 12, 19
$Max Turret Player Ownage: 3, 4, 7, 12, 19
$Percentage Required For Kill Scale: 0.30, 0.30, 0.30, 0.30, 0.30
$Percentage Required For Assist Scale: 0.15, 0.15, 0.15, 0.15, 0.15
$Percentage Awarded For Capship Assist: 0.1, 0.2, 0.35, 0.5, 0.6
$Repair Penalty: 10, 20, 35, 50, 60
$Delay Before Allowing Bombs to Be Shot Down: 1.5, 1.5, 1.5, 1.5, 1.5
$Chance AI Has to Fire Missiles at Player: 0, 1, 2, 3, 4
$Max Aim Update Delay: 0, 0, 0, 0, 0
$Turret Max Aim Update Delay: 0, 0, 0, 0, 0
$Player Autoaim FOV: 0, 0, 0, 0, 0
$Detail Distance Multiplier: 0.125,0.25, 1.0, 4.0, 8.0

$big ships can attack beam turrets on untargeted ships: NO
$smart primary weapon selection: NO
$smart secondary weapon selection: NO
$smart shield management: NO
$smart afterburner management: NO
$allow rapid secondary dumbfire: NO
$huge turret weapons ignore bombs: NO
$don't insert random turret fire delay: NO
$hack improve non-homing swarm turret fire accuracy: NO
$shockwaves damage small ship subsystems: NO
$navigation subsystem governs warpout capability: NO
$ignore lower bound for minimum speed of docked ship: NO
$disable linked fire penalty: NO
$disable weapon damage scaling: NO
$use additive weapon velocity: NO
$use newtonian dampening: NO
$include beams for kills and assists: NO
$score kills based on damage caused: NO
$score assists based on damage caused: NO
$allow event and goal scoring in multiplayer: NO
$fix linked primary weapon decision bug: NO
$prevent turrets targeting too distant bombs: NO
$smart subsystem targeting for turrets: NO
$fix heat seekers homing on stealth ships bug: NO
$multi allow empty primaries: NO
$multi allow empty secondaries: NO
$allow turrets target weapons freely: NO
$use only single fov for turrets: NO
$allow vertical dodge: NO
$force beam turrets to use normal fov: NO
$fix AI class bug: NO
$turrets ignore targets radius in range checks: NO
$no extra collision avoidance vs player: NO
$perform fewer checks for death screams: NO
$advanced turret fov edge checks: NO
$require turrets to have target in fov: NO
$all ships manage shields: NO
$ai aims from ship center: NO
$allow primary link at mission start: NO
$allow beams to damage bombs: NO
$disable weapon damage scaling for player: NO
$countermeasures affect aspect seekers: NO
$ai path mode: normal
$no warp camera: NO

#End
</pre>

== References ==
# "[http://www.hard-light.net/forums/index.php/topic,50870.msg1029741.html#msg1029741 Re: New difficulty? - Feature request!]", ''Hard Light Productions Forums'', Hard Light Productions, 2007-12-15. Retrieved on [[December_27]], [[2007]].

[[Category:Tables]]

Command-Line Reference

2016-09-01T02:25:04Z

AdmiralRalwood: /* -shadow_quality */ -shadow_quality can now be used by itself.

{{TableVersionGit|2016-28-07|b40631e}}

Command-Line Flags (also called Command-Line Parameters) are optional flags passed to the FSO executable, and generally enables one or more features added to the FS2 Open engine. These flags are accessed conveniently through an [[FSO Launcher]]. To have FSO list all available flags, use any one of the following: [[Command-Line_Reference#-help|-help]], [[Command-Line_Reference#-help|--help]], [[Command-Line_Reference#-help|-h]], or [[Command-Line_Reference#-help|-?]].



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

Only polygons mapped with textures for which a shinemap exists will receive specular mapping; no attempt is made to generate spec maps where they do not exist. Specular maps are specified with the base map name plus "-shine" (i.e. TCov3A-shine.pcx).
{{Table3615|
*This feature is on by default, use launcher option Disable Specular or if necessary to manually disable enter the flag -nospec}}

====-env====
'''"Enable Environment maps"'''

It only works if [[Command-Line_Reference#-spec|-spec]] is also set. Environment mapping intensity will be determined from the shine map too (see [[Texturing]] for more info). [[Installing FreeSpace 2 Open#Video setup|See Video setup.]]
{{Table3615|
*This feature is on by default, use launcher option Disable Environment Maps or if necessary to manually disable enter the flag -noenv }}

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

Only polygons mapped with textures for which a glowmap exists will be glowmapped. Glow maps are specified with the base map name plus "-glow" (i.e. TCov4A-glow.pcx)
{{Table3615|
*This feature is on by default, use launcher option Disable Glow Maps or if necessary to manually disable enter the flag -noglow }}

====-nomotiondebris====
'''"Disable motion debris"'''

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

Disables fullscreen scaling of video clips.

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

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

Normal maps require GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary normal maps (the same name of the base map plus "-normal"). DXT5_NM DDS format is needed. (Technical note: DXT5 will work, since only the GREEN and ALPHA channels are read by the current shader system. One direction of lines goes into the GREEN channel, the other direction goes into the ALPHA channel. RED and BLUE can be either base gray (#808080) or black. Usual practice is after creating the DXT5_NM, copy the RED channel to the ALPHA channel, black out the RED and BLUE an then save as either a DXT5 or u8888 (uncompressed) DDS file.)
{{Table3615|
*This feature is on by default, use launcher option Disable Normal Maps or if necessary to manually disable enter the flag -nonormal }}

====-height====
Enables height maps (parallax mapping). It only works if [[Command-Line_Reference#-normal|-normal]] is also set. It also needs GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary height maps (with the same name than base map plus "-height").
{{Table3615|
*This feature is on by default. To manually disable, enter the flag -noheight}}

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

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

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

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

This only has any effect when both a 2d and 3d shockwave effect are present, otherwise the only available effect is used (2d shockwave is defined by effects/shockwave01.eff or .ani, and 3d shockwave by models/shockwave.pof)

Note that 3d shockwaves are usually flat discs, that FSO scales up. The animated 2d billboards used by 2d shockwaves with the addition of [[Command-Line Reference#-soft_particles|soft particles]], may look better when intersecting with models (which shockwaves often do). Use at your discretion.

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

Enables the FXAA postprocessing stage. Further information can be found here: http://www.hard-light.net/forums/index.php?topic=76145.0

====-nolightshafts====
'''"Disable lightshafts"'''

Disables Lightshafts even if a mission designer enables them via SEXP in a mission. This was previously documented as -flightshaftsoff but appears to have been changed to -nolightshafts for consistency before -flightshaftsoff was ever used in a released build.

====-enable_shadows====
{{table373|
'''"Enable shadows"'''

Enables shadows where supported by the OpenGL version provided by the user's GPU. -shadow_quality can be used to control the quality level.
{{note|Currently doesn't support shadows for cockpits and show ship.}}
}}

====-shadow_quality====
{{table373|
'''"Set shadows quality"'''

Valid ranges are 0 to 2 with 2 being the default.

* 0 disables shadows (so there's no point in setting it!)
* 1 uses 512x512 shadow maps (lower quality)
* 2 uses 1024x1024 shadow maps (higher quality)

Currently this requires -enable_shadows to be set, or it has no effect.
}}
{{table38|No longer requires -enable_shadows to be set.}}

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

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

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

====-no_fps_capping====
'''"Don't limit frames-per-second"'''

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

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

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

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

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

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

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

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

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

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

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

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

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

Uses ship models in ship selection window. It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their ships. In this situation, and if it is not used, the game will probably crash to desktop in the ship selection window.

====-weapon_choice_3d====
'''"Use Models for Weapon Selection"'''

Uses weapon models in weapon loadout window for secondary weapons (missiles and bombs). It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their secondary weapons. In this situation, and if it is not used, the game will probably crash to desktop in the weapon loadout window.

====-3dwarp====
'''"Enable 3D Warp"'''

Use full geometry for the subspace warp effect.

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

Enable a flash at warp in and warp out.

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

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

====-stretch_menu====
'''"Stretch interface to fill screen"'''

Scales the interface to fill the screen without preserving the aspect ratio. Omit this to keep the aspect ratio, adding black bars where appropriate.

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

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

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

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

===Launcher===
====-portable_mode====
'''"Store config in portable location"'''

Uses the root directory of FSO for storing pilot and config files. The current launcher does not have proper support for this yet so you need to manually copy the fs2_open.ini from the original config directory to your FreeSpace Root directory.

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

Creates a standalone multi-player server.

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

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

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

====-closed====
'''"Start Hosted Server as Closed"'''

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

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

====-restricted====
'''"Host Confirms Join requests"'''

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

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

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

====-clientdamage====
{{Note| This feature is not available in current builds.}}

====-mpnoreturn====
'''"Disables Flight Deck option"'''

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

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

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

Disables the gamma settings in the options screen.

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

Disables all video playback.

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

Disables some parsing warnings and makes other parse errors non-fatal. Do not rely on this when creating new tables. The errors are there for a reason.

====-parse_cmdline_only====
'''"Parse Command Line Only"'''

Parse only the application command line settings, and ignore any that may have been set in the on-disk data/cmdline_fso.cfg or per-user cmdline_fso.cfg (on Linux/Mac)

====-safeloading====
Loads missions the old way. Typically safer, but slower.
{{Note| This parameter was removed as of the July 5, 2011 nightly build.}}

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

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

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

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

Disables IBX caching of model geometry data. This will dramatically increase load times, but will help troubleshoot a model if one is working incorrectly.

====-loadallweps====
'''"Load all weapons, even those not used"'''

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

====-disable_pbo====
'''"Disable OpenGL Pixel Buffer Objects"'''

Disables the use of Pixel Buffer Objects (PBO) which may cause certain OpenGL operations to perform slower. Note PBO's were only used at three places in FSO anyway so it's *probably* not going to have a noticeable effect.

May be required to workaround issues in certain versions of Linux's Mesa drivers for Intel integrated graphics cards where crashes occur in the mainhall (i.e. whenever a popup occurs). Distros that seem to have this problem presently include Ubuntu 13.10 and openSUSE 13.1.
{{Table371|
*This feature is present to work around a bug in Linux's Mesa drivers for Intel integrated graphics cards}}

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

Disables the use of GLSL rendering (OpenGL shaders). The game will revert to legacy fixed render pipeline. Please note that Normal and Height map effects will be unavailable.

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

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

[http://scp.indiegames.us/mantis/view.php?id=1669 Mantis #1669] is what led to this flag's creation.

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

====-disable_di_mouse====
'''"Disables the DirectInput mouse code for FSO on windows."'''

'''Windows Only''' Can make mouse movement smoother on certain machines.

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

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

====-use_gldrawelements====
'''"Use glDrawElements instead of glDrawRangeElements"'''

Introduced as a means of switching to the slower OpenGL call glDrawElements, instead of glDrawRangeElements.
{{Table3614|
*This feature may resolve certain rendering problems where parts of models are not drawn on Linux drivers}}

====-keyboard_layout====
'''"Manually sets a keyboard layout"'''

A commandline parameter to set the keyboard layout as a string parameter.
{{Table3614|
*Currently the only valid string is "qwertz" (German) but French azerty may be added in future.}}

====-old_collision====
'''"Use old collision detection system"'''

Uses the old collision code instead of Swifty's new collision code introduced in the 'go_even_faster' project.

====-gl_finish====
'''"Fix input lag on AMD+Linux"'''
{{Table371|
This option adds a "glFinish()" call just prior to swapping buffers. It works around an issue with "recent" (HD 6000 & newer?) AMD cards using proprietary drivers on Linux. Be warned that enabling this may reduce framerate.
}}

Refer to [http://www.hard-light.net/forums/index.php?topic=88102.0 this thread] and [https://github.com/ValveSoftware/Source-1-Games/issues/765 Valve's bugtracker] for more details).

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

Enables ingame joining in multiplayer. FIXME: Host option?

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

Windows-only. Enables voice-recognition for wingmen commands. Must be specifically compiled into a build in order for it to be available; 3.6.10 final includes the feature. See [[Voice Recognition]] for more details.

====-fb_explosions====
'''"Enable Framebuffer Shockwaves"'''

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

Displays current frames per second.

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

Displays current position coordinates of camera.

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

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

====-fullscreen_window====
'''"Run in Fullscreen Window"'''
{{Note| This feature is only available on Windows.}}

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

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

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

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

Shows coordinates of the mouse cursor.

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

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

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

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

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

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

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

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

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

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

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

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

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

Disables all collisions.

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

Disables weapons rendering.

====-output_sexps====
This will make the FSO build spit out an html file that documents the supported SEXP's.

Just double click on sexps.html and it should open in your default web browser.

====-output_scripting====
This will make the FSO build spit out an html file that documents the supported scripting hooks and LUA libraries.

Just double click on scripting.html and it should open in your default web browser.

====-nograb====
Disables focus grabbing in a window.
{{Note| This feature is not available on Windows.}}

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

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

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

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

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

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

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

====-profile_frame_time====
'''"Profile engine subsystems"'''

Activates the frame profiling code. This presents a readout showing the current, minimum, maximum and average percentages of frametime a given section of code has taken up; this can be used to identify particular bottlenecks or measure the effectiveness of certain optimizations.

====-profile_write_file====
'''"Write profiling information to file"'''

This will write the frame times of each gameplay frame to the file 'profiling.csv' where each line is ''<time>;<frametime>''. Both times are measured in microseconds. ''time'' is measured from an arbitrary time in the past. To get consistent results the first ''time'' value should be substracted from all ''time'' values. The first two frames are usually very long because the timer is set at engine startup so you might want to exclude those from your data.

====-no_unfocused_pause====
'''"Don't pause if the window isn't focused"'''

When the FSO window looses focus it will not pause the game, useful for doing non-interactive test runs.

====-benchmark_mode====
'''"Puts the game into benchmark mode"'''
See [[Benchmarking]] for more information.

====-noninteractive====
'''"Disables interactive dialogs"'''
Disables all dialogs and chooses the default option when one would be displayed. Very useful for a standalone server on a headless system.

==Other==
The following options are not available as checkboxes in the launcher. Many require parameters, which follow the flag separated by a space. The prototype for use in this case is "-option argument"

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

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

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

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

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

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

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

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

===Graphics===
====-bloom_intensity====
Requires -post_processing ("Enable Post Processing") command.
Default value is 75. Range is 0-200.

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

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

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

====-center_res====
Specifies how much of the screen area should be utilized by menus, movies, the HUD, and various other 2D graphics. Intended for use with configurations with an extremely wide field of view, such as triple-monitor setups.

By default, if the screen resolution's aspect ratio is wider than 7:2, most 2D elements utilize only the center 3/10 of the screen area. This setting allows users to override this behavior to make better use of the center monitor. (The reason for using 3/10 rather than 1/3 is that many triple-monitor setups use bezel correction, which reduces the fraction of the screen area that the center monitor displays.)

For example, if the screen resolution is 6000x1080, then -center_res 1920x1080 will keep most 2D graphics in the center 1920x1080 area. This setting is automatically scaled to fit the screen resolution, so (assuming the resolution is still 6000x1080) -center_res 1280x720 is given, then that resolution is enlarged to 1920x1080.

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

===Gameplay===
====-start_mission====
'''"Skip the mainhall in jump right into the specified mission"'''

Jump into the mission specified by the filename. Only in effect on the first run. This will skip load of the mainhall and its other related things altogether.

====-mod====
Specifies in which folders inside FreeSpace 2 directory, the game looks for all the game data (models, missions, textures, tables, ...). Retail version only looks inside ''Freespace2/data/'' structure and ''Freespace2/vp archives''.

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

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

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

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

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

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

'''Data precedence'''

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

Inside each directory, data precedence is the following:

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

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

'''Additional notes'''
# As derived from the explanation, the exact names for directories or vp archives are actually irrelevant. It only matters the directory order inside -mod flag argument and the alphabetical order for vp archives inside each used directory.
# This flag is also used by [[Portal:FRED|FRED]]. So if there is special mod info, (like backgrounds maps, ship models or whatever), it must be typed, (''Fred2_Open_r.exe -MOD whatever''), or FRED won't be able to use it. A special build of wxLauncher is able to configure FRED so that the -mod doesn't have to be done manually see [http://www.hard-light.net/forums/index.php?topic=67950.msg1387911#msg1387911 the forum post] for more details.
{{Table3612|As of 3.6.12 FRED now loads cmdline_fso.cfg just like FS does so FRED will use the same settings as FS including the -mod settings}}
# Be careful while typing the directory names in the flag argument or inside mod.ini files. The program doesn't check if the typed directories exist. If they do not exist, they are just ignored. No warnings, no errors, no messages at all.

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

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

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

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

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

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

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

}}

====-fov====
This flag allows the player to specify the ''vertical'' Field of View (FoV) angle, in radians, for the player eyepoint. The angle is measured across the full height of the viewing cone. The FoV angle is technically known as the Angle of View (AoV)

*Syntax: '''''float''''' Angle
*Valid Values: 0 to 2*Pi radians
*Default Value: 0.75 radians

{{Note|For peculiar reasons, the actual FoV/AoV used by the game will be the supplied value multiplied by 1.39626348.}}

The the FoV angle/AoV is what determines the relative zoom level of the main game camera. Smaller angles generally equal to higher zoom levels, while larger angles equal to lower zoom levels (down to the theoretical x0 magnification).

However, too small of an angle will have a squashed look on the edges of your screen, and too high of an angle will greatly stretch edges. It is recommended to change the AoV, as FS2's default AoV has some perspective distortion at the screen edges (the default AoV is too high).

A natural looking (as if you where physically in the cockpit) AoV depends on the distance the player's actual eyes are away from the screen: the further away from the screen, the smaller the AoV should be, and vice versa. "Ergonomic" distances generally yield a '''''diagonal''''' AoV of 0.523 radians (30 degrees), but you can easily find the natural AoV by the following formula:

AoV (radians) = 2 * atan( H / ( 2*D ))

where:

Height of screen = H

Distance between head/eye and the screen = D

Generally, gamers like to increase the AoV in order to increase their peripheral vision on the screen, so as to gain a better situational awareness around their craft. An AoV of 0.39 radians seems to be a good start, but feel free to experiment and use whatever AoV you are most comfortable with.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

====-connect====
Automatically connect to multiplayer IP:PORT.

Takes one string value, such as 192.168.0.1:

====-timeout====
Multiplayer network timeout (secs).

Takes one integer argument, the timeout value in seconds. Default is 30.

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

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

===Help===
====-help====
Instructs FSO to print out all supported parameters. Some launchers can use these options to automatically populate the available command line options, even if the version of FSO is far newer than the launcher itself. NOTE: This option only works in Linux builds...

====--help====
See [[Command-Line_Reference#-help|-help]]

====-h====
See [[Command-Line_Reference#-help|-help]]

====-?====
See [[Command-Line_Reference#-help|-help]]

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

Ships and General Mod Creation

2016-08-30T19:14:58Z

AdmiralRalwood: /* Getting Started: */ Cleaning up this awkward construction.

Thanks to the work of the [[Source Code Project]] (SCP) team modifying FreeSpace 2 is now very easy, though understanding everything by yourself is extremely difficult with to date only one major modification released that could be called a solo project (see [[WoD]]). Your best bet to start Modifying is to focus on one area, at least to begin with, then once you have a grasp of how things work or you decide you are no longer interested in it and you feel like other areas interest you can start looking at them. Modifying any game calls on a wide array of talents from general creative writing to table editing, model making and the ever in demand skills of texture artists. This page is intended as a getting started and confidence builder as an in depth how to is a massive undertaking and the detailed information on how to mod FreeSpace is found within the modding section of this wiki with issue specific help and advice available on the Hard Light Productions forum.

==Before We Get Started==

===Your New Best Friends===

By closely reading this page, you have taken your first steps of making the most important friend every FreeSpace modder has - the Modding Portal of the FreeSpace Wiki. Within the Wiki's pages is a gold mine of information created by the SCP team and community members who have spent a huge amount of time and effort making sure things work, and how they work is well documented.

Your next best friends are in your FreeSpace2\data folder, and they are fs2_open.log and fred2_open.log. These two files are the logs generated by the debug builds of FreeSpace 2 and the FRED2 editor. The way to tell between a release and debug build is that after the build cycle number in the file name there is a d for debug or r for regular, eg 3.6.12d. any information after this point in the file name is information that tells the support guys exactly which version you are using. Whenever you are running a debug build of FreeSpace or FRED, the program creates a constant record of the program's activity and lists any error messages where possible that occur and stores that record in the listed log files. Debug builds try to catch every error they can while release builds try to ignore them, making debug build an invaluable tool for error-checking. To open the logs, simply double click on them and, if prompted, select any text editor.

===Required:===

The following are required to create mods for FreeSpace Open:

*A working and legitimate copy of FreeSpace 2
*FreeSpace Open executable (preferably the latest stable build or, if you know what you are doing, a Nightly build)
*Imagination

==Getting Started:==

The first thing to know when modifying FreeSpace 2 is to understand how the mod structure works. Each mod needs its own folder within the FreeSpace 2 folder. For example, Wings of Dawn on my computer is C:\Games\Freespace2\Wings of Dawn. All files that directly relate to the WoD mod are found within this folder on my PC, though a file (mod.ini) within the folder tells FreeSpace to go and look for the mediavps mod. The mod structure allows for mods to be chained together in a simple fashion. Within the mod folders is another folder called data. The data folder is not present in mods relying on .[[VP]] files, which are container files that mimic the mod structure and are used to make distributing and installing mods easier. Within the data folder are the subfolders which the files that make the mod are stored. The subfolders are there to keep everyone sane and make everything easier to find. The majority are self-explanatory but a detailed breakdown can be found in [[FS2_Data_Structure]]. Below is a summary of important information relating to this tutorial.

*''Cache'' - To reduce loading times, the engine will generate a cache file for each model it encounters. Since cache generation can take quite long for more complex models, you should always include cache files for unique mods.
{{Table374|
:Cache files are no longer used or generated by the executable; since making a new mod should always be done on the latest stable release, you shouldn't have to worry about cache files anymore.}}
*''Cbanims'' - This is where command and mission briefing animations are stored.
*''Effects'' - Weapon and other 2D effects, stars, planets, nebulae, e.t.c.
*''Fonts'' - Font files are kept here. Unless you are aiming at a total conversion, you will in all likelihood not need this folder.
*''Hud'' - This is where custom HUD graphics go.
*''Intelanims'' - Animations used in the Techroom for weapons and intel sections are located here.
*''Interface'' - Images and animations used in the menu system go here. Not everything that you would expect to be a still is stored as a still, so research carefully before changing anything. Only larger mods and total conversions generally go into this because it is hard to do properly.
*''Maps'' - Texture files for ships and other model-based objects.
*''Missions'' - This is where FRED should be storing mission files and the only place where FS2 will look for missions and campaigns, both single- and multi-player.
*''Models'' - .pof files go here no matter what purpose.
*''Music'' - In-game music files go here.
*''Sounds'' - Sound effects like weapons fire belong here.
*''Tables'' - This is where the .tbl and .tbm files go that tells the game how to use the majority of the information in the folders listed and also controls a number of other game aspects.
*''Voice'' - Voice overs for mission chatter.

==Simple Modifications==

One of the simplest things to do is add a new weapons or ships created by the community. The two are often related as ships created by members might have their own custom weapons.

===Adding A Ship===

The following will be an example of how to add a ship in FreeSpace:

*Go to [[SC Lamia]] in [[User-made Ships]] and download it.
*Create a folder in FreeSpace2 directory called New Ship.
*Within the New Ship directory, create a folder called data.
*Extract sc_lamia.rar. If you are unable to, you can download a file archiver such as 7-zip to extract the files.
*Inside the file are three folders called maps, models, and tables. Copy them into your New Ship\data folder without altering them.
*Create a mod.ini by opening a text editor. The following are required for the mod.ini to work:
**[launcher]
**modname = New Ship;
**[multimod]
**primarylist = ;
**secondarylist = mediavps_3612 ;
***This is optional. By having the mediavps_3612 listed in your secondarylist, you will use the SC Lamia as well as the Mediavps instead of the Lamia with retail FS2 assets.

Congratulations! You have just created your first mod. If you look in the maps folder there will be three .dds image files which make up the ship's texture. The models folder will contain SCLamia.pof, and in tables there are two .tbm files - one for the ship and one for a custom weapon for that ship.

There is one more thing I want you to do, though. Open sclamia-shp.tbm in a text editor and find the line starting $flags:. The full line reads ''$Flags: ( "cruiser" )''. Add "in tech database" with the quotation marks to the line between the parentheses so it reads ''$Flags: ( "cruiser" "in tech database" )''. Save and close the file. This allows the Lamia to be viewed in the Techroom from the beginning. Open your FreeSpace launcher and select New Ship as the mod and run the game. If you get an error message, go back to the file and double-check the flags line to the example I provided. When you reach the main screen go to the Techroom and at the bottom should be the Shivan cruiser you just added, the ship will not appear in any missions at this time because a mission file needs creating using the ship.

===Mod.ini===

Unlike other files, the mod.ini does not go in the data folder of a mod. Instead, this file goes in the main directory for the mod (e.g. Freespace2\New Ship for the above example) and adds the final polish to a mod. It performs useful tasks like linking other mods. Like many of the files in Freespace 2, this is basically a renamed .txt file and can be opened by any text editor. Let’s take a look at one.

# PLEASE NOTE ALL INI SETTINGS ARE *OPTIONAL*
# modname: Display name only, so you can have spaces instead of underscores for multi word MOD's
# image255x112: Location of a 255x112 bmp you wish to display in the launcher
# infotext: Text that will appear in the launcher
# website: Link to your website
# forum: Link to your forum
[launcher]
modname = Mod Name
image255x112 = mod-logo.bmp;
infotext = Here is a short blurb for the mod
# website = Here is where a web address goes if your mod has one
# forum = http://www.hard-light.net/forums

[multimod]
primarylist = ;
secondarylist = mediavps_3612;

This is the contents of the mod.ini for a sample mod.

Anything following a # is a comment and is ignored by the launcher.

The first section is information for the FreeSpace launcher and contains the following:

* modname: the name of the mod
* image255x112: the name of a 255x112 pixel .bmp to use as a mod image
* infotext: the area where you can put info about the mod and/or a tag line
* website: the link to your website that will be linked to the Website button in the launcher
* forum: the link to your forum that will be linked to the Forum button in the launcher

In the example shown both website and forum are commented out but if you remove the # and save they will be read by the launcher.

The next bit links the mod into other ones, the example above will call the 3.6.12 version of the mediavps to enhance the visuals of anything in FreeSpace 2 that is not touched by your mod. For example, if you turn the Ravana green, the Ravan will not be red because the mediaVPs_3612 is in the secondary line. However, it will become red if you have the mediavps_3612 in your primarylist. Most of the time, you will only use secondary list. This is the one you are recommended to use unless you know exactly what you are doing.

===Changing Other Mods===

You have downloaded some mod. You played it, and you have beaten it. However, you want to change something. Perhaps you feel the anti-fighter turrets are too weak or that there is a different ship you want to use. Do NOT add, remove, or change anything in the actual folder! This is because you will change the mod as long as the altered files are in there. What you should do is create a mod as explained in 'Adding A Ship' and place a mod.ini referencing the folder name for whatever mod you wish to alter in the secondary mod line. Then place the edit-that-you-want-to-make (e.g. model, .tbm, etc.) into this new mod. Once you have done all of that, select the new mod folder in the Freespace launcher’s mod tab and run. Because of the reference to the original in the mod.ini, that and any mods referenced by that mod will be loaded, but the changes you made will override the original. This way, you get to play your twist on the mod whenever you want without having to alter the original mod to play it.

==.VP==

Because of the ease in damaging data key to a mod or indeed retail, IT IS STRONGLY ADVISED THAT .VP FILES ARE NOT EDITED IN ANY WAY!

The advantage of a .vp file is ease of distribution. A .vp file is a container used to maintain the file structure. All that is required is that they are all placed in the mod folder. The problem with changing them is that if you edit one and get it wrong, you may have to reinstall the mod because there is no way for mod/FSO support teams to know what you have done to the .vp, and they have enough on their plate without having to user fix a problem that shouldn't have happened.

==.TBM VS. .TBL==

A .tbl is the core table file of that type, and only one can be loaded into FreeSpace at any one time. .tbl files provide the structure to the engine and require all basic elements to be present to work.

A .tbm (called [[Modular Tables]]) file, on the other hand, is an additional file to the .tbl, usually providing additional data to the .tbl or overriding it if needed. Generally, you'll be using a .tbm unless you're planning on doing a total conversion. .tbm files also have the advantage that FS2 can handle multiple .tbm files of any given type, though a modder should avoid conflicting entries at all costs.

==Closing Words==

I cannot overstate the usefulness of [[Portal:Modding]] and everything within its links. A good 90-95% of what I know about modding was learned in there and the rest was trial and error with a new newbie questions on the forum and IRC channel.

Another thing is that it is as a matter of courtesy to credit people whose resources you use. You are unlikely to get thrown out of the community for not doing so, but it is always nice to have that little nod of thanks.

Also on a side note: don’t change the name of the folder for and existing/downloaded mod. Many mods reference each other, and changing the name for the folder will break the links in the mod.ini of any mods that tries to use it. This increases the chance that there will be assets missing. On top of this, when you report the issues cause by changing folder name, you will be treated in a colder manner because you have broken the hard work that went into making sure the mod worked correctly in the first place. Lets face it. How would you react if you got your mod working nicely and someone comes to you because the mod doesn’t work by being renamed? And then several other people started to complain about the same problem?

Remember the most important thing when modding a FreeSpace is to have fun. It can be surprising how fun trial, error, and figuring things out for yourself can be.

Good luck and if you really do get stuck do not be afraid to ask questions.

[[Category:Tutorials|General Mod Creation]]

Ships and General Mod Creation

2016-08-30T19:01:54Z

AdmiralRalwood: /* Getting Started: */ Cache files aren't used anymore.

Thanks to the work of the [[Source Code Project]] (SCP) team modifying FreeSpace 2 is now very easy, though understanding everything by yourself is extremely difficult with to date only one major modification released that could be called a solo project (see [[WoD]]). Your best bet to start Modifying is to focus on one area, at least to begin with, then once you have a grasp of how things work or you decide you are no longer interested in it and you feel like other areas interest you can start looking at them. Modifying any game calls on a wide array of talents from general creative writing to table editing, model making and the ever in demand skills of texture artists. This page is intended as a getting started and confidence builder as an in depth how to is a massive undertaking and the detailed information on how to mod FreeSpace is found within the modding section of this wiki with issue specific help and advice available on the Hard Light Productions forum.

==Before We Get Started==

===Your New Best Friends===

By closely reading this page, you have taken your first steps of making the most important friend every FreeSpace modder has - the Modding Portal of the FreeSpace Wiki. Within the Wiki's pages is a gold mine of information created by the SCP team and community members who have spent a huge amount of time and effort making sure things work, and how they work is well documented.

Your next best friends are in your FreeSpace2\data folder, and they are fs2_open.log and fred2_open.log. These two files are the logs generated by the debug builds of FreeSpace 2 and the FRED2 editor. The way to tell between a release and debug build is that after the build cycle number in the file name there is a d for debug or r for regular, eg 3.6.12d. any information after this point in the file name is information that tells the support guys exactly which version you are using. Whenever you are running a debug build of FreeSpace or FRED, the program creates a constant record of the program's activity and lists any error messages where possible that occur and stores that record in the listed log files. Debug builds try to catch every error they can while release builds try to ignore them, making debug build an invaluable tool for error-checking. To open the logs, simply double click on them and, if prompted, select any text editor.

===Required:===

The following are required to create mods for FreeSpace Open:

*A working and legitimate copy of FreeSpace 2
*FreeSpace Open executable (preferably the latest stable build or, if you know what you are doing, a Nightly build)
*Imagination

==Getting Started:==

The first thing to know when modifying FreeSpace 2 is to understand how the mod structure works. Each mod needs its own folder within the FreeSpace 2 folder. For example, Wings of Dawn on my computer is C:\Games\Freespace2\Wings of Dawn. All files that directly relate to the WoD mod are found within this folder on my PC, though a file (mod.ini) within the folder tells FreeSpace to go and look for the mediavps mod. The mod structure allows for mods to be chained together in a simple fashion. Within the mod folders is another folder called data. The data folder is not present in mods relying on .[[VP]] files, which are container files that mimic the mod structure and are used to make distributing and installing mods easier. Within the data folder are the subfolders which the files that make the mod are stored. The subfolders are there to keep everyone sane and make everything easier to find. The majority are self-explanatory but a detailed breakdown can be found in [[FS2_Data_Structure]]. Below is a summary of important information relating to this tutorial.

*''Cache'' - To reduce loading times, the engine will generate a cache file for each model it encounters. Since cache generation can take quite long for more complex models, you should always include cache files for unique mods.
{{Table374|
:Cache files are no longer used or generated by the executable; since making a new mod should always be done on the latest stable release, you shouldn't have to worry about cache files anymore.}}
*''Cbanims'' - This is where command and mission briefing animations are stored.
*''Effects'' - Weapon and other 2D effects, stars, planets, nebulae, e.t.c.
*''Fonts'' - Font files are kept here. Unless you are aiming at a total conversion, you will in all likelihood not need this folder.
*''Hud'' - This is where custom HUD graphics go.
*''Intelanims'' - Animations used in the Techroom for weapons and intel sections are located here.
*''Interface'' - Images and animations used in the menu system go here. Not everything that you would expect to be a still is stored as a still, so research carefully before changing anything. Only larger mods and total conversions generally go into this because it is hard to do properly.
*''Maps'' - Texture files for ships and other model-based objects.
*''Missions'' - This is where FRED should be storing mission files and the only place where FS2 will look for missions both single player and campaign.
*''Models'' - .pof files go here no matter what purpose.
*''Music'' - In-game music files go here.
*''Sounds'' - Sound effects like weapons fire belong here.
*''Tables'' - This is where the .tbl and .tbm files go that tells the game how to use the majority of the information in the folders listed and also controls a number of other game aspects.
*''Voice'' - Voice overs for mission chatter.

==Simple Modifications==

One of the simplest things to do is add a new weapons or ships created by the community. The two are often related as ships created by members might have their own custom weapons.

===Adding A Ship===

The following will be an example of how to add a ship in FreeSpace:

*Go to [[SC Lamia]] in [[User-made Ships]] and download it.
*Create a folder in FreeSpace2 directory called New Ship.
*Within the New Ship directory, create a folder called data.
*Extract sc_lamia.rar. If you are unable to, you can download a file archiver such as 7-zip to extract the files.
*Inside the file are three folders called maps, models, and tables. Copy them into your New Ship\data folder without altering them.
*Create a mod.ini by opening a text editor. The following are required for the mod.ini to work:
**[launcher]
**modname = New Ship;
**[multimod]
**primarylist = ;
**secondarylist = mediavps_3612 ;
***This is optional. By having the mediavps_3612 listed in your secondarylist, you will use the SC Lamia as well as the Mediavps instead of the Lamia with retail FS2 assets.

Congratulations! You have just created your first mod. If you look in the maps folder there will be three .dds image files which make up the ship's texture. The models folder will contain SCLamia.pof, and in tables there are two .tbm files - one for the ship and one for a custom weapon for that ship.

There is one more thing I want you to do, though. Open sclamia-shp.tbm in a text editor and find the line starting $flags:. The full line reads ''$Flags: ( "cruiser" )''. Add "in tech database" with the quotation marks to the line between the parentheses so it reads ''$Flags: ( "cruiser" "in tech database" )''. Save and close the file. This allows the Lamia to be viewed in the Techroom from the beginning. Open your FreeSpace launcher and select New Ship as the mod and run the game. If you get an error message, go back to the file and double-check the flags line to the example I provided. When you reach the main screen go to the Techroom and at the bottom should be the Shivan cruiser you just added, the ship will not appear in any missions at this time because a mission file needs creating using the ship.

===Mod.ini===

Unlike other files, the mod.ini does not go in the data folder of a mod. Instead, this file goes in the main directory for the mod (e.g. Freespace2\New Ship for the above example) and adds the final polish to a mod. It performs useful tasks like linking other mods. Like many of the files in Freespace 2, this is basically a renamed .txt file and can be opened by any text editor. Let’s take a look at one.

# PLEASE NOTE ALL INI SETTINGS ARE *OPTIONAL*
# modname: Display name only, so you can have spaces instead of underscores for multi word MOD's
# image255x112: Location of a 255x112 bmp you wish to display in the launcher
# infotext: Text that will appear in the launcher
# website: Link to your website
# forum: Link to your forum
[launcher]
modname = Mod Name
image255x112 = mod-logo.bmp;
infotext = Here is a short blurb for the mod
# website = Here is where a web address goes if your mod has one
# forum = http://www.hard-light.net/forums

[multimod]
primarylist = ;
secondarylist = mediavps_3612;

This is the contents of the mod.ini for a sample mod.

Anything following a # is a comment and is ignored by the launcher.

The first section is information for the FreeSpace launcher and contains the following:

* modname: the name of the mod
* image255x112: the name of a 255x112 pixel .bmp to use as a mod image
* infotext: the area where you can put info about the mod and/or a tag line
* website: the link to your website that will be linked to the Website button in the launcher
* forum: the link to your forum that will be linked to the Forum button in the launcher

In the example shown both website and forum are commented out but if you remove the # and save they will be read by the launcher.

The next bit links the mod into other ones, the example above will call the 3.6.12 version of the mediavps to enhance the visuals of anything in FreeSpace 2 that is not touched by your mod. For example, if you turn the Ravana green, the Ravan will not be red because the mediaVPs_3612 is in the secondary line. However, it will become red if you have the mediavps_3612 in your primarylist. Most of the time, you will only use secondary list. This is the one you are recommended to use unless you know exactly what you are doing.

===Changing Other Mods===

You have downloaded some mod. You played it, and you have beaten it. However, you want to change something. Perhaps you feel the anti-fighter turrets are too weak or that there is a different ship you want to use. Do NOT add, remove, or change anything in the actual folder! This is because you will change the mod as long as the altered files are in there. What you should do is create a mod as explained in 'Adding A Ship' and place a mod.ini referencing the folder name for whatever mod you wish to alter in the secondary mod line. Then place the edit-that-you-want-to-make (e.g. model, .tbm, etc.) into this new mod. Once you have done all of that, select the new mod folder in the Freespace launcher’s mod tab and run. Because of the reference to the original in the mod.ini, that and any mods referenced by that mod will be loaded, but the changes you made will override the original. This way, you get to play your twist on the mod whenever you want without having to alter the original mod to play it.

==.VP==

Because of the ease in damaging data key to a mod or indeed retail, IT IS STRONGLY ADVISED THAT .VP FILES ARE NOT EDITED IN ANY WAY!

The advantage of a .vp file is ease of distribution. A .vp file is a container used to maintain the file structure. All that is required is that they are all placed in the mod folder. The problem with changing them is that if you edit one and get it wrong, you may have to reinstall the mod because there is no way for mod/FSO support teams to know what you have done to the .vp, and they have enough on their plate without having to user fix a problem that shouldn't have happened.

==.TBM VS. .TBL==

A .tbl is the core table file of that type, and only one can be loaded into FreeSpace at any one time. .tbl files provide the structure to the engine and require all basic elements to be present to work.

A .tbm (called [[Modular Tables]]) file, on the other hand, is an additional file to the .tbl, usually providing additional data to the .tbl or overriding it if needed. Generally, you'll be using a .tbm unless you're planning on doing a total conversion. .tbm files also have the advantage that FS2 can handle multiple .tbm files of any given type, though a modder should avoid conflicting entries at all costs.

==Closing Words==

I cannot overstate the usefulness of [[Portal:Modding]] and everything within its links. A good 90-95% of what I know about modding was learned in there and the rest was trial and error with a new newbie questions on the forum and IRC channel.

Another thing is that it is as a matter of courtesy to credit people whose resources you use. You are unlikely to get thrown out of the community for not doing so, but it is always nice to have that little nod of thanks.

Also on a side note: don’t change the name of the folder for and existing/downloaded mod. Many mods reference each other, and changing the name for the folder will break the links in the mod.ini of any mods that tries to use it. This increases the chance that there will be assets missing. On top of this, when you report the issues cause by changing folder name, you will be treated in a colder manner because you have broken the hard work that went into making sure the mod worked correctly in the first place. Lets face it. How would you react if you got your mod working nicely and someone comes to you because the mod doesn’t work by being renamed? And then several other people started to complain about the same problem?

Remember the most important thing when modding a FreeSpace is to have fun. It can be surprising how fun trial, error, and figuring things out for yourself can be.

Good luck and if you really do get stuck do not be afraid to ask questions.

[[Category:Tutorials|General Mod Creation]]

FreeSpace Trivia

2016-08-27T23:47:14Z

AdmiralRalwood: /* Bugs */ This is false; removing a ship from your escort list just prevents the game from highlighting asteroids that are on a collision course.

==Quirks==
===Mission-related Quirks===
* In [[The Place of Chariots]], the mission where you encounter the [[NTF Boadicea|NTF ''Boadicea'']], Volition used the facing-waypoint SEXP to ensure that the ''Boadicea'' never appears when the player is looking directly at it. If the player turns toward the area where the Boadicea appears and never turns away, the mission will never progress.
* The mission name 'Exodus' appears in all three Volition single-player campaigns (The Main FreeSpace Campaign, Silent Threat, and FreeSpace 2).
* The mission names 'The Great Hunt' and 'Clash of the Titans' (with/without II on the end) appear in both FS1 and FS2.
* [[As Lightning Fall]] is the only FreeSpace 2 mission with no beams mounted on any ship.
* In FRED, ships are auto-named by assigning a number to their ship class (for example, GTC ''Leviathan 5''). However, if a ship already has the name about to be assigned by the auto-namer, the new ship will be named "U.R.A. ''Moron 1''".
* During FreeSpace 1, most if not all [[Hammer of Light]] ships were actually assigned the Neutral IFF. The Shivans were assigned the Hostile IFF, which allows the two sides to engage each other. Note however, that Neutral ships will not attack Hostile ships unless specifically ordered to, in keeping with the HoL's non-resistance belief when it comes to Shivans. Apart from behavior, this is impossible to tell in-game as both Neutral and Hostile IFFs appear red on the HUD. It could also be noted that in certain missions NTF ships were also marked Neutral.
* Some FreeSpace 1 FRED mission descriptions read, "i am the god of beer and fire."
* [[The Place of Chariots]] and [[The Romans Blunder]] appear to have been designed as a linked pair of missions. The freighters in the first mission appear in the second one and have been set to carry cargo containing the same things. Both freighters and cargo have been set to red alert.
* Rather bizarrely, [[SJ Sathanas|SJ ''Sathanas 01'']] is set to red-alert in [[High Noon]]. We cannot be entirely sure what that means. It could be a simple mistake or it could be an indication that ''Sathanas 01'' was meant to accumulate damage from a preceding mission (There is a systematic error in the Volition missions where they set red-alert-carry on both the mission preceding the red alert and the red alert itself).
* The [[ST Azrael|Shivan ''Azrael'' transport]] that carries off [[Admiral Bosch|Bosch]] in [[Return to Babel]] is also set to red-alert.
* Most interestingly of all, Alpha wing in [[Their Finest Hour]] is set up to red-alert. This can indicate that the last three missions of the campaign were all meant to be played in sequence. This probably proved too difficult, so the first mission was turned into a stand alone.
* The SOC pilots, "Xinny" and "Zero", who fly with the player in [[Into the Lion's Den]], are actually named after two real FreeSpace 1 multiplayer pilots who reached the top of the scoreboards and were offered to be mentioned in FreeSpace 2 by [[Volition]].

===Ship-related Quirks===
* The [[GVC Aten|''Aten'' cruiser]] destroyed before the mission in La Ruota Della Fortuna is designated ''Maltusa''.
* The [[SCv Moloch|SCv ''Moloch'']]'s fighterbay was never used in the main campaign. However, it was used in a multiplayer mission.
* The TTC 1 tech container does not appear at all in either the FS1 or Silent Threat campaigns. A few of them appear in [[...But Hate the Traitor]], during the FS2 campaign. It also appears in the FS2 cutscene "Colossus" (albeit slightly enlarged).
* The ship name ''Andromeda'' was used for three Vasudan ships and one Terran ship: the PVFR ''Andromeda'' in [[The Hammer and the Anvil]], the PVC ''Andromeda'' in [[The Pursuit]], the GTSC ''Andromeda'' in [[On the Run]], and the GVC ''Andromeda'' in a command briefing in [[Surrender, Belisarius|Surrender, Belisarius!]].
* The [[PVS Scarab|''Scarab'' support ship]] and the [[GVEP Ra|''Ra'' escape pod]] have FreeSpace's only "in-game" depiction of a Vasudan, Shivan, or Terran. The "unmanned" Scarab has a dead Vasudan in its debris, while the Ra's story is somewhat more [[Find the MOON Challenge Results|interesting]].
* The [[GTEP Hermes|GTEP ''Hermes'']], [[GTS Centaur|GTS ''Centaur'']], [[PVS Scarab|PVS ''Scarab'']], [[GVS Nephthys|GVS ''Nephthys'']] and [[GTS Hygeia|GTS ''Hygeia'']] all have untargetable engine subsystems but can still be disabled by weapons fire. The ''Centaur'' in [[Enter the Dragon]] is occasionally disabled by the ''Shakti's'' blob turrets, for example. The ''Ra'' has an engine subsystem as well, but for whatever reason, it cannot be disabled.
* In the second training mission of FS2, there is an [[GTI Arcadia|''Arcadia''-class installation]] named the ''Kos''. It appears to serve no purpose in the mission.
* All GTVA warships in [[Their Finest Hour]] are beam-freed by SEXP. However, the GTC ''Stalwart'' and GVC ''Heket'' are beam-freed moments before they warp in, so they are unable to fire their beams for the entire mission. Only the GVCv ''Khepri'''s beam-free-all SEXP was set correctly.
* The Vasudans have no equivalent to the [[GTT Argo|GTT ''Argo'']] or [[SFr Asmodeus|SFr ''Asmodeus'']]. To get around this problem in [[Return to Babel]], the Vasudans actually use an ''Argo'' transport named the G'''V'''T ''Qeb''. There is Volition concept art for the GVT ''Qeb'' class, which was apparently never made.
* The [[GTD Hecate|GTD ''Hecate'']] model is apparently based off that of the [[GTD Hades|GTD ''Hades'']]. The bow, rear engine arrangement, and "vertical" superstructures are similar.
* The [[GVB Bakha|GVB ''Bakha'']] is never "given" to the player using an allow-ship SEXP; it is only forced in [[Bearbaiting]] and [[High Noon]], both being "scramble" missions. On a related note, the [[GVB Sekhmet|GVB ''Sekhmet'']] is the only Terran or Vasudan fighter/bomber in FS2 that the player is never granted, or has a chance to fly in, during the main single-player campaign.
* The player has only one chance to fly the [[GTF Pegasus|GTF ''Pegasus'']], in [[Endgame]].
* Viewed from the side, the [[GTI Arcadia|''Arcadia'' installation]] resembles the [[GTA]] logo.
* The [[GTG Zephyrus|''Zephyrus'']] and [[GVG Anuket|''Anuket'']] gas miner-class vessels have dockpoints named 'blahblah'.
* Almost all the freighters and transports, namely the [[GTT Elysium|''Elysium'']], [[GTFr Chronos|''Chronos'']], [[GTFr Poseidon|''Poseidon'']], [[GVT Isis|''Isis'']], [[PVFr Bast|''Bast'']], [[PVFr Ma'at|''Ma'at'']], [[GVFr Satis|''Satis'']], [[ST Azrael|''Azrael'']], [[SFr Mephisto|''Mephisto'']] and [[SFr Asmodeus|''Asmodeus'']] have unused shield meshes. The shield meshes can easily be re-activated by editing the [[ships.tbl]] file. None of the new freighters or transports included with FreeSpace 2 share this trait.
* The [[GTSG Mjolnir]] has a shield system with 800 hitpoints. However, it lacks a shield mesh, thus it has no shields by default.

===Weapon-related Quirks===
* The BFGreen is only used once in the game (during [[Endgame]] and only on one of the Colossus' turrets).
* The LRBGreen was only used once, in [[High Noon]].
* You can target your own bomb using the target-object-in-reticle key as well as the proximity target key. If you have previously acquired an aspect lock on a target, your target display will show a video from the bomb's seeker. If you have not acquired an aspect lock yet, it will show the regular display.
* The player is granted the Cyclops#short before [[Slaying Ravana]]. The player actually uses Cyclops#shorts until the [[The King's Gambit]]; he is never granted the "real" [[GTM Cyclops|Cyclops]], but uses it anyway for [[The King's Gambit]].
* The [[Harbinger]] missile model is reused as the tip of the [[Stiletto]] missile model.
* The amount of damage that a beam can inflict on a friendly is limited. On Very Easy, Easy, Medium, Hard, and Insane, the limits are 0, 5, 10, 20, and 30 damage, respectively (per every ~.2 seconds).
* A [[FreeSpace Reference Bible]] command brief states that the Terrans or Vasudans "tried three different missile prototypes, with no luck whatsoever" against the Lucifer as it attacked "the Vasudan outpost in the Diones system".

===Other Quirks===
* There are only three canon references to ground warfare in FreeSpace. If the player wins [[Surrender, Belisarius|the first mission]] in FS2, he is told that 600,000 ground troops are sent to invade Cygnus Prime. Also, there is an FS1 multi mission where the player attacks an HoL marine convoy. Finally, the FS2 multi mission Rebel Intercept has the player intercepting NTF reinforcements headed to reinforce a ground battle in [[Sirius]].
* FS1 command brief and tech room .anis normally had readable text. Almost all FS2 .anis, however, have some kind of nonsense text. The Meson Bomb command brief animation reads like an advertisement (Guaranteed to blow anything up...).
* Almost every radio message in FS2, other than training messages, is accompanied by a head animation. Several radio messages in FS1, however, don't have a head animation. None of the freighter's messages in FS1 have one, and there are two instances of "Command" not having an animation. In [[Eve of Destruction]], if the [[GTC Orff|GTC ''Orff'']] is destroyed, Command speaks without a head .ani. Also, in [[Paving the Way]], Admiral Wolf's messages have no head .ani. In the FS2 mission [[Mystery of the Trinity]], when the NTC ''Trinity'' reaches critical damage, a pilot speaks without a head .ani. This is due to a bug with the personas.
* The only squadron leader or admiral that the player ever sees is Admiral Wolf. Admiral Wolf (Alpha 1's commander on the [[GTD Galatea|GTD ''Galatea'']]) appears once, in a cutscene (and also a few times in-mission with the normal command head .ani).
* The FS2 techroom animation for Sol shows the Earth facing ''backwards'' and rotating the wrong way.
* The FS1 Vasudan persona is not fully voice-acted.
* In [[ships.tbl]] in both FS1 and FS2, ship names beginning with an "@" indicate a ship that was present in the demo.
* FreeSpace contains many [[Node Inconsistencies|node inconsistencies]]. For example various FS1 command brief ANIs show 3 different nodes connecting Sol to other systems (but not all at once).
* Right-clicking in the mainhall allows you to cycle through interface choices.
* Mission sm3-05 in FS1 makes reference to an enigmatic "[[Ysusi]] System". In the mission briefing display, there is a node labelled "Ysusi System" placed outside the view area.
* The ''Hermes'' escape pod in ''Out of the Dark, Into the Night'' is capable of intersystem jumps, but at the same time, the larger Medusa bomber can't.

==Bugs==

Software, mission design, and similar bugs.

* Exclusive to FS1, if a support ship is ordered to dock with the player through AI orders and not by player command, the player's ship will be thrown out of the game area at high velocity in an intense spin. Leaving the game area by warping is subsequently impossible due to the spin.
* The FreeSpace engine's solution to complicated collision problems is to fling one of the offending objects far out of the game area, in the order of 500,000 units. It was once a minor pastime of the FreeSpace community to see how far one could be "flung" after messing around with the Orion's fighterbay.
* In [[Love the Treason...]], the jump node to [[Regulus]] is named "Regulas".
* If you fire bombs into certain fighterbays, such as the [[GTI Arcadia|Arcadia]]'s, your bombs will fly in circles until they run out of fuel and explode.
* If you name an object "planet" in FRED, and you go near the object in-game, a message will appear saying "Too close to planet. Taking damage!"
* In the command briefing animation for [[The King's Gambit]], the strategy is described in "Stage One" followed by "Stage 2".
* Sentry 04 in 'Place of Chariots' is assigned the cargo "Unable To Scan".
* The TC-TRI cargo containers carried by Capricorn wing in "The Romans Blunder" are friendly.
* The [[GTI Ganymede|GTI ''Ganymede'']] is never used during the main FS2 campaign, although it appears in a multiplayer dogfight.
* The SCv ''Moloch'''s fighterbay paths are misplaced. It also has an incorrect turret normal on one of its bottom laser turrets that allows the ''Moloch'' to fire through itself. This is a common problem with Volition FreeSpace models. For example, the GTFr ''Chronos'' can fire straight through itself, as well as the Medusa's turret in FS1, giving the players a whole 360 degree firing range of the turret.
* The ''Myrmidon'' fighter is able to carry Helios anti-matter bombs, but not Cyclops or other heavy weaponry. This never has a chance to be noticed in the main campaign, as the player only uses the Helios in the two scramble missions [[Bearbaiting]] and [[High Noon]]. This is widely believed to be either a data entry error or some kind of joke.
*The "big damage", "huge", etc. flags are not fully implemented in FS1; it's possible to kill the Lucifer with an [[GTW ML-16|ML-16]]. They are implemented in FS2, however.
*If you order a support ship to depart while it is still docked to you in FreeSpace 1, the game will register that you warped out, but you become invincible and can continue the mission. However, you will not be able to complete the mission, and any red-alert triggers will result in the next mission being screwed up and the game will crash.

==Design Changes==

This category includes both early development decisions that were later changed, game engine changes between FS1 and FS2.

* Act I of FreeSpace 1 (consisting of the missions up to [[First Strike]]) was originally released as ''Descent: FreeSpace - Darkness Rising''. This OEM version was included with several Dell computers along with Sidewinder joysticks as part of a promotional offer.
* Volition released a [[FreeSpace Alpha]] version to several reviewers before the release of FS1. The Alpha contained a stripped-down, incomplete version of FS1, with the two FS1 demo missions plus an original mission featuring a Fenris/Leviathan cruiser named GTC ''Juggernath''. The mission was dropped before the official demo shipped.
* According to a table file in FS2, [[Silent Threat]] had another weapon known as the "GTM-84 Corkscrew Missile", and was "deemed too wacky for final release."
* Despite what the training missions say, support ships never run out of secondary weapons.
* The [[SC Cain|SC ''Cain'']] and [[SC Lilith|SC ''Lilith'']] cruiser originally had a different hull design, with two fin-like appendages protruding from the lower hull. These can clearly be seen in [[FreeSpace Alpha|alpha/beta]] screenshots.
* The Prometheus was originally introduced much earlier into the game (sometime around [[The Big Bang]]).
* [[First Strike]] originally had an asteroid field.
* The special-issue DVD release of Descent: FreeSpace used planet bitmaps as backgrounds like in FS2, as well as afterburner trails. These additional effects were also apparently included in the demo, although they are missing in the main release.
* If you export the [[GTB Artemis|''Artemis'']]/[[GTF Ares|''Ares'']]/[[GVS Nephthys|''Nephthys'']]/[[GVF Ptah|''Ptah'']]/[[GVB Sekhmet|''Sekhmet'']] POF to COB, you can see that the main object is called "herca", suggesting that they were either based on or were early concepts for the Hercules Mk II.
* The [[GVB Bakha|''Bakha'']] was originally a fighter.
* Shivan ships were originally green in color.
* The [[SD Demon|SD ''Demon'']]'s hull integrity was increased by 60% between FS1 and FS2, from 100,000 to 160,000 hitpoints.
* The old FreeSpace 2 website, which had a [http://web.archive.org/web/20080317015244/http://www.freespace2.com/bfod.cfm Bug Fix of the Day page], stated that FS1 had a 50 point penalty for rearming (62.5 points on Insane). This point penalty system was removed in FS2.
* In the mission [[Into the Maelstrom]], there are two ''Elysium'' transports named Hauler 1 and Hauler 2. They have no purpose in the mission.
* [[Clash of the Titans]] had a [[GTC Fenris|''Fenris''-class cruiser]] designated the ''Gladiator''. Its arrival cue was set to [[false]], however.
* In [[Their Finest Hour]], the ''Colossus'' has a complex waypoint path, implying that it was originally meant to have a complicated and dramatic battle with SJ ''Sathanas 17''. In the final version, the waypoints are not used and the ''Colossus'' is disabled. Command orders the ''Colossus'' to warp out even though its engines aren't working.
* The FS1 voice VP contains some "alternate" voice acting for several missions. For example, the freighter and transport dialogue during [[First Strike]] was apparently originally voiced by a woman.
* The command briefing for [[Enter the Dragon]] refers to "your investigation of the [[SD Lucifer|''Lucifer'']] at [[Antares]]". [[Alpha 1]] had not even encountered the ''Lucifer'' at that point in the campaign.
* FRED1 (the mission editor for FS1) originally had a feature known as TBL info. It is now present in FRED2_OPEN.
* The [[SD Lucifer|''Lucifer'']] tech description in FS1 states that it has three "flux" cannons. However, it only has two. The third beam (perhaps the one used for bombarding planets) was probably meant to be mounted on the bow of the ship. Development notes specify that a beam is to be located on each set of three red circles.
*The high-res Lucifer model that Volition used for cutscenes has two "antennae" that are not present in the in-game model. They were probably removed for aesthetic reasons, but the non-canon HTL Lucifer re-incorporated them. Also, the high-res Lucifer has several green lights along with its red lighting which are clearly visible in the endgame cutscene.
* Originally, [[Eve of Destruction]] had the player cast as part of the [[GTC Orff|GTC ''Orff'']]'s crew, not the [[GTD Galatea|GTD ''Galatea'']]'s. This can be verified through briefing screenshots taken from [[FreeSpace Alpha]].
* The [[FreeSpace Reference Bible]] seems to imply that groups ships jumping in from subspace were originally intended to all come through the same "hole", rather than each ship having an individual hole. (''The pilot is soon within sight of the Terran installation. As the pilot struggles to relay his story and keep his bomber from disintegrating, many subspace holes open up in front of him, out of which streams of Shivan fighters pour.'')
* There is a sound file in the FS1 VPs called "Approach.wav" that sounds like a fighter coming in to land on its carrier. This implies that Volition initially intended there to be a landing cutscene at the end of each mission, like Wing Commander. The file might also be a leftover from an earlier design choice with every mission ending with the player entering a docking bay. This was scrapped early on, due to it severely changing the way missions were played.
* The FS2 voice VP, stu_fs2.vp, contains voice acting for an unreleased mission, M09. More information can be found on the [http://www.hard-light.net/forums/index.php/topic,42231.0.html Hard Light thread] on the subject.
*The reason why FreeSpace is called FreeSpace is because it actually is referring to subspace. Inside the reference bible, the following quote is found "''When scientists discovered what used to be called “FreeSpace” (now referred to as “subspace”)''"
*[[Christopher Snipes|Snipes]]' voice actor was originally going to be the voice of the Training Instructor, but this was changed sometime in development.

==Renamings==

Most of these renamings were noticed in pre-release screenshots, model file names, or in FRED by looking at internal names used in the missions themselves.

* Hostile Vasudan wings were originally called "Steel", "Brass", "Iron", etc.
* Shivan wings were originally called "Cobra", "Viper", "Hornet", etc.
* The Cyclops bomb was originally named Belial.
* The Harpoon missile was originally named Crossbow. The name for the missile can clearly be seen in the FreeSpace 2 trailer.
* The Subach HL-7 laser was originally named Subach HL-33.
* The Subach HL-7 laser and Mekhu HL-7 laser were originally named Sidearm. The name SD-4 Sidearm can clearly be seen in the FreeSpace 2 trailer. Moreover, in the retail version of FreeSpace 2 the icon and animation files for the weapons are still called iconSD4 and SD4, respectively.
* The Akheton SDG laser was originally named DR-2 Scalpel. At some point during the development phase it was also known as Akheton DR-2.
* The Interceptor was originally called the Shrike. At one point it was also called the Mega.
* The Avenger laser was originally named Phalanx.
* The ML-16 laser was originally named Light Laser.
* The Harbinger was originally called the Mag-Pulse.
* The Prometheus was originally called the Flux.
* The Phoenix V was originally called the Angelfire.
* The Synaptic was originally called the Cluster.
* The MX-50 was originally called the Rockeye. The name is still present in the FreeSpace 1 demo.
* The Rockeye was originally called the Wasp.
* The GTW-83 Lamprey was originally called the Shrieker, and was later changed to GTW-83 Light Laser, before finally settling on the present name.
* The Hornet was originally called the Swarm.
* The GTW-66 Maxim Cannon was originally called the GTW-66 Newton Cannon.
* The Morning Star was originally called the Mace. Later in development the name was changed to Flail II. Ultimately, though, it was renamed Morning Star.
* The Hornet was originally called the Bombardier.
* NTF wings were originally called "Corsair", "Bandit", etc.
* Admiral Khafre's name was originally Admiral Hepsut ([[Surrender, Belisarius]])
* The GTD ''Aquitaine'' was originally named the GTD ''Intrepid''.
* The GTD ''Galatea'', was originally named the ITA ''Repulse'' ([[FreeSpace Reference Bible]]).
* The SJ ''Sathanas'' was originally named ''Apocalypse''. If you look at your event log after completing [[A Monster in the Mist]], you can still see a goal named "Scan Apocalypse Subsystems".
* The GTFr ''Chronos'' was originally named ''Boar''.
* The GVF ''Tauret'' was originally named ''Crab''.
* The SF ''Dragon'' was originally named ''Mosquito''.
* The Avenger Prototype was originally named Mass Driver Prototype.
* Shivan wings were also originally named "Scab Alpha", "Scab Beta", etc.
* For a long time the ''Apollo'' fighter was called ''SF-XX Generic Fighter''.
* In the [[FreeSpace Alpha|Alpha]] version, the Fury Missile still used the graphics of the left-out G-13 Medium Laser. The laser weapon disappeared completely before the original FreeSpace 1 demo, and was unique to the Alpha version. It also looks a lot like the Tsunami colored grey.

==Cutscene quirks==

Allegedly, Volition contracted another company to make the FreeSpace cutscenes. They have several canon inconsistencies.

===FreeSpace 1 Intro===
* The "Apollo" pictured in the FS1 introduction cutscene is actually a modified version of the in-game [[GTF Apollo|''Apollo'']]. According to the FreeSpace Reference Bible, the Apollo in the intro cutscene is a "Terran bomber". Its gun mounts are slightly different and off-center, among other changes. Perhaps [[Volition]] placed the ''Apollo'''s gun mounts closer to the centerline for the sake of playability. The [[SF Manticore|''Manticore'']], too, has different fire points (mounted on the twin "booms" instead of centered like they are in the game. These different firing points make a return in the FS2 intro).
* If you look carefully, you can see a (apparently dead) copilot in the front seat of the intro's Apollo-bomber. He is visible for less than a second. The [[FreeSpace Reference Bible]] refers to this copilot as the "gunner".
* [[GTF Hercules|''Hercules'']] and [[GTB Medusa|''Medusa'']] icons are shown on Riviera Station's radar display (although no Hercs or Medusas are visible in the cutscene).

===Hallfight===
* The captured Shivan vessel is called a "freighter", but it is actually an [[ST Azrael|''Azrael''-class transport]].

===FreeSpace 2 Intro===
* The HLP community has christened the [[GTD Orion|''Orion''-class destroyer]] holed in the intro as the [[GTD Legion|GTD ''Legion'']], with consent from [[Volition]]. FS1 command briefings claim that the ''Bastion'' and ''Galatea'' are guarding [[Deneb]], and makes no reference to any other Terran destroyers guarding the system. [[Volition]] has stated that this ship was not the ''Galatea'', and the ''Bastion'' does not bite the bullet until nearly the end of FS2.
* A Shivan [[Demon|''Demon''-class destroyer]] appears after the destruction of the ''Legion'', even though the only Shivan destroyer (other than the ''Lucifer'') in the system, the [[SD Eva|''Eva'']], was already destroyed in [[Evangelist]].
* The beam fire from the [[SD Lucifer|''SD Lucifer'']] that destroyed the ''Legion'' comes out of the port side of the ship, rather than the "arms" of the ''Lucifer'', from which the beams fired in FS1 missions.
* The sound of the SD ''Lucifer'''s beam firing is exactly the same as the BFGreen's.
* The [[GTB Ursa]] is shown even though it was not distributed among GTA fleets until after [[Running the Gauntlet]].
* None of the [[GTC Fenris|''Fenris'' cruisers]] had their missile launchers shown.
* A [[GTF Hercules|''Hercules'']] is shown crashing into the planet after getting shot down. It sits on the planet surface, relatively undamaged. In reality, an object in uncontrolled descent from orbit with the mass of a FreeSpace 2 fighter (which is hardly budged by "mutli-kiloton" missiles) would leave a deep crater in the ground. The pilot would experience extreme g-force upon impact and would not be alive to climb out of the cockpit as he apparently does in the cutscene.
* The [[GTD Hades|GTD ''Hades'']] is shown as a wreck on the surface of the Deneb planet. Silent Threat command briefings indicate that the Hades was destroyed in [[Beta Aquilae]], however.

===Colossus cutscene===
* The [[GTI Ganymede|''Ganymede'']] in the cutscene is several times bigger than normal.
* The [[SD Lucifer|''Lucifer'']] is smaller than normal.
* The [[GTFr Chronos|''Chronos'' freighters]] have two turrets, as opposed to the usual one, and they look different from the normal turret.
* The ''Chronos'' freighters are either much smaller than their in-game counterparts, or the TTC 1 cargo pod is much bigger.
* [[Mirfak]] is named Mirfax.
* The [[GTD Galatea|''Galatea'']] appears in the Colossus fleet.
* The Colossus data scene has several blocks of text, all of them starting with "Math is cool."

=="Real Life"==

This category includes mainly business decisions, but also interesting connections between FreeSpace and RL.

* FreeSpace 1 was officially distributed as "Conflict: FreeSpace - The Great War" in Europe and "Descent: FreeSpace - The Great War" in the United States.
* The [[GTM Infyrno]] is a deliberate misspelling of Inferno, for copyright reasons.
* It's FreeSpace, not Freespace (notice the capitalization of the S).
* FreeSpace 1 is called Descent: FreeSpace in the US due to copyright issues with the disk compression utility FreeSpace.
* ''FreeSpace 2'' was originally named ''FreeSpace 2: Colossus'' (for the demo). Even before that, it was named ''FreeSpace 2: Exodus''.
* In Greek, the plural of Knossos is Knossoi, and the plural of Sathanas is Sathanai (ancient Greek) or Sathanes (modern Greek). These are loose translations; Sathanas is simply the Greek representation of the Hebrew word for Satan. Volition always circumvented the plural by using phrases such as "Sathanas juggernauts".
* Volition employees apparently created a humorous music track known as [[Bite Me]], created from numerous voice acting outtakes.

==Canon inconsistencies: Retail FS2 box==
Several [[canon]] inconsistencies are present on the retail FS2 box (although these inconsistencies are not generally accepted as canon themselves): [[Image:Freespacebox-1a.JPG|thumb|'''The front side of the European box edition.''']]
[[Image:Freespacebox-2a.JPG|thumb|'''The back side of the European box edition.''']]

* The [[GTCv Deimos|GTCv ''Deimos'']] is listed as an AWACS ship (on the backside of the box there is written "GTA Deimos"). However, the following text specifies that the ship class is a "corvette" (on the back side of the box).
* The ''Deimos'' has side-mounted multipart turrets that are not present in the game, or even possible under the game engine (on the front side of the box).
* The ''Deimos'''s turrets are not firing [[Terran Turret]]s. Instead they are firing [[GTW UD-8 Kayser|Kayser]]-like lasers (on the front side of the box).
* Only the [[GTF Perseus|''Perseus'']] in front of the ''Deimos'' has engine thrusters (on the front side of the box).
* On the European version of the box, the [[SD Lucifer|''Lucifer'']] is visible just at the right of the first ''Deimos'''s top turret (on the front side of the box).
* On the European version of the box, the ''Deimos'' is a destroyer (the nameplate on the corvette says "..D Deimos")(on the front side of the box).
*In the back side of the box, the text below the rightmost screenshot says: "Encounter 'beam weapons' that can penetrate and utterly carve gigantic capital ships in half." However, beams in the game cannot cleave anything in half.
*In the introduction (back side), the last paragraph says: "Your nemesis has arrived... and they are wondering what happened to their scouting party." This most likely refers to the Shivan force that attacked in 2335 (FS1).
* The Italian version of the box says that beam weapons can be used also by fighters, according to the blurb on the back ("Imparate a usare le armi a raggi...", or "Learn to use beam weapons...")(not shown).

[[Category:The games|Trivia]]