FreeSpace Wiki - User contributions [en]

Game settings.tbl

2026-10-01T16:19:54Z

Wookieejedi: fix thruster depth formating

{{SCP_table}}
{{TableVersionGit|2025-02-10|642111676012bc6696f4024c40296a6c20b3b958}}
{{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

If the version targeted in [[game_settings.tbl#$Target_Version:|target version]] is equal to or later than these listed, the following options are enabled by default:
{{Table220|
*[[game_settings.tbl#$Fixed_Turret_Collisions:|Fixed Turret Collisions]]
*[[game_settings.tbl#$Fixed_Missile_Detonation:|Fixed Missile Detonation]]
*[[game_settings.tbl#$Shockwaves_Damage_All_Object_Types_Once:|Shockwaves Damage All Object Types Once]]
*[[game_settings.tbl#$AI_use_framerate_independent_turning:|AI use framerate independent turning]]
*[[game_settings.tbl#$Use_host_orientation_for_set-camera-facing:|Use host orientation for set-camera-facing]]
}}
{{Table230|
*[[game_settings.tbl#$Shockwaves_Inherit_Parent_Weapon_Damage_Type:|Shockwaves Inherit Parent Weapon Damage Type]]
*[[game_settings.tbl#$Fixed_Chaining_To_Repeating_Events:|Fixed Chaining To Repeating Events]]
}}
{{Table240|
*[[game_settings.tbl#$Calculate_subsystem_hitpoints_after_parsing:|Calculate subsystem hitpoints after parsing]]}}
{{Table242|
*[[game_settings.tbl#$Fix_scripted_velocity:|Fix scripted velocity]]}}
{{Table250|
*[[game_settings.tbl#$Use_model_eyepoint_for_set-camera-host:|Use model eyepoint for set-camera-host]]
*[[game_settings.tbl#$Use_model_eyepoint_normals:|Use model eyepoint normals]]
*[[game_settings.tbl#$Fix_asteroid/debris_field_bounding_box_checks:|Fix asteroid/debris field bounding box checks]]
*[[game_settings.tbl#$Disable_expensive_turret_target_check:|Disable expensive turret target check]]
*[[game_settings.tbl#$Skybox_internal_depth_consistency:|Skybox internal depth consistency]]
}}
{{Table260|
*[[game_settings.tbl#$Zero-radius_explosions_skip_fireballs:|Zero-radius explosions skip fireballs]]
*[[game_settings.tbl#$Render_insignias_as_decals:|Render insignias as decals:]]}}
{{Table262|
*[[game_settings.tbl#$Fix collision moment of inertia:|Fix collision moment of inertia]]}}

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

The icon should be in data/maps or data/interface, and can apparently be any single-frame image format supported by FSO. The default icon is .png.

*Syntax: '''''String'''''
}}

===$Mod title:===
{{Table224|
Specifies the title of the mod and will be displayed at the mainhall near the FSO version.
*Syntax: '''''String'''''
}}
{{Table250|
It is now possible to display the mod title on its own. Previously, the mod version was also required.
}}

===$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'''''
}}
{{Table250|
It is now possible to display the mod version on its own. Previously, the mod title was also required.
}}

===$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'''''}}

===$Splash screens:===
{{Table232|
Defines a list of splash screens that FSO can display upon game startup. The actual image displayed is chosen at random from the applicable entries. Entries with exact aspect ratio matches will be prioritized first, followed by aspect ratio ranged matches, followed by entries without an aspect ratio specified.}}

====+Bitmap:====
{{table232|
The name of the bitmap to use as a splash screen. Extension will be removed if included.
*Syntax: '''''+Bitmap: String'''''}}

====+Aspect Ratio:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio matches the specified number within +/- 0.01.
*Syntax: '''''+Aspect Ratio: Float'''''}}

====+Aspect Ratio Min:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at least the specified number.
*Syntax: '''''+Aspect Ratio Min: Float'''''}}

====+Aspect Ratio Max:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at most the specified number.
*Syntax: '''''+Aspect Ratio Max: Float'''''}}

===$Splash fade in time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade in.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Splash fade out time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade out.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Center splash logo:===
{{Table232|
Sets whether the splash logo will be displayed in the middle of the screen. If this is false (the default), it will be displayed at the top-left.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Disable FSO Internal Loadout Restoration System:===
{{Table234|
When the player configures the ships and weapons of the wings in the loadout screen, FSO will remember these settings and attempt to apply them again if the player quits the mission and comes back to it later. FSO will only remember the most recent mission's loadout, so it will not attempt to restore the loadout if the player loads a different mission. It will also not attempt this if the mission's ''$Modified:'' date has changed. This flag can be used to prevent FSO from attempting restoration even if it normally would.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Lua API returns nil instead of invalid object:===
{{Table242|
A design choice very early in FSO's scripting development established that invalid results return invalid objects. By using this flag, invalid results will return nil instead.
*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 initalize built-in languages by default:===
{{Table240|
Prevent FSO from initializing the three additional built-in languages (German, French, and Polish). This allows mods which don't support those languages to remove them from the SCPUI language selector.
*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'''''}}

===$Auto select subsystem under reticle when targeting same ship:===
{{Table242|This is a streamlining of functionality, that makes it so one doesn't need to hit a second key to select the subsystem under the reticle. Instead once you have the capital ship selected, hit Target Under Reticle and it will target a subsystem under the reticle if the feature is enabled and there isn't a new target under the reticle.
*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'''''
}}

===$HUD drop shadows enabled by default:===
{{Table232|
If this flag is active, certain elements displayed on the HUD (all text, the main targeting reticle, and the background of the ETS gauges) will have a "drop shadow" effect. Note that whether or not the flag is active, the player can set this using the "Toggle HUD Drop Shadows" control.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Unify scanning behavior:===
{{Table242|
*Unifies scanning behavior between subsystem, regular, and cargo allowing missions to use all scan types in all situations.
*Also allows changing the "Cargo:" text line in a mission by adding "$Cargo Title: STRING" after the "$Cargo 1:" or "$Cargo 2:" lines in the mission file. FRED UI support not yet added for $Cargo Title so you have to do it manually.
*When this flag is enabled, all ships, no matter the ship class, will react the same way to the cargo-related or scanning-related ship flags:
**They are not scannable by default
**Setting the "scannable" flag makes them scannable, and scanning the subsystem will reveal the cargo
**A new flag available with alter-ship-flag, "no-scanned-cargo", changes the behavior to scanned/unscanned instead of revealing the cargo
**The "toggle-subsystem-scanning" flag must be set to swap full-ship scanning mode into subsystem scanning mode and works for all ship types
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Don't show callsigns in the escort list:===
{{Table242|
By default, callsigns are shown in the escort list using the same format as in the target box. If this flag is active, callsigns will not be displayed.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Hide main Rearm/Repair items in Comms Gauge:===
{{Table250|
Prevents 5. Rearm/Repair Subsys and 6. Abort Rearm from being shown in the squad messaging menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Always show selected item in Comms Gauge:===
{{Table262|
Ensures that the visual indicator for which is the active item in the squad messaging menu is always shown. Useful if you are using the select Comms menu item keys. By default this is not shown until the player presses the up or down key for the select Comms menu item keys.
*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'''''

===$Fixed Chaining To Repeating Events:===
{{Table230|When set, this makes event chaining to repeated events work as designed - that is, the chained event will only be evaluated after the chain delay. If the repeating event's interval is shorter than the chain delay, then the delay countdown will continually be restarted until all repetitions have completed. Without this flag, FSO will emulate retail behavior which, due to a bug, allowed chained events to be evaluated immediately after a repeating event is first evaluated.

NOTE: Although the name does not reflect it, the same issue affects repeating events that are evaluated by <tt>is-event-true-delay</tt> and <tt>is-event-false-delay</tt>. Without this flag, FSO will emulate retail behavior which causes these SEXP operators to ignore any delay when evaluating repeated events. With this flag, the delay will be measured from when the final repeat iteration occurs.
*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'''''}}

===$Use model eyepoint for set-camera-host:===
{{Table250|The default behavior for set-camera-host is to position the camera at the origin coordinates (0,0,0) of the host. This flag will make the camera use the model eyepoint instead.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Use model eyepoint normals:===
{{Table250|If set, model eyepoints will respect the normal vector set for the eyepoint in the model file for the eyepoint. If not set, model eyepoints will use the model's orientation.
*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)'''''}}

===$HUD-set-coords base resolution:===
{{Table232|The hud-set-coords SEXP has always used exact pixels, without regard for the current screen resolution. This setting enables a similar scaling mechanism as ''$Show-subtitle base resolution:''.
*Syntax: '''''(Integer, Integer)'''''
*Default Value: '''''(-1, -1)'''''}}

===$Always Show Directive Value Count:===
{{Table250|
*If this setting is enabled, Directive-as-Value values in Directives will always show the number. By default this is disabled, and only values > 1 are shown.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

==#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'''''}}

===$EMP Pain Flash Factor:===
{{Table224|
Determines the intensity of the flash when the player is hit by an EMP blast or weapon.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$EMP Pain Flash Color:===
{{Table224|
Determines the RGB color value of the flash when the player is hit by an EMP blast or weapon.
*Syntax: Color, (red, green, blue) respectively, integer value from 0 to 255
*Default Value: '''''(255, 255, 127)'''''}}

===$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)
}}

===$EMP Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)
}}

===$Damage Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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.
{{Table262|
*Can now be an arbitrary non-zero number of floats. If not set to 4, you must table [[#$Shadow Smoothness Factor:]]
}}
*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.
{{Table262|
*Can now be an arbitrary non-zero number of floats. If not set to 4, you must table [[#$Shadow Smoothness Factor:]]
}}
*Syntax: '''''List of floats'''''
*Default Value: '''''(0.25, 0.75, 1.5, 3.0)'''''}}

{{Table262|
===$Shadow Smoothness Factor:===
Sets the strength of the smoothing for each shadow cascade. Larger values mean smoother / softer shadows. Shadow smoothness also scales with cascade distance, so the same value for a larger cascade will be perceived to be smoother.
The number of smoothness factors ''must'' match the number of Shadow Cockpit Cascades + Shadow Cascades (each 4 by default).
The list should first contain the smoothness factors for the cockpit cascades in order, and then the smoothness factors for the main cascades in order
*Syntax: '''''List of floats'''''
*Default Value: '''''(0.00333, 0.004, 0.005, 0.005, 0.00333, 0.004, 0.005, 0.005)'''''}}

===$Shadow Disable Techroom:===
{{Table224|
Disables shadows on ships in the techroom.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Cockpit:===
{{Table224|
Disables shadows on the player cockpit in mission.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Weapons:===
{{Table224|
Disables shadows on weapons in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Ships:===
{{Table224|
Disables shadows on ships in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Show Ship Casts Shadow:===
{{Table224|
When cockpit shadows are enabled, enabling this setting will cause the players ship model shown with "show ship" to cast shadow onto the cockpit.
*Syntax: '''''Boolean'''''
}}

===$Ship Model And Cockpit Share Coordinate Space:===
{{Table224|
When having the "show ship" flag enabled and cockpit models for a ship, this flag should be on if the cockpits can fit into the actual geometry of the ship model. Disable this flag if this is not the case and the cockpit needs to be rendered on top of the ship regardless of actual coordinates. If this can be enabled, the external show ship model can be rendered using deferred rendering.
*Syntax: '''''Boolean'''''
}}

===$Show Ship enabled only if Cockpits enabled:===
{{Table250|
Enabling this setting will only use the 'show-ship' flag if cockpits are enabled. Useful if your ship uses both 'show-ship' and cockpits that exist within the 'show-ship' space, and you want to allow players to toggle off cockpits. Note, 'show-ship' always only appears if in first-person view.
*Syntax: '''''Boolean'''''
}}

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

===$Do Not Render Lasers Below Length:===
{{Table250|
*Specifies the smallest length that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Do Not Render Lasers Below Radius:===
{{Table250|
*Specifies the smallest radius that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Thruster Easing Value:===
{{Table220|
*Smooths out the behavior of maneuvering thruster flares the higher above 0 it is.
*This is the exponential time constant for the visual flare length to reach it's true length.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

===$Primary Thruster Glow Depth Factor:===
{{Table262|
*This value is a multiplier of the Primary Thruster glow's computed size. By default, Primary Thrusters showed through model geometry, but setting this value to less than or equal to 0 will fix the issue.
*Syntax: '''''Float'''''
*Default Value: 0.325f}}

===$Tertiary Thruster Glow Depth Factor:===
{{Table262|
*This value is a multiplier of the Tertiary Thruster glow's computed size. By default, Tertiary Thrusters does not show through model geometry, but you could make it so by setting this value to greater than 0.
*Syntax: '''''Float'''''
*Default Value: -0.5f}}

===$SCPUI attempts to load hires animations:===
{{Table230|
*Prevents SCPUI from trying to load anims prefixed with "2_"
*Syntax: '''''Boolean'''''
*Default Value: true}}

{{Table230|
===$Max draw distance:===
===$Min draw distance:===
*These values do more than just cutoff the visuals at certain distances, and they must be adjusted carefully to ensure unintentional rendering artifacts are not introduced.
*The rendering engine has limited amount of 'depth resolution', the degree to which it can tell a certain polygon is closer or farther away than another. When two polygons are too close, they will Z-fight, picking arbitrarily which is closer. It is the span between the min and max draw distance that determines how well the engine can determine depth, if they are too far from one another, the Z-fighting will become more common as it has to spread its resolution over a wider range. If they are close, Z-fighting will be lessened at the cost of a smaller range of distance able to be rendered.
*Syntax: '''''Float''''', meters
*Default Values: 10,000,000,000 and 1, respectively
}}

{{Table232|
===$Randomize particle rotation:===
*Particle bitmaps are typically screen-aligned; the upper portion of the bitmap will always be mapped to the upper portion of the particle, from the point of view of the camera. Enabling this option makes ''all'' particles have a random 'tilt' in an arbitrary direction when created.
*Syntax: '''''Boolean'''''
*Default Value: false
}}

===$Disable shield effects:===
{{Table250|
*Specifies if FSO attempts to use the shield mesh impact effects. Enabling this flag will prevent the game from preforming any shield mesh effect code, which can be useful if a mod does not use those shield mesh effects.
*Syntax: '''''Boolean'''''
*Default Value: false}}

===$Disable all non-custom generic debris:===
{{Table250|
*Provides one simple control to turn off all non-custom generic debris (the tiny debris shards that are typically spawned when a ship/subsystem explodes). Note, generic debris that is manually specified in the ships table will still be spawned, this is only for turning off non-custom debris.
*Syntax: '''''Boolean'''''
*Default Value: false}}

===$Render insignias as decals:===
{{Table260|
*If set, insignias will be rendered using the decal system. This will make insignias render with correct and deferred lighting, and fix issues with apparent fading
*Models must be set up correctly for this to work! A model can have multiple insignias, with multiple polygon faces each. To enable this option, each visible insignia must have its own insignia entry in the model. If multiple visible insignias are incorrectly consolidated into one insignia entry with disjointed polygons, this will cause graphical artifacts.
*For reference, check out the retail FS2 models, which are set up correctly.
*Syntax: '''''Boolean'''''
*Default Value: false}}

==#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'''''}}

===$Use weapon class impact sounds for hits to player:===
{{Table224|
Allows weapons that hit the player to play their specific impact sounds, not the hard-coded default sounds.
*Syntax: '''''Boolean'''''
}}

===$Play thruster sounds for the player:===
{{Table232|
If the player's ship has thruster sounds defined, this will ensure they are played like normal, since they are typically suppressed.
*Syntax: '''''Boolean'''''
}}

===$Unify minimum engine sound:===
{{Table250|
Allows $Minimum Engine Volume in ships.tbl to work for all ship classes. By default, that value only triggers for non-huge ships.
*Syntax: '''''Boolean'''''
}}

===$Disabled or disrupted engines are silent:===
{{Table250|
If set, engines will not play their engine noise if the ship is disabled or a disrupted (such as disruptions caused by an active EMP effect or a weapon with the "electronics" flag).
*Syntax: '''''Boolean'''''
}}

==#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'''''}}

===$Add Message Head Ani Files:===
{{table224|
FRED will append each +Head entry listed below to the head ani selection list in the Event Editor.}}

====+Head:====
{{table224|
The head ani filename to add. Extensions will be stripped if included.
NOTE: Pay attention to file names or anis with a,b, c variation not display in-game (unless called directly). Proper name seems to be Head-xxxNa, Head-xxxNb, with N being some number and XXX being whatever you want. Needs further testing and confirmation
*Syntax: '''''+Head: String'''''}}

===$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'''''}}

===$FRED Briefing window resolution:===
{{table224|
The width and height of the briefing window in FRED. Defaults to 888x371. Note that changing this only affects FRED and can cause a mismatch to the ingame briefing view which defaults to 888x371 (or 555x232 for 640 base res).
*Syntax: '''''integer, integer'''''
*Default Value: '''''888,371'''''}}

===$Ignore Music Files In Music Player:===
{{table232|Music files in this section will not be added to FRED's built-in music player.}}
====+File:====
{{table232|Specifies a file
*Syntax: '''''string'''''}}

===$FRED spacemouse nonlinearities:===
{{table232|
Allows setting custom nonlinearities and scaling for controlling FRED with a spacemouse.
}}
====+Sideways exponent:====
{{table232|
The exponent for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Sideways scale:====
{{table232|The multiplier for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards exponent:====
{{table232|The exponent for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards scale:====
{{table232|The multiplier for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards exponent:====
{{table232|The exponent for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards scale:====
{{table232|The multiplier for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch exponent:====
{{table232|The exponent for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch scale:====
{{table232|The multiplier for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank exponent:====
{{table232|The exponent for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank scale:====
{{table232|The multiplier for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading exponent:====
{{table232|The exponent for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading scale:====
{{table232|The multiplier for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}

===$Skybox internal depth consistency:===
{{table250|If enabled, this will allow skyboxes that use submodels to render the submodels with proper Z-sorting if the 'No Z-Buffer' check box is set to on in FRED. In other words, parts of the skybox closer to the origin point will render in front of sections further away, as might be expected. This flag is enabled by default for FSO version 25.0 onwards
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

==#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. This fixes missile impacts to submodels whose center lies outside the geometry of the submodel. In other words, without this flag, a missile might detonate in the middle of the "bowl" of a concave submodel; with this flag, the missile will travel to the other side of the submodel before it detonates.
*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'''''

===$Use 3d ship select:===
{{Table224|
*Whether or not to use 3D models for ship select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d ship icons:===
{{Table224|
*Whether or not to use 3D models for ships in ship/weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d weapon select:===
{{Table224|
*Whether or not to use 3D models for weapon select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d weapon icons:===
{{Table224|
*Whether or not to use 3D models for weapons in weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$FS2 effect grid color:===
{{Table250|
*Specifies the grid color for the FS2 loadout animation effect
*Syntax: '''''Integer, Integer, Integer'''''
*Default Value: '''''0, 200, 0'''''}}

===$FS2 effect scanline color:===
{{Table250|
*Specifies the scan-line color for the FS2 loadout animation effect
*Syntax: '''''Integer, Integer, Integer'''''
*Default Value: '''''0, 255, 0'''''}}

===$FS2 effect grid density:===
{{Table250|
*Specifies the number of grid lines in the FS2 loadout animation effect
*Syntax: '''''Integer'''''
*Default Value: '''''7'''''}}

===$FS2 effect wireframe color:===
{{Table250|
*Specifies the wireframe color for the FS2 loadout animation effect
*Syntax: '''''Integer, Integer, Integer'''''
*Default Value: '''''80, 49, 160'''''}}

===$Use 3d overhead ship:===
{{Table224|
*Whether or not to use 3D models for ship overhead view instead of a bitmap in weapon select
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Default overhead ship style:===
{{Table224|
*This specifies which style of overhead view to use if 3d overhead view is active
*Syntax: '''''String'''''
*Possible options are "ROTATE" or "TOPVIEW"
}}
{{Table250|
*'''+Overhead Line Color 1:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (64, 192, 192)
*'''+Overhead Line Color 2:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (192, 128, 64)
*'''+Overhead Line Color 3:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (175, 175, 175)
*'''+Overhead Line Color 4:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (100, 100, 100)
}}

===$Always refresh selected weapon when viewing loadout:===
{{Table232|
*When set to true, this always refreshes the weapon shown in view box on the right side of the screen when opening the weapon loadout view. This ensures the viewed weapon is one that can actually be on the selected ship when first clicking on the weapon loadout screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$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'''''}}

===$Movie subtitle color:===
{{Table242|
*Specifies which color should be used for displaying subtitles in the cutscene player.
*Syntax: '''''Integer, Integer, Integer, Integer'''''
*Default Value: '''''255, 255, 255, 255'''''}}

===$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|
*Mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. By default is now ON, and can be accessed by going to the Options menu and pressing F3.
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

===$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'''''}}

===$Apply HUD shudder to chase view:===
{{Table232|
*Applies hud shudder (afterburner and engine wash) also to chase view. Does not override the command line toggle.
*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'''''}}

===$Lead indicator behavior:===
{{Table224|
Changes how Lead Indicators behave when multiple weapon banks are linked and in range.
When set to default, if you have linked weapons, only the indicator for the one with the farthest range will be drawn.
When set to multiple, a lead indicator is drawn for all primary weapons in range when you have them linked.
When set to average, a single lead indicator is drawn in the average of the position where each of them would usually be drawn.
*Syntax: '''''String'''''
** Valid options are '''''default''''', '''''multiple''''' and '''''average'''''
*Default Value: '''''default'''''
}}

===$Use distant firepoint for all turrets:===
{{Table224|
*Causes the game to use firepoint-based target leading calculations for all turrets. This is useful if all or most turrets in a given mod has firepoints that are distant from their center-point.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Enable Discord rich presence:===
{{Table224|
*Enables or disables the built-in Discord game-status reporting.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Always hide hidden ships in hotkey list:===
{{Table224|
*Whether or not to always hide ships with HIDDEN hotkey (set in FRED), even in the in-mission hotkey menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Allow automatically assigning personas:===
{{Table232|
*Whether or not the game will automatically assign personas to ships that have no persona set.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Countermeasures use capacity:===
{{Table232|
*Whether or not Countermeasures use tabled capacity.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Calculate subsystem hitpoints after parsing:===
{{Table234|
*Causes subsystem hitpoints to be calculated after all ships.tbl and -shp.tbm files have been parsed. This allows subsystem percentages to correctly reflect the final hull value rather than the first hull value encountered.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Contrails use absolute speed:===
{{Table240|
*Causes contrails to be created based on speed in any direction, rather than just forward speed. This allows contrails to appear when a ship is moving in a direction other than forwards.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix scripted velocity:===
{{Table242|
*If this setting is enabled, object velocity set via script will wholly determine the change in position for that frame, ignoring ''all'' other in-engine concerns. Otherwise, the game engine will likely overwrite/ignore any changes, depending on when the changes were made in the frame.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Preload briefing icon models:===
{{Table250|
*If set, this forces preloading of models used for briefing icons. This only loads models used for icons that haven't already been loaded for the mission. This is useful for SCPUI's where hovering over an icon shows the model without having to click on it and the stutter when it loads models not used in mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Behavior for pressing Escape key in options menu:===
{{Table250|
*If set to 'save', the escape key for the HUD and Options screen saves options when leaving those screens (ie it does the same thing as pressing Ctrl-Enter/Accept). By default (or if set to 'default') the Escape key will not save any changed values when exiting those screens.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Use closest distance method for 'Target Hostile Bomb or Bomber' control:===
{{Table250|
*If set to true, the 'Target Hostile Bomb or Bomber' control will target the closest hostile bomb or bomber, similar to how the 'Target Closest Hostile' key works. By default, the 'Target Hostile Bomb or Bomber' control will not sort by distance and simply only target in order of oldest to youngest objects (ie which object spawned first in the mission).
*Syntax: '''''Boolean'''''
*Default Value: '''''false'''''}}

===$Objects targeted with 'Target Hostile Bomb or Bomber' control:===
{{Table250|
*Determines what can be targeted when using the 'Target Hostile Bomb or Bomber' control. By default this control targets both bombs and bombers, which is the behavior if this field is set to 'default' or 'bombs and bombers'. If set to 'only bombs', the key will only target bombs and not target bombers. If set to 'only bombers', the key will only target bombers and not target bombs.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Fix asteroid/debris field bounding box checks:===
{{Table250|
*Fixes a bug where asteroid and debris fields did not properly check for whether large ships were within bounds.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable intro cutscene:===
{{Table250|
*If set, this disables loading of any cutscenes as the game starts that might play before the player reaches the pilot select screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Show locked status for scramble missions:===
{{Table250|
*If set, scramble mission will show a text line right below the words 'Weapons Loadout' that states "Ships/Weapons Locked" (XSTR 749), thus the player can easily see their loadouts are locked and they do not have to check the loaoout buttons on every mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable expensive turret target check:===
{{Table250|
*If set, this value speeds up turret target checking. By default, turret target acquisition was spending a lot of time doing a raycast, the result of which was barely used at all. If we don't need the target normal, all it does is get a target point slightly more accurate, but in practice it really isn't noticeable at all whether the target point of the turret is actually on the surface of the ship, or maybe on the other side of the ship.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Threshold below which shield skips damage:===
{{Table250|
*By default, FSO logic dictates that shields collisions and any related sound or visuals related to shields are skipped if the shields are under 10%. This value allows modders to customize the value, though the value must be between 0.0 and 1.0.
*Syntax: '''''Float'''''
*Default Value: '''''0.1'''''}}

===$Minimum ship radius for persistent debris::===
{{Table250|
*Ships with a radius larger than this value will have infinite debris lifetimes.
*Syntax: '''''Float'''''
*Default Value: '''''50'''''}}

===$Zero-radius explosions skip fireballs:===
{{Table260|
*If set, explosions with a visual radius of 0 will not have fireballs created, and will not have the fireball lifetime added to the explosion lifetime.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Link special-point subsystems to -destroyed submodels:===
{{Table260|
*If set, a special-point subsystem will be linked to its corresponding -destroyed submodel (if one exists). The -destroyed submodel will be shown when the subsystem is destroyed, and hidden again if the subsystem is repaired. By default, only submodel subsystems are linked to their corresponding -destroyed submodels.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix collision moment of inertia:===
{{Table262|
*Fixes a bug in collision physics where an object's moment of inertia was applied as though the object were facing the inverse of its actual orientation (that is, an orientation that would rotate it back to the identity orientation). Without this flag, a ship that is not aligned with the coordinate axes may rotate around the wrong axis, or by the wrong amount, when something collides with it. This applies to collisions among ships, asteroids, and debris. It does not apply to weapon impacts, which were never affected by the bug.
*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]]

Game settings.tbl

2026-10-01T16:18:44Z

Wookieejedi: add thruster depth factors

{{SCP_table}}
{{TableVersionGit|2025-02-10|642111676012bc6696f4024c40296a6c20b3b958}}
{{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

If the version targeted in [[game_settings.tbl#$Target_Version:|target version]] is equal to or later than these listed, the following options are enabled by default:
{{Table220|
*[[game_settings.tbl#$Fixed_Turret_Collisions:|Fixed Turret Collisions]]
*[[game_settings.tbl#$Fixed_Missile_Detonation:|Fixed Missile Detonation]]
*[[game_settings.tbl#$Shockwaves_Damage_All_Object_Types_Once:|Shockwaves Damage All Object Types Once]]
*[[game_settings.tbl#$AI_use_framerate_independent_turning:|AI use framerate independent turning]]
*[[game_settings.tbl#$Use_host_orientation_for_set-camera-facing:|Use host orientation for set-camera-facing]]
}}
{{Table230|
*[[game_settings.tbl#$Shockwaves_Inherit_Parent_Weapon_Damage_Type:|Shockwaves Inherit Parent Weapon Damage Type]]
*[[game_settings.tbl#$Fixed_Chaining_To_Repeating_Events:|Fixed Chaining To Repeating Events]]
}}
{{Table240|
*[[game_settings.tbl#$Calculate_subsystem_hitpoints_after_parsing:|Calculate subsystem hitpoints after parsing]]}}
{{Table242|
*[[game_settings.tbl#$Fix_scripted_velocity:|Fix scripted velocity]]}}
{{Table250|
*[[game_settings.tbl#$Use_model_eyepoint_for_set-camera-host:|Use model eyepoint for set-camera-host]]
*[[game_settings.tbl#$Use_model_eyepoint_normals:|Use model eyepoint normals]]
*[[game_settings.tbl#$Fix_asteroid/debris_field_bounding_box_checks:|Fix asteroid/debris field bounding box checks]]
*[[game_settings.tbl#$Disable_expensive_turret_target_check:|Disable expensive turret target check]]
*[[game_settings.tbl#$Skybox_internal_depth_consistency:|Skybox internal depth consistency]]
}}
{{Table260|
*[[game_settings.tbl#$Zero-radius_explosions_skip_fireballs:|Zero-radius explosions skip fireballs]]
*[[game_settings.tbl#$Render_insignias_as_decals:|Render insignias as decals:]]}}
{{Table262|
*[[game_settings.tbl#$Fix collision moment of inertia:|Fix collision moment of inertia]]}}

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

The icon should be in data/maps or data/interface, and can apparently be any single-frame image format supported by FSO. The default icon is .png.

*Syntax: '''''String'''''
}}

===$Mod title:===
{{Table224|
Specifies the title of the mod and will be displayed at the mainhall near the FSO version.
*Syntax: '''''String'''''
}}
{{Table250|
It is now possible to display the mod title on its own. Previously, the mod version was also required.
}}

===$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'''''
}}
{{Table250|
It is now possible to display the mod version on its own. Previously, the mod title was also required.
}}

===$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'''''}}

===$Splash screens:===
{{Table232|
Defines a list of splash screens that FSO can display upon game startup. The actual image displayed is chosen at random from the applicable entries. Entries with exact aspect ratio matches will be prioritized first, followed by aspect ratio ranged matches, followed by entries without an aspect ratio specified.}}

====+Bitmap:====
{{table232|
The name of the bitmap to use as a splash screen. Extension will be removed if included.
*Syntax: '''''+Bitmap: String'''''}}

====+Aspect Ratio:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio matches the specified number within +/- 0.01.
*Syntax: '''''+Aspect Ratio: Float'''''}}

====+Aspect Ratio Min:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at least the specified number.
*Syntax: '''''+Aspect Ratio Min: Float'''''}}

====+Aspect Ratio Max:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at most the specified number.
*Syntax: '''''+Aspect Ratio Max: Float'''''}}

===$Splash fade in time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade in.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Splash fade out time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade out.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Center splash logo:===
{{Table232|
Sets whether the splash logo will be displayed in the middle of the screen. If this is false (the default), it will be displayed at the top-left.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Disable FSO Internal Loadout Restoration System:===
{{Table234|
When the player configures the ships and weapons of the wings in the loadout screen, FSO will remember these settings and attempt to apply them again if the player quits the mission and comes back to it later. FSO will only remember the most recent mission's loadout, so it will not attempt to restore the loadout if the player loads a different mission. It will also not attempt this if the mission's ''$Modified:'' date has changed. This flag can be used to prevent FSO from attempting restoration even if it normally would.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Lua API returns nil instead of invalid object:===
{{Table242|
A design choice very early in FSO's scripting development established that invalid results return invalid objects. By using this flag, invalid results will return nil instead.
*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 initalize built-in languages by default:===
{{Table240|
Prevent FSO from initializing the three additional built-in languages (German, French, and Polish). This allows mods which don't support those languages to remove them from the SCPUI language selector.
*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'''''}}

===$Auto select subsystem under reticle when targeting same ship:===
{{Table242|This is a streamlining of functionality, that makes it so one doesn't need to hit a second key to select the subsystem under the reticle. Instead once you have the capital ship selected, hit Target Under Reticle and it will target a subsystem under the reticle if the feature is enabled and there isn't a new target under the reticle.
*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'''''
}}

===$HUD drop shadows enabled by default:===
{{Table232|
If this flag is active, certain elements displayed on the HUD (all text, the main targeting reticle, and the background of the ETS gauges) will have a "drop shadow" effect. Note that whether or not the flag is active, the player can set this using the "Toggle HUD Drop Shadows" control.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Unify scanning behavior:===
{{Table242|
*Unifies scanning behavior between subsystem, regular, and cargo allowing missions to use all scan types in all situations.
*Also allows changing the "Cargo:" text line in a mission by adding "$Cargo Title: STRING" after the "$Cargo 1:" or "$Cargo 2:" lines in the mission file. FRED UI support not yet added for $Cargo Title so you have to do it manually.
*When this flag is enabled, all ships, no matter the ship class, will react the same way to the cargo-related or scanning-related ship flags:
**They are not scannable by default
**Setting the "scannable" flag makes them scannable, and scanning the subsystem will reveal the cargo
**A new flag available with alter-ship-flag, "no-scanned-cargo", changes the behavior to scanned/unscanned instead of revealing the cargo
**The "toggle-subsystem-scanning" flag must be set to swap full-ship scanning mode into subsystem scanning mode and works for all ship types
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Don't show callsigns in the escort list:===
{{Table242|
By default, callsigns are shown in the escort list using the same format as in the target box. If this flag is active, callsigns will not be displayed.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Hide main Rearm/Repair items in Comms Gauge:===
{{Table250|
Prevents 5. Rearm/Repair Subsys and 6. Abort Rearm from being shown in the squad messaging menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Always show selected item in Comms Gauge:===
{{Table262|
Ensures that the visual indicator for which is the active item in the squad messaging menu is always shown. Useful if you are using the select Comms menu item keys. By default this is not shown until the player presses the up or down key for the select Comms menu item keys.
*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'''''

===$Fixed Chaining To Repeating Events:===
{{Table230|When set, this makes event chaining to repeated events work as designed - that is, the chained event will only be evaluated after the chain delay. If the repeating event's interval is shorter than the chain delay, then the delay countdown will continually be restarted until all repetitions have completed. Without this flag, FSO will emulate retail behavior which, due to a bug, allowed chained events to be evaluated immediately after a repeating event is first evaluated.

NOTE: Although the name does not reflect it, the same issue affects repeating events that are evaluated by <tt>is-event-true-delay</tt> and <tt>is-event-false-delay</tt>. Without this flag, FSO will emulate retail behavior which causes these SEXP operators to ignore any delay when evaluating repeated events. With this flag, the delay will be measured from when the final repeat iteration occurs.
*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'''''}}

===$Use model eyepoint for set-camera-host:===
{{Table250|The default behavior for set-camera-host is to position the camera at the origin coordinates (0,0,0) of the host. This flag will make the camera use the model eyepoint instead.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Use model eyepoint normals:===
{{Table250|If set, model eyepoints will respect the normal vector set for the eyepoint in the model file for the eyepoint. If not set, model eyepoints will use the model's orientation.
*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)'''''}}

===$HUD-set-coords base resolution:===
{{Table232|The hud-set-coords SEXP has always used exact pixels, without regard for the current screen resolution. This setting enables a similar scaling mechanism as ''$Show-subtitle base resolution:''.
*Syntax: '''''(Integer, Integer)'''''
*Default Value: '''''(-1, -1)'''''}}

===$Always Show Directive Value Count:===
{{Table250|
*If this setting is enabled, Directive-as-Value values in Directives will always show the number. By default this is disabled, and only values > 1 are shown.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

==#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'''''}}

===$EMP Pain Flash Factor:===
{{Table224|
Determines the intensity of the flash when the player is hit by an EMP blast or weapon.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$EMP Pain Flash Color:===
{{Table224|
Determines the RGB color value of the flash when the player is hit by an EMP blast or weapon.
*Syntax: Color, (red, green, blue) respectively, integer value from 0 to 255
*Default Value: '''''(255, 255, 127)'''''}}

===$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)
}}

===$EMP Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)
}}

===$Damage Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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.
{{Table262|
*Can now be an arbitrary non-zero number of floats. If not set to 4, you must table [[#$Shadow Smoothness Factor:]]
}}
*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.
{{Table262|
*Can now be an arbitrary non-zero number of floats. If not set to 4, you must table [[#$Shadow Smoothness Factor:]]
}}
*Syntax: '''''List of floats'''''
*Default Value: '''''(0.25, 0.75, 1.5, 3.0)'''''}}

{{Table262|
===$Shadow Smoothness Factor:===
Sets the strength of the smoothing for each shadow cascade. Larger values mean smoother / softer shadows. Shadow smoothness also scales with cascade distance, so the same value for a larger cascade will be perceived to be smoother.
The number of smoothness factors ''must'' match the number of Shadow Cockpit Cascades + Shadow Cascades (each 4 by default).
The list should first contain the smoothness factors for the cockpit cascades in order, and then the smoothness factors for the main cascades in order
*Syntax: '''''List of floats'''''
*Default Value: '''''(0.00333, 0.004, 0.005, 0.005, 0.00333, 0.004, 0.005, 0.005)'''''}}

===$Shadow Disable Techroom:===
{{Table224|
Disables shadows on ships in the techroom.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Cockpit:===
{{Table224|
Disables shadows on the player cockpit in mission.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Weapons:===
{{Table224|
Disables shadows on weapons in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Ships:===
{{Table224|
Disables shadows on ships in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Show Ship Casts Shadow:===
{{Table224|
When cockpit shadows are enabled, enabling this setting will cause the players ship model shown with "show ship" to cast shadow onto the cockpit.
*Syntax: '''''Boolean'''''
}}

===$Ship Model And Cockpit Share Coordinate Space:===
{{Table224|
When having the "show ship" flag enabled and cockpit models for a ship, this flag should be on if the cockpits can fit into the actual geometry of the ship model. Disable this flag if this is not the case and the cockpit needs to be rendered on top of the ship regardless of actual coordinates. If this can be enabled, the external show ship model can be rendered using deferred rendering.
*Syntax: '''''Boolean'''''
}}

===$Show Ship enabled only if Cockpits enabled:===
{{Table250|
Enabling this setting will only use the 'show-ship' flag if cockpits are enabled. Useful if your ship uses both 'show-ship' and cockpits that exist within the 'show-ship' space, and you want to allow players to toggle off cockpits. Note, 'show-ship' always only appears if in first-person view.
*Syntax: '''''Boolean'''''
}}

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

===$Do Not Render Lasers Below Length:===
{{Table250|
*Specifies the smallest length that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Do Not Render Lasers Below Radius:===
{{Table250|
*Specifies the smallest radius that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Thruster Easing Value:===
{{Table220|
*Smooths out the behavior of maneuvering thruster flares the higher above 0 it is.
*This is the exponential time constant for the visual flare length to reach it's true length.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

===$Primary Thruster Glow Depth Factor:===
{{Table262|
*This value is a multiplier of the Primary Thruster glow's computed size. By default Primary Thrusters showed through model geometry, but setting this value to <= 0 will fix the issue.
*Syntax: '''''Float'''''
*Default Value: 0.325f}}

===$Tertiary Thruster Glow Depth Factor:===
{{Table262|
*This value is a multiplier of the Tertiary Thruster glow's computed size. By default Tertiary Thrusters does not show through model geometry, but you could make it so by setting this value to > 0.
*Syntax: '''''Float'''''
*Default Value: 0.325f}}

===$SCPUI attempts to load hires animations:===
{{Table230|
*Prevents SCPUI from trying to load anims prefixed with "2_"
*Syntax: '''''Boolean'''''
*Default Value: true}}

{{Table230|
===$Max draw distance:===
===$Min draw distance:===
*These values do more than just cutoff the visuals at certain distances, and they must be adjusted carefully to ensure unintentional rendering artifacts are not introduced.
*The rendering engine has limited amount of 'depth resolution', the degree to which it can tell a certain polygon is closer or farther away than another. When two polygons are too close, they will Z-fight, picking arbitrarily which is closer. It is the span between the min and max draw distance that determines how well the engine can determine depth, if they are too far from one another, the Z-fighting will become more common as it has to spread its resolution over a wider range. If they are close, Z-fighting will be lessened at the cost of a smaller range of distance able to be rendered.
*Syntax: '''''Float''''', meters
*Default Values: 10,000,000,000 and 1, respectively
}}

{{Table232|
===$Randomize particle rotation:===
*Particle bitmaps are typically screen-aligned; the upper portion of the bitmap will always be mapped to the upper portion of the particle, from the point of view of the camera. Enabling this option makes ''all'' particles have a random 'tilt' in an arbitrary direction when created.
*Syntax: '''''Boolean'''''
*Default Value: false
}}

===$Disable shield effects:===
{{Table250|
*Specifies if FSO attempts to use the shield mesh impact effects. Enabling this flag will prevent the game from preforming any shield mesh effect code, which can be useful if a mod does not use those shield mesh effects.
*Syntax: '''''Boolean'''''
*Default Value: false}}

===$Disable all non-custom generic debris:===
{{Table250|
*Provides one simple control to turn off all non-custom generic debris (the tiny debris shards that are typically spawned when a ship/subsystem explodes). Note, generic debris that is manually specified in the ships table will still be spawned, this is only for turning off non-custom debris.
*Syntax: '''''Boolean'''''
*Default Value: false}}

===$Render insignias as decals:===
{{Table260|
*If set, insignias will be rendered using the decal system. This will make insignias render with correct and deferred lighting, and fix issues with apparent fading
*Models must be set up correctly for this to work! A model can have multiple insignias, with multiple polygon faces each. To enable this option, each visible insignia must have its own insignia entry in the model. If multiple visible insignias are incorrectly consolidated into one insignia entry with disjointed polygons, this will cause graphical artifacts.
*For reference, check out the retail FS2 models, which are set up correctly.
*Syntax: '''''Boolean'''''
*Default Value: false}}

==#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'''''}}

===$Use weapon class impact sounds for hits to player:===
{{Table224|
Allows weapons that hit the player to play their specific impact sounds, not the hard-coded default sounds.
*Syntax: '''''Boolean'''''
}}

===$Play thruster sounds for the player:===
{{Table232|
If the player's ship has thruster sounds defined, this will ensure they are played like normal, since they are typically suppressed.
*Syntax: '''''Boolean'''''
}}

===$Unify minimum engine sound:===
{{Table250|
Allows $Minimum Engine Volume in ships.tbl to work for all ship classes. By default, that value only triggers for non-huge ships.
*Syntax: '''''Boolean'''''
}}

===$Disabled or disrupted engines are silent:===
{{Table250|
If set, engines will not play their engine noise if the ship is disabled or a disrupted (such as disruptions caused by an active EMP effect or a weapon with the "electronics" flag).
*Syntax: '''''Boolean'''''
}}

==#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'''''}}

===$Add Message Head Ani Files:===
{{table224|
FRED will append each +Head entry listed below to the head ani selection list in the Event Editor.}}

====+Head:====
{{table224|
The head ani filename to add. Extensions will be stripped if included.
NOTE: Pay attention to file names or anis with a,b, c variation not display in-game (unless called directly). Proper name seems to be Head-xxxNa, Head-xxxNb, with N being some number and XXX being whatever you want. Needs further testing and confirmation
*Syntax: '''''+Head: String'''''}}

===$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'''''}}

===$FRED Briefing window resolution:===
{{table224|
The width and height of the briefing window in FRED. Defaults to 888x371. Note that changing this only affects FRED and can cause a mismatch to the ingame briefing view which defaults to 888x371 (or 555x232 for 640 base res).
*Syntax: '''''integer, integer'''''
*Default Value: '''''888,371'''''}}

===$Ignore Music Files In Music Player:===
{{table232|Music files in this section will not be added to FRED's built-in music player.}}
====+File:====
{{table232|Specifies a file
*Syntax: '''''string'''''}}

===$FRED spacemouse nonlinearities:===
{{table232|
Allows setting custom nonlinearities and scaling for controlling FRED with a spacemouse.
}}
====+Sideways exponent:====
{{table232|
The exponent for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Sideways scale:====
{{table232|The multiplier for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards exponent:====
{{table232|The exponent for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards scale:====
{{table232|The multiplier for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards exponent:====
{{table232|The exponent for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards scale:====
{{table232|The multiplier for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch exponent:====
{{table232|The exponent for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch scale:====
{{table232|The multiplier for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank exponent:====
{{table232|The exponent for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank scale:====
{{table232|The multiplier for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading exponent:====
{{table232|The exponent for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading scale:====
{{table232|The multiplier for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}

===$Skybox internal depth consistency:===
{{table250|If enabled, this will allow skyboxes that use submodels to render the submodels with proper Z-sorting if the 'No Z-Buffer' check box is set to on in FRED. In other words, parts of the skybox closer to the origin point will render in front of sections further away, as might be expected. This flag is enabled by default for FSO version 25.0 onwards
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

==#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. This fixes missile impacts to submodels whose center lies outside the geometry of the submodel. In other words, without this flag, a missile might detonate in the middle of the "bowl" of a concave submodel; with this flag, the missile will travel to the other side of the submodel before it detonates.
*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'''''

===$Use 3d ship select:===
{{Table224|
*Whether or not to use 3D models for ship select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d ship icons:===
{{Table224|
*Whether or not to use 3D models for ships in ship/weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d weapon select:===
{{Table224|
*Whether or not to use 3D models for weapon select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d weapon icons:===
{{Table224|
*Whether or not to use 3D models for weapons in weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$FS2 effect grid color:===
{{Table250|
*Specifies the grid color for the FS2 loadout animation effect
*Syntax: '''''Integer, Integer, Integer'''''
*Default Value: '''''0, 200, 0'''''}}

===$FS2 effect scanline color:===
{{Table250|
*Specifies the scan-line color for the FS2 loadout animation effect
*Syntax: '''''Integer, Integer, Integer'''''
*Default Value: '''''0, 255, 0'''''}}

===$FS2 effect grid density:===
{{Table250|
*Specifies the number of grid lines in the FS2 loadout animation effect
*Syntax: '''''Integer'''''
*Default Value: '''''7'''''}}

===$FS2 effect wireframe color:===
{{Table250|
*Specifies the wireframe color for the FS2 loadout animation effect
*Syntax: '''''Integer, Integer, Integer'''''
*Default Value: '''''80, 49, 160'''''}}

===$Use 3d overhead ship:===
{{Table224|
*Whether or not to use 3D models for ship overhead view instead of a bitmap in weapon select
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Default overhead ship style:===
{{Table224|
*This specifies which style of overhead view to use if 3d overhead view is active
*Syntax: '''''String'''''
*Possible options are "ROTATE" or "TOPVIEW"
}}
{{Table250|
*'''+Overhead Line Color 1:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (64, 192, 192)
*'''+Overhead Line Color 2:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (192, 128, 64)
*'''+Overhead Line Color 3:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (175, 175, 175)
*'''+Overhead Line Color 4:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (100, 100, 100)
}}

===$Always refresh selected weapon when viewing loadout:===
{{Table232|
*When set to true, this always refreshes the weapon shown in view box on the right side of the screen when opening the weapon loadout view. This ensures the viewed weapon is one that can actually be on the selected ship when first clicking on the weapon loadout screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$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'''''}}

===$Movie subtitle color:===
{{Table242|
*Specifies which color should be used for displaying subtitles in the cutscene player.
*Syntax: '''''Integer, Integer, Integer, Integer'''''
*Default Value: '''''255, 255, 255, 255'''''}}

===$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|
*Mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. By default is now ON, and can be accessed by going to the Options menu and pressing F3.
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

===$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'''''}}

===$Apply HUD shudder to chase view:===
{{Table232|
*Applies hud shudder (afterburner and engine wash) also to chase view. Does not override the command line toggle.
*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'''''}}

===$Lead indicator behavior:===
{{Table224|
Changes how Lead Indicators behave when multiple weapon banks are linked and in range.
When set to default, if you have linked weapons, only the indicator for the one with the farthest range will be drawn.
When set to multiple, a lead indicator is drawn for all primary weapons in range when you have them linked.
When set to average, a single lead indicator is drawn in the average of the position where each of them would usually be drawn.
*Syntax: '''''String'''''
** Valid options are '''''default''''', '''''multiple''''' and '''''average'''''
*Default Value: '''''default'''''
}}

===$Use distant firepoint for all turrets:===
{{Table224|
*Causes the game to use firepoint-based target leading calculations for all turrets. This is useful if all or most turrets in a given mod has firepoints that are distant from their center-point.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Enable Discord rich presence:===
{{Table224|
*Enables or disables the built-in Discord game-status reporting.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Always hide hidden ships in hotkey list:===
{{Table224|
*Whether or not to always hide ships with HIDDEN hotkey (set in FRED), even in the in-mission hotkey menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Allow automatically assigning personas:===
{{Table232|
*Whether or not the game will automatically assign personas to ships that have no persona set.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Countermeasures use capacity:===
{{Table232|
*Whether or not Countermeasures use tabled capacity.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Calculate subsystem hitpoints after parsing:===
{{Table234|
*Causes subsystem hitpoints to be calculated after all ships.tbl and -shp.tbm files have been parsed. This allows subsystem percentages to correctly reflect the final hull value rather than the first hull value encountered.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Contrails use absolute speed:===
{{Table240|
*Causes contrails to be created based on speed in any direction, rather than just forward speed. This allows contrails to appear when a ship is moving in a direction other than forwards.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix scripted velocity:===
{{Table242|
*If this setting is enabled, object velocity set via script will wholly determine the change in position for that frame, ignoring ''all'' other in-engine concerns. Otherwise, the game engine will likely overwrite/ignore any changes, depending on when the changes were made in the frame.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Preload briefing icon models:===
{{Table250|
*If set, this forces preloading of models used for briefing icons. This only loads models used for icons that haven't already been loaded for the mission. This is useful for SCPUI's where hovering over an icon shows the model without having to click on it and the stutter when it loads models not used in mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Behavior for pressing Escape key in options menu:===
{{Table250|
*If set to 'save', the escape key for the HUD and Options screen saves options when leaving those screens (ie it does the same thing as pressing Ctrl-Enter/Accept). By default (or if set to 'default') the Escape key will not save any changed values when exiting those screens.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Use closest distance method for 'Target Hostile Bomb or Bomber' control:===
{{Table250|
*If set to true, the 'Target Hostile Bomb or Bomber' control will target the closest hostile bomb or bomber, similar to how the 'Target Closest Hostile' key works. By default, the 'Target Hostile Bomb or Bomber' control will not sort by distance and simply only target in order of oldest to youngest objects (ie which object spawned first in the mission).
*Syntax: '''''Boolean'''''
*Default Value: '''''false'''''}}

===$Objects targeted with 'Target Hostile Bomb or Bomber' control:===
{{Table250|
*Determines what can be targeted when using the 'Target Hostile Bomb or Bomber' control. By default this control targets both bombs and bombers, which is the behavior if this field is set to 'default' or 'bombs and bombers'. If set to 'only bombs', the key will only target bombs and not target bombers. If set to 'only bombers', the key will only target bombers and not target bombs.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Fix asteroid/debris field bounding box checks:===
{{Table250|
*Fixes a bug where asteroid and debris fields did not properly check for whether large ships were within bounds.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable intro cutscene:===
{{Table250|
*If set, this disables loading of any cutscenes as the game starts that might play before the player reaches the pilot select screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Show locked status for scramble missions:===
{{Table250|
*If set, scramble mission will show a text line right below the words 'Weapons Loadout' that states "Ships/Weapons Locked" (XSTR 749), thus the player can easily see their loadouts are locked and they do not have to check the loaoout buttons on every mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable expensive turret target check:===
{{Table250|
*If set, this value speeds up turret target checking. By default, turret target acquisition was spending a lot of time doing a raycast, the result of which was barely used at all. If we don't need the target normal, all it does is get a target point slightly more accurate, but in practice it really isn't noticeable at all whether the target point of the turret is actually on the surface of the ship, or maybe on the other side of the ship.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Threshold below which shield skips damage:===
{{Table250|
*By default, FSO logic dictates that shields collisions and any related sound or visuals related to shields are skipped if the shields are under 10%. This value allows modders to customize the value, though the value must be between 0.0 and 1.0.
*Syntax: '''''Float'''''
*Default Value: '''''0.1'''''}}

===$Minimum ship radius for persistent debris::===
{{Table250|
*Ships with a radius larger than this value will have infinite debris lifetimes.
*Syntax: '''''Float'''''
*Default Value: '''''50'''''}}

===$Zero-radius explosions skip fireballs:===
{{Table260|
*If set, explosions with a visual radius of 0 will not have fireballs created, and will not have the fireball lifetime added to the explosion lifetime.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Link special-point subsystems to -destroyed submodels:===
{{Table260|
*If set, a special-point subsystem will be linked to its corresponding -destroyed submodel (if one exists). The -destroyed submodel will be shown when the subsystem is destroyed, and hidden again if the subsystem is repaired. By default, only submodel subsystems are linked to their corresponding -destroyed submodels.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix collision moment of inertia:===
{{Table262|
*Fixes a bug in collision physics where an object's moment of inertia was applied as though the object were facing the inverse of its actual orientation (that is, an orientation that would rotate it back to the identity orientation). Without this flag, a ship that is not aligned with the coordinate axes may rotate around the wrong axis, or by the wrong amount, when something collides with it. This applies to collisions among ships, asteroids, and debris. It does not apply to weapon impacts, which were never affected by the bug.
*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]]

Fate of the Galaxy

2026-09-05T11:44:38Z

Wookieejedi: /* Newsletter */

{{fotg}}

'''Fate of the Galaxy''' (FotG) is a free total conversion set in the ''[https://en.wikipedia.org/wiki/Star_Wars Star Wars]'' Original Trilogy. Developed using the open-source FreeSpace 2 Open (FSO) game engine, the project will be released as a standalone (the game FreeSpace 2 is not required). An active [https://fate-of-the-galaxy.github.io/ website], [https://www.hard-light.net/forums/index.php?board=143.0 forum] and [https://discord.gg/k7ZMdmt Discord Channel] are also maintained. As a disclaimer, Fate of the Galaxy is a total conversion for FreeSpace Open developed by a team of fan volunteers, it is not associated with Lucasfilm Ltd or Disney and is not an official Star Wars product

==Developers==
*'''chief1983:''' Project Lead
*'''Brand-X:''' Senior Artist and Content Moderator
*'''TopAce:''' Mission Design
*'''swashmebuckle:''' Music Composer, Writer
*'''zookeeper:''' Model Conversion, Artist, Scripting
*'''CountBuggula:''' Webmaster, Communications
*'''niffiwan:''' Coder
*'''wookieejedi:''' Mission Design, Scripting, Beta Management
*'''Limbert:''' Senior Artist
*'''bobbtmann:''' Senior Contributor
*'''Dark Visor:''' Senior Artist

''Full list of contributors is present in Credits screen of the game.''

==Gameplay==
In ''Fate of the Galaxy'' the player takes the role of a starfighter pilot through a series of missions and campaigns. The game is primarily played through the perspective of single-manned craft. There are no plans currently for player-control of capital ships, though certain player craft do allow for AI gunners. Current missions are set in space, including in asteroid fields, nebulas, and above planets. A multiplayer mode is also available to play and works well at low pings (~<100 ms). Standalone instances of the game are maintained, which allows players to easily join a server and play with friends.

The player will choose to play as a pilot for the Rebel Alliance, the Galactic Empire, or as an independent neutral adventurer/privateer. All factions have their own unique ships to control.

===Authenticity===
''Fate of the Galaxy'' strives to recreate combat as close to as seen in the Original Trilogy of ''Star Wars'', during scenes such as the [https://starwars.fandom.com/wiki/Battle_of_Endor/Legends Battle of Endor] and the [https://starwars.fandom.com/wiki/Battle_of_Yavin Battle of Yavin]. To achieve this, the members of the development team have extensively analyzed individual movements and moments within these scenes to determine a baseline for such game concepts as damage, speed, and maneuverability. Each fighter will stay as close as possible to its canonical statistics stated in various sources, but the final authority is the Original Trilogy movies themselves. Thus, many attributes may be contrary to other published materials due to their divergence from the Original Trilogy. In addition, visuals have been tuned to match the aesthetic of the Original Trilogy movies.

Given this focus on movie authenticity, the gameplay differs from that present in the default FreeSpace 2 universe. Ships will be much faster and combat quicker paced, with a larger focus on avoiding damage rather than absorbing it. Several coding features have been completed to create a new, unique style of combat.

==Vehicles==
The game includes multiple ships unique to each faction, with some designs being shared when appropriate. Each faction's fighters and capital ships have unique strengths, which presents different gameplay styles for each side.

===Alliance to Restore the Republic/New Republic===
[[Image:NuX.png|thumb|The X-wing Starfighter, main fighter of the Rebel Alliance]]
The Alliance to Restore the Republic and New Republic maintain a focus on versatile and durable starfighters and small, fast capital ships. Most of the Rebel fighters are equipped with secondary missile weapons such as concussion missiles or proton torpedoes. Rebel players will, in most cases, be unable to outmaneuver their Imperial counterparts and will rely on their superior durability and weapon complement, as well as teamwork to engage the enemy. Rebel capital ships are smaller than their Imperial counterparts, with each having diverse strengths due to their construction by various manufacturers. Rebel Mon Calamari Cruisers are noted for their incredible shield regeneration rates, while Corellian Corvettes are known for their speed.

The following Rebel/New Republic craft are included in the game:

*[https://starwars.fandom.com/wiki/X-wing_starfighter T-65 X-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL_Y-wing_starfighter BTL-A4 Y-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL-A4_LP_%22Longprobe%22 BTL-LP Longprobe Starfighter]
*[https://starwars.fandom.com/wiki/RZ-1_A-wing_interceptor RZ-1 A-wing Interceptor]
*[https://starwars.fandom.com/wiki/A/SF-01_B-wing_starfighter A/SF-01 B-wing Starfighter]
*[https://starwars.fandom.com/wiki/E-wing_escort_starfighter E-wing Escort Starfighter]
*[https://starwars.fandom.com/wiki/UT-60D_U-wing_starfighter/support_craft UT-60D U-wing]
*[https://starwars.fandom.com/wiki/Millennium_Falcon Millennium Falcon]

*[https://starwars.fandom.com/wiki/GR-75_medium_transport GR-75 Medium Transport]
*[https://starwars.fandom.com/wiki/CR90_corvette Corellian CR90 Corvette]
*[https://starwars.fandom.com/wiki/EF76_Nebulon-B_escort_frigate EF76 Nebulon-B Escort Frigate]
*[https://starwars.fandom.com/wiki/MC30C_frigate MC30 Heavy Frigate]
*[https://starwars.fandom.com/wiki/MC40a_light_cruiser MC40 Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Liberty_type_Star_Cruiser ''Liberty''-class Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Home_One_type_Star_Cruiser ''Home One''-class Star Cruiser]

===Galactic Empire===
[[Image:NuRTIE03.jpg|thumb|The TIE/ln Starfighter, main fighter of the Galactic Empire]]
The Galactic Empire's main strategy for fighters revolves around the concept of numerical advantage. Imperial TIEs usually lack shields and durability, but have very potent weaponry and great maneuverability to counter this weakness. Most Imperial fighters also forego any sort of missile secondary weapons and focus entirely on their lasers for offensive armament. Imperial capital ships are much larger than those of the Rebels, and focus on heavy offensive weaponry and great hull durability.

The following Imperial craft are included in the game:

*[https://starwars.fandom.com/wiki/TIE/LN_starfighter T.I.E. Starfighter & TIE/ln Starfighter]
*[https://starwars.fandom.com/wiki/TIE_Reconnaissance_Fighter TIE/rc Recon Fighter]
*[https://starwars.fandom.com/wiki/TIE/IN_interceptor TIE/In Interceptor Mark I and Mark II]
*[https://starwars.fandom.com/wiki/TIE/sa_bomber TIE/sa Bomber]
*[https://starwars.fandom.com/wiki/TIE_Advanced_x1 TIE Advanced x1]
*[https://starwars.fandom.com/wiki/V38_assault_fighter V38 Assault Fighter]

*[https://starwars.fandom.com/wiki/TIE/sh_shuttle TIE/sh Shuttle]
*[https://starwars.fandom.com/wiki/Alpha-class_Xg-1_Star_Wing Xg-1 Star Wing]
*[https://starwars.fandom.com/wiki/Delta-class_DX-9_stormtrooper_transport DX-9 Stormtrooper Transport]
*[https://starwars.fandom.com/wiki/Lambda-class_T-4a_shuttle Lambda-class T-4a Shuttle]
*[https://starwars.fandom.com/wiki/Zeta-class_Heavy_Cargo_Shuttle Zeta-class Heavy Cargo Shuttle]

*[https://starwars.fandom.com/wiki/All_Terrain_Armored_Transport ''All Terrain Armored Transport'']
*[https://starwars.fandom.com/wiki/Gozanti-class_cruiser ''Gozanti''-class Cruiser]

*[https://starwars.fandom.com/wiki/Raider-class_corvette ''Raider''-class Corvette]
*[https://starwars.fandom.com/wiki/Carrack-class_light_cruiser ''Carrack''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Arquitens-class_light_cruiser ''Arquitens''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Strike-class_medium_cruiser ''Strike''-class Medium Cruiser]
*[https://starwars.fandom.com/wiki/Vindicator-class_heavy_cruiser ''Vindicator''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Interdictor_vessel ''Interdictor''-class Cruiser]
*[https://starwars.fandom.com/wiki/Imperial_II-class_Star_Destroyer ''Imperator II''-class Star Destroyer]
*[https://starwars.fandom.com/wiki/Golan_space_defense_platform Golan M-series Dockyard Platforms]
*[https://starwars.fandom.com/wiki/Shield_Gate Golan M-3185 Shield Gate Station]

===Neutral===
There are multiple factions in the Star Wars galaxy which use many craft that are not produced for the Galactic Empire or the Rebel Alliance. These craft vary in characteristics and are used throughout the galaxy in various roles.

The following Neutral craft are included in the game:

*[https://starwars.fandom.com/wiki/Z-95_Headhunter Z-95 Headhunter]
*[https://starwars.fandom.com/wiki/CloakShape_fighter/Legends Cloakshape Starfighter]
*[https://starwars.fandom.com/wiki/N-1_starfighter N-1 Naboo Starfighter]
*[https://starwars.fandom.com/wiki/Alpha-3_Nimbus-class_V-wing_starfighter Alpha-3 Nimbus-class V-wing Starfighter]
*[https://starwars.fandom.com/wiki/Aggressive_ReConnaissance-170_starfighter/Legends ARC-170 Starfighter]
*[https://starwars.fandom.com/wiki/Vulture-class_starfighter Vulture-class_starfighter]
*[https://starwars.fandom.com/wiki/Ugly/Legends Various Uglies]
*[https://starwars.fandom.com/wiki/Firespray-31-class_patrol_and_attack_craft Firespray-31-class Gunship]
*[https://starwars.fandom.com/wiki/Slave_I Slave I]
*[https://starwars.fandom.com/wiki/YT-1300_light_freighter YT-1300 Light Freighter]
*[https://starwars.fandom.com/wiki/BFF-1_bulk_freighter BFF-1 Bulk Freighter]
*[https://starwars.fandom.com/wiki/Tug DV-3 Cargo Freighter]
*[https://starwars.fandom.com/wiki/Action_VI_transport Action VI Transport]
*[https://starwars.fandom.com/wiki/Transport Rayter-class Transport]
*[https://starwars.fandom.com/wiki/CSS-1_Corellian_Star_Shuttle Star Shuttle]
*[https://starwars.fandom.com/wiki/StarSpeeder_1000 Star Speeder]
*[https://starwars.fandom.com/wiki/GAT-12_Skipray_Blastboat GAT-10 Skipray Blastboat]
*[https://starwars.fandom.com/wiki/Consular-class_cruiser_(Charger_c70_retrofit) Corellian Charger C70 Retrofit]
*[https://starwars.fandom.com/wiki/Braha'tok-class_gunship Braha'tok-class gunship]
*[https://starwars.fandom.com/wiki/Marauder-class_corvette Marauder-class corvette]
*[https://starwars.fandom.com/wiki/Dreadnaught-class_heavy_cruiser ''Dreadnaught''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Venator-class_Star_Destroyer ''Venator''-class Cruiser]
*[https://starwars.fandom.com/wiki/XQ_Platform_series XQ1 and XQ2 Stations]
*[https://starwars.fandom.com/wiki/Asteroid_base Asteroid Base Station]
*[https://starwars.fandom.com/wiki/Repair_droid Dockyard Repair Droids]
*[https://starwars.fandom.com/wiki/Satellite/Legends Sensor and Defense Satellites]
*[https://starwars.fandom.com/wiki/Space_mine Space Mines]

==Missions and Campaigns==
''Fate of the Galaxy'' comes with a high level of single-player content. These include multiple campaigns, standalone missions, and the ability to create missions using the FSO mission editor FRED2. Multiplayer servers are also maintained and available to play on with friends.

The first three campaigns narrate three interconnected stories set at the beginning of the Galactic Civil War. Each of these three campaigns consists of about 5 missions, thus designers put high emphasis on quality mission design and high replayability. The player's performance throughout the campaign will affect how later missions play out. For example, the Alliance campaign will pit a ragtag Rebel task force against a dreaded ''Imperial''-class Star Destroyer in the early stages of the Rebellion, and the player's performance throughout the campaign has a major impact on this encounter's difficulty. The best possible outcome is hard to achieve, thus a number of playthroughs will be required.

Players receive different types of training in different campaigns. The Alliance mini-campaign starts with a basic training mission that teaches the basics to new players along with gameplay features that are unique to ''Fate of the Galaxy'''. The Imperial mini-campaign starts with an advanced training.

Standalone missions are also included in the first release. Many of them are serious, story-driven missions, but there will also be arcade-like "challenge" missions in which the player must accomplish a wide variety of objectives, such as surviving two minutes within a ''Strike''-class cruiser's firing range. There will also be a Practice Zone mission, where the player can test flying any of the small craft and actively spawn in any craft in the mission as a hostile or friendly to practice combat.

Three additional campaigns are being worked on and will be available when the game is released to the public, but specific details remain under embargo until public launch. This large component is code-named Project Alderaan.

==Development==
[[Image:Ewingmaps.jpg|thumb|The progression of model work shown on an E-wing Starfighter, from Model (Right) to Normal Maps (Center) and Diffuse Texture (Left). Note that this model will not be used.]]
Fate of the Galaxy picks up after a number of previous attempts to create a ''Star Wars'' mod for FreeSpace. For several years the "Star Wars Conversion Project" was worked on by various teams and developers, but without any releases.

In early 2007, chief1983 took over as project leader, and began to assemble a new team of developers. Choosing the name ''Fate of the Galaxy'', the initial team consisted of chief1983, Brand-X as a modeler and Turambar as a texturer. The initial plan put forward was to use the models and textures that had been completed by previous teams. Soon after the reformation of the mod team, however, it was decided that all new art assets were needed to compete with the high graphical standards of the newer models, and all previously completed ships were discarded.

Work continued on ship models and textures through the next year and a half, as new staff members were added to the development team. In May of 2008, work began on implementing the new ship models into the game and work began on redesigning the feel and pace of the FreeSpace 2 Open engine. Work still continued on the models needed for a campaign and demo release.

In early January of 2009, Brand-X experienced a hard drive failure which destroyed all previous models of his, setting the team's art department back significantly. Since then, work has progressed on recreating these models to even higher quality standards.

On June 4th, 2009, the first in-game screenshot of the X-wing starfighter was made public at the [http://www.moddb.com/games/fate-of-the-galaxy/images/x-wing-in-game-shots2#imagebox ModDB site] and at the official FotG [https://www.hard-light.net/forums/index.php?board=143.0 forums]. The first three campaigns, which are set at the beginning of the Galactic Civil War, were eventually completed, and worked then moved to standalone missions and three additional campaigns code-named Project Alderaan.

In December of 2018 the team began the first phases of private beta testing. In June of 2022, the private beta tests were stated as nearly concluded.

In May of 2019 the [https://www.youtube.com/watch?v=ler20EdjAfs&list=LLW8-wdcPLv0eT913KIi9_mw&index=2&t=0s teaser trailer] was posted.

Throughout 2020-2022 developmental showcases have consisted of forum updates and gameplay streams on Discord.

In June of 2022, multiplayer was confirmed to be working well, and standalone servers were created.

From 2023-2024, the game underwent extensive balance and optimization testing in preparation for the public release.

For the duration of 2025, additional polishing passes were conducted and continue to be refined.

===Newsletter===
Newsletters are posted on a quarterly basis on the [https://www.hard-light.net/forums/index.php?board=143.0 Fate of the Galaxy Forums]. Also, the majority of the unofficial development chatter occurs on the Fate of the Galaxy Discord channel [https://discord.gg/k7ZMdmt].

The most recent [https://www.hard-light.net/forums/index.php?topic=100129.0 newsletter] was released in August 2026. This update highlights new effect additions, many other enhancements, and numerous fixes and minor updates.

For reference, the [http://www.hard-light.net/forums/index.php/topic,54217.0.html first newsletter] was posted on June 1st, 2008.

===First Release===
The first open beta of ''Fate of the Galaxy'' was originally planned to be released sometime late-2008 or early 2009. However, with the art setback, the release has been pushed back. Subsequent additions and developments then lead the team to decide to release the game as a more polished 1.0 version. A date has not been decided yet, but the first three campaigns are done and relatively independent compared to the larger subsequent 3 campaigns.

Recent years have shown considerable progress on the project, including a release of a private beta and addition of multiple ships and integrating new features that were recently added to the FSO engine (such as deferred and shadow lighting for cockpits, optimizations, and advanced scripting controls).

In the most recent communications on Discord, co-community manager wookieejedi posted: "''We are primarily waiting on FSO 26.0.1 Stable, and guarantee FotG will be released before GTA6''" (September 2th, 2026).

==Gallery==
===Ship Lab shots===
<gallery>
Image:Bwing.jpg
Image:Falcon2.jpg
Image:Xwing.jpg
Image:Ywing2.jpg
Image:Z95.jpg |
</gallery>
===Renders===
<gallery>
Image:FalconWallpaper.png
Image:TBrender.png
Image:TransportFinal.jpg
Image:Wallpaper.1-1280.png
Image:Wallpaper.2-1280.png
</gallery>

==Links==
*[http://swc.hard-light.net/ Official Website]
*[https://discord.gg/k7ZMdmt Fate of the Galaxy Discord Server]
*[https://www.hard-light.net/forums/index.php?board=143.0 Official Forum]
*[https://www.moddb.com/games/fate-of-the-galaxy Fate of the Galaxy on ModDB]

Fate of the Galaxy

2026-09-05T11:43:56Z

Wookieejedi: /* Newsletter */

{{fotg}}

'''Fate of the Galaxy''' (FotG) is a free total conversion set in the ''[https://en.wikipedia.org/wiki/Star_Wars Star Wars]'' Original Trilogy. Developed using the open-source FreeSpace 2 Open (FSO) game engine, the project will be released as a standalone (the game FreeSpace 2 is not required). An active [https://fate-of-the-galaxy.github.io/ website], [https://www.hard-light.net/forums/index.php?board=143.0 forum] and [https://discord.gg/k7ZMdmt Discord Channel] are also maintained. As a disclaimer, Fate of the Galaxy is a total conversion for FreeSpace Open developed by a team of fan volunteers, it is not associated with Lucasfilm Ltd or Disney and is not an official Star Wars product

==Developers==
*'''chief1983:''' Project Lead
*'''Brand-X:''' Senior Artist and Content Moderator
*'''TopAce:''' Mission Design
*'''swashmebuckle:''' Music Composer, Writer
*'''zookeeper:''' Model Conversion, Artist, Scripting
*'''CountBuggula:''' Webmaster, Communications
*'''niffiwan:''' Coder
*'''wookieejedi:''' Mission Design, Scripting, Beta Management
*'''Limbert:''' Senior Artist
*'''bobbtmann:''' Senior Contributor
*'''Dark Visor:''' Senior Artist

''Full list of contributors is present in Credits screen of the game.''

==Gameplay==
In ''Fate of the Galaxy'' the player takes the role of a starfighter pilot through a series of missions and campaigns. The game is primarily played through the perspective of single-manned craft. There are no plans currently for player-control of capital ships, though certain player craft do allow for AI gunners. Current missions are set in space, including in asteroid fields, nebulas, and above planets. A multiplayer mode is also available to play and works well at low pings (~<100 ms). Standalone instances of the game are maintained, which allows players to easily join a server and play with friends.

The player will choose to play as a pilot for the Rebel Alliance, the Galactic Empire, or as an independent neutral adventurer/privateer. All factions have their own unique ships to control.

===Authenticity===
''Fate of the Galaxy'' strives to recreate combat as close to as seen in the Original Trilogy of ''Star Wars'', during scenes such as the [https://starwars.fandom.com/wiki/Battle_of_Endor/Legends Battle of Endor] and the [https://starwars.fandom.com/wiki/Battle_of_Yavin Battle of Yavin]. To achieve this, the members of the development team have extensively analyzed individual movements and moments within these scenes to determine a baseline for such game concepts as damage, speed, and maneuverability. Each fighter will stay as close as possible to its canonical statistics stated in various sources, but the final authority is the Original Trilogy movies themselves. Thus, many attributes may be contrary to other published materials due to their divergence from the Original Trilogy. In addition, visuals have been tuned to match the aesthetic of the Original Trilogy movies.

Given this focus on movie authenticity, the gameplay differs from that present in the default FreeSpace 2 universe. Ships will be much faster and combat quicker paced, with a larger focus on avoiding damage rather than absorbing it. Several coding features have been completed to create a new, unique style of combat.

==Vehicles==
The game includes multiple ships unique to each faction, with some designs being shared when appropriate. Each faction's fighters and capital ships have unique strengths, which presents different gameplay styles for each side.

===Alliance to Restore the Republic/New Republic===
[[Image:NuX.png|thumb|The X-wing Starfighter, main fighter of the Rebel Alliance]]
The Alliance to Restore the Republic and New Republic maintain a focus on versatile and durable starfighters and small, fast capital ships. Most of the Rebel fighters are equipped with secondary missile weapons such as concussion missiles or proton torpedoes. Rebel players will, in most cases, be unable to outmaneuver their Imperial counterparts and will rely on their superior durability and weapon complement, as well as teamwork to engage the enemy. Rebel capital ships are smaller than their Imperial counterparts, with each having diverse strengths due to their construction by various manufacturers. Rebel Mon Calamari Cruisers are noted for their incredible shield regeneration rates, while Corellian Corvettes are known for their speed.

The following Rebel/New Republic craft are included in the game:

*[https://starwars.fandom.com/wiki/X-wing_starfighter T-65 X-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL_Y-wing_starfighter BTL-A4 Y-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL-A4_LP_%22Longprobe%22 BTL-LP Longprobe Starfighter]
*[https://starwars.fandom.com/wiki/RZ-1_A-wing_interceptor RZ-1 A-wing Interceptor]
*[https://starwars.fandom.com/wiki/A/SF-01_B-wing_starfighter A/SF-01 B-wing Starfighter]
*[https://starwars.fandom.com/wiki/E-wing_escort_starfighter E-wing Escort Starfighter]
*[https://starwars.fandom.com/wiki/UT-60D_U-wing_starfighter/support_craft UT-60D U-wing]
*[https://starwars.fandom.com/wiki/Millennium_Falcon Millennium Falcon]

*[https://starwars.fandom.com/wiki/GR-75_medium_transport GR-75 Medium Transport]
*[https://starwars.fandom.com/wiki/CR90_corvette Corellian CR90 Corvette]
*[https://starwars.fandom.com/wiki/EF76_Nebulon-B_escort_frigate EF76 Nebulon-B Escort Frigate]
*[https://starwars.fandom.com/wiki/MC30C_frigate MC30 Heavy Frigate]
*[https://starwars.fandom.com/wiki/MC40a_light_cruiser MC40 Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Liberty_type_Star_Cruiser ''Liberty''-class Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Home_One_type_Star_Cruiser ''Home One''-class Star Cruiser]

===Galactic Empire===
[[Image:NuRTIE03.jpg|thumb|The TIE/ln Starfighter, main fighter of the Galactic Empire]]
The Galactic Empire's main strategy for fighters revolves around the concept of numerical advantage. Imperial TIEs usually lack shields and durability, but have very potent weaponry and great maneuverability to counter this weakness. Most Imperial fighters also forego any sort of missile secondary weapons and focus entirely on their lasers for offensive armament. Imperial capital ships are much larger than those of the Rebels, and focus on heavy offensive weaponry and great hull durability.

The following Imperial craft are included in the game:

*[https://starwars.fandom.com/wiki/TIE/LN_starfighter T.I.E. Starfighter & TIE/ln Starfighter]
*[https://starwars.fandom.com/wiki/TIE_Reconnaissance_Fighter TIE/rc Recon Fighter]
*[https://starwars.fandom.com/wiki/TIE/IN_interceptor TIE/In Interceptor Mark I and Mark II]
*[https://starwars.fandom.com/wiki/TIE/sa_bomber TIE/sa Bomber]
*[https://starwars.fandom.com/wiki/TIE_Advanced_x1 TIE Advanced x1]
*[https://starwars.fandom.com/wiki/V38_assault_fighter V38 Assault Fighter]

*[https://starwars.fandom.com/wiki/TIE/sh_shuttle TIE/sh Shuttle]
*[https://starwars.fandom.com/wiki/Alpha-class_Xg-1_Star_Wing Xg-1 Star Wing]
*[https://starwars.fandom.com/wiki/Delta-class_DX-9_stormtrooper_transport DX-9 Stormtrooper Transport]
*[https://starwars.fandom.com/wiki/Lambda-class_T-4a_shuttle Lambda-class T-4a Shuttle]
*[https://starwars.fandom.com/wiki/Zeta-class_Heavy_Cargo_Shuttle Zeta-class Heavy Cargo Shuttle]

*[https://starwars.fandom.com/wiki/All_Terrain_Armored_Transport ''All Terrain Armored Transport'']
*[https://starwars.fandom.com/wiki/Gozanti-class_cruiser ''Gozanti''-class Cruiser]

*[https://starwars.fandom.com/wiki/Raider-class_corvette ''Raider''-class Corvette]
*[https://starwars.fandom.com/wiki/Carrack-class_light_cruiser ''Carrack''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Arquitens-class_light_cruiser ''Arquitens''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Strike-class_medium_cruiser ''Strike''-class Medium Cruiser]
*[https://starwars.fandom.com/wiki/Vindicator-class_heavy_cruiser ''Vindicator''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Interdictor_vessel ''Interdictor''-class Cruiser]
*[https://starwars.fandom.com/wiki/Imperial_II-class_Star_Destroyer ''Imperator II''-class Star Destroyer]
*[https://starwars.fandom.com/wiki/Golan_space_defense_platform Golan M-series Dockyard Platforms]
*[https://starwars.fandom.com/wiki/Shield_Gate Golan M-3185 Shield Gate Station]

===Neutral===
There are multiple factions in the Star Wars galaxy which use many craft that are not produced for the Galactic Empire or the Rebel Alliance. These craft vary in characteristics and are used throughout the galaxy in various roles.

The following Neutral craft are included in the game:

*[https://starwars.fandom.com/wiki/Z-95_Headhunter Z-95 Headhunter]
*[https://starwars.fandom.com/wiki/CloakShape_fighter/Legends Cloakshape Starfighter]
*[https://starwars.fandom.com/wiki/N-1_starfighter N-1 Naboo Starfighter]
*[https://starwars.fandom.com/wiki/Alpha-3_Nimbus-class_V-wing_starfighter Alpha-3 Nimbus-class V-wing Starfighter]
*[https://starwars.fandom.com/wiki/Aggressive_ReConnaissance-170_starfighter/Legends ARC-170 Starfighter]
*[https://starwars.fandom.com/wiki/Vulture-class_starfighter Vulture-class_starfighter]
*[https://starwars.fandom.com/wiki/Ugly/Legends Various Uglies]
*[https://starwars.fandom.com/wiki/Firespray-31-class_patrol_and_attack_craft Firespray-31-class Gunship]
*[https://starwars.fandom.com/wiki/Slave_I Slave I]
*[https://starwars.fandom.com/wiki/YT-1300_light_freighter YT-1300 Light Freighter]
*[https://starwars.fandom.com/wiki/BFF-1_bulk_freighter BFF-1 Bulk Freighter]
*[https://starwars.fandom.com/wiki/Tug DV-3 Cargo Freighter]
*[https://starwars.fandom.com/wiki/Action_VI_transport Action VI Transport]
*[https://starwars.fandom.com/wiki/Transport Rayter-class Transport]
*[https://starwars.fandom.com/wiki/CSS-1_Corellian_Star_Shuttle Star Shuttle]
*[https://starwars.fandom.com/wiki/StarSpeeder_1000 Star Speeder]
*[https://starwars.fandom.com/wiki/GAT-12_Skipray_Blastboat GAT-10 Skipray Blastboat]
*[https://starwars.fandom.com/wiki/Consular-class_cruiser_(Charger_c70_retrofit) Corellian Charger C70 Retrofit]
*[https://starwars.fandom.com/wiki/Braha'tok-class_gunship Braha'tok-class gunship]
*[https://starwars.fandom.com/wiki/Marauder-class_corvette Marauder-class corvette]
*[https://starwars.fandom.com/wiki/Dreadnaught-class_heavy_cruiser ''Dreadnaught''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Venator-class_Star_Destroyer ''Venator''-class Cruiser]
*[https://starwars.fandom.com/wiki/XQ_Platform_series XQ1 and XQ2 Stations]
*[https://starwars.fandom.com/wiki/Asteroid_base Asteroid Base Station]
*[https://starwars.fandom.com/wiki/Repair_droid Dockyard Repair Droids]
*[https://starwars.fandom.com/wiki/Satellite/Legends Sensor and Defense Satellites]
*[https://starwars.fandom.com/wiki/Space_mine Space Mines]

==Missions and Campaigns==
''Fate of the Galaxy'' comes with a high level of single-player content. These include multiple campaigns, standalone missions, and the ability to create missions using the FSO mission editor FRED2. Multiplayer servers are also maintained and available to play on with friends.

The first three campaigns narrate three interconnected stories set at the beginning of the Galactic Civil War. Each of these three campaigns consists of about 5 missions, thus designers put high emphasis on quality mission design and high replayability. The player's performance throughout the campaign will affect how later missions play out. For example, the Alliance campaign will pit a ragtag Rebel task force against a dreaded ''Imperial''-class Star Destroyer in the early stages of the Rebellion, and the player's performance throughout the campaign has a major impact on this encounter's difficulty. The best possible outcome is hard to achieve, thus a number of playthroughs will be required.

Players receive different types of training in different campaigns. The Alliance mini-campaign starts with a basic training mission that teaches the basics to new players along with gameplay features that are unique to ''Fate of the Galaxy'''. The Imperial mini-campaign starts with an advanced training.

Standalone missions are also included in the first release. Many of them are serious, story-driven missions, but there will also be arcade-like "challenge" missions in which the player must accomplish a wide variety of objectives, such as surviving two minutes within a ''Strike''-class cruiser's firing range. There will also be a Practice Zone mission, where the player can test flying any of the small craft and actively spawn in any craft in the mission as a hostile or friendly to practice combat.

Three additional campaigns are being worked on and will be available when the game is released to the public, but specific details remain under embargo until public launch. This large component is code-named Project Alderaan.

==Development==
[[Image:Ewingmaps.jpg|thumb|The progression of model work shown on an E-wing Starfighter, from Model (Right) to Normal Maps (Center) and Diffuse Texture (Left). Note that this model will not be used.]]
Fate of the Galaxy picks up after a number of previous attempts to create a ''Star Wars'' mod for FreeSpace. For several years the "Star Wars Conversion Project" was worked on by various teams and developers, but without any releases.

In early 2007, chief1983 took over as project leader, and began to assemble a new team of developers. Choosing the name ''Fate of the Galaxy'', the initial team consisted of chief1983, Brand-X as a modeler and Turambar as a texturer. The initial plan put forward was to use the models and textures that had been completed by previous teams. Soon after the reformation of the mod team, however, it was decided that all new art assets were needed to compete with the high graphical standards of the newer models, and all previously completed ships were discarded.

Work continued on ship models and textures through the next year and a half, as new staff members were added to the development team. In May of 2008, work began on implementing the new ship models into the game and work began on redesigning the feel and pace of the FreeSpace 2 Open engine. Work still continued on the models needed for a campaign and demo release.

In early January of 2009, Brand-X experienced a hard drive failure which destroyed all previous models of his, setting the team's art department back significantly. Since then, work has progressed on recreating these models to even higher quality standards.

On June 4th, 2009, the first in-game screenshot of the X-wing starfighter was made public at the [http://www.moddb.com/games/fate-of-the-galaxy/images/x-wing-in-game-shots2#imagebox ModDB site] and at the official FotG [https://www.hard-light.net/forums/index.php?board=143.0 forums]. The first three campaigns, which are set at the beginning of the Galactic Civil War, were eventually completed, and worked then moved to standalone missions and three additional campaigns code-named Project Alderaan.

In December of 2018 the team began the first phases of private beta testing. In June of 2022, the private beta tests were stated as nearly concluded.

In May of 2019 the [https://www.youtube.com/watch?v=ler20EdjAfs&list=LLW8-wdcPLv0eT913KIi9_mw&index=2&t=0s teaser trailer] was posted.

Throughout 2020-2022 developmental showcases have consisted of forum updates and gameplay streams on Discord.

In June of 2022, multiplayer was confirmed to be working well, and standalone servers were created.

From 2023-2024, the game underwent extensive balance and optimization testing in preparation for the public release.

For the duration of 2025, additional polishing passes were conducted and continue to be refined.

===Newsletter===
Newsletters are posted on a quarterly basis on the [https://www.hard-light.net/forums/index.php?board=143.0 Fate of the Galaxy Forums]. Also, the majority of the unofficial development chatter occurs on the Fate of the Galaxy Discord channel [https://discord.gg/k7ZMdmt].

The most recent [https://www.hard-light.net/forums/index.php?topic=100129.0] was released in August 2026. This update highlights new effect additions, many other enhancements, and numerous fixes and minor updates.

For reference, the [http://www.hard-light.net/forums/index.php/topic,54217.0.html first newsletter] was posted on June 1st, 2008.

===First Release===
The first open beta of ''Fate of the Galaxy'' was originally planned to be released sometime late-2008 or early 2009. However, with the art setback, the release has been pushed back. Subsequent additions and developments then lead the team to decide to release the game as a more polished 1.0 version. A date has not been decided yet, but the first three campaigns are done and relatively independent compared to the larger subsequent 3 campaigns.

Recent years have shown considerable progress on the project, including a release of a private beta and addition of multiple ships and integrating new features that were recently added to the FSO engine (such as deferred and shadow lighting for cockpits, optimizations, and advanced scripting controls).

In the most recent communications on Discord, co-community manager wookieejedi posted: "''We are primarily waiting on FSO 26.0.1 Stable, and guarantee FotG will be released before GTA6''" (September 2th, 2026).

==Gallery==
===Ship Lab shots===
<gallery>
Image:Bwing.jpg
Image:Falcon2.jpg
Image:Xwing.jpg
Image:Ywing2.jpg
Image:Z95.jpg |
</gallery>
===Renders===
<gallery>
Image:FalconWallpaper.png
Image:TBrender.png
Image:TransportFinal.jpg
Image:Wallpaper.1-1280.png
Image:Wallpaper.2-1280.png
</gallery>

==Links==
*[http://swc.hard-light.net/ Official Website]
*[https://discord.gg/k7ZMdmt Fate of the Galaxy Discord Server]
*[https://www.hard-light.net/forums/index.php?board=143.0 Official Forum]
*[https://www.moddb.com/games/fate-of-the-galaxy Fate of the Galaxy on ModDB]

Fate of the Galaxy

2026-09-05T11:40:23Z

Wookieejedi: Release window update

{{fotg}}

'''Fate of the Galaxy''' (FotG) is a free total conversion set in the ''[https://en.wikipedia.org/wiki/Star_Wars Star Wars]'' Original Trilogy. Developed using the open-source FreeSpace 2 Open (FSO) game engine, the project will be released as a standalone (the game FreeSpace 2 is not required). An active [https://fate-of-the-galaxy.github.io/ website], [https://www.hard-light.net/forums/index.php?board=143.0 forum] and [https://discord.gg/k7ZMdmt Discord Channel] are also maintained. As a disclaimer, Fate of the Galaxy is a total conversion for FreeSpace Open developed by a team of fan volunteers, it is not associated with Lucasfilm Ltd or Disney and is not an official Star Wars product

==Developers==
*'''chief1983:''' Project Lead
*'''Brand-X:''' Senior Artist and Content Moderator
*'''TopAce:''' Mission Design
*'''swashmebuckle:''' Music Composer, Writer
*'''zookeeper:''' Model Conversion, Artist, Scripting
*'''CountBuggula:''' Webmaster, Communications
*'''niffiwan:''' Coder
*'''wookieejedi:''' Mission Design, Scripting, Beta Management
*'''Limbert:''' Senior Artist
*'''bobbtmann:''' Senior Contributor
*'''Dark Visor:''' Senior Artist

''Full list of contributors is present in Credits screen of the game.''

==Gameplay==
In ''Fate of the Galaxy'' the player takes the role of a starfighter pilot through a series of missions and campaigns. The game is primarily played through the perspective of single-manned craft. There are no plans currently for player-control of capital ships, though certain player craft do allow for AI gunners. Current missions are set in space, including in asteroid fields, nebulas, and above planets. A multiplayer mode is also available to play and works well at low pings (~<100 ms). Standalone instances of the game are maintained, which allows players to easily join a server and play with friends.

The player will choose to play as a pilot for the Rebel Alliance, the Galactic Empire, or as an independent neutral adventurer/privateer. All factions have their own unique ships to control.

===Authenticity===
''Fate of the Galaxy'' strives to recreate combat as close to as seen in the Original Trilogy of ''Star Wars'', during scenes such as the [https://starwars.fandom.com/wiki/Battle_of_Endor/Legends Battle of Endor] and the [https://starwars.fandom.com/wiki/Battle_of_Yavin Battle of Yavin]. To achieve this, the members of the development team have extensively analyzed individual movements and moments within these scenes to determine a baseline for such game concepts as damage, speed, and maneuverability. Each fighter will stay as close as possible to its canonical statistics stated in various sources, but the final authority is the Original Trilogy movies themselves. Thus, many attributes may be contrary to other published materials due to their divergence from the Original Trilogy. In addition, visuals have been tuned to match the aesthetic of the Original Trilogy movies.

Given this focus on movie authenticity, the gameplay differs from that present in the default FreeSpace 2 universe. Ships will be much faster and combat quicker paced, with a larger focus on avoiding damage rather than absorbing it. Several coding features have been completed to create a new, unique style of combat.

==Vehicles==
The game includes multiple ships unique to each faction, with some designs being shared when appropriate. Each faction's fighters and capital ships have unique strengths, which presents different gameplay styles for each side.

===Alliance to Restore the Republic/New Republic===
[[Image:NuX.png|thumb|The X-wing Starfighter, main fighter of the Rebel Alliance]]
The Alliance to Restore the Republic and New Republic maintain a focus on versatile and durable starfighters and small, fast capital ships. Most of the Rebel fighters are equipped with secondary missile weapons such as concussion missiles or proton torpedoes. Rebel players will, in most cases, be unable to outmaneuver their Imperial counterparts and will rely on their superior durability and weapon complement, as well as teamwork to engage the enemy. Rebel capital ships are smaller than their Imperial counterparts, with each having diverse strengths due to their construction by various manufacturers. Rebel Mon Calamari Cruisers are noted for their incredible shield regeneration rates, while Corellian Corvettes are known for their speed.

The following Rebel/New Republic craft are included in the game:

*[https://starwars.fandom.com/wiki/X-wing_starfighter T-65 X-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL_Y-wing_starfighter BTL-A4 Y-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL-A4_LP_%22Longprobe%22 BTL-LP Longprobe Starfighter]
*[https://starwars.fandom.com/wiki/RZ-1_A-wing_interceptor RZ-1 A-wing Interceptor]
*[https://starwars.fandom.com/wiki/A/SF-01_B-wing_starfighter A/SF-01 B-wing Starfighter]
*[https://starwars.fandom.com/wiki/E-wing_escort_starfighter E-wing Escort Starfighter]
*[https://starwars.fandom.com/wiki/UT-60D_U-wing_starfighter/support_craft UT-60D U-wing]
*[https://starwars.fandom.com/wiki/Millennium_Falcon Millennium Falcon]

*[https://starwars.fandom.com/wiki/GR-75_medium_transport GR-75 Medium Transport]
*[https://starwars.fandom.com/wiki/CR90_corvette Corellian CR90 Corvette]
*[https://starwars.fandom.com/wiki/EF76_Nebulon-B_escort_frigate EF76 Nebulon-B Escort Frigate]
*[https://starwars.fandom.com/wiki/MC30C_frigate MC30 Heavy Frigate]
*[https://starwars.fandom.com/wiki/MC40a_light_cruiser MC40 Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Liberty_type_Star_Cruiser ''Liberty''-class Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Home_One_type_Star_Cruiser ''Home One''-class Star Cruiser]

===Galactic Empire===
[[Image:NuRTIE03.jpg|thumb|The TIE/ln Starfighter, main fighter of the Galactic Empire]]
The Galactic Empire's main strategy for fighters revolves around the concept of numerical advantage. Imperial TIEs usually lack shields and durability, but have very potent weaponry and great maneuverability to counter this weakness. Most Imperial fighters also forego any sort of missile secondary weapons and focus entirely on their lasers for offensive armament. Imperial capital ships are much larger than those of the Rebels, and focus on heavy offensive weaponry and great hull durability.

The following Imperial craft are included in the game:

*[https://starwars.fandom.com/wiki/TIE/LN_starfighter T.I.E. Starfighter & TIE/ln Starfighter]
*[https://starwars.fandom.com/wiki/TIE_Reconnaissance_Fighter TIE/rc Recon Fighter]
*[https://starwars.fandom.com/wiki/TIE/IN_interceptor TIE/In Interceptor Mark I and Mark II]
*[https://starwars.fandom.com/wiki/TIE/sa_bomber TIE/sa Bomber]
*[https://starwars.fandom.com/wiki/TIE_Advanced_x1 TIE Advanced x1]
*[https://starwars.fandom.com/wiki/V38_assault_fighter V38 Assault Fighter]

*[https://starwars.fandom.com/wiki/TIE/sh_shuttle TIE/sh Shuttle]
*[https://starwars.fandom.com/wiki/Alpha-class_Xg-1_Star_Wing Xg-1 Star Wing]
*[https://starwars.fandom.com/wiki/Delta-class_DX-9_stormtrooper_transport DX-9 Stormtrooper Transport]
*[https://starwars.fandom.com/wiki/Lambda-class_T-4a_shuttle Lambda-class T-4a Shuttle]
*[https://starwars.fandom.com/wiki/Zeta-class_Heavy_Cargo_Shuttle Zeta-class Heavy Cargo Shuttle]

*[https://starwars.fandom.com/wiki/All_Terrain_Armored_Transport ''All Terrain Armored Transport'']
*[https://starwars.fandom.com/wiki/Gozanti-class_cruiser ''Gozanti''-class Cruiser]

*[https://starwars.fandom.com/wiki/Raider-class_corvette ''Raider''-class Corvette]
*[https://starwars.fandom.com/wiki/Carrack-class_light_cruiser ''Carrack''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Arquitens-class_light_cruiser ''Arquitens''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Strike-class_medium_cruiser ''Strike''-class Medium Cruiser]
*[https://starwars.fandom.com/wiki/Vindicator-class_heavy_cruiser ''Vindicator''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Interdictor_vessel ''Interdictor''-class Cruiser]
*[https://starwars.fandom.com/wiki/Imperial_II-class_Star_Destroyer ''Imperator II''-class Star Destroyer]
*[https://starwars.fandom.com/wiki/Golan_space_defense_platform Golan M-series Dockyard Platforms]
*[https://starwars.fandom.com/wiki/Shield_Gate Golan M-3185 Shield Gate Station]

===Neutral===
There are multiple factions in the Star Wars galaxy which use many craft that are not produced for the Galactic Empire or the Rebel Alliance. These craft vary in characteristics and are used throughout the galaxy in various roles.

The following Neutral craft are included in the game:

*[https://starwars.fandom.com/wiki/Z-95_Headhunter Z-95 Headhunter]
*[https://starwars.fandom.com/wiki/CloakShape_fighter/Legends Cloakshape Starfighter]
*[https://starwars.fandom.com/wiki/N-1_starfighter N-1 Naboo Starfighter]
*[https://starwars.fandom.com/wiki/Alpha-3_Nimbus-class_V-wing_starfighter Alpha-3 Nimbus-class V-wing Starfighter]
*[https://starwars.fandom.com/wiki/Aggressive_ReConnaissance-170_starfighter/Legends ARC-170 Starfighter]
*[https://starwars.fandom.com/wiki/Vulture-class_starfighter Vulture-class_starfighter]
*[https://starwars.fandom.com/wiki/Ugly/Legends Various Uglies]
*[https://starwars.fandom.com/wiki/Firespray-31-class_patrol_and_attack_craft Firespray-31-class Gunship]
*[https://starwars.fandom.com/wiki/Slave_I Slave I]
*[https://starwars.fandom.com/wiki/YT-1300_light_freighter YT-1300 Light Freighter]
*[https://starwars.fandom.com/wiki/BFF-1_bulk_freighter BFF-1 Bulk Freighter]
*[https://starwars.fandom.com/wiki/Tug DV-3 Cargo Freighter]
*[https://starwars.fandom.com/wiki/Action_VI_transport Action VI Transport]
*[https://starwars.fandom.com/wiki/Transport Rayter-class Transport]
*[https://starwars.fandom.com/wiki/CSS-1_Corellian_Star_Shuttle Star Shuttle]
*[https://starwars.fandom.com/wiki/StarSpeeder_1000 Star Speeder]
*[https://starwars.fandom.com/wiki/GAT-12_Skipray_Blastboat GAT-10 Skipray Blastboat]
*[https://starwars.fandom.com/wiki/Consular-class_cruiser_(Charger_c70_retrofit) Corellian Charger C70 Retrofit]
*[https://starwars.fandom.com/wiki/Braha'tok-class_gunship Braha'tok-class gunship]
*[https://starwars.fandom.com/wiki/Marauder-class_corvette Marauder-class corvette]
*[https://starwars.fandom.com/wiki/Dreadnaught-class_heavy_cruiser ''Dreadnaught''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Venator-class_Star_Destroyer ''Venator''-class Cruiser]
*[https://starwars.fandom.com/wiki/XQ_Platform_series XQ1 and XQ2 Stations]
*[https://starwars.fandom.com/wiki/Asteroid_base Asteroid Base Station]
*[https://starwars.fandom.com/wiki/Repair_droid Dockyard Repair Droids]
*[https://starwars.fandom.com/wiki/Satellite/Legends Sensor and Defense Satellites]
*[https://starwars.fandom.com/wiki/Space_mine Space Mines]

==Missions and Campaigns==
''Fate of the Galaxy'' comes with a high level of single-player content. These include multiple campaigns, standalone missions, and the ability to create missions using the FSO mission editor FRED2. Multiplayer servers are also maintained and available to play on with friends.

The first three campaigns narrate three interconnected stories set at the beginning of the Galactic Civil War. Each of these three campaigns consists of about 5 missions, thus designers put high emphasis on quality mission design and high replayability. The player's performance throughout the campaign will affect how later missions play out. For example, the Alliance campaign will pit a ragtag Rebel task force against a dreaded ''Imperial''-class Star Destroyer in the early stages of the Rebellion, and the player's performance throughout the campaign has a major impact on this encounter's difficulty. The best possible outcome is hard to achieve, thus a number of playthroughs will be required.

Players receive different types of training in different campaigns. The Alliance mini-campaign starts with a basic training mission that teaches the basics to new players along with gameplay features that are unique to ''Fate of the Galaxy'''. The Imperial mini-campaign starts with an advanced training.

Standalone missions are also included in the first release. Many of them are serious, story-driven missions, but there will also be arcade-like "challenge" missions in which the player must accomplish a wide variety of objectives, such as surviving two minutes within a ''Strike''-class cruiser's firing range. There will also be a Practice Zone mission, where the player can test flying any of the small craft and actively spawn in any craft in the mission as a hostile or friendly to practice combat.

Three additional campaigns are being worked on and will be available when the game is released to the public, but specific details remain under embargo until public launch. This large component is code-named Project Alderaan.

==Development==
[[Image:Ewingmaps.jpg|thumb|The progression of model work shown on an E-wing Starfighter, from Model (Right) to Normal Maps (Center) and Diffuse Texture (Left). Note that this model will not be used.]]
Fate of the Galaxy picks up after a number of previous attempts to create a ''Star Wars'' mod for FreeSpace. For several years the "Star Wars Conversion Project" was worked on by various teams and developers, but without any releases.

In early 2007, chief1983 took over as project leader, and began to assemble a new team of developers. Choosing the name ''Fate of the Galaxy'', the initial team consisted of chief1983, Brand-X as a modeler and Turambar as a texturer. The initial plan put forward was to use the models and textures that had been completed by previous teams. Soon after the reformation of the mod team, however, it was decided that all new art assets were needed to compete with the high graphical standards of the newer models, and all previously completed ships were discarded.

Work continued on ship models and textures through the next year and a half, as new staff members were added to the development team. In May of 2008, work began on implementing the new ship models into the game and work began on redesigning the feel and pace of the FreeSpace 2 Open engine. Work still continued on the models needed for a campaign and demo release.

In early January of 2009, Brand-X experienced a hard drive failure which destroyed all previous models of his, setting the team's art department back significantly. Since then, work has progressed on recreating these models to even higher quality standards.

On June 4th, 2009, the first in-game screenshot of the X-wing starfighter was made public at the [http://www.moddb.com/games/fate-of-the-galaxy/images/x-wing-in-game-shots2#imagebox ModDB site] and at the official FotG [https://www.hard-light.net/forums/index.php?board=143.0 forums]. The first three campaigns, which are set at the beginning of the Galactic Civil War, were eventually completed, and worked then moved to standalone missions and three additional campaigns code-named Project Alderaan.

In December of 2018 the team began the first phases of private beta testing. In June of 2022, the private beta tests were stated as nearly concluded.

In May of 2019 the [https://www.youtube.com/watch?v=ler20EdjAfs&list=LLW8-wdcPLv0eT913KIi9_mw&index=2&t=0s teaser trailer] was posted.

Throughout 2020-2022 developmental showcases have consisted of forum updates and gameplay streams on Discord.

In June of 2022, multiplayer was confirmed to be working well, and standalone servers were created.

From 2023-2024, the game underwent extensive balance and optimization testing in preparation for the public release.

For the duration of 2025, additional polishing passes were conducted and continue to be refined.

===Newsletter===
Newsletters are posted on a quarterly basis on the [https://www.hard-light.net/forums/index.php?board=143.0 Fate of the Galaxy Forums]. Also, the majority of the unofficial development chatter occurs on the Fate of the Galaxy Discord channel [https://discord.gg/k7ZMdmt].

The most recent [https://www.hard-light.net/forums/index.php?topic=99253.0] was released in May 2024. This update highlights new ship additions, MainHall updates, many other enhancements, and numerous fixes and minor updates.

For reference, the [http://www.hard-light.net/forums/index.php/topic,54217.0.html first newsletter] was posted on June 1st, 2008.

===First Release===
The first open beta of ''Fate of the Galaxy'' was originally planned to be released sometime late-2008 or early 2009. However, with the art setback, the release has been pushed back. Subsequent additions and developments then lead the team to decide to release the game as a more polished 1.0 version. A date has not been decided yet, but the first three campaigns are done and relatively independent compared to the larger subsequent 3 campaigns.

Recent years have shown considerable progress on the project, including a release of a private beta and addition of multiple ships and integrating new features that were recently added to the FSO engine (such as deferred and shadow lighting for cockpits, optimizations, and advanced scripting controls).

In the most recent communications on Discord, co-community manager wookieejedi posted: "''We are primarily waiting on FSO 26.0.1 Stable, and guarantee FotG will be released before GTA6''" (September 2th, 2026).

==Gallery==
===Ship Lab shots===
<gallery>
Image:Bwing.jpg
Image:Falcon2.jpg
Image:Xwing.jpg
Image:Ywing2.jpg
Image:Z95.jpg |
</gallery>
===Renders===
<gallery>
Image:FalconWallpaper.png
Image:TBrender.png
Image:TransportFinal.jpg
Image:Wallpaper.1-1280.png
Image:Wallpaper.2-1280.png
</gallery>

==Links==
*[http://swc.hard-light.net/ Official Website]
*[https://discord.gg/k7ZMdmt Fate of the Galaxy Discord Server]
*[https://www.hard-light.net/forums/index.php?board=143.0 Official Forum]
*[https://www.moddb.com/games/fate-of-the-galaxy Fate of the Galaxy on ModDB]

Ai profiles.tbl

2026-08-28T13:01:40Z

Wookieejedi: /* $strafe retreat collide distance: */

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''
*'''purge player-issued form-on-wing after subsequent order'''}}
{{Table260|
*'''$fix 'ignore if dead' flag:'''}}
{{Table262|
*'''$fix ai target recovery:'''
*'''$no collision avoidance for kamikaze fighters:'''
*'''$fix big ship waypoint completion:'''
*'''$fix shockwave expiring before dealing damage:'''
*'''$fix fighter/bomber AI recovers after engines repaired:'''
*'''$fix standard strafe:'''
}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$max allies rearming threshold:===
{{Table250|
*The maximum allowed number of allies that are allowed to be rearming at the same time. It should be noted that the effect is more noticeable at higher numbers.
*2 by default.
*Syntax: '''''Integer'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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).}}
{{Table260|
*As of 26.0, the "alt2" mode is available. The alt2 mode is like alt1 but allows shortcutting.}}

===$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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe retreat collide time:===
{{Table262|
*For strafe attacks against big ships, small ships calculate a point relative to the big ship they are attacking and move towards during it strafe. This value is how long until the attacking ship will reach the strafe attack point, when duration to the point is less than this value begin retreat from strafe (IE turn around and perform a new strafe). Default is 2.0 seconds. Note, a new strafe will also trigger if the check for '$strafe retreat collide distance:' is true.
**Syntax: '''''Float''''' (defaults to 2.0)}}

===$strafe retreat collide distance:===
{{Table262|
*For strafe attacks against big ships, small ships calculate a point relative to the big ship they are attacking and move towards during it strafe. This value is the distance until the attacking ship will reach the strafe attack point, when distance to the point is less than this value begin retreat from strafe (IE turn around and perform a new strafe). Note, a new strafe will also trigger if the check for '$strafe retreat collide time:' is true. Default is 200 meters.
**Syntax: '''''Float''''' (defaults to 200.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$fix ai target recovery:===
{{Table262|
*Fixes several target recovery bugs: fighters/bombers if strafing a large ship and that large ship dies or departs; ships being assigned a target that they don't actively pursue; and generally ships ending up in AIM_NONE while still holding a standing attack order. These typically manifest as a ship slowing down to 0 and then not moving until another order is issued. Enabling this flag allows the AI to recover properly from these situations. Note that this flag applies to orders where the AI chooses its own target; an invalid specific target will still be assigned and will cause the ship to slow down to 0.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

===$don't issue form-on-wing goals at mission start:===
{{Table250|
*Normally, at the beginning of a mission, player wings that do not have an initial goal will be given an initial goal to form on the player. Wings in the loadout screen (aka "starting" wings) will also, if they do not have an initial goal, be issued the same goal if they arrive after mission start. This flag disables that behavior.
*Syntax: '''''Boolean'''''}}

===$default form-on-wing priority:===
{{Table250|
*The default goal priority to be used when issuing a form-on-wing order via sexp or script. If not specified, this is 99. Note that orders issued via the HUD communications system will use the standard communications priorities (100 for ships and 95 for wings) regardless of this setting.
*Syntax: '''''Integer'''''}}

===$do not clear goals when running form-on-wing:===
{{Table250|
*Normally, as soon as a form-on-wing goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the form-on-wing behavior while forgetting both the form goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not clear goals when running stay-still:===
{{Table250|
*Normally, as soon as a stay-still goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the stay-still behavior while forgetting both the stay-still goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not set override when assigning form-on-wing:===
{{Table250|
*Normally, any form-on-wing goal, regardless of how it is assigned, is given a <tt>Goal_override</tt> flag. This causes its goal to be evaluated as the top priority goal, regardless of its actual priority or any other goal's priority. This flag prevents <tt>Goal_override</tt> from being assigned, causing form-on-wing to follow the normal goal prioritization logic.
*Syntax: '''''Boolean'''''}}

===$purge player-issued form-on-wing after subsequent order:===
{{Table250|
*Causes any form-on-wing goal issued by the player (i.e. via the HUD communications system) to be removed from a ship's goal list (even if it is not the current goal) when the ship is given another goal of any priority. This flag can be useful for mods which configure form-on-wing goals to use the same execution and prioritization logic as normal goals. Since form-on-wing goals are typically temporary, regardless of their priority, this flag enforces that temporary nature. By using this flag, mission designers can ensure that mission-directed AI goal logic is followed regardless of form-on-wing status.
*Syntax: '''''Boolean'''''}}

===$cancel future waves of any wing launched from an exited ship:===
{{Table250|
*Infamously, in FSO, a wing whose mothership is destroyed will not, itself, be considered destroyed if it has more waves remaining, because wing cleanup and logging typically only happen when the last ship in the last wave exits the mission. Instead, with no mothership to arrive from, waves will simply no longer arrive. Events that check to see if the wing is destroyed or departed will never fire. This flag fixes that behavior, ensuring that the wing is cleaned up and logged properly, by using the same logic as the enhanced cancel-future-waves SEXP operator.
*Syntax: '''''Boolean'''''}}

===$fix 'ignore if dead' flag:===
{{Table260|
*The subsystem flag "ignore if dead" that many mods use is supposed to "prevent homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target." The code was bugged though and unfortunately what ends up happening is that the weapon dumb fire instead of homes. This bug means if you destroy a subsystem with this flag, then lock onto it with an aspect weapon and fire the weapon, the weapon will just dumb fire. Enabling this flag fixes this, and actually makes "ignore if dead" flag work as intended.
*Syntax: '''''Boolean'''''}}

===$no collision avoidance for kamikaze fighters:===
{{Table262|
*Kamikaze fighters will often veer away from their target because they are paradoxically trying not to collide with it. When this flag is enabled, they will not veer away.
*Syntax: '''''Boolean'''''}}

===$fix big ship waypoint completion:===
{{Table262|
*Fixes the "spinning Orion" waypoint completion bug. When this flag is enabled, a) big ships complete a waypoint within their radius rather than sqrt(radius); and b) completion no longer requires moving 0.1m in a single frame.
*Syntax: '''''Boolean'''''}}

===$fix shockwave expiring before dealing damage:===
{{Table262|
*Fixes shockwave damage so that shockwaves that move faster than 1-frame properly still deal damage. Without this fix it is possible the shockwave may have lifetime shorter than one frame (e.g. high speed, small radius), which by default results in shockwave applying no damage.
*Syntax: '''''Boolean'''''}}

===$fix fighter/bomber AI recovers after engines repaired:===
{{Table262|
*Fixes edge-case of AI of fighters/bombers remaining stationary if their engines were destroyed and then repaired. This could occur if their engines get temporarily disabled and then repaired and their current target dies/departs, and by default this results in the fighter/bomber not moving even when their engines are repaired. Enabling this fix allows the fighter/bomber to avoid this issue and move properly.
*Syntax: '''''Boolean'''''}}

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

2026-08-28T13:01:27Z

Wookieejedi: /* $strafe retreat collide time: */

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''
*'''purge player-issued form-on-wing after subsequent order'''}}
{{Table260|
*'''$fix 'ignore if dead' flag:'''}}
{{Table262|
*'''$fix ai target recovery:'''
*'''$no collision avoidance for kamikaze fighters:'''
*'''$fix big ship waypoint completion:'''
*'''$fix shockwave expiring before dealing damage:'''
*'''$fix fighter/bomber AI recovers after engines repaired:'''
*'''$fix standard strafe:'''
}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$max allies rearming threshold:===
{{Table250|
*The maximum allowed number of allies that are allowed to be rearming at the same time. It should be noted that the effect is more noticeable at higher numbers.
*2 by default.
*Syntax: '''''Integer'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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).}}
{{Table260|
*As of 26.0, the "alt2" mode is available. The alt2 mode is like alt1 but allows shortcutting.}}

===$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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe retreat collide time:===
{{Table262|
*For strafe attacks against big ships, small ships calculate a point relative to the big ship they are attacking and move towards during it strafe. This value is how long until the attacking ship will reach the strafe attack point, when duration to the point is less than this value begin retreat from strafe (IE turn around and perform a new strafe). Default is 2.0 seconds. Note, a new strafe will also trigger if the check for '$strafe retreat collide distance:' is true.
**Syntax: '''''Float''''' (defaults to 2.0)}}

===$strafe retreat collide distance:===
{{Table26.2|
*For strafe attacks against big ships, small ships calculate a point relative to the big ship they are attacking and move towards during it strafe. This value is the distance until the attacking ship will reach the strafe attack point, when distance to the point is less than this value begin retreat from strafe (IE turn around and perform a new strafe). Note, a new strafe will also trigger if the check for '$strafe retreat collide time:' is true. Default is 200 meters.
**Syntax: '''''Float''''' (defaults to 200.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$fix ai target recovery:===
{{Table262|
*Fixes several target recovery bugs: fighters/bombers if strafing a large ship and that large ship dies or departs; ships being assigned a target that they don't actively pursue; and generally ships ending up in AIM_NONE while still holding a standing attack order. These typically manifest as a ship slowing down to 0 and then not moving until another order is issued. Enabling this flag allows the AI to recover properly from these situations. Note that this flag applies to orders where the AI chooses its own target; an invalid specific target will still be assigned and will cause the ship to slow down to 0.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

===$don't issue form-on-wing goals at mission start:===
{{Table250|
*Normally, at the beginning of a mission, player wings that do not have an initial goal will be given an initial goal to form on the player. Wings in the loadout screen (aka "starting" wings) will also, if they do not have an initial goal, be issued the same goal if they arrive after mission start. This flag disables that behavior.
*Syntax: '''''Boolean'''''}}

===$default form-on-wing priority:===
{{Table250|
*The default goal priority to be used when issuing a form-on-wing order via sexp or script. If not specified, this is 99. Note that orders issued via the HUD communications system will use the standard communications priorities (100 for ships and 95 for wings) regardless of this setting.
*Syntax: '''''Integer'''''}}

===$do not clear goals when running form-on-wing:===
{{Table250|
*Normally, as soon as a form-on-wing goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the form-on-wing behavior while forgetting both the form goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not clear goals when running stay-still:===
{{Table250|
*Normally, as soon as a stay-still goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the stay-still behavior while forgetting both the stay-still goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not set override when assigning form-on-wing:===
{{Table250|
*Normally, any form-on-wing goal, regardless of how it is assigned, is given a <tt>Goal_override</tt> flag. This causes its goal to be evaluated as the top priority goal, regardless of its actual priority or any other goal's priority. This flag prevents <tt>Goal_override</tt> from being assigned, causing form-on-wing to follow the normal goal prioritization logic.
*Syntax: '''''Boolean'''''}}

===$purge player-issued form-on-wing after subsequent order:===
{{Table250|
*Causes any form-on-wing goal issued by the player (i.e. via the HUD communications system) to be removed from a ship's goal list (even if it is not the current goal) when the ship is given another goal of any priority. This flag can be useful for mods which configure form-on-wing goals to use the same execution and prioritization logic as normal goals. Since form-on-wing goals are typically temporary, regardless of their priority, this flag enforces that temporary nature. By using this flag, mission designers can ensure that mission-directed AI goal logic is followed regardless of form-on-wing status.
*Syntax: '''''Boolean'''''}}

===$cancel future waves of any wing launched from an exited ship:===
{{Table250|
*Infamously, in FSO, a wing whose mothership is destroyed will not, itself, be considered destroyed if it has more waves remaining, because wing cleanup and logging typically only happen when the last ship in the last wave exits the mission. Instead, with no mothership to arrive from, waves will simply no longer arrive. Events that check to see if the wing is destroyed or departed will never fire. This flag fixes that behavior, ensuring that the wing is cleaned up and logged properly, by using the same logic as the enhanced cancel-future-waves SEXP operator.
*Syntax: '''''Boolean'''''}}

===$fix 'ignore if dead' flag:===
{{Table260|
*The subsystem flag "ignore if dead" that many mods use is supposed to "prevent homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target." The code was bugged though and unfortunately what ends up happening is that the weapon dumb fire instead of homes. This bug means if you destroy a subsystem with this flag, then lock onto it with an aspect weapon and fire the weapon, the weapon will just dumb fire. Enabling this flag fixes this, and actually makes "ignore if dead" flag work as intended.
*Syntax: '''''Boolean'''''}}

===$no collision avoidance for kamikaze fighters:===
{{Table262|
*Kamikaze fighters will often veer away from their target because they are paradoxically trying not to collide with it. When this flag is enabled, they will not veer away.
*Syntax: '''''Boolean'''''}}

===$fix big ship waypoint completion:===
{{Table262|
*Fixes the "spinning Orion" waypoint completion bug. When this flag is enabled, a) big ships complete a waypoint within their radius rather than sqrt(radius); and b) completion no longer requires moving 0.1m in a single frame.
*Syntax: '''''Boolean'''''}}

===$fix shockwave expiring before dealing damage:===
{{Table262|
*Fixes shockwave damage so that shockwaves that move faster than 1-frame properly still deal damage. Without this fix it is possible the shockwave may have lifetime shorter than one frame (e.g. high speed, small radius), which by default results in shockwave applying no damage.
*Syntax: '''''Boolean'''''}}

===$fix fighter/bomber AI recovers after engines repaired:===
{{Table262|
*Fixes edge-case of AI of fighters/bombers remaining stationary if their engines were destroyed and then repaired. This could occur if their engines get temporarily disabled and then repaired and their current target dies/departs, and by default this results in the fighter/bomber not moving even when their engines are repaired. Enabling this fix allows the fighter/bomber to avoid this issue and move properly.
*Syntax: '''''Boolean'''''}}

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

2026-08-28T12:59:46Z

Wookieejedi: add $fix standard strafe: to 26.2 default

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''
*'''purge player-issued form-on-wing after subsequent order'''}}
{{Table260|
*'''$fix 'ignore if dead' flag:'''}}
{{Table262|
*'''$fix ai target recovery:'''
*'''$no collision avoidance for kamikaze fighters:'''
*'''$fix big ship waypoint completion:'''
*'''$fix shockwave expiring before dealing damage:'''
*'''$fix fighter/bomber AI recovers after engines repaired:'''
*'''$fix standard strafe:'''
}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$max allies rearming threshold:===
{{Table250|
*The maximum allowed number of allies that are allowed to be rearming at the same time. It should be noted that the effect is more noticeable at higher numbers.
*2 by default.
*Syntax: '''''Integer'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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).}}
{{Table260|
*As of 26.0, the "alt2" mode is available. The alt2 mode is like alt1 but allows shortcutting.}}

===$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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe retreat collide time:===
{{Table26.2|
*For strafe attacks against big ships, small ships calculate a point relative to the big ship they are attacking and move towards during it strafe. This value is how long until the attacking ship will reach the strafe attack point, when duration to the point is less than this value begin retreat from strafe (IE turn around and perform a new strafe). Default is 2.0 seconds. Note, a new strafe will also trigger if the check for '$strafe retreat collide distance:' is true.
**Syntax: '''''Float''''' (defaults to 2.0)}}

===$strafe retreat collide distance:===
{{Table26.2|
*For strafe attacks against big ships, small ships calculate a point relative to the big ship they are attacking and move towards during it strafe. This value is the distance until the attacking ship will reach the strafe attack point, when distance to the point is less than this value begin retreat from strafe (IE turn around and perform a new strafe). Note, a new strafe will also trigger if the check for '$strafe retreat collide time:' is true. Default is 200 meters.
**Syntax: '''''Float''''' (defaults to 200.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$fix ai target recovery:===
{{Table262|
*Fixes several target recovery bugs: fighters/bombers if strafing a large ship and that large ship dies or departs; ships being assigned a target that they don't actively pursue; and generally ships ending up in AIM_NONE while still holding a standing attack order. These typically manifest as a ship slowing down to 0 and then not moving until another order is issued. Enabling this flag allows the AI to recover properly from these situations. Note that this flag applies to orders where the AI chooses its own target; an invalid specific target will still be assigned and will cause the ship to slow down to 0.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

===$don't issue form-on-wing goals at mission start:===
{{Table250|
*Normally, at the beginning of a mission, player wings that do not have an initial goal will be given an initial goal to form on the player. Wings in the loadout screen (aka "starting" wings) will also, if they do not have an initial goal, be issued the same goal if they arrive after mission start. This flag disables that behavior.
*Syntax: '''''Boolean'''''}}

===$default form-on-wing priority:===
{{Table250|
*The default goal priority to be used when issuing a form-on-wing order via sexp or script. If not specified, this is 99. Note that orders issued via the HUD communications system will use the standard communications priorities (100 for ships and 95 for wings) regardless of this setting.
*Syntax: '''''Integer'''''}}

===$do not clear goals when running form-on-wing:===
{{Table250|
*Normally, as soon as a form-on-wing goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the form-on-wing behavior while forgetting both the form goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not clear goals when running stay-still:===
{{Table250|
*Normally, as soon as a stay-still goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the stay-still behavior while forgetting both the stay-still goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not set override when assigning form-on-wing:===
{{Table250|
*Normally, any form-on-wing goal, regardless of how it is assigned, is given a <tt>Goal_override</tt> flag. This causes its goal to be evaluated as the top priority goal, regardless of its actual priority or any other goal's priority. This flag prevents <tt>Goal_override</tt> from being assigned, causing form-on-wing to follow the normal goal prioritization logic.
*Syntax: '''''Boolean'''''}}

===$purge player-issued form-on-wing after subsequent order:===
{{Table250|
*Causes any form-on-wing goal issued by the player (i.e. via the HUD communications system) to be removed from a ship's goal list (even if it is not the current goal) when the ship is given another goal of any priority. This flag can be useful for mods which configure form-on-wing goals to use the same execution and prioritization logic as normal goals. Since form-on-wing goals are typically temporary, regardless of their priority, this flag enforces that temporary nature. By using this flag, mission designers can ensure that mission-directed AI goal logic is followed regardless of form-on-wing status.
*Syntax: '''''Boolean'''''}}

===$cancel future waves of any wing launched from an exited ship:===
{{Table250|
*Infamously, in FSO, a wing whose mothership is destroyed will not, itself, be considered destroyed if it has more waves remaining, because wing cleanup and logging typically only happen when the last ship in the last wave exits the mission. Instead, with no mothership to arrive from, waves will simply no longer arrive. Events that check to see if the wing is destroyed or departed will never fire. This flag fixes that behavior, ensuring that the wing is cleaned up and logged properly, by using the same logic as the enhanced cancel-future-waves SEXP operator.
*Syntax: '''''Boolean'''''}}

===$fix 'ignore if dead' flag:===
{{Table260|
*The subsystem flag "ignore if dead" that many mods use is supposed to "prevent homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target." The code was bugged though and unfortunately what ends up happening is that the weapon dumb fire instead of homes. This bug means if you destroy a subsystem with this flag, then lock onto it with an aspect weapon and fire the weapon, the weapon will just dumb fire. Enabling this flag fixes this, and actually makes "ignore if dead" flag work as intended.
*Syntax: '''''Boolean'''''}}

===$no collision avoidance for kamikaze fighters:===
{{Table262|
*Kamikaze fighters will often veer away from their target because they are paradoxically trying not to collide with it. When this flag is enabled, they will not veer away.
*Syntax: '''''Boolean'''''}}

===$fix big ship waypoint completion:===
{{Table262|
*Fixes the "spinning Orion" waypoint completion bug. When this flag is enabled, a) big ships complete a waypoint within their radius rather than sqrt(radius); and b) completion no longer requires moving 0.1m in a single frame.
*Syntax: '''''Boolean'''''}}

===$fix shockwave expiring before dealing damage:===
{{Table262|
*Fixes shockwave damage so that shockwaves that move faster than 1-frame properly still deal damage. Without this fix it is possible the shockwave may have lifetime shorter than one frame (e.g. high speed, small radius), which by default results in shockwave applying no damage.
*Syntax: '''''Boolean'''''}}

===$fix fighter/bomber AI recovers after engines repaired:===
{{Table262|
*Fixes edge-case of AI of fighters/bombers remaining stationary if their engines were destroyed and then repaired. This could occur if their engines get temporarily disabled and then repaired and their current target dies/departs, and by default this results in the fighter/bomber not moving even when their engines are repaired. Enabling this fix allows the fighter/bomber to avoid this issue and move properly.
*Syntax: '''''Boolean'''''}}

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

Game settings.tbl

2026-08-16T16:37:42Z

Wookieejedi: $Always show selected item in Comms Gauge:

{{SCP_table}}
{{TableVersionGit|2025-02-10|642111676012bc6696f4024c40296a6c20b3b958}}
{{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

If the version targeted in [[game_settings.tbl#$Target_Version:|target version]] is equal to or later than these listed, the following options are enabled by default:
{{Table220|
*[[game_settings.tbl#$Fixed_Turret_Collisions:|Fixed Turret Collisions]]
*[[game_settings.tbl#$Fixed_Missile_Detonation:|Fixed Missile Detonation]]
*[[game_settings.tbl#$Shockwaves_Damage_All_Object_Types_Once:|Shockwaves Damage All Object Types Once]]
*[[game_settings.tbl#$AI_use_framerate_independent_turning:|AI use framerate independent turning]]
*[[game_settings.tbl#$Use_host_orientation_for_set-camera-facing:|Use host orientation for set-camera-facing]]
}}
{{Table230|
*[[game_settings.tbl#$Shockwaves_Inherit_Parent_Weapon_Damage_Type:|Shockwaves Inherit Parent Weapon Damage Type]]
*[[game_settings.tbl#$Fixed_Chaining_To_Repeating_Events:|Fixed Chaining To Repeating Events]]
}}
{{Table240|
*[[game_settings.tbl#$Calculate_subsystem_hitpoints_after_parsing:|Calculate subsystem hitpoints after parsing]]}}
{{Table242|
*[[game_settings.tbl#$Fix_scripted_velocity:|Fix scripted velocity]]}}
{{Table250|
*[[game_settings.tbl#$Use_model_eyepoint_for_set-camera-host:|Use model eyepoint for set-camera-host]]
*[[game_settings.tbl#$Use_model_eyepoint_normals:|Use model eyepoint normals]]
*[[game_settings.tbl#$Fix_asteroid/debris_field_bounding_box_checks:|Fix asteroid/debris field bounding box checks]]
*[[game_settings.tbl#$Disable_expensive_turret_target_check:|Disable expensive turret target check]]
*[[game_settings.tbl#$Skybox_internal_depth_consistency:|Skybox internal depth consistency]]
}}
{{Table260|
*[[game_settings.tbl#$Zero-radius_explosions_skip_fireballs:|Zero-radius explosions skip fireballs]]
*[[game_settings.tbl#$Render_insignias_as_decals:|Render insignias as decals:]]}}

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

The icon should be in data/maps or data/interface, and can apparently be any single-frame image format supported by FSO. The default icon is .png.

*Syntax: '''''String'''''
}}

===$Mod title:===
{{Table224|
Specifies the title of the mod and will be displayed at the mainhall near the FSO version.
*Syntax: '''''String'''''
}}
{{Table250|
It is now possible to display the mod title on its own. Previously, the mod version was also required.
}}

===$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'''''
}}
{{Table250|
It is now possible to display the mod version on its own. Previously, the mod title was also required.
}}

===$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'''''}}

===$Splash screens:===
{{Table232|
Defines a list of splash screens that FSO can display upon game startup. The actual image displayed is chosen at random from the applicable entries. Entries with exact aspect ratio matches will be prioritized first, followed by aspect ratio ranged matches, followed by entries without an aspect ratio specified.}}

====+Bitmap:====
{{table232|
The name of the bitmap to use as a splash screen. Extension will be removed if included.
*Syntax: '''''+Bitmap: String'''''}}

====+Aspect Ratio:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio matches the specified number within +/- 0.01.
*Syntax: '''''+Aspect Ratio: Float'''''}}

====+Aspect Ratio Min:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at least the specified number.
*Syntax: '''''+Aspect Ratio Min: Float'''''}}

====+Aspect Ratio Max:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at most the specified number.
*Syntax: '''''+Aspect Ratio Max: Float'''''}}

===$Splash fade in time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade in.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Splash fade out time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade out.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Center splash logo:===
{{Table232|
Sets whether the splash logo will be displayed in the middle of the screen. If this is false (the default), it will be displayed at the top-left.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Disable FSO Internal Loadout Restoration System:===
{{Table234|
When the player configures the ships and weapons of the wings in the loadout screen, FSO will remember these settings and attempt to apply them again if the player quits the mission and comes back to it later. FSO will only remember the most recent mission's loadout, so it will not attempt to restore the loadout if the player loads a different mission. It will also not attempt this if the mission's ''$Modified:'' date has changed. This flag can be used to prevent FSO from attempting restoration even if it normally would.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Lua API returns nil instead of invalid object:===
{{Table242|
A design choice very early in FSO's scripting development established that invalid results return invalid objects. By using this flag, invalid results will return nil instead.
*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 initalize built-in languages by default:===
{{Table240|
Prevent FSO from initializing the three additional built-in languages (German, French, and Polish). This allows mods which don't support those languages to remove them from the SCPUI language selector.
*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'''''}}

===$Auto select subsystem under reticle when targeting same ship:===
{{Table242|This is a streamlining of functionality, that makes it so one doesn't need to hit a second key to select the subsystem under the reticle. Instead once you have the capital ship selected, hit Target Under Reticle and it will target a subsystem under the reticle if the feature is enabled and there isn't a new target under the reticle.
*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'''''
}}

===$HUD drop shadows enabled by default:===
{{Table232|
If this flag is active, certain elements displayed on the HUD (all text, the main targeting reticle, and the background of the ETS gauges) will have a "drop shadow" effect. Note that whether or not the flag is active, the player can set this using the "Toggle HUD Drop Shadows" control.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Unify scanning behavior:===
{{Table242|
*Unifies scanning behavior between subsystem, regular, and cargo allowing missions to use all scan types in all situations.
*Also allows changing the "Cargo:" text line in a mission by adding "$Cargo Title: STRING" after the "$Cargo 1:" or "$Cargo 2:" lines in the mission file. FRED UI support not yet added for $Cargo Title so you have to do it manually.
*When this flag is enabled, all ships, no matter the ship class, will react the same way to the cargo-related or scanning-related ship flags:
**They are not scannable by default
**Setting the "scannable" flag makes them scannable, and scanning the subsystem will reveal the cargo
**A new flag available with alter-ship-flag, "no-scanned-cargo", changes the behavior to scanned/unscanned instead of revealing the cargo
**The "toggle-subsystem-scanning" flag must be set to swap full-ship scanning mode into subsystem scanning mode and works for all ship types
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Don't show callsigns in the escort list:===
{{Table242|
By default, callsigns are shown in the escort list using the same format as in the target box. If this flag is active, callsigns will not be displayed.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Hide main Rearm/Repair items in Comms Gauge:===
{{Table250|
Prevents 5. Rearm/Repair Subsys and 6. Abort Rearm from being shown in the squad messaging menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Always show selected item in Comms Gauge:===
{{Table262|
Ensures that the visual indicator for which is the active item in the squad messaging menu is always shown. Useful if you are using the select Comms menu item keys. By default this is not shown until the player presses the up or down key for the select Comms menu item keys.
*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'''''

===$Fixed Chaining To Repeating Events:===
{{Table230|When set, this makes event chaining to repeated events work as designed - that is, the chained event will only be evaluated after the chain delay. If the repeating event's interval is shorter than the chain delay, then the delay countdown will continually be restarted until all repetitions have completed. Without this flag, FSO will emulate retail behavior which, due to a bug, allowed chained events to be evaluated immediately after a repeating event is first evaluated.

NOTE: Although the name does not reflect it, the same issue affects repeating events that are evaluated by <tt>is-event-true-delay</tt> and <tt>is-event-false-delay</tt>. Without this flag, FSO will emulate retail behavior which causes these SEXP operators to ignore any delay when evaluating repeated events. With this flag, the delay will be measured from when the final repeat iteration occurs.
*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'''''}}

===$Use model eyepoint for set-camera-host:===
{{Table250|The default behavior for set-camera-host is to position the camera at the origin coordinates (0,0,0) of the host. This flag will make the camera use the model eyepoint instead.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Use model eyepoint normals:===
{{Table250|If set, model eyepoints will respect the normal vector set for the eyepoint in the model file for the eyepoint. If not set, model eyepoints will use the model's orientation.
*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)'''''}}

===$HUD-set-coords base resolution:===
{{Table232|The hud-set-coords SEXP has always used exact pixels, without regard for the current screen resolution. This setting enables a similar scaling mechanism as ''$Show-subtitle base resolution:''.
*Syntax: '''''(Integer, Integer)'''''
*Default Value: '''''(-1, -1)'''''}}

===$Always Show Directive Value Count:===
{{Table250|
*If this setting is enabled, Directive-as-Value values in Directives will always show the number. By default this is disabled, and only values > 1 are shown.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

==#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'''''}}

===$EMP Pain Flash Factor:===
{{Table224|
Determines the intensity of the flash when the player is hit by an EMP blast or weapon.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$EMP Pain Flash Color:===
{{Table224|
Determines the RGB color value of the flash when the player is hit by an EMP blast or weapon.
*Syntax: Color, (red, green, blue) respectively, integer value from 0 to 255
*Default Value: '''''(255, 255, 127)'''''}}

===$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)
}}

===$EMP Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)
}}

===$Damage Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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.
{{Table262|
*Can now be an arbitrary non-zero number of floats. If not set to 4, you must table [[#$Shadow Smoothness Factor:]]
}}
*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.
{{Table262|
*Can now be an arbitrary non-zero number of floats. If not set to 4, you must table [[#$Shadow Smoothness Factor:]]
}}
*Syntax: '''''List of floats'''''
*Default Value: '''''(0.25, 0.75, 1.5, 3.0)'''''}}

{{Table262|
===$Shadow Smoothness Factor:===
Sets the strength of the smoothing for each shadow cascade. Larger values mean smoother / softer shadows. Shadow smoothness also scales with cascade distance, so the same value for a larger cascade will be perceived to be smoother.
The number of smoothness factors ''must'' match the number of Shadow Cockpit Cascades + Shadow Cascades (each 4 by default).
The list should first contain the smoothness factors for the cockpit cascades in order, and then the smoothness factors for the main cascades in order
*Syntax: '''''List of floats'''''
*Default Value: '''''(0.00333, 0.004, 0.005, 0.005, 0.00333, 0.004, 0.005, 0.005)'''''}}

===$Shadow Disable Techroom:===
{{Table224|
Disables shadows on ships in the techroom.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Cockpit:===
{{Table224|
Disables shadows on the player cockpit in mission.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Weapons:===
{{Table224|
Disables shadows on weapons in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Ships:===
{{Table224|
Disables shadows on ships in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Show Ship Casts Shadow:===
{{Table224|
When cockpit shadows are enabled, enabling this setting will cause the players ship model shown with "show ship" to cast shadow onto the cockpit.
*Syntax: '''''Boolean'''''
}}

===$Ship Model And Cockpit Share Coordinate Space:===
{{Table224|
When having the "show ship" flag enabled and cockpit models for a ship, this flag should be on if the cockpits can fit into the actual geometry of the ship model. Disable this flag if this is not the case and the cockpit needs to be rendered on top of the ship regardless of actual coordinates. If this can be enabled, the external show ship model can be rendered using deferred rendering.
*Syntax: '''''Boolean'''''
}}

===$Show Ship enabled only if Cockpits enabled:===
{{Table250|
Enabling this setting will only use the 'show-ship' flag if cockpits are enabled. Useful if your ship uses both 'show-ship' and cockpits that exist within the 'show-ship' space, and you want to allow players to toggle off cockpits. Note, 'show-ship' always only appears if in first-person view.
*Syntax: '''''Boolean'''''
}}

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

===$Do Not Render Lasers Below Length:===
{{Table250|
*Specifies the smallest length that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Do Not Render Lasers Below Radius:===
{{Table250|
*Specifies the smallest radius that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Thruster Easing Value:===
{{Table220|
*Smooths out the behavior of maneuvering thruster flares the higher above 0 it is.
*This is the exponential time constant for the visual flare length to reach it's true length.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

===$SCPUI attempts to load hires animations:===
{{Table230|
*Prevents SCPUI from trying to load anims prefixed with "2_"
*Syntax: '''''Boolean'''''
*Default Value: true}}

{{Table230|
===$Max draw distance:===
===$Min draw distance:===
*These values do more than just cutoff the visuals at certain distances, and they must be adjusted carefully to ensure unintentional rendering artifacts are not introduced.
*The rendering engine has limited amount of 'depth resolution', the degree to which it can tell a certain polygon is closer or farther away than another. When two polygons are too close, they will Z-fight, picking arbitrarily which is closer. It is the span between the min and max draw distance that determines how well the engine can determine depth, if they are too far from one another, the Z-fighting will become more common as it has to spread its resolution over a wider range. If they are close, Z-fighting will be lessened at the cost of a smaller range of distance able to be rendered.
*Syntax: '''''Float''''', meters
*Default Values: 10,000,000,000 and 1, respectively
}}

{{Table232|
===$Randomize particle rotation:===
*Particle bitmaps are typically screen-aligned; the upper portion of the bitmap will always be mapped to the upper portion of the particle, from the point of view of the camera. Enabling this option makes ''all'' particles have a random 'tilt' in an arbitrary direction when created.
*Syntax: '''''Boolean'''''
*Default Value: false
}}

===$Disable shield effects:===
{{Table250|
*Specifies if FSO attempts to use the shield mesh impact effects. Enabling this flag will prevent the game from preforming any shield mesh effect code, which can be useful if a mod does not use those shield mesh effects.
*Syntax: '''''Boolean'''''
*Default Value: false}}

===$Disable all non-custom generic debris:===
{{Table250|
*Provides one simple control to turn off all non-custom generic debris (the tiny debris shards that are typically spawned when a ship/subsystem explodes). Note, generic debris that is manually specified in the ships table will still be spawned, this is only for turning off non-custom debris.
*Syntax: '''''Boolean'''''
*Default Value: false}}

===$Render insignias as decals:===
{{Table260|
*If set, insignias will be rendered using the decal system. This will make insignias render with correct and deferred lighting, and fix issues with apparent fading
*Models must be set up correctly for this to work! A model can have multiple insignias, with multiple polygon faces each. To enable this option, each visible insignia must have its own insignia entry in the model. If multiple visible insignias are incorrectly consolidated into one insignia entry with disjointed polygons, this will cause graphical artifacts.
*For reference, check out the retail FS2 models, which are set up correctly.
*Syntax: '''''Boolean'''''
*Default Value: false}}

==#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'''''}}

===$Use weapon class impact sounds for hits to player:===
{{Table224|
Allows weapons that hit the player to play their specific impact sounds, not the hard-coded default sounds.
*Syntax: '''''Boolean'''''
}}

===$Play thruster sounds for the player:===
{{Table232|
If the player's ship has thruster sounds defined, this will ensure they are played like normal, since they are typically suppressed.
*Syntax: '''''Boolean'''''
}}

===$Unify minimum engine sound:===
{{Table250|
Allows $Minimum Engine Volume in ships.tbl to work for all ship classes. By default, that value only triggers for non-huge ships.
*Syntax: '''''Boolean'''''
}}

===$Disabled or disrupted engines are silent:===
{{Table250|
If set, engines will not play their engine noise if the ship is disabled or a disrupted (such as disruptions caused by an active EMP effect or a weapon with the "electronics" flag).
*Syntax: '''''Boolean'''''
}}

==#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'''''}}

===$Add Message Head Ani Files:===
{{table224|
FRED will append each +Head entry listed below to the head ani selection list in the Event Editor.}}

====+Head:====
{{table224|
The head ani filename to add. Extensions will be stripped if included.
NOTE: Pay attention to file names or anis with a,b, c variation not display in-game (unless called directly). Proper name seems to be Head-xxxNa, Head-xxxNb, with N being some number and XXX being whatever you want. Needs further testing and confirmation
*Syntax: '''''+Head: String'''''}}

===$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'''''}}

===$FRED Briefing window resolution:===
{{table224|
The width and height of the briefing window in FRED. Defaults to 888x371. Note that changing this only affects FRED and can cause a mismatch to the ingame briefing view which defaults to 888x371 (or 555x232 for 640 base res).
*Syntax: '''''integer, integer'''''
*Default Value: '''''888,371'''''}}

===$Ignore Music Files In Music Player:===
{{table232|Music files in this section will not be added to FRED's built-in music player.}}
====+File:====
{{table232|Specifies a file
*Syntax: '''''string'''''}}

===$FRED spacemouse nonlinearities:===
{{table232|
Allows setting custom nonlinearities and scaling for controlling FRED with a spacemouse.
}}
====+Sideways exponent:====
{{table232|
The exponent for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Sideways scale:====
{{table232|The multiplier for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards exponent:====
{{table232|The exponent for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards scale:====
{{table232|The multiplier for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards exponent:====
{{table232|The exponent for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards scale:====
{{table232|The multiplier for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch exponent:====
{{table232|The exponent for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch scale:====
{{table232|The multiplier for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank exponent:====
{{table232|The exponent for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank scale:====
{{table232|The multiplier for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading exponent:====
{{table232|The exponent for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading scale:====
{{table232|The multiplier for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}

===$Skybox internal depth consistency:===
{{table250|If enabled, this will allow skyboxes that use submodels to render the submodels with proper Z-sorting if the 'No Z-Buffer' check box is set to on in FRED. In other words, parts of the skybox closer to the origin point will render in front of sections further away, as might be expected. This flag is enabled by default for FSO version 25.0 onwards
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

==#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. This fixes missile impacts to submodels whose center lies outside the geometry of the submodel. In other words, without this flag, a missile might detonate in the middle of the "bowl" of a concave submodel; with this flag, the missile will travel to the other side of the submodel before it detonates.
*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'''''

===$Use 3d ship select:===
{{Table224|
*Whether or not to use 3D models for ship select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d ship icons:===
{{Table224|
*Whether or not to use 3D models for ships in ship/weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d weapon select:===
{{Table224|
*Whether or not to use 3D models for weapon select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d weapon icons:===
{{Table224|
*Whether or not to use 3D models for weapons in weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$FS2 effect grid color:===
{{Table250|
*Specifies the grid color for the FS2 loadout animation effect
*Syntax: '''''Integer, Integer, Integer'''''
*Default Value: '''''0, 200, 0'''''}}

===$FS2 effect scanline color:===
{{Table250|
*Specifies the scan-line color for the FS2 loadout animation effect
*Syntax: '''''Integer, Integer, Integer'''''
*Default Value: '''''0, 255, 0'''''}}

===$FS2 effect grid density:===
{{Table250|
*Specifies the number of grid lines in the FS2 loadout animation effect
*Syntax: '''''Integer'''''
*Default Value: '''''7'''''}}

===$FS2 effect wireframe color:===
{{Table250|
*Specifies the wireframe color for the FS2 loadout animation effect
*Syntax: '''''Integer, Integer, Integer'''''
*Default Value: '''''80, 49, 160'''''}}

===$Use 3d overhead ship:===
{{Table224|
*Whether or not to use 3D models for ship overhead view instead of a bitmap in weapon select
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Default overhead ship style:===
{{Table224|
*This specifies which style of overhead view to use if 3d overhead view is active
*Syntax: '''''String'''''
*Possible options are "ROTATE" or "TOPVIEW"
}}
{{Table250|
*'''+Overhead Line Color 1:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (64, 192, 192)
*'''+Overhead Line Color 2:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (192, 128, 64)
*'''+Overhead Line Color 3:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (175, 175, 175)
*'''+Overhead Line Color 4:'''
** The RGB color for ship secondary bank 1.
**Syntax: '''''Color''''', (red, green, blue) respectively, integer value from 0 to 255
**Default value: (100, 100, 100)
}}

===$Always refresh selected weapon when viewing loadout:===
{{Table232|
*When set to true, this always refreshes the weapon shown in view box on the right side of the screen when opening the weapon loadout view. This ensures the viewed weapon is one that can actually be on the selected ship when first clicking on the weapon loadout screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$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'''''}}

===$Movie subtitle color:===
{{Table242|
*Specifies which color should be used for displaying subtitles in the cutscene player.
*Syntax: '''''Integer, Integer, Integer, Integer'''''
*Default Value: '''''255, 255, 255, 255'''''}}

===$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|
*Mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. By default is now ON, and can be accessed by going to the Options menu and pressing F3.
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

===$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'''''}}

===$Apply HUD shudder to chase view:===
{{Table232|
*Applies hud shudder (afterburner and engine wash) also to chase view. Does not override the command line toggle.
*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'''''}}

===$Lead indicator behavior:===
{{Table224|
Changes how Lead Indicators behave when multiple weapon banks are linked and in range.
When set to default, if you have linked weapons, only the indicator for the one with the farthest range will be drawn.
When set to multiple, a lead indicator is drawn for all primary weapons in range when you have them linked.
When set to average, a single lead indicator is drawn in the average of the position where each of them would usually be drawn.
*Syntax: '''''String'''''
** Valid options are '''''default''''', '''''multiple''''' and '''''average'''''
*Default Value: '''''default'''''
}}

===$Use distant firepoint for all turrets:===
{{Table224|
*Causes the game to use firepoint-based target leading calculations for all turrets. This is useful if all or most turrets in a given mod has firepoints that are distant from their center-point.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Enable Discord rich presence:===
{{Table224|
*Enables or disables the built-in Discord game-status reporting.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Always hide hidden ships in hotkey list:===
{{Table224|
*Whether or not to always hide ships with HIDDEN hotkey (set in FRED), even in the in-mission hotkey menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Allow automatically assigning personas:===
{{Table232|
*Whether or not the game will automatically assign personas to ships that have no persona set.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Countermeasures use capacity:===
{{Table232|
*Whether or not Countermeasures use tabled capacity.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Calculate subsystem hitpoints after parsing:===
{{Table234|
*Causes subsystem hitpoints to be calculated after all ships.tbl and -shp.tbm files have been parsed. This allows subsystem percentages to correctly reflect the final hull value rather than the first hull value encountered.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Contrails use absolute speed:===
{{Table240|
*Causes contrails to be created based on speed in any direction, rather than just forward speed. This allows contrails to appear when a ship is moving in a direction other than forwards.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix scripted velocity:===
{{Table242|
*If this setting is enabled, object velocity set via script will wholly determine the change in position for that frame, ignoring ''all'' other in-engine concerns. Otherwise, the game engine will likely overwrite/ignore any changes, depending on when the changes were made in the frame.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Preload briefing icon models:===
{{Table250|
*If set, this forces preloading of models used for briefing icons. This only loads models used for icons that haven't already been loaded for the mission. This is useful for SCPUI's where hovering over an icon shows the model without having to click on it and the stutter when it loads models not used in mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Behavior for pressing Escape key in options menu:===
{{Table250|
*If set to 'save', the escape key for the HUD and Options screen saves options when leaving those screens (ie it does the same thing as pressing Ctrl-Enter/Accept). By default (or if set to 'default') the Escape key will not save any changed values when exiting those screens.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Use closest distance method for 'Target Hostile Bomb or Bomber' control:===
{{Table250|
*If set to true, the 'Target Hostile Bomb or Bomber' control will target the closest hostile bomb or bomber, similar to how the 'Target Closest Hostile' key works. By default, the 'Target Hostile Bomb or Bomber' control will not sort by distance and simply only target in order of oldest to youngest objects (ie which object spawned first in the mission).
*Syntax: '''''Boolean'''''
*Default Value: '''''false'''''}}

===$Objects targeted with 'Target Hostile Bomb or Bomber' control:===
{{Table250|
*Determines what can be targeted when using the 'Target Hostile Bomb or Bomber' control. By default this control targets both bombs and bombers, which is the behavior if this field is set to 'default' or 'bombs and bombers'. If set to 'only bombs', the key will only target bombs and not target bombers. If set to 'only bombers', the key will only target bombers and not target bombs.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Fix asteroid/debris field bounding box checks:===
{{Table250|
*Fixes a bug where asteroid and debris fields did not properly check for whether large ships were within bounds.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable intro cutscene:===
{{Table250|
*If set, this disables loading of any cutscenes as the game starts that might play before the player reaches the pilot select screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Show locked status for scramble missions:===
{{Table250|
*If set, scramble mission will show a text line right below the words 'Weapons Loadout' that states "Ships/Weapons Locked" (XSTR 749), thus the player can easily see their loadouts are locked and they do not have to check the loaoout buttons on every mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable expensive turret target check:===
{{Table250|
*If set, this value speeds up turret target checking. By default, turret target acquisition was spending a lot of time doing a raycast, the result of which was barely used at all. If we don't need the target normal, all it does is get a target point slightly more accurate, but in practice it really isn't noticeable at all whether the target point of the turret is actually on the surface of the ship, or maybe on the other side of the ship.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Threshold below which shield skips damage:===
{{Table250|
*By default, FSO logic dictates that shields collisions and any related sound or visuals related to shields are skipped if the shields are under 10%. This value allows modders to customize the value, though the value must be between 0.0 and 1.0.
*Syntax: '''''Float'''''
*Default Value: '''''0.1'''''}}

===$Minimum ship radius for persistent debris::===
{{Table250|
*Ships with a radius larger than this value will have infinite debris lifetimes.
*Syntax: '''''Float'''''
*Default Value: '''''50'''''}}

===$Zero-radius explosions skip fireballs:===
{{Table260|
*If set, explosions with a visual radius of 0 will not have fireballs created, and will not have the fireball lifetime added to the explosion lifetime.
*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]]

Ai profiles.tbl

2026-08-16T12:54:30Z

Wookieejedi: add strafing tuning

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''
*'''purge player-issued form-on-wing after subsequent order'''}}
{{Table260|
*'''$fix 'ignore if dead' flag:'''}}
{{Table262|
*'''$fix target updating with strafe:'''
*'''$no collision avoidance for kamikaze fighters:'''
*'''$fix big ship waypoint completion:'''
*'''$fix shockwave expiring before dealing damage:'''
*'''$fix fighter/bomber AI recovers after engines repaired:'''
}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$max allies rearming threshold:===
{{Table250|
*The maximum allowed number of allies that are allowed to be rearming at the same time. It should be noted that the effect is more noticeable at higher numbers.
*2 by default.
*Syntax: '''''Integer'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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).}}
{{Table260|
*As of 26.0, the "alt2" mode is available. The alt2 mode is like alt1 but allows shortcutting.}}

===$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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$fix target updating with strafe:===
{{Table262|
*Fixes edge-case of AI of fighters/bombers remaining stationary if a fighter/bomber enters strafe mode attacking a large ship and that large ship dies or departs. By default, this edge-case results in the fighter/bomber AI slowing down to 0 and then not moving until another order is issued. Enabling this flag properly allows the fighter/bomber to avoid this issue and move properly.
*Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe retreat collide time:===
{{Table26.2|
*For strafe attacks against big ships, small ships calculate a point relative to the big ship they are attacking and move towards during it strafe. This value is how long until the attacking ship will reach the strafe attack point, when duration to the point is less than this value begin retreat from strafe (IE turn around and perform a new strafe). Default is 2.0 seconds. Note, a new strafe will also trigger if the check for '$strafe retreat collide distance:' is true.
**Syntax: '''''Float''''' (defaults to 2.0)}}

===$strafe retreat collide distance:===
{{Table26.2|
*For strafe attacks against big ships, small ships calculate a point relative to the big ship they are attacking and move towards during it strafe. This value is the distance until the attacking ship will reach the strafe attack point, when distance to the point is less than this value begin retreat from strafe (IE turn around and perform a new strafe). Note, a new strafe will also trigger if the check for '$strafe retreat collide time:' is true. Default is 200 meters.
**Syntax: '''''Float''''' (defaults to 200.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

===$don't issue form-on-wing goals at mission start:===
{{Table250|
*Normally, at the beginning of a mission, player wings that do not have an initial goal will be given an initial goal to form on the player. Wings in the loadout screen (aka "starting" wings) will also, if they do not have an initial goal, be issued the same goal if they arrive after mission start. This flag disables that behavior.
*Syntax: '''''Boolean'''''}}

===$default form-on-wing priority:===
{{Table250|
*The default goal priority to be used when issuing a form-on-wing order via sexp or script. If not specified, this is 99. Note that orders issued via the HUD communications system will use the standard communications priorities (100 for ships and 95 for wings) regardless of this setting.
*Syntax: '''''Integer'''''}}

===$do not clear goals when running form-on-wing:===
{{Table250|
*Normally, as soon as a form-on-wing goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the form-on-wing behavior while forgetting both the form goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not clear goals when running stay-still:===
{{Table250|
*Normally, as soon as a stay-still goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the stay-still behavior while forgetting both the stay-still goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not set override when assigning form-on-wing:===
{{Table250|
*Normally, any form-on-wing goal, regardless of how it is assigned, is given a <tt>Goal_override</tt> flag. This causes its goal to be evaluated as the top priority goal, regardless of its actual priority or any other goal's priority. This flag prevents <tt>Goal_override</tt> from being assigned, causing form-on-wing to follow the normal goal prioritization logic.
*Syntax: '''''Boolean'''''}}

===$purge player-issued form-on-wing after subsequent order:===
{{Table250|
*Causes any form-on-wing goal issued by the player (i.e. via the HUD communications system) to be removed from a ship's goal list (even if it is not the current goal) when the ship is given another goal of any priority. This flag can be useful for mods which configure form-on-wing goals to use the same execution and prioritization logic as normal goals. Since form-on-wing goals are typically temporary, regardless of their priority, this flag enforces that temporary nature. By using this flag, mission designers can ensure that mission-directed AI goal logic is followed regardless of form-on-wing status.
*Syntax: '''''Boolean'''''}}

===$cancel future waves of any wing launched from an exited ship:===
{{Table250|
*Infamously, in FSO, a wing whose mothership is destroyed will not, itself, be considered destroyed if it has more waves remaining, because wing cleanup and logging typically only happen when the last ship in the last wave exits the mission. Instead, with no mothership to arrive from, waves will simply no longer arrive. Events that check to see if the wing is destroyed or departed will never fire. This flag fixes that behavior, ensuring that the wing is cleaned up and logged properly, by using the same logic as the enhanced cancel-future-waves SEXP operator.
*Syntax: '''''Boolean'''''}}

===$fix 'ignore if dead' flag:===
{{Table260|
*The subsystem flag "ignore if dead" that many mods use is supposed to "prevent homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target." The code was bugged though and unfortunately what ends up happening is that the weapon dumb fire instead of homes. This bug means if you destroy a subsystem with this flag, then lock onto it with an aspect weapon and fire the weapon, the weapon will just dumb fire. Enabling this flag fixes this, and actually makes "ignore if dead" flag work as intended.
*Syntax: '''''Boolean'''''}}

===$no collision avoidance for kamikaze fighters:===
{{Table262|
*Kamikaze fighters will often veer away from their target because they are paradoxically trying not to collide with it. When this flag is enabled, they will not veer away.
*Syntax: '''''Boolean'''''}}

===$fix big ship waypoint completion:===
{{Table262|
*Fixes the "spinning Orion" waypoint completion bug. When this flag is enabled, a) big ships complete a waypoint within their radius rather than sqrt(radius); and b) completion no longer requires moving 0.1m in a single frame.
*Syntax: '''''Boolean'''''}}

===$fix shockwave expiring before dealing damage:===
{{Table262|
*Fixes shockwave damage so that shockwaves that move faster than 1-frame properly still deal damage. Without this fix it is possible the shockwave may have lifetime shorter than one frame (e.g. high speed, small radius), which by default results in shockwave applying no damage.
*Syntax: '''''Boolean'''''}}

===$fix fighter/bomber AI recovers after engines repaired:===
{{Table262|
*Fixes edge-case of AI of fighters/bombers remaining stationary if their engines were destroyed and then repaired. This could occur if their engines get temporarily disabled and then repaired and their current target dies/departs, and by default this results in the fighter/bomber not moving even when their engines are repaired. Enabling this fix allows the fighter/bomber to avoid this issue and move properly.
*Syntax: '''''Boolean'''''}}

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

2026-07-20T01:26:29Z

Wookieejedi: add 26.2 enabled

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''
*'''purge player-issued form-on-wing after subsequent order'''}}
{{Table260|
*'''$fix 'ignore if dead' flag:'''}}
{{Table262|
*'''$fix target updating with strafe:'''
*'''$no collision avoidance for kamikaze fighters:'''
*'''$fix big ship waypoint completion:'''
*'''$fix shockwave expiring before dealing damage:'''
*'''$fix fighter/bomber AI recovers after engines repaired:'''
}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$max allies rearming threshold:===
{{Table250|
*The maximum allowed number of allies that are allowed to be rearming at the same time. It should be noted that the effect is more noticeable at higher numbers.
*2 by default.
*Syntax: '''''Integer'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$fix target updating with strafe:===
{{Table262|
*Fixes edge-case of AI of fighters/bombers remaining stationary if a fighter/bomber enters strafe mode attacking a large ship and that large ship dies or departs. By default, this edge-case results in the fighter/bomber AI slowing down to 0 and then not moving until another order is issued. Enabling this flag properly allows the fighter/bomber to avoid this issue and move properly.
*Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

===$don't issue form-on-wing goals at mission start:===
{{Table250|
*Normally, at the beginning of a mission, player wings that do not have an initial goal will be given an initial goal to form on the player. Wings in the loadout screen (aka "starting" wings) will also, if they do not have an initial goal, be issued the same goal if they arrive after mission start. This flag disables that behavior.
*Syntax: '''''Boolean'''''}}

===$default form-on-wing priority:===
{{Table250|
*The default goal priority to be used when issuing a form-on-wing order via sexp or script. If not specified, this is 99. Note that orders issued via the HUD communications system will use the standard communications priorities (100 for ships and 95 for wings) regardless of this setting.
*Syntax: '''''Integer'''''}}

===$do not clear goals when running form-on-wing:===
{{Table250|
*Normally, as soon as a form-on-wing goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the form-on-wing behavior while forgetting both the form goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not clear goals when running stay-still:===
{{Table250|
*Normally, as soon as a stay-still goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the stay-still behavior while forgetting both the stay-still goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not set override when assigning form-on-wing:===
{{Table250|
*Normally, any form-on-wing goal, regardless of how it is assigned, is given a <tt>Goal_override</tt> flag. This causes its goal to be evaluated as the top priority goal, regardless of its actual priority or any other goal's priority. This flag prevents <tt>Goal_override</tt> from being assigned, causing form-on-wing to follow the normal goal prioritization logic.
*Syntax: '''''Boolean'''''}}

===$purge player-issued form-on-wing after subsequent order:===
{{Table250|
*Causes any form-on-wing goal issued by the player (i.e. via the HUD communications system) to be removed from a ship's goal list (even if it is not the current goal) when the ship is given another goal of any priority. This flag can be useful for mods which configure form-on-wing goals to use the same execution and prioritization logic as normal goals. Since form-on-wing goals are typically temporary, regardless of their priority, this flag enforces that temporary nature. By using this flag, mission designers can ensure that mission-directed AI goal logic is followed regardless of form-on-wing status.
*Syntax: '''''Boolean'''''}}

===$cancel future waves of any wing launched from an exited ship:===
{{Table250|
*Infamously, in FSO, a wing whose mothership is destroyed will not, itself, be considered destroyed if it has more waves remaining, because wing cleanup and logging typically only happen when the last ship in the last wave exits the mission. Instead, with no mothership to arrive from, waves will simply no longer arrive. Events that check to see if the wing is destroyed or departed will never fire. This flag fixes that behavior, ensuring that the wing is cleaned up and logged properly, by using the same logic as the enhanced cancel-future-waves SEXP operator.
*Syntax: '''''Boolean'''''}}

===$fix 'ignore if dead' flag:===
{{Table260|
*The subsystem flag "ignore if dead" that many mods use is supposed to "prevent homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target." The code was bugged though and unfortunately what ends up happening is that the weapon dumb fire instead of homes. This bug means if you destroy a subsystem with this flag, then lock onto it with an aspect weapon and fire the weapon, the weapon will just dumb fire. Enabling this flag fixes this, and actually makes "ignore if dead" flag work as intended.
*Syntax: '''''Boolean'''''}}

===$no collision avoidance for kamikaze fighters:===
{{Table262|
*Kamikaze fighters will often veer away from their target because they are paradoxically trying not to collide with it. When this flag is enabled, they will not veer away.
*Syntax: '''''Boolean'''''}}

===$fix big ship waypoint completion:===
{{Table262|
*Fixes the "spinning Orion" waypoint completion bug. When this flag is enabled, a) big ships complete a waypoint within their radius rather than sqrt(radius); and b) completion no longer requires moving 0.1m in a single frame.
*Syntax: '''''Boolean'''''}}

===$fix shockwave expiring before dealing damage:===
{{Table262|
*Fixes shockwave damage so that shockwaves that move faster than 1-frame properly still deal damage. Without this fix it is possible the shockwave may have lifetime shorter than one frame (e.g. high speed, small radius), which by default results in shockwave applying no damage.
*Syntax: '''''Boolean'''''}}

===$fix fighter/bomber AI recovers after engines repaired:===
{{Table262|
*Fixes edge-case of AI of fighters/bombers remaining stationary if their engines were destroyed and then repaired. This could occur if their engines get temporarily disabled and then repaired and their current target dies/departs, and by default this results in the fighter/bomber not moving even when their engines are repaired. Enabling this fix allows the fighter/bomber to avoid this issue and move properly.
*Syntax: '''''Boolean'''''}}

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

2026-07-19T04:16:05Z

Wookieejedi: add new AI flags

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''
*'''purge player-issued form-on-wing after subsequent order'''}}
{{Table260|
*'''$fix 'ignore if dead' flag:'''}}
{{Table262|
*'''$no collision avoidance for kamikaze fighters:'''
*'''$fix big ship waypoint completion:'''}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$max allies rearming threshold:===
{{Table250|
*The maximum allowed number of allies that are allowed to be rearming at the same time. It should be noted that the effect is more noticeable at higher numbers.
*2 by default.
*Syntax: '''''Integer'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$fix target updating with strafe:===
{{Table262|
*Fixes edge-case of AI of fighters/bombers remaining stationary if a fighter/bomber enters strafe mode attacking a large ship and that large ship dies or departs. By default, this edge-case results in the fighter/bomber AI slowing down to 0 and then not moving until another order is issued. Enabling this flag properly allows the fighter/bomber to avoid this issue and move properly.
*Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

===$don't issue form-on-wing goals at mission start:===
{{Table250|
*Normally, at the beginning of a mission, player wings that do not have an initial goal will be given an initial goal to form on the player. Wings in the loadout screen (aka "starting" wings) will also, if they do not have an initial goal, be issued the same goal if they arrive after mission start. This flag disables that behavior.
*Syntax: '''''Boolean'''''}}

===$default form-on-wing priority:===
{{Table250|
*The default goal priority to be used when issuing a form-on-wing order via sexp or script. If not specified, this is 99. Note that orders issued via the HUD communications system will use the standard communications priorities (100 for ships and 95 for wings) regardless of this setting.
*Syntax: '''''Integer'''''}}

===$do not clear goals when running form-on-wing:===
{{Table250|
*Normally, as soon as a form-on-wing goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the form-on-wing behavior while forgetting both the form goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not clear goals when running stay-still:===
{{Table250|
*Normally, as soon as a stay-still goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the stay-still behavior while forgetting both the stay-still goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not set override when assigning form-on-wing:===
{{Table250|
*Normally, any form-on-wing goal, regardless of how it is assigned, is given a <tt>Goal_override</tt> flag. This causes its goal to be evaluated as the top priority goal, regardless of its actual priority or any other goal's priority. This flag prevents <tt>Goal_override</tt> from being assigned, causing form-on-wing to follow the normal goal prioritization logic.
*Syntax: '''''Boolean'''''}}

===$purge player-issued form-on-wing after subsequent order:===
{{Table250|
*Causes any form-on-wing goal issued by the player (i.e. via the HUD communications system) to be removed from a ship's goal list (even if it is not the current goal) when the ship is given another goal of any priority. This flag can be useful for mods which configure form-on-wing goals to use the same execution and prioritization logic as normal goals. Since form-on-wing goals are typically temporary, regardless of their priority, this flag enforces that temporary nature. By using this flag, mission designers can ensure that mission-directed AI goal logic is followed regardless of form-on-wing status.
*Syntax: '''''Boolean'''''}}

===$cancel future waves of any wing launched from an exited ship:===
{{Table250|
*Infamously, in FSO, a wing whose mothership is destroyed will not, itself, be considered destroyed if it has more waves remaining, because wing cleanup and logging typically only happen when the last ship in the last wave exits the mission. Instead, with no mothership to arrive from, waves will simply no longer arrive. Events that check to see if the wing is destroyed or departed will never fire. This flag fixes that behavior, ensuring that the wing is cleaned up and logged properly, by using the same logic as the enhanced cancel-future-waves SEXP operator.
*Syntax: '''''Boolean'''''}}

===$fix 'ignore if dead' flag:===
{{Table260|
*The subsystem flag "ignore if dead" that many mods use is supposed to "prevent homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target." The code was bugged though and unfortunately what ends up happening is that the weapon dumb fire instead of homes. This bug means if you destroy a subsystem with this flag, then lock onto it with an aspect weapon and fire the weapon, the weapon will just dumb fire. Enabling this flag fixes this, and actually makes "ignore if dead" flag work as intended.
*Syntax: '''''Boolean'''''}}

===$no collision avoidance for kamikaze fighters:===
{{Table262|
*Kamikaze fighters will often veer away from their target because they are paradoxically trying not to collide with it. When this flag is enabled, they will not veer away.
*Syntax: '''''Boolean'''''}}

===$fix big ship waypoint completion:===
{{Table262|
*Fixes the "spinning Orion" waypoint completion bug. When this flag is enabled, a) big ships complete a waypoint within their radius rather than sqrt(radius); and b) completion no longer requires moving 0.1m in a single frame.
*Syntax: '''''Boolean'''''}}

===$fix shockwave expiring before dealing damage:===
{{Table262|
*Fixes shockwave damage so that shockwaves that move faster than 1-frame properly still deal damage. Without this fix it is possible the shockwave may have lifetime shorter than one frame (e.g. high speed, small radius), which by default results in shockwave applying no damage.
*Syntax: '''''Boolean'''''}}

===$fix fighter/bomber AI recovers after engines repaired:===
{{Table262|
*Fixes edge-case of AI of fighters/bombers remaining stationary if their engines were destroyed and then repaired. This could occur if their engines get temporarily disabled and then repaired and their current target dies/departs, and by default this results in the fighter/bomber not moving even when their engines are repaired. Enabling this fix allows the fighter/bomber to avoid this issue and move properly.
*Syntax: '''''Boolean'''''}}

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

Subsystem

2026-06-08T12:16:03Z

Wookieejedi: tune ignore if dead language

{{Fileversion|7119}}

The Options listed in this article should entered into the '''$Subsystem''' section of the [[Ships.tbl]]. Multiple Subsystems may be defined.

*All subsystems a ship can have must be defined in ship's model file (.pof).
*See [[Subobject_and_subsystem_properties|Subobject and subsystem properties]] for information about what subsystems the game has defined meaning for.

{{Table3610|
*[[Animation_Code|Animation Code]] can be applied to the subsystems that consist of submodels, like multi-part turrets.
{{Table220|
'''DEPRECATED''': Unless setting initial orientation of multipart turrets, consider using the [[Animation.tbl]] in combination with [[Ships.tbl#.24Animations:|$Animations:]]
}}
}}

==$Subsystem:==
*The name of the subsystem as defined in .pof file, % of ship's total hitpoints the subsystem has and rotation time (360 degrees) for multi-part turrets. Note: Assigning zero to the %-hitpoint entry causes the subsystem to be without hitpoints, like fighterbays on some capital ships.
*Syntax: '''''String''''', '''''Float''''', '''''Float''''', name of the subsystem followed by the subsystem hitpoints as % of ships hitpoints and seconds per 360 degree turn. Subsystem name must be the same as described in model file (.pof).
{{Table3610|
*Entries can be left empty in which case game uses default values}}
**Example: communications, 5, 0.0

===$Alt Subsystem Name:===
{{Table3610|
*Defines the alternate name for the subsystem. This name is shown for example in the targeting window when subsystem is targeted.
*Syntax: '''''String'''''}}
{{Table3611|
*Option to use pipe character '<nowiki>|</nowiki>' to force line breaks into the alt subsystem name}}

===$Alt Damage Popup Subsystem Name:===
{{Table3611|
*Defines the alternate name for the subsystem when it is displayed on the '''damaged systems''' popup.
*Syntax: '''''String'''''}}

===$Armor Type:===
{{Table3610|
* '''REQUIRES ADDITIONAL TABLE'''. Defines armor type used for the subsystem. If subsystem armor type is not defined ships armor type is used instead.
* Syntax: '''''String''''', as defined in [[armor.tbl]]}}

===$Default PBanks:===
*Defines default primary weapon for the turret
*Syntax: ( '''''"String"''''' )
**Example: ( ''"Subach HL-7"'' )

===$PBank Capacity:===
{{Table3610|
*Defines ammunition capacity of turrets ballistic primary weapon.
*Syntax: ( '''''Integer''''' )}}

===$Default SBanks:===
*Defines default secondary weapon for the turret
*Syntax: ( '''''"String"''''' )

===$SBank Capacity:===
*Defines ammunition capacity of turrets secondary weapon.
*Syntax: ( '''''Integer''''' )

===$Engine Wash:===
*All engines may use information concerning the engine wash. Engine washes are usually used only with larger vessels.
*Syntax: '''''String''''', name as defined in Engine Wash section in [[ships.tbl]]
**Example: ''Default1000''

===$AliveSnd:===
{{Table3610|
*Specifies a sound to play from the subsystem while it is not destroyed.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$DeadSnd:===
{{Table3610|
*Specifies a sound to play from the subsystem while it is destroyed.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$RotationSnd:===
{{Table3613|
*Can be used to define a sound that is played when this subsystem rotates.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Turret Base RotationSnd:===
{{Table3611|
*Defines the sound which is played when the turrets base rotates
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Turret Gun RotationSnd:===
{{Table3611|
*Defines the sound which is played when the turrets guns change their elevation
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Turret BaseSnd Volume:===
{{Table3611|
*Defines the multiplier for the sound volume for turret base rotations
*Syntax: '''''Float'''''}}

===$Turret GunSnd Volume:===
{{Table3611|
*Defines the multiplier for the sound volume for turret guns change their elevation
*Syntax: '''''Float'''''}}

===$AWACS:===
*Sets this subsystem's effective AWACS range. (AWACS reveals stealthed ships, cuts through nebula fog.)
*Syntax: intensity, '''''Float''''', and radius, '''''Float''''', - intensity is an ignored but required field. - radius is the maximum range of the AWACS.

===$Scan time:===
{{Table220|
*Scan time for this subsystem. If this is not set, the scan time for the ship is used for the subsystem
*Syntax: '''''Integer''''' in milliseconds
}}

===$Maximum Barrel Elevation:===
{{Table3611|
*Defines the maximum barrel elevation for the turret gun object of a multipart turret.
*Basically 'inverse FOV'.
*Syntax: '''''Integer''''', from 0 to 90}}

===$Turret Base FOV:===
{{Table3611|
*Defines the FOV of the turret base of a multipart turret, possibly restricting how far it can traverse left and right.
*Syntax: '''''Integer''''', from 0 to 359}}

===$Turret Barrel FOV:===
{{Table224|
*Defines the overall FOV of the turret, overriding any FOV defined in the POF.
*Syntax: '''''Integer''''', from 0 to 359}}

===$Turret Reset Delay:===
{{Table3611|
*Defines the time after losing the target before the turret begins to reset itself
*Syntax: '''''Integer''''', in milliseconds}}

===$Turret Optimum Range:===
{{Table3611|
*Defines the optimum range for the turret
*Syntax: '''''Float'''''}}

===$Turret Direction Preference:===
{{Table3611|
*Defines the turrets preference to keep targeting targets based how far the turret should turn instead of nearest target
*The higher the value the higher the preference to keep targeting targets close to previous targets direction
*Syntax: '''''Integer''''', from 0 to 100, 0 disables the preference setup}}

===$Target Priority:===
{{Table3611|
*Defines the target priorities, and their order for the turret
*Syntax: '''''String list'''''}}

===$Max Turrets per Bomb:===
{{Table3613|
*Limits the number of turrets that can be targeting the same bomb.
*When this is set, when this turret tries to target a bomb, it will check to see how many turrets are already targeting it and only choose it as a target if there are less than this number.
*This allows control over the default behavior, where every turret will fire at the leading bomb.
*Syntax: '''''Integer'''''}}

===$Max Turrets per Target:===
{{Table3613|
*Limits the number of turrets that can be targeting the same target.
*'''ONLY AFFECTS SMALL TARGETS''' such as fighters and bombers. This limit does '''NOT''' apply vs large ships.
*When this is set, when this turret tries to target a ship, it will check to see how many turrets are already targeting it and only choose it as a target if there are less than this number.
*This helps turrets spread their efforts out among multiple targets.
*Syntax: '''''Integer'''''}}

===$ROF:===
{{Table3613|
*Defines the modifier applied to the turret rate of fire (ROF).

====+Use firingpoints====
*Modifies (multiplies) the rate of fire by the number of firingpoints the turret has.

====+Multiplier:====
*Checked only if ''+Use firingpoints'' has not been defined
*If set to larger than 0 the value acts as multiplier
*If set to 1.0 the feature is disabled
*If set to equal to or smaller than 0 it as if ''+Use firingpoints'' option would have been enabled
*Syntax: '''''Float'''''}}

===$Flags:===
{{Table3610|
*Can be used to sets additional subsystem related properties
*Syntax: ( '''''"String" "String"''''' )
*List of available flags:

===="untargetable"====
*Subsystem cannot be targeted

===="carry no damage"====
*Damage caused to the subsystem will not carry over to the parent ship

===="use multiple guns"====
*Enables the turret to fire all equipped weapons, picking a not-in-use firing point at each trigger. Not to be confused with 'Salvo mode'.

===="fire down normals"====
*Forces the turret to fire along the turret normals - regardless of the swarm setting.

===="check hull"====
*Forces the firing turret to check against the parent model if valid line of sight exists between the firingpoint and the target.}}

{{Table3611|
===="fixed firingpoints"====
*Forces the firing turret to retain the firingpoints of their weapons: if the turret has multiple banks, the first bank will only fire from the first firepoint, the second bank only from the second firepoint, and so on. Maximum number of weapons is the same as maximum number of weapons in turret (3 primary, 4 secondary)

===="salvo mode"====
*Forces the firing turret to use only the first weapon defined for it but fires it simultaneously from all the firing points. Not to be confused with 'use multiple guns'

===="no subsystem targeting"====
*Prevents the firing turret from targeting targets subsystems - instead forces the turret to fire randomly at the targets hull.

===="fire on target"====
*Prevents the turret from firing unless the turret barrels (firingpoints) and targets are aligned.

===="reset when idle"====
*Forces the turret to reset to its initial position if it has no targets.

===="carry shockwave"====
*Forces the turret to carry damage caused by shockwaves to the hull regardless of other flags.}}

{{Table3613|
===="allow landing"====
*Defines the subsystem as something on which player can attempt to land on

===="target requires fov"====
*Prevents turret from accidentally selecting target out of it field of view (fov) when acquiring targets

===="fov edge checks"====
*The turret will more eagerly acquire targets as long as a sufficient portion of the target is within its fov.

===="no replace"====
*Tells game not to use the replacement submodel (-destroyed) when the subsystem loses all of it's hitpoints.

===="no live debris"====
*Prevents the subsystem from releasing live debris pieces when destroyed

===="ignore if dead"====
*When subsystem has been destroyed prevents homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target. Note, for this to actually work you must also enable the AI Profiles flag of "$fix 'ignore if dead' flag" and/or target the mod to 26.0. If you do not do this then using this flag will mean that any weapon locked onto to a destroyed subsystem with this flag will result in the weapon not homing at all.

===="allow vanishing"====
*Allow subsystem to be destroyed from the ship without sound or graphical effects

===="damage as hull"====
*Treats subsystem as if it were hull when applying damage.

===="starts locked"====
*Turret starts locked and won't shoot until you use a turret-free or turret-free-all SEXP on it.

===="no aggregate"====
*Freespace keeps track of a ships overall functionality (such as if a ship is sensorless, disarmed or disabled) via a total hitpoint count of the associated subsystems. For example if a ship has three engines with 100HP each, the 'engines' count will be at 300HP. Shooting at any of the subsystems with the keyword 'engine' in them will decrement this total, and when it is at 0 then the ship becomes disabled.
*This flag tells FS to ignore the associated subsystem and not count it towards those totals. For example, if a ship had three 100HP engines with one set to 'no aggregate' then the 'engines' count will be 200HP. Shooting the 'no aggregate' engine will not decrement the 'engines' count, and so in other words the status of this engine is irrelevant to whether or not the ship is disabled. In the same way when applied to a turret, the turret's status is irrelevant to whether the ship is disarmed or not.

===="wait for animation"====
*When this flag is active, a turret will only fire after any associated subsystem animations (such as a turret hatch opening) have played out.

===="play fire sound for player"====
*If this turret is on a player ship, play its associated sounds.

===="only target if can fire"====
*Do additional checks to make sure that a turret which cannot fire at its target releases that target.
}}

{{Table3615|
===="no disappear"====
*If this subsystem is a physical subsystem, it won't disappear nor switch to the -destroyed model when destroyed.

===="collide submodel"====
*If this subsystem is a physical subsystem, it will only take damage from hits which impact the submodel. By default damage is taken from all hits within the submodel's radius*2. Does not affect area damage such as shockwaves.

===="allow destroyed rotation"====
*Allows a rotating subobject to continue to rotate even when it has been destroyed
}}

{{Table373|
===="turret use ammo"====
*If the subsystem is a turret, it will use ammo.
**Note: If the turret does not have ammo, it will not fire. Remember that the maximum ammo a turret can hold is the Capacity of the Bank divided by the Cargo Size of the weapon.

===="autorepair if disabled"====
*Allows the subsystem to repair itself even if disabled (normally, disabled subsystems do not repair themselves)

===="don't autorepair if disabled"====
*Inverse of "autorepair if disabled": excludes this subsystem from autorepair if the ship class [[Ships.tbl#.22repair_disabled_subsystems.22|"repair disabled subsystems"]] flag is set

===="share fire direction"====
*If this subsystem is a turret, whenever the turret fires it will make all of the firing points shoot their weapon in the same direction instead of at the same point or set of points on a target.
}}

{{Table381|
===="no damage spew"====
*If this subsystem is hit then there will be no damage spew particles emitted.

===="no impact debris"====
*If this subsystem is hit then no impact debris will be generated.
}}

{{Table250|
===="disable all generic impact debris"====
*Newer name for "no impact debris"--turns off the tiny debris shards that are typically spawned when something impacts a subsystem.
}}

{{Table220|
===="hide turret from loadout stats"====
*This subsystem is not counted as a turret in the auto-generated "+Turrets:" line in the statistics summary window of the ship loadout editor.
}}

{{Table222|
===="turret has distant firepoint"====
*Turret barrel is very long and should be taken into account when aiming (rather than calculating the aim from the turret center)
}}

{{Table242|
===="override submodel impact"====
*If a weapon impacted a submodel, but this subsystem is within range, this subsystem takes priority in the hit sequence rather than the submodel. This allows case-by-case exceptions to the [[Game_settings.tbl#.24Damage_Impacted_Subsystem_First:|$Damage Impacted Subsystem First:]] mod flag.
}}

===[[Animation Code]]===
{{Table3610|
*Option for animating the submodels
{{Table220|
'''DEPRECATED''': Unless setting initial orientation of multipart turrets, consider using the [[Animation.tbl]] in combination with [[Ships.tbl#.24Animations:|$Animations:]]
}}
}}

===$On Beam Warmdown:===
{{Table212|
Specifies an [[Action System|action system]] program set to be executed when a beam attached to this subsystem is starting its warmdown sequence.
}}

==Case Specific Entries==

===Turret===
*All turrets require information concerning the weapon mounted to the turret. The entry can be either '''$Default PBanks''' for turret primaries (including beams) or '''$Default SBanks''' for turret secondaries
{{Table3610|
*[[Animation_Code#Setting_Turret_Angle|Animation Code]] can be used with multi-part turrets.
*Multiple defined weapons will all fire but the targeting is handled by the first weapon in the list. '''Multiple beams are not possible'''. All weapons alternate between the firingpoints of the turret so turrets do not need to have more than one weapon defined no matter how many barrels or firingpoints they have.}}

====Example====

<pre>
$Subsystem: turret01, 1.0, 1.0
$Default PBanks: ( "Terran Turret" )
</pre>

===Engine===

====Example====

<pre>
$Subsystem: engine01, 5.0, 0.0
$Engine Wash: Default1000
</pre>

[[Category:Tables]]

Subsystem

2026-06-08T03:15:10Z

Wookieejedi: ignore if dead update

{{Fileversion|7119}}

The Options listed in this article should entered into the '''$Subsystem''' section of the [[Ships.tbl]]. Multiple Subsystems may be defined.

*All subsystems a ship can have must be defined in ship's model file (.pof).
*See [[Subobject_and_subsystem_properties|Subobject and subsystem properties]] for information about what subsystems the game has defined meaning for.

{{Table3610|
*[[Animation_Code|Animation Code]] can be applied to the subsystems that consist of submodels, like multi-part turrets.
{{Table220|
'''DEPRECATED''': Unless setting initial orientation of multipart turrets, consider using the [[Animation.tbl]] in combination with [[Ships.tbl#.24Animations:|$Animations:]]
}}
}}

==$Subsystem:==
*The name of the subsystem as defined in .pof file, % of ship's total hitpoints the subsystem has and rotation time (360 degrees) for multi-part turrets. Note: Assigning zero to the %-hitpoint entry causes the subsystem to be without hitpoints, like fighterbays on some capital ships.
*Syntax: '''''String''''', '''''Float''''', '''''Float''''', name of the subsystem followed by the subsystem hitpoints as % of ships hitpoints and seconds per 360 degree turn. Subsystem name must be the same as described in model file (.pof).
{{Table3610|
*Entries can be left empty in which case game uses default values}}
**Example: communications, 5, 0.0

===$Alt Subsystem Name:===
{{Table3610|
*Defines the alternate name for the subsystem. This name is shown for example in the targeting window when subsystem is targeted.
*Syntax: '''''String'''''}}
{{Table3611|
*Option to use pipe character '<nowiki>|</nowiki>' to force line breaks into the alt subsystem name}}

===$Alt Damage Popup Subsystem Name:===
{{Table3611|
*Defines the alternate name for the subsystem when it is displayed on the '''damaged systems''' popup.
*Syntax: '''''String'''''}}

===$Armor Type:===
{{Table3610|
* '''REQUIRES ADDITIONAL TABLE'''. Defines armor type used for the subsystem. If subsystem armor type is not defined ships armor type is used instead.
* Syntax: '''''String''''', as defined in [[armor.tbl]]}}

===$Default PBanks:===
*Defines default primary weapon for the turret
*Syntax: ( '''''"String"''''' )
**Example: ( ''"Subach HL-7"'' )

===$PBank Capacity:===
{{Table3610|
*Defines ammunition capacity of turrets ballistic primary weapon.
*Syntax: ( '''''Integer''''' )}}

===$Default SBanks:===
*Defines default secondary weapon for the turret
*Syntax: ( '''''"String"''''' )

===$SBank Capacity:===
*Defines ammunition capacity of turrets secondary weapon.
*Syntax: ( '''''Integer''''' )

===$Engine Wash:===
*All engines may use information concerning the engine wash. Engine washes are usually used only with larger vessels.
*Syntax: '''''String''''', name as defined in Engine Wash section in [[ships.tbl]]
**Example: ''Default1000''

===$AliveSnd:===
{{Table3610|
*Specifies a sound to play from the subsystem while it is not destroyed.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$DeadSnd:===
{{Table3610|
*Specifies a sound to play from the subsystem while it is destroyed.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$RotationSnd:===
{{Table3613|
*Can be used to define a sound that is played when this subsystem rotates.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Turret Base RotationSnd:===
{{Table3611|
*Defines the sound which is played when the turrets base rotates
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Turret Gun RotationSnd:===
{{Table3611|
*Defines the sound which is played when the turrets guns change their elevation
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Turret BaseSnd Volume:===
{{Table3611|
*Defines the multiplier for the sound volume for turret base rotations
*Syntax: '''''Float'''''}}

===$Turret GunSnd Volume:===
{{Table3611|
*Defines the multiplier for the sound volume for turret guns change their elevation
*Syntax: '''''Float'''''}}

===$AWACS:===
*Sets this subsystem's effective AWACS range. (AWACS reveals stealthed ships, cuts through nebula fog.)
*Syntax: intensity, '''''Float''''', and radius, '''''Float''''', - intensity is an ignored but required field. - radius is the maximum range of the AWACS.

===$Scan time:===
{{Table220|
*Scan time for this subsystem. If this is not set, the scan time for the ship is used for the subsystem
*Syntax: '''''Integer''''' in milliseconds
}}

===$Maximum Barrel Elevation:===
{{Table3611|
*Defines the maximum barrel elevation for the turret gun object of a multipart turret.
*Basically 'inverse FOV'.
*Syntax: '''''Integer''''', from 0 to 90}}

===$Turret Base FOV:===
{{Table3611|
*Defines the FOV of the turret base of a multipart turret, possibly restricting how far it can traverse left and right.
*Syntax: '''''Integer''''', from 0 to 359}}

===$Turret Barrel FOV:===
{{Table224|
*Defines the overall FOV of the turret, overriding any FOV defined in the POF.
*Syntax: '''''Integer''''', from 0 to 359}}

===$Turret Reset Delay:===
{{Table3611|
*Defines the time after losing the target before the turret begins to reset itself
*Syntax: '''''Integer''''', in milliseconds}}

===$Turret Optimum Range:===
{{Table3611|
*Defines the optimum range for the turret
*Syntax: '''''Float'''''}}

===$Turret Direction Preference:===
{{Table3611|
*Defines the turrets preference to keep targeting targets based how far the turret should turn instead of nearest target
*The higher the value the higher the preference to keep targeting targets close to previous targets direction
*Syntax: '''''Integer''''', from 0 to 100, 0 disables the preference setup}}

===$Target Priority:===
{{Table3611|
*Defines the target priorities, and their order for the turret
*Syntax: '''''String list'''''}}

===$Max Turrets per Bomb:===
{{Table3613|
*Limits the number of turrets that can be targeting the same bomb.
*When this is set, when this turret tries to target a bomb, it will check to see how many turrets are already targeting it and only choose it as a target if there are less than this number.
*This allows control over the default behavior, where every turret will fire at the leading bomb.
*Syntax: '''''Integer'''''}}

===$Max Turrets per Target:===
{{Table3613|
*Limits the number of turrets that can be targeting the same target.
*'''ONLY AFFECTS SMALL TARGETS''' such as fighters and bombers. This limit does '''NOT''' apply vs large ships.
*When this is set, when this turret tries to target a ship, it will check to see how many turrets are already targeting it and only choose it as a target if there are less than this number.
*This helps turrets spread their efforts out among multiple targets.
*Syntax: '''''Integer'''''}}

===$ROF:===
{{Table3613|
*Defines the modifier applied to the turret rate of fire (ROF).

====+Use firingpoints====
*Modifies (multiplies) the rate of fire by the number of firingpoints the turret has.

====+Multiplier:====
*Checked only if ''+Use firingpoints'' has not been defined
*If set to larger than 0 the value acts as multiplier
*If set to 1.0 the feature is disabled
*If set to equal to or smaller than 0 it as if ''+Use firingpoints'' option would have been enabled
*Syntax: '''''Float'''''}}

===$Flags:===
{{Table3610|
*Can be used to sets additional subsystem related properties
*Syntax: ( '''''"String" "String"''''' )
*List of available flags:

===="untargetable"====
*Subsystem cannot be targeted

===="carry no damage"====
*Damage caused to the subsystem will not carry over to the parent ship

===="use multiple guns"====
*Enables the turret to fire all equipped weapons, picking a not-in-use firing point at each trigger. Not to be confused with 'Salvo mode'.

===="fire down normals"====
*Forces the turret to fire along the turret normals - regardless of the swarm setting.

===="check hull"====
*Forces the firing turret to check against the parent model if valid line of sight exists between the firingpoint and the target.}}

{{Table3611|
===="fixed firingpoints"====
*Forces the firing turret to retain the firingpoints of their weapons: if the turret has multiple banks, the first bank will only fire from the first firepoint, the second bank only from the second firepoint, and so on. Maximum number of weapons is the same as maximum number of weapons in turret (3 primary, 4 secondary)

===="salvo mode"====
*Forces the firing turret to use only the first weapon defined for it but fires it simultaneously from all the firing points. Not to be confused with 'use multiple guns'

===="no subsystem targeting"====
*Prevents the firing turret from targeting targets subsystems - instead forces the turret to fire randomly at the targets hull.

===="fire on target"====
*Prevents the turret from firing unless the turret barrels (firingpoints) and targets are aligned.

===="reset when idle"====
*Forces the turret to reset to its initial position if it has no targets.

===="carry shockwave"====
*Forces the turret to carry damage caused by shockwaves to the hull regardless of other flags.}}

{{Table3613|
===="allow landing"====
*Defines the subsystem as something on which player can attempt to land on

===="target requires fov"====
*Prevents turret from accidentally selecting target out of it field of view (fov) when acquiring targets

===="fov edge checks"====
*The turret will more eagerly acquire targets as long as a sufficient portion of the target is within its fov.

===="no replace"====
*Tells game not to use the replacement submodel (-destroyed) when the subsystem loses all of it's hitpoints.

===="no live debris"====
*Prevents the subsystem from releasing live debris pieces when destroyed

===="ignore if dead"====
*When subsystem has been destroyed prevents homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target. Note, for this to actually work you must also enable the AI Profiles flag of "$fix 'ignore if dead' flag" and/or use FSO 26.0. If you do not do this then using this flag will mean that any weapon locked onto to a destroyed subsystem with this flag will result in the weapon not homing at all.

===="allow vanishing"====
*Allow subsystem to be destroyed from the ship without sound or graphical effects

===="damage as hull"====
*Treats subsystem as if it were hull when applying damage.

===="starts locked"====
*Turret starts locked and won't shoot until you use a turret-free or turret-free-all SEXP on it.

===="no aggregate"====
*Freespace keeps track of a ships overall functionality (such as if a ship is sensorless, disarmed or disabled) via a total hitpoint count of the associated subsystems. For example if a ship has three engines with 100HP each, the 'engines' count will be at 300HP. Shooting at any of the subsystems with the keyword 'engine' in them will decrement this total, and when it is at 0 then the ship becomes disabled.
*This flag tells FS to ignore the associated subsystem and not count it towards those totals. For example, if a ship had three 100HP engines with one set to 'no aggregate' then the 'engines' count will be 200HP. Shooting the 'no aggregate' engine will not decrement the 'engines' count, and so in other words the status of this engine is irrelevant to whether or not the ship is disabled. In the same way when applied to a turret, the turret's status is irrelevant to whether the ship is disarmed or not.

===="wait for animation"====
*When this flag is active, a turret will only fire after any associated subsystem animations (such as a turret hatch opening) have played out.

===="play fire sound for player"====
*If this turret is on a player ship, play its associated sounds.

===="only target if can fire"====
*Do additional checks to make sure that a turret which cannot fire at its target releases that target.
}}

{{Table3615|
===="no disappear"====
*If this subsystem is a physical subsystem, it won't disappear nor switch to the -destroyed model when destroyed.

===="collide submodel"====
*If this subsystem is a physical subsystem, it will only take damage from hits which impact the submodel. By default damage is taken from all hits within the submodel's radius*2. Does not affect area damage such as shockwaves.

===="allow destroyed rotation"====
*Allows a rotating subobject to continue to rotate even when it has been destroyed
}}

{{Table373|
===="turret use ammo"====
*If the subsystem is a turret, it will use ammo.
**Note: If the turret does not have ammo, it will not fire. Remember that the maximum ammo a turret can hold is the Capacity of the Bank divided by the Cargo Size of the weapon.

===="autorepair if disabled"====
*Allows the subsystem to repair itself even if disabled (normally, disabled subsystems do not repair themselves)

===="don't autorepair if disabled"====
*Inverse of "autorepair if disabled": excludes this subsystem from autorepair if the ship class [[Ships.tbl#.22repair_disabled_subsystems.22|"repair disabled subsystems"]] flag is set

===="share fire direction"====
*If this subsystem is a turret, whenever the turret fires it will make all of the firing points shoot their weapon in the same direction instead of at the same point or set of points on a target.
}}

{{Table381|
===="no damage spew"====
*If this subsystem is hit then there will be no damage spew particles emitted.

===="no impact debris"====
*If this subsystem is hit then no impact debris will be generated.
}}

{{Table250|
===="disable all generic impact debris"====
*Newer name for "no impact debris"--turns off the tiny debris shards that are typically spawned when something impacts a subsystem.
}}

{{Table220|
===="hide turret from loadout stats"====
*This subsystem is not counted as a turret in the auto-generated "+Turrets:" line in the statistics summary window of the ship loadout editor.
}}

{{Table222|
===="turret has distant firepoint"====
*Turret barrel is very long and should be taken into account when aiming (rather than calculating the aim from the turret center)
}}

{{Table242|
===="override submodel impact"====
*If a weapon impacted a submodel, but this subsystem is within range, this subsystem takes priority in the hit sequence rather than the submodel. This allows case-by-case exceptions to the [[Game_settings.tbl#.24Damage_Impacted_Subsystem_First:|$Damage Impacted Subsystem First:]] mod flag.
}}

===[[Animation Code]]===
{{Table3610|
*Option for animating the submodels
{{Table220|
'''DEPRECATED''': Unless setting initial orientation of multipart turrets, consider using the [[Animation.tbl]] in combination with [[Ships.tbl#.24Animations:|$Animations:]]
}}
}}

===$On Beam Warmdown:===
{{Table212|
Specifies an [[Action System|action system]] program set to be executed when a beam attached to this subsystem is starting its warmdown sequence.
}}

==Case Specific Entries==

===Turret===
*All turrets require information concerning the weapon mounted to the turret. The entry can be either '''$Default PBanks''' for turret primaries (including beams) or '''$Default SBanks''' for turret secondaries
{{Table3610|
*[[Animation_Code#Setting_Turret_Angle|Animation Code]] can be used with multi-part turrets.
*Multiple defined weapons will all fire but the targeting is handled by the first weapon in the list. '''Multiple beams are not possible'''. All weapons alternate between the firingpoints of the turret so turrets do not need to have more than one weapon defined no matter how many barrels or firingpoints they have.}}

====Example====

<pre>
$Subsystem: turret01, 1.0, 1.0
$Default PBanks: ( "Terran Turret" )
</pre>

===Engine===

====Example====

<pre>
$Subsystem: engine01, 5.0, 0.0
$Engine Wash: Default1000
</pre>

[[Category:Tables]]

Ai profiles.tbl

2026-06-08T03:12:34Z

Wookieejedi: $fix 'ignore if dead' flag

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''
*'''purge player-issued form-on-wing after subsequent order'''}}
{{Table260|
*'''$fix 'ignore if dead' flag:'''}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$max allies rearming threshold:===
{{Table250|
*The maximum allowed number of allies that are allowed to be rearming at the same time. It should be noted that the effect is more noticeable at higher numbers.
*2 by default.
*Syntax: '''''Integer'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

===$don't issue form-on-wing goals at mission start:===
{{Table250|
*Normally, at the beginning of a mission, player wings that do not have an initial goal will be given an initial goal to form on the player. Wings in the loadout screen (aka "starting" wings) will also, if they do not have an initial goal, be issued the same goal if they arrive after mission start. This flag disables that behavior.
*Syntax: '''''Boolean'''''}}

===$default form-on-wing priority:===
{{Table250|
*The default goal priority to be used when issuing a form-on-wing order via sexp or script. If not specified, this is 99. Note that orders issued via the HUD communications system will use the standard communications priorities (100 for ships and 95 for wings) regardless of this setting.
*Syntax: '''''Integer'''''}}

===$do not clear goals when running form-on-wing:===
{{Table250|
*Normally, as soon as a form-on-wing goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the form-on-wing behavior while forgetting both the form goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not clear goals when running stay-still:===
{{Table250|
*Normally, as soon as a stay-still goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the stay-still behavior while forgetting both the stay-still goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not set override when assigning form-on-wing:===
{{Table250|
*Normally, any form-on-wing goal, regardless of how it is assigned, is given a <tt>Goal_override</tt> flag. This causes its goal to be evaluated as the top priority goal, regardless of its actual priority or any other goal's priority. This flag prevents <tt>Goal_override</tt> from being assigned, causing form-on-wing to follow the normal goal prioritization logic.
*Syntax: '''''Boolean'''''}}

===$purge player-issued form-on-wing after subsequent order:===
{{Table250|
*Causes any form-on-wing goal issued by the player (i.e. via the HUD communications system) to be removed from a ship's goal list (even if it is not the current goal) when the ship is given another goal of any priority. This flag can be useful for mods which configure form-on-wing goals to use the same execution and prioritization logic as normal goals. Since form-on-wing goals are typically temporary, regardless of their priority, this flag enforces that temporary nature. By using this flag, mission designers can ensure that mission-directed AI goal logic is followed regardless of form-on-wing status.
*Syntax: '''''Boolean'''''}}

===$cancel future waves of any wing launched from an exited ship:===
{{Table250|
*Infamously, in FSO, a wing whose mothership is destroyed will not, itself, be considered destroyed if it has more waves remaining, because wing cleanup and logging typically only happen when the last ship in the last wave exits the mission. Instead, with no mothership to arrive from, waves will simply no longer arrive. Events that check to see if the wing is destroyed or departed will never fire. This flag fixes that behavior, ensuring that the wing is cleaned up and logged properly, by using the same logic as the enhanced cancel-future-waves SEXP operator.
*Syntax: '''''Boolean'''''}}

===$fix 'ignore if dead' flag:===
{{Table260|
*The subsystem flag "ignore if dead" that many mods use is supposed to "prevent homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target." The code was bugged though and unfortunately what ends up happening is that the weapon dumb fire instead of homes. This bug means if you destroy a subsystem with this flag, then lock onto it with an aspect weapon and fire the weapon, the weapon will just dumb fire. Enabling this flag fixes this, and actually makes "ignore if dead" flag work as intended.
*Syntax: '''''Boolean'''''}}

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

2026-03-30T19:03:55Z

Wookieejedi: add cancel future waves of any wing launched from an exited ship:

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''
*'''purge player-issued form-on-wing after subsequent order'''}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$max allies rearming threshold:===
{{Table250|
*The maximum allowed number of allies that are allowed to be rearming at the same time. It should be noted that the effect is more noticeable at higher numbers.
*2 by default.
*Syntax: '''''Integer'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*The value is multiplied to a vector proportional the ship's velocity divided by its rotation time, which roughly determines the minimum distance needed to pull away from an obstacle directly ahead, and the time at which the AI will stop what's it's doing to pull away.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

===$don't issue form-on-wing goals at mission start:===
{{Table250|
*Normally, at the beginning of a mission, player wings that do not have an initial goal will be given an initial goal to form on the player. Wings in the loadout screen (aka "starting" wings) will also, if they do not have an initial goal, be issued the same goal if they arrive after mission start. This flag disables that behavior.
*Syntax: '''''Boolean'''''}}

===$default form-on-wing priority:===
{{Table250|
*The default goal priority to be used when issuing a form-on-wing order via sexp or script. If not specified, this is 99. Note that orders issued via the HUD communications system will use the standard communications priorities (100 for ships and 95 for wings) regardless of this setting.
*Syntax: '''''Integer'''''}}

===$do not clear goals when running form-on-wing:===
{{Table250|
*Normally, as soon as a form-on-wing goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the form-on-wing behavior while forgetting both the form goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not clear goals when running stay-still:===
{{Table250|
*Normally, as soon as a stay-still goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the stay-still behavior while forgetting both the stay-still goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not set override when assigning form-on-wing:===
{{Table250|
*Normally, any form-on-wing goal, regardless of how it is assigned, is given a <tt>Goal_override</tt> flag. This causes its goal to be evaluated as the top priority goal, regardless of its actual priority or any other goal's priority. This flag prevents <tt>Goal_override</tt> from being assigned, causing form-on-wing to follow the normal goal prioritization logic.
*Syntax: '''''Boolean'''''}}

===$purge player-issued form-on-wing after subsequent order:===
{{Table250|
*Causes any form-on-wing goal issued by the player (i.e. via the HUD communications system) to be removed from a ship's goal list (even if it is not the current goal) when the ship is given another goal of any priority. This flag can be useful for mods which configure form-on-wing goals to use the same execution and prioritization logic as normal goals. Since form-on-wing goals are typically temporary, regardless of their priority, this flag enforces that temporary nature. By using this flag, mission designers can ensure that mission-directed AI goal logic is followed regardless of form-on-wing status.
*Syntax: '''''Boolean'''''}}

===$cancel future waves of any wing launched from an exited ship:===
{{Table250|
*Infamously, in FSO, a wing whose mothership is destroyed will not, itself, be considered destroyed if it has more waves remaining, because wing cleanup and logging typically only happen when the last ship in the last wave exits the mission. Instead, with no mothership to arrive from, waves will simply no longer arrive. Events that check to see if the wing is destroyed or departed will never fire. This flag fixes that behavior, ensuring that the wing is cleaned up and logged properly, by using the same logic as the enhanced cancel-future-waves SEXP operator.
*Syntax: '''''Boolean'''''}}

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

Fate of the Galaxy

2026-03-09T22:11:27Z

Wookieejedi: add vulture droid

{{fotg}}

'''Fate of the Galaxy''' (FotG) is a free total conversion set in the ''[https://en.wikipedia.org/wiki/Star_Wars Star Wars]'' Original Trilogy. Developed using the open-source FreeSpace 2 Open (FSO) game engine, the project will be released as a standalone (the game FreeSpace 2 is not required). An active [https://fate-of-the-galaxy.github.io/ website], [https://www.hard-light.net/forums/index.php?board=143.0 forum] and [https://discord.gg/k7ZMdmt Discord Channel] are also maintained. As a disclaimer, Fate of the Galaxy is a total conversion for FreeSpace Open developed by a team of fan volunteers, it is not associated with Lucasfilm Ltd or Disney and is not an official Star Wars product

==Developers==
*'''chief1983:''' Project Lead
*'''Brand-X:''' Senior Artist and Content Moderator
*'''TopAce:''' Mission Design
*'''swashmebuckle:''' Music Composer, Writer
*'''zookeeper:''' Model Conversion, Artist, Scripting
*'''CountBuggula:''' Webmaster, Communications
*'''niffiwan:''' Coder
*'''wookieejedi:''' Mission Design, Scripting, Beta Management
*'''Limbert:''' Senior Artist
*'''bobbtmann:''' Senior Contributor
*'''Dark Visor:''' Senior Artist

''Full list of contributors is present in Credits screen of the game.''

==Gameplay==
In ''Fate of the Galaxy'' the player takes the role of a starfighter pilot through a series of missions and campaigns. The game is primarily played through the perspective of single-manned craft. There are no plans currently for player-control of capital ships, though certain player craft do allow for AI gunners. Current missions are set in space, including in asteroid fields, nebulas, and above planets. A multiplayer mode is also available to play and works well at low pings (~<100 ms). Standalone instances of the game are maintained, which allows players to easily join a server and play with friends.

The player will choose to play as a pilot for the Rebel Alliance, the Galactic Empire, or as an independent neutral adventurer/privateer. All factions have their own unique ships to control.

===Authenticity===
''Fate of the Galaxy'' strives to recreate combat as close to as seen in the Original Trilogy of ''Star Wars'', during scenes such as the [https://starwars.fandom.com/wiki/Battle_of_Endor/Legends Battle of Endor] and the [https://starwars.fandom.com/wiki/Battle_of_Yavin Battle of Yavin]. To achieve this, the members of the development team have extensively analyzed individual movements and moments within these scenes to determine a baseline for such game concepts as damage, speed, and maneuverability. Each fighter will stay as close as possible to its canonical statistics stated in various sources, but the final authority is the Original Trilogy movies themselves. Thus, many attributes may be contrary to other published materials due to their divergence from the Original Trilogy. In addition, visuals have been tuned to match the aesthetic of the Original Trilogy movies.

Given this focus on movie authenticity, the gameplay differs from that present in the default FreeSpace 2 universe. Ships will be much faster and combat quicker paced, with a larger focus on avoiding damage rather than absorbing it. Several coding features have been completed to create a new, unique style of combat.

==Vehicles==
The game includes multiple ships unique to each faction, with some designs being shared when appropriate. Each faction's fighters and capital ships have unique strengths, which presents different gameplay styles for each side.

===Alliance to Restore the Republic/New Republic===
[[Image:NuX.png|thumb|The X-wing Starfighter, main fighter of the Rebel Alliance]]
The Alliance to Restore the Republic and New Republic maintain a focus on versatile and durable starfighters and small, fast capital ships. Most of the Rebel fighters are equipped with secondary missile weapons such as concussion missiles or proton torpedoes. Rebel players will, in most cases, be unable to outmaneuver their Imperial counterparts and will rely on their superior durability and weapon complement, as well as teamwork to engage the enemy. Rebel capital ships are smaller than their Imperial counterparts, with each having diverse strengths due to their construction by various manufacturers. Rebel Mon Calamari Cruisers are noted for their incredible shield regeneration rates, while Corellian Corvettes are known for their speed.

The following Rebel/New Republic craft are included in the game:

*[https://starwars.fandom.com/wiki/X-wing_starfighter T-65 X-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL_Y-wing_starfighter BTL-A4 Y-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL-A4_LP_%22Longprobe%22 BTL-LP Longprobe Starfighter]
*[https://starwars.fandom.com/wiki/RZ-1_A-wing_interceptor RZ-1 A-wing Interceptor]
*[https://starwars.fandom.com/wiki/A/SF-01_B-wing_starfighter A/SF-01 B-wing Starfighter]
*[https://starwars.fandom.com/wiki/E-wing_escort_starfighter E-wing Escort Starfighter]
*[https://starwars.fandom.com/wiki/UT-60D_U-wing_starfighter/support_craft UT-60D U-wing]
*[https://starwars.fandom.com/wiki/Millennium_Falcon Millennium Falcon]

*[https://starwars.fandom.com/wiki/GR-75_medium_transport GR-75 Medium Transport]
*[https://starwars.fandom.com/wiki/CR90_corvette Corellian CR90 Corvette]
*[https://starwars.fandom.com/wiki/EF76_Nebulon-B_escort_frigate EF76 Nebulon-B Escort Frigate]
*[https://starwars.fandom.com/wiki/MC30C_frigate MC30 Heavy Frigate]
*[https://starwars.fandom.com/wiki/MC40a_light_cruiser MC40 Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Liberty_type_Star_Cruiser ''Liberty''-class Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Home_One_type_Star_Cruiser ''Home One''-class Star Cruiser]

===Galactic Empire===
[[Image:NuRTIE03.jpg|thumb|The TIE/ln Starfighter, main fighter of the Galactic Empire]]
The Galactic Empire's main strategy for fighters revolves around the concept of numerical advantage. Imperial TIEs usually lack shields and durability, but have very potent weaponry and great maneuverability to counter this weakness. Most Imperial fighters also forego any sort of missile secondary weapons and focus entirely on their lasers for offensive armament. Imperial capital ships are much larger than those of the Rebels, and focus on heavy offensive weaponry and great hull durability.

The following Imperial craft are included in the game:

*[https://starwars.fandom.com/wiki/TIE/LN_starfighter T.I.E. Starfighter & TIE/ln Starfighter]
*[https://starwars.fandom.com/wiki/TIE_Reconnaissance_Fighter TIE/rc Recon Fighter]
*[https://starwars.fandom.com/wiki/TIE/IN_interceptor TIE/In Interceptor Mark I and Mark II]
*[https://starwars.fandom.com/wiki/TIE/sa_bomber TIE/sa Bomber]
*[https://starwars.fandom.com/wiki/TIE_Advanced_x1 TIE Advanced x1]
*[https://starwars.fandom.com/wiki/V38_assault_fighter V38 Assault Fighter]

*[https://starwars.fandom.com/wiki/TIE/sh_shuttle TIE/sh Shuttle]
*[https://starwars.fandom.com/wiki/Alpha-class_Xg-1_Star_Wing Xg-1 Star Wing]
*[https://starwars.fandom.com/wiki/Delta-class_DX-9_stormtrooper_transport DX-9 Stormtrooper Transport]
*[https://starwars.fandom.com/wiki/Lambda-class_T-4a_shuttle Lambda-class T-4a Shuttle]
*[https://starwars.fandom.com/wiki/Zeta-class_Heavy_Cargo_Shuttle Zeta-class Heavy Cargo Shuttle]

*[https://starwars.fandom.com/wiki/All_Terrain_Armored_Transport ''All Terrain Armored Transport'']
*[https://starwars.fandom.com/wiki/Gozanti-class_cruiser ''Gozanti''-class Cruiser]

*[https://starwars.fandom.com/wiki/Raider-class_corvette ''Raider''-class Corvette]
*[https://starwars.fandom.com/wiki/Carrack-class_light_cruiser ''Carrack''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Arquitens-class_light_cruiser ''Arquitens''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Strike-class_medium_cruiser ''Strike''-class Medium Cruiser]
*[https://starwars.fandom.com/wiki/Vindicator-class_heavy_cruiser ''Vindicator''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Interdictor_vessel ''Interdictor''-class Cruiser]
*[https://starwars.fandom.com/wiki/Imperial_II-class_Star_Destroyer ''Imperator II''-class Star Destroyer]
*[https://starwars.fandom.com/wiki/Golan_space_defense_platform Golan M-series Dockyard Platforms]
*[https://starwars.fandom.com/wiki/Shield_Gate Golan M-3185 Shield Gate Station]

===Neutral===
There are multiple factions in the Star Wars galaxy which use many craft that are not produced for the Galactic Empire or the Rebel Alliance. These craft vary in characteristics and are used throughout the galaxy in various roles.

The following Neutral craft are included in the game:

*[https://starwars.fandom.com/wiki/Z-95_Headhunter Z-95 Headhunter]
*[https://starwars.fandom.com/wiki/CloakShape_fighter/Legends Cloakshape Starfighter]
*[https://starwars.fandom.com/wiki/N-1_starfighter N-1 Naboo Starfighter]
*[https://starwars.fandom.com/wiki/Alpha-3_Nimbus-class_V-wing_starfighter Alpha-3 Nimbus-class V-wing Starfighter]
*[https://starwars.fandom.com/wiki/Aggressive_ReConnaissance-170_starfighter/Legends ARC-170 Starfighter]
*[https://starwars.fandom.com/wiki/Vulture-class_starfighter Vulture-class_starfighter]
*[https://starwars.fandom.com/wiki/Ugly/Legends Various Uglies]
*[https://starwars.fandom.com/wiki/Firespray-31-class_patrol_and_attack_craft Firespray-31-class Gunship]
*[https://starwars.fandom.com/wiki/Slave_I Slave I]
*[https://starwars.fandom.com/wiki/YT-1300_light_freighter YT-1300 Light Freighter]
*[https://starwars.fandom.com/wiki/BFF-1_bulk_freighter BFF-1 Bulk Freighter]
*[https://starwars.fandom.com/wiki/Tug DV-3 Cargo Freighter]
*[https://starwars.fandom.com/wiki/Action_VI_transport Action VI Transport]
*[https://starwars.fandom.com/wiki/Transport Rayter-class Transport]
*[https://starwars.fandom.com/wiki/CSS-1_Corellian_Star_Shuttle Star Shuttle]
*[https://starwars.fandom.com/wiki/StarSpeeder_1000 Star Speeder]
*[https://starwars.fandom.com/wiki/GAT-12_Skipray_Blastboat GAT-10 Skipray Blastboat]
*[https://starwars.fandom.com/wiki/Consular-class_cruiser_(Charger_c70_retrofit) Corellian Charger C70 Retrofit]
*[https://starwars.fandom.com/wiki/Braha'tok-class_gunship Braha'tok-class gunship]
*[https://starwars.fandom.com/wiki/Marauder-class_corvette Marauder-class corvette]
*[https://starwars.fandom.com/wiki/Dreadnaught-class_heavy_cruiser ''Dreadnaught''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Venator-class_Star_Destroyer ''Venator''-class Cruiser]
*[https://starwars.fandom.com/wiki/XQ_Platform_series XQ1 and XQ2 Stations]
*[https://starwars.fandom.com/wiki/Asteroid_base Asteroid Base Station]
*[https://starwars.fandom.com/wiki/Repair_droid Dockyard Repair Droids]
*[https://starwars.fandom.com/wiki/Satellite/Legends Sensor and Defense Satellites]
*[https://starwars.fandom.com/wiki/Space_mine Space Mines]

==Missions and Campaigns==
''Fate of the Galaxy'' comes with a high level of single-player content. These include multiple campaigns, standalone missions, and the ability to create missions using the FSO mission editor FRED2. Multiplayer servers are also maintained and available to play on with friends.

The first three campaigns narrate three interconnected stories set at the beginning of the Galactic Civil War. Each of these three campaigns consists of about 5 missions, thus designers put high emphasis on quality mission design and high replayability. The player's performance throughout the campaign will affect how later missions play out. For example, the Alliance campaign will pit a ragtag Rebel task force against a dreaded ''Imperial''-class Star Destroyer in the early stages of the Rebellion, and the player's performance throughout the campaign has a major impact on this encounter's difficulty. The best possible outcome is hard to achieve, thus a number of playthroughs will be required.

Players receive different types of training in different campaigns. The Alliance mini-campaign starts with a basic training mission that teaches the basics to new players along with gameplay features that are unique to ''Fate of the Galaxy'''. The Imperial mini-campaign starts with an advanced training.

Standalone missions are also included in the first release. Many of them are serious, story-driven missions, but there will also be arcade-like "challenge" missions in which the player must accomplish a wide variety of objectives, such as surviving two minutes within a ''Strike''-class cruiser's firing range. There will also be a Practice Zone mission, where the player can test flying any of the small craft and actively spawn in any craft in the mission as a hostile or friendly to practice combat.

Three additional campaigns are being worked on and will be available when the game is released to the public, but specific details remain under embargo until public launch. This large component is code-named Project Alderaan.

==Development==
[[Image:Ewingmaps.jpg|thumb|The progression of model work shown on an E-wing Starfighter, from Model (Right) to Normal Maps (Center) and Diffuse Texture (Left). Note that this model will not be used.]]
Fate of the Galaxy picks up after a number of previous attempts to create a ''Star Wars'' mod for FreeSpace. For several years the "Star Wars Conversion Project" was worked on by various teams and developers, but without any releases.

In early 2007, chief1983 took over as project leader, and began to assemble a new team of developers. Choosing the name ''Fate of the Galaxy'', the initial team consisted of chief1983, Brand-X as a modeler and Turambar as a texturer. The initial plan put forward was to use the models and textures that had been completed by previous teams. Soon after the reformation of the mod team, however, it was decided that all new art assets were needed to compete with the high graphical standards of the newer models, and all previously completed ships were discarded.

Work continued on ship models and textures through the next year and a half, as new staff members were added to the development team. In May of 2008, work began on implementing the new ship models into the game and work began on redesigning the feel and pace of the FreeSpace 2 Open engine. Work still continued on the models needed for a campaign and demo release.

In early January of 2009, Brand-X experienced a hard drive failure which destroyed all previous models of his, setting the team's art department back significantly. Since then, work has progressed on recreating these models to even higher quality standards.

On June 4th, 2009, the first in-game screenshot of the X-wing starfighter was made public at the [http://www.moddb.com/games/fate-of-the-galaxy/images/x-wing-in-game-shots2#imagebox ModDB site] and at the official FotG [https://www.hard-light.net/forums/index.php?board=143.0 forums]. The first three campaigns, which are set at the beginning of the Galactic Civil War, were eventually completed, and worked then moved to standalone missions and three additional campaigns code-named Project Alderaan.

In December of 2018 the team began the first phases of private beta testing. In June of 2022, the private beta tests were stated as nearly concluded.

In May of 2019 the [https://www.youtube.com/watch?v=ler20EdjAfs&list=LLW8-wdcPLv0eT913KIi9_mw&index=2&t=0s teaser trailer] was posted.

Throughout 2020-2022 developmental showcases have consisted of forum updates and gameplay streams on Discord.

In June of 2022, multiplayer was confirmed to be working well, and standalone servers were created.

From 2023-2024, the game underwent extensive balance and optimization testing in preparation for the public release.

For the duration of 2025, additional polishing passes were conducted and continue to be refined.

===Newsletter===
Newsletters are posted on a quarterly basis on the [https://www.hard-light.net/forums/index.php?board=143.0 Fate of the Galaxy Forums]. Also, the majority of the unofficial development chatter occurs on the Fate of the Galaxy Discord channel [https://discord.gg/k7ZMdmt].

The most recent [https://www.hard-light.net/forums/index.php?topic=99253.0] was released in May 2024. This update highlights new ship additions, MainHall updates, many other enhancements, and numerous fixes and minor updates.

For reference, the [http://www.hard-light.net/forums/index.php/topic,54217.0.html first newsletter] was posted on June 1st, 2008.

===First Release===
The first open beta of ''Fate of the Galaxy'' was originally planned to be released sometime late-2008 or early 2009. However, with the art setback, the release has been pushed back. Subsequent additions and developments then lead the team to decide to release the game as a more polished 1.0 version. A date has not been decided yet, but the first three campaigns are done and relatively independent compared to the larger subsequent 3 campaigns.

Recent years have shown considerable progress on the project, including a release of a private beta and addition of multiple ships and integrating new features that were recently added to the FSO engine (such as deferred and shadow lighting for cockpits, optimizations, and advanced scripting controls).

In the most recent communications on Discord, co-community manager wookieejedi posted: "''We are getting extremely close to releasing FotG publicly--one of the largest remaining milestones is having FSO release 25.0 stable (which is ideally not far away). We simply can’t wait to share the game with you all once those milestones are completed.''" (May 4th, 2025)

==Gallery==
===Ship Lab shots===
<gallery>
Image:Bwing.jpg
Image:Falcon2.jpg
Image:Xwing.jpg
Image:Ywing2.jpg
Image:Z95.jpg |
</gallery>
===Renders===
<gallery>
Image:FalconWallpaper.png
Image:TBrender.png
Image:TransportFinal.jpg
Image:Wallpaper.1-1280.png
Image:Wallpaper.2-1280.png
</gallery>

==Links==
*[http://swc.hard-light.net/ Official Website]
*[https://discord.gg/k7ZMdmt Fate of the Galaxy Discord Server]
*[https://www.hard-light.net/forums/index.php?board=143.0 Official Forum]
*[https://www.moddb.com/games/fate-of-the-galaxy Fate of the Galaxy on ModDB]

Fate of the Galaxy

2026-02-13T19:44:10Z

Wookieejedi: tune gozanti

{{fotg}}

'''Fate of the Galaxy''' (FotG) is a free total conversion set in the ''[https://en.wikipedia.org/wiki/Star_Wars Star Wars]'' Original Trilogy. Developed using the open-source FreeSpace 2 Open (FSO) game engine, the project will be released as a standalone (the game FreeSpace 2 is not required). An active [https://fate-of-the-galaxy.github.io/ website], [https://www.hard-light.net/forums/index.php?board=143.0 forum] and [https://discord.gg/k7ZMdmt Discord Channel] are also maintained. As a disclaimer, Fate of the Galaxy is a total conversion for FreeSpace Open developed by a team of fan volunteers, it is not associated with Lucasfilm Ltd or Disney and is not an official Star Wars product

==Developers==
*'''chief1983:''' Project Lead
*'''Brand-X:''' Senior Artist and Content Moderator
*'''TopAce:''' Mission Design
*'''swashmebuckle:''' Music Composer, Writer
*'''zookeeper:''' Model Conversion, Artist, Scripting
*'''CountBuggula:''' Webmaster, Communications
*'''niffiwan:''' Coder
*'''wookieejedi:''' Mission Design, Scripting, Beta Management
*'''Limbert:''' Senior Artist
*'''bobbtmann:''' Senior Contributor
*'''Dark Visor:''' Senior Artist

''Full list of contributors is present in Credits screen of the game.''

==Gameplay==
In ''Fate of the Galaxy'' the player takes the role of a starfighter pilot through a series of missions and campaigns. The game is primarily played through the perspective of single-manned craft. There are no plans currently for player-control of capital ships, though certain player craft do allow for AI gunners. Current missions are set in space, including in asteroid fields, nebulas, and above planets. A multiplayer mode is also available to play and works well at low pings (~<100 ms). Standalone instances of the game are maintained, which allows players to easily join a server and play with friends.

The player will choose to play as a pilot for the Rebel Alliance, the Galactic Empire, or as an independent neutral adventurer/privateer. All factions have their own unique ships to control.

===Authenticity===
''Fate of the Galaxy'' strives to recreate combat as close to as seen in the Original Trilogy of ''Star Wars'', during scenes such as the [https://starwars.fandom.com/wiki/Battle_of_Endor/Legends Battle of Endor] and the [https://starwars.fandom.com/wiki/Battle_of_Yavin Battle of Yavin]. To achieve this, the members of the development team have extensively analyzed individual movements and moments within these scenes to determine a baseline for such game concepts as damage, speed, and maneuverability. Each fighter will stay as close as possible to its canonical statistics stated in various sources, but the final authority is the Original Trilogy movies themselves. Thus, many attributes may be contrary to other published materials due to their divergence from the Original Trilogy. In addition, visuals have been tuned to match the aesthetic of the Original Trilogy movies.

Given this focus on movie authenticity, the gameplay differs from that present in the default FreeSpace 2 universe. Ships will be much faster and combat quicker paced, with a larger focus on avoiding damage rather than absorbing it. Several coding features have been completed to create a new, unique style of combat.

==Vehicles==
The game includes multiple ships unique to each faction, with some designs being shared when appropriate. Each faction's fighters and capital ships have unique strengths, which presents different gameplay styles for each side.

===Alliance to Restore the Republic/New Republic===
[[Image:NuX.png|thumb|The X-wing Starfighter, main fighter of the Rebel Alliance]]
The Alliance to Restore the Republic and New Republic maintain a focus on versatile and durable starfighters and small, fast capital ships. Most of the Rebel fighters are equipped with secondary missile weapons such as concussion missiles or proton torpedoes. Rebel players will, in most cases, be unable to outmaneuver their Imperial counterparts and will rely on their superior durability and weapon complement, as well as teamwork to engage the enemy. Rebel capital ships are smaller than their Imperial counterparts, with each having diverse strengths due to their construction by various manufacturers. Rebel Mon Calamari Cruisers are noted for their incredible shield regeneration rates, while Corellian Corvettes are known for their speed.

The following Rebel/New Republic craft are included in the game:

*[https://starwars.fandom.com/wiki/X-wing_starfighter T-65 X-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL_Y-wing_starfighter BTL-A4 Y-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL-A4_LP_%22Longprobe%22 BTL-LP Longprobe Starfighter]
*[https://starwars.fandom.com/wiki/RZ-1_A-wing_interceptor RZ-1 A-wing Interceptor]
*[https://starwars.fandom.com/wiki/A/SF-01_B-wing_starfighter A/SF-01 B-wing Starfighter]
*[https://starwars.fandom.com/wiki/E-wing_escort_starfighter E-wing Escort Starfighter]
*[https://starwars.fandom.com/wiki/UT-60D_U-wing_starfighter/support_craft UT-60D U-wing]
*[https://starwars.fandom.com/wiki/Millennium_Falcon Millennium Falcon]

*[https://starwars.fandom.com/wiki/GR-75_medium_transport GR-75 Medium Transport]
*[https://starwars.fandom.com/wiki/CR90_corvette Corellian CR90 Corvette]
*[https://starwars.fandom.com/wiki/EF76_Nebulon-B_escort_frigate EF76 Nebulon-B Escort Frigate]
*[https://starwars.fandom.com/wiki/MC30C_frigate MC30 Heavy Frigate]
*[https://starwars.fandom.com/wiki/MC40a_light_cruiser MC40 Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Liberty_type_Star_Cruiser ''Liberty''-class Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Home_One_type_Star_Cruiser ''Home One''-class Star Cruiser]

===Galactic Empire===
[[Image:NuRTIE03.jpg|thumb|The TIE/ln Starfighter, main fighter of the Galactic Empire]]
The Galactic Empire's main strategy for fighters revolves around the concept of numerical advantage. Imperial TIEs usually lack shields and durability, but have very potent weaponry and great maneuverability to counter this weakness. Most Imperial fighters also forego any sort of missile secondary weapons and focus entirely on their lasers for offensive armament. Imperial capital ships are much larger than those of the Rebels, and focus on heavy offensive weaponry and great hull durability.

The following Imperial craft are included in the game:

*[https://starwars.fandom.com/wiki/TIE/LN_starfighter T.I.E. Starfighter & TIE/ln Starfighter]
*[https://starwars.fandom.com/wiki/TIE_Reconnaissance_Fighter TIE/rc Recon Fighter]
*[https://starwars.fandom.com/wiki/TIE/IN_interceptor TIE/In Interceptor Mark I and Mark II]
*[https://starwars.fandom.com/wiki/TIE/sa_bomber TIE/sa Bomber]
*[https://starwars.fandom.com/wiki/TIE_Advanced_x1 TIE Advanced x1]
*[https://starwars.fandom.com/wiki/V38_assault_fighter V38 Assault Fighter]

*[https://starwars.fandom.com/wiki/TIE/sh_shuttle TIE/sh Shuttle]
*[https://starwars.fandom.com/wiki/Alpha-class_Xg-1_Star_Wing Xg-1 Star Wing]
*[https://starwars.fandom.com/wiki/Delta-class_DX-9_stormtrooper_transport DX-9 Stormtrooper Transport]
*[https://starwars.fandom.com/wiki/Lambda-class_T-4a_shuttle Lambda-class T-4a Shuttle]
*[https://starwars.fandom.com/wiki/Zeta-class_Heavy_Cargo_Shuttle Zeta-class Heavy Cargo Shuttle]

*[https://starwars.fandom.com/wiki/All_Terrain_Armored_Transport ''All Terrain Armored Transport'']
*[https://starwars.fandom.com/wiki/Gozanti-class_cruiser ''Gozanti''-class Cruiser]

*[https://starwars.fandom.com/wiki/Raider-class_corvette ''Raider''-class Corvette]
*[https://starwars.fandom.com/wiki/Carrack-class_light_cruiser ''Carrack''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Arquitens-class_light_cruiser ''Arquitens''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Strike-class_medium_cruiser ''Strike''-class Medium Cruiser]
*[https://starwars.fandom.com/wiki/Vindicator-class_heavy_cruiser ''Vindicator''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Interdictor_vessel ''Interdictor''-class Cruiser]
*[https://starwars.fandom.com/wiki/Imperial_II-class_Star_Destroyer ''Imperator II''-class Star Destroyer]
*[https://starwars.fandom.com/wiki/Golan_space_defense_platform Golan M-series Dockyard Platforms]
*[https://starwars.fandom.com/wiki/Shield_Gate Golan M-3185 Shield Gate Station]

===Neutral===
There are multiple factions in the Star Wars galaxy which use many craft that are not produced for the Galactic Empire or the Rebel Alliance. These craft vary in characteristics and are used throughout the galaxy in various roles.

The following Neutral craft are included in the game:

*[https://starwars.fandom.com/wiki/Z-95_Headhunter Z-95 Headhunter]
*[https://starwars.fandom.com/wiki/CloakShape_fighter/Legends Cloakshape Starfighter]
*[https://starwars.fandom.com/wiki/N-1_starfighter N-1 Naboo Starfighter]
*[https://starwars.fandom.com/wiki/Alpha-3_Nimbus-class_V-wing_starfighter Alpha-3 Nimbus-class V-wing Starfighter]
*[https://starwars.fandom.com/wiki/Aggressive_ReConnaissance-170_starfighter/Legends ARC-170 Starfighter]
*[https://starwars.fandom.com/wiki/Ugly/Legends Various Uglies]
*[https://starwars.fandom.com/wiki/Firespray-31-class_patrol_and_attack_craft Firespray-31-class Gunship]
*[https://starwars.fandom.com/wiki/Slave_I Slave I]
*[https://starwars.fandom.com/wiki/YT-1300_light_freighter YT-1300 Light Freighter]
*[https://starwars.fandom.com/wiki/BFF-1_bulk_freighter BFF-1 Bulk Freighter]
*[https://starwars.fandom.com/wiki/Tug DV-3 Cargo Freighter]
*[https://starwars.fandom.com/wiki/Action_VI_transport Action VI Transport]
*[https://starwars.fandom.com/wiki/Transport Rayter-class Transport]
*[https://starwars.fandom.com/wiki/CSS-1_Corellian_Star_Shuttle Star Shuttle]
*[https://starwars.fandom.com/wiki/StarSpeeder_1000 Star Speeder]
*[https://starwars.fandom.com/wiki/GAT-12_Skipray_Blastboat GAT-10 Skipray Blastboat]
*[https://starwars.fandom.com/wiki/Consular-class_cruiser_(Charger_c70_retrofit) Corellian Charger C70 Retrofit]
*[https://starwars.fandom.com/wiki/Braha'tok-class_gunship Braha'tok-class gunship]
*[https://starwars.fandom.com/wiki/Marauder-class_corvette Marauder-class corvette]
*[https://starwars.fandom.com/wiki/Dreadnaught-class_heavy_cruiser ''Dreadnaught''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Venator-class_Star_Destroyer ''Venator''-class Cruiser]
*[https://starwars.fandom.com/wiki/XQ_Platform_series XQ1 and XQ2 Stations]
*[https://starwars.fandom.com/wiki/Asteroid_base Asteroid Base Station]
*[https://starwars.fandom.com/wiki/Repair_droid Dockyard Repair Droids]
*[https://starwars.fandom.com/wiki/Satellite/Legends Sensor and Defense Satellites]
*[https://starwars.fandom.com/wiki/Space_mine Space Mines]

==Missions and Campaigns==
''Fate of the Galaxy'' comes with a high level of single-player content. These include multiple campaigns, standalone missions, and the ability to create missions using the FSO mission editor FRED2. Multiplayer servers are also maintained and available to play on with friends.

The first three campaigns narrate three interconnected stories set at the beginning of the Galactic Civil War. Each of these three campaigns consists of about 5 missions, thus designers put high emphasis on quality mission design and high replayability. The player's performance throughout the campaign will affect how later missions play out. For example, the Alliance campaign will pit a ragtag Rebel task force against a dreaded ''Imperial''-class Star Destroyer in the early stages of the Rebellion, and the player's performance throughout the campaign has a major impact on this encounter's difficulty. The best possible outcome is hard to achieve, thus a number of playthroughs will be required.

Players receive different types of training in different campaigns. The Alliance mini-campaign starts with a basic training mission that teaches the basics to new players along with gameplay features that are unique to ''Fate of the Galaxy'''. The Imperial mini-campaign starts with an advanced training.

Standalone missions are also included in the first release. Many of them are serious, story-driven missions, but there will also be arcade-like "challenge" missions in which the player must accomplish a wide variety of objectives, such as surviving two minutes within a ''Strike''-class cruiser's firing range. There will also be a Practice Zone mission, where the player can test flying any of the small craft and actively spawn in any craft in the mission as a hostile or friendly to practice combat.

Three additional campaigns are being worked on and will be available when the game is released to the public, but specific details remain under embargo until public launch. This large component is code-named Project Alderaan.

==Development==
[[Image:Ewingmaps.jpg|thumb|The progression of model work shown on an E-wing Starfighter, from Model (Right) to Normal Maps (Center) and Diffuse Texture (Left). Note that this model will not be used.]]
Fate of the Galaxy picks up after a number of previous attempts to create a ''Star Wars'' mod for FreeSpace. For several years the "Star Wars Conversion Project" was worked on by various teams and developers, but without any releases.

In early 2007, chief1983 took over as project leader, and began to assemble a new team of developers. Choosing the name ''Fate of the Galaxy'', the initial team consisted of chief1983, Brand-X as a modeler and Turambar as a texturer. The initial plan put forward was to use the models and textures that had been completed by previous teams. Soon after the reformation of the mod team, however, it was decided that all new art assets were needed to compete with the high graphical standards of the newer models, and all previously completed ships were discarded.

Work continued on ship models and textures through the next year and a half, as new staff members were added to the development team. In May of 2008, work began on implementing the new ship models into the game and work began on redesigning the feel and pace of the FreeSpace 2 Open engine. Work still continued on the models needed for a campaign and demo release.

In early January of 2009, Brand-X experienced a hard drive failure which destroyed all previous models of his, setting the team's art department back significantly. Since then, work has progressed on recreating these models to even higher quality standards.

On June 4th, 2009, the first in-game screenshot of the X-wing starfighter was made public at the [http://www.moddb.com/games/fate-of-the-galaxy/images/x-wing-in-game-shots2#imagebox ModDB site] and at the official FotG [https://www.hard-light.net/forums/index.php?board=143.0 forums]. The first three campaigns, which are set at the beginning of the Galactic Civil War, were eventually completed, and worked then moved to standalone missions and three additional campaigns code-named Project Alderaan.

In December of 2018 the team began the first phases of private beta testing. In June of 2022, the private beta tests were stated as nearly concluded.

In May of 2019 the [https://www.youtube.com/watch?v=ler20EdjAfs&list=LLW8-wdcPLv0eT913KIi9_mw&index=2&t=0s teaser trailer] was posted.

Throughout 2020-2022 developmental showcases have consisted of forum updates and gameplay streams on Discord.

In June of 2022, multiplayer was confirmed to be working well, and standalone servers were created.

From 2023-2024, the game underwent extensive balance and optimization testing in preparation for the public release.

For the duration of 2025, additional polishing passes were conducted and continue to be refined.

===Newsletter===
Newsletters are posted on a quarterly basis on the [https://www.hard-light.net/forums/index.php?board=143.0 Fate of the Galaxy Forums]. Also, the majority of the unofficial development chatter occurs on the Fate of the Galaxy Discord channel [https://discord.gg/k7ZMdmt].

The most recent [https://www.hard-light.net/forums/index.php?topic=99253.0] was released in May 2024. This update highlights new ship additions, MainHall updates, many other enhancements, and numerous fixes and minor updates.

For reference, the [http://www.hard-light.net/forums/index.php/topic,54217.0.html first newsletter] was posted on June 1st, 2008.

===First Release===
The first open beta of ''Fate of the Galaxy'' was originally planned to be released sometime late-2008 or early 2009. However, with the art setback, the release has been pushed back. Subsequent additions and developments then lead the team to decide to release the game as a more polished 1.0 version. A date has not been decided yet, but the first three campaigns are done and relatively independent compared to the larger subsequent 3 campaigns.

Recent years have shown considerable progress on the project, including a release of a private beta and addition of multiple ships and integrating new features that were recently added to the FSO engine (such as deferred and shadow lighting for cockpits, optimizations, and advanced scripting controls).

In the most recent communications on Discord, co-community manager wookieejedi posted: "''We are getting extremely close to releasing FotG publicly--one of the largest remaining milestones is having FSO release 25.0 stable (which is ideally not far away). We simply can’t wait to share the game with you all once those milestones are completed.''" (May 4th, 2025)

==Gallery==
===Ship Lab shots===
<gallery>
Image:Bwing.jpg
Image:Falcon2.jpg
Image:Xwing.jpg
Image:Ywing2.jpg
Image:Z95.jpg |
</gallery>
===Renders===
<gallery>
Image:FalconWallpaper.png
Image:TBrender.png
Image:TransportFinal.jpg
Image:Wallpaper.1-1280.png
Image:Wallpaper.2-1280.png
</gallery>

==Links==
*[http://swc.hard-light.net/ Official Website]
*[https://discord.gg/k7ZMdmt Fate of the Galaxy Discord Server]
*[https://www.hard-light.net/forums/index.php?board=143.0 Official Forum]
*[https://www.moddb.com/games/fate-of-the-galaxy Fate of the Galaxy on ModDB]

Fate of the Galaxy

2026-02-13T19:43:48Z

Wookieejedi: add new empire craft

{{fotg}}

'''Fate of the Galaxy''' (FotG) is a free total conversion set in the ''[https://en.wikipedia.org/wiki/Star_Wars Star Wars]'' Original Trilogy. Developed using the open-source FreeSpace 2 Open (FSO) game engine, the project will be released as a standalone (the game FreeSpace 2 is not required). An active [https://fate-of-the-galaxy.github.io/ website], [https://www.hard-light.net/forums/index.php?board=143.0 forum] and [https://discord.gg/k7ZMdmt Discord Channel] are also maintained. As a disclaimer, Fate of the Galaxy is a total conversion for FreeSpace Open developed by a team of fan volunteers, it is not associated with Lucasfilm Ltd or Disney and is not an official Star Wars product

==Developers==
*'''chief1983:''' Project Lead
*'''Brand-X:''' Senior Artist and Content Moderator
*'''TopAce:''' Mission Design
*'''swashmebuckle:''' Music Composer, Writer
*'''zookeeper:''' Model Conversion, Artist, Scripting
*'''CountBuggula:''' Webmaster, Communications
*'''niffiwan:''' Coder
*'''wookieejedi:''' Mission Design, Scripting, Beta Management
*'''Limbert:''' Senior Artist
*'''bobbtmann:''' Senior Contributor
*'''Dark Visor:''' Senior Artist

''Full list of contributors is present in Credits screen of the game.''

==Gameplay==
In ''Fate of the Galaxy'' the player takes the role of a starfighter pilot through a series of missions and campaigns. The game is primarily played through the perspective of single-manned craft. There are no plans currently for player-control of capital ships, though certain player craft do allow for AI gunners. Current missions are set in space, including in asteroid fields, nebulas, and above planets. A multiplayer mode is also available to play and works well at low pings (~<100 ms). Standalone instances of the game are maintained, which allows players to easily join a server and play with friends.

The player will choose to play as a pilot for the Rebel Alliance, the Galactic Empire, or as an independent neutral adventurer/privateer. All factions have their own unique ships to control.

===Authenticity===
''Fate of the Galaxy'' strives to recreate combat as close to as seen in the Original Trilogy of ''Star Wars'', during scenes such as the [https://starwars.fandom.com/wiki/Battle_of_Endor/Legends Battle of Endor] and the [https://starwars.fandom.com/wiki/Battle_of_Yavin Battle of Yavin]. To achieve this, the members of the development team have extensively analyzed individual movements and moments within these scenes to determine a baseline for such game concepts as damage, speed, and maneuverability. Each fighter will stay as close as possible to its canonical statistics stated in various sources, but the final authority is the Original Trilogy movies themselves. Thus, many attributes may be contrary to other published materials due to their divergence from the Original Trilogy. In addition, visuals have been tuned to match the aesthetic of the Original Trilogy movies.

Given this focus on movie authenticity, the gameplay differs from that present in the default FreeSpace 2 universe. Ships will be much faster and combat quicker paced, with a larger focus on avoiding damage rather than absorbing it. Several coding features have been completed to create a new, unique style of combat.

==Vehicles==
The game includes multiple ships unique to each faction, with some designs being shared when appropriate. Each faction's fighters and capital ships have unique strengths, which presents different gameplay styles for each side.

===Alliance to Restore the Republic/New Republic===
[[Image:NuX.png|thumb|The X-wing Starfighter, main fighter of the Rebel Alliance]]
The Alliance to Restore the Republic and New Republic maintain a focus on versatile and durable starfighters and small, fast capital ships. Most of the Rebel fighters are equipped with secondary missile weapons such as concussion missiles or proton torpedoes. Rebel players will, in most cases, be unable to outmaneuver their Imperial counterparts and will rely on their superior durability and weapon complement, as well as teamwork to engage the enemy. Rebel capital ships are smaller than their Imperial counterparts, with each having diverse strengths due to their construction by various manufacturers. Rebel Mon Calamari Cruisers are noted for their incredible shield regeneration rates, while Corellian Corvettes are known for their speed.

The following Rebel/New Republic craft are included in the game:

*[https://starwars.fandom.com/wiki/X-wing_starfighter T-65 X-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL_Y-wing_starfighter BTL-A4 Y-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL-A4_LP_%22Longprobe%22 BTL-LP Longprobe Starfighter]
*[https://starwars.fandom.com/wiki/RZ-1_A-wing_interceptor RZ-1 A-wing Interceptor]
*[https://starwars.fandom.com/wiki/A/SF-01_B-wing_starfighter A/SF-01 B-wing Starfighter]
*[https://starwars.fandom.com/wiki/E-wing_escort_starfighter E-wing Escort Starfighter]
*[https://starwars.fandom.com/wiki/UT-60D_U-wing_starfighter/support_craft UT-60D U-wing]
*[https://starwars.fandom.com/wiki/Millennium_Falcon Millennium Falcon]

*[https://starwars.fandom.com/wiki/GR-75_medium_transport GR-75 Medium Transport]
*[https://starwars.fandom.com/wiki/CR90_corvette Corellian CR90 Corvette]
*[https://starwars.fandom.com/wiki/EF76_Nebulon-B_escort_frigate EF76 Nebulon-B Escort Frigate]
*[https://starwars.fandom.com/wiki/MC30C_frigate MC30 Heavy Frigate]
*[https://starwars.fandom.com/wiki/MC40a_light_cruiser MC40 Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Liberty_type_Star_Cruiser ''Liberty''-class Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Home_One_type_Star_Cruiser ''Home One''-class Star Cruiser]

===Galactic Empire===
[[Image:NuRTIE03.jpg|thumb|The TIE/ln Starfighter, main fighter of the Galactic Empire]]
The Galactic Empire's main strategy for fighters revolves around the concept of numerical advantage. Imperial TIEs usually lack shields and durability, but have very potent weaponry and great maneuverability to counter this weakness. Most Imperial fighters also forego any sort of missile secondary weapons and focus entirely on their lasers for offensive armament. Imperial capital ships are much larger than those of the Rebels, and focus on heavy offensive weaponry and great hull durability.

The following Imperial craft are included in the game:

*[https://starwars.fandom.com/wiki/TIE/LN_starfighter T.I.E. Starfighter & TIE/ln Starfighter]
*[https://starwars.fandom.com/wiki/TIE_Reconnaissance_Fighter TIE/rc Recon Fighter]
*[https://starwars.fandom.com/wiki/TIE/IN_interceptor TIE/In Interceptor Mark I and Mark II]
*[https://starwars.fandom.com/wiki/TIE/sa_bomber TIE/sa Bomber]
*[https://starwars.fandom.com/wiki/TIE_Advanced_x1 TIE Advanced x1]
*[https://starwars.fandom.com/wiki/V38_assault_fighter V38 Assault Fighter]

*[https://starwars.fandom.com/wiki/TIE/sh_shuttle TIE/sh Shuttle]
*[https://starwars.fandom.com/wiki/Alpha-class_Xg-1_Star_Wing Xg-1 Star Wing]
*[https://starwars.fandom.com/wiki/Delta-class_DX-9_stormtrooper_transport DX-9 Stormtrooper Transport]
*[https://starwars.fandom.com/wiki/Lambda-class_T-4a_shuttle Lambda-class T-4a Shuttle]
*[https://starwars.fandom.com/wiki/Zeta-class_Heavy_Cargo_Shuttle Zeta-class Heavy Cargo Shuttle]

*[https://starwars.fandom.com/wiki/All_Terrain_Armored_Transport ''All Terrain Armored Transport'']
*[https://starwars.fandom.com/wiki/Gozanti-class_cruiser ''Gozanti''-class Corvette]

*[https://starwars.fandom.com/wiki/Raider-class_corvette ''Raider''-class Corvette]
*[https://starwars.fandom.com/wiki/Carrack-class_light_cruiser ''Carrack''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Arquitens-class_light_cruiser ''Arquitens''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Strike-class_medium_cruiser ''Strike''-class Medium Cruiser]
*[https://starwars.fandom.com/wiki/Vindicator-class_heavy_cruiser ''Vindicator''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Interdictor_vessel ''Interdictor''-class Cruiser]
*[https://starwars.fandom.com/wiki/Imperial_II-class_Star_Destroyer ''Imperator II''-class Star Destroyer]
*[https://starwars.fandom.com/wiki/Golan_space_defense_platform Golan M-series Dockyard Platforms]
*[https://starwars.fandom.com/wiki/Shield_Gate Golan M-3185 Shield Gate Station]

===Neutral===
There are multiple factions in the Star Wars galaxy which use many craft that are not produced for the Galactic Empire or the Rebel Alliance. These craft vary in characteristics and are used throughout the galaxy in various roles.

The following Neutral craft are included in the game:

*[https://starwars.fandom.com/wiki/Z-95_Headhunter Z-95 Headhunter]
*[https://starwars.fandom.com/wiki/CloakShape_fighter/Legends Cloakshape Starfighter]
*[https://starwars.fandom.com/wiki/N-1_starfighter N-1 Naboo Starfighter]
*[https://starwars.fandom.com/wiki/Alpha-3_Nimbus-class_V-wing_starfighter Alpha-3 Nimbus-class V-wing Starfighter]
*[https://starwars.fandom.com/wiki/Aggressive_ReConnaissance-170_starfighter/Legends ARC-170 Starfighter]
*[https://starwars.fandom.com/wiki/Ugly/Legends Various Uglies]
*[https://starwars.fandom.com/wiki/Firespray-31-class_patrol_and_attack_craft Firespray-31-class Gunship]
*[https://starwars.fandom.com/wiki/Slave_I Slave I]
*[https://starwars.fandom.com/wiki/YT-1300_light_freighter YT-1300 Light Freighter]
*[https://starwars.fandom.com/wiki/BFF-1_bulk_freighter BFF-1 Bulk Freighter]
*[https://starwars.fandom.com/wiki/Tug DV-3 Cargo Freighter]
*[https://starwars.fandom.com/wiki/Action_VI_transport Action VI Transport]
*[https://starwars.fandom.com/wiki/Transport Rayter-class Transport]
*[https://starwars.fandom.com/wiki/CSS-1_Corellian_Star_Shuttle Star Shuttle]
*[https://starwars.fandom.com/wiki/StarSpeeder_1000 Star Speeder]
*[https://starwars.fandom.com/wiki/GAT-12_Skipray_Blastboat GAT-10 Skipray Blastboat]
*[https://starwars.fandom.com/wiki/Consular-class_cruiser_(Charger_c70_retrofit) Corellian Charger C70 Retrofit]
*[https://starwars.fandom.com/wiki/Braha'tok-class_gunship Braha'tok-class gunship]
*[https://starwars.fandom.com/wiki/Marauder-class_corvette Marauder-class corvette]
*[https://starwars.fandom.com/wiki/Dreadnaught-class_heavy_cruiser ''Dreadnaught''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Venator-class_Star_Destroyer ''Venator''-class Cruiser]
*[https://starwars.fandom.com/wiki/XQ_Platform_series XQ1 and XQ2 Stations]
*[https://starwars.fandom.com/wiki/Asteroid_base Asteroid Base Station]
*[https://starwars.fandom.com/wiki/Repair_droid Dockyard Repair Droids]
*[https://starwars.fandom.com/wiki/Satellite/Legends Sensor and Defense Satellites]
*[https://starwars.fandom.com/wiki/Space_mine Space Mines]

==Missions and Campaigns==
''Fate of the Galaxy'' comes with a high level of single-player content. These include multiple campaigns, standalone missions, and the ability to create missions using the FSO mission editor FRED2. Multiplayer servers are also maintained and available to play on with friends.

The first three campaigns narrate three interconnected stories set at the beginning of the Galactic Civil War. Each of these three campaigns consists of about 5 missions, thus designers put high emphasis on quality mission design and high replayability. The player's performance throughout the campaign will affect how later missions play out. For example, the Alliance campaign will pit a ragtag Rebel task force against a dreaded ''Imperial''-class Star Destroyer in the early stages of the Rebellion, and the player's performance throughout the campaign has a major impact on this encounter's difficulty. The best possible outcome is hard to achieve, thus a number of playthroughs will be required.

Players receive different types of training in different campaigns. The Alliance mini-campaign starts with a basic training mission that teaches the basics to new players along with gameplay features that are unique to ''Fate of the Galaxy'''. The Imperial mini-campaign starts with an advanced training.

Standalone missions are also included in the first release. Many of them are serious, story-driven missions, but there will also be arcade-like "challenge" missions in which the player must accomplish a wide variety of objectives, such as surviving two minutes within a ''Strike''-class cruiser's firing range. There will also be a Practice Zone mission, where the player can test flying any of the small craft and actively spawn in any craft in the mission as a hostile or friendly to practice combat.

Three additional campaigns are being worked on and will be available when the game is released to the public, but specific details remain under embargo until public launch. This large component is code-named Project Alderaan.

==Development==
[[Image:Ewingmaps.jpg|thumb|The progression of model work shown on an E-wing Starfighter, from Model (Right) to Normal Maps (Center) and Diffuse Texture (Left). Note that this model will not be used.]]
Fate of the Galaxy picks up after a number of previous attempts to create a ''Star Wars'' mod for FreeSpace. For several years the "Star Wars Conversion Project" was worked on by various teams and developers, but without any releases.

In early 2007, chief1983 took over as project leader, and began to assemble a new team of developers. Choosing the name ''Fate of the Galaxy'', the initial team consisted of chief1983, Brand-X as a modeler and Turambar as a texturer. The initial plan put forward was to use the models and textures that had been completed by previous teams. Soon after the reformation of the mod team, however, it was decided that all new art assets were needed to compete with the high graphical standards of the newer models, and all previously completed ships were discarded.

Work continued on ship models and textures through the next year and a half, as new staff members were added to the development team. In May of 2008, work began on implementing the new ship models into the game and work began on redesigning the feel and pace of the FreeSpace 2 Open engine. Work still continued on the models needed for a campaign and demo release.

In early January of 2009, Brand-X experienced a hard drive failure which destroyed all previous models of his, setting the team's art department back significantly. Since then, work has progressed on recreating these models to even higher quality standards.

On June 4th, 2009, the first in-game screenshot of the X-wing starfighter was made public at the [http://www.moddb.com/games/fate-of-the-galaxy/images/x-wing-in-game-shots2#imagebox ModDB site] and at the official FotG [https://www.hard-light.net/forums/index.php?board=143.0 forums]. The first three campaigns, which are set at the beginning of the Galactic Civil War, were eventually completed, and worked then moved to standalone missions and three additional campaigns code-named Project Alderaan.

In December of 2018 the team began the first phases of private beta testing. In June of 2022, the private beta tests were stated as nearly concluded.

In May of 2019 the [https://www.youtube.com/watch?v=ler20EdjAfs&list=LLW8-wdcPLv0eT913KIi9_mw&index=2&t=0s teaser trailer] was posted.

Throughout 2020-2022 developmental showcases have consisted of forum updates and gameplay streams on Discord.

In June of 2022, multiplayer was confirmed to be working well, and standalone servers were created.

From 2023-2024, the game underwent extensive balance and optimization testing in preparation for the public release.

For the duration of 2025, additional polishing passes were conducted and continue to be refined.

===Newsletter===
Newsletters are posted on a quarterly basis on the [https://www.hard-light.net/forums/index.php?board=143.0 Fate of the Galaxy Forums]. Also, the majority of the unofficial development chatter occurs on the Fate of the Galaxy Discord channel [https://discord.gg/k7ZMdmt].

The most recent [https://www.hard-light.net/forums/index.php?topic=99253.0] was released in May 2024. This update highlights new ship additions, MainHall updates, many other enhancements, and numerous fixes and minor updates.

For reference, the [http://www.hard-light.net/forums/index.php/topic,54217.0.html first newsletter] was posted on June 1st, 2008.

===First Release===
The first open beta of ''Fate of the Galaxy'' was originally planned to be released sometime late-2008 or early 2009. However, with the art setback, the release has been pushed back. Subsequent additions and developments then lead the team to decide to release the game as a more polished 1.0 version. A date has not been decided yet, but the first three campaigns are done and relatively independent compared to the larger subsequent 3 campaigns.

Recent years have shown considerable progress on the project, including a release of a private beta and addition of multiple ships and integrating new features that were recently added to the FSO engine (such as deferred and shadow lighting for cockpits, optimizations, and advanced scripting controls).

In the most recent communications on Discord, co-community manager wookieejedi posted: "''We are getting extremely close to releasing FotG publicly--one of the largest remaining milestones is having FSO release 25.0 stable (which is ideally not far away). We simply can’t wait to share the game with you all once those milestones are completed.''" (May 4th, 2025)

==Gallery==
===Ship Lab shots===
<gallery>
Image:Bwing.jpg
Image:Falcon2.jpg
Image:Xwing.jpg
Image:Ywing2.jpg
Image:Z95.jpg |
</gallery>
===Renders===
<gallery>
Image:FalconWallpaper.png
Image:TBrender.png
Image:TransportFinal.jpg
Image:Wallpaper.1-1280.png
Image:Wallpaper.2-1280.png
</gallery>

==Links==
*[http://swc.hard-light.net/ Official Website]
*[https://discord.gg/k7ZMdmt Fate of the Galaxy Discord Server]
*[https://www.hard-light.net/forums/index.php?board=143.0 Official Forum]
*[https://www.moddb.com/games/fate-of-the-galaxy Fate of the Galaxy on ModDB]

Fate of the Galaxy

2026-01-06T16:27:03Z

Wookieejedi: add raider

{{fotg}}

'''Fate of the Galaxy''' (FotG) is a free total conversion set in the ''[https://en.wikipedia.org/wiki/Star_Wars Star Wars]'' Original Trilogy. Developed using the open-source FreeSpace 2 Open (FSO) game engine, the project will be released as a standalone (the game FreeSpace 2 is not required). An active [https://fate-of-the-galaxy.github.io/ website], [https://www.hard-light.net/forums/index.php?board=143.0 forum] and [https://discord.gg/k7ZMdmt Discord Channel] are also maintained. As a disclaimer, Fate of the Galaxy is a total conversion for FreeSpace Open developed by a team of fan volunteers, it is not associated with Lucasfilm Ltd or Disney and is not an official Star Wars product

==Developers==
*'''chief1983:''' Project Lead
*'''Brand-X:''' Senior Artist and Content Moderator
*'''TopAce:''' Mission Design
*'''swashmebuckle:''' Music Composer, Writer
*'''zookeeper:''' Model Conversion, Artist, Scripting
*'''CountBuggula:''' Webmaster, Communications
*'''niffiwan:''' Coder
*'''wookieejedi:''' Mission Design, Scripting, Beta Management
*'''Limbert:''' Senior Artist
*'''bobbtmann:''' Senior Contributor
*'''Dark Visor:''' Senior Artist

''Full list of contributors is present in Credits screen of the game.''

==Gameplay==
In ''Fate of the Galaxy'' the player takes the role of a starfighter pilot through a series of missions and campaigns. The game is primarily played through the perspective of single-manned craft. There are no plans currently for player-control of capital ships, though certain player craft do allow for AI gunners. Current missions are set in space, including in asteroid fields, nebulas, and above planets. A multiplayer mode is also available to play and works well at low pings (~<100 ms). Standalone instances of the game are maintained, which allows players to easily join a server and play with friends.

The player will choose to play as a pilot for the Rebel Alliance, the Galactic Empire, or as an independent neutral adventurer/privateer. All factions have their own unique ships to control.

===Authenticity===
''Fate of the Galaxy'' strives to recreate combat as close to as seen in the Original Trilogy of ''Star Wars'', during scenes such as the [https://starwars.fandom.com/wiki/Battle_of_Endor/Legends Battle of Endor] and the [https://starwars.fandom.com/wiki/Battle_of_Yavin Battle of Yavin]. To achieve this, the members of the development team have extensively analyzed individual movements and moments within these scenes to determine a baseline for such game concepts as damage, speed, and maneuverability. Each fighter will stay as close as possible to its canonical statistics stated in various sources, but the final authority is the Original Trilogy movies themselves. Thus, many attributes may be contrary to other published materials due to their divergence from the Original Trilogy. In addition, visuals have been tuned to match the aesthetic of the Original Trilogy movies.

Given this focus on movie authenticity, the gameplay differs from that present in the default FreeSpace 2 universe. Ships will be much faster and combat quicker paced, with a larger focus on avoiding damage rather than absorbing it. Several coding features have been completed to create a new, unique style of combat.

==Vehicles==
The game includes multiple ships unique to each faction, with some designs being shared when appropriate. Each faction's fighters and capital ships have unique strengths, which presents different gameplay styles for each side.

===Alliance to Restore the Republic/New Republic===
[[Image:NuX.png|thumb|The X-wing Starfighter, main fighter of the Rebel Alliance]]
The Alliance to Restore the Republic and New Republic maintain a focus on versatile and durable starfighters and small, fast capital ships. Most of the Rebel fighters are equipped with secondary missile weapons such as concussion missiles or proton torpedoes. Rebel players will, in most cases, be unable to outmaneuver their Imperial counterparts and will rely on their superior durability and weapon complement, as well as teamwork to engage the enemy. Rebel capital ships are smaller than their Imperial counterparts, with each having diverse strengths due to their construction by various manufacturers. Rebel Mon Calamari Cruisers are noted for their incredible shield regeneration rates, while Corellian Corvettes are known for their speed.

The following Rebel/New Republic craft are included in the game:

*[https://starwars.fandom.com/wiki/X-wing_starfighter T-65 X-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL_Y-wing_starfighter BTL-A4 Y-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL-A4_LP_%22Longprobe%22 BTL-LP Longprobe Starfighter]
*[https://starwars.fandom.com/wiki/RZ-1_A-wing_interceptor RZ-1 A-wing Interceptor]
*[https://starwars.fandom.com/wiki/A/SF-01_B-wing_starfighter A/SF-01 B-wing Starfighter]
*[https://starwars.fandom.com/wiki/E-wing_escort_starfighter E-wing Escort Starfighter]
*[https://starwars.fandom.com/wiki/UT-60D_U-wing_starfighter/support_craft UT-60D U-wing]
*[https://starwars.fandom.com/wiki/Millennium_Falcon Millennium Falcon]

*[https://starwars.fandom.com/wiki/GR-75_medium_transport GR-75 Medium Transport]
*[https://starwars.fandom.com/wiki/CR90_corvette Corellian CR90 Corvette]
*[https://starwars.fandom.com/wiki/EF76_Nebulon-B_escort_frigate EF76 Nebulon-B Escort Frigate]
*[https://starwars.fandom.com/wiki/MC30C_frigate MC30 Heavy Frigate]
*[https://starwars.fandom.com/wiki/MC40a_light_cruiser MC40 Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Liberty_type_Star_Cruiser ''Liberty''-class Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Home_One_type_Star_Cruiser ''Home One''-class Star Cruiser]

===Galactic Empire===
[[Image:NuRTIE03.jpg|thumb|The TIE/ln Starfighter, main fighter of the Galactic Empire]]
The Galactic Empire's main strategy for fighters revolves around the concept of numerical advantage. Imperial TIEs usually lack shields and durability, but have very potent weaponry and great maneuverability to counter this weakness. Most Imperial fighters also forego any sort of missile secondary weapons and focus entirely on their lasers for offensive armament. Imperial capital ships are much larger than those of the Rebels, and focus on heavy offensive weaponry and great hull durability.

The following Imperial craft are included in the game:

*[https://starwars.fandom.com/wiki/TIE/LN_starfighter T.I.E. Starfighter & TIE/ln Starfighter]
*[https://starwars.fandom.com/wiki/TIE_Reconnaissance_Fighter TIE/rc Recon Fighter]
*[https://starwars.fandom.com/wiki/TIE/IN_interceptor/Legends TIE/In Interceptor Mark I and Mark II]
*[https://starwars.fandom.com/wiki/TIE/sa_bomber TIE/sa Bomber]
*[https://starwars.fandom.com/wiki/TIE_Advanced_x1 TIE Advanced x1]
*[https://starwars.fandom.com/wiki/V38_assault_fighter V38 Assault Fighter]

*[https://starwars.fandom.com/wiki/TIE/sh_shuttle TIE/sh Shuttle]
*[https://starwars.fandom.com/wiki/Alpha-class_Xg-1_Star_Wing Xg-1 Star Wing]
*[https://starwars.fandom.com/wiki/Delta-class_DX-9_stormtrooper_transport DX-9 Stormtrooper Transport]
*[https://starwars.fandom.com/wiki/Lambda-class_T-4a_shuttle Lambda-class T-4a Shuttle]
*[https://starwars.fandom.com/wiki/Zeta-class_Heavy_Cargo_Shuttle Zeta-class Heavy Cargo Shuttle]

*[https://starwars.fandom.com/wiki/Raider-class_corvette ''Raider''-class Corvette]
*[https://starwars.fandom.com/wiki/Carrack-class_light_cruiser ''Carrack''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Arquitens-class_light_cruiser ''Arquitens''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Strike-class_medium_cruiser ''Strike''-class Medium Cruiser]
*[https://starwars.fandom.com/wiki/Vindicator-class_heavy_cruiser ''Vindicator''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Interdictor_vessel ''Interdictor''-class Cruiser]
*[https://starwars.fandom.com/wiki/Imperial_II-class_Star_Destroyer ''Imperator II''-class Star Destroyer]
*[https://starwars.fandom.com/wiki/Golan_space_defense_platform Golan M-series Dockyard Platforms]
*[https://starwars.fandom.com/wiki/Shield_Gate Golan M-3185 Shield Gate Station]

===Neutral===
There are multiple factions in the Star Wars galaxy which use many craft that are not produced for the Galactic Empire or the Rebel Alliance. These craft vary in characteristics and are used throughout the galaxy in various roles.

The following Neutral craft are included in the game:

*[https://starwars.fandom.com/wiki/Z-95_Headhunter Z-95 Headhunter]
*[https://starwars.fandom.com/wiki/CloakShape_fighter/Legends Cloakshape Starfighter]
*[https://starwars.fandom.com/wiki/N-1_starfighter N-1 Naboo Starfighter]
*[https://starwars.fandom.com/wiki/Alpha-3_Nimbus-class_V-wing_starfighter Alpha-3 Nimbus-class V-wing Starfighter]
*[https://starwars.fandom.com/wiki/Aggressive_ReConnaissance-170_starfighter/Legends ARC-170 Starfighter]
*[https://starwars.fandom.com/wiki/Ugly/Legends Various Uglies]
*[https://starwars.fandom.com/wiki/Firespray-31-class_patrol_and_attack_craft Firespray-31-class Gunship]
*[https://starwars.fandom.com/wiki/Slave_I Slave I]
*[https://starwars.fandom.com/wiki/YT-1300_light_freighter YT-1300 Light Freighter]
*[https://starwars.fandom.com/wiki/BFF-1_bulk_freighter BFF-1 Bulk Freighter]
*[https://starwars.fandom.com/wiki/Tug DV-3 Cargo Freighter]
*[https://starwars.fandom.com/wiki/Action_VI_transport Action VI Transport]
*[https://starwars.fandom.com/wiki/Transport Rayter-class Transport]
*[https://starwars.fandom.com/wiki/CSS-1_Corellian_Star_Shuttle Star Shuttle]
*[https://starwars.fandom.com/wiki/StarSpeeder_1000 Star Speeder]
*[https://starwars.fandom.com/wiki/GAT-12_Skipray_Blastboat GAT-10 Skipray Blastboat]
*[https://starwars.fandom.com/wiki/Consular-class_cruiser_(Charger_c70_retrofit) Corellian Charger C70 Retrofit]
*[https://starwars.fandom.com/wiki/Braha'tok-class_gunship Braha'tok-class gunship]
*[https://starwars.fandom.com/wiki/Marauder-class_corvette Marauder-class corvette]
*[https://starwars.fandom.com/wiki/Dreadnaught-class_heavy_cruiser ''Dreadnaught''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Venator-class_Star_Destroyer ''Venator''-class Cruiser]
*[https://starwars.fandom.com/wiki/XQ_Platform_series XQ1 and XQ2 Stations]
*[https://starwars.fandom.com/wiki/Asteroid_base Asteroid Base Station]
*[https://starwars.fandom.com/wiki/Repair_droid Dockyard Repair Droids]
*[https://starwars.fandom.com/wiki/Satellite/Legends Sensor and Defense Satellites]
*[https://starwars.fandom.com/wiki/Space_mine Space Mines]

==Missions and Campaigns==
''Fate of the Galaxy'' comes with a high level of single-player content. These include multiple campaigns, standalone missions, and the ability to create missions using the FSO mission editor FRED2. Multiplayer servers are also maintained and available to play on with friends.

The first three campaigns narrate three interconnected stories set at the beginning of the Galactic Civil War. Each of these three campaigns consists of about 5 missions, thus designers put high emphasis on quality mission design and high replayability. The player's performance throughout the campaign will affect how later missions play out. For example, the Alliance campaign will pit a ragtag Rebel task force against a dreaded ''Imperial''-class Star Destroyer in the early stages of the Rebellion, and the player's performance throughout the campaign has a major impact on this encounter's difficulty. The best possible outcome is hard to achieve, thus a number of playthroughs will be required.

Players receive different types of training in different campaigns. The Alliance mini-campaign starts with a basic training mission that teaches the basics to new players along with gameplay features that are unique to ''Fate of the Galaxy'''. The Imperial mini-campaign starts with an advanced training.

Standalone missions are also included in the first release. Many of them are serious, story-driven missions, but there will also be arcade-like "challenge" missions in which the player must accomplish a wide variety of objectives, such as surviving two minutes within a ''Strike''-class cruiser's firing range. There will also be a Practice Zone mission, where the player can test flying any of the small craft and actively spawn in any craft in the mission as a hostile or friendly to practice combat.

Three additional campaigns are being worked on and will be available when the game is released to the public, but specific details remain under embargo until public launch. This large component is code-named Project Alderaan.

==Development==
[[Image:Ewingmaps.jpg|thumb|The progression of model work shown on an E-wing Starfighter, from Model (Right) to Normal Maps (Center) and Diffuse Texture (Left). Note that this model will not be used.]]
Fate of the Galaxy picks up after a number of previous attempts to create a ''Star Wars'' mod for FreeSpace. For several years the "Star Wars Conversion Project" was worked on by various teams and developers, but without any releases.

In early 2007, chief1983 took over as project leader, and began to assemble a new team of developers. Choosing the name ''Fate of the Galaxy'', the initial team consisted of chief1983, Brand-X as a modeler and Turambar as a texturer. The initial plan put forward was to use the models and textures that had been completed by previous teams. Soon after the reformation of the mod team, however, it was decided that all new art assets were needed to compete with the high graphical standards of the newer models, and all previously completed ships were discarded.

Work continued on ship models and textures through the next year and a half, as new staff members were added to the development team. In May of 2008, work began on implementing the new ship models into the game and work began on redesigning the feel and pace of the FreeSpace 2 Open engine. Work still continued on the models needed for a campaign and demo release.

In early January of 2009, Brand-X experienced a hard drive failure which destroyed all previous models of his, setting the team's art department back significantly. Since then, work has progressed on recreating these models to even higher quality standards.

On June 4th, 2009, the first in-game screenshot of the X-wing starfighter was made public at the [http://www.moddb.com/games/fate-of-the-galaxy/images/x-wing-in-game-shots2#imagebox ModDB site] and at the official FotG [https://www.hard-light.net/forums/index.php?board=143.0 forums]. The first three campaigns, which are set at the beginning of the Galactic Civil War, were eventually completed, and worked then moved to standalone missions and three additional campaigns code-named Project Alderaan.

In December of 2018 the team began the first phases of private beta testing. In June of 2022, the private beta tests were stated as nearly concluded.

In May of 2019 the [https://www.youtube.com/watch?v=ler20EdjAfs&list=LLW8-wdcPLv0eT913KIi9_mw&index=2&t=0s teaser trailer] was posted.

Throughout 2020-2022 developmental showcases have consisted of forum updates and gameplay streams on Discord.

In June of 2022, multiplayer was confirmed to be working well, and standalone servers were created.

From 2023-2024, the game underwent extensive balance and optimization testing in preparation for the public release.

For the duration of 2025, additional polishing passes were conducted and continue to be refined.

===Newsletter===
Newsletters are posted on a quarterly basis on the [https://www.hard-light.net/forums/index.php?board=143.0 Fate of the Galaxy Forums]. Also, the majority of the unofficial development chatter occurs on the Fate of the Galaxy Discord channel [https://discord.gg/k7ZMdmt].

The most recent [https://www.hard-light.net/forums/index.php?topic=99253.0] was released in May 2024. This update highlights new ship additions, MainHall updates, many other enhancements, and numerous fixes and minor updates.

For reference, the [http://www.hard-light.net/forums/index.php/topic,54217.0.html first newsletter] was posted on June 1st, 2008.

===First Release===
The first open beta of ''Fate of the Galaxy'' was originally planned to be released sometime late-2008 or early 2009. However, with the art setback, the release has been pushed back. Subsequent additions and developments then lead the team to decide to release the game as a more polished 1.0 version. A date has not been decided yet, but the first three campaigns are done and relatively independent compared to the larger subsequent 3 campaigns.

Recent years have shown considerable progress on the project, including a release of a private beta and addition of multiple ships and integrating new features that were recently added to the FSO engine (such as deferred and shadow lighting for cockpits, optimizations, and advanced scripting controls).

In the most recent communications on Discord, co-community manager wookieejedi posted: "''We are getting extremely close to releasing FotG publicly--one of the largest remaining milestones is having FSO release 25.0 stable (which is ideally not far away). We simply can’t wait to share the game with you all once those milestones are completed.''" (May 4th, 2025)

==Gallery==
===Ship Lab shots===
<gallery>
Image:Bwing.jpg
Image:Falcon2.jpg
Image:Xwing.jpg
Image:Ywing2.jpg
Image:Z95.jpg |
</gallery>
===Renders===
<gallery>
Image:FalconWallpaper.png
Image:TBrender.png
Image:TransportFinal.jpg
Image:Wallpaper.1-1280.png
Image:Wallpaper.2-1280.png
</gallery>

==Links==
*[http://swc.hard-light.net/ Official Website]
*[https://discord.gg/k7ZMdmt Fate of the Galaxy Discord Server]
*[https://www.hard-light.net/forums/index.php?board=143.0 Official Forum]
*[https://www.moddb.com/games/fate-of-the-galaxy Fate of the Galaxy on ModDB]

Fate of the Galaxy

2025-12-22T17:07:25Z

Wookieejedi: add venator

{{fotg}}

'''Fate of the Galaxy''' (FotG) is a free total conversion set in the ''[https://en.wikipedia.org/wiki/Star_Wars Star Wars]'' Original Trilogy. Developed using the open-source FreeSpace 2 Open (FSO) game engine, the project will be released as a standalone (the game FreeSpace 2 is not required). An active [https://fate-of-the-galaxy.github.io/ website], [https://www.hard-light.net/forums/index.php?board=143.0 forum] and [https://discord.gg/k7ZMdmt Discord Channel] are also maintained. As a disclaimer, Fate of the Galaxy is a total conversion for FreeSpace Open developed by a team of fan volunteers, it is not associated with Lucasfilm Ltd or Disney and is not an official Star Wars product

==Developers==
*'''chief1983:''' Project Lead
*'''Brand-X:''' Senior Artist and Content Moderator
*'''TopAce:''' Mission Design
*'''swashmebuckle:''' Music Composer, Writer
*'''zookeeper:''' Model Conversion, Artist, Scripting
*'''CountBuggula:''' Webmaster, Communications
*'''niffiwan:''' Coder
*'''wookieejedi:''' Mission Design, Scripting, Beta Management
*'''Limbert:''' Senior Artist
*'''bobbtmann:''' Senior Contributor
*'''Dark Visor:''' Senior Artist

''Full list of contributors is present in Credits screen of the game.''

==Gameplay==
In ''Fate of the Galaxy'' the player takes the role of a starfighter pilot through a series of missions and campaigns. The game is primarily played through the perspective of single-manned craft. There are no plans currently for player-control of capital ships, though certain player craft do allow for AI gunners. Current missions are set in space, including in asteroid fields, nebulas, and above planets. A multiplayer mode is also available to play and works well at low pings (~<100 ms). Standalone instances of the game are maintained, which allows players to easily join a server and play with friends.

The player will choose to play as a pilot for the Rebel Alliance, the Galactic Empire, or as an independent neutral adventurer/privateer. All factions have their own unique ships to control.

===Authenticity===
''Fate of the Galaxy'' strives to recreate combat as close to as seen in the Original Trilogy of ''Star Wars'', during scenes such as the [https://starwars.fandom.com/wiki/Battle_of_Endor/Legends Battle of Endor] and the [https://starwars.fandom.com/wiki/Battle_of_Yavin Battle of Yavin]. To achieve this, the members of the development team have extensively analyzed individual movements and moments within these scenes to determine a baseline for such game concepts as damage, speed, and maneuverability. Each fighter will stay as close as possible to its canonical statistics stated in various sources, but the final authority is the Original Trilogy movies themselves. Thus, many attributes may be contrary to other published materials due to their divergence from the Original Trilogy. In addition, visuals have been tuned to match the aesthetic of the Original Trilogy movies.

Given this focus on movie authenticity, the gameplay differs from that present in the default FreeSpace 2 universe. Ships will be much faster and combat quicker paced, with a larger focus on avoiding damage rather than absorbing it. Several coding features have been completed to create a new, unique style of combat.

==Vehicles==
The game includes multiple ships unique to each faction, with some designs being shared when appropriate. Each faction's fighters and capital ships have unique strengths, which presents different gameplay styles for each side.

===Alliance to Restore the Republic/New Republic===
[[Image:NuX.png|thumb|The X-wing Starfighter, main fighter of the Rebel Alliance]]
The Alliance to Restore the Republic and New Republic maintain a focus on versatile and durable starfighters and small, fast capital ships. Most of the Rebel fighters are equipped with secondary missile weapons such as concussion missiles or proton torpedoes. Rebel players will, in most cases, be unable to outmaneuver their Imperial counterparts and will rely on their superior durability and weapon complement, as well as teamwork to engage the enemy. Rebel capital ships are smaller than their Imperial counterparts, with each having diverse strengths due to their construction by various manufacturers. Rebel Mon Calamari Cruisers are noted for their incredible shield regeneration rates, while Corellian Corvettes are known for their speed.

The following Rebel/New Republic craft are included in the game:

*[https://starwars.fandom.com/wiki/X-wing_starfighter T-65 X-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL_Y-wing_starfighter BTL-A4 Y-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL-A4_LP_%22Longprobe%22 BTL-LP Longprobe Starfighter]
*[https://starwars.fandom.com/wiki/RZ-1_A-wing_interceptor RZ-1 A-wing Interceptor]
*[https://starwars.fandom.com/wiki/A/SF-01_B-wing_starfighter A/SF-01 B-wing Starfighter]
*[https://starwars.fandom.com/wiki/E-wing_escort_starfighter E-wing Escort Starfighter]
*[https://starwars.fandom.com/wiki/UT-60D_U-wing_starfighter/support_craft UT-60D U-wing]
*[https://starwars.fandom.com/wiki/Millennium_Falcon Millennium Falcon]

*[https://starwars.fandom.com/wiki/GR-75_medium_transport GR-75 Medium Transport]
*[https://starwars.fandom.com/wiki/CR90_corvette Corellian CR90 Corvette]
*[https://starwars.fandom.com/wiki/EF76_Nebulon-B_escort_frigate EF76 Nebulon-B Escort Frigate]
*[https://starwars.fandom.com/wiki/MC30C_frigate MC30 Heavy Frigate]
*[https://starwars.fandom.com/wiki/MC40a_light_cruiser MC40 Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Liberty_type_Star_Cruiser ''Liberty''-class Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Home_One_type_Star_Cruiser ''Home One''-class Star Cruiser]

===Galactic Empire===
[[Image:NuRTIE03.jpg|thumb|The TIE/ln Starfighter, main fighter of the Galactic Empire]]
The Galactic Empire's main strategy for fighters revolves around the concept of numerical advantage. Imperial TIEs usually lack shields and durability, but have very potent weaponry and great maneuverability to counter this weakness. Most Imperial fighters also forego any sort of missile secondary weapons and focus entirely on their lasers for offensive armament. Imperial capital ships are much larger than those of the Rebels, and focus on heavy offensive weaponry and great hull durability.

The following Imperial craft are included in the game:

*[https://starwars.fandom.com/wiki/TIE/LN_starfighter T.I.E. Starfighter & TIE/ln Starfighter]
*[https://starwars.fandom.com/wiki/TIE_Reconnaissance_Fighter TIE/rc Recon Fighter]
*[https://starwars.fandom.com/wiki/TIE/IN_interceptor/Legends TIE/In Interceptor Mark I and Mark II]
*[https://starwars.fandom.com/wiki/TIE/sa_bomber TIE/sa Bomber]
*[https://starwars.fandom.com/wiki/TIE_Advanced_x1 TIE Advanced x1]
*[https://starwars.fandom.com/wiki/V38_assault_fighter V38 Assault Fighter]

*[https://starwars.fandom.com/wiki/TIE/sh_shuttle TIE/sh Shuttle]
*[https://starwars.fandom.com/wiki/Alpha-class_Xg-1_Star_Wing Xg-1 Star Wing]
*[https://starwars.fandom.com/wiki/Delta-class_DX-9_stormtrooper_transport DX-9 Stormtrooper Transport]
*[https://starwars.fandom.com/wiki/Lambda-class_T-4a_shuttle Lambda-class T-4a Shuttle]
*[https://starwars.fandom.com/wiki/Zeta-class_Heavy_Cargo_Shuttle Zeta-class Heavy Cargo Shuttle]

*[https://starwars.fandom.com/wiki/Carrack-class_light_cruiser ''Carrack''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Arquitens-class_light_cruiser ''Arquitens''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Strike-class_medium_cruiser ''Strike''-class Medium Cruiser]
*[https://starwars.fandom.com/wiki/Vindicator-class_heavy_cruiser ''Vindicator''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Interdictor_vessel ''Interdictor''-class Cruiser]
*[https://starwars.fandom.com/wiki/Imperial_II-class_Star_Destroyer ''Imperator II''-class Star Destroyer]
*[https://starwars.fandom.com/wiki/Golan_space_defense_platform Golan M-series Dockyard Platforms]
*[https://starwars.fandom.com/wiki/Shield_Gate Golan M-3185 Shield Gate Station]

===Neutral===
There are multiple factions in the Star Wars galaxy which use many craft that are not produced for the Galactic Empire or the Rebel Alliance. These craft vary in characteristics and are used throughout the galaxy in various roles.

The following Neutral craft are included in the game:

*[https://starwars.fandom.com/wiki/Z-95_Headhunter Z-95 Headhunter]
*[https://starwars.fandom.com/wiki/CloakShape_fighter/Legends Cloakshape Starfighter]
*[https://starwars.fandom.com/wiki/N-1_starfighter N-1 Naboo Starfighter]
*[https://starwars.fandom.com/wiki/Alpha-3_Nimbus-class_V-wing_starfighter Alpha-3 Nimbus-class V-wing Starfighter]
*[https://starwars.fandom.com/wiki/Aggressive_ReConnaissance-170_starfighter/Legends ARC-170 Starfighter]
*[https://starwars.fandom.com/wiki/Ugly/Legends Various Uglies]
*[https://starwars.fandom.com/wiki/Firespray-31-class_patrol_and_attack_craft Firespray-31-class Gunship]
*[https://starwars.fandom.com/wiki/Slave_I Slave I]
*[https://starwars.fandom.com/wiki/YT-1300_light_freighter YT-1300 Light Freighter]
*[https://starwars.fandom.com/wiki/BFF-1_bulk_freighter BFF-1 Bulk Freighter]
*[https://starwars.fandom.com/wiki/Tug DV-3 Cargo Freighter]
*[https://starwars.fandom.com/wiki/Action_VI_transport Action VI Transport]
*[https://starwars.fandom.com/wiki/Transport Rayter-class Transport]
*[https://starwars.fandom.com/wiki/CSS-1_Corellian_Star_Shuttle Star Shuttle]
*[https://starwars.fandom.com/wiki/StarSpeeder_1000 Star Speeder]
*[https://starwars.fandom.com/wiki/GAT-12_Skipray_Blastboat GAT-10 Skipray Blastboat]
*[https://starwars.fandom.com/wiki/Consular-class_cruiser_(Charger_c70_retrofit) Corellian Charger C70 Retrofit]
*[https://starwars.fandom.com/wiki/Braha'tok-class_gunship Braha'tok-class gunship]
*[https://starwars.fandom.com/wiki/Marauder-class_corvette Marauder-class corvette]
*[https://starwars.fandom.com/wiki/Dreadnaught-class_heavy_cruiser ''Dreadnaught''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Venator-class_Star_Destroyer ''Venator''-class Cruiser]
*[https://starwars.fandom.com/wiki/XQ_Platform_series XQ1 and XQ2 Stations]
*[https://starwars.fandom.com/wiki/Asteroid_base Asteroid Base Station]
*[https://starwars.fandom.com/wiki/Repair_droid Dockyard Repair Droids]
*[https://starwars.fandom.com/wiki/Satellite/Legends Sensor and Defense Satellites]
*[https://starwars.fandom.com/wiki/Space_mine Space Mines]

==Missions and Campaigns==
''Fate of the Galaxy'' comes with a high level of single-player content. These include multiple campaigns, standalone missions, and the ability to create missions using the FSO mission editor FRED2. Multiplayer servers are also maintained and available to play on with friends.

The first three campaigns narrate three interconnected stories set at the beginning of the Galactic Civil War. Each of these three campaigns consists of about 5 missions, thus designers put high emphasis on quality mission design and high replayability. The player's performance throughout the campaign will affect how later missions play out. For example, the Alliance campaign will pit a ragtag Rebel task force against a dreaded ''Imperial''-class Star Destroyer in the early stages of the Rebellion, and the player's performance throughout the campaign has a major impact on this encounter's difficulty. The best possible outcome is hard to achieve, thus a number of playthroughs will be required.

Players receive different types of training in different campaigns. The Alliance mini-campaign starts with a basic training mission that teaches the basics to new players along with gameplay features that are unique to ''Fate of the Galaxy'''. The Imperial mini-campaign starts with an advanced training.

Standalone missions are also included in the first release. Many of them are serious, story-driven missions, but there will also be arcade-like "challenge" missions in which the player must accomplish a wide variety of objectives, such as surviving two minutes within a ''Strike''-class cruiser's firing range. There will also be a Practice Zone mission, where the player can test flying any of the small craft and actively spawn in any craft in the mission as a hostile or friendly to practice combat.

Three additional campaigns are being worked on and will be available when the game is released to the public, but specific details remain under embargo until public launch. This large component is code-named Project Alderaan.

==Development==
[[Image:Ewingmaps.jpg|thumb|The progression of model work shown on an E-wing Starfighter, from Model (Right) to Normal Maps (Center) and Diffuse Texture (Left). Note that this model will not be used.]]
Fate of the Galaxy picks up after a number of previous attempts to create a ''Star Wars'' mod for FreeSpace. For several years the "Star Wars Conversion Project" was worked on by various teams and developers, but without any releases.

In early 2007, chief1983 took over as project leader, and began to assemble a new team of developers. Choosing the name ''Fate of the Galaxy'', the initial team consisted of chief1983, Brand-X as a modeler and Turambar as a texturer. The initial plan put forward was to use the models and textures that had been completed by previous teams. Soon after the reformation of the mod team, however, it was decided that all new art assets were needed to compete with the high graphical standards of the newer models, and all previously completed ships were discarded.

Work continued on ship models and textures through the next year and a half, as new staff members were added to the development team. In May of 2008, work began on implementing the new ship models into the game and work began on redesigning the feel and pace of the FreeSpace 2 Open engine. Work still continued on the models needed for a campaign and demo release.

In early January of 2009, Brand-X experienced a hard drive failure which destroyed all previous models of his, setting the team's art department back significantly. Since then, work has progressed on recreating these models to even higher quality standards.

On June 4th, 2009, the first in-game screenshot of the X-wing starfighter was made public at the [http://www.moddb.com/games/fate-of-the-galaxy/images/x-wing-in-game-shots2#imagebox ModDB site] and at the official FotG [https://www.hard-light.net/forums/index.php?board=143.0 forums]. The first three campaigns, which are set at the beginning of the Galactic Civil War, were eventually completed, and worked then moved to standalone missions and three additional campaigns code-named Project Alderaan.

In December of 2018 the team began the first phases of private beta testing. In June of 2022, the private beta tests were stated as nearly concluded.

In May of 2019 the [https://www.youtube.com/watch?v=ler20EdjAfs&list=LLW8-wdcPLv0eT913KIi9_mw&index=2&t=0s teaser trailer] was posted.

Throughout 2020-2022 developmental showcases have consisted of forum updates and gameplay streams on Discord.

In June of 2022, multiplayer was confirmed to be working well, and standalone servers were created.

From 2023-2024, the game underwent extensive balance and optimization testing in preparation for the public release.

For the duration of 2025, additional polishing passes were conducted and continue to be refined.

===Newsletter===
Newsletters are posted on a quarterly basis on the [https://www.hard-light.net/forums/index.php?board=143.0 Fate of the Galaxy Forums]. Also, the majority of the unofficial development chatter occurs on the Fate of the Galaxy Discord channel [https://discord.gg/k7ZMdmt].

The most recent [https://www.hard-light.net/forums/index.php?topic=99253.0] was released in May 2024. This update highlights new ship additions, MainHall updates, many other enhancements, and numerous fixes and minor updates.

For reference, the [http://www.hard-light.net/forums/index.php/topic,54217.0.html first newsletter] was posted on June 1st, 2008.

===First Release===
The first open beta of ''Fate of the Galaxy'' was originally planned to be released sometime late-2008 or early 2009. However, with the art setback, the release has been pushed back. Subsequent additions and developments then lead the team to decide to release the game as a more polished 1.0 version. A date has not been decided yet, but the first three campaigns are done and relatively independent compared to the larger subsequent 3 campaigns.

Recent years have shown considerable progress on the project, including a release of a private beta and addition of multiple ships and integrating new features that were recently added to the FSO engine (such as deferred and shadow lighting for cockpits, optimizations, and advanced scripting controls).

In the most recent communications on Discord, co-community manager wookieejedi posted: "''We are getting extremely close to releasing FotG publicly--one of the largest remaining milestones is having FSO release 25.0 stable (which is ideally not far away). We simply can’t wait to share the game with you all once those milestones are completed.''" (May 4th, 2025)

==Gallery==
===Ship Lab shots===
<gallery>
Image:Bwing.jpg
Image:Falcon2.jpg
Image:Xwing.jpg
Image:Ywing2.jpg
Image:Z95.jpg |
</gallery>
===Renders===
<gallery>
Image:FalconWallpaper.png
Image:TBrender.png
Image:TransportFinal.jpg
Image:Wallpaper.1-1280.png
Image:Wallpaper.2-1280.png
</gallery>

==Links==
*[http://swc.hard-light.net/ Official Website]
*[https://discord.gg/k7ZMdmt Fate of the Galaxy Discord Server]
*[https://www.hard-light.net/forums/index.php?board=143.0 Official Forum]
*[https://www.moddb.com/games/fate-of-the-galaxy Fate of the Galaxy on ModDB]

Game settings.tbl

2025-10-15T20:47:22Z

Wookieejedi: add new target bomb or bomber options

{{SCP_table}}
{{TableVersionGit|2025-02-10|642111676012bc6696f4024c40296a6c20b3b958}}
{{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

If the version targeted in [[game_settings.tbl#$Target_Version:|target version]] is equal to or later than these listed, the following options are enabled by default:
{{Table220|
*[[game_settings.tbl#$Fixed_Turret_Collisions:|Fixed Turret Collisions]]
*[[game_settings.tbl#$Fixed_Missile_Detonation:|Fixed Missile Detonation]]
*[[game_settings.tbl#$Shockwaves_Damage_All_Object_Types_Once:|Shockwaves Damage All Object Types Once]]
*[[game_settings.tbl#$AI_use_framerate_independent_turning:|AI use framerate independent turning]]
*[[game_settings.tbl#$Use_host_orientation_for_set-camera-facing:|Use host orientation for set-camera-facing]]
}}
{{Table230|
*[[game_settings.tbl#$Shockwaves_Inherit_Parent_Weapon_Damage_Type:|Shockwaves Inherit Parent Weapon Damage Type]]
*[[game_settings.tbl#$Fixed_Chaining_To_Repeating_Events:|Fixed Chaining To Repeating Events]]
}}
{{Table240|
*[[game_settings.tbl#$Calculate_subsystem_hitpoints_after_parsing:|Calculate subsystem hitpoints after parsing]]}}

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

The icon should be in data/maps or data/interface, and can apparently be any single-frame image format supported by FSO. The default icon is .png.

*Syntax: '''''String'''''
}}

===$Mod title:===
{{Table224|
Specifies the title of the mod and will be displayed at the mainhall near the FSO version.
*Syntax: '''''String'''''
}}
{{Table250|
It is now possible to display the mod title on its own. Previously, the mod version was also required.
}}

===$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'''''
}}
{{Table250|
It is now possible to display the mod version on its own. Previously, the mod title was also required.
}}

===$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'''''}}

===$Splash screens:===
{{Table232|
Defines a list of splash screens that FSO can display upon game startup. The actual image displayed is chosen at random from the applicable entries. Entries with exact aspect ratio matches will be prioritized first, followed by aspect ratio ranged matches, followed by entries without an aspect ratio specified.}}

====+Bitmap:====
{{table232|
The name of the bitmap to use as a splash screen. Extension will be removed if included.
*Syntax: '''''+Bitmap: String'''''}}

====+Aspect Ratio:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio matches the specified number within +/- 0.01.
*Syntax: '''''+Aspect Ratio: Float'''''}}

====+Aspect Ratio Min:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at least the specified number.
*Syntax: '''''+Aspect Ratio Min: Float'''''}}

====+Aspect Ratio Max:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at most the specified number.
*Syntax: '''''+Aspect Ratio Max: Float'''''}}

===$Splash fade in time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade in.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Splash fade out time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade out.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Center splash logo:===
{{Table232|
Sets whether the splash logo will be displayed in the middle of the screen. If this is false (the default), it will be displayed at the top-left.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Disable FSO Internal Loadout Restoration System:===
{{Table234|
When the player configures the ships and weapons of the wings in the loadout screen, FSO will remember these settings and attempt to apply them again if the player quits the mission and comes back to it later. FSO will only remember the most recent mission's loadout, so it will not attempt to restore the loadout if the player loads a different mission. It will also not attempt this if the mission's ''$Modified:'' date has changed. This flag can be used to prevent FSO from attempting restoration even if it normally would.
*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'''''
}}

===$HUD drop shadows enabled by default:===
{{Table232|
If this flag is active, certain elements displayed on the HUD (all text, the main targeting reticle, and the background of the ETS gauges) will have a "drop shadow" effect. Note that whether or not the flag is active, the player can set this using the "Toggle HUD Drop Shadows" control.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Unify scanning behavior:===
{{Table242|
*Unifies scanning behavior between subsystem, regular, and cargo allowing missions to use all scan types in all situations.
*Also allows changing the "Cargo:" text line in a mission by adding "$Cargo Title: STRING" after the "$Cargo 1:" or "$Cargo 2:" lines in the mission file. FRED UI support not yet added for $Cargo Title so you have to do it manually.
*When this flag is enabled, all ships, no matter the ship class, will react the same way to the cargo-related or scanning-related ship flags:
**They are not scannable by default
**Setting the "scannable" flag makes them scannable, and scanning the subsystem will reveal the cargo
**A new flag available with alter-ship-flag, "no-scanned-cargo", changes the behavior to scanned/unscanned instead of revealing the cargo
**The "toggle-subsystem-scanning" flag must be set to swap full-ship scanning mode into subsystem scanning mode and works for all ship types
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Don't show callsigns in the escort list:===
{{Table242|
By default, callsigns are shown in the escort list using the same format as in the target box. If this flag is active, callsigns will not be displayed.
*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'''''

===$Fixed Chaining To Repeating Events:===
{{Table230|When set, this makes event chaining to repeated events work as designed - that is, the chained event will only be evaluated after the chain delay. If the repeating event's interval is shorter than the chain delay, then the delay countdown will continually be restarted until all repetitions have completed. Without this flag, FSO will emulate retail behavior which, due to a bug, allowed chained events to be evaluated immediately after a repeating event is first evaluated.

NOTE: Although the name does not reflect it, the same issue affects repeating events that are evaluated by <tt>is-event-true-delay</tt> and <tt>is-event-false-delay</tt>. Without this flag, FSO will emulate retail behavior which causes these SEXP operators to ignore any delay when evaluating repeated events. With this flag, the delay will be measured from when the final repeat iteration occurs.
*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)'''''}}

===$HUD-set-coords base resolution:===
{{Table232|The hud-set-coords SEXP has always used exact pixels, without regard for the current screen resolution. This setting enables a similar scaling mechanism as ''$Show-subtitle base resolution:''.
*Syntax: '''''(Integer, Integer)'''''
*Default Value: '''''(-1, -1)'''''}}

===$$Always Show Directive Value Count:===
{{Table250|
*If this setting is enabled, Directive-as-Value values in Directives will always show the number. By default this is disabled, and only values > 1 are shown.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

==#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'''''}}

===$EMP Pain Flash Factor:===
{{Table224|
Determines the intensity of the flash when the player is hit by an EMP blast or weapon.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$EMP Pain Flash Color:===
{{Table224|
Determines the RGB color value of the flash when the player is hit by an EMP blast or weapon.
*Syntax: Color, (red, green, blue) respectively, integer value from 0 to 255
*Default Value: '''''(255, 255, 127)'''''}}

===$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)
}}

===$EMP Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)
}}

===$Damage Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)'''''}}

===$Shadow Disable Techroom:===
{{Table224|
Disables shadows on ships in the techroom.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Cockpit:===
{{Table224|
Disables shadows on the player cockpit in mission.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Weapons:===
{{Table224|
Disables shadows on weapons in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Ships:===
{{Table224|
Disables shadows on ships in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Show Ship Casts Shadow:===
{{Table224|
When cockpit shadows are enabled, enabling this setting will cause the players ship model shown with "show ship" to cast shadow onto the cockpit.
*Syntax: '''''Boolean'''''
}}

===$Ship Model And Cockpit Share Coordinate Space:===
{{Table224|
When having the "show ship" flag enabled and cockpit models for a ship, this flag should be on if the cockpits can fit into the actual geometry of the ship model. Disable this flag if this is not the case and the cockpit needs to be rendered on top of the ship regardless of actual coordinates. If this can be enabled, the external show ship model can be rendered using deferred rendering.
*Syntax: '''''Boolean'''''
}}

===$Show Ship enabled only if Cockpits enabled:===
{{Table250|
Enabling this setting will only use the 'show-ship' flag if cockpits are enabled. Useful if your ship uses both 'show-ship' and cockpits that exist within the 'show-ship' space, and you want to allow players to toggle off cockpits. Note, 'show-ship' always only appears if in first-person view.
*Syntax: '''''Boolean'''''
}}

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

===$Do Not Render Lasers Below Length:===
{{Table250|
*Specifies the smallest length that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Do Not Render Lasers Below Radius:===
{{Table250|
*Specifies the smallest radius that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Thruster Easing Value:===
{{Table220|
*Smooths out the behavior of maneuvering thruster flares the higher above 0 it is.
*This is the exponential time constant for the visual flare length to reach it's true length.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

===$SCPUI attempts to load hires animations:===
{{Table230|
*Prevents SCPUI from trying to load anims prefixed with "2_"
*Syntax: '''''Boolean'''''
*Default Value: true}}

{{Table230|
===$Max draw distance:===
===$Min draw distance:===
*These values do more than just cutoff the visuals at certain distances, and they must be adjusted carefully to ensure unintentional rendering artifacts are not introduced.
*The rendering engine has limited amount of 'depth resolution', the degree to which it can tell a certain polygon is closer or farther away than another. When two polygons are too close, they will Z-fight, picking arbitrarily which is closer. It is the span between the min and max draw distance that determines how well the engine can determine depth, if they are too far from one another, the Z-fighting will become more common as it has to spread its resolution over a wider range. If they are close, Z-fighting will be lessened at the cost of a smaller range of distance able to be rendered.
*Syntax: '''''Float''''', meters
*Default Values: 10,000,000,000 and 1, respectively
}}

{{Table232|
===$Randomize particle rotation:===
*Particle bitmaps are typically screen-aligned; the upper portion of the bitmap will always be mapped to the upper portion of the particle, from the point of view of the camera. Enabling this option makes ''all'' particles have a random 'tilt' in an arbitrary direction when created.
*Syntax: '''''Boolean'''''
*Default Value: false
}}

===$Disable shield effects:===
{{Table250|
*Specifies if FSO attempts to use the shield mesh impact effects. Enabling this flag will prevent the game from preforming any shield mesh effect code, which can be useful if a mod does not use those shield mesh effects.
*Syntax: '''''Boolean'''''
*Default Value: false}}

===$Disable all non-custom generic debris:===
{{Table250|
*Provides one simple control to turn off all non-custom generic debris (the tiny debris shards that are typically spawned when a ship/subsystem explodes). Note, generic debris that is manually specified in the ships table will still be spawned, this is only for turning off non-custom debris.
*Syntax: '''''Boolean'''''
*Default Value: false}}

==#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'''''}}

===$Use weapon class impact sounds for hits to player:===
{{Table224|
Allows weapons that hit the player to play their specific impact sounds, not the hard-coded default sounds.
*Syntax: '''''Boolean'''''
}}

===$Play thruster sounds for the player:===
{{Table232|
If the player's ship has thruster sounds defined, this will ensure they are played like normal, since they are typically suppressed.
*Syntax: '''''Boolean'''''
}}

===$Unify minimum engine sound:===
{{Table250|
Allows $Minimum Engine Volume in ships.tbl to work for all ship classes. By default, that value only triggers for non-huge ships.
*Syntax: '''''Boolean'''''
}}

===$Disabled or disrupted engines are silent:===
{{Table250|
If set, engines will not play their engine noise if the ship is disabled or a disrupted (such as disruptions caused by an active EMP effect or a weapon with the "electronics" flag).
*Syntax: '''''Boolean'''''
}}

==#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'''''}}

===$Add Message Head Ani Files:===
{{table224|
FRED will append each +Head entry listed below to the head ani selection list in the Event Editor.}}

====+Head:====
{{table224|
The head ani filename to add. Extensions will be stripped if included.
NOTE: Pay attention to file names or anis with a,b, c variation not display in-game (unless called directly). Proper name seems to be Head-xxxNa, Head-xxxNb, with N being some number and XXX being whatever you want. Needs further testing and confirmation
*Syntax: '''''+Head: String'''''}}

===$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'''''}}

===$FRED Briefing window resolution:===
{{table224|
The width and height of the briefing window in FRED. Defaults to 888x371. Note that changing this only affects FRED and can cause a mismatch to the ingame briefing view which defaults to 888x371 (or 555x232 for 640 base res).
*Syntax: '''''integer, integer'''''
*Default Value: '''''888,371'''''}}

===$Ignore Music Files In Music Player:===
{{table232|Music files in this section will not be added to FRED's built-in music player.}}
====+File:====
{{table232|Specifies a file
*Syntax: '''''string'''''}}

===$FRED spacemouse nonlinearities:===
{{table232|
Allows setting custom nonlinearities and scaling for controlling FRED with a spacemouse.
}}
====+Sideways exponent:====
{{table232|
The exponent for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Sideways scale:====
{{table232|The multiplier for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards exponent:====
{{table232|The exponent for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards scale:====
{{table232|The multiplier for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards exponent:====
{{table232|The exponent for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards scale:====
{{table232|The multiplier for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch exponent:====
{{table232|The exponent for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch scale:====
{{table232|The multiplier for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank exponent:====
{{table232|The exponent for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank scale:====
{{table232|The multiplier for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading exponent:====
{{table232|The exponent for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading scale:====
{{table232|The multiplier for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}

===$Skybox internal depth consistency:===
{{table250|If enabled, this will allow skyboxes that use submodels to render the submodels with proper Z-sorting if the 'No Z-Buffer' check box is set to on in FRED. In other words, parts of the skybox closer to the origin point will render in front of sections further away, as might be expected. This flag is enabled by default for FSO version 25.0 onwards
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

==#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. This fixes missile impacts to submodels whose center lies outside the geometry of the submodel. In other words, without this flag, a missile might detonate in the middle of the "bowl" of a concave submodel; with this flag, the missile will travel to the other side of the submodel before it detonates.
*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'''''

===$Use 3d ship select:===
{{Table224|
*Whether or not to use 3D models for ship select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d ship icons:===
{{Table224|
*Whether or not to use 3D models for ships in ship/weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d weapon select:===
{{Table224|
*Whether or not to use 3D models for weapon select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d weapon icons:===
{{Table224|
*Whether or not to use 3D models for weapons in weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d overhead ship:===
{{Table224|
*Whether or not to use 3D models for ship overhead view instead of a bitmap in weapon select
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Default overhead ship style:===
{{Table224|
*This specifies which style of overhead view to use if 3d overhead view is active
*Syntax: '''''String'''''
*Possible options are "ROTATE" or "TOPVIEW"}}

===$Always refresh selected weapon when viewing loadout:===
{{Table232|
*When set to true, this always refreshes the weapon shown in view box on the right side of the screen when opening the weapon loadout view. This ensures the viewed weapon is one that can actually be on the selected ship when first clicking on the weapon loadout screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$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|
*Mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. By default is now ON, and can be accessed by going to the Options menu and pressing F3.
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

===$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'''''}}

===$Apply HUD shudder to chase view:===
{{Table232|
*Applies hud shudder (afterburner and engine wash) also to chase view. Does not override the command line toggle.
*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'''''}}

===$Lead indicator behavior:===
{{Table224|
Changes how Lead Indicators behave when multiple weapon banks are linked and in range.
When set to default, if you have linked weapons, only the indicator for the one with the farthest range will be drawn.
When set to multiple, a lead indicator is drawn for all primary weapons in range when you have them linked.
When set to average, a single lead indicator is drawn in the average of the position where each of them would usually be drawn.
*Syntax: '''''String'''''
** Valid options are '''''default''''', '''''multiple''''' and '''''average'''''
*Default Value: '''''default'''''
}}

===$Use distant firepoint for all turrets:===
{{Table224|
*Causes the game to use firepoint-based target leading calculations for all turrets. This is useful if all or most turrets in a given mod has firepoints that are distant from their center-point.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Enable discord rich presence:===
{{Table224|
*Enables or disables the built-in Discord game-status reporting.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Always hide hidden ships in hotkey list:===
{{Table224|
*Whether or not to always hide ships with HIDDEN hotkey (set in FRED), even in the in-mission hotkey menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Allow automatically assigning personas:===
{{Table232|
*Whether or not the game will automatically assign personas to ships that have no persona set.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Countermeasures use capacity:===
{{Table232|
*Whether or not Countermeasures use tabled capacity.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Calculate subsystem hitpoints after parsing:===
{{Table234|
*Causes subsystem hitpoints to be calculated after all ships.tbl and -shp.tbm files have been parsed. This allows subsystem percentages to correctly reflect the final hull value rather than the first hull value encountered.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix scripted velocity:===
{{Table242|
*If this setting is enabled, object velocity set via script will wholly determine the change in position for that frame, ignoring ''all'' other in-engine concerns. Otherwise, the game engine will likely overwrite/ignore any changes, depending on when the changes were made in the frame.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Preload briefing icon models:===
{{Table250|
*If set, this forces preloading of models used for briefing icons. This only loads models used for icons that haven't already been loaded for the mission. This is useful for SCPUI's where hovering over an icon shows the model without having to click on it and the stutter when it loads models not used in mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Behavior for pressing Escape key in options menu:===
{{Table250|
*If set to 'save', the escape key for the HUD and Options screen saves options when leaving those screens (ie it does the same thing as pressing Ctrl-Enter/Accept). By default (or if set to 'default') the Escape key will not save any changed values when exiting those screens.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Use closest distance method for 'Target Hostile Bomb or Bomber' control:===
{{Table250|
*If set to true, the 'Target Hostile Bomb or Bomber' control will target the closest hostile bomb or bomber, similar to how the 'Target Closest Hostile' key works. By default, the 'Target Hostile Bomb or Bomber' control will not sort by distance and simply only target in order of oldest to youngest objects (ie which object spawned first in the mission).
*Syntax: '''''Boolean'''''
*Default Value: '''''false'''''}}

===$Objects targeted with 'Target Hostile Bomb or Bomber' control:===
{{Table250|
*Determines what can be targeted when using the 'Target Hostile Bomb or Bomber' control. By default this control targets both bombs and bombers, which is the behavior if this field is set to 'default' or 'bombs and bombers'. If set to 'only bombs', the key will only target bombs and not target bombers. If set to 'only bombers', the key will only target bombers and not target bombs.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Disable intro cutscene:===
{{Table250|
*If set, this disables loading of any cutscenes as the game starts that might play before the player reaches the pilot select screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Show locked status for scramble missions:===
{{Table250|
*If set, scramble mission will show a text line right below the words 'Weapons Loadout' that states "Ships/Weapons Locked" (XSTR 749), thus the player can easily see their loadouts are locked and they do not have to check the loaoout buttons on every mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable expensive turret target check:===
{{Table250|
*If set, this value speeds up turret target checking. By default, turret target acquisition was spending a lot of time doing a raycast, the result of which was barely used at all. If we don't need the target normal, all it does is get a target point slightly more accurate, but in practice it really isn't noticeable at all whether the target point of the turret is actually on the surface of the ship, or maybe on the other side of the ship.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Threshold below which shield skips damage:===
{{Table250|
*By default, FSO logic dictates that shields collisions and any related sound or visuals related to shields are skipped if the shields are under 10%. This value allows modders to customize the value, though the value must be between 0.0 and 1.0.
*Syntax: '''''Float'''''
*Default Value: '''''0.1'''''}}

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

Ai profiles.tbl

2025-10-15T20:35:04Z

Wookieejedi: add $max allies rearming threshold:

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''
*'''purge player-issued form-on-wing after subsequent order'''}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$max allies rearming threshold:===
{{Table250|
*The maximum allowed number of allies that are allowed to be rearming at the same time. It should be noted that the effect is more noticeable at higher numbers.
*2 by default.
*Syntax: '''''Integer'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use ai-form-on-wing-new:===
{{Table250|
*Will cause form-on-wing orders issued by the hud squadmsg menu (i.e. player orders) to be the 'new' variant that does not clear other goals assigned to the same ship/wing.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

===$don't issue form-on-wing goals at mission start:===
{{Table250|
*Normally, at the beginning of a mission, player wings that do not have an initial goal will be given an initial goal to form on the player. Wings in the loadout screen (aka "starting" wings) will also, if they do not have an initial goal, be issued the same goal if they arrive after mission start. This flag disables that behavior.
*Syntax: '''''Boolean'''''}}

===$default form-on-wing priority:===
{{Table250|
*The default goal priority to be used when issuing a form-on-wing order via sexp or script. If not specified, this is 99. Note that orders issued via the HUD communications system will use the standard communications priorities (100 for ships and 95 for wings) regardless of this setting.
*Syntax: '''''Integer'''''}}

===$do not clear goals when running form-on-wing:===
{{Table250|
*Normally, as soon as a form-on-wing goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the form-on-wing behavior while forgetting both the form goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not clear goals when running stay-still:===
{{Table250|
*Normally, as soon as a stay-still goal is executed by a ship, every goal on that ship is cleared. Thus the ship will follow the stay-still behavior while forgetting both the stay-still goal and all previous goals, and if it receives any other goal in any way, it will immediately begin a new behavior. This flag prevents the goal clearing.
*Syntax: '''''Boolean'''''}}

===$do not set override when assigning form-on-wing:===
{{Table250|
*Normally, any form-on-wing goal, regardless of how it is assigned, is given a <tt>Goal_override</tt> flag. This causes its goal to be evaluated as the top priority goal, regardless of its actual priority or any other goal's priority. This flag prevents <tt>Goal_override</tt> from being assigned, causing form-on-wing to follow the normal goal prioritization logic.
*Syntax: '''''Boolean'''''}}

===$purge player-issued form-on-wing after subsequent order:===
{{Table250|
*Causes any form-on-wing goal issued by the player (i.e. via the HUD communications system) to be removed from a ship's goal list (even if it is not the current goal) when the ship is given another goal of any priority. This flag can be useful for mods which configure form-on-wing goals to use the same execution and prioritization logic as normal goals. Since form-on-wing goals are typically temporary, regardless of their priority, this flag enforces that temporary nature. By using this flag, mission designers can ensure that mission-directed AI goal logic is followed regardless of form-on-wing status.
*Syntax: '''''Boolean'''''}}

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

Game settings.tbl

2025-10-07T15:58:14Z

Wookieejedi: add generic debris flag

{{SCP_table}}
{{TableVersionGit|2025-02-10|642111676012bc6696f4024c40296a6c20b3b958}}
{{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

If the version targeted in [[game_settings.tbl#$Target_Version:|target version]] is equal to or later than these listed, the following options are enabled by default:
{{Table220|
*[[game_settings.tbl#$Fixed_Turret_Collisions:|Fixed Turret Collisions]]
*[[game_settings.tbl#$Fixed_Missile_Detonation:|Fixed Missile Detonation]]
*[[game_settings.tbl#$Shockwaves_Damage_All_Object_Types_Once:|Shockwaves Damage All Object Types Once]]
*[[game_settings.tbl#$AI_use_framerate_independent_turning:|AI use framerate independent turning]]
*[[game_settings.tbl#$Use_host_orientation_for_set-camera-facing:|Use host orientation for set-camera-facing]]
}}
{{Table230|
*[[game_settings.tbl#$Shockwaves_Inherit_Parent_Weapon_Damage_Type:|Shockwaves Inherit Parent Weapon Damage Type]]
*[[game_settings.tbl#$Fixed_Chaining_To_Repeating_Events:|Fixed Chaining To Repeating Events]]
}}
{{Table240|
*[[game_settings.tbl#$Calculate_subsystem_hitpoints_after_parsing:|Calculate subsystem hitpoints after parsing]]}}

==#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'''''
}}
{{Table250|
It is now possible to display the mod title on its own. Previously, the mod version was also required.
}}

===$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'''''
}}
{{Table250|
It is now possible to display the mod version on its own. Previously, the mod title was also required.
}}

===$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'''''}}

===$Splash screens:===
{{Table232|
Defines a list of splash screens that FSO can display upon game startup. The actual image displayed is chosen at random from the applicable entries. Entries with exact aspect ratio matches will be prioritized first, followed by aspect ratio ranged matches, followed by entries without an aspect ratio specified.}}

====+Bitmap:====
{{table232|
The name of the bitmap to use as a splash screen. Extension will be removed if included.
*Syntax: '''''+Bitmap: String'''''}}

====+Aspect Ratio:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio matches the specified number within +/- 0.01.
*Syntax: '''''+Aspect Ratio: Float'''''}}

====+Aspect Ratio Min:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at least the specified number.
*Syntax: '''''+Aspect Ratio Min: Float'''''}}

====+Aspect Ratio Max:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at most the specified number.
*Syntax: '''''+Aspect Ratio Max: Float'''''}}

===$Splash fade in time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade in.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Splash fade out time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade out.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Center splash logo:===
{{Table232|
Sets whether the splash logo will be displayed in the middle of the screen. If this is false (the default), it will be displayed at the top-left.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Disable FSO Internal Loadout Restoration System:===
{{Table234|
When the player configures the ships and weapons of the wings in the loadout screen, FSO will remember these settings and attempt to apply them again if the player quits the mission and comes back to it later. FSO will only remember the most recent mission's loadout, so it will not attempt to restore the loadout if the player loads a different mission. It will also not attempt this if the mission's ''$Modified:'' date has changed. This flag can be used to prevent FSO from attempting restoration even if it normally would.
*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'''''
}}

===$HUD drop shadows enabled by default:===
{{Table232|
If this flag is active, certain elements displayed on the HUD (all text, the main targeting reticle, and the background of the ETS gauges) will have a "drop shadow" effect. Note that whether or not the flag is active, the player can set this using the "Toggle HUD Drop Shadows" control.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Unify scanning behavior:===
{{Table242|
*Unifies scanning behavior between subsystem, regular, and cargo allowing missions to use all scan types in all situations.
*Also allows changing the "Cargo:" text line in a mission by adding "$Cargo Title: STRING" after the "$Cargo 1:" or "$Cargo 2:" lines in the mission file. FRED UI support not yet added for $Cargo Title so you have to do it manually.
*When this flag is enabled, all ships, no matter the ship class, will react the same way to the cargo-related or scanning-related ship flags:
**They are not scannable by default
**Setting the "scannable" flag makes them scannable, and scanning the subsystem will reveal the cargo
**A new flag available with alter-ship-flag, "no-scanned-cargo", changes the behavior to scanned/unscanned instead of revealing the cargo
**The "toggle-subsystem-scanning" flag must be set to swap full-ship scanning mode into subsystem scanning mode and works for all ship types
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Don't show callsigns in the escort list:===
{{Table242|
By default, callsigns are shown in the escort list using the same format as in the target box. If this flag is active, callsigns will not be displayed.
*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'''''

===$Fixed Chaining To Repeating Events:===
{{Table230|When set, this makes event chaining to repeated events work as designed - that is, the chained event will only be evaluated after the chain delay. If the repeating event's interval is shorter than the chain delay, then the delay countdown will continually be restarted until all repetitions have completed. Without this flag, FSO will emulate retail behavior which, due to a bug, allowed chained events to be evaluated immediately after a repeating event is first evaluated.

NOTE: Although the name does not reflect it, the same issue affects repeating events that are evaluated by <tt>is-event-true-delay</tt> and <tt>is-event-false-delay</tt>. Without this flag, FSO will emulate retail behavior which causes these SEXP operators to ignore any delay when evaluating repeated events. With this flag, the delay will be measured from when the final repeat iteration occurs.
*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)'''''}}

===$HUD-set-coords base resolution:===
{{Table232|The hud-set-coords SEXP has always used exact pixels, without regard for the current screen resolution. This setting enables a similar scaling mechanism as ''$Show-subtitle base resolution:''.
*Syntax: '''''(Integer, Integer)'''''
*Default Value: '''''(-1, -1)'''''}}

===$$Always Show Directive Value Count:===
{{Table250|
*If this setting is enabled, Directive-as-Value values in Directives will always show the number. By default this is disabled, and only values > 1 are shown.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

==#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'''''}}

===$EMP Pain Flash Factor:===
{{Table224|
Determines the intensity of the flash when the player is hit by an EMP blast or weapon.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$EMP Pain Flash Color:===
{{Table224|
Determines the RGB color value of the flash when the player is hit by an EMP blast or weapon.
*Syntax: Color, (red, green, blue) respectively, integer value from 0 to 255
*Default Value: '''''(255, 255, 127)'''''}}

===$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)
}}

===$EMP Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)
}}

===$Damage Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)'''''}}

===$Shadow Disable Techroom:===
{{Table224|
Disables shadows on ships in the techroom.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Cockpit:===
{{Table224|
Disables shadows on the player cockpit in mission.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Weapons:===
{{Table224|
Disables shadows on weapons in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Ships:===
{{Table224|
Disables shadows on ships in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Show Ship Casts Shadow:===
{{Table224|
When cockpit shadows are enabled, enabling this setting will cause the players ship model shown with "show ship" to cast shadow onto the cockpit.
*Syntax: '''''Boolean'''''
}}

===$Ship Model And Cockpit Share Coordinate Space:===
{{Table224|
When having the "show ship" flag enabled and cockpit models for a ship, this flag should be on if the cockpits can fit into the actual geometry of the ship model. Disable this flag if this is not the case and the cockpit needs to be rendered on top of the ship regardless of actual coordinates. If this can be enabled, the external show ship model can be rendered using deferred rendering.
*Syntax: '''''Boolean'''''
}}

===$Show Ship enabled only if Cockpits enabled:===
{{Table250|
Enabling this setting will only use the 'show-ship' flag if cockpits are enabled. Useful if your ship uses both 'show-ship' and cockpits that exist within the 'show-ship' space, and you want to allow players to toggle off cockpits. Note, 'show-ship' always only appears if in first-person view.
*Syntax: '''''Boolean'''''
}}

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

===$Do Not Render Lasers Below Length:===
{{Table250|
*Specifies the smallest length that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Do Not Render Lasers Below Radius:===
{{Table250|
*Specifies the smallest radius that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Thruster Easing Value:===
{{Table220|
*Smooths out the behavior of maneuvering thruster flares the higher above 0 it is.
*This is the exponential time constant for the visual flare length to reach it's true length.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

===$SCPUI attempts to load hires animations:===
{{Table230|
*Prevents SCPUI from trying to load anims prefixed with "2_"
*Syntax: '''''Boolean'''''
*Default Value: true}}

{{Table230|
===$Max draw distance:===
===$Min draw distance:===
*These values do more than just cutoff the visuals at certain distances, and they must be adjusted carefully to ensure unintentional rendering artifacts are not introduced.
*The rendering engine has limited amount of 'depth resolution', the degree to which it can tell a certain polygon is closer or farther away than another. When two polygons are too close, they will Z-fight, picking arbitrarily which is closer. It is the span between the min and max draw distance that determines how well the engine can determine depth, if they are too far from one another, the Z-fighting will become more common as it has to spread its resolution over a wider range. If they are close, Z-fighting will be lessened at the cost of a smaller range of distance able to be rendered.
*Syntax: '''''Float''''', meters
*Default Values: 10,000,000,000 and 1, respectively
}}

{{Table232|
===$Randomize particle rotation:===
*Particle bitmaps are typically screen-aligned; the upper portion of the bitmap will always be mapped to the upper portion of the particle, from the point of view of the camera. Enabling this option makes ''all'' particles have a random 'tilt' in an arbitrary direction when created.
*Syntax: '''''Boolean'''''
*Default Value: false
}}

===$Disable shield effects:===
{{Table250|
*Specifies if FSO attempts to use the shield mesh impact effects. Enabling this flag will prevent the game from preforming any shield mesh effect code, which can be useful if a mod does not use those shield mesh effects.
*Syntax: '''''Boolean'''''
*Default Value: false}}

===$Disable all non-custom generic debris:===
{{Table250|
*Provides one simple control to turn off all non-custom generic debris (the tiny debris shards that are typically spawned when a ship/subsystem explodes). Note, generic debris that is manually specified in the ships table will still be spawned, this is only for turning off non-custom debris.
*Syntax: '''''Boolean'''''
*Default Value: false}}

==#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'''''}}

===$Use weapon class impact sounds for hits to player:===
{{Table224|
Allows weapons that hit the player to play their specific impact sounds, not the hard-coded default sounds.
*Syntax: '''''Boolean'''''
}}

===$Play thruster sounds for the player:===
{{Table232|
If the player's ship has thruster sounds defined, this will ensure they are played like normal, since they are typically suppressed.
*Syntax: '''''Boolean'''''
}}

===$Unify minimum engine sound:===
{{Table250|
Allows $Minimum Engine Volume in ships.tbl to work for all ship classes. By default, that value only triggers for non-huge ships.
*Syntax: '''''Boolean'''''
}}

===$Disabled or disrupted engines are silent:===
{{Table250|
If set, engines will not play their engine noise if the ship is disabled or a disrupted (such as disruptions caused by an active EMP effect or a weapon with the "electronics" flag).
*Syntax: '''''Boolean'''''
}}

==#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'''''}}

===$Add Message Head Ani Files:===
{{table224|
FRED will append each +Head entry listed below to the head ani selection list in the Event Editor.}}

====+Head:====
{{table224|
The head ani filename to add. Extensions will be stripped if included.
NOTE: Pay attention to file names or anis with a,b, c variation not display in-game (unless called directly). Proper name seems to be Head-xxxNa, Head-xxxNb, with N being some number and XXX being whatever you want. Needs further testing and confirmation
*Syntax: '''''+Head: String'''''}}

===$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'''''}}

===$FRED Briefing window resolution:===
{{table224|
The width and height of the briefing window in FRED. Defaults to 888x371. Note that changing this only affects FRED and can cause a mismatch to the ingame briefing view which defaults to 888x371 (or 555x232 for 640 base res).
*Syntax: '''''integer, integer'''''
*Default Value: '''''888,371'''''}}

===$Ignore Music Files In Music Player:===
{{table232|Music files in this section will not be added to FRED's built-in music player.}}
====+File:====
{{table232|Specifies a file
*Syntax: '''''string'''''}}

===$FRED spacemouse nonlinearities:===
{{table232|
Allows setting custom nonlinearities and scaling for controlling FRED with a spacemouse.
}}
====+Sideways exponent:====
{{table232|
The exponent for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Sideways scale:====
{{table232|The multiplier for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards exponent:====
{{table232|The exponent for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards scale:====
{{table232|The multiplier for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards exponent:====
{{table232|The exponent for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards scale:====
{{table232|The multiplier for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch exponent:====
{{table232|The exponent for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch scale:====
{{table232|The multiplier for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank exponent:====
{{table232|The exponent for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank scale:====
{{table232|The multiplier for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading exponent:====
{{table232|The exponent for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading scale:====
{{table232|The multiplier for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}

===$Skybox internal depth consistency:===
{{table250|If enabled, this will allow skyboxes that use submodels to render the submodels with proper Z-sorting if the 'No Z-Buffer' check box is set to on in FRED. In other words, parts of the skybox closer to the origin point will render in front of sections further away, as might be expected. This flag is enabled by default for FSO version 25.0 onwards
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

==#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. This fixes missile impacts to submodels whose center lies outside the geometry of the submodel. In other words, without this flag, a missile might detonate in the middle of the "bowl" of a concave submodel; with this flag, the missile will travel to the other side of the submodel before it detonates.
*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'''''

===$Use 3d ship select:===
{{Table224|
*Whether or not to use 3D models for ship select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d ship icons:===
{{Table224|
*Whether or not to use 3D models for ships in ship/weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d weapon select:===
{{Table224|
*Whether or not to use 3D models for weapon select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d weapon icons:===
{{Table224|
*Whether or not to use 3D models for weapons in weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d overhead ship:===
{{Table224|
*Whether or not to use 3D models for ship overhead view instead of a bitmap in weapon select
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Default overhead ship style:===
{{Table224|
*This specifies which style of overhead view to use if 3d overhead view is active
*Syntax: '''''String'''''
*Possible options are "ROTATE" or "TOPVIEW"}}

===$Always refresh selected weapon when viewing loadout:===
{{Table232|
*When set to true, this always refreshes the weapon shown in view box on the right side of the screen when opening the weapon loadout view. This ensures the viewed weapon is one that can actually be on the selected ship when first clicking on the weapon loadout screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$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|
*Mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. By default is now ON, and can be accessed by going to the Options menu and pressing F3.
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

===$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'''''}}

===$Apply HUD shudder to chase view:===
{{Table232|
*Applies hud shudder (afterburner and engine wash) also to chase view. Does not override the command line toggle.
*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'''''}}

===$Lead indicator behavior:===
{{Table224|
Changes how Lead Indicators behave when multiple weapon banks are linked and in range.
When set to default, if you have linked weapons, only the indicator for the one with the farthest range will be drawn.
When set to multiple, a lead indicator is drawn for all primary weapons in range when you have them linked.
When set to average, a single lead indicator is drawn in the average of the position where each of them would usually be drawn.
*Syntax: '''''String'''''
** Valid options are '''''default''''', '''''multiple''''' and '''''average'''''
*Default Value: '''''default'''''
}}

===$Use distant firepoint for all turrets:===
{{Table224|
*Causes the game to use firepoint-based target leading calculations for all turrets. This is useful if all or most turrets in a given mod has firepoints that are distant from their center-point.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Enable discord rich presence:===
{{Table224|
*Enables or disables the built-in Discord game-status reporting.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Always hide hidden ships in hotkey list:===
{{Table224|
*Whether or not to always hide ships with HIDDEN hotkey (set in FRED), even in the in-mission hotkey menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Allow automatically assigning personas:===
{{Table232|
*Whether or not the game will automatically assign personas to ships that have no persona set.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Countermeasures use capacity:===
{{Table232|
*Whether or not Countermeasures use tabled capacity.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Calculate subsystem hitpoints after parsing:===
{{Table234|
*Causes subsystem hitpoints to be calculated after all ships.tbl and -shp.tbm files have been parsed. This allows subsystem percentages to correctly reflect the final hull value rather than the first hull value encountered.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix scripted velocity:===
{{Table242|
*If this setting is enabled, object velocity set via script will wholly determine the change in position for that frame, ignoring ''all'' other in-engine concerns. Otherwise, the game engine will likely overwrite/ignore any changes, depending on when the changes were made in the frame.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Preload briefing icon models:===
{{Table250|
*If set, this forces preloading of models used for briefing icons. This only loads models used for icons that haven't already been loaded for the mission. This is useful for SCPUI's where hovering over an icon shows the model without having to click on it and the stutter when it loads models not used in mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Behavior for pressing Escape key in options menu:===
{{Table250|
*If set to 'save', the escape key for the HUD and Options screen saves options when leaving those screens (ie it does the same thing as pressing Ctrl-Enter/Accept). By default (or if set to 'default') the Escape key will not save any changed values when exiting those screens.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Disable intro cutscene:===
{{Table250|
*If set, this disables loading of any cutscenes as the game starts that might play before the player reaches the pilot select screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Show locked status for scramble missions:===
{{Table250|
*If set, scramble mission will show a text line right below the words 'Weapons Loadout' that states "Ships/Weapons Locked" (XSTR 749), thus the player can easily see their loadouts are locked and they do not have to check the loaoout buttons on every mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable expensive turret target check:===
{{Table250|
*If set, this value speeds up turret target checking. By default, turret target acquisition was spending a lot of time doing a raycast, the result of which was barely used at all. If we don't need the target normal, all it does is get a target point slightly more accurate, but in practice it really isn't noticeable at all whether the target point of the turret is actually on the surface of the ship, or maybe on the other side of the ship.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Threshold below which shield skips damage:===
{{Table250|
*By default, FSO logic dictates that shields collisions and any related sound or visuals related to shields are skipped if the shields are under 10%. This value allows modders to customize the value, though the value must be between 0.0 and 1.0.
*Syntax: '''''Float'''''
*Default Value: '''''0.1'''''}}

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

Subsystem

2025-10-07T15:53:06Z

Wookieejedi: add new generic debris flag

{{Fileversion|7119}}

The Options listed in this article should entered into the '''$Subsystem''' section of the [[Ships.tbl]]. Multiple Subsystems may be defined.

*All subsystems a ship can have must be defined in ship's model file (.pof).
*See [[Subobject_and_subsystem_properties|Subobject and subsystem properties]] for information about what subsystems the game has defined meaning for.

{{Table3610|
*[[Animation_Code|Animation Code]] can be applied to the subsystems that consist of submodels, like multi-part turrets.
{{Table220|
'''DEPRECATED''': Unless setting initial orientation of multipart turrets, consider using the [[Animation.tbl]] in combination with [[Ships.tbl#.24Animations:|$Animations:]]
}}
}}

==$Subsystem:==
*The name of the subsystem as defined in .pof file, % of ship's total hitpoints the subsystem has and rotation time (360 degrees) for multi-part turrets. Note: Assigning zero to the %-hitpoint entry causes the subsystem to be without hitpoints, like fighterbays on some capital ships.
*Syntax: '''''String''''', '''''Float''''', '''''Float''''', name of the subsystem followed by the subsystem hitpoints as % of ships hitpoints and seconds per 360 degree turn. Subsystem name must be the same as described in model file (.pof).
{{Table3610|
*Entries can be left empty in which case game uses default values}}
**Example: communications, 5, 0.0

===$Alt Subsystem Name:===
{{Table3610|
*Defines the alternate name for the subsystem. This name is shown for example in the targeting window when subsystem is targeted.
*Syntax: '''''String'''''}}
{{Table3611|
*Option to use pipe character '<nowiki>|</nowiki>' to force line breaks into the alt subsystem name}}

===$Alt Damage Popup Subsystem Name:===
{{Table3611|
*Defines the alternate name for the subsystem when it is displayed on the '''damaged systems''' popup.
*Syntax: '''''String'''''}}

===$Armor Type:===
{{Table3610|
* '''REQUIRES ADDITIONAL TABLE'''. Defines armor type used for the subsystem. If subsystem armor type is not defined ships armor type is used instead.
* Syntax: '''''String''''', as defined in [[armor.tbl]]}}

===$Default PBanks:===
*Defines default primary weapon for the turret
*Syntax: ( '''''"String"''''' )
**Example: ( ''"Subach HL-7"'' )

===$PBank Capacity:===
{{Table3610|
*Defines ammunition capacity of turrets ballistic primary weapon.
*Syntax: ( '''''Integer''''' )}}

===$Default SBanks:===
*Defines default secondary weapon for the turret
*Syntax: ( '''''"String"''''' )

===$SBank Capacity:===
*Defines ammunition capacity of turrets secondary weapon.
*Syntax: ( '''''Integer''''' )

===$Engine Wash:===
*All engines may use information concerning the engine wash. Engine washes are usually used only with larger vessels.
*Syntax: '''''String''''', name as defined in Engine Wash section in [[ships.tbl]]
**Example: ''Default1000''

===$AliveSnd:===
{{Table3610|
*Specifies a sound to play from the subsystem while it is not destroyed.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$DeadSnd:===
{{Table3610|
*Specifies a sound to play from the subsystem while it is destroyed.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$RotationSnd:===
{{Table3613|
*Can be used to define a sound that is played when this subsystem rotates.
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Turret Base RotationSnd:===
{{Table3611|
*Defines the sound which is played when the turrets base rotates
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Turret Gun RotationSnd:===
{{Table3611|
*Defines the sound which is played when the turrets guns change their elevation
*Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]}}

===$Turret BaseSnd Volume:===
{{Table3611|
*Defines the multiplier for the sound volume for turret base rotations
*Syntax: '''''Float'''''}}

===$Turret GunSnd Volume:===
{{Table3611|
*Defines the multiplier for the sound volume for turret guns change their elevation
*Syntax: '''''Float'''''}}

===$AWACS:===
*Sets this subsystem's effective AWACS range. (AWACS reveals stealthed ships, cuts through nebula fog.)
*Syntax: intensity, '''''Float''''', and radius, '''''Float''''', - intensity is an ignored but required field. - radius is the maximum range of the AWACS.

===$Scan time:===
{{Table220|
*Scan time for this subsystem. If this is not set, the scan time for the ship is used for the subsystem
*Syntax: '''''Integer''''' in milliseconds
}}

===$Maximum Barrel Elevation:===
{{Table3611|
*Defines the maximum barrel elevation for the turret gun object of a multipart turret.
*Basically 'inverse FOV'.
*Syntax: '''''Integer''''', from 0 to 90}}

===$Turret Base FOV:===
{{Table3611|
*Defines the FOV of the turret base of a multipart turret, possibly restricting how far it can traverse left and right.
*Syntax: '''''Integer''''', from 0 to 359}}

===$Turret Barrel FOV:===
{{Table224|
*Defines the overall FOV of the turret, overriding any FOV defined in the POF.
*Syntax: '''''Integer''''', from 0 to 359}}

===$Turret Reset Delay:===
{{Table3611|
*Defines the time after losing the target before the turret begins to reset itself
*Syntax: '''''Integer''''', in milliseconds}}

===$Turret Optimum Range:===
{{Table3611|
*Defines the optimum range for the turret
*Syntax: '''''Float'''''}}

===$Turret Direction Preference:===
{{Table3611|
*Defines the turrets preference to keep targeting targets based how far the turret should turn instead of nearest target
*The higher the value the higher the preference to keep targeting targets close to previous targets direction
*Syntax: '''''Integer''''', from 0 to 100, 0 disables the preference setup}}

===$Target Priority:===
{{Table3611|
*Defines the target priorities, and their order for the turret
*Syntax: '''''String list'''''}}

===$Max Turrets per Bomb:===
{{Table3613|
*Limits the number of turrets that can be targeting the same bomb.
*When this is set, when this turret tries to target a bomb, it will check to see how many turrets are already targeting it and only choose it as a target if there are less than this number.
*This allows control over the default behavior, where every turret will fire at the leading bomb.
*Syntax: '''''Integer'''''}}

===$Max Turrets per Target:===
{{Table3613|
*Limits the number of turrets that can be targeting the same target.
*'''ONLY AFFECTS SMALL TARGETS''' such as fighters and bombers. This limit does '''NOT''' apply vs large ships.
*When this is set, when this turret tries to target a ship, it will check to see how many turrets are already targeting it and only choose it as a target if there are less than this number.
*This helps turrets spread their efforts out among multiple targets.
*Syntax: '''''Integer'''''}}

===$ROF:===
{{Table3613|
*Defines the modifier applied to the turret rate of fire (ROF).

====+Use firingpoints====
*Modifies (multiplies) the rate of fire by the number of firingpoints the turret has.

====+Multiplier:====
*Checked only if ''+Use firingpoints'' has not been defined
*If set to larger than 0 the value acts as multiplier
*If set to 1.0 the feature is disabled
*If set to equal to or smaller than 0 it as if ''+Use firingpoints'' option would have been enabled
*Syntax: '''''Float'''''}}

===$Flags:===
{{Table3610|
*Can be used to sets additional subsystem related properties
*Syntax: ( '''''"String" "String"''''' )
*List of available flags:

===="untargetable"====
*Subsystem cannot be targeted

===="carry no damage"====
*Damage caused to the subsystem will not carry over to the parent ship

===="use multiple guns"====
*Enables the turret to fire all equipped weapons, picking a not-in-use firing point at each trigger. Not to be confused with 'Salvo mode'.

===="fire down normals"====
*Forces the turret to fire along the turret normals - regardless of the swarm setting.

===="check hull"====
*Forces the firing turret to check against the parent model if valid line of sight exists between the firingpoint and the target.}}

{{Table3611|
===="fixed firingpoints"====
*Forces the firing turret to retain the firingpoints of their weapons: if the turret has multiple banks, the first bank will only fire from the first firepoint, the second bank only from the second firepoint, and so on. Maximum number of weapons is the same as maximum number of weapons in turret (3 primary, 4 secondary)

===="salvo mode"====
*Forces the firing turret to use only the first weapon defined for it but fires it simultaneously from all the firing points. Not to be confused with 'use multiple guns'

===="no subsystem targeting"====
*Prevents the firing turret from targeting targets subsystems - instead forces the turret to fire randomly at the targets hull.

===="fire on target"====
*Prevents the turret from firing unless the turret barrels (firingpoints) and targets are aligned.

===="reset when idle"====
*Forces the turret to reset to its initial position if it has no targets.

===="carry shockwave"====
*Forces the turret to carry damage caused by shockwaves to the hull regardless of other flags.}}

{{Table3613|
===="allow landing"====
*Defines the subsystem as something on which player can attempt to land on

===="target requires fov"====
*Prevents turret from accidentally selecting target out of it field of view (fov) when acquiring targets

===="fov edge checks"====
*The turret will more eagerly acquire targets as long as a sufficient portion of the target is within its fov.

===="no replace"====
*Tells game not to use the replacement submodel (-destroyed) when the subsystem loses all of it's hitpoints.

===="no live debris"====
*Prevents the subsystem from releasing live debris pieces when destroyed

===="ignore if dead"====
*When subsystem has been destroyed prevents homing weapons from attempting to hit the now destroyed submodel and instead tells them to home on the main hull of the target

===="allow vanishing"====
*Allow subsystem to be destroyed from the ship without sound or graphical effects

===="damage as hull"====
*Treats subsystem as if it were hull when applying damage.

===="starts locked"====
*Turret starts locked and won't shoot until you use a turret-free or turret-free-all SEXP on it.

===="no aggregate"====
*Freespace keeps track of a ships overall functionality (such as if a ship is sensorless, disarmed or disabled) via a total hitpoint count of the associated subsystems. For example if a ship has three engines with 100HP each, the 'engines' count will be at 300HP. Shooting at any of the subsystems with the keyword 'engine' in them will decrement this total, and when it is at 0 then the ship becomes disabled.
*This flag tells FS to ignore the associated subsystem and not count it towards those totals. For example, if a ship had three 100HP engines with one set to 'no aggregate' then the 'engines' count will be 200HP. Shooting the 'no aggregate' engine will not decrement the 'engines' count, and so in other words the status of this engine is irrelevant to whether or not the ship is disabled. In the same way when applied to a turret, the turret's status is irrelevant to whether the ship is disarmed or not.

===="wait for animation"====
*When this flag is active, a turret will only fire after any associated subsystem animations (such as a turret hatch opening) have played out.

===="play fire sound for player"====
*If this turret is on a player ship, play its associated sounds.

===="only target if can fire"====
*Do additional checks to make sure that a turret which cannot fire at its target releases that target.
}}

{{Table3615|
===="no disappear"====
*If this subsystem is a physical subsystem, it won't disappear nor switch to the -destroyed model when destroyed.

===="collide submodel"====
*If this subsystem is a physical subsystem, it will only take damage from hits which impact the submodel. By default damage is taken from all hits within the submodel's radius*2. Does not affect area damage such as shockwaves.

===="allow destroyed rotation"====
*Allows a rotating subobject to continue to rotate even when it has been destroyed
}}

{{Table373|
===="turret use ammo"====
*If the subsystem is a turret, it will use ammo.
**Note: If the turret does not have ammo, it will not fire. Remember that the maximum ammo a turret can hold is the Capacity of the Bank divided by the Cargo Size of the weapon.

===="autorepair if disabled"====
*Allows the subsystem to repair itself even if disabled (normally, disabled subsystems do not repair themselves)

===="don't autorepair if disabled"====
*Inverse of "autorepair if disabled": excludes this subsystem from autorepair if the ship class [[Ships.tbl#.22repair_disabled_subsystems.22|"repair disabled subsystems"]] flag is set

===="share fire direction"====
*If this subsystem is a turret, whenever the turret fires it will make all of the firing points shoot their weapon in the same direction instead of at the same point or set of points on a target.
}}

{{Table381|
===="no damage spew"====
*If this subsystem is hit then there will be no damage spew particles emitted.

===="no impact debris"====
*If this subsystem is hit then no impact debris will be generated.
}}

{{Table250|
===="disable all generic impact debris"====
*Newer name for "no impact debris"--turns off the tiny debris shards that are typically spawned when something impacts a subsystem.
}}

{{Table220|
===="hide turret from loadout stats"====
*This subsystem is not counted as a turret in the auto-generated "+Turrets:" line in the statistics summary window of the ship loadout editor.
}}

{{Table222|
===="turret has distant firepoint"====
*Turret barrel is very long and should be taken into account when aiming (rather than calculating the aim from the turret center)
}}

{{Table242|
===="override submodel impact"====
*If a weapon impacted a submodel, but this subsystem is within range, this subsystem takes priority in the hit sequence rather than the submodel. This allows case-by-case exceptions to the [[Game_settings.tbl#.24Damage_Impacted_Subsystem_First:|$Damage Impacted Subsystem First:]] mod flag.
}}

===[[Animation Code]]===
{{Table3610|
*Option for animating the submodels
{{Table220|
'''DEPRECATED''': Unless setting initial orientation of multipart turrets, consider using the [[Animation.tbl]] in combination with [[Ships.tbl#.24Animations:|$Animations:]]
}}
}}

===$On Beam Warmdown:===
{{Table212|
Specifies an [[Action System|action system]] program set to be executed when a beam attached to this subsystem is starting its warmdown sequence.
}}

==Case Specific Entries==

===Turret===
*All turrets require information concerning the weapon mounted to the turret. The entry can be either '''$Default PBanks''' for turret primaries (including beams) or '''$Default SBanks''' for turret secondaries
{{Table3610|
*[[Animation_Code#Setting_Turret_Angle|Animation Code]] can be used with multi-part turrets.
*Multiple defined weapons will all fire but the targeting is handled by the first weapon in the list. '''Multiple beams are not possible'''. All weapons alternate between the firingpoints of the turret so turrets do not need to have more than one weapon defined no matter how many barrels or firingpoints they have.}}

====Example====

<pre>
$Subsystem: turret01, 1.0, 1.0
$Default PBanks: ( "Terran Turret" )
</pre>

===Engine===

====Example====

<pre>
$Subsystem: engine01, 5.0, 0.0
$Engine Wash: Default1000
</pre>

[[Category:Tables]]

Ships.tbl

2025-10-07T15:50:05Z

Wookieejedi: add new generic debris flags

{{TableVersionGit|2024-11-13|d6b444c}}
{{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

See the article [[Subsystem]] for ship table information that is specific to subsystems.

==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]] 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 ships.tbl or in earlier parsed *-shp.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.}}

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

===+Use Ship as Template:===
{{Table232|
*Creates a copy of the specified ship to use as a base for this ship.
*'''''Caution!''''' This is highly dependent on the order the tables are loaded. If the ship used as a template is modified using <tt>+nocreate</tt>, the tabled changes will only be applied to the newly created ship if they are loaded ''before'' <tt>+Use Ship as Template</tt>. Any <tt>+nocreate</tt> changes ''after'' <tt>+Use Ship as Template</tt> will not have any effect on the newly created ship class. Thus, proper templates should be preferred if possible.
*Cannot be used in conjunction with <tt>+Use Template</tt>.
*Syntax: '''''String''''', name of the ship class to use as a template}}

===$Alt Name:===
{{Table3613|
*Alternative $Name: for the ship. Used to rename ships without breaking missions.
*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 Animations:===
{{Table230|
*Allows specifying animations that only run on the cockpit model of a ship
*See [[#$Animations:|$Animations]]
*Syntax: '''''( "String" "String" )''''', names of the animations for this ship, as defined in the Animation.tbl
**Example: ( "wingflap" "docksequence" )
}}

===$Driven Cockpit Animations:===
{{Table242|
*See [[Animation_Drivers#Parsing (+Driver Set:)]]
*Driven cockpit animations '''are not''' compatible with $Cockpit Animations! If you need cockpit animations without drivers, create a driver set that has no driver and list all animations in it's +Affected Animations:
}}

===$Cockpit Moveables:===
{{Table230|
*Allows specifying moveables that only run on the cockpit model of a ship
*See [[#$Moveables:|$Moveables]]
*Syntax: '''''( "String" "String" )''''', names of the moveable animations for this ship, as defined in the Animation.tbl
**Example: ( "wingflap" "docksequence" )
}}

===+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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be used on weapon impact,
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Impact Spew'' is not a valid option!
}}

===$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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be used for the smoke of a weapon impact,
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Damage Spew'' is not a valid option!
*Note that the scaling applied by ''$Damage Spew'' '''is not''' applied to''$Damage Spew Effect:'' automatically. If desired, it has to be manually added using ''$Particle Source Curve:'' within the particle definition
}}

===$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.
{{Table250|
====+Rotation Magnitude Maximum:====
What the maximum resulting rotational velocity can be from a ship collision in degrees per second. Setting this to a value such as 360 (degrees/second) properly allows mods to have ships spin out if they have collision while not spinning out at wild speeds that look immersion breaking. If negative, then there is no limit to rotational velocity from collisions. Default is -1.0.
}}
====+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.
}}

===$Gravity Const:===
{{Table224|
**If the mission has gravity, this is the multiplier applied to acceleration from gravity on the ship.
**Note that due to the exponential damping from $Damp, the acceleration from gravity will eventually even out with $Damp and result in a constant velocity in the direction of gravity.
**Syntax: '''''Float'''''}}

===$Dying Gravity Const:===
{{Table224|
**Same as above, but while ths ship is dying/in death roll.
**The aforementioned exponential damp is still in effect during this time, but it is weaker.
**Syntax: '''''Float'''''
**Default: The same as $Gravity Const:}}

===$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'''''}}
{{Table250|
*'''+Hitpoints Radius Multiplier:'''
**Defines the hitpoints multiplier. By default this is -1 and thus disabled, but if set to a value greater than or equal 0, the debris hitpoints will be multiplied by this value and the radius of the debris submodel. Useful for making debris have hitpoints that vary based on size of the debris piece.
**Syntax: '''''Float'''''
}}
{{Table3611|
*'''+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}}
{{Table224|
*'''+Debris Gravity Const:'''
**If the mission has gravity, this is the multiplier applied to acceleration from gravity on the ship's debris.
**Syntax: '''''Float'''''
**Default: The same as $Dying Gravity Const}}
{{Table232|
*'''+Debris Density:'''
**Same as [[Ship.tbl#$Density:|Density]] but only applied to the ship's debris.
**Syntax: '''''Float'''''
**Default: 1.0}}
{{Table202|
*'''+Ambient Sound:'''
**The sound played in the vicinity of debris.}}
{{Table212|
*'''+Generic Debris POF file:'''
**The filename of the ship's generic debris, by default debris01.pof.
**Big or huge ships do not normally have generic debris, but if this is specified for them, they will generate generic debris on explosion.
**These debris peices are temporary, noncollideable and are generated in randomizard positions and orientations.
**Syntax: '''''String'''
*'''+Generic Debris Spew Num:'''
**How many generic debris fragments to generate when the ship explodes.
**If this is a big or huge ship, this is the number of generic debris fragments to generate for every individual propagating explosion.
**Syntax: '''''Integer'''
**Default: ''20''}}

===$Density:===
*Multiplies the mass and moment of inertia of the relevant ship.
*Ships with a high mass and moment of inertia will be moved/rotated by collisions and impacts less strongly.
*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), but only for the player, the AI will act as though it is still 0.
*Syntax: '''''Float'''''
*Defaults to 0.}}

====+Glide Accel Mult:====
{{Table3611|
*Defines the acceleration multiplier for the gliding mode.
**If > 0, sets a fixed acceleration rate in glide mode: ships will accelerate at their tabled maximum velocity along the given axis, interpreted in m/s^2, multiplied by ''+Glide Accel Mult:''.
**If set to 0, impossible to accelerate while in glide mode.
**If negative, enables glide speed ramping: acceleration in glide mode ramps using the same constants as in normal flight. Note, however, that glide acceleration ignores the ship's ''$Damp:'' value, so glide acceleration will always be faster than in normal flight; and if the damping constant is significantly larger than the acceleration constant along a given axis, this difference will become very pronounced.
*Syntax: '''''Float'''''
*Default: ''0''}}
{{Table3610|
*Entry exists as a dummy entry which doesn't 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}}

===+Primary Bank Autoaim FOV:===
{{Table232|
*Defines the autoaim for the primary bank.
*Can be listed once for each existing bank on the ship.
*Syntax: '''''Float'''''}}

===$Aims at Flight Cursor:===
{{Table242|
*Enables flight cursor-style flying for the ship, and causes the ship to fire in the direction of the cursor.
*'''Note:''' Only works for players! AI may need a system like autoaim to mimic it.
*Syntax: '''''Boolean'''''}}

===+Extent:===
{{Table242|
*Required if the above is true.
*How many degrees away from the center the player is allowed to shoot, using the flight cursor.
*Syntax: '''''Float''''', degrees}}

===$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|
:*''[Fireball Unique ID]'' - Uses the default mechanics but replaces the portal effect with the identified fireball.
*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}}

===$Supercap warpin physics:===
{{Table234|
*Specifies whether this ship should use supercap deceleration when arriving, similar to the Colossus. Can also disable supercap deceleration on a ship that normally has it.
*Syntax: '''''Boolean'''''}}

===$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|
:*''[Fireball Unique ID]'' - Uses the default mechanics but replaces the portal effect with the identified fireball.
*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}}

===$Supercap warpout physics:===
{{Table234|
*Specifies whether this ship should use special physics when departing, as a complement to $Supercap warpin physics. Currently has no effect.
*Syntax: '''''Boolean'''''}}

===$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 has many smaller explosions while in its death-roll. Also determines whether the ship splits in two or not unless explicitly set below.
*Syntax: '''''Boolean''''', yes or no

===$Expl Splits Ship:===
{{Table202|
*Whether the ship splits in two and slowly explodes outward towards its front and back, or just immediately explodes into debris.
*Syntax: '''''Boolean''''', yes or no, defaults to the value of '$Expl Propagates:' above}}

===$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 Rotation Multiplier:===
{{Table202|
*Multiplies the strength of the rotation imparted by death-rolling.
*Syntax: '''''Float'''''
**Default: 1.0}}

===$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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be used when a ship is splitting apart,
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Ship Splitting Particles'' is not a valid option!
}}

===$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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be used when a knossos type object is dying.
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Alternate Death Particles'' is not a valid option!
}}

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

===$Debris Flame Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be added to debris spawned from this ship.
*Syntax: '''String''', the particle effect name
}}

===$Vaporize Percent Chance:===
{{Table3611|
*Allows ships to sometimes explode instantly instead of going through a death roll first. Overrides the same flag in [[objecttypes.tbl]]. Note that this option is misleadingly named; "vaporization" usually refers to a ship exploding into tiny debris shards rather than hull chunks.
*Syntax: '''''Float''''', percent chance of instant explosion, 0 to 100}}
{{Table240|In version 24.0 and later, '''$Skip Death Roll Percent Chance:''' can be used as a more accurate alternative.}}

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

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

===$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 its 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 its 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 its 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)''
*Note: This requires the [[Weapons.tbl#.24External_Model_File:|$External_Model_File entry to be defined in weapons.tbl]]. Weapons without external models will revert to the standard behaviour.
*Behavior is as follows:
**If your bank carries fewer or as many missiles as the number of gunpoints on your bank, you will have exactly as many external model shown as you have missiles left in your bank (going in the order of gunpoints defined in the POF). External models will disappear when missiles are fired.
**If your bank carries more missiles than you have gunpoints in your bank, then external models will "recoil" (to simulate a reloading animation) every time you fire, and will disappear based on the % of missile left in the bank. Example: you have 2 gunpoints and 4 missiles, the first external model will disappear after you fire the second missile.
**If your weapon uses the [[Weapons.tbl#.22external_model_launcher.22|"external_model_launcher" flag]], then the model will be displayed on all gunpoints and will not recoil nor disappear when fired.}}

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

===$Allowed Firing Patterns for Dynamic Primary Linking:===
{{Table250|
*If the ship has dynamic primary linking enabled, defines the list of firing patterns which the player may cycle through using the appropriate control.
*This is optional. If not set, the only firing pattern available will be CYCLE FORWARD.
*Takes a list of patterns. The options are:
**'''CYCLE FORWARD''': Fires '''$Shots''' shots from the first '''$Shots''' gunpoints (starting at gunpoint 0), then from the next '''$Shots''' gunpoints, and so on.
**'''CYCLE REVERSE''': Same behavior as CYCLE FORWARD, but begins at the highest-numbered gunpoint and works downward.
**'''RANDOM EXHAUSTIVE''': Fires '''$Shots''' shots at a time from randomly-selected gunpoints until each gunpoint has been fired once, and then starts over.
**'''RANDOM NONREPEATING''': Fires '''$Shots''' randomly-selected gunpoints at a time, but never fires the same gunpoint twice in a row (unless forced to because $Shots is equal to more than half the number of gunpoints).
**'''RANDOM REPEATING''': Fires '''$Shots''' randomly-selected gunpoints at a time. No restrictions.
*Syntax: '''String list''', for example, ("CYCLE FORWARD", "CYCLE REVERSE")}}

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

====+Max Shield Impact Effect Radius:====
{{Table250|
*Caps the size of the visual effect displayed on the shield mesh from impacts.
*Syntax: '''''Float''''', meters}}

===$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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be triggered when this ship's shields are hit.
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Shield Impact Explosion'' is not a valid option!
}}

===$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/afterburner energy regeneration is disabled. Checked via code inspection 2014-12-29
{{Table250|
If the current AI profile has the '''$ETS uses ship class power output:''' flag enabled, this will act as a multiplier for ETS energy. For example, a ship with a power output of 2 will recharge its afterburner twice as fast as a ship with the same stats but a power output of 1.
}}
*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:}}

===+Shield Regen Hit Delay:===
{{Table214|
*Specifies a time delay after being hit by a weapon before the shield may begin regenerating again.
*Syntax: '''''Float''''', seconds}}

===$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:}}

===$Shield to Weapon Transfer Quantity:===
{{Table202|
*The fraction of ''maximum'' shield capacity to use when making direct shield -> weapon energy transfers.
*Syntax: '''''Float'''''
**Default: ''0.2''
*'''Note:''' default direct transfers have a large and poorly-appreciated impact on ETS balancing. If you care about balancing your ship's weapon and shield recharge rates you are advised to set this to 0.}}

===$Shield to Weapon Transfer Efficiency:===
{{Table202|*The fraction of the transferred shield energy that will actually end up in the weapon capacitor.
*Syntax: '''''Float'''''
**Default: ''1.0''
*Note that the amount deposited will be absolute, not relative. For instance, for a ship with 100 weapon energy and 200 shields and default quantity and efficiency, a shield->weapon transfer will deduct 40 shield energy and add 40 weapon energy. It is entirely possible for efficiency to be more than 1.0.
*Unless transfer efficiency is tuned to account for the different charge rates for weapons and shields, direct transfers will tend to make the ETS unbalanced in the hands of an experienced player, as in retail.}}

===$Shield to Weapon Transfer Speed:===
{{Table202|*The rate at which transferred energy will move into the weapon capacitor,
*Syntax: '''''Float'''''
**Default:''0.04''
*When energy is transferred it is instantly deducted from shields, but it must 'trickle' into the weapon capacitor at a fixed fraction per second. This acts as a second bonus recharge on top of whatever the ETS produces.}}

===$Weapon to Shield Transfer Quantity:===

===$Weapon to Shield Transfer Efficiency:===

===$Weapon to Shield Transfer Speed:===

{{Table202|As above, but with the transfer direction reversed.}}

===$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''''', percentage of hitpoints repaired per second}}

===$Hull Self Repair Maximum:===
{{Table220|
*Maximum percentage of total hull strength that the hull will self-repair to.
*Syntax: '''''Float''''', percentage of hull hitpoints}}

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

===$Subsystem Self Repair Maximum:===
{{Table220|
*Maximum percentage of total subsystem strength that subsystems will self-repair to.
*Syntax: '''''Float''''', percentage of subsystems hitpoints}}

===$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
====+Aburn Minimum Start Fuel:====
{{Table202|
*Minimum afterburner fuel the ship must have before allowed to afterburn.
*Syntax: '''''Float''''', fuel}}
====+Aburn Minimum Fuel to Burn:====
{{Table202|
*Forces the ship to afterburn until at least this much fuel is used, or it runs out of fuel.
*Syntax: '''''Float''''', fuel}}
====+Aburn Cooldown Time:====
{{Table202|
*How much time must have elapsed since the last afterburn finished to allow afterburning again.
*Syntax: '''''Float''''', seconds}}
{{Table3610|
====$Trails:====
*Allows afterburner trails to be used
=====+Bitmap:=====
*Texture used to draw the afterburner trail
*Syntax: '''''String''''', filename
{{Table212|
=====+Bitmap Stretch:=====
*Multiplies how far the bitmap is stretched over each trail segment.
*Syntax: '''''Float'''''
**Default:''1''}}
=====+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'''''
{{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
*Smaller numbers below 1 cause the trail to fade away very slowly at first, and then suddenly at the end. Larger numbers above 1 cause it to fade away quickly at first, and then slow down for most of its life.
*Syntax: '''''Float''''', positive
**Default:''1''}}
=====+Life:=====
*How long the trail will last
*Syntax: '''''Float''''', seconds}}
{{Table202|
=====+Spread:=====
*Causes the trail points to diffuse and drift apart at this speed over time.
*Syntax: '''''Float''''', meters per second}}
{{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
}}

===$Scanning time multiplier:===
{{Table220|
*A factor to apply to scan time when this ship is doing the scanning
*Syntax: '''''Float'''''
}}

===$Scanning range multiplier:===
{{Table220|
*A factor to apply to scan distance when this ship is doing the scanning
*Syntax: '''''Float'''''
}}

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

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

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

===$Chase View Offset:===
{{Table214|
*Specifies a custom camera position when the ship is being viewed in the chase camera.
*Syntax: '''''Vector''''', three '''floats''', x, y and z values respectively in meters}}

===$Chase View Rigidity:===
{{Table214|
*Specifies how 'rigidly' the camera adheres to the 'rest' position of the chase view camera when doing maneuvers or changing speed.
*Syntax: '''''Float'''''
** Defaults to 5.0.}}

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

{{Table214|
===$Wingmen Gauge Dot Override:===
*(Optional) Defines an animation to use for the dots in the wingmen status gauge. Overrides 'Dot Filename:' under the '+Wingman Status:' entry in [[Hud_gauges.tbl#.2BWingman_Status:|Hud_gauges.tbl]]
*Must be an animation with two frames.
*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:===
{{Table250|
*Defines the alternative particle thruster.
*'''$Thruster Effect:''' OR '''$Afterburner Effect:'''
*Specifies the [[Particle Effects|particle effect]] which will be used for thruster and afterburner effects.
*Any number of thruster and afterburner particles can be specified here.
*Afterburner particles require at least 1 existing particle thruster entry.
*These can be used both instead and in combination with the legacy particles (''$Thruster Particle Bitmap:'', ''$Afterburner Particle Bitmap:'') described below
*Syntax: '''String''', the particle effect name
}}

{{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
{{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
*Smaller numbers below 1 cause the trail to fade away very slowly at first, and then suddenly at the end. Larger numbers above 1 cause it to fade away quickly at first, and then slow down for most of its life.
*Syntax: '''''Float''''', positive
**Default:''1''}}
====+Max Life:====
*How long the contrail remains
*Syntax: '''''Float'''''', seconds
{{Table202|
=====+Spread:=====
*Causes the trail points to diffuse and drift apart at this speed over time.
*Syntax: '''''Float''''', meters per second}}
====+Spew Time:====
*Time in milliseconds to create new trail points, lower means less 'jagged' trails.
*Syntax: '''''Integer'''''
====+Bitmap:====
*The image to use for the contrail.
*Syntax: '''''String''''', filename
{{Table212|
====+Bitmap Stretch:====
*Multiplies how far the bitmap is stretched over each trail segment.
*Syntax: '''''Float'''''
**Default:''1''}}
{{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:'''
**Optional
**Rather than adding a new entry, an existing entry can be overriden by using its index in the list (starting at 0).
**Syntax: '''''Integer'''''
*'''+Used For:'''
{{Table230|
**This field may be omitted, and the activation of the thruster will be calculated automatically based on its position and direction.
}}
**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
***THESE NAMES MAY BE MISLEADING FOR YOU.
***'Roll left' and 'Roll right' are actually yaw, activated when the ship rotates around its top-bottom axis.
***'Bank left' and 'Bank right' are actually roll, activated when the ship rotates around its front-back axis.
{{Table232|
***'Yaw left' and 'Yaw right' are now valid strings for this field. 'Roll left' and 'Roll right' are still recognized for compatibility.
}}
**Syntax: '''''("String" "String")'''''
**Allows one or more strings, does not have a set limit.
*'''+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]]}}

===$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")'''
}}

===$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'''''}}

===$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'''
{{Table220|
====+arrival rvec:====
*When using this path to arrive via fighterbay, the arriving 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 arrive via fighterbay.
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively}}
====+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.
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively
====+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'''''
}}
}}

===$Passive Lightning Arcs:===
{{Table220|
*Creates a 'lightning arc' between two points on the ship's hull, like when the ship is EMP'd or damaged, but naturally and fixed to two points on the ship.
*This section can be repeated.
*'''All subfields are required'''
====+Submodel 1:====
*The name of the name of the submodel the first end is connected to.
*Note that the arc will ''not'' move along with a submodel while it is animating (but it will be initially created in the correct position). In the case of an animating submodel, it is recommended to use very short durations/frequencies.
**Syntax: '''''String'''''
====+Position 1:====
*The position on the ship this end is attached to, relative to the origin of the entire ship.
**Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively
====+Submodel 2:====
====+Position 2:====
*The same as the above for the other end of the arc.
====+Duration:====
*How long the arc persists while active.
**Syntax: '''''Float''''', seconds
====+Frequency:====
*How long after creating an arc it should wait before creating another.
**Syntax: '''''Float''''', seconds}}
{{Table224|
====+Primary color 1:====
*The first primary color of the arc, chosen randomly between color 1 and 2.
**Syntax: three '''''Integers''''', 0-255
====+Primary color 2:====
*The second primary color of the arc, chosen randomly between color 1 and 2.
**Syntax: three '''''Integers''''', 0-255
====+Secondary color:====
*The secondary color of the arc. This is the inner color, usually close to white.
**Syntax: three '''''Integers''''', 0-255}}

===$Animations:===
{{Table220|
*The new way of specifying triggered animations, replacing the subsystem-based definitions
*See [[Animation.tbl]]
*Syntax: '''''( "String" "String" )''''', names of the animations for this ship, as defined in the Animation.tbl
**Example: ( "wingflap" "docksequence" )
}}

===$Driven Animations:===
{{Table240|
*See [[Animation_Drivers#Parsing (+Driver Set:)]]
*Driven animations '''are not''' compatible with $Animations! If you need animations without drivers, create a driver set that has no driver and list all animations in it's +Affected Animations:
}}

===$Animation Moveables:===
{{Table220|
*Like $Animations: but for specific in-mission adjustable moveable animations.
*See [[Animation.tbl]]
*Syntax: '''''( "String" "String" )''''', names of the moveable animations for this ship, as defined in the Animation.tbl
**Example: ( "wingflap" "docksequence" )
}}

===$Custom data:===
{{Table220|
Defines a set of custom data that for this ship 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 Ship 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. }}

===$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" or "support"====
*Defines the ship as repair and rearm vessel and sets AI behaviour accordingly

===="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" or "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" or "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" or "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" or "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-targetable, and not on radar.}}

===="no type"====
*Does not enable any type-specific behavior

----
==="ship copy"===
*Defines the ship as a copy of another ship. For ships which have this flag and are a hash-variant of another ship (like '''SF Dragon''' and '''SF Dragon#2 (Weakened)'''), the ship copy will be listed on the scoreboard as the original ship. This only affects the listing, not the score.

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

==="don't collide invisible" or "dont collide invisible"===
*Defines invisible textures as non-collidable (For example, a hangar entrance)

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

==="no_fred"===
*Ship will not appear in any of the FRED dropdown lists for ship classes.

==="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 modelled 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 shield icon from the model itself}}

===no weapon damage scaling"===
{{Table3610|
*Weapons that impact this ship will not by scaled according to 'big damage' or supercap rules}}

==="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}}

==="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 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}}

==="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:|$Model_Point_Shield_Controls:]] to allow the shield augmentation controls to be used.}}

==="repair disabled subsystems"===
{{Table371|
Destroyed subsystems will auto-repair, provided [[Ships.tbl#.24Subsystem_Repair_Rate:|$Subsystem Repair Rate:]] is greater than 0. }}

==="don't bank when turning"===
{{Table210|All maneuvers by this ship class will have the same effect as the equivalent flag in <tt>ship-maneuver</tt>: the ship will not bank when changing its heading.}}

==="don't clamp max velocity"===
{{Table210|All maneuvers by this ship class will have the same effect as the equivalent flag in <tt>ship-maneuver</tt>: the ship's velocity will not be limited by its tabled max velocity, provided the max velocity is greater than 0. Use with caution!}}

==="instantaneous acceleration"===
{{Table210|All maneuvers by this ship class will have the same effect as the equivalent flag in <tt>ship-maneuver</tt>: whenever the ship decides to change speed, it will instantaneously reach its desired speed.}}

==="large ship deathroll"===
{{Table210|
Causes the ship to deathroll like a fighter, even if it is big or huge (which is disabled by default). Note that their deathroll intensity is scaled down by being larger size. }}

==="no impact debris"===
{{Table212|
Turns off the tiny debris shards that are typically spawned when something impacts a ship. }}

==="disable all generic impact debris"===
{{Table250|
Newer name for "no impact debris"--turns off the tiny debris shards that are typically spawned when something impacts a ship. }}

==="disable all generic explosion debris"===
{{Table250|
Turns off the tiny debris shards that are typically spawned when a ship explodes. }}

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

Ai profiles.tbl

2025-09-16T20:10:06Z

Wookieejedi: add +combat collision avoidance for fightercraft includes target:

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===+combat collision avoidance for fightercraft includes target:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance to include the target ship it might be attacking. Enabling this can help reduce collisions when attacking if ship speeds in your mod are higher than retail.
*Syntax: '''''Boolean'''''}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use ai-form-on-wing-new:===
{{Table250|
*Will cause form-on-wing orders issued by the hud squadmsg menu (i.e. player orders) to be the 'new' variant that does not clear other goals assigned to the same ship/wing.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

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

2025-09-03T02:58:31Z

Wookieejedi: add $attack-any idle circle distance:

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use ai-form-on-wing-new:===
{{Table250|
*Will cause form-on-wing orders issued by the hud squadmsg menu (i.e. player orders) to be the 'new' variant that does not clear other goals assigned to the same ship/wing.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$attack-any idle circle distance:===
{{Table250|
*Ships with the 'attack-any' order will circle around an invisible point if there are no hostile present. This value sets the radius of how big of a circle to fly around while the AI waits for new hostiles to arrive.
**Syntax: '''''Float''''' (defaults to 100.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

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

Game settings.tbl

2025-08-13T12:22:32Z

Wookieejedi: add $Skybox internal depth consistency:

{{SCP_table}}
{{TableVersionGit|2025-02-10|642111676012bc6696f4024c40296a6c20b3b958}}
{{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

If the version targeted in [[game_settings.tbl#$Target_Version:|target version]] is equal to or later than these listed, the following options are enabled by default:
{{Table220|
*[[game_settings.tbl#$Fixed_Turret_Collisions:|Fixed Turret Collisions]]
*[[game_settings.tbl#$Fixed_Missile_Detonation:|Fixed Missile Detonation]]
*[[game_settings.tbl#$Shockwaves_Damage_All_Object_Types_Once:|Shockwaves Damage All Object Types Once]]
*[[game_settings.tbl#$AI_use_framerate_independent_turning:|AI use framerate independent turning]]
*[[game_settings.tbl#$Use_host_orientation_for_set-camera-facing:|Use host orientation for set-camera-facing]]
}}
{{Table230|
*[[game_settings.tbl#$Shockwaves_Inherit_Parent_Weapon_Damage_Type:|Shockwaves Inherit Parent Weapon Damage Type]]
*[[game_settings.tbl#$Fixed_Chaining_To_Repeating_Events:|Fixed Chaining To Repeating Events]]
}}
{{Table240|
*[[game_settings.tbl#$Calculate_subsystem_hitpoints_after_parsing:|Calculate subsystem hitpoints after parsing]]}}

==#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'''''
}}
{{Table250|
It is now possible to display the mod title on its own. Previously, the mod version was also required.
}}

===$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'''''
}}
{{Table250|
It is now possible to display the mod version on its own. Previously, the mod title was also required.
}}

===$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'''''}}

===$Splash screens:===
{{Table232|
Defines a list of splash screens that FSO can display upon game startup. The actual image displayed is chosen at random from the applicable entries. Entries with exact aspect ratio matches will be prioritized first, followed by aspect ratio ranged matches, followed by entries without an aspect ratio specified.}}

====+Bitmap:====
{{table232|
The name of the bitmap to use as a splash screen. Extension will be removed if included.
*Syntax: '''''+Bitmap: String'''''}}

====+Aspect Ratio:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio matches the specified number within +/- 0.01.
*Syntax: '''''+Aspect Ratio: Float'''''}}

====+Aspect Ratio Min:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at least the specified number.
*Syntax: '''''+Aspect Ratio Min: Float'''''}}

====+Aspect Ratio Max:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at most the specified number.
*Syntax: '''''+Aspect Ratio Max: Float'''''}}

===$Splash fade in time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade in.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Splash fade out time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade out.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Center splash logo:===
{{Table232|
Sets whether the splash logo will be displayed in the middle of the screen. If this is false (the default), it will be displayed at the top-left.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Disable FSO Internal Loadout Restoration System:===
{{Table234|
When the player configures the ships and weapons of the wings in the loadout screen, FSO will remember these settings and attempt to apply them again if the player quits the mission and comes back to it later. FSO will only remember the most recent mission's loadout, so it will not attempt to restore the loadout if the player loads a different mission. It will also not attempt this if the mission's ''$Modified:'' date has changed. This flag can be used to prevent FSO from attempting restoration even if it normally would.
*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'''''
}}

===$HUD drop shadows enabled by default:===
{{Table232|
If this flag is active, certain elements displayed on the HUD (all text, the main targeting reticle, and the background of the ETS gauges) will have a "drop shadow" effect. Note that whether or not the flag is active, the player can set this using the "Toggle HUD Drop Shadows" control.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Unify scanning behavior:===
{{Table242|
*Unifies scanning behavior between subsystem, regular, and cargo allowing missions to use all scan types in all situations.
*Also allows changing the "Cargo:" text line in a mission by adding "$Cargo Title: STRING" after the "$Cargo 1:" or "$Cargo 2:" lines in the mission file. FRED UI support not yet added for $Cargo Title so you have to do it manually.
*When this flag is enabled, all ships, no matter the ship class, will react the same way to the cargo-related or scanning-related ship flags:
**They are not scannable by default
**Setting the "scannable" flag makes them scannable, and scanning the subsystem will reveal the cargo
**A new flag available with alter-ship-flag, "no-scanned-cargo", changes the behavior to scanned/unscanned instead of revealing the cargo
**The "toggle-subsystem-scanning" flag must be set to swap full-ship scanning mode into subsystem scanning mode and works for all ship types
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Don't show callsigns in the escort list:===
{{Table242|
By default, callsigns are shown in the escort list using the same format as in the target box. If this flag is active, callsigns will not be displayed.
*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'''''

===$Fixed Chaining To Repeating Events:===
{{Table230|When set, this makes event chaining to repeated events work as designed - that is, the chained event will only be evaluated after the chain delay. If the repeating event's interval is shorter than the chain delay, then the delay countdown will continually be restarted until all repetitions have completed. Without this flag, FSO will emulate retail behavior which, due to a bug, allowed chained events to be evaluated immediately after a repeating event is first evaluated.

NOTE: Although the name does not reflect it, the same issue affects repeating events that are evaluated by <tt>is-event-true-delay</tt> and <tt>is-event-false-delay</tt>. Without this flag, FSO will emulate retail behavior which causes these SEXP operators to ignore any delay when evaluating repeated events. With this flag, the delay will be measured from when the final repeat iteration occurs.
*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)'''''}}

===$HUD-set-coords base resolution:===
{{Table232|The hud-set-coords SEXP has always used exact pixels, without regard for the current screen resolution. This setting enables a similar scaling mechanism as ''$Show-subtitle base resolution:''.
*Syntax: '''''(Integer, Integer)'''''
*Default Value: '''''(-1, -1)'''''}}

===$$Always Show Directive Value Count:===
{{Table250|
*If this setting is enabled, Directive-as-Value values in Directives will always show the number. By default this is disabled, and only values > 1 are shown.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

==#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'''''}}

===$EMP Pain Flash Factor:===
{{Table224|
Determines the intensity of the flash when the player is hit by an EMP blast or weapon.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$EMP Pain Flash Color:===
{{Table224|
Determines the RGB color value of the flash when the player is hit by an EMP blast or weapon.
*Syntax: Color, (red, green, blue) respectively, integer value from 0 to 255
*Default Value: '''''(255, 255, 127)'''''}}

===$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)
}}

===$EMP Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)
}}

===$Damage Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)'''''}}

===$Shadow Disable Techroom:===
{{Table224|
Disables shadows on ships in the techroom.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Cockpit:===
{{Table224|
Disables shadows on the player cockpit in mission.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Weapons:===
{{Table224|
Disables shadows on weapons in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Ships:===
{{Table224|
Disables shadows on ships in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Show Ship Casts Shadow:===
{{Table224|
When cockpit shadows are enabled, enabling this setting will cause the players ship model shown with "show ship" to cast shadow onto the cockpit.
*Syntax: '''''Boolean'''''
}}

===$Ship Model And Cockpit Share Coordinate Space:===
{{Table224|
When having the "show ship" flag enabled and cockpit models for a ship, this flag should be on if the cockpits can fit into the actual geometry of the ship model. Disable this flag if this is not the case and the cockpit needs to be rendered on top of the ship regardless of actual coordinates. If this can be enabled, the external show ship model can be rendered using deferred rendering.
*Syntax: '''''Boolean'''''
}}

===$Show Ship enabled only if Cockpits enabled:===
{{Table250|
Enabling this setting will only use the 'show-ship' flag if cockpits are enabled. Useful if your ship uses both 'show-ship' and cockpits that exist within the 'show-ship' space, and you want to allow players to toggle off cockpits. Note, 'show-ship' always only appears if in first-person view.
*Syntax: '''''Boolean'''''
}}

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

===$Do Not Render Lasers Below Length:===
{{Table250|
*Specifies the smallest length that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Do Not Render Lasers Below Radius:===
{{Table250|
*Specifies the smallest radius that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Thruster Easing Value:===
{{Table220|
*Smooths out the behavior of maneuvering thruster flares the higher above 0 it is.
*This is the exponential time constant for the visual flare length to reach it's true length.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

===$SCPUI attempts to load hires animations:===
{{Table230|
*Prevents SCPUI from trying to load anims prefixed with "2_"
*Syntax: '''''Boolean'''''
*Default Value: true}}

{{Table230|
===$Max draw distance:===
===$Min draw distance:===
*These values do more than just cutoff the visuals at certain distances, and they must be adjusted carefully to ensure unintentional rendering artifacts are not introduced.
*The rendering engine has limited amount of 'depth resolution', the degree to which it can tell a certain polygon is closer or farther away than another. When two polygons are too close, they will Z-fight, picking arbitrarily which is closer. It is the span between the min and max draw distance that determines how well the engine can determine depth, if they are too far from one another, the Z-fighting will become more common as it has to spread its resolution over a wider range. If they are close, Z-fighting will be lessened at the cost of a smaller range of distance able to be rendered.
*Syntax: '''''Float''''', meters
*Default Values: 10,000,000,000 and 1, respectively
}}

{{Table232|
===$Randomize particle rotation:===
*Particle bitmaps are typically screen-aligned; the upper portion of the bitmap will always be mapped to the upper portion of the particle, from the point of view of the camera. Enabling this option makes ''all'' particles have a random 'tilt' in an arbitrary direction when created.
*Syntax: '''''Boolean'''''
*Default Value: false
}}

===$Disable shield effects:===
{{Table250|
*Specifies if FSO attempts to use the shield mesh impact effects. Enabling this flag will prevent the game from preforming any shield mesh effect code, which can be useful if a mod does not use those shield mesh effects.
*Syntax: '''''Boolean'''''
*Default Value: false}}

==#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'''''}}

===$Use weapon class impact sounds for hits to player:===
{{Table224|
Allows weapons that hit the player to play their specific impact sounds, not the hard-coded default sounds.
*Syntax: '''''Boolean'''''
}}

===$Play thruster sounds for the player:===
{{Table232|
If the player's ship has thruster sounds defined, this will ensure they are played like normal, since they are typically suppressed.
*Syntax: '''''Boolean'''''
}}

===$Unify minimum engine sound:===
{{Table250|
Allows $Minimum Engine Volume in ships.tbl to work for all ship classes. By default, that value only triggers for non-huge ships.
*Syntax: '''''Boolean'''''
}}

===$Disabled or disrupted engines are silent:===
{{Table250|
If set, engines will not play their engine noise if the ship is disabled or a disrupted (such as disruptions caused by an active EMP effect or a weapon with the "electronics" flag).
*Syntax: '''''Boolean'''''
}}

==#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'''''}}

===$Add Message Head Ani Files:===
{{table224|
FRED will append each +Head entry listed below to the head ani selection list in the Event Editor.}}

====+Head:====
{{table224|
The head ani filename to add. Extensions will be stripped if included.
NOTE: Pay attention to file names or anis with a,b, c variation not display in-game (unless called directly). Proper name seems to be Head-xxxNa, Head-xxxNb, with N being some number and XXX being whatever you want. Needs further testing and confirmation
*Syntax: '''''+Head: String'''''}}

===$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'''''}}

===$FRED Briefing window resolution:===
{{table224|
The width and height of the briefing window in FRED. Defaults to 888x371. Note that changing this only affects FRED and can cause a mismatch to the ingame briefing view which defaults to 888x371 (or 555x232 for 640 base res).
*Syntax: '''''integer, integer'''''
*Default Value: '''''888,371'''''}}

===$Ignore Music Files In Music Player:===
{{table232|Music files in this section will not be added to FRED's built-in music player.}}
====+File:====
{{table232|Specifies a file
*Syntax: '''''string'''''}}

===$FRED spacemouse nonlinearities:===
{{table232|
Allows setting custom nonlinearities and scaling for controlling FRED with a spacemouse.
}}
====+Sideways exponent:====
{{table232|
The exponent for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Sideways scale:====
{{table232|The multiplier for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards exponent:====
{{table232|The exponent for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards scale:====
{{table232|The multiplier for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards exponent:====
{{table232|The exponent for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards scale:====
{{table232|The multiplier for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch exponent:====
{{table232|The exponent for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch scale:====
{{table232|The multiplier for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank exponent:====
{{table232|The exponent for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank scale:====
{{table232|The multiplier for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading exponent:====
{{table232|The exponent for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading scale:====
{{table232|The multiplier for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}

===$Skybox internal depth consistency:===
{{table250|If enabled, this will allow skyboxes that use submodels to render the submodels with proper Z-sorting if the 'No Z-Buffer' check box is set to on in FRED. In other words, parts of the skybox closer to the origin point will render in front of sections further away, as might be expected. This flag is enabled by default for FSO versions >= 25.0.}}
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

==#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. This fixes missile impacts to submodels whose center lies outside the geometry of the submodel. In other words, without this flag, a missile might detonate in the middle of the "bowl" of a concave submodel; with this flag, the missile will travel to the other side of the submodel before it detonates.
*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'''''

===$Use 3d ship select:===
{{Table224|
*Whether or not to use 3D models for ship select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d ship icons:===
{{Table224|
*Whether or not to use 3D models for ships in ship/weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d weapon select:===
{{Table224|
*Whether or not to use 3D models for weapon select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d weapon icons:===
{{Table224|
*Whether or not to use 3D models for weapons in weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d overhead ship:===
{{Table224|
*Whether or not to use 3D models for ship overhead view instead of a bitmap in weapon select
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Default overhead ship style:===
{{Table224|
*This specifies which style of overhead view to use if 3d overhead view is active
*Syntax: '''''String'''''
*Possible options are "ROTATE" or "TOPVIEW"}}

===$Always refresh selected weapon when viewing loadout:===
{{Table232|
*When set to true, this always refreshes the weapon shown in view box on the right side of the screen when opening the weapon loadout view. This ensures the viewed weapon is one that can actually be on the selected ship when first clicking on the weapon loadout screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$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|
*Mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. By default is now ON, and can be accessed by going to the Options menu and pressing F3.
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

===$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'''''}}

===$Apply HUD shudder to chase view:===
{{Table232|
*Applies hud shudder (afterburner and engine wash) also to chase view. Does not override the command line toggle.
*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'''''}}

===$Lead indicator behavior:===
{{Table224|
Changes how Lead Indicators behave when multiple weapon banks are linked and in range.
When set to default, if you have linked weapons, only the indicator for the one with the farthest range will be drawn.
When set to multiple, a lead indicator is drawn for all primary weapons in range when you have them linked.
When set to average, a single lead indicator is drawn in the average of the position where each of them would usually be drawn.
*Syntax: '''''String'''''
** Valid options are '''''default''''', '''''multiple''''' and '''''average'''''
*Default Value: '''''default'''''
}}

===$Use distant firepoint for all turrets:===
{{Table224|
*Causes the game to use firepoint-based target leading calculations for all turrets. This is useful if all or most turrets in a given mod has firepoints that are distant from their center-point.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Enable discord rich presence:===
{{Table224|
*Enables or disables the built-in Discord game-status reporting.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Always hide hidden ships in hotkey list:===
{{Table224|
*Whether or not to always hide ships with HIDDEN hotkey (set in FRED), even in the in-mission hotkey menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Allow automatically assigning personas:===
{{Table232|
*Whether or not the game will automatically assign personas to ships that have no persona set.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Countermeasures use capacity:===
{{Table232|
*Whether or not Countermeasures use tabled capacity.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Calculate subsystem hitpoints after parsing:===
{{Table234|
*Causes subsystem hitpoints to be calculated after all ships.tbl and -shp.tbm files have been parsed. This allows subsystem percentages to correctly reflect the final hull value rather than the first hull value encountered.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix scripted velocity:===
{{Table242|
*If this setting is enabled, object velocity set via script will wholly determine the change in position for that frame, ignoring ''all'' other in-engine concerns. Otherwise, the game engine will likely overwrite/ignore any changes, depending on when the changes were made in the frame.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Preload briefing icon models:===
{{Table250|
*If set, this forces preloading of models used for briefing icons. This only loads models used for icons that haven't already been loaded for the mission. This is useful for SCPUI's where hovering over an icon shows the model without having to click on it and the stutter when it loads models not used in mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Behavior for pressing Escape key in options menu:===
{{Table250|
*If set to 'save', the escape key for the HUD and Options screen saves options when leaving those screens (ie it does the same thing as pressing Ctrl-Enter/Accept). By default (or if set to 'default') the Escape key will not save any changed values when exiting those screens.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Disable intro cutscene:===
{{Table250|
*If set, this disables loading of any cutscenes as the game starts that might play before the player reaches the pilot select screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Show locked status for scramble missions:===
{{Table250|
*If set, scramble mission will show a text line right below the words 'Weapons Loadout' that states "Ships/Weapons Locked" (XSTR 749), thus the player can easily see their loadouts are locked and they do not have to check the loaoout buttons on every mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable expensive turret target check:===
{{Table250|
*If set, this value speeds up turret target checking. By default, turret target acquisition was spending a lot of time doing a raycast, the result of which was barely used at all. If we don't need the target normal, all it does is get a target point slightly more accurate, but in practice it really isn't noticeable at all whether the target point of the turret is actually on the surface of the ship, or maybe on the other side of the ship.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Threshold below which shield skips damage:===
{{Table250|
*By default, FSO logic dictates that shields collisions and any related sound or visuals related to shields are skipped if the shields are under 10%. This value allows modders to customize the value, though the value must be between 0.0 and 1.0.
*Syntax: '''''Float'''''
*Default Value: '''''0.1'''''}}

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

Ai profiles.tbl

2025-08-05T18:33:00Z

Wookieejedi: update language on $standard strafe triggers under this speed:

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use ai-form-on-wing-new:===
{{Table250|
*Will cause form-on-wing orders issued by the hud squadmsg menu (i.e. player orders) to be the 'new' variant that does not clear other goals assigned to the same ship/wing.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher, such as 40 if you ship's max speed is 100, and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving. In other words, once a ship slows down during attacking, as soon as it drops below the tabled speed (and assuming strafe used more is turned on), it'll start to strafe instead of slowing down even more.
**Syntax: '''''Float''''' (defaults to 3.0 m/s)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

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

Ships.tbl

2025-08-02T02:36:48Z

Wookieejedi: +Rotation Magnitude Maximum:

{{TableVersionGit|2024-11-13|d6b444c}}
{{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

See the article [[Subsystem]] for ship table information that is specific to subsystems.

==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]] 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 ships.tbl or in earlier parsed *-shp.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.}}

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

===+Use Ship as Template:===
{{Table232|
*Creates a copy of the specified ship to use as a base for this ship.
*'''''Caution!''''' This is highly dependent on the order the tables are loaded. If the ship used as a template is modified using <tt>+nocreate</tt>, the tabled changes will only be applied to the newly created ship if they are loaded ''before'' <tt>+Use Ship as Template</tt>. Any <tt>+nocreate</tt> changes ''after'' <tt>+Use Ship as Template</tt> will not have any effect on the newly created ship class. Thus, proper templates should be preferred if possible.
*Cannot be used in conjunction with <tt>+Use Template</tt>.
*Syntax: '''''String''''', name of the ship class to use as a template}}

===$Alt Name:===
{{Table3613|
*Alternative $Name: for the ship. Used to rename ships without breaking missions.
*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 Animations:===
{{Table230|
*Allows specifying animations that only run on the cockpit model of a ship
*See [[#$Animations:|$Animations]]
*Syntax: '''''( "String" "String" )''''', names of the animations for this ship, as defined in the Animation.tbl
**Example: ( "wingflap" "docksequence" )
}}

===$Driven Cockpit Animations:===
{{Table242|
*See [[Animation_Drivers#Parsing (+Driver Set:)]]
*Driven cockpit animations '''are not''' compatible with $Cockpit Animations! If you need cockpit animations without drivers, create a driver set that has no driver and list all animations in it's +Affected Animations:
}}

===$Cockpit Moveables:===
{{Table230|
*Allows specifying moveables that only run on the cockpit model of a ship
*See [[#$Moveables:|$Moveables]]
*Syntax: '''''( "String" "String" )''''', names of the moveable animations for this ship, as defined in the Animation.tbl
**Example: ( "wingflap" "docksequence" )
}}

===+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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be used on weapon impact,
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Impact Spew'' is not a valid option!
}}

===$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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be used for the smoke of a weapon impact,
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Damage Spew'' is not a valid option!
*Note that the scaling applied by ''$Damage Spew'' '''is not''' applied to''$Damage Spew Effect:'' automatically. If desired, it has to be manually added using ''$Particle Source Curve:'' within the particle definition
}}

===$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.
{{Table250|
====+Rotation Magnitude Maximum:====
What the maximum resulting rotational velocity can be from a ship collision in degrees per second. Setting this to a value such as 360 (degrees/second) properly allows mods to have ships spin out if they have collision while not spinning out at wild speeds that look immersion breaking. If negative, then there is no limit to rotational velocity from collisions. Default is -1.0.
}}
====+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.
}}

===$Gravity Const:===
{{Table224|
**If the mission has gravity, this is the multiplier applied to acceleration from gravity on the ship.
**Note that due to the exponential damping from $Damp, the acceleration from gravity will eventually even out with $Damp and result in a constant velocity in the direction of gravity.
**Syntax: '''''Float'''''}}

===$Dying Gravity Const:===
{{Table224|
**Same as above, but while ths ship is dying/in death roll.
**The aforementioned exponential damp is still in effect during this time, but it is weaker.
**Syntax: '''''Float'''''
**Default: The same as $Gravity Const:}}

===$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'''''}}
{{Table250|
*'''+Hitpoints Radius Multiplier:'''
**Defines the hitpoints multiplier. By default this is -1 and thus disabled, but if set to a value greater than or equal 0, the debris hitpoints will be multiplied by this value and the radius of the debris submodel. Useful for making debris have hitpoints that vary based on size of the debris piece.
**Syntax: '''''Float'''''
}}
{{Table3611|
*'''+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}}
{{Table224|
*'''+Debris Gravity Const:'''
**If the mission has gravity, this is the multiplier applied to acceleration from gravity on the ship's debris.
**Syntax: '''''Float'''''
**Default: The same as $Dying Gravity Const}}
{{Table232|
*'''+Debris Density:'''
**Same as [[Ship.tbl#$Density:|Density]] but only applied to the ship's debris.
**Syntax: '''''Float'''''
**Default: 1.0}}
{{Table202|
*'''+Ambient Sound:'''
**The sound played in the vicinity of debris.}}
{{Table212|
*'''+Generic Debris POF file:'''
**The filename of the ship's generic debris, by default debris01.pof.
**Big or huge ships do not normally have generic debris, but if this is specified for them, they will generate generic debris on explosion.
**Syntax: '''''String'''
*'''+Generic Debris Spew Num:'''
**How many generic debris fragments to generate when the ship explodes.
**If this is a big or huge ship, this is the number of generic debris fragments to generate for every individual propagating explosion.
**Syntax: '''''Integer'''
**Default: ''20''}}

===$Density:===
*Multiplies the mass and moment of inertia of the relevant ship.
*Ships with a high mass and moment of inertia will be moved/rotated by collisions and impacts less strongly.
*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), but only for the player, the AI will act as though it is still 0.
*Syntax: '''''Float'''''
*Defaults to 0.}}

====+Glide Accel Mult:====
{{Table3611|
*Defines the acceleration multiplier for the gliding mode.
**If > 0, sets a fixed acceleration rate in glide mode: ships will accelerate at their tabled maximum velocity along the given axis, interpreted in m/s^2, multiplied by ''+Glide Accel Mult:''.
**If set to 0, impossible to accelerate while in glide mode.
**If negative, enables glide speed ramping: acceleration in glide mode ramps using the same constants as in normal flight. Note, however, that glide acceleration ignores the ship's ''$Damp:'' value, so glide acceleration will always be faster than in normal flight; and if the damping constant is significantly larger than the acceleration constant along a given axis, this difference will become very pronounced.
*Syntax: '''''Float'''''
*Default: ''0''}}
{{Table3610|
*Entry exists as a dummy entry which doesn't 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}}

===+Primary Bank Autoaim FOV:===
{{Table232|
*Defines the autoaim for the primary bank.
*Can be listed once for each existing bank on the ship.
*Syntax: '''''Float'''''}}

===$Aims at Flight Cursor:===
{{Table242|
*Enables flight cursor-style flying for the ship, and causes the ship to fire in the direction of the cursor.
*'''Note:''' Only works for players! AI may need a system like autoaim to mimic it.
*Syntax: '''''Boolean'''''}}

===+Extent:===
{{Table242|
*Required if the above is true.
*How many degrees away from the center the player is allowed to shoot, using the flight cursor.
*Syntax: '''''Float''''', degrees}}

===$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|
:*''[Fireball Unique ID]'' - Uses the default mechanics but replaces the portal effect with the identified fireball.
*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}}

===$Supercap warpin physics:===
{{Table234|
*Specifies whether this ship should use supercap deceleration when arriving, similar to the Colossus. Can also disable supercap deceleration on a ship that normally has it.
*Syntax: '''''Boolean'''''}}

===$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|
:*''[Fireball Unique ID]'' - Uses the default mechanics but replaces the portal effect with the identified fireball.
*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}}

===$Supercap warpout physics:===
{{Table234|
*Specifies whether this ship should use special physics when departing, as a complement to $Supercap warpin physics. Currently has no effect.
*Syntax: '''''Boolean'''''}}

===$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 has many smaller explosions while in its death-roll. Also determines whether the ship splits in two or not unless explicitly set below.
*Syntax: '''''Boolean''''', yes or no

===$Expl Splits Ship:===
{{Table202|
*Whether the ship splits in two and slowly explodes outward towards its front and back, or just immediately explodes into debris.
*Syntax: '''''Boolean''''', yes or no, defaults to the value of '$Expl Propagates:' above}}

===$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 Rotation Multiplier:===
{{Table202|
*Multiplies the strength of the rotation imparted by death-rolling.
*Syntax: '''''Float'''''
**Default: 1.0}}

===$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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be used when a ship is splitting apart,
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Ship Splitting Particles'' is not a valid option!
}}

===$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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be used when a knossos type object is dying.
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Alternate Death Particles'' is not a valid option!
}}

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

===$Debris Flame Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be added to debris spawned from this ship.
*Syntax: '''String''', the particle effect name
}}

===$Vaporize Percent Chance:===
{{Table3611|
*Allows ships to sometimes explode instantly instead of going through a death roll first. Overrides the same flag in [[objecttypes.tbl]]. Note that this option is misleadingly named; "vaporization" usually refers to a ship exploding into tiny debris shards rather than hull chunks.
*Syntax: '''''Float''''', percent chance of instant explosion, 0 to 100}}
{{Table240|In version 24.0 and later, '''$Skip Death Roll Percent Chance:''' can be used as a more accurate alternative.}}

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

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

===$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 its 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 its 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 its 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)''
*Note: This requires the [[Weapons.tbl#.24External_Model_File:|$External_Model_File entry to be defined in weapons.tbl]]. Weapons without external models will revert to the standard behaviour.
*Behavior is as follows:
**If your bank carries fewer or as many missiles as the number of gunpoints on your bank, you will have exactly as many external model shown as you have missiles left in your bank (going in the order of gunpoints defined in the POF). External models will disappear when missiles are fired.
**If your bank carries more missiles than you have gunpoints in your bank, then external models will "recoil" (to simulate a reloading animation) every time you fire, and will disappear based on the % of missile left in the bank. Example: you have 2 gunpoints and 4 missiles, the first external model will disappear after you fire the second missile.
**If your weapon uses the [[Weapons.tbl#.22external_model_launcher.22|"external_model_launcher" flag]], then the model will be displayed on all gunpoints and will not recoil nor disappear when fired.}}

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

===$Allowed Firing Patterns for Dynamic Primary Linking:===
{{Table250|
*If the ship has dynamic primary linking enabled, defines the list of firing patterns which the player may cycle through using the appropriate control.
*This is optional. If not set, the only firing pattern available will be CYCLE FORWARD.
*Takes a list of patterns. The options are:
**'''CYCLE FORWARD''': Fires '''$Shots''' shots from the first '''$Shots''' gunpoints (starting at gunpoint 0), then from the next '''$Shots''' gunpoints, and so on.
**'''CYCLE REVERSE''': Same behavior as CYCLE FORWARD, but begins at the highest-numbered gunpoint and works downward.
**'''RANDOM EXHAUSTIVE''': Fires '''$Shots''' shots at a time from randomly-selected gunpoints until each gunpoint has been fired once, and then starts over.
**'''RANDOM NONREPEATING''': Fires '''$Shots''' randomly-selected gunpoints at a time, but never fires the same gunpoint twice in a row (unless forced to because $Shots is equal to more than half the number of gunpoints).
**'''RANDOM REPEATING''': Fires '''$Shots''' randomly-selected gunpoints at a time. No restrictions.
*Syntax: '''String list''', for example, ("CYCLE FORWARD", "CYCLE REVERSE")}}

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

====+Max Shield Impact Effect Radius:====
{{Table250|
*Caps the size of the visual effect displayed on the shield mesh from impacts.
*Syntax: '''''Float''''', meters}}

===$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 Effect:===
{{Table250|
*Specifies the [[Particle Effects|particle effect]] which will be triggered when this ship's shields are hit.
*Syntax: '''String''', the particle effect name
*If this option is specified then ''$Shield Impact Explosion'' is not a valid option!
}}

===$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/afterburner energy regeneration is disabled. Checked via code inspection 2014-12-29
{{Table250|
If the current AI profile has the '''$ETS uses ship class power output:''' flag enabled, this will act as a multiplier for ETS energy. For example, a ship with a power output of 2 will recharge its afterburner twice as fast as a ship with the same stats but a power output of 1.
}}
*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:}}

===+Shield Regen Hit Delay:===
{{Table214|
*Specifies a time delay after being hit by a weapon before the shield may begin regenerating again.
*Syntax: '''''Float''''', seconds}}

===$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:}}

===$Shield to Weapon Transfer Quantity:===
{{Table202|
*The fraction of ''maximum'' shield capacity to use when making direct shield -> weapon energy transfers.
*Syntax: '''''Float'''''
**Default: ''0.2''
*'''Note:''' default direct transfers have a large and poorly-appreciated impact on ETS balancing. If you care about balancing your ship's weapon and shield recharge rates you are advised to set this to 0.}}

===$Shield to Weapon Transfer Efficiency:===
{{Table202|*The fraction of the transferred shield energy that will actually end up in the weapon capacitor.
*Syntax: '''''Float'''''
**Default: ''1.0''
*Note that the amount deposited will be absolute, not relative. For instance, for a ship with 100 weapon energy and 200 shields and default quantity and efficiency, a shield->weapon transfer will deduct 40 shield energy and add 40 weapon energy. It is entirely possible for efficiency to be more than 1.0.
*Unless transfer efficiency is tuned to account for the different charge rates for weapons and shields, direct transfers will tend to make the ETS unbalanced in the hands of an experienced player, as in retail.}}

===$Shield to Weapon Transfer Speed:===
{{Table202|*The rate at which transferred energy will move into the weapon capacitor,
*Syntax: '''''Float'''''
**Default:''0.04''
*When energy is transferred it is instantly deducted from shields, but it must 'trickle' into the weapon capacitor at a fixed fraction per second. This acts as a second bonus recharge on top of whatever the ETS produces.}}

===$Weapon to Shield Transfer Quantity:===

===$Weapon to Shield Transfer Efficiency:===

===$Weapon to Shield Transfer Speed:===

{{Table202|As above, but with the transfer direction reversed.}}

===$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''''', percentage of hitpoints repaired per second}}

===$Hull Self Repair Maximum:===
{{Table220|
*Maximum percentage of total hull strength that the hull will self-repair to.
*Syntax: '''''Float''''', percentage of hull hitpoints}}

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

===$Subsystem Self Repair Maximum:===
{{Table220|
*Maximum percentage of total subsystem strength that subsystems will self-repair to.
*Syntax: '''''Float''''', percentage of subsystems hitpoints}}

===$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
====+Aburn Minimum Start Fuel:====
{{Table202|
*Minimum afterburner fuel the ship must have before allowed to afterburn.
*Syntax: '''''Float''''', fuel}}
====+Aburn Minimum Fuel to Burn:====
{{Table202|
*Forces the ship to afterburn until at least this much fuel is used, or it runs out of fuel.
*Syntax: '''''Float''''', fuel}}
====+Aburn Cooldown Time:====
{{Table202|
*How much time must have elapsed since the last afterburn finished to allow afterburning again.
*Syntax: '''''Float''''', seconds}}
{{Table3610|
====$Trails:====
*Allows afterburner trails to be used
=====+Bitmap:=====
*Texture used to draw the afterburner trail
*Syntax: '''''String''''', filename
{{Table212|
=====+Bitmap Stretch:=====
*Multiplies how far the bitmap is stretched over each trail segment.
*Syntax: '''''Float'''''
**Default:''1''}}
=====+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'''''
{{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
*Smaller numbers below 1 cause the trail to fade away very slowly at first, and then suddenly at the end. Larger numbers above 1 cause it to fade away quickly at first, and then slow down for most of its life.
*Syntax: '''''Float''''', positive
**Default:''1''}}
=====+Life:=====
*How long the trail will last
*Syntax: '''''Float''''', seconds}}
{{Table202|
=====+Spread:=====
*Causes the trail points to diffuse and drift apart at this speed over time.
*Syntax: '''''Float''''', meters per second}}
{{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
}}

===$Scanning time multiplier:===
{{Table220|
*A factor to apply to scan time when this ship is doing the scanning
*Syntax: '''''Float'''''
}}

===$Scanning range multiplier:===
{{Table220|
*A factor to apply to scan distance when this ship is doing the scanning
*Syntax: '''''Float'''''
}}

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

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

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

===$Chase View Offset:===
{{Table214|
*Specifies a custom camera position when the ship is being viewed in the chase camera.
*Syntax: '''''Vector''''', three '''floats''', x, y and z values respectively in meters}}

===$Chase View Rigidity:===
{{Table214|
*Specifies how 'rigidly' the camera adheres to the 'rest' position of the chase view camera when doing maneuvers or changing speed.
*Syntax: '''''Float'''''
** Defaults to 5.0.}}

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

{{Table214|
===$Wingmen Gauge Dot Override:===
*(Optional) Defines an animation to use for the dots in the wingmen status gauge. Overrides 'Dot Filename:' under the '+Wingman Status:' entry in [[Hud_gauges.tbl#.2BWingman_Status:|Hud_gauges.tbl]]
*Must be an animation with two frames.
*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:===
{{Table250|
*Defines the alternative particle thruster.
*'''$Thruster Effect:''' OR '''$Afterburner Effect:'''
*Specifies the [[Particle Effects|particle effect]] which will be used for thruster and afterburner effects.
*Any number of thruster and afterburner particles can be specified here.
*Afterburner particles require at least 1 existing particle thruster entry.
*These can be used both instead and in combination with the legacy particles (''$Thruster Particle Bitmap:'', ''$Afterburner Particle Bitmap:'') described below
*Syntax: '''String''', the particle effect name
}}

{{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
{{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
*Smaller numbers below 1 cause the trail to fade away very slowly at first, and then suddenly at the end. Larger numbers above 1 cause it to fade away quickly at first, and then slow down for most of its life.
*Syntax: '''''Float''''', positive
**Default:''1''}}
====+Max Life:====
*How long the contrail remains
*Syntax: '''''Float'''''', seconds
{{Table202|
=====+Spread:=====
*Causes the trail points to diffuse and drift apart at this speed over time.
*Syntax: '''''Float''''', meters per second}}
====+Spew Time:====
*Time in milliseconds to create new trail points, lower means less 'jagged' trails.
*Syntax: '''''Integer'''''
====+Bitmap:====
*The image to use for the contrail.
*Syntax: '''''String''''', filename
{{Table212|
====+Bitmap Stretch:====
*Multiplies how far the bitmap is stretched over each trail segment.
*Syntax: '''''Float'''''
**Default:''1''}}
{{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:'''
**Optional
**Rather than adding a new entry, an existing entry can be overriden by using its index in the list (starting at 0).
**Syntax: '''''Integer'''''
*'''+Used For:'''
{{Table230|
**This field may be omitted, and the activation of the thruster will be calculated automatically based on its position and direction.
}}
**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
***THESE NAMES MAY BE MISLEADING FOR YOU.
***'Roll left' and 'Roll right' are actually yaw, activated when the ship rotates around its top-bottom axis.
***'Bank left' and 'Bank right' are actually roll, activated when the ship rotates around its front-back axis.
{{Table232|
***'Yaw left' and 'Yaw right' are now valid strings for this field. 'Roll left' and 'Roll right' are still recognized for compatibility.
}}
**Syntax: '''''("String" "String")'''''
**Allows one or more strings, does not have a set limit.
*'''+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]]}}

===$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")'''
}}

===$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'''''}}

===$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'''
{{Table220|
====+arrival rvec:====
*When using this path to arrive via fighterbay, the arriving 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 arrive via fighterbay.
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively}}
====+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.
*Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively
====+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'''''
}}
}}

===$Passive Lightning Arcs:===
{{Table220|
*Creates a 'lightning arc' between two points on the ship's hull, like when the ship is EMP'd or damaged, but naturally and fixed to two points on the ship.
*This section can be repeated.
*'''All subfields are required'''
====+Submodel 1:====
*The name of the name of the submodel the first end is connected to.
*Note that the arc will ''not'' move along with a submodel while it is animating (but it will be initially created in the correct position). In the case of an animating submodel, it is recommended to use very short durations/frequencies.
**Syntax: '''''String'''''
====+Position 1:====
*The position on the ship this end is attached to, relative to the origin of the entire ship.
**Syntax: '''''Vector''''', three '''floats''', x-axis, y-axis, z-axis, respectively
====+Submodel 2:====
====+Position 2:====
*The same as the above for the other end of the arc.
====+Duration:====
*How long the arc persists while active.
**Syntax: '''''Float''''', seconds
====+Frequency:====
*How long after creating an arc it should wait before creating another.
**Syntax: '''''Float''''', seconds}}
{{Table224|
====+Primary color 1:====
*The first primary color of the arc, chosen randomly between color 1 and 2.
**Syntax: three '''''Integers''''', 0-255
====+Primary color 2:====
*The second primary color of the arc, chosen randomly between color 1 and 2.
**Syntax: three '''''Integers''''', 0-255
====+Secondary color:====
*The secondary color of the arc. This is the inner color, usually close to white.
**Syntax: three '''''Integers''''', 0-255}}

===$Animations:===
{{Table220|
*The new way of specifying triggered animations, replacing the subsystem-based definitions
*See [[Animation.tbl]]
*Syntax: '''''( "String" "String" )''''', names of the animations for this ship, as defined in the Animation.tbl
**Example: ( "wingflap" "docksequence" )
}}

===$Driven Animations:===
{{Table240|
*See [[Animation_Drivers#Parsing (+Driver Set:)]]
*Driven animations '''are not''' compatible with $Animations! If you need animations without drivers, create a driver set that has no driver and list all animations in it's +Affected Animations:
}}

===$Animation Moveables:===
{{Table220|
*Like $Animations: but for specific in-mission adjustable moveable animations.
*See [[Animation.tbl]]
*Syntax: '''''( "String" "String" )''''', names of the moveable animations for this ship, as defined in the Animation.tbl
**Example: ( "wingflap" "docksequence" )
}}

===$Custom data:===
{{Table220|
Defines a set of custom data that for this ship 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 Ship 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. }}

===$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" or "support"====
*Defines the ship as repair and rearm vessel and sets AI behaviour accordingly

===="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" or "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" or "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" or "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" or "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-targetable, and not on radar.}}

===="no type"====
*Does not enable any type-specific behavior

----
==="ship copy"===
*Defines the ship as a copy of another ship. For ships which have this flag and are a hash-variant of another ship (like '''SF Dragon''' and '''SF Dragon#2 (Weakened)'''), the ship copy will be listed on the scoreboard as the original ship. This only affects the listing, not the score.

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

==="don't collide invisible" or "dont collide invisible"===
*Defines invisible textures as non-collidable (For example, a hangar entrance)

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

==="no_fred"===
*Ship will not appear in any of the FRED dropdown lists for ship classes.

==="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 modelled 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 shield icon from the model itself}}

===no weapon damage scaling"===
{{Table3610|
*Weapons that impact this ship will not by scaled according to 'big damage' or supercap rules}}

==="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}}

==="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 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}}

==="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:|$Model_Point_Shield_Controls:]] to allow the shield augmentation controls to be used.}}

==="repair disabled subsystems"===
{{Table371|
Destroyed subsystems will auto-repair, provided [[Ships.tbl#.24Subsystem_Repair_Rate:|$Subsystem Repair Rate:]] is greater than 0. }}

==="don't bank when turning"===
{{Table210|All maneuvers by this ship class will have the same effect as the equivalent flag in <tt>ship-maneuver</tt>: the ship will not bank when changing its heading.}}

==="don't clamp max velocity"===
{{Table210|All maneuvers by this ship class will have the same effect as the equivalent flag in <tt>ship-maneuver</tt>: the ship's velocity will not be limited by its tabled max velocity, provided the max velocity is greater than 0. Use with caution!}}

==="instantaneous acceleration"===
{{Table210|All maneuvers by this ship class will have the same effect as the equivalent flag in <tt>ship-maneuver</tt>: whenever the ship decides to change speed, it will instantaneously reach its desired speed.}}

==="large ship deathroll"===
{{Table210|
Causes the ship to deathroll like a fighter, even if it is big or huge (which is disabled by default). Note that their deathroll intensity is scaled down by being larger size. }}

==="no impact debris"===
{{Table212|
Turns off the tiny debris shards that are typically spawned when something impacts a ship. }}

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

2025-07-19T16:38:19Z

Wookieejedi: add new flags

{{SCP_table}}
{{TableVersionGit|2025-02-10|642111676012bc6696f4024c40296a6c20b3b958}}
{{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

If the version targeted in [[game_settings.tbl#$Target_Version:|target version]] is equal to or later than these listed, the following options are enabled by default:
{{Table220|
*[[game_settings.tbl#$Fixed_Turret_Collisions:|Fixed Turret Collisions]]
*[[game_settings.tbl#$Fixed_Missile_Detonation:|Fixed Missile Detonation]]
*[[game_settings.tbl#$Shockwaves_Damage_All_Object_Types_Once:|Shockwaves Damage All Object Types Once]]
*[[game_settings.tbl#$AI_use_framerate_independent_turning:|AI use framerate independent turning]]
*[[game_settings.tbl#$Use_host_orientation_for_set-camera-facing:|Use host orientation for set-camera-facing]]
}}
{{Table230|
*[[game_settings.tbl#$Shockwaves_Inherit_Parent_Weapon_Damage_Type:|Shockwaves Inherit Parent Weapon Damage Type]]
*[[game_settings.tbl#$Fixed_Chaining_To_Repeating_Events:|Fixed Chaining To Repeating Events]]
}}
{{Table240|
*[[game_settings.tbl#$Calculate_subsystem_hitpoints_after_parsing:|Calculate subsystem hitpoints after parsing]]}}

==#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'''''
}}
{{Table250|
It is now possible to display the mod title on its own. Previously, the mod version was also required.
}}

===$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'''''
}}
{{Table250|
It is now possible to display the mod version on its own. Previously, the mod title was also required.
}}

===$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'''''}}

===$Splash screens:===
{{Table232|
Defines a list of splash screens that FSO can display upon game startup. The actual image displayed is chosen at random from the applicable entries. Entries with exact aspect ratio matches will be prioritized first, followed by aspect ratio ranged matches, followed by entries without an aspect ratio specified.}}

====+Bitmap:====
{{table232|
The name of the bitmap to use as a splash screen. Extension will be removed if included.
*Syntax: '''''+Bitmap: String'''''}}

====+Aspect Ratio:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio matches the specified number within +/- 0.01.
*Syntax: '''''+Aspect Ratio: Float'''''}}

====+Aspect Ratio Min:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at least the specified number.
*Syntax: '''''+Aspect Ratio Min: Float'''''}}

====+Aspect Ratio Max:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at most the specified number.
*Syntax: '''''+Aspect Ratio Max: Float'''''}}

===$Splash fade in time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade in.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Splash fade out time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade out.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Center splash logo:===
{{Table232|
Sets whether the splash logo will be displayed in the middle of the screen. If this is false (the default), it will be displayed at the top-left.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Disable FSO Internal Loadout Restoration System:===
{{Table234|
When the player configures the ships and weapons of the wings in the loadout screen, FSO will remember these settings and attempt to apply them again if the player quits the mission and comes back to it later. FSO will only remember the most recent mission's loadout, so it will not attempt to restore the loadout if the player loads a different mission. It will also not attempt this if the mission's ''$Modified:'' date has changed. This flag can be used to prevent FSO from attempting restoration even if it normally would.
*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'''''
}}

===$HUD drop shadows enabled by default:===
{{Table232|
If this flag is active, certain elements displayed on the HUD (all text, the main targeting reticle, and the background of the ETS gauges) will have a "drop shadow" effect. Note that whether or not the flag is active, the player can set this using the "Toggle HUD Drop Shadows" control.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Unify scanning behavior:===
{{Table242|
*Unifies scanning behavior between subsystem, regular, and cargo allowing missions to use all scan types in all situations.
*Also allows changing the "Cargo:" text line in a mission by adding "$Cargo Title: STRING" after the "$Cargo 1:" or "$Cargo 2:" lines in the mission file. FRED UI support not yet added for $Cargo Title so you have to do it manually.
*When this flag is enabled, all ships, no matter the ship class, will react the same way to the cargo-related or scanning-related ship flags:
**They are not scannable by default
**Setting the "scannable" flag makes them scannable, and scanning the subsystem will reveal the cargo
**A new flag available with alter-ship-flag, "no-scanned-cargo", changes the behavior to scanned/unscanned instead of revealing the cargo
**The "toggle-subsystem-scanning" flag must be set to swap full-ship scanning mode into subsystem scanning mode and works for all ship types
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Don't show callsigns in the escort list:===
{{Table242|
By default, callsigns are shown in the escort list using the same format as in the target box. If this flag is active, callsigns will not be displayed.
*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'''''

===$Fixed Chaining To Repeating Events:===
{{Table230|When set, this makes event chaining to repeated events work as designed - that is, the chained event will only be evaluated after the chain delay. If the repeating event's interval is shorter than the chain delay, then the delay countdown will continually be restarted until all repetitions have completed. Without this flag, FSO will emulate retail behavior which, due to a bug, allowed chained events to be evaluated immediately after a repeating event is first evaluated.

NOTE: Although the name does not reflect it, the same issue affects repeating events that are evaluated by <tt>is-event-true-delay</tt> and <tt>is-event-false-delay</tt>. Without this flag, FSO will emulate retail behavior which causes these SEXP operators to ignore any delay when evaluating repeated events. With this flag, the delay will be measured from when the final repeat iteration occurs.
*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)'''''}}

===$HUD-set-coords base resolution:===
{{Table232|The hud-set-coords SEXP has always used exact pixels, without regard for the current screen resolution. This setting enables a similar scaling mechanism as ''$Show-subtitle base resolution:''.
*Syntax: '''''(Integer, Integer)'''''
*Default Value: '''''(-1, -1)'''''}}

===$$Always Show Directive Value Count:===
{{Table250|
*If this setting is enabled, Directive-as-Value values in Directives will always show the number. By default this is disabled, and only values > 1 are shown.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

==#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'''''}}

===$EMP Pain Flash Factor:===
{{Table224|
Determines the intensity of the flash when the player is hit by an EMP blast or weapon.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$EMP Pain Flash Color:===
{{Table224|
Determines the RGB color value of the flash when the player is hit by an EMP blast or weapon.
*Syntax: Color, (red, green, blue) respectively, integer value from 0 to 255
*Default Value: '''''(255, 255, 127)'''''}}

===$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)
}}

===$EMP Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)
}}

===$Damage Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)'''''}}

===$Shadow Disable Techroom:===
{{Table224|
Disables shadows on ships in the techroom.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Cockpit:===
{{Table224|
Disables shadows on the player cockpit in mission.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Weapons:===
{{Table224|
Disables shadows on weapons in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Ships:===
{{Table224|
Disables shadows on ships in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Show Ship Casts Shadow:===
{{Table224|
When cockpit shadows are enabled, enabling this setting will cause the players ship model shown with "show ship" to cast shadow onto the cockpit.
*Syntax: '''''Boolean'''''
}}

===$Ship Model And Cockpit Share Coordinate Space:===
{{Table224|
When having the "show ship" flag enabled and cockpit models for a ship, this flag should be on if the cockpits can fit into the actual geometry of the ship model. Disable this flag if this is not the case and the cockpit needs to be rendered on top of the ship regardless of actual coordinates. If this can be enabled, the external show ship model can be rendered using deferred rendering.
*Syntax: '''''Boolean'''''
}}

===$Show Ship enabled only if Cockpits enabled:===
{{Table250|
Enabling this setting will only use the 'show-ship' flag if cockpits are enabled. Useful if your ship uses both 'show-ship' and cockpits that exist within the 'show-ship' space, and you want to allow players to toggle off cockpits. Note, 'show-ship' always only appears if in first-person view.
*Syntax: '''''Boolean'''''
}}

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

===$Do Not Render Lasers Below Length:===
{{Table250|
*Specifies the smallest length that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Do Not Render Lasers Below Radius:===
{{Table250|
*Specifies the smallest radius that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Thruster Easing Value:===
{{Table220|
*Smooths out the behavior of maneuvering thruster flares the higher above 0 it is.
*This is the exponential time constant for the visual flare length to reach it's true length.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

===$SCPUI attempts to load hires animations:===
{{Table230|
*Prevents SCPUI from trying to load anims prefixed with "2_"
*Syntax: '''''Boolean'''''
*Default Value: true}}

{{Table230|
===$Max draw distance:===
===$Min draw distance:===
*These values do more than just cutoff the visuals at certain distances, and they must be adjusted carefully to ensure unintentional rendering artifacts are not introduced.
*The rendering engine has limited amount of 'depth resolution', the degree to which it can tell a certain polygon is closer or farther away than another. When two polygons are too close, they will Z-fight, picking arbitrarily which is closer. It is the span between the min and max draw distance that determines how well the engine can determine depth, if they are too far from one another, the Z-fighting will become more common as it has to spread its resolution over a wider range. If they are close, Z-fighting will be lessened at the cost of a smaller range of distance able to be rendered.
*Syntax: '''''Float''''', meters
*Default Values: 10,000,000,000 and 1, respectively
}}

{{Table232|
===$Randomize particle rotation:===
*Particle bitmaps are typically screen-aligned; the upper portion of the bitmap will always be mapped to the upper portion of the particle, from the point of view of the camera. Enabling this option makes ''all'' particles have a random 'tilt' in an arbitrary direction when created.
*Syntax: '''''Boolean'''''
*Default Value: false
}}

===$Disable shield effects:===
{{Table250|
*Specifies if FSO attempts to use the shield mesh impact effects. Enabling this flag will prevent the game from preforming any shield mesh effect code, which can be useful if a mod does not use those shield mesh effects.
*Syntax: '''''Boolean'''''
*Default Value: false}}

==#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'''''}}

===$Use weapon class impact sounds for hits to player:===
{{Table224|
Allows weapons that hit the player to play their specific impact sounds, not the hard-coded default sounds.
*Syntax: '''''Boolean'''''
}}

===$Play thruster sounds for the player:===
{{Table232|
If the player's ship has thruster sounds defined, this will ensure they are played like normal, since they are typically suppressed.
*Syntax: '''''Boolean'''''
}}

===$Unify minimum engine sound:===
{{Table250|
Allows $Minimum Engine Volume in ships.tbl to work for all ship classes. By default, that value only triggers for non-huge ships.
*Syntax: '''''Boolean'''''
}}

===$Disabled or disrupted engines are silent:===
{{Table250|
If set, engines will not play their engine noise if the ship is disabled or a disrupted (such as disruptions caused by an active EMP effect or a weapon with the "electronics" flag).
*Syntax: '''''Boolean'''''
}}

==#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'''''}}

===$Add Message Head Ani Files:===
{{table224|
FRED will append each +Head entry listed below to the head ani selection list in the Event Editor.}}

====+Head:====
{{table224|
The head ani filename to add. Extensions will be stripped if included.
NOTE: Pay attention to file names or anis with a,b, c variation not display in-game (unless called directly). Proper name seems to be Head-xxxNa, Head-xxxNb, with N being some number and XXX being whatever you want. Needs further testing and confirmation
*Syntax: '''''+Head: String'''''}}

===$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'''''}}

===$FRED Briefing window resolution:===
{{table224|
The width and height of the briefing window in FRED. Defaults to 888x371. Note that changing this only affects FRED and can cause a mismatch to the ingame briefing view which defaults to 888x371 (or 555x232 for 640 base res).
*Syntax: '''''integer, integer'''''
*Default Value: '''''888,371'''''}}

===$Ignore Music Files In Music Player:===
{{table232|Music files in this section will not be added to FRED's built-in music player.}}
====+File:====
{{table232|Specifies a file
*Syntax: '''''string'''''}}

===$FRED spacemouse nonlinearities:===
{{table232|
Allows setting custom nonlinearities and scaling for controlling FRED with a spacemouse.
}}
====+Sideways exponent:====
{{table232|
The exponent for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Sideways scale:====
{{table232|The multiplier for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards exponent:====
{{table232|The exponent for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards scale:====
{{table232|The multiplier for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards exponent:====
{{table232|The exponent for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards scale:====
{{table232|The multiplier for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch exponent:====
{{table232|The exponent for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch scale:====
{{table232|The multiplier for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank exponent:====
{{table232|The exponent for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank scale:====
{{table232|The multiplier for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading exponent:====
{{table232|The exponent for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading scale:====
{{table232|The multiplier for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}

==#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. This fixes missile impacts to submodels whose center lies outside the geometry of the submodel. In other words, without this flag, a missile might detonate in the middle of the "bowl" of a concave submodel; with this flag, the missile will travel to the other side of the submodel before it detonates.
*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'''''

===$Use 3d ship select:===
{{Table224|
*Whether or not to use 3D models for ship select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d ship icons:===
{{Table224|
*Whether or not to use 3D models for ships in ship/weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d weapon select:===
{{Table224|
*Whether or not to use 3D models for weapon select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d weapon icons:===
{{Table224|
*Whether or not to use 3D models for weapons in weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d overhead ship:===
{{Table224|
*Whether or not to use 3D models for ship overhead view instead of a bitmap in weapon select
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Default overhead ship style:===
{{Table224|
*This specifies which style of overhead view to use if 3d overhead view is active
*Syntax: '''''String'''''
*Possible options are "ROTATE" or "TOPVIEW"}}

===$Always refresh selected weapon when viewing loadout:===
{{Table232|
*When set to true, this always refreshes the weapon shown in view box on the right side of the screen when opening the weapon loadout view. This ensures the viewed weapon is one that can actually be on the selected ship when first clicking on the weapon loadout screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$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|
*Mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. By default is now ON, and can be accessed by going to the Options menu and pressing F3.
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

===$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'''''}}

===$Apply HUD shudder to chase view:===
{{Table232|
*Applies hud shudder (afterburner and engine wash) also to chase view. Does not override the command line toggle.
*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'''''}}

===$Lead indicator behavior:===
{{Table224|
Changes how Lead Indicators behave when multiple weapon banks are linked and in range.
When set to default, if you have linked weapons, only the indicator for the one with the farthest range will be drawn.
When set to multiple, a lead indicator is drawn for all primary weapons in range when you have them linked.
When set to average, a single lead indicator is drawn in the average of the position where each of them would usually be drawn.
*Syntax: '''''String'''''
** Valid options are '''''default''''', '''''multiple''''' and '''''average'''''
*Default Value: '''''default'''''
}}

===$Use distant firepoint for all turrets:===
{{Table224|
*Causes the game to use firepoint-based target leading calculations for all turrets. This is useful if all or most turrets in a given mod has firepoints that are distant from their center-point.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Enable discord rich presence:===
{{Table224|
*Enables or disables the built-in Discord game-status reporting.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Always hide hidden ships in hotkey list:===
{{Table224|
*Whether or not to always hide ships with HIDDEN hotkey (set in FRED), even in the in-mission hotkey menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Allow automatically assigning personas:===
{{Table232|
*Whether or not the game will automatically assign personas to ships that have no persona set.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Countermeasures use capacity:===
{{Table232|
*Whether or not Countermeasures use tabled capacity.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Calculate subsystem hitpoints after parsing:===
{{Table234|
*Causes subsystem hitpoints to be calculated after all ships.tbl and -shp.tbm files have been parsed. This allows subsystem percentages to correctly reflect the final hull value rather than the first hull value encountered.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix scripted velocity:===
{{Table242|
*If this setting is enabled, object velocity set via script will wholly determine the change in position for that frame, ignoring ''all'' other in-engine concerns. Otherwise, the game engine will likely overwrite/ignore any changes, depending on when the changes were made in the frame.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Preload briefing icon models:===
{{Table250|
*If set, this forces preloading of models used for briefing icons. This only loads models used for icons that haven't already been loaded for the mission. This is useful for SCPUI's where hovering over an icon shows the model without having to click on it and the stutter when it loads models not used in mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Behavior for pressing Escape key in options menu:===
{{Table250|
*If set to 'save', the escape key for the HUD and Options screen saves options when leaving those screens (ie it does the same thing as pressing Ctrl-Enter/Accept). By default (or if set to 'default') the Escape key will not save any changed values when exiting those screens.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Disable intro cutscene:===
{{Table250|
*If set, this disables loading of any cutscenes as the game starts that might play before the player reaches the pilot select screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Show locked status for scramble missions:===
{{Table250|
*If set, scramble mission will show a text line right below the words 'Weapons Loadout' that states "Ships/Weapons Locked" (XSTR 749), thus the player can easily see their loadouts are locked and they do not have to check the loaoout buttons on every mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Disable expensive turret target check:===
{{Table250|
*If set, this value speeds up turret target checking. By default, turret target acquisition was spending a lot of time doing a raycast, the result of which was barely used at all. If we don't need the target normal, all it does is get a target point slightly more accurate, but in practice it really isn't noticeable at all whether the target point of the turret is actually on the surface of the ship, or maybe on the other side of the ship.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Threshold below which shield skips damage:===
{{Table250|
*By default, FSO logic dictates that shields collisions and any related sound or visuals related to shields are skipped if the shields are under 10%. This value allows modders to customize the value, though the value must be between 0.0 and 1.0.
*Syntax: '''''Float'''''
*Default Value: '''''0.1'''''}}

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

Fate of the Galaxy

2025-07-10T13:52:15Z

Wookieejedi: tune C70 name

{{fotg}}

'''Fate of the Galaxy''' (FotG) is a free total conversion set in the ''[https://en.wikipedia.org/wiki/Star_Wars Star Wars]'' Original Trilogy. Developed using the open-source FreeSpace 2 Open (FSO) game engine, the project will be released as a standalone (the game FreeSpace 2 is not required). An active [https://fate-of-the-galaxy.github.io/ website], [https://www.hard-light.net/forums/index.php?board=143.0 forum] and [https://discord.gg/k7ZMdmt Discord Channel] are also maintained. As a disclaimer, Fate of the Galaxy is a total conversion for FreeSpace Open developed by a team of fan volunteers, it is not associated with Lucasfilm Ltd or Disney and is not an official Star Wars product

==Developers==
*'''chief1983:''' Project Lead
*'''Brand-X:''' Senior Artist and Content Moderator
*'''TopAce:''' Mission Design
*'''swashmebuckle:''' Music Composer, Writer
*'''zookeeper:''' Model Conversion, Artist, Scripting
*'''CountBuggula:''' Webmaster, Communications
*'''niffiwan:''' Coder
*'''wookieejedi:''' Mission Design, Scripting, Beta Management
*'''Limbert:''' Senior Artist
*'''bobbtmann:''' Senior Contributor
*'''Dark Visor:''' Senior Artist

''Full list of contributors is present in Credits screen of the game.''

==Gameplay==
In ''Fate of the Galaxy'' the player takes the role of a starfighter pilot through a series of missions and campaigns. The game is primarily played through the perspective of single-manned craft. There are no plans currently for player-control of capital ships, though certain player craft do allow for AI gunners. Current missions are set in space, including in asteroid fields, nebulas, and above planets. A multiplayer mode is also available to play and works well at low pings (~<100 ms). Standalone instances of the game are maintained, which allows players to easily join a server and play with friends.

The player will choose to play as a pilot for the Rebel Alliance, the Galactic Empire, or as an independent neutral adventurer/privateer. All factions have their own unique ships to control.

===Authenticity===
''Fate of the Galaxy'' strives to recreate combat as close to as seen in the Original Trilogy of ''Star Wars'', during scenes such as the [https://starwars.fandom.com/wiki/Battle_of_Endor/Legends Battle of Endor] and the [https://starwars.fandom.com/wiki/Battle_of_Yavin Battle of Yavin]. To achieve this, the members of the development team have extensively analyzed individual movements and moments within these scenes to determine a baseline for such game concepts as damage, speed, and maneuverability. Each fighter will stay as close as possible to its canonical statistics stated in various sources, but the final authority is the Original Trilogy movies themselves. Thus, many attributes may be contrary to other published materials due to their divergence from the Original Trilogy. In addition, visuals have been tuned to match the aesthetic of the Original Trilogy movies.

Given this focus on movie authenticity, the gameplay differs from that present in the default FreeSpace 2 universe. Ships will be much faster and combat quicker paced, with a larger focus on avoiding damage rather than absorbing it. Several coding features have been completed to create a new, unique style of combat.

==Vehicles==
The game includes multiple ships unique to each faction, with some designs being shared when appropriate. Each faction's fighters and capital ships have unique strengths, which presents different gameplay styles for each side.

===Alliance to Restore the Republic/New Republic===
[[Image:NuX.png|thumb|The X-wing Starfighter, main fighter of the Rebel Alliance]]
The Alliance to Restore the Republic and New Republic maintain a focus on versatile and durable starfighters and small, fast capital ships. Most of the Rebel fighters are equipped with secondary missile weapons such as concussion missiles or proton torpedoes. Rebel players will, in most cases, be unable to outmaneuver their Imperial counterparts and will rely on their superior durability and weapon complement, as well as teamwork to engage the enemy. Rebel capital ships are smaller than their Imperial counterparts, with each having diverse strengths due to their construction by various manufacturers. Rebel Mon Calamari Cruisers are noted for their incredible shield regeneration rates, while Corellian Corvettes are known for their speed.

The following Rebel/New Republic craft are included in the game:

*[https://starwars.fandom.com/wiki/X-wing_starfighter T-65 X-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL_Y-wing_starfighter BTL-A4 Y-wing Starfighter]
*[https://starwars.fandom.com/wiki/BTL-A4_LP_%22Longprobe%22 BTL-LP Longprobe Starfighter]
*[https://starwars.fandom.com/wiki/RZ-1_A-wing_interceptor RZ-1 A-wing Interceptor]
*[https://starwars.fandom.com/wiki/A/SF-01_B-wing_starfighter A/SF-01 B-wing Starfighter]
*[https://starwars.fandom.com/wiki/E-wing_escort_starfighter E-wing Escort Starfighter]
*[https://starwars.fandom.com/wiki/UT-60D_U-wing_starfighter/support_craft UT-60D U-wing]
*[https://starwars.fandom.com/wiki/Millennium_Falcon Millennium Falcon]

*[https://starwars.fandom.com/wiki/GR-75_medium_transport GR-75 Medium Transport]
*[https://starwars.fandom.com/wiki/CR90_corvette Corellian CR90 Corvette]
*[https://starwars.fandom.com/wiki/EF76_Nebulon-B_escort_frigate EF76 Nebulon-B Escort Frigate]
*[https://starwars.fandom.com/wiki/MC30C_frigate MC30 Heavy Frigate]
*[https://starwars.fandom.com/wiki/MC40a_light_cruiser MC40 Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Liberty_type_Star_Cruiser ''Liberty''-class Star Cruiser]
*[https://starwars.fandom.com/wiki/MC80_Home_One_type_Star_Cruiser ''Home One''-class Star Cruiser]

===Galactic Empire===
[[Image:NuRTIE03.jpg|thumb|The TIE/ln Starfighter, main fighter of the Galactic Empire]]
The Galactic Empire's main strategy for fighters revolves around the concept of numerical advantage. Imperial TIEs usually lack shields and durability, but have very potent weaponry and great maneuverability to counter this weakness. Most Imperial fighters also forego any sort of missile secondary weapons and focus entirely on their lasers for offensive armament. Imperial capital ships are much larger than those of the Rebels, and focus on heavy offensive weaponry and great hull durability.

The following Imperial craft are included in the game:

*[https://starwars.fandom.com/wiki/TIE/LN_starfighter T.I.E. Starfighter & TIE/ln Starfighter]
*[https://starwars.fandom.com/wiki/TIE_Reconnaissance_Fighter TIE/rc Recon Fighter]
*[https://starwars.fandom.com/wiki/TIE/IN_interceptor/Legends TIE/In Interceptor Mark I and Mark II]
*[https://starwars.fandom.com/wiki/TIE/sa_bomber TIE/sa Bomber]
*[https://starwars.fandom.com/wiki/TIE_Advanced_x1 TIE Advanced x1]
*[https://starwars.fandom.com/wiki/V38_assault_fighter V38 Assault Fighter]

*[https://starwars.fandom.com/wiki/TIE/sh_shuttle TIE/sh Shuttle]
*[https://starwars.fandom.com/wiki/Alpha-class_Xg-1_Star_Wing Xg-1 Star Wing]
*[https://starwars.fandom.com/wiki/Delta-class_DX-9_stormtrooper_transport DX-9 Stormtrooper Transport]
*[https://starwars.fandom.com/wiki/Lambda-class_T-4a_shuttle Lambda-class T-4a Shuttle]
*[https://starwars.fandom.com/wiki/Zeta-class_Heavy_Cargo_Shuttle Zeta-class Heavy Cargo Shuttle]

*[https://starwars.fandom.com/wiki/Carrack-class_light_cruiser ''Carrack''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Arquitens-class_light_cruiser ''Arquitens''-class Light Cruiser]
*[https://starwars.fandom.com/wiki/Strike-class_medium_cruiser ''Strike''-class Medium Cruiser]
*[https://starwars.fandom.com/wiki/Vindicator-class_heavy_cruiser ''Vindicator''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/Interdictor_vessel ''Interdictor''-class Cruiser]
*[https://starwars.fandom.com/wiki/Imperial_II-class_Star_Destroyer ''Imperator II''-class Star Destroyer]
*[https://starwars.fandom.com/wiki/Golan_space_defense_platform Golan M-series Dockyard Platforms]
*[https://starwars.fandom.com/wiki/Shield_Gate Golan M-3185 Shield Gate Station]

===Neutral===
There are multiple factions in the Star Wars galaxy which use many craft that are not produced for the Galactic Empire or the Rebel Alliance. These craft vary in characteristics and are used throughout the galaxy in various roles.

The following Neutral craft are included in the game:

*[https://starwars.fandom.com/wiki/Z-95_Headhunter Z-95 Headhunter]
*[https://starwars.fandom.com/wiki/CloakShape_fighter/Legends Cloakshape Starfighter]
*[https://starwars.fandom.com/wiki/N-1_starfighter N-1 Naboo Starfighter]
*[https://starwars.fandom.com/wiki/Alpha-3_Nimbus-class_V-wing_starfighter Alpha-3 Nimbus-class V-wing Starfighter]
*[https://starwars.fandom.com/wiki/Aggressive_ReConnaissance-170_starfighter/Legends ARC-170 Starfighter]
*[https://starwars.fandom.com/wiki/Ugly/Legends Various Uglies]
*[https://starwars.fandom.com/wiki/Firespray-31-class_patrol_and_attack_craft Firespray-31-class Gunship]
*[https://starwars.fandom.com/wiki/Slave_I Slave I]
*[https://starwars.fandom.com/wiki/YT-1300_light_freighter YT-1300 Light Freighter]
*[https://starwars.fandom.com/wiki/BFF-1_bulk_freighter BFF-1 Bulk Freighter]
*[https://starwars.fandom.com/wiki/Tug DV-3 Cargo Freighter]
*[https://starwars.fandom.com/wiki/Action_VI_transport Action VI Transport]
*[https://starwars.fandom.com/wiki/Transport Rayter-class Transport]
*[https://starwars.fandom.com/wiki/CSS-1_Corellian_Star_Shuttle Star Shuttle]
*[https://starwars.fandom.com/wiki/StarSpeeder_1000 Star Speeder]
*[https://starwars.fandom.com/wiki/GAT-12_Skipray_Blastboat GAT-10 Skipray Blastboat]
*[https://starwars.fandom.com/wiki/Consular-class_cruiser_(Charger_c70_retrofit) Corellian Charger C70 Retrofit]
*[https://starwars.fandom.com/wiki/Braha'tok-class_gunship Braha'tok-class gunship]
*[https://starwars.fandom.com/wiki/Marauder-class_corvette Marauder-class corvette]
*[https://starwars.fandom.com/wiki/Dreadnaught-class_heavy_cruiser ''Dreadnaught''-class Heavy Cruiser]
*[https://starwars.fandom.com/wiki/XQ_Platform_series XQ1 and XQ2 Stations]
*[https://starwars.fandom.com/wiki/Asteroid_base Asteroid Base Station]
*[https://starwars.fandom.com/wiki/Repair_droid Dockyard Repair Droids]
*[https://starwars.fandom.com/wiki/Satellite/Legends Sensor and Defense Satellites]
*[https://starwars.fandom.com/wiki/Space_mine Space Mines]

==Missions and Campaigns==
''Fate of the Galaxy'' comes with a high level of single-player content. These include multiple campaigns, standalone missions, and the ability to create missions using the FSO mission editor FRED2. Multiplayer servers are also maintained and available to play on with friends.

The first three campaigns narrate three interconnected stories set at the beginning of the Galactic Civil War. Each of these three campaigns consists of about 5 missions, thus designers put high emphasis on quality mission design and high replayability. The player's performance throughout the campaign will affect how later missions play out. For example, the Alliance campaign will pit a ragtag Rebel task force against a dreaded ''Imperial''-class Star Destroyer in the early stages of the Rebellion, and the player's performance throughout the campaign has a major impact on this encounter's difficulty. The best possible outcome is hard to achieve, thus a number of playthroughs will be required.

Players receive different types of training in different campaigns. The Alliance mini-campaign starts with a basic training mission that teaches the basics to new players along with gameplay features that are unique to ''Fate of the Galaxy'''. The Imperial mini-campaign starts with an advanced training.

Standalone missions are also included in the first release. Many of them are serious, story-driven missions, but there will also be arcade-like "challenge" missions in which the player must accomplish a wide variety of objectives, such as surviving two minutes within a ''Strike''-class cruiser's firing range. There will also be a Practice Zone mission, where the player can test flying any of the small craft and actively spawn in any craft in the mission as a hostile or friendly to practice combat.

Three additional campaigns are being worked on and will be available when the game is released to the public, but specific details remain under embargo until public launch. This large component is code-named Project Alderaan.

==Development==
[[Image:Ewingmaps.jpg|thumb|The progression of model work shown on an E-wing Starfighter, from Model (Right) to Normal Maps (Center) and Diffuse Texture (Left). Note that this model will not be used.]]
Fate of the Galaxy picks up after a number of previous attempts to create a ''Star Wars'' mod for FreeSpace. For several years the "Star Wars Conversion Project" was worked on by various teams and developers, but without any releases.

In early 2007, chief1983 took over as project leader, and began to assemble a new team of developers. Choosing the name ''Fate of the Galaxy'', the initial team consisted of chief1983, Brand-X as a modeler and Turambar as a texturer. The initial plan put forward was to use the models and textures that had been completed by previous teams. Soon after the reformation of the mod team, however, it was decided that all new art assets were needed to compete with the high graphical standards of the newer models, and all previously completed ships were discarded.

Work continued on ship models and textures through the next year and a half, as new staff members were added to the development team. In May of 2008, work began on implementing the new ship models into the game and work began on redesigning the feel and pace of the FreeSpace 2 Open engine. Work still continued on the models needed for a campaign and demo release.

In early January of 2009, Brand-X experienced a hard drive failure which destroyed all previous models of his, setting the team's art department back significantly. Since then, work has progressed on recreating these models to even higher quality standards.

On June 4th, 2009, the first in-game screenshot of the X-wing starfighter was made public at the [http://www.moddb.com/games/fate-of-the-galaxy/images/x-wing-in-game-shots2#imagebox ModDB site] and at the official FotG [https://www.hard-light.net/forums/index.php?board=143.0 forums]. The first three campaigns, which are set at the beginning of the Galactic Civil War, were eventually completed, and worked then moved to standalone missions and three additional campaigns code-named Project Alderaan.

In December of 2018 the team began the first phases of private beta testing. In June of 2022, the private beta tests were stated as nearly concluded.

In May of 2019 the [https://www.youtube.com/watch?v=ler20EdjAfs&list=LLW8-wdcPLv0eT913KIi9_mw&index=2&t=0s teaser trailer] was posted.

Throughout 2020-2022 developmental showcases have consisted of forum updates and gameplay streams on Discord.

In June of 2022, multiplayer was confirmed to be working well, and standalone servers were created.

From 2023-2024, the game underwent extensive balance and optimization testing in preparation for the public release.

For the duration of 2025, additional polishing passes were conducted and continue to be refined.

===Newsletter===
Newsletters are posted on a quarterly basis on the [https://www.hard-light.net/forums/index.php?board=143.0 Fate of the Galaxy Forums]. Also, the majority of the unofficial development chatter occurs on the Fate of the Galaxy Discord channel [https://discord.gg/k7ZMdmt].

The most recent [https://www.hard-light.net/forums/index.php?topic=99253.0] was released in May 2024. This update highlights new ship additions, MainHall updates, many other enhancements, and numerous fixes and minor updates.

For reference, the [http://www.hard-light.net/forums/index.php/topic,54217.0.html first newsletter] was posted on June 1st, 2008.

===First Release===
The first open beta of ''Fate of the Galaxy'' was originally planned to be released sometime late-2008 or early 2009. However, with the art setback, the release has been pushed back. Subsequent additions and developments then lead the team to decide to release the game as a more polished 1.0 version. A date has not been decided yet, but the first three campaigns are done and relatively independent compared to the larger subsequent 3 campaigns.

Recent years have shown considerable progress on the project, including a release of a private beta and addition of multiple ships and integrating new features that were recently added to the FSO engine (such as deferred and shadow lighting for cockpits, optimizations, and advanced scripting controls).

In the most recent communications on Discord, co-community manager wookieejedi posted: "''We are getting extremely close to releasing FotG publicly--one of the largest remaining milestones is having FSO release 25.0 stable (which is ideally not far away). We simply can’t wait to share the game with you all once those milestones are completed.''" (May 4th, 2025)

==Gallery==
===Ship Lab shots===
<gallery>
Image:Bwing.jpg
Image:Falcon2.jpg
Image:Xwing.jpg
Image:Ywing2.jpg
Image:Z95.jpg |
</gallery>
===Renders===
<gallery>
Image:FalconWallpaper.png
Image:TBrender.png
Image:TransportFinal.jpg
Image:Wallpaper.1-1280.png
Image:Wallpaper.2-1280.png
</gallery>

==Links==
*[http://swc.hard-light.net/ Official Website]
*[https://discord.gg/k7ZMdmt Fate of the Galaxy Discord Server]
*[https://www.hard-light.net/forums/index.php?board=143.0 Official Forum]
*[https://www.moddb.com/games/fate-of-the-galaxy Fate of the Galaxy on ModDB]

Ai profiles.tbl

2025-06-26T12:30:42Z

Wookieejedi: correct order

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use ai-form-on-wing-new:===
{{Table250|
*Will cause form-on-wing orders issued by the hud squadmsg menu (i.e. player orders) to be the 'new' variant that does not clear other goals assigned to the same ship/wing.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving.
**Syntax: '''''Float''''' (defaults to 3.0)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

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

2025-06-25T19:30:32Z

Wookieejedi: add standard strafe fix

{{SCP_table}}
{{TableVersionGit|2025-02-12|72a11fd542671e849042a2e8de0f090e5cbdae0d}}
{{Tables}}
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.

{{Table232| This table can also be called '''mission_profiles.tbl'''}}

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.tbm
{{Table232| Can also be extended with '''xxx-msp.tbm'''}}

If the version targeted in [[game_settings.tbl]] is equal to or later than these listed, the following options are enabled by default:
{{Table3610|
*'''reset last_hit_target_time for player hits'''}}
{{Table372|
*'''fix ramming stationary targets bug'''}}
{{Table202|
*'''huge turret weapons ignore bombs'''
*'''fix linked primary weapon decision bug'''
*'''prevent turrets targeting too distant bombs'''
*'''fix heat seekers homing on stealth ships bug'''
*'''allow vertical dodge'''
*'''fix ai class bug'''
*'''ai guards specific ship in wing'''
*'''fix ai path order bug'''
*'''aspect bomb invulnerability fix'''
*'''use actual primary range'''
*'''fighters/bombers with no shields can manage ETS'''}}
{{Table214|
*'''fixed ship-weapon collisions'''}}
{{Table220|
*'''fighterbay arrivals use carrier orientation'''
*'''prevent negative turret ammo'''
*'''fix keep-safe-distance'''}}
{{Table224|
*'''fix good-rearm-time bug'''
*'''no continuous turn on attack'''
*'''remove-goal properly removes play-dead order'''}}
{{Table232|
*'''ships playing dead don't manage ETS'''}}
{{Table234|
*'''hud squad messages use tactical disarm/disable'''}}
{{Table242|
*'''debris damage respects 'big damage' flag'''
*'''force beam turrets to use normal fov'''
*'''guards ignore protected attackers'''}}
{{Table250|
*'''fix avoid-shockwave bugs'''}}

==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 '''FS2 Retail''', 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. -1 means no limit.
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Max Weapon Friendly Fire Damage:===
{{Table242|
*Defines the maximum damage inflicted by friendly weapon fire, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$Max Weapon Self Damage:===
{{Table242|
*Defines the maximum damage inflicted by self-hits, including shockwaves. -1 means no limit.
*Syntax: '''Float list'''
**Default: -1, -1, -1, -1, -1
}}

===$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
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Integer 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
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Integer 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: '''Integer 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 time 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''', seconds
**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: '''Integer 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: '''Integer 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 for an AI to hesitate about firing a secondary or homing turret weapon at the player. Values range from 0-6, at 0 they will frequently hesitate, at 6 they will never hesitate.
*Syntax: '''Integer list'''
**Default: 0, 1, 2, 3, 4
* Mechanic details: AIs are only allowed to fire homing secondaries or turrets with homing weapons at the player in a limited window of time. The window starts every ten seconds, and lasts ('''value''' + 1) 7ths of that ten second cycle. Each ship has it's own cycle, so their windows are not all synchronized.
* Example: a value of 1 becomes 2/7ths, so ships can fire homing weapons at the player for roughly 2.85 seconds at a time, then are unable to fire them for 7.15 seconds.
}}

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

===$free afterburner use:===
{{Table382|
*If set, the AI will use afterburners in more situations.}}

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

===$check communications for non-player ships:===
{{Table202|
*When set, every ship will have the same communications subsystem restrictions as the player, including minimum strength to send messages and EMP scramble status.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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 player secondary doublefire:===
{{Table202|
*If set, players are not allowed to dual-fire their secondaries.}}

===$disable ai secondary doublefire:===
{{Table202|
*If set, AIs are not allowed to dual-fire their secondaries.}}

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

===$fix ramming stationary targets bug:===
{{Table202|
*When set, AI ships will try not to crash into stationary targets. See [http://scp.indiegames.us/mantis/view.php?id=3147 Mantis #3147].
*Off by default.
*Syntax: '''''Boolean'''''}}

===$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, ships that are on different teams and ships that are outside the player's squadron will be allowed to send death screams. Additionally, the game will no longer cap a maximum number of screams per mission. (This flag originated as a customization of message behavior for the Wing Commander Saga mod.)
Prior to revision 9119, this was "$perform less checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22fov_edge_checks.22|"fov edge checks"]].}}

===$require turrets to have target in fov:===
{{Table3614|
*Forces all turrets to use [[Subsystem#.22target_requires_fov.22|"target requires fov"]].}}

===$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|
*Normally, 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 flag to YES to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES; to get rid of retail behavior you would specify NO. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
* Default: NO.
* When no, when any secondary encounters any beam it is instantly destroyed regardless of if it is marked as interceptable, has a health value, or any other circumstance that would normally apply to interception by other weapons.
* When true, damage and health values are respected in these circumstances. Secondaries without hitpoints are still destroyed, however.
}}

===$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|
*By default, an aspect seeker that's been decoyed by a CM just flies straight forward, while a heatseeker in the same position will actively home in on the CM. This flag makes aspect seekers match heatseeker behavior in this regard.}}

===$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).}}

===$support don't add primaries:===
{{Table382|
*When set, the support ship will not equip a new primary weapon into an empty bank.
*Off by default.
*Syntax: '''''Boolean'''''}}

===$fighterbay arrivals use carrier orientation:===
{{Table220|
*Causes all ships arriving via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they exit.
*Syntax: '''''Boolean'''''}}

===$fighterbay departures use carrier orientation:===
{{Table220|
*Causes all ships departing via a ship's fighterbay to attempt to align their right vector with their carrier's right vector as they enter.
*Syntax: '''''Boolean'''''}}

===$debris damage respects 'big damage' flag:===
{{Table242|
*Causes damage inflicted by debris to be limited by the 'big damage' flag in the same way as damage inflicted by weapons.
*Syntax: '''''Boolean'''''}}

===$don't limit change in speed due to physics whack:===
{{Table242|
*With this flag, the speed change due to physics whacks (collision, shockwave, etc.) is unlimited. Without this flag, the speed change will be capped at 440 m/s if it exceeds 500 m/s.
*Syntax: '''''Boolean'''''}}

===$guards ignore protected attackers:===
{{Table242|
*With this flag, the AI will not guard against ships that have the "protect-ship" flag.
*Syntax: '''''Boolean'''''}}

===$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 lose its mind 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'''''}}

===$strict turret-tagged-only targeting:===
{{Table372|
*When set, newer turret-tagged-only behavior will be enabled. See [http://scp.indiegames.us/mantis/view.php?id=3114 Mantis #3114].
*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'''''}}

===$override radius for subsystem path points:===
{{Table202|
*When set, this value overrides the default distance for determining if a ship had reached a point in a model subsystem path. Useful to allow ships with high damp values to navigate subsystem paths when attacking a subsystem. Must be greater than or equal to 1. If '''''$use POF radius for subsystem path points:''''' is set than this override value will only be used if the point in the subsystem path is less than 1 or invalid.
*5 by default.
*Syntax: '''''Integer'''''}}

===$use POF radius for subsystem path points:===
{{Table202|
*When set, the distance for determining if a ship had reached a point in a model subsystem path will be the radius of that path point, not the default distance of 5.
*Off by default. If this is set to YES and ''''''$override radius for subsystem path points:''''' is set to greater than or equal to 1, then the path point radius will be used. If the path point radius cannot be found or is less than 1 then override radius will be used if it is set to greater than or equal to 1.
*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:]].}}
}}

===$lead indicator second-order prediction factor:===
{{Table202|
*This is a 0 to 1 multiplier of a factor to adjust the lead indicator to take into account a ship's rotational velocity as well as its velocity. This will directly affect autoaim, making it more accurate for turning enemies.
*This ''will'' make the lead indicator slightly jitterier in general, and does not properly take into account gliding. It is recommended to adjust the value to fit your situation.
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$no directional bias for missile and ship turning:===
{{Table202|
*When enabled, this will cause ships and missiles to take direct turning paths to point at their target. This does not directly affect their turning time, but in many situations will result in more efficient paths and a better time-to-target.
*Syntax: '''''Boolean'''''}}

===$respect ship axial turnrate differences:===
{{Table202|
*Normally AI ships will use the average of their pitch and heading turn times for their turn time on all axes. If this is enabled the ship will actually use the tabled values for each axis.
*'''''NOTE''''':The AI will '''''NOT''''' take this into account when turning, it will always turn directly towards its target, even if it could bank and use a faster axis instead. Use this flag carefully, and make sure that their your ships have exactly the turn times you want for each axis.
*Syntax: '''''Boolean'''''}}

===$any ship with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on any ship to manage ETS for weapons and engines even if they do not have shields set to on. Do note that in Vanilla FS2, some capital ships can go much faster with this enabled.
*Syntax: '''''Boolean'''''}}

===$fighters/bombers with no shields can manage ETS:===
{{Table202|
*Normally AI ships will not manage ETS if they do not have shields set to be on. When enabled, this flag allows the AI on fighters and bombers to manage ETS for weapons and engines even if they do have shields set to on.
*Syntax: '''''Boolean'''''}}

===$ships playing dead don't manage ETS:===
{{Table232|
*Prevents ships from managing their ETS is they are currently playing dead. Managing ETS could lead to unexpected speed changes in ship-maneuver.
*Syntax: '''''Boolean'''''}}

===$better combat collision avoidance for fightercraft:===
{{Table202|
*If set will cause small ships to be much better at avoiding colliding with large ships while fighting, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat collision avoidance aggression for fightercraft:===
{{Table250|
*Requires $better combat collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$better guard collision avoidance for fightercraft:===
{{Table250|
*If set will cause small ships to be much better at avoiding colliding with large ships while guarding, and will not spend as long recovering from a collision if one does occur.
*Syntax: '''''Boolean'''''}}

===+combat guard avoidance aggression for fightercraft:===
{{Table250|
*Requires $better guarding collision avoidance for fightercraft: to be set above. Sets the avoidance aggression value for avoiding colliding with large ships while fighting, higher numbers increase collision avoidance.
*Syntax: '''''Float''''' (defaults to 3.5)}}

===$firing requires exact los:===
{{Table202|
*If set will cause turrets and AI weapons to only fire if they have a clear line of sight from their firing point to their target's ship's center.
*Syntax: '''''Boolean'''''}}

===$exact los minimum detection radius:===
{{Table242|
*The minimum radius of objects that are considered for line-of-sight when using the ''$firing requires exact los:'' flag. The default is 10.
*Syntax: '''''Float'''''}}

===$improved missile avoidance for fightercraft:===
{{Table212|
*Fighters/bombers will be much more effective at dodging missiles in general. Of note is that AI do not normally care about countermeasure effect range before dropping them (only distance less than 200m), with this flag, they will only drop them if within countermeasure range.
*Syntax: '''''Boolean'''''}}

===$unify usage of AI profile countermeasure chance:===
{{Table250|
*Specifies all AI ships to use their specific AI class profile countermeasure firing chance. By default Friendly ships always use the second value in '''$AI Countermeasure Firing Chance:''' from default AI profile. The older name of "$friendly ships use AI profile countermeasure chance:" also enables this flag.
*Syntax: '''''Boolean'''''}}

===$improved subsystem attack pathing:===
{{Table212|
*Fightercraft will use a somewhat more efficient and faster subsystem attack pathing method.
*Notably, this method ''does not'' use the path system. Using this flag, aside from docking and fighter bay paths, ''all other'' paths will be ignored and are no longer necessary.
*Syntax: '''''Boolean'''''}}

===$fixed ship-weapon collisions:===
{{Table214|
*Fixes an error in ship-weapon collisions which would occasionally cause them to not trigger when they should.
*Most obvious when projectiles would erroneously bypass a full shield quadrant and damage the hull.
*Syntax: '''''Boolean'''''}}

===$AI secondary range awareness:===
{{Table214|
*Controls if the AI considers weapon range at all when selecting a secondary weapon to attempt to use. Currently available options are:
*'RETAIL': The default. After performing filtering logic based on the target types and weapon flags, the AI will select the first valid secondary bank as its active one, regardless of range.
*'AWARE': As retail, except that if a weapon is out of range it the AI will keep looking down the list to see if it has a weapon that is in range, and use that instead if it does. All other weapon selection and restriction logic still applies.}}

===$no shield damage from ship collisions:===
{{Table214|
*Normally, the heavier ship in a collision will receive shield damage from the collision if it has one.
*This disables that, and causes all involved ships to only take hull damage.
*Syntax: '''''Boolean'''''}}

===$turret target recheck time:===
{{Table220|
*Defines the amount of time between target recalculation for turrets.
*Affects turret reaction time in all scenarios, acquiring a target from idle, re-affirming the current target, switching to a new target or even a new subsystem on the same target.
*Be aware setting this value too low can have an extreme performance impact. It is recommended to not set this below 30 ms.
*Syntax: '''''Float''''', milliseconds
*Default: 2000}}

===$prevent negative turret ammo:===
{{Table220|
*By default, turrets with ammo would end up firing one extra shot, resulting in a -1 ammo. This flag corrects that behavior, so the ammo count is properly used.
*Syntax: '''''Boolean'''''}}

===$fix keep-safe-distance:===
{{Table220|
*Allows any ship flying the keep-safe-distance behavior to turn toward its goal point. Without this flag, ships will fly into the distance in a straight line.
*Syntax: '''''Boolean'''''}}

===$AI ignores aspect lock for leading:===
{{Table222|
*When off, AI fighters follows retail behavior of aiming directly at a target when using aspect lock missiles. When on AIs ignore this consideration and always lead their targets when attempting to aim at them.
*Syntax: '''''Boolean'''''
*Default: on}}

===$fix good-rearm-time bug:===
{{Table224|
*Causes the "good rearm time" SEXP to correctly expire (revert to being a "bad rearm time") at the end of the specified time.
*Syntax: '''''Boolean'''''}}

===$no continuous turn on attack:===
{{Table224|
*Prevents an AI behavior where fighters/bombers will spin around for a second or two when they acquire a target.
*Syntax: '''''Boolean'''''}}

===$remove-goal properly removes play-dead order:===
{{Table224|
*Causes remove-goal to take the ship out of the play-dead AI mode when removing the play-dead goal.
*Syntax: '''''Boolean'''''}}

===$bay arrivals not time limited:===
{{Table224|
*Causes AI to always complete a bay arrival path, even if it takes longer than 10 seconds.
*Syntax: '''''Boolean'''''}}

===$use adjusted AI class autoscale:===
{{Table224|
*Causes autoscaled AI classes to scale only based on the collection of autoscaled AI classes, not all AI classes. This prevents autoscaled calculations from being skewed by the presence of non-autoscaled classes in the list.
*Syntax: '''''Boolean'''''}}

===$carry shield difficulty scaling bug:===
{{Table232|
*Enables an erroneous behavior where player damage difficulty scaling is applied twice to damage from area blasts and shockwaves, greatly changing the effective difficulty scaling. This is a ''bug'' that should not be enabled, unless the mod was balanced during the time between 3.6.14 and 23.1 (mods [[Game_settings.tbl#.24Target_Version:|targeting within those versions]] automatically have this flag enabled).
*Syntax: '''''Boolean'''''}}

===$debris affected by physics whacks:===
{{Table232|
*Allows debris to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$asteroids affected by physics whacks:===
{{Table232|
*Allows asteroids to be affected by physics whacks from weapons.
*Syntax: '''''Boolean'''''}}

===$dynamic goals afterburn hard:===
{{Table232|
*Will cause all dynamic goals (such as a fighter defending itself, or a fighter chasing an attacker as part of a guard order) to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$player orders afterburn hard:===
{{Table242|
*Will cause all player orders to 'afterburn hard' as the optional argument on ai-goals do.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use tactical disarm/disable:===
{{Table234|
*Will cause disarm or disable orders issued by the hud squadmsg menu (i.e. player orders) to be 'tactical' goals that do not cause the target to be protected from attack.
*Syntax: '''''Boolean'''''}}

===$hud squad messages use ai-form-on-wing-new:===
{{Table250|
*Will cause form-on-wing orders issued by the hud squadmsg menu (i.e. player orders) to be the 'new' variant that does not clear other goals assigned to the same ship/wing.
*Syntax: '''''Boolean'''''}}

===$align to target when guarding stationary ship:===
{{Table242|
*Will cause ships to match the target's orientation when following a guard order, rather than facing directly away from the target which is the normal behavior.
*Syntax: '''''Boolean'''''}}

===$rotation factor multiplier for player collisions:===
{{Table242|
*Allows modders to have players experience rotational effects from collisions. This value is multiplied by the value of [https://wiki.hard-light.net/index.php/Ships.tbl#.2BRotation_Factor: $Collision Physics: +Rotation Factor:] in the ships table (which is specified for the ship class).
**Syntax: '''''Float''''' (defaults to 0.0)}}

===$fix avoid-shockwave bugs:===
{{Table250|
*Fixes a number of bugs affecting the behavior of AI ships trying to avoid ship or weapon shockwaves. With this flag enabled, the AI will be aware of the correct homing position and impact position of the weapon being evaded, will check the correct ship for shockwave damage, and will properly update stale shockwave-avoidance data. See PR 6378 for more details.
*Syntax: '''''Boolean'''''}}

===$standard strafe used more:===
{{Table250|
*Sets if the AI tries to always entry strafe mode when attacking large ships even if there are no hostile fighters nearby. By default the AI will only entry strafe mode if the speed is below '$standard strafe triggers under this speed:' and enemy fighters are nearby.
**Syntax: '''''Boolean'''''}}

===$fix standard strafe:===
{{Table250|
*If set, this will allow AI to be more effective when attacking big ships in standard strafe mode. With this flag off, there were edge cases where the AI would fly to a point to start a strafe, then think it would collide with the target and then retreat from strafe mode, only to realize it was now far enough to re-engage strafe mode, which commonly resulted in AI just flying around not accomplishing much.
**Syntax: '''''Boolean'''''}}

===$standard strafe triggers under this speed:===
{{Table250|
*Sets the velocity under which the AI checks if they should enter strafe mode when attacking large ships. Setting this value higher and enabling $standard strafe used more:' will result in the AI strafing by continually moving, instead of parking next to a big ship and blasting it while not moving.
**Syntax: '''''Float''''' (defaults to 3.0)}}

===$strafe distance from target bounding box:===
{{Table250|
*Sets the distance at which the AI flies away from their target's bounding box to attempt a strafing run when attacking large ships. Setting this value higher will result in ships doing fewer longer distance strafing runs.
**Syntax: '''''Float''''' (defaults to 300.0)}}

===$strafe stops after time unhit:===
{{Table250|
*Sets the time duration of a strafing run when attacking a big ship if the attacking ship has not been hit. After this time elapses the AI will stop the current strafing run and loop back to logic of determining of whether or not to do another strafing run. Set higher to allow for longer duration strafing runs.
**Syntax: '''''Float''''' (defaults to 20.0)}}

===$guard uses big-orbit for target radius above:===
{{Table250|
*Sets the radius of a guardee ship that will trigger the guarder to use the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. This 'big guard' mode differs from normal guard, where the AI will attempt to match the speed of the guardee if it is moving, and if it is stationary, it will fly somewhat randomly in circles around it.
**Syntax: '''''Float''''' (defaults to 500.0)}}

===$guard with big-orbit uses max speed percent:===
{{Table250|
*Sets maximum percent velocity of a guarder ship when it is using the 'big guard' mode, which is where the guarder will fly around the guarder following a cylindrical shape. By default, this value is 1.0, where the AI will fly around this cylindrical shape at full throttle. Value must be greater than 0 and less than or equal to 1.
**Syntax: '''''Float''''' (defaults to 1.0)}}

===$unify usage of AI Shield Manage Delay:===
{{Table250|
*Specifies all AI ships to use their specific AI class shield manage delay. By default, Friendly ships always use the second value in '''AI Shield Manage Delay:''' from default AI profile.
*Syntax: '''''Boolean'''''}}

===$fix AI shield management bug:===
{{Table250|
*Fixes an edge-case bug with shield management where the AI will not direct shield energy to a quadrant if it was hit when that quadrant was down. In other words, if a shield quadrant is knocked down to 0 and continues to be shot the AI will not realize it needs to direct energy to that quadrant. Enabling this flag allows the AI to properly recognize which quadrant is in danger and needs additional recharge.
*Syntax: '''''Boolean'''''}}

===$AI balances shields instead of directs when attacked:===
{{Table250|
*By default, FSO AI on ships that manage shields will direct shield energy to a quadrant that was recently hit. If this flag is enabled the AI will always balance shields instead, which can be useful depending on the situation.
*Syntax: '''''Boolean'''''}}

===$disable AI transferring energy:===
{{Table250|
*Prevents AI ships from transferring energy between weapons and shields. AI ships are allowed to attempt transferring energy by default, but some mods may disable this feature for the mod and wish to also ensure the AI does not use it.
*Syntax: '''''Boolean'''''}}

===$enable freespace 1 style missile behavior:===
{{Table250|
*Enables a set of behaviors observed from missiles in the Freespace 1 release.
**Detonate when within 50 meters and not pointing at their target.
**Move slower than normal when not pointing at their target.
**Aspect seekers follow a -1x lag pursuit scalar for the last second before hitting their target.
*Note that the last point will make aspect seekers much less likely to hit moving targets.
*[[Weapons.tbl#.22freespace_1_missile_behavior.22|Can be applied on a per-weapon basis]]
*Syntax: '''''Boolean'''''}}

===$ETS uses ship class power output:===
{{Table250|
*Connects the '''$Power Output:''' field in a ship class entry to the ETS system. The ship's power output will serve as a multiplier for ETS energy flowing to guns, shields, and engines, modifying their recharge rates accordingly.
*Syntax: '''''Boolean'''''}}

===$ETS energy same regardless of system presence:===
{{Table250|
*Pro-rates available ETS energy according to the number of systems available. Normally, for ships without a shield system, FreeSpace behaves as if all shield energy is redirected to guns and engines. Consequently, weapons and afterburner will recharge faster, and a ship's default speed will be higher, than if shields were present. When this flag is enabled, available ETS energy is scaled so that the rates are the same in both situations.
*This flag presents certain trade-offs. On one hand, this flag avoids the possibly surprising behavior of ships performing, in shieldless engagements, better than one might expect from the table entry. On the other hand, see the next bullet point.
*Modders should consider both the gameplay and story aspects of this flag. From an in-universe perspective, enabling this flag means that, on a shieldless ship, the energy that would otherwise go to shields is expended without effect and is wasted. Or, looking at it another way, it means that upgrading a ship to have a shield system also entails upgrading the reactor to deliver 50% more energy.
*Syntax: '''''Boolean'''''}}

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

Game settings.tbl

2025-06-25T02:38:57Z

Wookieejedi: add new sound flags, too

{{SCP_table}}
{{TableVersionGit|2025-02-10|642111676012bc6696f4024c40296a6c20b3b958}}
{{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

If the version targeted in [[game_settings.tbl#$Target_Version:|target version]] is equal to or later than these listed, the following options are enabled by default:
{{Table220|
*[[game_settings.tbl#$Fixed_Turret_Collisions:|Fixed Turret Collisions]]
*[[game_settings.tbl#$Fixed_Missile_Detonation:|Fixed Missile Detonation]]
*[[game_settings.tbl#$Shockwaves_Damage_All_Object_Types_Once:|Shockwaves Damage All Object Types Once]]
*[[game_settings.tbl#$AI_use_framerate_independent_turning:|AI use framerate independent turning]]
*[[game_settings.tbl#$Use_host_orientation_for_set-camera-facing:|Use host orientation for set-camera-facing]]
}}
{{Table230|
*[[game_settings.tbl#$Shockwaves_Inherit_Parent_Weapon_Damage_Type:|Shockwaves Inherit Parent Weapon Damage Type]]
*[[game_settings.tbl#$Fixed_Chaining_To_Repeating_Events:|Fixed Chaining To Repeating Events]]
}}
{{Table240|
*[[game_settings.tbl#$Calculate_subsystem_hitpoints_after_parsing:|Calculate subsystem hitpoints after parsing]]}}

==#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'''''
}}
{{Table250|
It is now possible to display the mod title on its own. Previously, the mod version was also required.
}}

===$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'''''
}}
{{Table250|
It is now possible to display the mod version on its own. Previously, the mod title was also required.
}}

===$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'''''}}

===$Splash screens:===
{{Table232|
Defines a list of splash screens that FSO can display upon game startup. The actual image displayed is chosen at random from the applicable entries. Entries with exact aspect ratio matches will be prioritized first, followed by aspect ratio ranged matches, followed by entries without an aspect ratio specified.}}

====+Bitmap:====
{{table232|
The name of the bitmap to use as a splash screen. Extension will be removed if included.
*Syntax: '''''+Bitmap: String'''''}}

====+Aspect Ratio:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio matches the specified number within +/- 0.01.
*Syntax: '''''+Aspect Ratio: Float'''''}}

====+Aspect Ratio Min:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at least the specified number.
*Syntax: '''''+Aspect Ratio Min: Float'''''}}

====+Aspect Ratio Max:====
{{table234|
Only consider this bitmap to be an applicable entry if the user's screen aspect ratio is at most the specified number.
*Syntax: '''''+Aspect Ratio Max: Float'''''}}

===$Splash fade in time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade in.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Splash fade out time:===
{{Table232|
Sets the time in milliseconds it takes for a splash screen to fade out.
*Syntax: '''''Integer'''''
*Default Value: '''''0'''''}}

===$Center splash logo:===
{{Table232|
Sets whether the splash logo will be displayed in the middle of the screen. If this is false (the default), it will be displayed at the top-left.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$Disable FSO Internal Loadout Restoration System:===
{{Table234|
When the player configures the ships and weapons of the wings in the loadout screen, FSO will remember these settings and attempt to apply them again if the player quits the mission and comes back to it later. FSO will only remember the most recent mission's loadout, so it will not attempt to restore the loadout if the player loads a different mission. It will also not attempt this if the mission's ''$Modified:'' date has changed. This flag can be used to prevent FSO from attempting restoration even if it normally would.
*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'''''
}}

===$HUD drop shadows enabled by default:===
{{Table232|
If this flag is active, certain elements displayed on the HUD (all text, the main targeting reticle, and the background of the ETS gauges) will have a "drop shadow" effect. Note that whether or not the flag is active, the player can set this using the "Toggle HUD Drop Shadows" control.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Unify scanning behavior:===
{{Table242|
*Unifies scanning behavior between subsystem, regular, and cargo allowing missions to use all scan types in all situations.
*Also allows changing the "Cargo:" text line in a mission by adding "$Cargo Title: STRING" after the "$Cargo 1:" or "$Cargo 2:" lines in the mission file. FRED UI support not yet added for $Cargo Title so you have to do it manually.
*When this flag is enabled, all ships, no matter the ship class, will react the same way to the cargo-related or scanning-related ship flags:
**They are not scannable by default
**Setting the "scannable" flag makes them scannable, and scanning the subsystem will reveal the cargo
**A new flag available with alter-ship-flag, "no-scanned-cargo", changes the behavior to scanned/unscanned instead of revealing the cargo
**The "toggle-subsystem-scanning" flag must be set to swap full-ship scanning mode into subsystem scanning mode and works for all ship types
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''
}}

===$Don't show callsigns in the escort list:===
{{Table242|
By default, callsigns are shown in the escort list using the same format as in the target box. If this flag is active, callsigns will not be displayed.
*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'''''

===$Fixed Chaining To Repeating Events:===
{{Table230|When set, this makes event chaining to repeated events work as designed - that is, the chained event will only be evaluated after the chain delay. If the repeating event's interval is shorter than the chain delay, then the delay countdown will continually be restarted until all repetitions have completed. Without this flag, FSO will emulate retail behavior which, due to a bug, allowed chained events to be evaluated immediately after a repeating event is first evaluated.

NOTE: Although the name does not reflect it, the same issue affects repeating events that are evaluated by <tt>is-event-true-delay</tt> and <tt>is-event-false-delay</tt>. Without this flag, FSO will emulate retail behavior which causes these SEXP operators to ignore any delay when evaluating repeated events. With this flag, the delay will be measured from when the final repeat iteration occurs.
*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)'''''}}

===$HUD-set-coords base resolution:===
{{Table232|The hud-set-coords SEXP has always used exact pixels, without regard for the current screen resolution. This setting enables a similar scaling mechanism as ''$Show-subtitle base resolution:''.
*Syntax: '''''(Integer, Integer)'''''
*Default Value: '''''(-1, -1)'''''}}

===$$Always Show Directive Value Count:===
{{Table250|
*If this setting is enabled, Directive-as-Value values in Directives will always show the number. By default this is disabled, and only values > 1 are shown.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

==#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'''''}}

===$EMP Pain Flash Factor:===
{{Table224|
Determines the intensity of the flash when the player is hit by an EMP blast or weapon.
*Syntax: '''''Float'''''
*Default Value: '''''1.0'''''}}

===$EMP Pain Flash Color:===
{{Table224|
Determines the RGB color value of the flash when the player is hit by an EMP blast or weapon.
*Syntax: Color, (red, green, blue) respectively, integer value from 0 to 255
*Default Value: '''''(255, 255, 127)'''''}}

===$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)
}}

===$EMP Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)
}}

===$Damage Arc Width:===
{{Table224|
Allows setting how the width is calculated for the EMP lightning arc effect.
*'''+Width Default:'''
**The default width of the arc. This value will be multiplied by `+Width Radius Multiplier:` if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.9
*'''+Width Radius Multiplier:'''
**The value that the width is multiplied by if the radius of the ship is less than or equal to `+Do Not Use Width Multiplier Over Radius:`.
**Syntax: '''''Float'''''
**Default value: 0.01
*'''+Do Not Use Width Multiplier Over Radius:'''
**If the object is larger than this radius, the `+Width Default:` value is used.
**Syntax: '''''Float'''''
**Default value: 500
*'''+Width Radius Minimum:'''
**Minimum width that the arc can be. Any calculated widths lower than this value will be set to this value.
**Syntax: '''''Float'''''
**Default value: 0.2
}}

===$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)'''''}}

===$Shadow Disable Techroom:===
{{Table224|
Disables shadows on ships in the techroom.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Cockpit:===
{{Table224|
Disables shadows on the player cockpit in mission.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Weapons:===
{{Table224|
Disables shadows on weapons in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Shadow Disable Mission Brief Ships:===
{{Table224|
Disables shadows on ships in the mission briefing.
*Syntax: '''''Boolean'''''
}}

===$Show Ship Casts Shadow:===
{{Table224|
When cockpit shadows are enabled, enabling this setting will cause the players ship model shown with "show ship" to cast shadow onto the cockpit.
*Syntax: '''''Boolean'''''
}}

===$Ship Model And Cockpit Share Coordinate Space:===
{{Table224|
When having the "show ship" flag enabled and cockpit models for a ship, this flag should be on if the cockpits can fit into the actual geometry of the ship model. Disable this flag if this is not the case and the cockpit needs to be rendered on top of the ship regardless of actual coordinates. If this can be enabled, the external show ship model can be rendered using deferred rendering.
*Syntax: '''''Boolean'''''
}}

===$Show Ship enabled only if Cockpits enabled:===
{{Table250|
Enabling this setting will only use the 'show-ship' flag if cockpits are enabled. Useful if your ship uses both 'show-ship' and cockpits that exist within the 'show-ship' space, and you want to allow players to toggle off cockpits. Note, 'show-ship' always only appears if in first-person view.
*Syntax: '''''Boolean'''''
}}

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

===$Do Not Render Lasers Below Length:===
{{Table250|
*Specifies the smallest length that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Do Not Render Lasers Below Radius:===
{{Table250|
*Specifies the smallest radius that lasers will be rendered.
*Syntax: '''''Float'''''
*Default Value: 0.0001}}

===$Thruster Easing Value:===
{{Table220|
*Smooths out the behavior of maneuvering thruster flares the higher above 0 it is.
*This is the exponential time constant for the visual flare length to reach it's true length.
*Syntax: '''''Float'''''
*Default Value: 0.0}}

===$SCPUI attempts to load hires animations:===
{{Table230|
*Prevents SCPUI from trying to load anims prefixed with "2_"
*Syntax: '''''Boolean'''''
*Default Value: true}}

{{Table230|
===$Max draw distance:===
===$Min draw distance:===
*These values do more than just cutoff the visuals at certain distances, and they must be adjusted carefully to ensure unintentional rendering artifacts are not introduced.
*The rendering engine has limited amount of 'depth resolution', the degree to which it can tell a certain polygon is closer or farther away than another. When two polygons are too close, they will Z-fight, picking arbitrarily which is closer. It is the span between the min and max draw distance that determines how well the engine can determine depth, if they are too far from one another, the Z-fighting will become more common as it has to spread its resolution over a wider range. If they are close, Z-fighting will be lessened at the cost of a smaller range of distance able to be rendered.
*Syntax: '''''Float''''', meters
*Default Values: 10,000,000,000 and 1, respectively
}}

{{Table232|
===$Randomize particle rotation:===
*Particle bitmaps are typically screen-aligned; the upper portion of the bitmap will always be mapped to the upper portion of the particle, from the point of view of the camera. Enabling this option makes ''all'' particles have a random 'tilt' in an arbitrary direction when created.
*Syntax: '''''Boolean'''''
*Default Value: false
}}

===$Disable shield effects:===
{{Table250|
*Specifies if FSO attempts to use the shield mesh impact effects. Enabling this flag will prevent the game from preforming any shield mesh effect code, which can be useful if a mod does not use those shield mesh effects.
*Syntax: '''''Boolean'''''
*Default Value: false}}

==#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'''''}}

===$Use weapon class impact sounds for hits to player:===
{{Table224|
Allows weapons that hit the player to play their specific impact sounds, not the hard-coded default sounds.
*Syntax: '''''Boolean'''''
}}

===$Play thruster sounds for the player:===
{{Table232|
If the player's ship has thruster sounds defined, this will ensure they are played like normal, since they are typically suppressed.
*Syntax: '''''Boolean'''''
}}

===$Unify minimum engine sound:===
{{Table250|
Allows $Minimum Engine Volume in ships.tbl to work for all ship classes. By default, that value only triggers for non-huge ships.
*Syntax: '''''Boolean'''''
}}

===$Disabled or disrupted engines are silent:===
{{Table250|
If set, engines will not play their engine noise if the ship is disabled or a disrupted (such as disruptions caused by an active EMP effect or a weapon with the "electronics" flag).
*Syntax: '''''Boolean'''''
}}

==#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'''''}}

===$Add Message Head Ani Files:===
{{table224|
FRED will append each +Head entry listed below to the head ani selection list in the Event Editor.}}

====+Head:====
{{table224|
The head ani filename to add. Extensions will be stripped if included.
NOTE: Pay attention to file names or anis with a,b, c variation not display in-game (unless called directly). Proper name seems to be Head-xxxNa, Head-xxxNb, with N being some number and XXX being whatever you want. Needs further testing and confirmation
*Syntax: '''''+Head: String'''''}}

===$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'''''}}

===$FRED Briefing window resolution:===
{{table224|
The width and height of the briefing window in FRED. Defaults to 888x371. Note that changing this only affects FRED and can cause a mismatch to the ingame briefing view which defaults to 888x371 (or 555x232 for 640 base res).
*Syntax: '''''integer, integer'''''
*Default Value: '''''888,371'''''}}

===$Ignore Music Files In Music Player:===
{{table232|Music files in this section will not be added to FRED's built-in music player.}}
====+File:====
{{table232|Specifies a file
*Syntax: '''''string'''''}}

===$FRED spacemouse nonlinearities:===
{{table232|
Allows setting custom nonlinearities and scaling for controlling FRED with a spacemouse.
}}
====+Sideways exponent:====
{{table232|
The exponent for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Sideways scale:====
{{table232|The multiplier for input for Sideways spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards exponent:====
{{table232|The exponent for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Forwards scale:====
{{table232|The multiplier for input for Forwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards exponent:====
{{table232|The exponent for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Upwards scale:====
{{table232|The multiplier for input for Upwards spacemouse motion.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch exponent:====
{{table232|The exponent for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Pitch scale:====
{{table232|The multiplier for input for Pitch spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank exponent:====
{{table232|The exponent for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Bank scale:====
{{table232|The multiplier for input for Bank spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading exponent:====
{{table232|The exponent for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}
====+Heading scale:====
{{table232|The multiplier for input for Heading spacemouse rotation.
*Syntax: '''''float'''''
*Default Value: '''''1'''''}}

==#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. This fixes missile impacts to submodels whose center lies outside the geometry of the submodel. In other words, without this flag, a missile might detonate in the middle of the "bowl" of a concave submodel; with this flag, the missile will travel to the other side of the submodel before it detonates.
*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'''''

===$Use 3d ship select:===
{{Table224|
*Whether or not to use 3D models for ship select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d ship icons:===
{{Table224|
*Whether or not to use 3D models for ships in ship/weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d weapon select:===
{{Table224|
*Whether or not to use 3D models for weapon select instead of animations
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

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

===$Use 3d weapon icons:===
{{Table224|
*Whether or not to use 3D models for weapons in weapon select instead of icons
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Use 3d overhead ship:===
{{Table224|
*Whether or not to use 3D models for ship overhead view instead of a bitmap in weapon select
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Default overhead ship style:===
{{Table224|
*This specifies which style of overhead view to use if 3d overhead view is active
*Syntax: '''''String'''''
*Possible options are "ROTATE" or "TOPVIEW"}}

===$Always refresh selected weapon when viewing loadout:===
{{Table232|
*When set to true, this always refreshes the weapon shown in view box on the right side of the screen when opening the weapon loadout view. This ensures the viewed weapon is one that can actually be on the selected ship when first clicking on the weapon loadout screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''NO'''''}}

===$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|
*Mode whereby various settings can be modified by FSO while it's still running, rather than being set by the launcher before execution. By default is now ON, and can be accessed by going to the Options menu and pressing F3.
*Syntax: '''''Boolean'''''
*Default Value: '''''YES'''''}}

===$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'''''}}

===$Apply HUD shudder to chase view:===
{{Table232|
*Applies hud shudder (afterburner and engine wash) also to chase view. Does not override the command line toggle.
*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'''''}}

===$Lead indicator behavior:===
{{Table224|
Changes how Lead Indicators behave when multiple weapon banks are linked and in range.
When set to default, if you have linked weapons, only the indicator for the one with the farthest range will be drawn.
When set to multiple, a lead indicator is drawn for all primary weapons in range when you have them linked.
When set to average, a single lead indicator is drawn in the average of the position where each of them would usually be drawn.
*Syntax: '''''String'''''
** Valid options are '''''default''''', '''''multiple''''' and '''''average'''''
*Default Value: '''''default'''''
}}

===$Use distant firepoint for all turrets:===
{{Table224|
*Causes the game to use firepoint-based target leading calculations for all turrets. This is useful if all or most turrets in a given mod has firepoints that are distant from their center-point.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Enable discord rich presence:===
{{Table224|
*Enables or disables the built-in Discord game-status reporting.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Always hide hidden ships in hotkey list:===
{{Table224|
*Whether or not to always hide ships with HIDDEN hotkey (set in FRED), even in the in-mission hotkey menu.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Allow automatically assigning personas:===
{{Table232|
*Whether or not the game will automatically assign personas to ships that have no persona set.
*Syntax: '''''Boolean'''''
*Default Value: '''''True'''''}}

===$Countermeasures use capacity:===
{{Table232|
*Whether or not Countermeasures use tabled capacity.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Calculate subsystem hitpoints after parsing:===
{{Table234|
*Causes subsystem hitpoints to be calculated after all ships.tbl and -shp.tbm files have been parsed. This allows subsystem percentages to correctly reflect the final hull value rather than the first hull value encountered.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Fix scripted velocity:===
{{Table242|
*If this setting is enabled, object velocity set via script will wholly determine the change in position for that frame, ignoring ''all'' other in-engine concerns. Otherwise, the game engine will likely overwrite/ignore any changes, depending on when the changes were made in the frame.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Preload briefing icon models:===
{{Table250|
*If set, this forces preloading of models used for briefing icons. This only loads models used for icons that haven't already been loaded for the mission. This is useful for SCPUI's where hovering over an icon shows the model without having to click on it and the stutter when it loads models not used in mission.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Behavior for pressing Escape key in options menu:===
{{Table250|
*If set to 'save', the escape key for the HUD and Options screen saves options when leaving those screens (ie it does the same thing as pressing Ctrl-Enter/Accept). By default (or if set to 'default') the Escape key will not save any changed values when exiting those screens.
*Syntax: '''''String'''''
*Default Value: '''''default'''''}}

===$Disable intro cutscene:===
{{Table250|
*If set, this disables loading of any cutscenes as the game starts that might play before the player reaches the pilot select screen.
*Syntax: '''''Boolean'''''
*Default Value: '''''False'''''}}

===$Show locked status for scramble missions:===
{{Table250|
*If set, scramble mission will show a text line right below the words 'Weapons Loadout' that states "Ships/Weapons Locked" (XSTR 749), thus the player can easily see their loadouts are locked and they do not have to check the loaoout buttons on every mission.
*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]]