FreeSpace Wiki - User contributions [en]

Talk:Rampage's Post Modding Guide

2023-01-19T18:25:18Z

Qazwsx: Qazwsx moved page Talk:Rampage's Post Modding Guide to Archived talk:Rampage's Post Modding Guide

#REDIRECT [[Archived talk:Rampage's Post Modding Guide]]

Archived talk:Rampage's Post Modding Guide

2023-01-19T18:25:18Z

Qazwsx: Qazwsx moved page Talk:Rampage's Post Modding Guide to Archived talk:Rampage's Post Modding Guide

Just a quick copy paste from the wayback machine. I'll fix it up later. [[User:Black Wolf|Black Wolf]] 18:54, 14 June 2010 (UTC)

I have to ask though, is this worth having? Does this contain info that the other guides don't have? [[User:The E|The E]] 14:20, 15 June 2010 (UTC)

I personally found it much clearer and easier to understand while using TS to convert the Canberra than any of the articles that were on the wiki. It can't hurt. [[User:Black Wolf|Black Wolf]] 16:06, 15 June 2010 (UTC)

Rampage's Post Modding Guide

2023-01-19T18:25:18Z

Qazwsx: Qazwsx moved page Rampage's Post Modding Guide to Archived:Rampage's Post Modding Guide

#REDIRECT [[Archived:Rampage's Post Modding Guide]]

Archived:Rampage's Post Modding Guide

2023-01-19T18:25:18Z

Qazwsx: Qazwsx moved page Rampage's Post Modding Guide to Archived:Rampage's Post Modding Guide

==Prerequisites==
In order to master Post MOD MODding, you must first know the interface of trueSpace, how to model in general in the program that you like the most (E.G. Blender, 3DS MAX, Rhino 3D, etc.). Second, you must know basic mathematics, which includes interval notation (commonly used in this manual), some algebra, and most important, basic, 3D geometry to make a decent model.

==Requirements==
In order to MOD well for FreeSpace 2 and its community, you must have certain modeling tools. These tools are as follows:
* trueSpace [1.0, latest version] (Recommended for Practically Everything in Regards to Modeling. Preferred version: 4.0 and Above)
* trueSpace 2.0 <<Download>>
* Adobe Photoshop [5.0, latest version] or Paint Shop Pro [5.0, version]U[version, latest version] (Recommended for Texture Bitmap Processing)
* Lithunwrap (Recommended for Model Texturing)
* Lithunwrap <<Download>>
* 3D Exploration (Recommended for Model Conversion from Other Model Forms. I think it was replaced by a stronger, better program.)
* 3D Exploration Trial Version <<Download>>
* POF Construction Suite (Recommended for POF Editing)
* POF-CON
* DMTOOLS ModelView32 (Recommended for POF Viewing and some Editing)
* COB2FS2 (Recommended for Germane POF Conversion from COB file when POF Construction Suite Can't Process the COB File. Don't you have strong animosity that "stack overrun protection" thing in POF-Con?)
* And Other Tools, Whenever They May Apply
These Tool(s) are not recommended by us:
* Segeltuch (If You Want to Make Shields, Learn How to Model! No offense)

==Making LODs (Levels of Detail)==
The LOD is the representation of a model in a mode of detail. In FreeSpace 2, the first LOD (or LOD 0) is displayed on some models when the player ship (in interval notation) is (0, 500) meters or closer to the model it represents. The second LOD is displayed when the player ship is (500, 750) meters from the model it represents and so on and so forth.
The first level of detail is comprised of every piece of geometry without a local light separating it from the main group. The first LOD or LOD 0 is the main group. First level sub-objects of the model belong to LOD 0. To make other LODs, you must have a geometry model or several geometry models grouped and everything else pertaining to that LOD, such as thruster and turret sub-models, set to go into a sub-object named "detailx", where x is the LOD number. This number must be (in interval notation) [1,4]. Also make sure that you glue a light to each and every LOD. (It doesn't matter if you have 1 sub-model (not sub-groups, E.G. LOD1 thruster model is a separate group with its own light.) or 20 sub-models in your LOD, it's just ONE light named "detailx-light".) (So detail1 would represent LOD 1 and detail 2 would represent LOD 2, and so forth.) Glue the sub-object "detailx" as sibling to the LOD 0 chunk. (This means that "detailx" is a sub-object on the first hierarchy level of the model.) When everything is done, make sure that you glue the LOD subgroups to the main model group in ascending order (detail1, detail2, detail3, etc. Thanks to StratComm!)

==Making Debris==
Debris subobjects are geometry chunks shown by FreeSpace 2 when the ship is destroyed. We suspect that you know how to make debris pieces geometrically by separating several highlighted faces from the main object. After you obtain your debris geometry models, glue each geometry model to a local light as sibling so you obtain a subobject group with exactly one model chunk with its corresponding light. Name this group "debrisy", where y starts with one and end with the number of independent debris chunks you want in your model. For example, name the first sub-model chunk "debris1" and the second "debris2" and so on and so forth. Debris groups should not have subgroups, but CAN have submodels. (You can have as many models you want to represent a single piece of debris.) Glue every one of these debris sub-models as sibling to LOD 0, which means that debris subobjects are on the first hierarchy level of your model.

==Making Thrusters==
Thruster models are what FreeSpace 2 show when a ship (probably a fighter or a bomber) moves from one place to another. We suppose that you already have a geometry model or models ready and positioned somewhere in your model when we begin the process of making thruster sub-models. When you are ready to begin, select all of the independent geometry models pertaining to the thruster or thrusters you want to make. Glue all the thrusters' geometry models to one local light as sibling and name it "thruster01". You only can have one thruster sub-model per LOD, for all thrusters you may have in different places on the model in the given LOD.

==Making Shields==
Shields protect a ship in FreeSpace 2 from being destroyed quickly. We suppose that you already have a geometry model or models ready and positioned somewhere in your model when we begin the process of making shield sub-models. One important thing is that all shield geometry models must be triangulated and also must have a monotone color as its texture. When you are ready to begin, select all of the independent geometry models pertaining to the shield of your model. Glue all the shield's geometry models to one local light as sibling and name it "shield". You only can have one shield submodel, for all independent shields you may have in your model.

==Making Single (Octagonal) Turrets==
This process is a little bit more complex than the other processes mentioned above, but it's not difficult compared to making Multi-part Turrets. You should have made and positioned your turret models before you begin the process described below. It's important that you do the turret process in the order given below. First, relinquish control of all turret geometry models within a hierarchy and unglue them or move them (through TrueView) out of your model and into the entire scene. This is critical for the next step. Second, you must set an axis for every turret geometry model you plan to use in your model. To do this, you must find the "Centralize Axis" button. It is found in the sub-menu in trueSpace's "Normalize Scale". It looks like a x-y-z axis next to an orange wireframe cube. Before you click on it, you must have the geometry model that you want the axis to apply selected. Then after you have it selected, click on the "Centralize Axis" button. Your turret geometry model should become highlighted orange and a small (or big) axis should appear. After the axis becomes highlighted, find the "Normalize Rotation" button and hit it once. After doing so, you're done with this part. You may choose to delete the axis, but it is suggested that you leave the axis where it is. To exit out of axis-editing mode, just click on another object. Now go back to the geometry model and make a "Local Light". Move the light to the center of the turret model that you had the axis applied to and glue it to the light as sibling. Name this new sub-model selection "turretz" where "z" is the number from "01" to the number of your last octagonal turret (turret01, turret02, turret03, turret04 for every octagonal turret you want in your model.). It is important to make the number a two-digit number. Repeat the process for every octagonal turret you want in your model. When you are done with the sub-models for all the simple turrets, glue them one by one to your main model sub-object or detail sub-object as child or just move them to their corresponding location in your model hierarchy via TrueView.

==Making Multi-part Turrets==
This is probably the most difficult part in after-mod MODding. We still expect that you have positioned your multi-part turrets in their appropriate places before you begin the process described below. You'll need one turret base geometry model and at least one turret barrel geometry model per turret. When you have the models set in the position that you want them to be at, start applying axis to the turret base. The axis should be centralized by using the "Centralize Axis" button in trueSpace and afterwards moved to the very bottom of the turret base, for it to rotate correctly in FreeSpace 2. Also note that the turret base must be independent from EVERYTHING or it will not rotate correctly in FreeSpace 2. (In simple words: "Make sure that the turret geometry model is independent of EVERYTHING when applying the axis to the turret base model.") This also applies to the turret barrel, which is covered in the next step. Next, select the turret barrel and click on the "Centralize Axis" button. Move the axis to the bottom of the barrel (If you do this correctly, the turret barrel shouldn't float in mid-space when rotating in FreeSpace 2.). Repeat this step for every multi-part turret in the model. (See StratComm's alternative below.) When you are done, glue each turret barrel to a local light and name the group "turretz-arm", where "z" is the turret number. (Turret15-arm, Turret16-arm, etc.) After you have the turret barrel geometry models glued to its corresponding local light, use the same process to glue the turret base geometry models together with its corresponding local light. Name the turret base group "turretz", where "z" is the turret number (turret15, turret16, turret17, etc.). The next step is very important. You must glue the turret barrel sub-object to the turret base sub-object as child. Or you can just drag and drop the turret barrel sub-object into the turret base sub-object via TrueView. Finally, glue the turret base as child to the main model sub-object or detail sub-object.
====StratComm's Way====
Make multi-part turrets in a separate scene, do the axis part, arrange the groups, save it as a COB file, and import it into your model afterwards. After importing the turret into the main model, then rename it according to the sequence in the model.

==Making Subsystem Models==
This practically uses the same process for making octagonal turrets. Before we begin, position the subsystem geometry models in the respectable places. Now relinquish control of every subsystem geometry model from the main model and its corresponding light and unglue both out of the model. Now use the "Centralize Axis" button to apply an axis to a selected subsystem geometry model. Repeat the process for any other subsystem geometry models you might have for this model. After you applied the axis to every one of the subsystem geometry models, glue each geometry model to a local light as sibling. Name the sub-model "[subsystem-name]x", where "[subsystem-name]" is the name of the subsystem and x is the number of the subsystem, if "[subsystem-name]" is the same (I.E.: reactor01, reactor02, reactor03, etc.). Repeat the process for any other subsystem geometry models. Finally, glue the subsystem sub-objects to the main model or detail sub-object as child or drag and drop the subsystem sub-object into the main model sub-object or detail sub-object via TrueView.

==Making Subsystem and Turret Debris==
This process is similar to that of making thrusters and shields. Have the debris chunks ready and positioned in their respectable spots so we can begin. First, glue the debris geometry model to its corresponding light and name it "[subsystem/turret-name]y-destroyed", where "subsystem/turret-name" is the name of the subsystem or turret and "y" is the subsystem/turret number. Repeat for any other subsystem/turret debris you want for your model. After finishing off the debris sub-models, glue them as child to the main model sub-object or detail sub-object or drag and drop them to their corresponding location via TrueView. Important: DO NOT glue the subsystem/turret debris sub-objects to their corresponding subsystem or turret!

==Conclusion==
MODding is an art, a work of beauty. 3D designers are the core of this-art. Without them, Freespace 2 would be just three dislocated CDs sitting in our closets collecting dust particles. With our faithful 3D designers, Freespace 2 has surpassed every other game in its genre, even the old Descent series. The community continues to grow and "newbies" continues to flood in. In order to improve our community, we must teach these novices the art of 3D modeling.

[[Category:Modding]]

User:Qazwsx

2023-01-19T10:11:58Z

Qazwsx: Created page with "qazwsx on the forums, qazwsxal on the discord. Projects: SCP graphical enhancements - 23.0 shader update and environment lighting. As-yet-unreleased Warhammer 40k TC/Ship P..."

qazwsx on the forums, qazwsxal on the discord.

Projects:

SCP graphical enhancements - 23.0 shader update and environment lighting.

As-yet-unreleased Warhammer 40k TC/Ship Pack

Knossos Successor - [https://github.com/qazwsxal/sol-gate sol-gate] MEGA WIP

Manually Installing FreeSpace 2 Open

2023-01-17T14:27:00Z

Qazwsx: Make it very clear that you should probably be using knossos.

<span style="font-size:125%; font-weight:bold; color:red">This page covers installing FSO and associated mods by hand. It is STRONGLY RECCOMENDED to use the [[Knossos (mod manager)]] as it considerably streamlines and automates the whole process.</span>
<br/> <br/>

This guide assumes you already have a working copy of FreeSpace 2 installed. If not, see [[Installing FreeSpace 2]].

== Step One: Understanding what you need ==
There are three main components that you need to get the most out of fs2_open.

* First, you need to install the retail data from [[Installing FreeSpace 2|FreeSpace 2]]
* Second, the '''fs2_open build'''. This is the core game engine, a single executable file.
* Next, the '''launcher'''. This lets you configure the fs2_open executable for your particular system, in much the same way the original FreeSpace 2 launcher is used to configure it.
* Finally, the '''MediaVPs'''. These contain all sorts of graphical improvements and are highly recommended. Version numbers of mediaVPs generally agree with the fs2_open build that they're supposed to be used with.

== Step Two: Getting the Launcher ==

Unless you are using an extremely old build, you will want to get the appropriate launcher for your OS. It may be bundled with your release but the direct download link is below.

Windows: [http://www.hard-light.net/forums/index.php?topic=67950.0 wxLauncher]

OS X: [http://www.hard-light.net/forums/index.php?topic=67950.0 wxLauncher] unless you are using Tiger or a PowerPC Mac, in which case use Soulstorm's [http://www.hard-light.net/forums/index.php?topic=51391.0 OS X Launcher 3.0] ([[Soulstorm's OS X Launcher|instructions]])

Linux: [http://www.hard-light.net/forums/index.php?topic=67950.0 wxLauncher] (build it from source; see the [http://code.google.com/p/wxlauncher/source/browse/ReadMe.txt readme] for instructions)

== Step Three: Choosing a build ==
There are two main types of fs2_open builds, at the time of this writing. A "build" is any executable built from source code. Any build may also be a debug build. (Debug builds usually have names that end with "_d" or "_dbg" or somesuch) If you don't know why you'd want to use a debug build, you're almost certainly better off not using one.

All builds should be extracted to your main FreeSpace 2 folder.

=== Official Releases ===
The first type is the "stable" release build. Additionally, some official release builds are available with installers. It's a good idea to get the most recent official release, even if you end up deciding to get a recent build anyway. Current official release is '''FreeSpace Open 3.8.0'''.

[https://www.hard-light.net/forums/index.php?topic=93812.0 FreeSpace Open 3.8.0 release thread]

=== Test Builds ===
Recent Builds are ones that individual coders release. Most of the time they're released to either test or showcase some particular new feature. If you're curious about how reliable a build is, your best bet is to check the original thread it was posted in and see what people's responses were.

[https://www.hard-light.net/forums/index.php/board,97.0.html Test builds forum]

[https://www.hard-light.net/forums/index.php/board,113.0.html Cross Platform Development forum (for Linux/OS X builds)]

=== Nightly Builds ===

In addition to recent builds, nightly builds are built every evening after any changes have been applied to the source code. These are put out so that the code base can be quickly verified for general stability. Testing nightly builds on a regular basis and reporting bugs helps ensure a stable code base is maintained.

[https://www.hard-light.net/forums/index.php/board,173.0.html Nightly builds forum]

== Step Four: MediaVPs ==

With the release of the 3.8 MediaVPs, there is once again only one set of recommended MediaVPs available. The detailed instructions for installing and the current links can currently be found in the MediaVPs Release Thread linked below.

MediaVPs should be installed in a new 'MediaVPs_38X' directory under the main FreeSpace directory (\freespace2\MediaVPs_38X) This preserves the possibility to play with either with retail FreeSpace 2 vp files if this is desired (for example in multiplayer) and using the retail FreeSpace 2 executive files and requires minimal extra time to set up. (See step six for further details).

[https://www.hard-light.net/forums/index.php?topic=94988.0 3.8 MediaVPs Release Thread]

== Step Five: Configuring Everything ==

=== Basic setup ===

At this point, you have one final stage remaining before fs2_open is ready to go. Open up wxLauncher. Select the EXE you'd like to use from the dropdown menu in the "Basic Settings" tab. There are two types typically for any build release:
* a debug build with the name containing 'd', 'debug' or 'FASTDBG' right after the version number. For example, fs2_open_3_8_0_x64_AVX-FASTDBG.exe.
* a regular/release build with the name containing 'r' or nothing right after the version number. For example, fs2_open_3_8_0_x64_AVX.exe.

For normal play you will want to use a regular build but for any testing, development, or bug reporting you definitely want to use a debug build. For example, fs2_open_3_8_0_x64_AVX-FASTDBG.exe vs fs2_open_3_8_0_x64_AVX.exe.

Next, ensure that the "Audio/Joystick" and "Network" tabs have the proper settings.

=== Speech setup ===

If you are using Windows XP, or have the Speech API installed, fs2_open will be able to read briefings, techroom descriptions, and even ingame messages to you using computer-generated voices. Although no match for real voice acting, it is convenient when valid plot points are mentioned in the middle of combat. Speech in the various locations can be turned on and off by checking and unchecking the check boxes; you can choose which of the installed voices to use in fs2_open by changing the drop-down menu. As of this writing, fs2_open will only use the voice you choose for everything. Text to Speech is typically only available in stable release builds. Recent Builds from a coder's test branch will usually not have it, nor will Nightly Builds.

=== Video setup ===

In the "Video" section, you can choose choose various graphics options. Here, you can set the resolution as well as the colour depth. It is recommended to use a resolution greater or equal to 1024x768 at 32 bits of colour depth.

=== Mod setup ===

The "Mods" tab lets you easily switch between mods by clicking on them and hitting the "Activate" button.

This tab allow you to choose a mod directory to use; files in the mod directory will be given precedence over other files, so you can easily switch between mods by installing them to different directories.

=== Advanced setup ===

This tab is where most of fs2_open's options can be toggled on and off. At the bottom is a readout of your current command line; you should include this in any debugging reports you make.

The long list of checkboxes let you toggle the various new features in fs2_open, many of which are graphical improvements. Recommended options for midrange systems are "Enable post processing", "Enable soft particles" and "Enable FXAA anti-aliasing". There are many, many more options, but these should get you started.

"Custom flags" allows you to add any command line flags that don't show up in the Launcher. This may be because they require additional arguments, as is the case with the "-fov" command line argument. For more information, see the [[Command-Line Reference]] page.

[http://wiki.hard-light.net/index.php/Command-Line_Reference line Flags]

=== Language Setup ===

Freespace & Freespace 2 supported non-English languages such as French, German & Polish. Some mods (most notably Freespace Port) also support non-English languages. The steps required to change the language differ depending on which OS FSO is running on.

Note that due to pilot file limitations, pilots can only be used with '''one''' language. If you switch languages you need to have multiple pilots.

To set the language, modify the Language entry in the [[Getting_started_with_FreeSpace_2#Registry|registry or the [Default] section of the .ini file]].

e.g.

<code>
[Default]

...

Language=French
</code>

== Step Six: Cutscenes ==

Depending on how you installed the game, the cutscenes might not be in the proper location. If you bought your copy of FS2 from Good Old Games, the cutscenes (ten .mve files) are somewhere in \freespace2\data2\ or \freespace2\data3\ . You can get them working by moving them to \freespace2\data\movies\ . Create the directory if it does not exist. You can also download either the [http://www.freespacemods.net/download.php?view.124 original MVE cutscenes] or [http://freespacemods.net/download.php?view.128 OGG-encoded versions] from FreeSpaceMods.net. If you have the game CDs/DVD, you can copy the cutscenes from them to the FreeSpace2/data/movies/ folder. The OGG cutscenes are smaller but might not perform as well on older hardware that could run the MVEs without problem. Now you should have the full gamut of updated and retail content installed!

Note: If you've found the AVI versions of the cutscenes, do not use them. Support for AVI has been removed in FSO versions 3.6.10 and higher.

[[Category:Source Code Project]]

Ai profiles.tbl

2022-12-15T15:36:29Z

Qazwsx: Mention alternative accepted spelling of "Missles" to prevent future bug hunts

{{SCP_table}}
{{TableVersionGit|2020-10-09|465af93dc}}
{{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.

This table is one of the [[Modular Tables]] and can be extended with xxx-aip.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'''
*'''any ship 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'''}}

==General Format==
'''#AI Profiles'''

'''$Default Profile:''' ''a profile name''

''Up to 9 different AI profiles''

'''#End'''

==#AI Profiles==
*Indicates to the parser that this is an ai_profiles table file.

===$Default Profile:===
*Defines the profile that each mission will use if no profile is specified in FRED. In addition, this profile will be selected automatically in FRED when you create a new mission. If this line is not specified, the default profile will be the FreeSpace 2 retail behavior.

===$Profile Name:===
*The name of the profile, naturally.

----

The following entries accept '''float list''' of five comma-separated values. One value for each of the difficulty levels (Very Easy, Easy, Medium, Hard, Insane).

===$Player Afterburner Recharge Scale:===
{{Table3610|
*Sets the speed of afterburner recharge
*Syntax: '''Float list'''
**Default: 5, 3, 2, 1.5, 1}}

===$Max Beam Friendly Fire Damage:===
{{Table3610|
*Defines the maximum damage inflicted by friendly beam fire
*Syntax: '''Float list'''
**Default: 0, 5, 10, 20, 30}}

===$Player Countermeasure Life Scale:===
{{Table3610|
*Sets the factor applied to player launched countermeasure lifetime
*Syntax: '''Float list'''
**Default: 3, 2, 1.5, 1.25, 1}}

===$AI Countermeasure Firing Chance:===
{{Table3610|
*Defines the chance a countermeasure will be fired by an AI-controlled ship (this is scaled by ai_class)
*Syntax: '''Float list'''
**Default: 0.2, 0.3, 0.5, 0.9, 1.1}}

===$AI In Range Time:===
{{Table3610|
*The delay (in seconds) for the AI to fire its weapons after getting in range.
*Syntax: '''Float list'''
**Default: 2, 1.4, 0.75, 0, -1}}

===$AI Always Links Ammo Weapons:===
{{Table3610|
*AI ships will link ballistic primaries if ammo levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 95, 80, 60, 40, 20}}

===$AI Maybe Links Ammo Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Ammo Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Primary Ammo Burst Multiplier:===
{{Table3611|
*Allows the AI to fire primary weapons in bursts. How long the bursts are (and how much time between them) is a function of ammo remaining, distance to target, angle to target, and this multiplier. A value of 0 turns this feature off (AI fires normally, without bursts). A value < 1 will make for shorter bursts with larger gaps, and a value > 1 will give longer bursts with shorter gaps.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$AI Always Links Energy Weapons:===
{{Table3610|
*AI ships will link energy primaries if energy levels are greater than these percents.
*Syntax: '''Float list'''
**Default: 100, 80, 60, 40, 20}}

===$AI Maybe Links Energy Weapons:===
{{Table3610|
*Defines the same as '''$AI Always Links Energy Weapons:''' but in situations when its hull is below 33 % of maximum hitpoints.
*Syntax: '''Float list'''
**Default: 90, 60, 40, 20, 10}}

===$Max Missiles Locked on Player:===
{{Table3610|
*Defines the maximum number of missiles allowed to be homing in on a player at any given time
*Note: Single-player only, no restriction in multiplayer
*Note: The alternative spelling "Missles" is also accepted for backwards compatibility reasons.
*Syntax: '''Float list'''
**Default: 2, 3, 4, 7, 99}}

===$Max Player Attackers:===
{{Table3610|
*Sets the maximum number of ships allowed to be attacking the player at any given time
*This number is also checked when a ship checks for a new target, such as using the goal attack-any.
*Syntax: '''Float list'''
**Default: 2, 3, 4, 5, 99}}

===$Max Incoming Asteroids:===
{{Table3610|
*Sets the maximum number of active (i.e. "thrown") asteroids that can be heading toward a friendly ship at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 5, 7, 10}}

===$Player Damage Factor: or $AI Damage Reduction to Player Hull:===
{{Table3610|
*Defines the factor applied to damage suffered by the player
*Syntax: '''Float list'''
**Default: 0.25, 0.5, 0.65, 0.85, 1}}

===$Player Subsys Damage Factor: or $AI Damage Reduction to Player Subsys:===
{{Table3610|
*Sets the factor applied to subsystem damage suffered by the player. This is in addition to the '''$Player Damage Factor:'''
*Syntax: '''Float list'''
**Default: 0.2, 0.4, 0.6, 0.8, 1}}

===$Predict Position Delay:===
{{Table3610|
*Sets the 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: '''Float list'''
**Default: 3, 4, 7, 12, 19}}

===$Max Turret Player Ownage:===
{{Table3610|
*Sets the maximum number of turrets on a particular ship allowed to be attacking the player at any given time
*Syntax: '''Float list'''
**Default: 3, 4, 7, 12, 19}}

===$Percentage Required For Kill Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.30, 0.30, 0.30, 0.30, 0.30}}

===$Percentage Required For Assist Scale:===
{{Table3610|
*Sets the minimum percentage of the total assessed damage a player must inflict in order to be awarded an assist (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.15, 0.15, 0.15, 0.15, 0.15}}

===$Percentage Awarded For Capship Assist:===
{{Table3610|
*In TvT and Coop missions all teammates will be granted this percentage of the capships score when someone scores a kill (3.6.10 and on)
*Syntax: '''Float list'''
**Default: 0.5, 0.5, 0.5, 0.5, 0.5}}

===$Repair Penalty:===
{{Table3611|
*The amount to subtract from the player's score if they are repaired by a support ship
*Syntax: '''Integer list'''
**Default: 10, 20, 35, 50, 60}}

===$Delay Before Allowing Bombs to Be Shot Down:===
{{Table3611|
*Time after bombs are fired during which the bombs are invulnerable to weapon hits
*Syntax: '''Float list'''
**Default: 1.5, 1.5, 1.5, 1.5, 1.5}}

===$Chance AI Has to Fire Missiles at Player:===
{{Table3611|
*Chance - expressed in ('''value''' + 1) / 7 - of each AI turret within current 10 second segment to be allowed to shoot missiles at player ship.
*Syntax: '''Float list'''
**Default: 0, 1, 2, 3, 4}}

===$Max Aim Update Delay:===
{{Table3611|
*Maximum amount of delay allowed before the AI will update its aim. Until the next update, the AI will project the target forward based on last checked position and velocity. Applies to small ships vs small ships (dogfights). The actual delay is randomly selected between 0 and the maximum (so setting a value of 2 will result in an average of 1 second delay).
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Turret Max Aim Update Delay:===
{{Table3611|
*As $Max Aim Update Delay, but affecting turrets instead
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Autoaim FOV:===
{{Table3613|
*Gives the player autoaim within the specified number of degrees from the target (FOV).
*Unlike the ships.tbl settings for autoaim, this only affects the player (and, of course, only if there is a nonzero value for the difficulty level.)
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Detail Distance Multiplier:===
{{Table3613|
*Affects how the "model detail level" setting in Options switches between LOD levels.
*This number acts as a multiplier on the LOD distances specified in ships.tbl.
*NOTE THAT THIS IS PER DETAIL LEVEL, NOT PER DIFFICULTY LEVEL.
*Syntax: '''Float list'''
**Default: 0.125, 0.25, 1.0, 4.0, 8.0}}
----

The following entries are boolean flags. They can be set to ''YES'' or ''NO'', ''TRUE'' or ''FALSE'', ''OUI'' or ''NON'', ''HIja′'' or ''ghobe′'', etc. The default is ''NO''.

===$big ships can attack beam turrets on untargeted ships:===
{{Table3610|
*If set, big ships can attack a beam turret that's firing on them from a ship that they don't currently have targeted.}}

===$smart primary weapon selection:===
{{Table3610|
*If set, enables the new primary weapon selection method}}

===$smart secondary weapon selection:===
{{Table3610|
*If set, enables the new secondary weapon selection method (including proper use of bomber+ missiles)}}

===$smart shield management:===
{{Table3610|
*If set, shields will devote all their charging energy to the weakest quadrant(s) and not waste energy on fully-charged quadrants (previously was -smart_shields on the command line)}}

===$smart afterburner management:===
{{Table3610|
*If set, the AI will properly use brief pulses of afterburner power instead of afterburning until fuel is exhausted}}

===$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 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, the game will check if the dying ship is a player's wingman, before making it give a death scream.
Prior to revision 9119, this was "$perform 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'''''}}

===$ai path mode:===
{{Table3613|
*Possible options are "normal" and "alt1". The alt1 mode differs from the normal behaviour in the following ways:
**1. No path shortcutting. Normal pathing AI will skip forward along a path to the furthest point it can reach. This is sometimes desirable, but makes it a lot harder to predict how the AI is going to behave at various points along a path. Turning this off also allows us to force the AI to straighten out, by giving it several waypoints in a more-or-less straight line. This is useful for such things as lining up a landing.
**2. No sliding when following paths. Docking still works, but there is some code that causes the AI to go full retard if it just misses a point: it turns towards the point in big, looping circles. This is apparently caused by passing a slide_vec value into ai_turn_towards_vector, which doesn't even seem to do what you'd expect it to do. Passing a null value instead turns off the stupid. (The behavior is fixed in alt1).
**3. Momentum taken into account when following paths. Path points will trigger sooner, proportional to the ship's speed and momentum. This prevents the AI from massively overshooting a waypoint, especially with high-damp ships.
**4. AI tries to follow the line between waypoints. Instead of just pointing at the next waypoint, the AI will fly a bit towards the line. This helps keep the AI actually on the path it claims to be following. See picture:[[Image:Altpaths.png]]
Blue is what happens with regular pathing. Red is the modified pathing: as you can see, it actively moves back towards the line.
**5. AI will respect "cap-waypoint-speed" when following paths (such as when docking or departing via bay).}}

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

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

===$no warp camera:===
{{Table3615|
*When set, prevents the view from switching to the external camera when the player warps out.
*Note: this flag is deprecated and may get moved to another table without further notice.}}

===$fix ai path order bug:===
{{Table3615|
*When set, ship will follow its own waypoint path unless the wingleader has the same waypoint path and order.
*Off by default.
*Syntax: '''''Boolean'''''}}

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

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

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

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

===$friendly ships use AI profile countermeasure chance:===
{{Table212|
*Specifies Friendly 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.
*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'''''}}

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

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

PF Shagrath

2022-05-29T18:33:15Z

Qazwsx: Updated download links and removed dead gamewarden link

{{User-made Ships|''PF '''Shagrath'''''}}

{{shipimage|image=[[Image:pfshagrath.jpg]]|caption=PF Shagrath}}

==Description:==

===Tech Room Description===
The Shagrath Heavy Raider is one of the most common pirate fighters. It was designed around multiple gatling systems, the massive helvette cannon as well as a pair of thrasher or phalanx cannons. Excess power from the ship's oversized reactor, which would otherwise be used by energy weapons, is fed into an ion preburner that effectively doubles the ships thrust output. The Shagrath cannot effectively fight lengthy battles, it is most frequently used in hit and run attacks. "Its secondary weapons capacity is somewhat limited. it can carry a single light warhead strapped to the hull, and its internal bays, which amount to nothing more than hand loaded launch tubes, can only carry a few types of missiles.

===Credits List===
*Model by '''Nuke'''

===Name Origin===
''Shagrath'' is a Norwegian musician best known as the vocalist (and, as of 2009, keyboardist) of Norwegian symphonic black metal band Dimmu Borgir.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Heavy Raider
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Death Cult Pirates
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| Poor
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 75.0 - 150.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| 175.0 mps
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| Heavy
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 300
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| 300
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 49 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Gun Mounts|Gun Mounts]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=4 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Guns
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 1
| 400
| Helvete
|- align="center"
| 2nd
| 2
| 800
| Thrasher
|- align="center"
| colspan=4| Compatible Primaries
|-
| colspan=4| Phalanx, Helvete, Thrasher
|}

*'''[[Technical_Terms_and_Definitions#Missile Banks|Missile Banks]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=3 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:40px" |Bank
| style="width:60px" |Capacity
| style="width:160px" |Standard Loadout
|- align="center"
| 1st
| 24
| Shark
|- align="center"
| 2nd
| 24
| [[GTM EMP Adv.|EMP Adv]]
|- align="center"
| 3rd
| 10
| Little Boy
|- align="center"
| colspan=3| Compatible Secondaries
|-
| colspan=3| Shark, Stinger, [[GTM Trebuchet|Trebuchet]], [[GTM EMP Adv.|EMP Adv.]], [[GTM Infyrno|Infyrno]], Littleboy
|}

===Veteran Comments===
{{comment|}}

==Download link:==
*(FSMods Archive): https://www.freespacemods.net/download_186.html