FreeSpace Wiki - User contributions [en]

GTVA Colossus

2014-11-06T18:59:51Z

Headdie: Update Colossus to information to 2014

{{FS12_Ships}}
The largest space-faring warship ever constructed by the [[Terrans]] or [[Vasudans]], the '''GTVA ''Colossus''''' was the result of twenty years of joint effort from dozens of contractors from across the [[Galactic Terran-Vasudan Alliance]]. Logging in with a length of six kilometers, this behemoth was equipped with over eighty weapon turrets, in addition to over 240 combat spacecraft.

With the offensive power that exceeded most [[GTVA]] battle groups, the ''Colossus'' was designed to combat the [[Shivans]] upon their return to Allied territory. The prospective target was one or more [[SD Lucifer|''Lucifer'']]-class super-destroyers, and it was deemed that the ''Colossus'' would not only have the firepower not only to destroy such a foe, but also to survive multiple hits from a ''Lucifer'''s primary weapon system.

Although the ''Colossus'' was a joint endeavor of both the Terrans and Vasudans, it is apparent that the ship itself exhibits more Terran design traits than Vasudan. It can be assumed that some of the Vasudan elements manifest themselves in less immediately overt ways.

==History==
{{Gtvaship
| image = [[Image:RScreen0044.png|300px]]
| name = GTVA ''Colossus''
| class = GTVA ''Colossus''
| 1stapp = [[The Sixth Wonder]]
| inservice = [[NTF Rebellion]] [[Second Shivan Incursion]]
| faction = [[Galactic Terran-Vasudan Alliance]]
| fate = [[Their Finest Hour|Destroyed]] by [[SJ Sathanas|SJ ''Sathanas 17'']]
}}
The first combat deployment of the ''Colossus'' was against the [[Neo-Terran Front]]. It can be truthfully said that it was the ''Colossus'' that was the ultimate factor in the NTF's collapse. NTF forces proved to be [[Feint! Parry! Riposte!|no match]] for the ''Colossus'' and her battle group, and the rebels made every effort to avoid direct combat with the warship. With his fleet shattered, and the remnants being actively pursued and destroyed by the ''Colossus'', [[Famous persons|Admiral Aken Bosch]] gave the order to flee GTVA space to the relative safety of the nebula beyond [[Gamma Draconis]].

With the NTF defeated, the ''Colossus'' was finally to fulfill the role her designers had envisioned for her: the defeat of a second Shivan incursion. However, as it turned out, the challenge was not to be [[SD Lucifer|SD ''Lucifer'']]-class superdestroyers, but rather the even more massive [[SJ Sathanas|SJ ''Sathanas'']]-class juggernaut. Twenty years of constant struggle finally culminated with the ''Colossus'''s destruction of the [[SJ Sathanas|''Sathanas'']], all at the cost of moderate damage to the ''Colossus''.

All would have been well was it not for the [[Shivans]] possessing multiple juggernauts. In the closing stages of the Battle of [[Capella]], the ''Colossus'' was deployed to interdict Shivan traffic at the [[Gamma Draconis]] jump node in [[Capella]] to divert enemy forces and attention away from the [[GTD Bastion|''Bastion'']], which was en route to collapse the jump corridor to [[Epsilon Pegasi]]. The ploy succeeded, as the [[Shivans]] first deployed a [[SD Ravana]], then a [[SJ Sathanas|SJ ''Sathanas'']] to engage the ''Colossus''. In her weakened state, it was obvious that the ''Colossus'' would not survive an engagement with another ''Sathanas''-class juggernaut, and Allied Command ordered the ''Colossus'' to withdraw.

However, with the success of the ''Bastion'''s critical mission in doubt, the ''Colossus'' disobeyed the direct order from Allied Command, and refused to disengage. Subsequently, the ''Colossus'' was destroyed with the loss of all hands. The thirty-thousand officers and crew of the ''Colossus'' willingly sacrificed themselves to ensure the continued survival of the billions of individuals making up the Terran and Vasudan species, and ultimately, the [[Galactic Terran-Vasudan Alliance]].

==Confirmed kills==
*NTCv ''Hawkwood'' (Destroyed at Enif Station)
*NTD ''Repulse'' (Admiral Koth's flagship. Kamikaze attacked the Colossus)
*NTD ''Andronicus'' (Reported destroyed in Command Briefing)
*NTC ''Camisard'' (Reported destroyed in Command Briefing)
*NTC ''Vanguard'' (''Reported destroyed in Endgame'')
*NTCv ''Congreve'' (''Implied destroyed in Endgame'')
*NTCv ''Danton'' (''Endgame'')
*SJ ''Sathanas'' (First, High Noon mission)
*SD ''Beast'' (Destroyed shortly before ''Sathanas 17'' destroyed the Colossus)

==Quotes==
"This is the GTVA ''Colossus''. Fighters, stand clear of hostile warships. All batteries, fire at will!"

"This is the GTVA ''Colossus''. Admiral Koth, you are ordered to power down your engines immediately and surrender. The Polaris jump node is blockaded, there is no escape."

"You are sacrificing thousands of lives for nothing!"

"If only Koth had surrendered rather than playing Martyr, his crew would still be alive"

"A Shivan juggernaut has jumped within range. What's the status of the [[GTD Bastion|''Bastion'']]?"

"We'll hold them back here. Just get the [[GTD Bastion|''Bastion'']] through!"

==Colossus cutscene==
'''Narrator:''' ''The following is classified level Rho. Unauthorized access is punishable under the GTVA security act, Deneb convention, section 21.3.5. We vanquished the Shivans in the Great War but the hard questions remained. How would we confront the threat of future invasion? The Shivans might return at any time, any place, without warning. How would we fight the next threat to the very existence of our species? In 2345, on the tenth anniversary of the Shivan attack on Ross 128, the Vasudan emperor Khonsu II addressed the newly-formed GTVA General Assembly. The emperor inaugurated an ambitious and unprecedented joint endeavor: The GTVA ''Colossus''.''

'''Khonsu II:''' ''Together we built a civilization on the ruins of the [[Great War]], and now we stand on the threshold of a new era of prosperity and harmony. With Project Colossus, the Vasudan people celebrate our shared covenant of peaceful co-existence and mutual defense of our Terran allies.''

'''Narrator:''' ''The ''Colossus'' is the most powerful space faring warship ever constructed. Spanning six kilometers from bow to stern, the ''Colossus'' has taken over twenty years to complete. Twelve ''Lucifer''-class destroyers can fit within its massive hull. Its state-of-the-art weaponry includes forty-five laser turrets, fifteen flak guns, twelve missile batteries, and twelve beam cannons. The ''Colossus'' wields more firepower than five ''Orion''-class destroyers combined. Sixty fighter and bomber wings are housed in its vast hangar and its crew numbers over thirty thousand. Among its major contractors are industry giants Triton Dynamics, Subach-Innes, and the Akheton Corporation. The alliance now wages war on multiple fronts: in Deneb, Alpha Centuri, Epsilon Pegasi, and the [[Nebula System|mysterious nebula]] beyond Gamma Draconis. Once deployed the ''Colossus'' will end these conflicts swiftly and decisively. If ever the Shivans return to threaten our worlds we will be ready to face the challenge, securing peace for today and for generations to come.''

==Description:==
{{shipimage|image=[[Image:Gtvacolossus-old.jpg]]|caption=The GTVA Colossus}}
===FS2 Tech Room Description===
The GTVA ''Colossus'' resulted from an endeavor unprecedented in Terran or Vasudan history. This 6-kilometer-long behemoth is the result of 20 years of joint effort from dozens of contractors of both races. The ''Colossus'' is the most powerful space-faring warship ever made, bristling with over 80 weapon turrets. It also houses 60 fighter and bomber wings and requires a crew of over 30,000. The firepower of the ''Colossus'' is greater than that of most GTVA battle groups.

===Developer Notes===
None

===Name Origin===
Used in Latin to refer to large statues, the term is used in English (in lower case, being a common noun) to refer to anything of large size.

The sixth of the Seven Wonders of the Ancient World was the Colossus of Rhodes, a giant bronze statue representing the god [[Helios]] that was constructed following a very important military victory. This is why the first mission featuring the ''Colossus'' is named "[[The Sixth Wonder]]."

==Performance:==
===Statistics===
{{Ship Stats|''See'': [[GTVA Colossus ship type debate|Ship type debate]]|All canon [[corporations]]|N/A|200.0, 200.0, 200.0|25.0|N/A|N/A|1 000 000|N/A|6166}}{|-
| style="width:200px"|'''[[Technical_Terms_and_Definitions#Fighter Complement|Fighter Complement]]'''
| style="width:200px"|240 fightercraft (organized as 60 wings or 20 squads)
|}

===Armaments===
*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#300505;"| '''FreeSpace 2'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Turret]]
| 8
|- align="center"
| [[Terran Huge Turret]]
| 10
|- align="center"
| [[Standard Flak]]
| 12
|- align="center"
| [[MX-52]]
| 8
|- align="center"
| [[GTM Piranha|Piranha]]
| 2
|- align="center"
| [[AAAf]]
| 10
|- align="center"
| [[TerSlash]]
| 7
|- align="center"
| [[BGreen]]
| 6
|}

==Modding Resources==
{{shipimage|image=[[Image:Willy B-Colossus-MVP2014.png]]|caption=The GTVA Colossus in FS2_Open MVP 2014}}
'''Retail''':
:$POF File: ???
:Textures: ???

'''MediaVP 2014''':
:$POF File: ???
:Textures: ???
 
History 
Proposed by: ??? on ??? 
First WIP Post: ??? on ??? 
First In-Game Model: ??? on ??? 
Completed In-Game Model: ??? on ??? 
Final Corrections: ??? on ??? 

==Gallery==
<Gallery>
Image:RScreen0025.jpg | Admiral Koth engages the GTVA Colossus.
Image:RScreen0073.png | Demonstrating the meaning of superior firepower.
Image:RScreen0044.png | The GTVA Colossus.
Image:RScreen0047.png | The Colossus meets its end at the hands of the [[Shivans]].
Image:Gtvacolossus.jpg]|The GTVA Colossus in FS2_Open 3.6.10
</gallery>

==Veteran Comments==
{{Comment|''The 6 BGreen beams of the Colossus are powerful and allow it to have no trouble taking on multiple destroyers at once while taking minimal damage in return. The Colossus is an all-round good ship — it has plenty of armor, a large number of turrets, and it's surprisingly fast for a ship of its size, matching the speed of the Sathanas and outpacing all destroyers.''

''The GTVA Colossus is not that great at killing ships of equal size to it as the above. The placement of its main beam turrets are all over the ship, meaning that maximum firepower cannot be directed against heavier ships. However, this does also have its advantages. It means that no capital ship can be in a safe spot from it. It is also loaded with massive amounts of anti-fighter and bomber weaponry, making it a nightmare to attack. These anti-fighter weapons are also located around the main beams of the warship, making it more difficult to disable.''

''I think that the blind spots of the Colossus are its rear and top although its rear is defended by four [[TerSlash]]es and its top is defended by two.''

''The Colossus model is infamous for its low moment-of-inertia value, which causes it to swing around like a baseball bat during tight turns. This is also partly because its pivot point is located at the very back, where the huge engines are. Most other ships in contrast, including the Sathanas, have their pivot point located near the centre of the ship, so their turns look more normal even if their moment-of-inertia value is similar to the Colossus'.''

''Keep in mind that the firepower demonstrated by the Colossus in [[High Noon]] was due to pushing the beams and fire control to their limit, resulting in considerable damage to the ship and weapons even if the Sathanas never fired a shot. Replacing the Colossus' default beams with more powerful beams without even mentioning overloads is not good at all.''

''Strangely enough, the Colossus is never mentioned as either a destroyer, superdestroyer or a juggernaut in the game, instead being ambiguously called a warship. This sparked a debate, as every other canon ship was given a ship type excluding the Colossus. Further details on this debate may be found [[GTVA Colossus ship type debate|here]].''

''Although many tend to praise the Colossus for its well-distributed anticapital firepower, this tactic, sadly, may usually prove ineffective. For example, if an attack operation against the Colossus were planned, the attacker's warships would have to be placed in one spot, so that the Colossus could only fire a fraction of its beam count. In short, the Colossus rarely is able to demonstrate its full firepower, since the enemy would not dare engage it from all sides anyway.''

}}

[[Category:Unique ships|Colossus, GTVA]]
[[Category:Ship]]

File:Willy B-Colossus-MVP2014.png

2014-11-06T18:56:12Z

Headdie: uploaded a new version of "File:Willy B-Colossus-MVP2014.png": Reduced to a suitable size for Ship listings

MVP 2014 Colossus taken by Willy_B - uploaded by headdie

File:Willy B-Colossus-MVP2014.png

2014-11-06T18:50:47Z

Headdie: MVP 2014 Colossus taken by Willy_B - uploaded by headdie

MVP 2014 Colossus taken by Willy_B - uploaded by headdie

FreeSpace 1 game information

2013-11-29T20:50:22Z

Headdie: Added compatibility instructions for Windows 7 64 bit

==FreeSpace: Game Information==
[[#Story|Story]] | [[#Features|Features]] | [[#System Requirements|System Requirements]]

===Story===

The Terrans and the Vasudans are in the middle of a high pitched, 14 year, intergalactic war. With the front nearly at a standstill and the casualties ranging in the billions, things look bleak. Then, during the middle of the fighting, a new foe arrives, named the Shivans by Terran Command. The Shivans systematically wipe out Terran and Vasudan outposts alike. With both Terran and Vasudans on the run, they must work together against their common enemy if they are to save their people, civilization, and homeworlds.

====Silent Threat====

As the Great War rages on, you've been commissioned by the GTI (Galactic Terran Intelligence) for special intelligence operations. In a matter of National Security, you've been asked to go behind enemy lines in order to preserve the fragile space treaty. Is the GTI setting you up or are the Shivans spreading their evil rage?

===Features===

*Engage massive capital ships and destroyers of unprecedented size and detail
*Feel ships explode around you with advanced physics and breathtaking effects
*Command intelligent wingmen & request reinforcements in real-time space combat
*Watch the Advanced AI system guide skillful wingmen and devious opponents, adapting to your abilities
*Swoop in and out of deadly 3D asteroid fields
*Advance in rank, earn medals and ribbons, gain more resposibility and features as your skills increase
*Listen to the event-driven music system tailor the soundtrack to the action
*Watch a detailed branching campaign unfold where your mission performances make the difference
*See high-resolution, breathtaking cinematic cutscenes with an epic storyline
*Create your own full-featured missions with FRED, our FreeSpace Mission Editor, included free!
*Play with up to 12 players via TCP/IP network
*Grab a microphone and talk to other players live during the action
*Track your statistics, rank, and medals against players from all over the world FREE on Parallax Online!

===System Requirements===

====Required====
*PentiumTM 133 with 3D accelerator (Glide or D3D only) OR PentiumTM 166 without 3D accelerator
*WindowsÂ® 95 with DirectX 5.0 or WindowsÂ® NT 4.0 with DirectX 3.0
*32mb RAM
*8X or faster CD-ROM Drive
*210mb available hard drive space
*100% Microsoft-compatible mouse
*Direct Sound compliant sound card

====Recommended====
*PentiumTM 200 with 3D accelerator (Glide or D3D only)
*48mb RAM
*PCI or AGP video card with 2mb of RAM
*Joystick supported

====Recommended====
Following the thread http://www.hard-light.net/forums/index.php?topic=86181.msg1721852#msg1721852 it has been discovered that the following steps can be used to get the game working in Windows 7 64 bit

*Installing the Game
*Installed the 1.06 patch for the game
*Installed the 1.06 EAX patch.
*Open the game folder to locate Freespace.exe and the FS.exe
*Open properties and went to the "Compatibility" Tab for both files
*Set the compatibility mode for both files to Win 95, in Resolution 640x480 and run as Administrator
*Started FS1 retail and it worked.

If you do not get the patches it won`t work
You can install the Addon Silent Threat too.

[[Category:The games]]

Command-Line Reference

2012-11-06T21:55:11Z

Headdie: added alterations in flag behavior for -spec -env -glow -normal flags in 3.6.15

Command-Line Flags (also called Command-Line Parameters) are optional flags passed to the FSO executable, and generally enables one or more features added to the FS2 Open engine. These flags are accessed conveniently through an [[FSO Launcher]]. To have FSO list all available flags, use any one of the following: [[Command-Line_Reference#-help|-help]], [[Command-Line_Reference#-help|--help]], [[Command-Line_Reference#-help|-h]], or [[Command-Line_Reference#-help|-?]].



===Graphics===
====-spec====
'''"Enable Specular"'''

Only polygons mapped with textures for which a shinemap exists will receive specular mapping; no attempt is made to generate spec maps where they do not exist. Specular maps are specified with the base map name plus "-shine" (i.e. TCov3A-shine.pcx).
{{Table3615|
*This feature is on by default, use launcher option Disable Specular or if necessary to manually disable enter the flag -nospec}}

====-env====
'''"Enable Environment maps"'''

It only works if [[Command-Line_Reference#-spec|-spec]] is also set. Environment mapping intensity will be determined from the shine map too (see [[Texturing]] for more info). [[Installing FreeSpace 2 Open#Video setup|See Video setup.]]
{{Table3615|
*This feature is on by default, use launcher option Disable Environment Maps or if necessary to manually disable enter the flag -noenv }}

====-glow====
'''"Enable Glowmaps"'''

Only polygons mapped with textures for which a glowmap exists will be glowmapped. Glow maps are specified with the base map name plus "-glow" (i.e. TCov4A-glow.pcx)
{{Table3615|
*This feature is on by default, use launcher option Disable Glow Maps or if necessary to manually disable enter the flag -noglow }}

====-mipmap====
'''"Enable mipmapping"'''

Causes for non-mipmapped textures to have mipmaps generated within the GPU on certain kind of texture formats, (IIRC, DDS formatted textures with a power of 2 size in both width and height). 
Since the use of already mipmapped DDS textures has become common, it has become deprecated.
The quality of the generated mipmaps depends on each GPU and used driver. It is normally used with [[Command-Line_Reference#-img2dds|-img2dds]] flag.

====-nomotiondebris====
'''"Disable motion debris"'''

====-noscalevid====
"Disable scale-to-window for Movies"

Disables fullscreen scaling of video clips.

====-missile_lighting====
'''"Apply Lighting to Missiles"'''

====-normal====
'''"Enable Normal Maps"'''

Normal maps require GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary normal maps (the same name of the base map plus "-normal"). DXT5_NM DDS format is needed. (Technical note: DXT5 will work, since only the GREEN and ALPHA channels are read by the current shader system. One direction of lines goes into the GREEN channel, the other direction goes into the ALPHA channel. RED and BLUE can be either base gray (#808080) or black. Usual practice is after creating the DXT5_NM, copy the RED channel to the ALPHA channel, black out the RED and BLUE an then save as either a DXT5 or u8888 (uncompressed) DDS file.)
{{Table3615|
*This feature is on by default, use launcher option Disable Normal Maps or if necessary to manually disable enter the flag -nonormal }}

====-post_process====
'''"Enable Post Processing"'''

enables the use (if present) of post-processing effects as defined by the post_process.tbl. Bloom usage has an additional cmdline option for setting it's value, most post processing effects are achieved in mission per the mission designer or can be enabled globally in the table.

====-soft_particles====
'''"Enable soft particles"'''

====-3dshockwave====
'''"Enable 3D Shockwaves"'''

This only has any effect when both a 2d and 3d shockwave effect are present, otherwise the only available effect is used.

====-fxaa====
'''"Enable FXAA antialiasing"'''

Enables the FXAA postprocessing stage. Needs optional FXAA shaders, which can be found here: http://www.hard-light.net/forums/index.php?topic=76145.0

====-flightshaftsoff====
'''"Force Lightshafts off"'''

Disables Lightshafts even if a mission designer enables them via SEXP in a mission.

===Game Speed===
====-img2dds====
'''"Compress non-compressed images"'''

Converts all images to DDS (compressed) format. Decreases memory usage but potentially reduces image quality.

====-no_vsync====
'''"Disable vertical sync"'''

====-cache_bitmaps====
'''"Cache bitmaps between missions"'''

Will ideally reduce the load-time from one mission to another.

===HUD===
====-dualscanlines====
'''"Another Pair of Scanning Lines"'''

Adds a second pair of scanning lines to the target window when scanning an object.

====-targetinfo====
'''"Enable Info next to Target"'''

Displays target info, such as name and class, beside the targeted object.

====-orbradar====
'''"Enables 3D radar"'''

An Orb style 3D radar will replace the standard 2D version.

====-rearm_timer====
'''"Enable Rearm/Repair Completion Timer"'''

Displays time remaining until rearm and repair from a support ship is complete.

====-ballistic_gauge====
'''"Enable the analog Ballistic Ammo gauge"'''

Adds an ammo gauge to the HUD when armed with a ballistic weapon.

===Gameplay===
====-ship_choice_3d====
'''"Use Models for Ship Selection"'''

Uses ship models in ship selection window. It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their ships. In this situation, and if it is not used, the game will probably crash to desktop in the ship selection window.

====-weapon_choice_3d====
'''"Use Models for Weapon Selection"'''

Uses weapon models in weapon loadout window for secondary weapons (missiles and bombs). It completely disables the standard ANI interface in this screen. 
Some mods need a compulsory use of this flag because they don't have available animations for their secondary weapons. In this situation, and if it is not used, the game will probably crash to desktop in the weapon loadout window.

====-3dwarp====
'''"Enable 3D Warp"'''

Use full geometry for the subspace warp effect.

====-warp_flash====
'''"Enable Flash upon Warp"'''

Enable a flash at warp in and warp out.

====-no_ap_interrupt====
'''"Disable Interrupting of AutoPilot"'''

Tells the game to not allow players to interrupt an autopilot already-in-progress.

===Audio===
====-snd_preload====
'''"Preload mission game sounds"'''

Useful in preventing game stuttering when sounds are played for the first time.

====-nosound====
'''"Disable Sound and Music"'''

====-nomusic====
'''"Disables Music"'''

===Multiplayer===
====-standalone====
'''"Run as Stand Alone Server"'''

Creates a standalone multi-player server.

====-startgame====
'''"Skip Mainhall and Start Hosting"'''

Once you launch and choose a pilot within the game, you will immediately have begun to host a game. This can be used in conjunction with several options to customize the game you create: -closed, -restricted, -password, -gamename, -allowabove, and -allowbelow. -startgame has no effect when -standalone is used.

See related: [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]] [[Command-Line_Reference#-gamename|-gamename]] [[Command-Line_Reference#-allowabove|-allowabove]] [[Command-Line_Reference#-allowbelow|-allowbelow]]

====-closed====
'''"Start Hosted Server as Closed"'''

Hosts a new game in a closed state, where no one can join until the in-game "Close" button is cleared. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -restricted or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]]

====-restricted====
'''"Host Confirms Join requests"'''

Hosts a new game in a restricted state. The host is presented with option to accept or deny each client's request to join the game. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-password|-password]]

====-multilog====
Creates a log file with a summary of packets sent and received in multiplayer games. The file is saved as \data\multi.log within the active mod folder—or with main data folder if no mod is active.

====-clientdamage====
This feature is not available in current builds.

====-mpnoreturn====
'''"Disables Flight Deck option"'''

Disables return to the flight deck screen after a mission completes.

===Troubleshooting===
====-nohtl====
'''"Software Mode (very slow)"'''
{{Warning| Enabling this will significantly reduce performance.}}
Reverts to software rendering mode.

====-no_set_gamma====
'''"Disable Setting of Gamma"'''

Disables the gamma settings in the options screen.

====-nomovies====
'''"Disable Video Playback"'''

Disables all video playback.

====-noparseerrors====
'''"Disable Parsing Errors"'''

Disables some parsing warnings and makes other parse errors non-fatal. Do not rely on this when creating new tables. The errors are there for a reason.

====-safeloading====
Loads missions the old way. Typically safer, but slower.
*'''Note:''' the parameter was removed as of the July 5, 2011 nightly build.

====-query_speech====
'''"Does this build have Speech?"'''

Determines if the current build includes text-to-speech.

====-novbo====
'''"Disable OpenGL VBO"'''

====-noibx====
'''"Don't use cached index buffers (IBX)"'''

Disables IBX caching of model geometry data. This will dramatically increase load times, but will help troubleshoot a model if one is working incorrectly.

====-loadallweps====
'''"Load all weapons, even those not used"'''

====-disable_fbo====
'''"Disable OpenGL RenderTargets"'''

====-no_glsl====
'''"Disable GLSL (shader) Support"'''

Disables the use of GLSL rendering (OpenGL shaders). The game will revert to legacy fixed render pipeline. Please note that Normal and Height map effects will be unavailable.

====-disable_glsl_model====
'''"Don't use shaders for model rendering"'''

====-ati_swap====
'''"Fix Color issues on some ATI cards"'''

====-no_3d_sound====
'''"Use only 2D/stereo for sound effects"'''

====-disable_di_mouse====
'''"Disables the DirectInput mouse code for FSO on windows."'''

'''Windows Only''' Can make mouse movement smoother on certain machines.

===Experimental===
====-ingame_join====
'''"Allows Ingame Joining"'''

Enables ingame joining in multiplayer. FIXME: Host option?

====-voicer====
'''"Voice Recognition"'''

Windows-only. Enables voice-recognition for wingmen commands. Must be specifically compiled into a build in order for it to be available; 3.6.10 final includes the feature. See [[Voice Recognition]] for more details.

===Development Tools===
====-fps====
'''"Show frames per second on HUD"'''

Displays current frames per second.

====-pos====
'''"Show Position of Camera"'''

Displays current position coordinates of camera.

====-window====
'''"Run in Window"'''

Runs the game in a window. No check to make sure that resolution is no higher than your desktop resolution, so be careful.

====-fullscreen_window====
'''"Run in Fullscreen Window"'''

====-timerbar====
Displays a timing bar across the top of the screen. Timerbar format varies by build. This is a relic from the Volition development days, and is unmaintained.
*'''Note:''' the parameter was removed as of the July 5, 2011 nightly build.

====-stats====
'''"Show Statistics"'''

Shows total and free physical memory, virtual memory and system pagefile.

====-coords====
'''"Show Coordinates"'''

Shows coordinates of the mouse cursor.

====-show_mem_usage====
'''"Show Memory Usage"'''

Shows detailed RAM usage based on file, handler and process usage and display on the left-center side of the screen during mission load and while in mission.

The meaning of the info displayed in the upper right corner of the HUD is:

'''DYN''' = dynamic memory, basically anything that's been allocated by the vm_* memory functions. This does NOT indicate total memory usage but does account for most of it.

'''POF''' = model memory, how much memory is being used by models (does not include textures)

'''C-BMP, BMP''' = bmpman memory, how much is used by the textures/images that are loaded. C-BMP means that you are using -cache_bitmaps and it will try to keep textures in memory between level loads and as the new level is loading it will keep what it needs and unload what it doesn't. Can greatly increase level loading speed, but does so at the cost of memory between level loads. This does not increase overall memory usage though, only during the loading screen. BMP means that it is not cached and all textures are unloaded from memory at the start of level load and all needed textures are then loaded from the disk again.

'''S-RAM''' = sound memory, how much is used by the sounds loaded in memory at the time. This counts static sounds only (from sounds.tbl, etc.) and not streaming sounds (music, voices, briefing stuff, etc).

'''V-RAM''' = approximate memory usage of video textures. This does not mean that your card has this much memory, and can report higher numbers that your card actually has memory. For OpenGL it also includes some of the geometry data, but this number does not reflect the total memory that your video card is using. It only reports how much data the game has purposefully loaded into API memory (meaning it could be in system memory, video card memory, or AGP memory).

''(It only works with debug builds, not with release builds).''

====-pofspew====
Reads all objects in the pof file of the selected mod, and creates an ibx cache file for each object in the data/cache folder for that mod. 
Details for each object are output to a pofspew.txt file created in the data folder. 
Otherwise, ibx files are created in game before each mission.

====-tablecrcs====
Is actually now (or should be) a typed reference rather than as a selection item. Takes 1 argument, usually a descriptive name.
Example usage: "-table_crcs MediaVPs" will create a table_crcs.csv file in the running mod (name can be separate of the mod selected) that allows for the validation of the tables used by that mod while on-line. The descriptive parameter given helps "allocate" that .csv file to the mod in question, and as such should closely or exactly match that mods name if possible.

====-missioncrcs====
Is actually now (or should be) a typed reference rather than as a selection item. Takes 1 argument, usually a descriptive name.
Example usage: "-mission_crcs MediaVPs" will create a mission_crcs.csv file in the running mod (name can be separate of the mod selected) that allows for the validation of the missions used by that mod while on-line. The descriptive parameter given helps "allocate" that .csv file to the mod in question, and as such should closely or exactly match that mods name if possible.

====-dis_collisions====
'''"Disable Collisions"'''

Disables all collisions.

====-dis_weapons====
'''"Disable Weapon Rendering"'''

Disables weapons rendering.

====-output_sexps====
This will make the FSO build spit out an html file that documents the supported SEXP's.

Just double click on sexps.html and it should open in your default web browser.

====-output_scripting====
This will make the FSO build spit out an html file that documents the supported scripting hooks and LUA libraries.

Just double click on scripting.html and it should open in your default web browser.

====-nograb====
Unix only. Disables focus grabbing in a window.

====-save_render_target====
'''"Save Render Targets to file"'''

====-debug_window====
'''"Display Debug Window"'''

Lists the fs2_open.log in (nearly)real-time generation.

====-verify_vps====
'''"Spew VP crcs to vp_crcs.txt"'''

Exports the CRC values of the VP files being loaded into a vp_crcs.txt file.

====-reparse_mainhall====
'''"Reparse mainhall.tbl when loading halls"'''

Mainhall.tbl will be reparsed every time a mainhall is loaded, as opposed to just once at game startup.

====-start_mission====
'''"Skip the mainhall in jump right into the specified mission"'''

Jump into the mission specified by the filename. Only in effect on the first run. This will skip load of the mainhall and its other related things altogether.

==Other==
The following options are not available as checkboxes in the launcher. Many require parameters, which follow the flag separated by a space. The prototype for use in this case is "-option argument"

===Lighting===
These factors can dramatically alter the atmosphere of the game. [[Sample Lighting Settings|This page]] has some sample lighting settings with screenshots.

====-ambient_factor====
This must be entered into the "Custom flags" field. This is a multiplier applied to the intensity of ambient lighting. Ambient light is lighting applied to all parts of a ship. FS2's standard value is 120. Try 75 for a good and realistic looking value. However, that is relative.

====-no_emissive_light====
By default, all ships in FS2 have a light generated on their own, it is more or less similar to a minimal amount of -ambient_factor. This feature was implemented to help the player seeing the ships over a black background. This flag disables this feature. Use it with a low -ambient_factor value to obtain an ultra-realistic dark looking.

====-spec_exp====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts the size of the shiny spot on ships. Higher number mean smaller spots. Default is 16. However, 11 is recommended. This is a relative value.

====-spec_point====
This must be used with the -spec command line parameter and must be entered into the
"Custom flags" field. Adjusts how much laser weapons contribute to specular highlights. Higher number mean greater contributions. Default is 1.0. However, 0.6 is recommended. This is a relative value.

====-spec_static====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much suns contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, is 0.8 recommended. This is a relative value.

====-spec_tube====
This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much Beam Weapons contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0. However, 0.4 is recommended. This is a relative value.

====-ogl_spec====
Takes a numerical argument. This value changes the basic shininess of the specular light in OpenGL. A lower value reduces the overall intensity of the light making it broader and less powerful. A higher value makes it more focused and brighter. The default value is 80, and the usable range is 0 to 128 (clamped). The original default value was 60, but it was raised to behave more D3D like.

===Graphics===
====-bloom_intensity====
Requires -post_processing ("Enable Post Processing") command.
Default value is 75. Range is 0-200.

====-height====
Enables height maps (parallax mapping). It only works if [[Command-Line_Reference#-normal|-normal]] is also set. It also needs GLSL rendering, (see [[OpenGL_Shaders_(GLSL)|OpenGL Shaders (GLSL)]] for further info). It needs auxiliary height maps (with the same name than base map plus "-height").

====-clipdist====
Changes the distance from the viewpoint for the near-clipping plane.

Takes one argument decimal specifying the distance to the near-clipping plane.

====-res====
Allows you to specify a resolution if the desired one cannot be set in the Launcher.
For example, -res 1920x1080 would run the game in 1920 x 1080 resolution. Since it requires an argument, it needs to be entered as a custom flag when using the Launcher. The "Run at specified resolution" option the Launcher gives is essentially this, but without being able to actually specify a resolution, it doesn't work.

====-fxaa_preset====
Requires both -post_processing and -fxaa. Can be used to adjust the FXAA quality and speed, 0 is fastest, 6 is highest quality. Default setting is 3.

===Gameplay===
====-mod====
{{Note| Please note that the ''[[mod.ini]]'' file is a feature exclusive to the Windows Launcher.}}
Specifies in which folders inside FreeSpace 2 directory, the game looks for all the game data (models, missions, textures, tables, ...). Retail version only looks inside ''Freespace2/data/'' structure and ''Freespace2/vp archives''.

This flag allows installing several different mods that modify retail behavior, and switching between them without needing to erase files or having undesired cross effects. Each mod should be installed in its own folder.

It takes one argument string: the chain of names of the used directories. Comma (''',''') must be used as separator. In this way, '''-mod dir1,dir2,dir3,...,dirx''' causes the game to use the following directory precedence:

#Freespace2/dir1/
#Freespace2/dir2/
#Freespace2/dir3/
# ... (the rest of the typed directories) ...
#Freespace2/dirx/
#Freespace2/

This flag can be indirectly set, (and it is normally set), through Launcher MOD tab and [[mod.ini]] file.

Within the Launcher's MOD tab you can select one directory, (let's call it ''moddir''), so the flag is at least set to '''-mod moddir'''.
If ''Freespace2/moddir/[[mod.ini]]'' exists it will be used to modify the -mod flag, too.

For further details, see '''[[mod.ini]]'''

'''Data precedence'''

As already said, within the different directories, the data precedence is set by the specified order in the -mod flag. The lowest priority goes to the Freespace2 installation directory.

Inside each directory, data precedence is the following:

#Individual files located in ''Current_dir/data/'' subdir structure. See [[FS2_Data_Structure|FS2 Data Structure topic]] for deeper info about the different folders and contents this structure has.
#Files located inside vp archives. (These vp archives are "similar" to zip archives. They just contain other files and folders. Moreover, files have to be stored using the same ''data/'' structure used outside it). Vp archives are read in alphabetical order, so aaa.vp files have higher priority than aab.vp files and so on.

The highest priority file overrides the rest of them. In this way, if you have a ''Mission.fs2'' inside ''Freespace2/Pri1/data/missions/'' it doesn't matter that this ''Mission.fs2'' is also inside ''Freespace2/Pri1/aaa.vp'', ''Freespace2/Pri1/aab.vp'', ... or ''Freespace2/data/missions/''. This data precedence allows the user to quickly replace old files by corrected or enhanced ones adding them in a higher priority place.

'''Additional notes'''
# As derived from the explanation, the exact names for directories or vp archives are actually irrelevant. It only matters the directory order inside -mod flag argument and the alphabetical order for vp archives inside each used directory.
# This flag is also used by [[Portal:FRED|FRED]]. So if there is special mod info, (like backgrounds maps, ship models or whatever), it must be typed, (''Fred2_Open_r.exe -MOD whatever''), or FRED won't be able to use it. A special build of wxLauncher is able to configure FRED so that the -mod doesn't have to be done manually see [http://www.hard-light.net/forums/index.php?topic=67950.msg1387911#msg1387911 the forum post] for more details.
{{Table3612|As of 3.6.12 FRED now loads cmdline_fso.cfg just like FS does so FRED will use the same settings as FS including the -mod settings}}
# Be careful while typing the directory names in the flag argument or inside mod.ini files. The program doesn't check if the typed directories exist. If they do not exist, they are just ignored. No warnings, no errors, no messages at all.

{{Warning| '''Priority and Texture Formats'''

''Obsolete behavior - Until FS2_open v3.6.9.:''

FS2_Open can use several file formats in textures: [http://en.wikipedia.org/wiki/PCX PCX], [http://en.wikipedia.org/wiki/DirectDraw_Surface DDS], [http://en.wikipedia.org/wiki/JPG JPG] and [http://en.wikipedia.org/wiki/TGA TGA]. Make sure you keep the format when you update your texture. For example if you update the old ''TextureOfMyFighter.tga'', do not save it as ''TextureOfMyFighter.dds'' in a higher priority place, because there is a chance of the game loading the old one despite of all.

The reason to do this is that, loading process (including priorities) is applied firstly for a kind of textures (TGAs), then for another kind (JPGs), and so on. This behavior can lead to situation where your new, updated and higher priority placed texture is not read because the format of the older one.

''New behavior - From FS2_open v3.6.10. (including previous beta testing releases):''

The former issue has been fixed. Now texture format priority is only applied within the same location. In this ''strange'' situation it goes DDS -> TGA -> JPG -> PCX. Examples:
* ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.dds'' is loaded instead of ''/Freespace2/MyVp.vp>>>data/maps/MyTexture.tga''.
* But your improved ''/Freespace2/data/maps/MyTexture.xxx'' will override them both despite of its format.
In this way, when you update any texture, you don't have to pay attention to its original format. Just place it in a higher priority place.

Nevertheless, global priority is kept between animated and static textures. Because of their management, animated textures (ANIs and EFFs) are looked for BEFORE static ones. In this way there's no way to update an animated texture with a static one (an obsolete ANI is always going to be loaded before the newer DDS version). The solution: use an updated EFF with just one frame.

}}

====-fov====
This flag allows the player to specify the ''vertical'' Field of View (FoV) angle, in radians, for the player eyepoint. The angle is measured across the full width of the viewing cone. The FoV angle is technically known as the Angle of View (AoV)

*Syntax: '''''float''''' Angle
*Valid Values: 0 to 2*Pi radians
*Default Value: 0.75 radians

The the FoV angle/AoV is what determines the relative zoom level of the main game camera. Smaller angles generally equal to higher zoom levels, while larger angles equal to lower zoom levels (down to the theoretical x0 magnification).

However, too small of an angle will have a squashed look on the edges of your screen, and too high of an angle will greatly stretch edges. It is recommended to change the AoV, as FS2's default AoV has some perspective distortion at the screen edges (the default AoV is too high).

A natural looking (as if you where physically in the cockpit) AoV depends on the distance the player's actual eyes are away from the screen: the further away from the screen, the smaller the AoV should be, and vice versa. "Ergonomic" distances generally yield a '''''diagonal''''' AoV of 0.523 radians (30 degrees), but you can easily find the natural AoV by the following formula:

AoV (radians) = atan( H / ( 2*D ))

where:

Height of screen = H

Distance between head/eye and the screen = D

Generally, gamers like to increase the AoV in order to increase their peripheral vision on the screen, so as to gain a better situational awareness around their craft. An AoV of 0.39 radians seems to be a good start, but feel free to experiment and use whatever AoV you are most comfortable with.

===Multiplayer===
====-gamename====
Specifies the name of the game to be created by the host. This only works when used in conjunction with -startgame.

Takes one argument string, the name to be assigned to the game being created.

This argument does nothing when used with -standalone. To set the name for a standalone server, see [[Multiplayer(Main)#Standalone Servers|Standalone Servers]].

See related:   [[Command-Line_Reference#-startgame|-startgame]]   [[Multiplayer(Main)#Standalone Servers|Standalone Servers]]

====-password====
Specifies the password for a standalone server. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -restricted.

Takes one argument string, the required password for the game being created.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]]

====-allowabove====
Specifies a player's minimum rank for joining a game. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking above which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-allowbelow====
Specifies a player's maximum rank for joining a game on a standalone server. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking below which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-port====
Specifies the port on which to host a game or serve a standalone game.

Takes one argument integer, the port on which the host will listen for clients.

====-connect====
{{Sectstub}}
====-timeout====
{{Sectstub}}
====-cap_object_update====
Caps the maximum object update the server will respond to regardless of what the client has set. If the client is set to request high object updates but the server is capped to low, then that's all the client will get.

Takes one argument integer (0 to 3) which corresponds to the object update cap (With 0 being low and 3 being LAN).

===Help===
====-help====
Instructs FSO to print out all supported parameters. Some launchers can use these options to automatically populate the available command line options, even if the version of FSO is far newer than the launcher itself. NOTE: This option only works in Linux builds...

====--help====
See [[Command-Line_Reference#-help|-help]]

====-h====
See [[Command-Line_Reference#-help|-help]]

====-?====
See [[Command-Line_Reference#-help|-help]]

[[Category:Lists]]
[[Category:Source Code Project]]

Ai profiles.tbl

2012-10-18T17:00:12Z

Headdie: /* $Predict Position Delay: */ added comments from Sushi regarding this found http://www.hard-light.net/forums/index.php?topic=82604.msg1648392#msg1648392

{{SCP_table}}

{{TableVersion|9126}}

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.

There is a "hidden" profile called FS2 RETAIL that is hard-coded into FreeSpace Open and cannot be modified. It is always the default profile unless another is specified using $Default Profile.

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

[[Tables|List of Tables]]

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

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

''Up to 9 different AI profiles''

'''#End'''

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

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

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

----

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

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

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

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

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

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

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

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

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

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

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

===$Max Missiles Locked on Player:===
{{Table3610|
*Defines the maximum number of missiles allowed to be homing in on a player at any given time
*Note: Single-player only, no restriction in multiplayer
*Syntax: '''Float list'''
**Default: 2, 3, 4, 7, 99}}

===$Max Player Attackers:===
{{Table3610|
*Sets the maximum number of ships allowed to be attacking the player at any given time
*Syntax: '''Float list'''
**Default: 2, 3, 4, 5, 99}}

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

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

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

===$Predict Position Delay:===
{{Table3610|
*Sets the measure of time (in F1_0 units) after which the AI will recalculate the position of its target.
*It does not apply to the AI's aim, it only applies to things like avoiding collisions and maneuvering at close range. Generally, anything other than a 0 just allows the AI to do monumentally stupid things like try to turn to avoid ramming where it thought you were 2 seconds ago.
*Syntax: '''Float list'''
**Default: 2, 1.5, 1.333, 0.5, 0}}

===$AI Shield Manage Delay:===
{{Table3610|
*Also '''$AI Shield Manage Delays:'''
*Sets the time in seconds between each instance of an AI ship managing its shields
*Syntax: '''Float list'''
**Default: 5, 4, 2.5, 1.2, 0.1}}

===$Friendly AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 2, 1.4, 1.25, 1.1, 1}}

===$Hostile AI Fire Delay Scale:===
{{Table3610|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 4, 2.5, 1.75, 1.25, 1}}

===$Friendly AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for friendly ships
*Syntax: '''Float list'''
**Default: 0.4, 0.6, 0.8, 1.0, 1.2}}

===$Hostile AI Secondary Fire Delay Scale:===
{{Table3614|
*Sets the factor applied to "fire wait" for hostile ships
*Syntax: '''Float list'''
**Default: 1.4, 1.2, 1.0, 0.8, 0.6}}

===$AI Turn Time Scale:===
{{Table3610|
*Defines the factor applied to time it takes for enemy ships to turn. A value of 1.0 means the ship turns at normal speed, 2.0 means half speed (takes twice as long), etc. Note that this value ONLY affects ships hostile to the player (always 1.0 for friendly ships).
*Syntax: '''Float list'''
**Default: 3, 2.2, 1.6, 1.3, 1}}

===$Glide Attack Percent:===
{{Table3611|
*How often the AI will use the "glide attack" move when it has the opportunity. Glide attack means using glide to maintain course while aiming and firing at the current target. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Circle Strafe Percent:===
{{Table3611|
*How often the AI will use the "circle strafe" move when it has the opportunity. Circle strafe means that the ship will attempt "Descent-like" combat, trying to maintain distance while circling around the target using sidethrusters. Ships will only attempt this when sidethrust top speed is at least 2/3 of target's current velocity.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Glide Strafe Percent:===
{{Table3611|
*How often the AI will use the "glide strafe" move when it has the opportunity. Glide strafe means using glide to attack capships by flying past and shooting at them. Only affects ships capable of glide.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Random Sidethrust Percent:===
{{Table3611|
*Percentage of the time where AI ships will randomly sidethrust in a dogfight.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Time Threshold:===
{{Table3611|
*The minimum amount of time required for the AI to detect a "stalemate" situation. If a ship and its target have been within a certain distance of each other (defined by ''$Stalemate Distance Threshold'') for this amount of time without either of them scoring a hit on the other, the AI will do something to break the stalemate. Only applies to small ships. If this value is 0 or less, no stalemate detection is performed.
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Stalemate Distance Threshold:===
{{Table3611|
*The maximum distance that an AI ship must remain from its target for a "stalemate" to occur (see ''$Stalemate Time Threshold'').
*Syntax: '''Float list'''
**Default: 0, 0, 0, 0, 0}}

===$Player Shield Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's shields recharge
*Syntax: '''Float list'''
**Default: 4, 2, 1.5, 1.25, 1}}

===$Player Weapon Recharge Scale:===
{{Table3610|
*Defines the factor applied to the speed at which the player's weapons recharge
*Syntax: '''Float list'''
**Default: 10, 4, 2.5, 2, 1.5}}

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===$allow rapid secondary dumbfire:===
{{Table3610|
*If set, allows an AI ship to switch to rapid fire for dumbfire missiles}}

===$huge turret weapons ignore bombs:===
{{Table3610|
*If set, causes huge turret weapons (including anti-capship beams) to not target bombs}}

===$don't insert random turret fire delay:===
{{Table3610|
*If set, removes the random turret fire delay (from .1 to .9 seconds) inserted in addition to AI Fire Delay Scale}}

===$hack improve non-homing swarm turret fire accuracy:===
{{Table3610|
*If set, triggers a hack to improves the accuracy of non-homing swarm missiles by firing them along the turret's last fire direction rather than the direction it currently faces
*Also disables swarm weapons ability to fire only on the 'turrets barrel line'.}}

===$shockwaves damage small ship subsystems:===
{{Table3610|
*If set, shockwaves will cause damage to small ship subsystems (like in FS1)}}

===$navigation subsystem governs warpout capability:===
{{Table3610|
*If set, ships will not be able to warp out if their navigation subsystem is destroyed or low in strength}}

===$ignore lower bound for minimum speed of docked ship:===
{{Table3610|
*If set, there will be no lower bound for the speed at which docked ships move (like in FS1).
*When a ship is towing another ship or ships, the towing ship will be slowed down to a degree depending on the total mass of all docked ships. In FS1, the ships could slow down to an arbitrarily slow speed, even a fraction of a m/s above zero. In FS2, there is a lower bound on this behavior so that all ships are guaranteed to move at a minimum docked speed. When set, this flag removes the lower bound and restores FS1 behavior.}}

===$disable linked fire penalty:===
{{Table3610|
*If set, there will be no penalty for linking primaries. Normally, the rate of fire is *1 for a single bank, *0.66 for two banks and *0.5 for three banks (the fire delay is increased according to the formula 1+([nb of banks]-1)*0.5 ).}}

===$disable weapon damage scaling:===
{{Table3610|
*If set, weapons will do the same damage to a ship regardless of "big damage", "supercap", etc. ship types.}}

===$use additive weapon velocity:===
{{Table3610|
*If set, weapons will inherit their firing ship's velocity. A ship traveling quickly will fire weapons faster than a ship traveling slowly. This also improves the accuracy of weapons fired while gliding.}}

===$use newtonian dampening:===
{{Table3610|
*Newtonian Dampening changes turning and acceleration behavior. By default, there's quite a bit of slide when you turn, and when combined with high damp values (such as in BtRL), you can actually push your speed up beyond the max. Newtonian Dampening is the more realistic turns, where too much turning will lower your speed. Forward momentum is also affected. Backslash can explain it in more detail. [http://www.hard-light.net/forums/index.php/topic,50870.msg1029741.html#msg1029741] }}

===$include beams for kills and assists:===
{{Table3610|
*If set, beam damage is counted when calculating kills and assists.}}

===$score kills based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the killer inflicted on the dead ship.}}

===$score assists based on damage caused:===
{{Table3610|
*If set, kills gain score based on the percentage damage the player gaining the assist inflicted on the dead ship.}}

===$allow event and goal scoring in multiplayer:===
{{Table3610|
*If set, players (rather than just their team) can gain score from events in multiplayer.}}

===$fix linked primary weapon decision bug:===
{{Table3610|
*If set, the AI will properly link primaries according to specified percentages of energy levels instead of retail behavior where it mistakenly linked according to absolute energy levels.}}

===$prevent turrets targeting too distant bombs:===
{{Table3610|
*If set, prevents turrets from targeting bombs beyond maximum range of the weapons of the turret.}}

===$smart subsystem targeting for turrets:===
{{Table3610|
*If set, prevents turrets from trying to target subsystems beyond their fov limits, also keeps the turret subsystem targeting preference order intact regardless of the angle to the target.}}

===$fix heat seekers homing on stealth ships bug:===
{{Table3610|
*If set, heat-seeking missiles will not home in on stealth ships (this mirrors the established behavior where heat-seeking missiles do not home in on ships that are hidden from sensors).}}

===$multi allow empty primaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without primaries.}}

===$multi allow empty secondaries:===
{{Table3610|
*If set, allows a player to commit into a multiplayer game without secondaries.}}

===$allow turrets target weapons freely:===
{{Table3611|
*If set, allows turrets to target any weapons instead of just targeting bombs, to be used in conjunction with target priorities setup.}}

===$use only single fov for turrets:===
{{Table3611|
*If set, allows turrets to fire outside some hardcoded FOV set for certain missile types limits, and rely only on the user defined FOV.}}

===$allow vertical dodge:===
{{Table3611|
*If set, allows ships to dodge weapons fire vertically as well as horizontally.}}

===$force beam turrets to use normal fov:===
{{Table3611|
*If set makes beam turrets use same FOV rules as other weapons do. Prevents beam from a turret from following the target beyond the turret's FOV}}

===$fix AI class bug:===
{{Table3611|
*Fixes a bug where AI class attributes are not set properly on ships if the AI class is set in the mission to something other than the default for the ship type. Set this to YES if you want attributes in [[Ai.tbl]] to mean anything at all.}}

===$turrets ignore targets radius in range checks:===
{{Table3611|
*TBD.}}

===$no extra collision avoidance vs player:===
{{Table3611|
*Disables the extra collision avoidance that AI normally uses against the player. Makes the AI more aggressive vs the player at close range (same treatment as vs other AI), although ship-ship collisions are slightly more likely.}}

===$perform fewer checks for death screams:===
{{Table3614|
*If set, the game will check if the dying ship is a player's wingman, before making it give a death scream.
Prior to revision 9119, this was "$perform fewer checks for death screams:", but the old version will still parse correctly.}}

===$advanced turret fov edge checks:===
{{Table3614|
*TBD.}}

===$require turrets to have target in fov:===
{{Table3614|
*TBD.}}

===$all ships manage shields:===
{{Table3613|
*Allows AI to manage shields on big ships}}

===$ai aims from ship center:===
{{Table3613|
*AI aims weapons using the center of the ship instead of the first gunpoint. If a convergence offset is specified for this ship in ships.tbl, AI aims using that as a reference point.}}

===$allow primary link at mission start:===
{{Table370|
*When set, no ships will link primaries for the first 30 seconds of a mission. In addition, ships will randomly not link for the first two minutes of a mission. Set this to NO to get rid of this often-problematic retail behavior. (Prior to revision 9119, this was called $allow primary link delay and defaulted to YES. The old method is still supported for compatibility.)}}

===$allow beams to damage bombs:===
{{Table3613|
*When set, beam weapons will be able to effectively intercept bombs. In addition, bombs flying through a beam path will get damaged and destroyed. Default: NO.}}

===$disable weapon damage scaling for player:===
{{Table3613|
*When set, Player weapon damage will no longer be scaled down when firing a non-huge primary against a ship with the "big damage" flag. Use with caution, as this may severely impact mission balance.}}

===$countermeasures affect aspect seekers:===
{{Table3613|
*TBD.}}

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

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

Weapons.tbl

2012-09-04T20:21:02Z

Headdie: /* $Substitute: */ added note *Feature causes crash to desktop when weapon is used with a turret. to 3613

{{TableVersion|8414}}

The '''weapons.tbl''' defines all of the weapon classes used in FSO.

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

[[Tables|List of Tables]]

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

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

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

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

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

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

==Core Table==

===$Name:===
*This is the name of the weapon. If it's going to be used by the player, keep it under 12 characters so it doesn't spill over the HUD box. Two special characters can be used in the name: '''#''' and '''@'''. Their usage details are the very same than inside the [[Ships.tbl#.24Name:_2|$Name field from Ships.tbl]].
*Syntax: '''''String'''''

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

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

===$Subtype:===
{{Table3610|
*Can be used to specify whether a weapon is a primary or secondary weapon.
*Syntax: '''''"String"''''', either Primary or Secondary}}

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

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

'''Example'''

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

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

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

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

'''Example'''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Blending type: additive

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

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

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

Blending type: additive

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===$Fire Wait:===
*Time in seconds between firings
*Note that Fire wait will be reset to 1 if it is set over 5 for non turreted primary weapons
*Syntax: '''''Float''''', seconds

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

===$Damage Type:===
{{Table3610|
Defines the damage type that this weapon uses. All armor effects are applied after shield and have no function against shockwave or subsystem damage.

'''REQUIRES:''' [[armor.tbl]]

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

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

===$Arm distance:===
{{Table3610|
*Defines the distance from the firing ships that is required before the weapon comes hot
*If the distance has not been reached when the weapon detonates the Dinky explosion is used
*Syntax: '''''Float''''', meters}}
{{Table3615|
*This parameter is also applied to flak weapons. Previous behaviour was to arm weapons after 10 meters of travel.}}

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

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

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

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

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

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

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

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

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

===$Inner Radius:===
*Radius at which the full explosion damage is done. Marks the line where damage attenuation begins. Damage is reduced by the square of the distance between the inner radius and outer radius. i.e. half way between inner and outer results in 1/4 damage
*Syntax: '''''Float''''', meters

===$Outer Radius:===
*Maximum radius at which any damage is done. See $Inner Radius for the attenuation formula.
*Also defines the size of the shockwave (if shockwave speed is > 0)
*Syntax: '''''Float''''', meters

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

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

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

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

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

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

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

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

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

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

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

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

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

===$Homing:===
'''This option is exclusive to secondaries.'''

Defines if the bolts/missiles in question is homing
*The bolts of primaries will turn to face their target if this option is set to YES... but is otherwise the same as a normal bolt ( when the option is set to NO ).

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

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

===='''+Type:'''====
Defines the homing method
*Syntax: '''''String''''', ''ASPECT'' or ''HEAT''
{{Table3610| An additional option, ''JAVELIN'', has been added. This behaves like an aspect missile but automatically only locks onto the engines of a target, and only if the engines are in sight.}}

===='''+Turn Time:'''====
Determines how well the missile maneuvers. Is defined as the number of seconds it takes the missile to do a 360 degree circle
**Syntax: '''''Float''''', seconds

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

This is the width of the weapon's viewing cone, given in degrees. Objects outside this cone are effectively invisible to the missile. The value / 2 gives the angle from the missile's centerline to the edge of the viewing cone.
*Syntax: '''''Float''''', degrees
{{Table3610| Has been enabled also to aspect seekers as an option.}}

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

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

===='''+Lock Pixels/Sec:'''====
'''For aspect/javelin missiles only'''
The number of pixels the aspect triangle moves per second while attempting lock-on.

*Syntax: '''''Integer''''', pixels per second

===='''+Catch-up Pixels/Sec:'''====
'''For aspect/javelin missiles only'''

The number of pixels moved per second while attempting to catch up to the target.
*Syntax: '''''Integer''''', pixels per second

===='''+Catch-up Penalty:'''====
'''For aspect/javelin missiles only'''

Extra pixels to move after catching up. (Needs verification )
**Syntax: '''''Integer''''', pixels

===='''+Seeker Strength:'''====
{{Table3610|
Defines the seeking ability of the homing system. Default of heat seekers is 3 and for aspect seekers 2. Spoofing change is defined as '''cm type effectiveness'''/'''seeker strength'''.
*Syntax: '''''Float''''', seeker strength}}

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===$Trail:===
*This is used if you want your weapon to have a trail. Trail is often used only with secondaries though it works with standard primaries as well.
*'''+Start Width:'''
**How wide the head of the trail is.
**Syntax: '''''Float''''', meters
*'''+End Width:'''
**How wide the tail of the trail is.
**Syntax: '''''Float''''', meters
*'''+Start Alpha:'''
**The opacity of the trail head.
**Syntax: '''''Float''''', value between 0 and 1
*'''+End Alpha:'''
**The opacity of the trail tail.
**Syntax: '''''Float''''', value between 0 and 1
*'''+Max Life:'''
**How long the trail lasts.
**Syntax: '''''Float''''', seconds
*'''+Bitmap:'''
**The graphic file to use for the trail.
**Syntax: '''''String''''', filename
{{Table3611|
*'''+Faded Out Sections:'''
**Defines the number of the trail sections (counting from the leading edge) which are gradually faded out.
**Syntax: '''''Integer''''', number of trail sections}}

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

}}

===$Spawn Angle:===
{{Table3610|
*Defines the cone (with an angle) where the spawned weapons appear. ''Value'' gives the angle from the missiles centerline. The maximum possible angle between any two child weapons would be ''Value*2''.
*Spawn angle can be defined as many times as the carrier missile has child weapons defined for it (up to 5).
*Syntax: '''''Float''''', degrees}}

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

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

===$BeamInfo:===
*'''+Type:'''
**Defines the type of beam in question. Beam types: 0 is a standard non-slashing type beam. 1 is a slashing type beam. 2 is a targeting beam that is used to trigger SSMs. 3 is a beam type that fires pulses in anti-fighter role and acts like type 0 beam in other roles. 4 is a beam that is restricted to what is directly in front of it, along turrets firepoints normal.
**Syntax: '''''Integer''''',, only values from 0 to 4 are legal
*'''+Life:'''
**How long it lasts once the beam is actually firing.
**Syntax: '''''Float''''', seconds
*'''+Warmup:'''
**Warmup time
**Syntax: '''''Integer''''', milliseconds
*'''+Warmdown:'''
**Warmdown time
**Syntax: '''''Integer''''', milliseconds
*'''+Radius:'''
**Muzzle glow radius
**Syntax: '''''Float''''', meters
*'''+PCount:'''
**Particles spewed every interval. ??
**Syntax: '''''Integer'''''
*'''+PRadius:'''
**Particle radius
**Syntax: '''''Float''''', meters
*'''+PAngle:'''
**Defines the random "cone" where the particles are generated
**Syntax: '''''Float''''', angle of the cone
*'''+PAni:'''
**Animation used to represent the particles
**Syntax: '''''String''''', filename
*'''+Miss Factor:'''
**The higher the numbers, the more likely that this beam will miss. One value for every difficulty level
**Syntax: '''''Miss Factor''''', five '''floats''', very easy, easy, moderate, hard, insane, respectively.
***Example: 0.5 0.975 1.35 1.875 2.5
{{Table3613|
*'''IFF specific miss factors'''
**Identical to the preceding entry but IFF specific. Replace the <IFF> with the name of the IFF from [[iff_defs.tbl]]
**Syntax: '''''+<IFF> Miss Factor:''''', five '''floats''', very easy, easy, moderate, hard, insane, respectively.
***Example: 0.5 0.975 1.35 1.875 2.5}}
*'''+BeamSound:'''
**Corresponding looping sound effect when the beam is firing.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+WarmupSound:'''
**Corresponding sound effect when the beam is beam warmed up.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+WarmdownSound:'''
**Corresponding sound effect when the beam is warming down.
**Syntax: '''''Integer''''' or '''''String''''', name or identification number of the sound as defined in [[sounds.tbl]]
*'''+Muzzleglow:'''
**Defines the bitmap used to create the muzzle glow
**Syntax: '''''String''''', filename
*'''+Shots:'''
**Defines into how may invidual shots the type 3 (AAA) beams are divided. Note total firing is the same as the +Life:
**Syntax: '''''Integer'''''
*'''+ShrinkFactor:'''
**What percentage of lifetime where beam starts shrinking (0.1 == 10% life left)
**Syntax: '''''Float'''''
*'''+ShrinkPct:'''
**What percentage of max width we subtract per second
**Syntax: '''''Float'''''
{{Table3610|
*'''+Range:'''
**Defines the maximum range where the beam still has any effect.
**Syntax: '''''Float''''', meters
*'''+Attenuation:'''
**Defines the point where the damage caused by the beam starts to attenuate. At maximum range damage is zero.
**Syntax: '''''Float''''', from 0 - firing point to 1 - no effect
***Default: 1}}
{{Table3611|
*'''+BeamWidth:'''
**Defines the width of the beam for collision test purposes instead of using widest beam section.
**Syntax: '''''Float''''
*'''+Beam Flash Effect:'''
**Defines the additional impact flash effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Flash Radius:'''
**Defines the radius for the additional impact flash effect.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect:'''
**Defines the beam piercing (bursting flames) effect for the beam.
**Syntax: '''''String''''', filename
*'''+Beam Piercing Radius:'''
**Defines the average radius used for the beam piercing effects.
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Velocity:'''
**Defines the base velocity for the piercing effects
**Syntax: '''''Float'''''
*'''+Beam Piercing Splash Effect Velocity:'''
**Defines the base velocity for the secondary piercing effects
**Negative velocity causes the particles to move to opposite direction
**Syntax: '''''Float'''''
*'''+Beam Piercing Effect Variance:'''
**Defines the variances of the particles from the main path
**Values close to 0 cause minimum variance, higher values cause higher variances
**Syntax: '''''Float'''''}}

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

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

===$Pspew:===
{{Table3610|
*Defines a particle spew effect for the given weapon
}}{{Table3613|
*'''+Index:'''
**indicates which spewer to add/edit/delete. may be 0-3. used for xmt compatibility.
**Syntax: '''''Integer'''''
*'''+Remove'''
**removes spewer at +Index: (requires +index:)
*'''+Type:'''
**type of particle spew
**Syntax: '''''String'', Default, Helix, Sparkler, Ring, or Plume '''
}}{{Table3610|
*'''+Count:'''
**Defines how many particles are spawn when they are ready to be created (at each +Time: interval)
**Syntax: '''''Integer'''''
*'''+Time:'''
**Defines the time in milliseconds between next particle(s) spewed
**Syntax: '''''Integer''''', milliseconds
*'''+Vel:'''
**Defines the created particles velocity as percentage of the weapons velocity
**Syntax: '''''Float'''''
*'''+Radius:'''
**Defines the size of the created particles
**Syntax: '''''Float''''', meters
*'''+Life:'''
**Defines how long the particles last.
**Syntax: '''''Float''''', seconds
*'''+Scale:'''
**Defines the particle spread. Small value will make particles group together
**typically controls how big the effect is or how fast it moves away from the weapon path on a perpendicular (or sometimes arbitrary) axis.
**helical spews and rings use this value to control how fast the particle helix moves away from the central axis.
**sparklers use this to control how fast particles move away from the spawn point, in any direction
**plumes use this to set the diameter of the disk across which particles are spawned
**Syntax: '''''Float'''''
}}{{Table3613|
*'''+Z Scale:'''
**for sparklers, allows you to elongate the effect to surround other effects, like lasers. essentially a length multiplier
**for plume, it multiplies against +scale to set the plume to spread or converge, zero would be full convergence, 1 would be straight flight, and bigger numbers would cause particles to diverge from the disk.
**Syntax: '''''Float'''''
*'''+Rotation Rate:'''
**used only by helical spews, controls how many rotations per second the helix makes
**Syntax: '''''Float'', may be negative, useful for setting up 2 spews that spin in opposite directions'''
*'''+Offset:'''
**position of effect with regards to the weapon center
**Syntax: '''''Vector'''''
*'''+Initial Velocity:'''
**to indicate both direction and speed of particle effects regards to the weapon velocity and +scale:
**Syntax: '''''Vector'''''
}}{{Table3610|
*'''+Bitmap:
**Defines the animation used to create the particle spew effect
**Syntax: '''''String''''', filename}}

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

*Sets this weapon as a TAG missile, level 1, 2, or 3. The second number is the duration in seconds.
*TAG Level 1 will illuminate hidden targets such as stealth fighters or ships normally obscured by nebula conditions.
*TAG Level 2 illiminates targets much like TAG Level 1, but turrets will prefer to shoot at them over other ships.
*TAG Level 3 has no effect in retail.
{{Table3610|
*TAG Level 3 allows the weapon to trigger [[Weapon.tbl#$SSM:|SSMs]]}}

*Syntax: '''''Integer''''' '''''Float''''', TAG level and seconds respectively

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

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

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

===$decal:===
{{Table3610|
*Defines impact decals if they are in use
*'''+texture:'''
**Defines the texture used for impact decals (can use '''''-burn''''' and '''''-glow''''' textures)
**Syntax: '''''String''''', filename
*'''+backface texture:'''
**Defines ???
**Syntax: '''''String''''', filename
*'''+radius:'''
**Defines the size of the impact decals on target
**Syntax: '''''Float''''', meters
*'''+burn time:'''
**Defines the time the '''''-burn''''' texture appears on the target
**Syntax: '''''Integer''''', milliseconds}}
{{Table3613|
*Feature removed - table parsing retained to maintain compatibility}}

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

===$Weapon Hitpoints:===
{{Table3611|
*Defines the amount of hitpoints a weapon has.
*Weapons with '''"bomb"''' flag have 50 hitpoints by default
*Giving weapon hitpoints makes it possible for the weapon to be shot down or be destroyed by EMP.
**Syntax: '''''Integer'''''
}}

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

===$Burst Shots:===
{{Table3611|
*Defines the number of shots in a burst
*Shots in a burst use shorter ( '''$Burst Delay:''' ) delay than usually
**Syntax: '''''Integer'''''}}

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

===$Burst Flags:===
{{Table3611|
*Defines the flags used to define the burst firing behaviour
**Syntax: ( '''''String''''' '''''String''''' ), list of flags
**Available burst flags:
***'''"fast firing"''', acts as if '''same turret cooldown''' flag would be used between the shots in the burst.
***'''"random length"''', makes AI to fire burst of random length (from 1 to burst shots).}}

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

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

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

===$Substitute:===
{{Table3613|
*Feature causes crash to desktop when weapon is used with a turret.
*Defines a pattern of ammo to substitute for primary or secondary weapons. '''$substitute:''' can be repeated any number of times. ''+period'' and ''+index'' will grow the pattern array anytime something does not fit so any whole number will be accepted. If neither ''+period'' or ''+index'' is specified, it is assumed to be equivalent to ''+index: '''0'''''.
**Syntax: '''''Weapon Name'''''
*'''+period:'''
*Substitute '''Weapon Name''' every ''period'' shots. '''Mutually exclusive with ''+index'''''
**Syntax: '''''Positive Integer'''''
*'''+offset:'''
*Shift period pattern ''offset'' shots. '''Must be used with ''+frequency'''''
**Syntax: '''''Positive Integer'''''
*'''+index:'''
*Substitute the '''Weapon Name''' at ''index'' in the shot pattern. '''Mutually exclusive with ''+period'''''
**Syntax: '''''Positive Integer'''''
}}

==Weapons.tbl Flags==

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

==="Spawn ''Name'',''Value''"===
*Will spawn the specified number of defined missiles upon detonation.
{{Table3610|
*Multiple spawn types can be defined for a single 'carrier' weapon up to maximum of 5 different weapons}}

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

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

==="Huge"===
*Allows this weapon to do the final 10% damage to a ship with the "Big Damage" flag. Also the AI will not try to hit fighters with it.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==="stream"===
* Does nothing

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==="capital+"===
{{Table3613|
*Tells AI to use this weapon only on capital ships}}

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Sample==

<pre>
#Primary Weapons

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

#End

#Secondary Weapons

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

#End

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

[[Category:Tables]]

User-made Ships

2012-07-18T07:45:37Z

Headdie: Added tags to CCF Volkov and CCF Minsk

__NOTOC__
{|-
{|border=0 cellpadding=4 cellspacing=0 style="margin: 0 0 1em 1em; background: #000; border: 0px #000 solid; border-collapse: collapse;"
|-
|{{UMS-Legend}}
|width=510px|The following is a list of released, user-made ship mods for [[Freespace 2]], for use in the creation of custom missions and campaigns. 
*For canon ship classes from FreeSpace: The Great War: [[Great War-era craft]]
*For canon ship classes from FreeSpace 2: [[FreeSpace 2-era craft]]
*For ships from The Babylon Project: [[TBP shiplist|The Babylon Project craft]]
*For ships from Wings of Dawn: [[Wings_of_Dawn_Ships|Wings of Dawn craft]]
|-
|}
|}

==Downloadable mods==
==Fighter Craft==
__NOTOC__
{| border=1 cellpadding=0 style="background:#351515;"
|- align="center"
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Vasudan'''
| style="width:200px" |'''Shivan'''
| style="width:200px" |'''Other'''
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[Bad Ulysses]] {{WH}}{{WU}}{{WN}}{{BC}}
| style="width:200px" | [[GTF Perseus Adv]]
| style="width:200px" | [[GVAf Apis]]
| style="width:200px" | [[SF Chelob]]
| style="width:200px" | [[AF Charlatan]]
|- align="left"
| style="width:200px" | [[CCF Minsk]] {{WU}}{{WN}}
| style="width:200px" | [[GTF Phoenix (Nuke)]]
| style="width:200px" | [[GVDr Scarab]]
| style="width:200px" | [[SF Chimera]]
| style="width:200px" | [[AF Kato]]
|- align="left"
| style="width:200px" | [[CCF Volkov]] {{WU}}{{WN}}
| style="width:200px" | [[GTF Phoenix (TrashMan)]]
| style="width:200px" | [[GVF Anouke]]
| style="width:200px" | [[SF Gorgon]]
| style="width:200px" | [[AF Phylaki]]
|- align="left"
| style="width:200px" | [[EAF Acheron]]
| style="width:200px" | [[GTF Raziel]]
| style="width:200px" | [[GVF Apis]]
| style="width:200px" | [[SF Harpy]]
| style="width:200px" | [[Bek'Tah Interceptor]]
|- align="left"
| style="width:200px" | [[EAF Claymore Mk1]]
| style="width:200px" | [[GTF Selkie]] {{WH}}{{WU}}{{BC}}
| style="width:200px" | [[GVF Ennead]]
| style="width:200px" | [[SF Hydra]]
| style="width:200px" | [[HEF Blizzard]]
|- align="left"
| style="width:200px" | [[EAF Claymore Mk2]]
| style="width:200px" | [[GTF Starstrider]]
| style="width:200px" | [[GVF Heket]]
| style="width:200px" | [[SF Ifrit]]
| style="width:200px" | [[KCSL Kama]]
|- align="left"
| style="width:200px" | [[EAF Claymore Mk3]]
| style="width:200px" | [[GTF Svalin]]
| style="width:200px" | [[GVF Heptu]]
| style="width:200px" | [[SF Naga]]
| style="width:200px" | [[Lethe]]
|- align="left"
| style="width:200px" | [[EAF Lethe]]
| style="width:200px" | [[GTF Vampire]]
| style="width:200px" | [[GVF Heset]]
| style="width:200px" | [[SF Scorpion II]]
| style="width:200px" | [[Lizard Huntercraft]]
|- align="left"
| style="width:200px" | [[EAF Stentor]]
| style="width:200px" | [[GTF Vesuvius]]
| style="width:200px" | [[GVF Imset]]
| style="width:200px" | [[SF Serpent]]
| style="width:200px" | [[Lizard Killercraft]]
|- align="left"
| style="width:200px" | [[EAF Styx]]
| style="width:200px" | [[GTF Ymir]]
| style="width:200px" | [[GVF Khepri]]
| style="width:200px" | [[SF Succubus (INF)]]
| style="width:200px" | [[Lizard Swarmercraft]]
|- align="left"
| style="width:200px" | [[FTF Jackal]]
| style="width:200px" | [[GTVF Hestia]]
| style="width:200px" | [[GVF Mihos]]
| style="width:200px" | [[SF Succubus (Nuke)]]
| style="width:200px" | [[NF Banshee]]
|- align="left"
| style="width:200px" | [[FTF Lancer]]
| style="width:200px" | [[IH2 Sunrider]]
| style="width:200px" | [[GVF Reshef]]
| style="width:200px" | [[Space Spider]]
| style="width:200px" | [[NF Larvae]] {{WH}}{{WU}}{{BC}}
|- align="left"
| style="width:200px" | [[FTF Mig]]
| style="width:200px" | [[ITF Anan]]
| style="width:200px" | [[GVF Saqqara]]
| style="width:200px" |
| style="width:200px" | [[NF Phantasm]]
|- align="left"
| style="width:200px" | [[FTF Wraith]]
| style="width:200px" | [[ITF Benkei]]
| style="width:200px" | [[GVF Scarab]]
| style="width:200px" |
| style="width:200px" | [[NF Unknown]]
|- align="left"
| style="width:200px" | [[FTFx Thor]]
| style="width:200px" | [[ITF Oni]]
| style="width:200px" | [[GVF Seker]]
| style="width:200px" |
| style="width:200px" | [[RLF Panther]]
|- align="left"
| style="width:200px" | [[GTF Achilles]]
| style="width:200px" | [[PF Chimera]]
| style="width:200px" | [[GVF Shrike]]
| style="width:200px" |
| style="width:200px" | [[RLF Tigris]]
|- align="left"
| style="width:200px" | [[GTF Agias]]
| style="width:200px" | [[PF Hellbat]]
| style="width:200px" | [[GVF Shu]]
| style="width:200px" |
| style="width:200px" | [[T-MF Cataphract]]
|- align="left"
| style="width:200px" | [[GTF Alves]]
| style="width:200px" | [[PF Satyr]]
| style="width:200px" | [[PVDr Jackal]]
| style="width:200px" |
| style="width:200px" | [[T-MF Hussar]]
|- align="left"
| style="width:200px" | [[GTF Angel (non-canon)|GTF Angel]]
| style="width:200px" | [[PF Shagrath]]
| style="width:200px" | [[PVF Seshat]]
| style="width:200px" |
| style="width:200px" | [[UF Notus]]
|- align="left"
| style="width:200px" | [[GTF Antaeus]]
| style="width:200px" | [[PF Vulture]]
| style="width:200px" | [[VEF Anhur MkIV]]
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Apollo Prototype]]
| style="width:200px" | [[PTF Kulas]]
| style="width:200px" | [[VEF Aoh]]
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Archon]]
| style="width:200px" | [[Pyro GX]]
| style="width:200px" | [[VEFx Yaaru]]
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Aurora]]
| style="width:200px" | [[Scimitar (Aldo)]]
| style="width:200px" | [[VRC Inpu]]
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Autolycus]]
| style="width:200px" | [[SOF Banshee]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Carabus]]
| style="width:200px" | [[SOF Chaos]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Chaos]]
| style="width:200px" | [[SOF Horae ]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Cyone]]
| style="width:200px" | [[SOF Ophion]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Daedelus]]
| style="width:200px" | [[Spacesuit]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Donar]]
| style="width:200px" | [[STVsF Nightwing]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Draco]]
| style="width:200px" | [[TDr Firebee]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Enceladus]]
| style="width:200px" | [[TF Falcon]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Eos]]
| style="width:200px" | [[TF Gefjon]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Ezechiel]]
| style="width:200px" | [[TF Ion]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Falcon]]
| style="width:200px" | [[TF Kestrel]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Hercules Mk3]]
| style="width:200px" | [[TF Kvasir]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Icarus]]
| style="width:200px" | [[TF Mustang Alpha]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Kelpie]]
| style="width:200px" | [[TF Mustang Beta]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Keres]]
| style="width:200px" | [[TF Shrike]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Ladiel]]
| style="width:200px" | [[UEF Izra'il]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Leto]]
| style="width:200px" | [[UTF Cherokee]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Losna]]
| style="width:200px" | [[UTF Comanche]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTF Maverick]]
| style="width:200px" | [[UTF Seminole]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}

==Bomber Craft==
__NOTOC__
{| border=1 cellpadding=0 style="background:#351515;"
|- align="center"
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Vasudan'''
| style="width:200px" |'''Shivan'''
| style="width:200px" |'''Other'''
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[CCB Gurkov]]
| style="width:200px" | [[GTB Hydra]]
| style="width:200px" | [[GTVB Hesat]]
| style="width:200px" | [[SB Durja]]
| style="width:200px" | [[AB Attis]]
|- align="left"
| style="width:200px" | [[EAB Gagana]]
| style="width:200px" | [[GTB Jotun]]
| style="width:200px" | [[GVB Atlas]]
| style="width:200px" | [[SB Kahlan]]
| style="width:200px" | [[AB Satyr]]
|- align="left"
| style="width:200px" | [[EAB Peregrine]]
| style="width:200px" | [[GTB Kronus]]
| style="width:200px" | [[GVB Imset]]
| style="width:200px" | [[SB Kasdeya]]
| style="width:200px" | [[AB Zakros]]
|- align="left"
| style="width:200px" | [[FTB Saracen]]
| style="width:200px" | [[GTB Maelstrom]]
| style="width:200px" | [[GVB Petbe]]
| style="width:200px" | [[SB Vindhyachal]]
| style="width:200px" | [[Bek'Tah Bomber]]
|- align="left"
| style="width:200px" | [[GTB Apollyon]]
| style="width:200px" | [[GTB Nemesis]]
| style="width:200px" | [[VEB Shai]]
| style="width:200px" | [[SB Yali]]
| style="width:200px" | [[NB Unknown]]
|- align="left"
| style="width:200px" | [[GTTB Armageddon]]
| style="width:200px" | [[GTB Phoebus]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" | [[T-MB Cuirassier]]
|- align="left"
| style="width:200px" | [[GTB Holler]]
| style="width:200px" | [[GTB Rhea]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" | [[NB Ghoul]]
|- align="left"
| style="width:200px" | [[TB Atlas]]
| style="width:200px" | [[GTB Sabus]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTB Azaes]]
| style="width:200px" | [[GTsB Scimitar]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTB Callisto]]
| style="width:200px" | [[GTB Surt]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTVB Chnubis]]
| style="width:200px" | [[GTB Thunderbolt]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTB Claymore]]
| style="width:200px" | [[GTB Uriel]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTB Danaus]]
| style="width:200px" | [[PB Sepuelture]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTB Diana]]
| style="width:200px" | [[UTB Navajo]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTB Gagana]]
| style="width:200px" | [[UTB Yurok]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTB Hera]]
| style="width:200px" | [[SOB Jotun D.H.]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[UEB Vajradhara]]
| style="width:200px" | [[GTB Archangel]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|- align="left"
| style="width:200px" | [[GTB Berserker]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}

==Capital Ships (Cruisers, Corvettes, Frigates and Gunships)==
__NOTOC__
{| border=1 cellpadding=0 style="background:#351515;"
|- align="center"
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Vasudan'''
| style="width:200px" |'''Shivan'''
| style="width:200px" |'''Other'''
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[CCCa Andropov]]
| style="width:200px" | [[SOC Orc]]
| style="width:200px" | [[GVC Aten Mk2]]
| style="width:200px" | [[SC Abel]]
| style="width:200px" | [[AC Gordia]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAC Aesacus]]
| style="width:200px" | [[TC Damocles]]
| style="width:200px" | [[GVC Mafdet]]
| style="width:200px" | [[SC Lamia]]
| style="width:200px" | [[AC Heraklion]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAC Avalonian]]
| style="width:200px" | [[UEC Sanctus]]
| style="width:200px" | [[GVC Mekhet]]
| style="width:200px" | [[SC Raguel]]
| style="width:200px" | [[AC Malia]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAC Eclipse]]
| style="width:200px" | [[EACv Darkness]]
| style="width:200px" | [[GVC Newet]]
| style="width:200px" | [[SC Rictus]]
| style="width:200px" | [[NC Unknown]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAC Evangelist]]
| style="width:200px" | [[GTCv Ajax]]
| style="width:200px" | [[GVC Sai]]
| style="width:200px" | [[SCv Scylla]]
| style="width:200px" | [[ACv Malia]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Aegis (158th)]]
| style="width:200px" | [[GTCv Alexandria]]
| style="width:200px" | [[GVC Somtus]]
| style="width:200px" | [[SFg Damini]]
| style="width:200px" | [[ACv Phaistos]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Aegis (OTT)]]
| style="width:200px" | [[GTCv Bellerophon]]
| style="width:200px" | [[GVC Asarte]]
| style="width:200px" | [[SGs Asura]]
| style="width:200px" | [[NCv Unknown]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Aegis (IPA)]]
| style="width:200px" | [[GTCv Chimera]]
| style="width:200px" | [[GVC Naunet]]
| style="width:200px" |
| style="width:200px" | [[AC Heraklion (ASW)]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Alcyone]]
| style="width:200px" | [[GTCv Chiron]]
| style="width:200px" | [[HLC Defiler]]
| style="width:200px" |
| style="width:200px" | [[AKFf Adamantium]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTBC Black Widow]]
| style="width:200px" | [[GTCv Cobra]]
| style="width:200px" | [[VEC Joh]]
| style="width:200px" |
| style="width:200px" | [[AKCve Orichalcum]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTBC Blade]]
| style="width:200px" | [[GTCv Eris]]
| style="width:200px" | [[GVCv Mandes]]
| style="width:200px" |
| style="width:200px" | [[KCSL Hecatos]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Boreas]]
| style="width:200px" | [[GTCv Nike]]
| style="width:200px" | [[GVCv Pachet]]
| style="width:200px" |
| style="width:200px" | [[AKCs Iliaster]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Cretheus]]
| style="width:200px" | [[GTCv Oberon]]
| style="width:200px" | [[GVCv Udjat]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Eris]]
| style="width:200px" | [[GTCv Ragnarok]]
| style="width:200px" | [[GVCv Petbe]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Garm]]
| style="width:200px" | [[GTCv Reyena]]
| style="width:200px" | [[VECv Duat]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Gryphon]]
| style="width:200px" | [[GTCv Valhalla]]
| style="width:200px" | [[VECv Geb]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Hyperion]]
| style="width:200px" | [[ITCv Raiden]]
| style="width:200px" | [[GVMCv Wepwawet]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Mars]]
| style="width:200px" | [[NTCv Echelon]]
| style="width:200px" | [[GVC Repten]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTxC Njord]]
| style="width:200px" | [[PTCv Baranek]]
| style="width:200px" | [[GVCv Satyrs]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Odysseus]]
| style="width:200px" | [[SOCv Ehreos]]
| style="width:200px" | [[GTVF Amon-Re]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Ophion]]
| style="width:200px" | [[SOCv Neptune]]
| style="width:200px" | [[GVC Tuket]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Orc]]
| style="width:200px" | [[SOCv Phobos ADv|SOCv Phobos Adv]]
| style="width:200px" | [[GVGs Hemsut]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCt Piranha]]
| style="width:200px" | [[GTFg Chrysaor]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Ticonderoga]]
| style="width:200px" | [[GTFg Retribution]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Tyr]]
| style="width:200px" | [[GTFf Saphah]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Unknown]]
| style="width:200px" | [[UEFg Karuna]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Vidar]]
| style="width:200px" | [[UEFg Narayana]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[LPC Galleon]]
| style="width:200px" | [[GTGs Antwerpen]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[PC Rumrunner]]
| style="width:200px" | [[GTGs Enforcer]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[ITC Dainishi]]
| style="width:200px" | [[GTGb Praetorian]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCv Morana]]
| style="width:200px" | [[GTC Rhea]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCv Tane]]
| style="width:200px" | [[GTCv Phobos]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[SOC Oculus]]
| style="width:200px" | [[GTC Avenger]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTVFg Arpyia]]
| style="width:200px" | [[GTMf Sparta]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[Phoenix Rising]]
| style="width:200px" | [[GTCv Calypso]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTC Atlantis]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}

==Large Capital Ships (Carriers, Destroyers and Super Destroyers)==
__NOTOC__
{| border=1 cellpadding=0 style="background:#351515;"
|- align="center"
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Vasudan'''
| style="width:200px" |'''Shivan'''
| style="width:200px" |'''Other'''
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTBCr Tennyson]]
| style="width:200px" | [[GTD Gaia]]
| style="width:200px" | [[GVCa Kabechet]]
| style="width:200px" | [[SCa Shiamak]]
| style="width:200px" | [[ACa Akrotiri]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EACa Telemus]]
| style="width:200px" | [[GTD Henderson]]
| style="width:200px" | [[GVCa Tanen]]
| style="width:200px" | [[SD Iblis]]
| style="width:200px" | [[AD Achladia]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCa Canberra]]
| style="width:200px" | [[GTD Hera]]
| style="width:200px" | [[GVD Apothess]]
| style="width:200px" | [[SD Kismat]]
| style="width:200px" | [[AD Odigitria]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCar Fury]]
| style="width:200px" | [[GTD Icelus]]
| style="width:200px" | [[GVD Asarte]]
| style="width:200px" | [[SD Vassago]]
| style="width:200px" | [[AD Pylos]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCa Galaxy]]
| style="width:200px" | [[GTD Legion (Orion)]]
| style="width:200px" | [[GVD Hedetet]]
| style="width:200px" | [[SSD Diablo]]
| style="width:200px" | [[ND Unknown]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTTCa Hestia]]
| style="width:200px" | [[GTD Megaera]]
| style="width:200px" | [[HLD Mefdef]]
| style="width:200px" |
| style="width:200px" | [[ASD Minos]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCa Phoenix]]
| style="width:200px" | [[GTD Ioa]]
| style="width:200px" | [[VCI Bastet]]
| style="width:200px" |
| style="width:200px" | [[HEC Typhoon]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCr Trifid]]
| style="width:200px" | [[GTHD Orion Mk2]]
| style="width:200px" | [[GVSD Hetka]]
| style="width:200px" |
| style="width:200px" | [[AKBc Azoth]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCa Warlock]]
| style="width:200px" | [[GTD Orion Phase II]]
| style="width:200px" | [[GVD Hathor]]
| style="width:200px" |
| style="width:200px" | [[NCa Vampire]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[TCa Constellation]]
| style="width:200px" | [[GTD Raynor]]
| style="width:200px" | [[GVD Pharaoh]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[TCa Sagittarius]]
| style="width:200px" | [[GTD Sirona]]
| style="width:200px" | [[GVD Apophis]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAD Lindos]]
| style="width:200px" | [[GTD Titan]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EASD Nemesis]]
| style="width:200px" | [[GTD Wotan]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAD Tereus]]
| style="width:200px" | [[GTD Zagreus]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[CCD Kiev]]
| style="width:200px" | [[ITD Ryujin]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[FD Vexor]]
| style="width:200px" | [[NTD Liberty]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTD Agamenmon]]
| style="width:200px" | [[Emperor]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTD Alexander]]
| style="width:200px" | [[SOD Segomo]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTD Atropos]]
| style="width:200px" | [[TD Reliant]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTD Boreas]]
| style="width:200px" | [[UED Solaris]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTD Daegon]]
| style="width:200px" | [[GTCa Nemesis (Old)]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTSD Bastion]]
| style="width:200px" | [[SOC Galatea]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[SOSD Olemus]]
| style="width:200px" | [[GTSD Odin]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTSD Anchorage]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}

==Super Capital Ships (Battleships, Dreadnoughts and Juggernauts)==
__NOTOC__
{| border=1 cellpadding=0 style="background:#351515;"
|- align="center"
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Vasudan'''
| style="width:200px" |'''Shivan'''
| style="width:200px" |'''Other'''
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTVBS Archangel Mk2]]
| style="width:200px" | [[SODn Solaris]]
| style="width:200px" | [[GVSJ Sechat-Hor]]
| style="width:200px" | [[SJ Amritaya]]
| style="width:200px" | [[AJ Androgeos]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTDn Archangel]]
| style="width:200px" | [[TSJ Icanus]]
| style="width:200px" |
| style="width:200px" | [[SSJ Dante]]
| style="width:200px" | [[Vishnan Preserver]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTBs Moscow]]
| style="width:200px" | [[GTVA Colossus Mk II]]
| style="width:200px" |
| style="width:200px" | [[SSJ Gigas]]
| style="width:200px" | [[AJ Androgeos (Old)]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTVA Titan]]
| style="width:200px" | [[TSJ Amaterasu]]
| style="width:200px" |
| style="width:200px" | [[SPD Vinaashak]]
| style="width:200px" | [[HEHc Hurricane V]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" | [[SSJ Gigas (Old)]]
| style="width:200px" |
|}

==Installations (Dry Docks, Star Bases and Jump Gates)==
__NOTOC__
{| border=1 cellpadding=0 style="background:#351515;"
|- align="center"
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Vasudan'''
| style="width:200px" |'''Shivan'''
| style="width:200px" |'''Other'''
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[CI Haven]]
| style="width:200px" | [[GTI Melia]]
| style="width:200px" | [[GVI Abthys]]
| style="width:200px" | [[SI Acridon]]
| style="width:200px" | [[AI Thera]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAI Andromeda]]
| style="width:200px" | [[GTI Nareos]]
| style="width:200px" | [[GVI Cairo]]
| style="width:200px" | [[SI Arachnas]]
| style="width:200px" | [[AI Pyrgos]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAI Lycaon]]
| style="width:200px" | [[GTI Samson]]
| style="width:200px" | [[GVI Cairo Extension]]
| style="width:200px" | [[SI Hara]]
| style="width:200px" | [[AKI Alkahest]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTI Acheron]]
| style="width:200px" | [[GTDI Titan]]
| style="width:200px" | [[GVI Cheops]]
| style="width:200px" | [[Shivan JumpGate]]
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTI Aeglos]]
| style="width:200px" | [[GTI Whitehall]]
| style="width:200px" | [[GVI Karnak]]
| style="width:200px" | [[SI Arachnas(Old)]]
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTExD Arcadia Defender]]
| style="width:200px" | [[ITI Yomi]]
| style="width:200px" | [[GVI Ogdoad]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTI Arcas]]
| style="width:200px" | [[PCI Phoron]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTI Asteria]]
| style="width:200px" | [[TI Achilles]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTI Athens]]
| style="width:200px" | [[TSS Exos]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTI Atlantis]]
| style="width:200px" | [[TDS 1]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTMI Aule]]
| style="width:200px" | [[TDS 2]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTI Bretonia]]
| style="width:200px" | [[TPG 1]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTI Chamelion]]
| style="width:200px" | [[Alliance Jump Gate]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTDk Acropolis]] {{WH}}{{WU}}
| style="width:200px" | [[GTExA]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTDS Goliath]]
| style="width:200px" | [[Intrasystem Gate]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTExC]]
| style="width:200px" | [[Asteroid Installation]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[Jump Gate]]
| style="width:200px" | [[Gas Refinery]] {{WH}}{{WU}}{{WN}}
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTI Silex]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}

==Non-Combatants (Freighters, Transports and Auxilliaries)==
__NOTOC__
{| border=1 cellpadding=0 style="background:#351515;"
|- align="center"
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Vasudan'''
| style="width:200px" |'''Shivan'''
| style="width:200px" |'''Other'''
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAFr Belus]]
| style="width:200px" | [[GTT Corsair]] {{WH}}{{WU}}
| style="width:200px" | [[GVFr Shai]]
| style="width:200px" | [[ST Xerxes]]
| style="width:200px" | [[RLFr Margay]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Aether]]
| style="width:200px" | [[GTT Naxos]]
| style="width:200px" | [[GVT Isten]]
| style="width:200px" |
| style="width:200px" | [[ATT Dallie]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTDS Briareos]]
| style="width:200px" | [[GTT Svalin]] {{WU}}
| style="width:200px" | [[GVT Qeb]]
| style="width:200px" |
| style="width:200px" | [[AS Kamilari]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Clarius]]
| style="width:200px" | [[GTT Titan]]
| style="width:200px" | [[GVT Sesmu]]
| style="width:200px" |
| style="width:200px" | [[LS Bek'Tah|Bek'Tah Support Ship]] {{WU}}
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Cyllene]]
| style="width:200px" | [[TT Pericles]]
| style="width:200px" | [[GVSC Imhotep]]
| style="width:200px" |
| style="width:200px" | [[AFr Phaistos]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Demeter]]
| style="width:200px" | [[UET Kadmos]]
| style="width:200px" | [[GVSC Neith]]
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Sizifus]]
| style="width:200px" | [[UET Upanishad]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Ulmo]]
| style="width:200px" | [[GTA Caerus]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Vela]]
| style="width:200px" | [[GTE Ehnaton]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[UEFr Demeter]]
| style="width:200px" | [[GTE Vidar]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[TG Bromios]]
| style="width:200px" | [[TSC Icarus]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCol Columbus]]
| style="width:200px" | [[UEA Oculus]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCVl Majestic]]
| style="width:200px" | [[Terran Probe]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTCVl Splendid]]
| style="width:200px" | [[GTEP Bachus]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTL Anemoi]] {{WH}}{{WN}}
| style="width:200px" | [[GTS Abaris]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[UEM Florence]] {{WH}}{{WN}}
| style="width:200px" | [[GTS Eos]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFT Constantine]]
| style="width:200px" | [[GTT Anatis]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTSC Copernicus]]
| style="width:200px" | [[PATr Baracuda]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTSC Cyrene]]
| style="width:200px" | [[GTT Star Rider]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTDr Phidias]] {{WH}}{{WU}}{{WN}}
| style="width:200px" | [[GTT Wyvern]] {{WH}}{{WU}}{{BC}}
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}

{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTSh Mercury]] {{WH}}{{WU}}{{WN}}{{BC}}
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}

==Other (Cargo Pods, Sentry Guns, Etc)==
__NOTOC__
{| border=1 cellpadding=0 style="background:#351515;"
|- align="center"
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Terran'''
| style="width:200px" |'''Vasudan'''
| style="width:200px" |'''Shivan'''
| style="width:200px" |'''Other'''
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[EAFr Belus Cargo]]
| style="width:200px" | [[GTFr Vela Cargo]]
| style="width:200px" | [[Vasudan Mine]]
| style="width:200px" | [[SSG Annihilator]]
| style="width:200px" | [[RLCg A09]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Clarius Cargo]]
| style="width:200px" | [[TDM Hephaestus]]
| style="width:200px" | [[GVSG Ammut]]
| style="width:200px" | [[SSG Erebos]]
| style="width:200px" | [[RLCg A17]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Cyllene Cargo]]
| style="width:200px" | [[GTSG Balmung]]
| style="width:200px" |
| style="width:200px" | [[SSG Somnath]]
| style="width:200px" | [[AC Phaistos Cargo]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Sizifus Cargo 1]]
| style="width:200px" | [[GTSG Euphrates]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" | [[TDD]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTFr Sizifus Cargo 2]]
| style="width:200px" | [[GTSG Safat]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" | [[Alien Defense Station]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[BSSG Myrdin]]
| style="width:200px" | [[Stalker Class Probe]] {{WH}}{{WU}}
| style="width:200px" |
| style="width:200px" |
| style="width:200px" | [[UNX]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTSG Gungnir]]
| style="width:200px" | [[GTSG Gunstar]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" | [[Serious Sandwich]]
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[GTSG Wolverine]]
| style="width:200px" | [[GTSG Pyre]]
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[Cargo Platform]] {{WH}}{{WU}}{{RI|Reason=Mod Incomplete Reasons#Cargo Platform}}
| style="width:200px" | [[Modular Construction Kit]] {{WH}}
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[TGas-1]] {{WH}}{{WU}}
| style="width:200px" | [[GTSG Sleipnir]] {{WH}}{{WU}}{{WN}}
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}
{| border=0 cellpadding=1 style="background:#000000;"
|- align="left"
| style="width:200px" | [[Gas Ring]] {{WH}}{{WU}}{{WN}}
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
| style="width:200px" |
|}

==Notes to Wiki contributors==
*To add a new ship use a sample template or copy and modify the source from an existing page. For screenshots I've been going with the size 480x340 as standard. But this is completely arbitrary and anything around that size is probably acceptable.
*The format can be difficult to edit. It is perfectly acceptable to simply tack on your ship at the bottom of the appropriate column. Someone else can then later edit it in if desired.
*When adding, please place your new ship in the appropriate column. There are two columns for Terrans, one for Vasudans and Shivans and one for other. If your ship belongs to a non-canon species please place it in the OTHER column.
*This is for mods which are not meant as replacements for stock models. Meaning that, an HTL version of the GTFr Chronos does not belong here. Modified stock models on other hand may be acceptable. Ie the GTFr Aether is a Chronos with a pod attached and an extra turret.
*Should two different models have the same name, add the author's name in brackets as a suffix. (or alternatively the mod pack name)
*Add only ready models which are released and freely available. Always include a download link. It is okay if you later update it.
*If you do not want to write a description for your mod, simply add the name of your ship, which redirects the browser to a download link or website.

[[Category: Mod Database]]

GTSC Copernicus

2012-07-11T16:23:18Z

Headdie: added download link to FoW so that there is a download for this

{{User-made Ships|''GTSC '''Copernicus'''''}}

{{shipimage|image=[[Image:Copernicus.jpg|500px]]|caption=GTSC Copernicus}}

==Description:==

===Tech Room Description===
After the second Shivan invasion, GTVA officials discovered the need for a science vessel that can conduct operations in dangerous areas without a sizable escort. The GTSC Copernicus was the answer to that problem. Much larger than the Faustus class, the ship spans 560 meters, and has an extremely advanced sensor array and is equipped with multiple on-board laboratories for a variety of projects. The Copernicus easily rivals most GTVA cruisers in offensive and defensive capabilities.

===Credits===
*Model by '''TrashMan'''

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Science Vessel
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| 30 mps
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| ???
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 560 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| [[Terran Turret]]
| 11
|- align="center"
| Terran Anti-Bomber Turret
| 4
|- align="center"
| Terran Medium Turret
| 3
|}

===Veteran Comments===

==Download link:==
[http://www.freespacemods.net/download.php?view.29 Flames of War | Freespacemods.net]

SSG Somnath

2012-04-30T10:43:29Z

Headdie:

{{User-made Ships|''SSG '''Somnath'''''}}

==Description:==

===Tech Room Description===

===Credits===
*Model by '''Headdie'''

===Notes===
*Original development resources are also included in the form of the original blender file, dae export, obj export and texture files.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Remote Beam Cannon
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 1000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Width|Width]]'''
| 62 m
|-
| '''[[Technical_Terms_and_Definitions#Height|Height]]'''
| 120 m
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 120 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| STurret
| 4
|}

===Veteran Comments===
{{comment|
Headdie
STurret is a toned down sred beam cannon}}

==Download link:==
http://www.freespacemods.net/download.php?view.820

SSG Somnath

2012-04-30T10:43:11Z

Headdie: Created

{{User-made Ships|''SSG '''Somnath'''''}}

==Description:==

===Tech Room Description===

===Credits===
*Model by '''Headdie'''

===Credits===
*Original development resources are also included in the form of the original blender file, dae export, obj export and texture files.

==Performance:==
===Statistics===
{|
|-
| style="width:200px" | '''[[Technical_Terms_and_Definitions#Type|Type]]'''
| style="width:200px" | Remote Beam Cannon
|-
| '''[[Technical_Terms_and_Definitions#Manufacturer|Manufacturer]]'''
| Unknown
|-
| '''[[Technical_Terms_and_Definitions#Maneuverablity|Maneuverability]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Velocity|Max Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Max Afterburner Velocity|Max Afterburner Velocity]]'''
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Armor|Armor]]'''
| N/A
|-
| [[Technical_Terms_and_Definitions#Hitpoints|Hitpoints]]
| 1000
|-
| [[Technical_Terms_and_Definitions#Shields|Shields]]
| N/A
|-
| '''[[Technical_Terms_and_Definitions#Width|Width]]'''
| 62 m
|-
| '''[[Technical_Terms_and_Definitions#Height|Height]]'''
| 120 m
|-
| '''[[Technical_Terms_and_Definitions#Length|Length]]'''
| 120 m
|}

===Armaments===

*'''[[Technical_Terms_and_Definitions#Turrets|Turrets]]'''
{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| colspan=2 style="background:#351515;"| '''Default Statistics'''
|- align="center"
| style="width:120px" |Turret Type
| style="width:60px" |Amount
|- align="center"
| STurret
| 4
|}

===Veteran Comments===
{{comment|
Headdie
STurret is a toned down sred beam cannon}}

==Download link:==
http://www.freespacemods.net/download.php?view.820

Total conversions

2012-04-25T09:09:42Z

Headdie: /* Wing Commander Saga */

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

==Released total conversions==

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

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

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

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

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

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

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

*'''Current release:''' ''3.4 FINAL''

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

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

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

*'''Current release:''' ''Darkest Dawn''
*'''Previous releases:''' ''Prologue''

===[[Wings of Dawn]]===

[[Image:logowod.png]]

Wings of Dawn is an anime-themed original universe created by Spoon. It features new models, weapons, head-anis and music.

*'''Current release:''' ''Full Campaign of 25+ Missions''

==Other total conversions==

===[[Diaspora]]===

Diaspora is a second TC based on the Reimagined Battlestar Galactica show.

*'''Current status:''' ''WIP''

===[[The Apocalypse Project]]===
A total conversion based on the Homeworld franchise

===[[Shadows of Lylat|Star Fox: Shadows of Lylat]]===

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

[[Image:SoL.gif]]

===[[Fate of the Galaxy]]===

[[Image:FotGOnTop.jpg|300px]]

Fate of the Galaxy is a total conversion based on the Star Wars universe.

*'''Release Date:''' TBA

===[[Halo for FreeSpace]]===

Bringing the Halo universe to FreeSpace 2!

===[[Fringespace]]===

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

[[Image:Fs_logo_sm.jpg]]

[[Category:Main]]

Total conversions

2012-04-25T09:08:18Z

Headdie: /* Wing Commander Saga */

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

==Released total conversions==

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

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

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

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

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

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

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

*'''Current release:''' ''3.4 FINAL''

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

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

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

*'''Current release:''' ''Prologue'', ''Darkest Dawn''

===[[Wings of Dawn]]===

[[Image:logowod.png]]

Wings of Dawn is an anime-themed original universe created by Spoon. It features new models, weapons, head-anis and music.

*'''Current release:''' ''Full Campaign of 25+ Missions''

==Other total conversions==

===[[Diaspora]]===

Diaspora is a second TC based on the Reimagined Battlestar Galactica show.

*'''Current status:''' ''WIP''

===[[The Apocalypse Project]]===
A total conversion based on the Homeworld franchise

===[[Shadows of Lylat|Star Fox: Shadows of Lylat]]===

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

[[Image:SoL.gif]]

===[[Fate of the Galaxy]]===

[[Image:FotGOnTop.jpg|300px]]

Fate of the Galaxy is a total conversion based on the Star Wars universe.

*'''Release Date:''' TBA

===[[Halo for FreeSpace]]===

Bringing the Halo universe to FreeSpace 2!

===[[Fringespace]]===

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

[[Image:Fs_logo_sm.jpg]]

[[Category:Main]]

Ships and General Mod Creation

2011-09-11T19:37:21Z

Headdie: expanded Effects entry

Thanks to the work of the [[Source Code Project]] (SCP) team modifying FreeSpace 2 is now very easy, though understanding everything by yourself is extremely difficult with to date only one major modification released that could be called a solo project (see [[WoD]]). Your best bet to start Modifying is to focus on one area, at least to begin with, then once you have a grasp of how things work or you decide you are no longer interested in it and you feel like other areas interest you can start looking at them. Modifying any game calls on a wide array of talents from general creative writing to table editing, model making and the ever in demand skills of texture artists. This page is intended as a getting started and confidence builder as an in depth how to is a massive undertaking and the detailed information on how to mod FreeSpace is found within the modding section of this wiki with issue specific help and advice available on the Hard Light Productions forum.

==Before We Get Started==

===Your New Best Friends===

By closely reading this page, you have taken your first steps of making the most important friend every FreeSpace modder has - the Modding Portal of the FreeSpace Wiki. Within the Wiki's pages is a gold mine of information created by the SCP team and community members who have spent a huge amount of time and effort making sure things work, and how they work is well documented.

Your next best friends are in your FreeSpace2\data folder, and they are fs2_open.log and fred2_open.log. These two files are the logs generated by the debug builds of FreeSpace 2 and the FRED2 editor. The way to tell between a release and debug build is that after the build cycle number in the file name there is a d for debug or r for regular, eg 3.6.12d. any information after this point in the file name is information that tells the support guys exactly which version you are using. Whenever you are running a debug build of FreeSpace or FRED, the program creates a constant record of the program's activity and lists any error messages where possible that occur and stores that record in the listed log files. Debug builds try to catch every error they can while release builds try to ignore them, making debug build an invaluable tool for error-checking. To open the logs, simply double click on them and, if prompted, select any text editor.

===Required:===

The following are required to create mods for FreeSpace Open:

*A working and legitimate copy of FreeSpace 2
*FreeSpace Open executable (preferably the latest stable build or, if you know what you are doing, a Nightly build)
*Imagination

==Getting Started:==

The first thing to know when modifying FreeSpace 2 is to understand how the mod structure works. Each mod needs its own folder within the FreeSpace 2 folder. For example, Wings of Dawn on my computer is C:\Games\Freespace2\Wings of Dawn. All files that directly relate to the WoD mod are found within this folder on my PC, though a file (mod.ini) within the folder tells FreeSpace to go and look for the mediavps mod. The mod structure allows for mods to be chained together in a simple fashion. Within the mod folders is another folder called data. The data folder is not present in mods relying on .[[VP]] files, which are container files that mimic the mod structure and are used to make distributing and installing mods easier. Within the data folder are the subfolders which the files that make the mod are stored. The subfolders are there to keep everyone sane and make everything easier to find. The majority are self-explanatory but a detailed breakdown can be found in [[FS2_Data_Structure]]. Below is a summary of important information relating to this tutorial.

*''Cache'' - To reduce loading times, the engine will generate a cache file for each model it encounters. Since cache generation can take quite long for more complex models, you should always include cache files for unique mods.
*''Cbanims'' - This is where command and mission briefing animations are stored.
*''Effects'' - Weapon and other 2D effects, stars, planets, nebulae, e.t.c.
*''Fonts'' - Font files are kept here. Unless you are aiming at a total conversion, you will in all likelihood not need this folder.
*''Hud'' - This is where custom HUD graphics go.
*''Intelanims'' - Animations used in the Techroom for weapons and intel sections are located here.
*''Interface'' - Images and animations used in the menu system go here. Not everything that you would expect to be a still is stored as a still, so research carefully before changing anything. Only larger mods and total conversions generally go into this because it is hard to do properly.
*''Maps'' - Texture files for ships and other model-based objects.
*''Missions'' - This is where FRED should be storing mission files and the only place where FS2 will look for missions both single player and campaign.
*''Models'' - .pof files go here no matter what purpose.
*''Music'' - In-game music files go here.
*''Sounds'' - Sound effects like weapons fire belong here.
*''Tables'' - This is where the .tbl and .tbm files go that tells the game how to use the majority of the information in the folders listed and also controls a number of other game aspects.
*''Voice'' - Voice overs for mission chatter.

==Simple Modifications==

One of the simplest things to do is add a new weapons or ships created by the community. The two are often related as ships created by members might have their own custom weapons.

===Adding A Ship===

The following will be an example of how to add a ship in FreeSpace:

*Go to [[SC Lamia]] in [[User-made Ships]] and download it.
*Create a folder in FreeSpace2 directory called New Ship.
*Within the New Ship directory, create a folder called data.
*Extract sc_lamia.rar. If you are unable to, you can download a file archiver such as 7-zip to extract the files.
*Inside the file are three folders called maps, models, and tables. Copy them into your New Ship\data folder without altering them.
*Create a mod.ini by opening a text editor. The following are required for the mod.ini to work:
**[launcher]
**modname = New Ship;
**[multimod]
**primarylist = ;
**secondarylist = mediavps_3612 ;
***This is optional. By having the mediavps_3612 listed in your secondarylist, you will use the SC Lamia as well as the Mediavps instead of the Lamia with retail FS2 assets.

Congratulations! You have just created your first mod. If you look in the maps folder there will be three .dds image files which make up the ship's texture. The models folder will contain SCLamia.pof, and in tables there are two .tbm files - one for the ship and one for a custom weapon for that ship.

There is one more thing I want you to do, though. Open sclamia-shp.tbm in a text editor and find the line starting $flags:. The full line reads ''$Flags: ( "cruiser" )''. Add "in tech database" with the quotation marks to the line between the parentheses so it reads ''$Flags: ( "cruiser" "in tech database" )''. Save and close the file. This allows the Lamia to be viewed in the Techroom from the beginning. Open your FreeSpace launcher and select New Ship as the mod and run the game. If you get an error message, go back to the file and double-check the flags line to the example I provided. When you reach the main screen go to the Techroom and at the bottom should be the Shivan cruiser you just added, the ship will not appear in any missions at this time because a mission file needs creating using the ship.

===Mod.ini===

Unlike other files, the mod.ini does not go in the data folder of a mod. Instead, this file goes in the main directory for the mod (e.g. Freespace2\New Ship for the above example) and adds the final polish to a mod. It performs useful tasks like linking other mods. Like many of the files in Freespace 2, this is basically a renamed .txt file and can be opened by any text editor. Let’s take a look at one.

# PLEASE NOTE ALL INI SETTINGS ARE *OPTIONAL*
# modname: Display name only, so you can have spaces instead of underscores for multi word MOD's
# image255x112: Location of a 255x112 bmp you wish to display in the launcher
# infotext: Text that will appear in the launcher
# website: Link to your website
# forum: Link to your forum
[launcher]
modname = Mod Name
image255x112 = mod-logo.bmp;
infotext = Here is a short blurb for the mod
# website = Here is where a web address goes if your mod has one
# forum = http://www.hard-light.net/forums

[multimod]
primarylist = ;
secondarylist = mediavps_3612;

This is the contents of the mod.ini for a sample mod.

Anything following a # is a comment and is ignored by the launcher.

The first section is information for the FreeSpace launcher and contains the following:

* modname: the name of the mod
* image255x112: the name of a 255x112 pixel .bmp to use as a mod image
* infotext: the area where you can put info about the mod and/or a tag line
* website: the link to your website that will be linked to the Website button in the launcher
* forum: the link to your forum that will be linked to the Forum button in the launcher

In the example shown both website and forum are commented out but if you remove the # and save they will be read by the launcher.

The next bit links the mod into other ones, the example above will call the 3.6.12 version of the mediavps to enhance the visuals of anything in FreeSpace 2 that is not touched by your mod. For example, if you turn the Ravana green, the Ravan will not be red because the mediaVPs_3612 is in the secondary line. However, it will become red if you have the mediavps_3612 in your primarylist. Most of the time, you will only use secondary list. This is the one you are recommended to use unless you know exactly what you are doing.

===Changing Other Mods===

You have downloaded some mod. You played it, and you have beaten it. However, you want to change something. Perhaps you feel the anti-fighter turrets are too weak or that there is a different ship you want to use. Do NOT add, remove, or change anything in the actual folder! This is because you will change the mod as long as the altered files are in there. What you should do is create a mod as explained in 'Adding A Ship' and place a mod.ini referencing the folder name for whatever mod you wish to alter in the secondary mod line. Then place the edit-that-you-want-to-make (e.g. model, .tbm, etc.) into this new mod. Once you have done all of that, select the new mod folder in the Freespace launcher’s mod tab and run. Because of the reference to the original in the mod.ini, that and any mods referenced by that mod will be loaded, but the changes you made will override the original. This way, you get to play your twist on the mod whenever you want without having to alter the original mod to play it.

==.VP==

Because of the ease in damaging data key to a mod or indeed retail, IT IS STRONGLY ADVISED THAT .VP FILES ARE NOT EDITED IN ANY WAY!

The advantage of a .vp file is ease of distribution. A .vp file is a container used to maintain the file structure. All that is required is that they are all placed in the mod folder. The problem with changing them is that if you edit one and get it wrong, you may have to reinstall the mod because there is no way for mod/FSO support teams to know what you have done to the .vp, and they have enough on their plate without having to user fix a problem that shouldn't have happened.

==.TBM VS. .TBL==

A .tbl is the core table file of that type, and only one can be loaded into FreeSpace at any one time. .tbl files provide the structure to the engine and require all basic elements to be present to work.

A .tbm (called [[Modular Tables]]) file, on the other hand, is an additional file to the .tbl, usually providing additional data to the .tbl or overriding it if needed. Generally, you'll be using a .tbm unless you're planning on doing a total conversion. .tbm files also have the advantage that FS2 can handle multiple .tbm files of any given type, though a modder should avoid conflicting entries at all costs.

==Closing Words==

I cannot overstate the usefulness of [[Portal:Modding]] and everything within its links. A good 90-95% of what I know about modding was learned in there and the rest was trial and error with a new newbie questions on the forum and IRC channel.

Another thing is that it is as a matter of courtesy to credit people whose resources you use. You are unlikely to get thrown out of the community for not doing so, but it is always nice to have that little nod of thanks.

Also on a side note: don’t change the name of the folder for and existing/downloaded mod. Many mods reference each other, and changing the name for the folder will break the links in the mod.ini of any mods that tries to use it. This increases the chance that there will be assets missing. On top of this, when you report the issues cause by changing folder name, you will be treated in a colder manner because you have broken the hard work that went into making sure the mod worked correctly in the first place. Lets face it. How would you react if you got your mod working nicely and someone comes to you because the mod doesn’t work by being renamed? And then several other people started to complain about the same problem?

Remember the most important thing when modding a FreeSpace is to have fun. It can be surprising how fun trial, error, and figuring things out for yourself can be.

Good luck and if you really do get stuck do not be afraid to ask questions.

[[Category:Tutorials|General Mod Creation]]

Ships and General Mod Creation

2011-05-29T17:15:28Z

Headdie: Added link to Modular Tables in tbm vs tbl

Thanks to the work of the [[Source Code Project]] (SCP) team modifying FreeSpace 2 is now very easy, though understanding everything by yourself is extremely difficult with to date only one major modification released that could be called a solo project (see [[WoD]]). Your best bet to start Modifying is to focus on one area, at least to begin with, then once you have a grasp of how things work or you decide you are no longer interested in it and you feel like other areas interest you can start looking at them. Modifying any game calls on a wide array of talents from general creative writing to table editing, model making and the ever in demand skills of texture artists. This page is intended as a getting started and confidence builder as an in depth how to is a massive undertaking and the detailed information on how to mod FreeSpace is found within the modding section of this wiki with issue specific help and advice available on the Hard Light Productions forum.

==Before We Get Started==

===Your New Best Friends===

By arriving at and closely reading this page you have taken your first steps to making the most important friend every freespace modder has, the modding portal of the freespace wiki. Within the Wiki's pages is a gold mine of information created by the SCP team and community members who have spent a huge amount of time and effort making sure things work and that how they work is well enough documented which is also why there are a few short, sharp "go read the wiki" comments on the forums.

Your next best friends are in your FreeSpace 2\data folder and they are fs2_open.log and fred2_open.log . These two files are the logs generated by the debug builds of FreeSpace 2 and the FRED 2 mission/campaign editor. The way to tell between a regular/retail and debug build is that after the build cycle number in the file name there is a d for debug or r for regular, eg 3.6.12d. any information after this point in the file name is information that tells the support guys exactly which file version you are using. Whenever you are running a debug build of FreeSpace or FRED the program creates a constant record of the programs activity and lists any error messages where possible that occur and stores that record in the listed log files, also debug builds try to catch every error they can while r builds try to ignore them so are an invaluable tool for error checking. To open the logs simply double click on them and if prompted select any text editor, though a word processor might render the log easier to read.

===Required:===

A working and legitimate copy of Freespace 2, FreeSpace Open executables (preferably the latest Stable build or nightly) and a bit of imagination. An internet connection you can readily access helps.

==Getting Started:==

The first thing to know when modifying FreeSpace 2 is to understand how the mod structure works. Each mod needs it's own folder within the FreeSpace 2 folder, for example Wings of Dawn on my computer is C:\Games\Freespace 2\Wings of Dawn . All files that directly relate to the WoD mod are found within this folder on my PC, though a file within the folder tells FreeSpace to go and look for the Media VPs mod, yes Media VPs are a mod, but the Mod structure allows for mods to be chained together in a simple fashion but that will be covered later. Within the mod folders is another folder called data, The data folder is not present in mods relying on .[[VP]] files, which are container files which mimic the mod structure and are used to make distributing and installing mods easier, again I will talk more about .VP files later. Within data are the sub folders which the files that make the mod are stored, the sub folders are there to keep everyone sane and make everything easy to find, the majority are self explanatory but a detailed breakdown can be found in [[FS2_Data_Structure]] but below I have summarized the information important to this tutorial.

''Cache'' - To reduce loading times, the engine will generate a cache file for each model it encounters. Since cache generation can take quite long for more complex models, you should always include cache files for unique mods.

''Cbanims'' - is where command and mission briefing animations are stored

''Effects'' - weapon and other 2d effects

''fonts'' - font files are kept here, unless you are aiming at a total conversion you will in all likelyhood not need this folder

''force feedback'' - unused in any mod that i know

''freddocs'' - the documents that are opened when you hit help in fred so just ignore again unless you are using a custom branch of Freespace engine

''hud'' - custom hud graphics

''intelanims'' - animations used in the techroom for weapons and intel sections

''interface'' - images and animations used in the menu system, note not everything you would expect to be a still is stored as a still so research carefully before changing anything. Again only larger mods and total conversions generally go into this stuff as it is very heavy going to do properly

''maps'' - Texture files for ships and other model based objects

''missions'' - where FRED2 should be storing mission files and the only place where FS2 will look for missions both single player and campaign

''models'' - .pof files go here no matter what purpose

''multidata'' - This is where the game stores player icons and other stuff downloaded during multiplayer sessions

''music'' - in game music files go here

''players'' - the files behind the Pilot screen on startup are stored here, not modding related except in very limited circumstances and is best just ignored unless the support guys tell you to go in there

''sounds'' - sound effects like weapons fire in here

''tables'' - last of the important ones, but the most important one, this is where the tbl and tbm files go that tells the game how to use the majority of the information in the folders listed and also controls a number of other game aspects.

''Voice'' - Voice overs for mission chatter

==Simple Modifications==

One of the simplest things to do is add a new weapon or ship created by the community and the two are often related as with new ships community members might decide they want to create a new weapon for it.

===Adding a ship===

First go to [[SC Lamia]] in [[User-made Ships]] and download it.
Next create a folder in FreeSpace 2 called New Ship and a data folder inside of that.
Then open up sc_lamia.rar if you cant there are a few small programs such as winrar that work with this format. Inside the file are 3 folders called maps, models and tables. The folders listed are identical in name to the folder names used in modifying freespace so copy them into your New Ship\data folder as they are. Congratulations you have just created your first mod. if you look in the maps folder there will be 3 .dds image files which make up the ships texture, in the models folder will contain SCLamia.pof and in tables there are two tbm files, one for the ship and one for a custom weapon for that ship. there is one more thing i want you to do though, open sclamia-shp.tbm in a text editor and find the line starting $flags: . the full line reads ''$Flags: ( "cruiser" )'' now add "in tech database" with the speech marks to the line between the brackets so it reads ''$Flags: ( "cruiser" "in tech database" )'' , save and close the file. Finally open your FreeSpace launcher and select New Ship as the mod and run the game, if you get an error message go back to the file and double check the flags line to the example I provided. When you reach the main screen go to the techroom and at the bottom should be the Shivan cruiser you just added, the ship wont appear in any missions at this time because a mission file needs creating using the ship. FreeSpace is that easy to mod, just drop the assets in the correct folders, making sure any related tables are altered to use it and off you go.

===The mod.ini===

At first glance this is a strange little file that just sits there and defies the convention that everything goes somewhere in the data folder of a mod. Instead this file goes in the main folder for the mod, eg Freespace 2\New Ship for the above example and is a very useful file which adds the final polish to a mod and performs useful tasks like linking into other mods. Like many of the files in Freespace 2 this is basically a renamed txt file and can be opened my any text editor. Let’s take a look at one.

‘# PLEASE NOTE ALL INI SETTINGS ARE *OPTIONAL*

‘# modname: Display name only, so you can have spaces instead of underscores for multi word MOD's

‘# image255x112: Location of a 255x112 bmp you wish to display in the launcher

‘# infotext: Text that will appear in the launcher

‘# website: Link to your website

‘# forum: Link to your forum

'[launcher]

'modname = Mod Name

'image255x112 = mod-logo.bmp;

'infotext = Here is a short blurb for the mod

‘#website = here is where a web address goes if your mod has one

‘#forum = http://www.hard-light.net/forums

[multimod]

primarylist = ;

secondarylist = MediaVPs_3612;

This is the contents of the mod.ini for a long term project I am working on with a few amendments.

Anything following a # is a comment and is ignored by any launcher reading it.

The first section is information for the FreeSpace launcher and contains:

* modname, the mod’s name,

* image255x112, the name of a 255x112 pixel bmp to use as a mod image

* infotext, is where you can put a little bit of info about the mod and/or a tag line

* website, activates the website button in the mod selection tab of your launcher and links it to your mod’s website if you have one

* forum, as above but for a forum.

In the example shown both website and forum are commented out but if you remove the # and save they will be read by the launcher.

The next bit links the mod into other ones, the example above will call the 3.6.12 version of the media vps to enhance the visuals of anything in Freespace 2 that is not touched by your mod, for example if you turn the Ravana green, because MediaVPs_3612 is in the secondary line it will not override this but it might do if you place it in primary. Most of the time you will only use secondary list and this is the one you are recommended to use unless you know exactly what you are doing.

***note
If you copy and paste the above example you will need to remove the ‘ from in front of each line it occurs.

===Changing Other Mods===

You have downloaded Blue Planet or some other mod, you played it and you have beaten it but you want to change something, perhaps you feel the anti-fighter turrets are too weak or that there is a different ship you want to use. Do Not Add, Remove Or Change Anything In The Actual Folder this is because you will change the mod as long as the altered files are in there, what you should do is create a mod as explained in Adding a ship and place a mod.ini referencing the folder name for Blue Planet or which ever mod you wish to alter in the secondary mod line. Then place the ship/tbm/whatever into this new mod. Once you have done all of that select the new mod folder in the Freespace launcher’s mod tab and run. Because of the reference to blue planet in the mod.ini that and mods referenced by Blue Planet will be loaded but the changes you made will override the original. This way you get to play your twist on the mod whenever you want but you don’t have to delve into the mod folders to play it as originally intended you just play the mod like you did before.

==On VP files==

Because of the ease in damaging data key to a mod or indeed retail IT IS STRONGLY ADVISED THAT .VP FILES ARE NOT EDITED IN ANY WAY!

The significant advantage of a VP file is ease of distribution. in simple terms a VP file is a container used to maintain the file structure between users because all that is required is that they are all placed in the Mod folder. the problem with changing them is that if you edit one and get it wrong the simple fix and in all likely hood the fix you will be told to do is to reinstall fs2/the mod as appropriate because there is no way for mod/FSO support teams to know what you have done to the VP and they have enough on their plate without having to user fix a problem that shouldn't have happened especially as the mod folders feature has been provided as a means achieving the same effect that requires no modifying of VPs.

==tbm vs tbl==

A tbl is the core table file of that type and only one can be loaded into freespace at any one time tbl files provide the structure to the engine and usually require all basic elements to be present to work.
tbm (called [[Modular Tables]]) on the other hand is an additional file to the tbl, usually providing additional data to the tbl or overriding it if needed. Until you get to the stage of building mods for more than adding a few ships you will probably only use tbm if available for that table type. tbm also has the advantage that FS2 can handle multiple tbm files of any given type though avoid conflicting entries at all costs.

==Closing Words==

I cannot over state the usefulness of [[Portal:Modding]] and everything within its links, a good 90-95%of what I know about modding was learned in there and the rest was trial and error with a new newbie questions on the forum and IRC channel.

Another thing is that it is as a matter of courtesy to credit people who’s resources you use, you are unlikely to get thrown out of the community for not doing so but it is always nice to have that little nod of thanks.

Also on a side note don’t change the name of the folder for and existing/downloaded mod, many mods reference each other and changing the name for the folder will brake the links in the mod.ini of any mods that tries to use it, which increases the chance that there will be assets missing or you end up using old assets. On top of this when you report the issues cause by changing folder name you will be treated in a colder manner because you have broken the hard work that went into making sure the mod worked correctly in the first place through a deliberate act. Lets face it, how would you react if you got your mod working nicely and someone comes to you because the mod doesn’t work because they changed something? And then several people started to complain with the same avoidable problem?

Remember the most important thing when modding a game, FreeSpace or any other like any hobby is to have fun. Also it can be surprising how fun trial, error and figuring things out for yourself can be.

Good luck and if you really do get stuck dont be afraid to ask questions.

[[Category:Tutorials|General Mod Creation]]

Ships and General Mod Creation

2011-05-28T21:07:42Z

Headdie: typo in the opening section

Thanks to the work of the [[Source Code Project]] (SCP) team modifying FreeSpace 2 is now very easy, though understanding everything by yourself is extremely difficult with to date only one major modification released that could be called a solo project (see [[WoD]]). Your best bet to start Modifying is to focus on one area, at least to begin with, then once you have a grasp of how things work or you decide you are no longer interested in it and you feel like other areas interest you can start looking at them. Modifying any game calls on a wide array of talents from general creative writing to table editing, model making and the ever in demand skills of texture artists. This page is intended as a getting started and confidence builder as an in depth how to is a massive undertaking and the detailed information on how to mod FreeSpace is found within the modding section of this wiki with issue specific help and advice available on the Hard Light Productions forum.

==Before We Get Started==

===Your New Best Friends===

By arriving at and closely reading this page you have taken your first steps to making the most important friend every freespace modder has, the modding portal of the freespace wiki. Within the Wiki's pages is a gold mine of information created by the SCP team and community members who have spent a huge amount of time and effort making sure things work and that how they work is well enough documented which is also why there are a few short, sharp "go read the wiki" comments on the forums.

Your next best friends are in your FreeSpace 2\data folder and they are fs2_open.log and fred2_open.log . These two files are the logs generated by the debug builds of FreeSpace 2 and the FRED 2 mission/campaign editor. The way to tell between a regular/retail and debug build is that after the build cycle number in the file name there is a d for debug or r for regular, eg 3.6.12d. any information after this point in the file name is information that tells the support guys exactly which file version you are using. Whenever you are running a debug build of FreeSpace or FRED the program creates a constant record of the programs activity and lists any error messages where possible that occur and stores that record in the listed log files, also debug builds try to catch every error they can while r builds try to ignore them so are an invaluable tool for error checking. To open the logs simply double click on them and if prompted select any text editor, though a word processor might render the log easier to read.

===Required:===

A working and legitimate copy of Freespace 2, FreeSpace Open executables (preferably the latest Stable build or nightly) and a bit of imagination. An internet connection you can readily access helps.

==Getting Started:==

The first thing to know when modifying FreeSpace 2 is to understand how the mod structure works. Each mod needs it's own folder within the FreeSpace 2 folder, for example Wings of Dawn on my computer is C:\Games\Freespace 2\Wings of Dawn . All files that directly relate to the WoD mod are found within this folder on my PC, though a file within the folder tells FreeSpace to go and look for the Media VPs mod, yes Media VPs are a mod, but the Mod structure allows for mods to be chained together in a simple fashion but that will be covered later. Within the mod folders is another folder called data, The data folder is not present in mods relying on .[[VP]] files, which are container files which mimic the mod structure and are used to make distributing and installing mods easier, again I will talk more about .VP files later. Within data are the sub folders which the files that make the mod are stored, the sub folders are there to keep everyone sane and make everything easy to find, the majority are self explanatory but a detailed breakdown can be found in [[FS2_Data_Structure]] but below I have summarized the information important to this tutorial.

''Cache'' - To reduce loading times, the engine will generate a cache file for each model it encounters. Since cache generation can take quite long for more complex models, you should always include cache files for unique mods.

''Cbanims'' - is where command and mission briefing animations are stored

''Effects'' - weapon and other 2d effects

''fonts'' - font files are kept here, unless you are aiming at a total conversion you will in all likelyhood not need this folder

''force feedback'' - unused in any mod that i know

''freddocs'' - the documents that are opened when you hit help in fred so just ignore again unless you are using a custom branch of Freespace engine

''hud'' - custom hud graphics

''intelanims'' - animations used in the techroom for weapons and intel sections

''interface'' - images and animations used in the menu system, note not everything you would expect to be a still is stored as a still so research carefully before changing anything. Again only larger mods and total conversions generally go into this stuff as it is very heavy going to do properly

''maps'' - Texture files for ships and other model based objects

''missions'' - where FRED2 should be storing mission files and the only place where FS2 will look for missions both single player and campaign

''models'' - .pof files go here no matter what purpose

''multidata'' - This is where the game stores player icons and other stuff downloaded during multiplayer sessions

''music'' - in game music files go here

''players'' - the files behind the Pilot screen on startup are stored here, not modding related except in very limited circumstances and is best just ignored unless the support guys tell you to go in there

''sounds'' - sound effects like weapons fire in here

''tables'' - last of the important ones, but the most important one, this is where the tbl and tbm files go that tells the game how to use the majority of the information in the folders listed and also controls a number of other game aspects.

''Voice'' - Voice overs for mission chatter

==Simple Modifications==

One of the simplest things to do is add a new weapon or ship created by the community and the two are often related as with new ships community members might decide they want to create a new weapon for it.

===Adding a ship===

First go to [[SC Lamia]] in [[User-made Ships]] and download it.
Next create a folder in FreeSpace 2 called New Ship and a data folder inside of that.
Then open up sc_lamia.rar if you cant there are a few small programs such as winrar that work with this format. Inside the file are 3 folders called maps, models and tables. The folders listed are identical in name to the folder names used in modifying freespace so copy them into your New Ship\data folder as they are. Congratulations you have just created your first mod. if you look in the maps folder there will be 3 .dds image files which make up the ships texture, in the models folder will contain SCLamia.pof and in tables there are two tbm files, one for the ship and one for a custom weapon for that ship. there is one more thing i want you to do though, open sclamia-shp.tbm in a text editor and find the line starting $flags: . the full line reads ''$Flags: ( "cruiser" )'' now add "in tech database" with the speech marks to the line between the brackets so it reads ''$Flags: ( "cruiser" "in tech database" )'' , save and close the file. Finally open your FreeSpace launcher and select New Ship as the mod and run the game, if you get an error message go back to the file and double check the flags line to the example I provided. When you reach the main screen go to the techroom and at the bottom should be the Shivan cruiser you just added, the ship wont appear in any missions at this time because a mission file needs creating using the ship. FreeSpace is that easy to mod, just drop the assets in the correct folders, making sure any related tables are altered to use it and off you go.

===The mod.ini===

At first glance this is a strange little file that just sits there and defies the convention that everything goes somewhere in the data folder of a mod. Instead this file goes in the main folder for the mod, eg Freespace 2\New Ship for the above example and is a very useful file which adds the final polish to a mod and performs useful tasks like linking into other mods. Like many of the files in Freespace 2 this is basically a renamed txt file and can be opened my any text editor. Let’s take a look at one.

‘# PLEASE NOTE ALL INI SETTINGS ARE *OPTIONAL*

‘# modname: Display name only, so you can have spaces instead of underscores for multi word MOD's

‘# image255x112: Location of a 255x112 bmp you wish to display in the launcher

‘# infotext: Text that will appear in the launcher

‘# website: Link to your website

‘# forum: Link to your forum

[launcher]
'modname = Mod Name

'image255x112 = mod-logo.bmp;

'infotext = Here is a short blurb for the mod

‘#website = here is where a web address goes if your mod has one

‘#forum = http://www.hard-light.net/forums

[multimod]

primarylist = ;

secondarylist = MediaVPs_3612;

This is the contents of the mod.ini for a long term project I am working on with a few amendments.

Anything following a # is a comment and is ignored by any launcher reading it.

The first section is information for the FreeSpace launcher and contains:

* modname, the mod’s name,

* image255x112, the name of a 255x112 pixel bmp to use as a mod image

* infotext, is where you can put a little bit of info about the mod and/or a tag line

* website, activates the website button in the mod selection tab of your launcher and links it to your mod’s website if you have one

* forum, as above but for a forum.

In the example shown both website and forum are commented out but if you remove the # and save they will be read by the launcher.

The next bit links the mod into other ones, the example above will call the 3.6.12 version of the media vps to enhance the visuals of anything in Freespace 2 that is not touched by your mod, for example if you turn the Ravana green, because MediaVPs_3612 is in the secondary line it will not override this but it might do if you place it in primary. Most of the time you will only use secondary list and this is the one you are recommended to use unless you know exactly what you are doing.

***note
If you copy and paste the above example you will need to remove the ‘ from in front of each line it occurs.

===Changing Other Mods===

You have downloaded Blue Planet or some other mod, you played it and you have beaten it but you want to change something, perhaps you feel the anti-fighter turrets are too weak or that there is a different ship you want to use. Do Not Add, Remove Or Change Anything In The Actual Folder this is because you will change the mod as long as the altered files are in there, what you should do is create a mod as explained in Adding a ship and place a mod.ini referencing the folder name for Blue Planet or which ever mod you wish to alter in the secondary mod line. Then place the ship/tbm/whatever into this new mod. Once you have done all of that select the new mod folder in the Freespace launcher’s mod tab and run. Because of the reference to blue planet in the mod.ini that and mods referenced by Blue Planet will be loaded but the changes you made will override the original. This way you get to play your twist on the mod whenever you want but you don’t have to delve into the mod folders to play it as originally intended you just play the mod like you did before.

==On VP files==

Because of the ease in damaging data key to a mod or indeed retail IT IS STRONGLY ADVISED THAT .VP FILES ARE NOT EDITED IN ANY WAY!

The significant advantage of a VP file is ease of distribution. in simple terms a VP file is a container used to maintain the file structure between users because all that is required is that they are all placed in the Mod folder. the problem with changing them is that if you edit one and get it wrong the simple fix and in all likely hood the fix you will be told to do is to reinstall fs2/the mod as appropriate because there is no way for mod/FSO support teams to know what you have done to the VP and they have enough on their plate without having to user fix a problem that shouldn't have happened especially as the mod folders feature has been provided as a means achieving the same effect that requires no modifying of VPs.

==tbm vs tbl==

A tbl is the core table file of that type and only one can be loaded into freespace at any one time tbl files provide the structure to the engine and usually require all basic elements to be present to work.
tbm on the other hand is an additional file to the tbl, usually providing additional data to the tbl or overriding it if needed. Until you get to the stage of building mods for more than adding a few ships you will probably only use tbm if available for that table type. tbm also has the advantage that FS2 can handle multiple tbm files of any given type though avoid conflicting entries at all costs.

==Closing Words==

I cannot over state the usefulness of [[Portal:Modding]] and everything within its links, a good 90-95%of what I know about modding was learned in there and the rest was trial and error with a new newbie questions on the forum and IRC channel.

Another thing is that it is as a matter of courtesy to credit people who’s resources you use, you are unlikely to get thrown out of the community for not doing so but it is always nice to have that little nod of thanks.

Also on a side note don’t change the name of the folder for and existing/downloaded mod, many mods reference each other and changing the name for the folder will brake the links in the mod.ini of any mods that tries to use it, which increases the chance that there will be assets missing or you end up using old assets. On top of this when you report the issues cause by changing folder name you will be treated in a colder manner because you have broken the hard work that went into making sure the mod worked correctly in the first place through a deliberate act. Lets face it, how would you react if you got your mod working nicely and someone comes to you because the mod doesn’t work because they changed something? And then several people started to complain with the same avoidable problem?

Remember the most important thing when modding a game, FreeSpace or any other like any hobby is to have fun. Also it can be surprising how fun trial, error and figuring things out for yourself can be.

Good luck and if you really do get stuck dont be afraid to ask questions.

[[Category:Tutorials|General Mod Creation]]

Ships and General Mod Creation

2011-05-05T17:54:13Z

Headdie: added section 3.3 and a mention about not changing mod folder names in the closing words

Thanks to the work of the [[Source Code Project]] (SCP) team modifying FreeSpace 2 is now very easy, though understanding everything by yourself is extremely difficult with to date only one major modification released that could be called a solo project (see [[WoD]]). Your best bet to start Modifying is to focus on one area, at least to begin with, then once you have a grasp of how things work or you decide you are no longer interested in it and you feel like other areas interest you can start looking at them. Modifying any game calls on a wade array of talents from general creative writing to table editing, model making and the ever in demand skills of texture artists. This page is intended as a getting started and confidence builder as an in depth how to is a massive undertaking and the detailed information on how to mod FreeSpace is found within the modding section of this wiki with issue specific help and advice available on the Hard Light Productions forum.

==Before We Get Started==

===Your New Best Friends===

By arriving at and closely reading this page you have taken your first steps to making the most important friend every freespace modder has, the modding portal of the freespace wiki. Within the Wiki's pages is a gold mine of information created by the SCP team and community members who have spent a huge amount of time and effort making sure things work and that how they work is well enough documented which is also why there are a few short, sharp "go read the wiki" comments on the forums.

Your next best friends are in your FreeSpace 2\data folder and they are fs2_open.log and fred2_open.log . These two files are the logs generated by the debug builds of FreeSpace 2 and the FRED 2 mission/campaign editor. The way to tell between a regular/retail and debug build is that after the build cycle number in the file name there is a d for debug or r for regular, eg 3.6.12d. any information after this point in the file name is information that tells the support guys exactly which file version you are using. Whenever you are running a debug build of FreeSpace or FRED the program creates a constant record of the programs activity and lists any error messages where possible that occur and stores that record in the listed log files, also debug builds try to catch every error they can while r builds try to ignore them so are an invaluable tool for error checking. To open the logs simply double click on them and if prompted select any text editor, though a word processor might render the log easier to read.

===Required:===

A working and legitimate copy of Freespace 2, FreeSpace Open executables (preferably the latest Stable build or nightly) and a bit of imagination. An internet connection you can readily access helps.

==Getting Started:==

The first thing to know when modifying FreeSpace 2 is to understand how the mod structure works. Each mod needs it's own folder within the FreeSpace 2 folder, for example Wings of Dawn on my computer is C:\Games\Freespace 2\Wings of Dawn . All files that directly relate to the WoD mod are found within this folder on my PC, though a file within the folder tells FreeSpace to go and look for the Media VPs mod, yes Media VPs are a mod, but the Mod structure allows for mods to be chained together in a simple fashion but that will be covered later. Within the mod folders is another folder called data, The data folder is not present in mods relying on .[[VP]] files, which are container files which mimic the mod structure and are used to make distributing and installing mods easier, again I will talk more about .VP files later. Within data are the sub folders which the files that make the mod are stored, the sub folders are there to keep everyone sane and make everything easy to find, the majority are self explanatory but a detailed breakdown can be found in [[FS2_Data_Structure]] but below I have summarized the information important to this tutorial.

''Cache'' - To reduce loading times, the engine will generate a cache file for each model it encounters. Since cache generation can take quite long for more complex models, you should always include cache files for unique mods.

''Cbanims'' - is where command and mission briefing animations are stored

''Effects'' - weapon and other 2d effects

''fonts'' - font files are kept here, unless you are aiming at a total conversion you will in all likelyhood not need this folder

''force feedback'' - unused in any mod that i know

''freddocs'' - the documents that are opened when you hit help in fred so just ignore again unless you are using a custom branch of Freespace engine

''hud'' - custom hud graphics

''intelanims'' - animations used in the techroom for weapons and intel sections

''interface'' - images and animations used in the menu system, note not everything you would expect to be a still is stored as a still so research carefully before changing anything. Again only larger mods and total conversions generally go into this stuff as it is very heavy going to do properly

''maps'' - Texture files for ships and other model based objects

''missions'' - where FRED2 should be storing mission files and the only place where FS2 will look for missions both single player and campaign

''models'' - .pof files go here no matter what purpose

''multidata'' - This is where the game stores player icons and other stuff downloaded during multiplayer sessions

''music'' - in game music files go here

''players'' - the files behind the Pilot screen on startup are stored here, not modding related except in very limited circumstances and is best just ignored unless the support guys tell you to go in there

''sounds'' - sound effects like weapons fire in here

''tables'' - last of the important ones, but the most important one, this is where the tbl and tbm files go that tells the game how to use the majority of the information in the folders listed and also controls a number of other game aspects.

''Voice'' - Voice overs for mission chatter

==Simple Modifications==

One of the simplest things to do is add a new weapon or ship created by the community and the two are often related as with new ships community members might decide they want to create a new weapon for it.

===Adding a ship===

First go to [[SC Lamia]] in [[User-made Ships]] and download it.
Next create a folder in FreeSpace 2 called New Ship and a data folder inside of that.
Then open up sc_lamia.rar if you cant there are a few small programs such as winrar that work with this format. Inside the file are 3 folders called maps, models and tables. The folders listed are identical in name to the folder names used in modifying freespace so copy them into your New Ship\data folder as they are. Congratulations you have just created your first mod. if you look in the maps folder there will be 3 .dds image files which make up the ships texture, in the models folder will contain SCLamia.pof and in tables there are two tbm files, one for the ship and one for a custom weapon for that ship. there is one more thing i want you to do though, open sclamia-shp.tbm in a text editor and find the line starting $flags: . the full line reads ''$Flags: ( "cruiser" )'' now add "in tech database" with the speech marks to the line between the brackets so it reads ''$Flags: ( "cruiser" "in tech database" )'' , save and close the file. Finally open your FreeSpace launcher and select New Ship as the mod and run the game, if you get an error message go back to the file and double check the flags line to the example I provided. When you reach the main screen go to the techroom and at the bottom should be the Shivan cruiser you just added, the ship wont appear in any missions at this time because a mission file needs creating using the ship. FreeSpace is that easy to mod, just drop the assets in the correct folders, making sure any related tables are altered to use it and off you go.

===The mod.ini===

At first glance this is a strange little file that just sits there and defies the convention that everything goes somewhere in the data folder of a mod. Instead this file goes in the main folder for the mod, eg Freespace 2\New Ship for the above example and is a very useful file which adds the final polish to a mod and performs useful tasks like linking into other mods. Like many of the files in Freespace 2 this is basically a renamed txt file and can be opened my any text editor. Let’s take a look at one.

‘# PLEASE NOTE ALL INI SETTINGS ARE *OPTIONAL*

‘# modname: Display name only, so you can have spaces instead of underscores for multi word MOD's

‘# image255x112: Location of a 255x112 bmp you wish to display in the launcher

‘# infotext: Text that will appear in the launcher

‘# website: Link to your website

‘# forum: Link to your forum

[launcher]
'modname = Mod Name

'image255x112 = mod-logo.bmp;

'infotext = Here is a short blurb for the mod

‘#website = here is where a web address goes if your mod has one

‘#forum = http://www.hard-light.net/forums

[multimod]

primarylist = ;

secondarylist = MediaVPs_3612;

This is the contents of the mod.ini for a long term project I am working on with a few amendments.

Anything following a # is a comment and is ignored by any launcher reading it.

The first section is information for the FreeSpace launcher and contains:

* modname, the mod’s name,

* image255x112, the name of a 255x112 pixel bmp to use as a mod image

* infotext, is where you can put a little bit of info about the mod and/or a tag line

* website, activates the website button in the mod selection tab of your launcher and links it to your mod’s website if you have one

* forum, as above but for a forum.

In the example shown both website and forum are commented out but if you remove the # and save they will be read by the launcher.

The next bit links the mod into other ones, the example above will call the 3.6.12 version of the media vps to enhance the visuals of anything in Freespace 2 that is not touched by your mod, for example if you turn the Ravana green, because MediaVPs_3612 is in the secondary line it will not override this but it might do if you place it in primary. Most of the time you will only use secondary list and this is the one you are recommended to use unless you know exactly what you are doing.

***note
If you copy and paste the above example you will need to remove the ‘ from in front of each line it occurs.

===Changing Other Mods===

You have downloaded Blue Planet or some other mod, you played it and you have beaten it but you want to change something, perhaps you feel the anti-fighter turrets are too weak or that there is a different ship you want to use. Do Not Add, Remove Or Change Anything In The Actual Folder this is because you will change the mod as long as the altered files are in there, what you should do is create a mod as explained in Adding a ship and place a mod.ini referencing the folder name for Blue Planet or which ever mod you wish to alter in the secondary mod line. Then place the ship/tbm/whatever into this new mod. Once you have done all of that select the new mod folder in the Freespace launcher’s mod tab and run. Because of the reference to blue planet in the mod.ini that and mods referenced by Blue Planet will be loaded but the changes you made will override the original. This way you get to play your twist on the mod whenever you want but you don’t have to delve into the mod folders to play it as originally intended you just play the mod like you did before.

==On VP files==

Because of the ease in damaging data key to a mod or indeed retail IT IS STRONGLY ADVISED THAT .VP FILES ARE NOT EDITED IN ANY WAY!

The significant advantage of a VP file is ease of distribution. in simple terms a VP file is a container used to maintain the file structure between users because all that is required is that they are all placed in the Mod folder. the problem with changing them is that if you edit one and get it wrong the simple fix and in all likely hood the fix you will be told to do is to reinstall fs2/the mod as appropriate because there is no way for mod/FSO support teams to know what you have done to the VP and they have enough on their plate without having to user fix a problem that shouldn't have happened especially as the mod folders feature has been provided as a means achieving the same effect that requires no modifying of VPs.

==tbm vs tbl==

A tbl is the core table file of that type and only one can be loaded into freespace at any one time tbl files provide the structure to the engine and usually require all basic elements to be present to work.
tbm on the other hand is an additional file to the tbl, usually providing additional data to the tbl or overriding it if needed. Until you get to the stage of building mods for more than adding a few ships you will probably only use tbm if available for that table type. tbm also has the advantage that FS2 can handle multiple tbm files of any given type though avoid conflicting entries at all costs.

==Closing Words==

I cannot over state the usefulness of [[Portal:Modding]] and everything within its links, a good 90-95%of what I know about modding was learned in there and the rest was trial and error with a new newbie questions on the forum and IRC channel.

Another thing is that it is as a matter of courtesy to credit people who’s resources you use, you are unlikely to get thrown out of the community for not doing so but it is always nice to have that little nod of thanks.

Also on a side note don’t change the name of the folder for and existing/downloaded mod, many mods reference each other and changing the name for the folder will brake the links in the mod.ini of any mods that tries to use it, which increases the chance that there will be assets missing or you end up using old assets. On top of this when you report the issues cause by changing folder name you will be treated in a colder manner because you have broken the hard work that went into making sure the mod worked correctly in the first place through a deliberate act. Lets face it, how would you react if you got your mod working nicely and someone comes to you because the mod doesn’t work because they changed something? And then several people started to complain with the same avoidable problem?

Remember the most important thing when modding a game, FreeSpace or any other like any hobby is to have fun. Also it can be surprising how fun trial, error and figuring things out for yourself can be.

Good luck and if you really do get stuck dont be afraid to ask questions.

[[Category:Tutorials|General Mod Creation]]

Ships and General Mod Creation

2011-05-05T15:54:16Z

Headdie: Created page with "Thanks to the work of the Source Code Project (SCP) team modifying FreeSpace 2 is now very easy, though understanding everything by yourself is extremely difficult with to da…"

Thanks to the work of the [[Source Code Project]] (SCP) team modifying FreeSpace 2 is now very easy, though understanding everything by yourself is extremely difficult with to date only one major modification released that could be called a solo project (see [[WoD]]). Your best bet to start Modifying is to focus on one area, at least to begin with, then once you have a grasp of how things work or you decide you are no longer interested in it and you feel like other areas interest you can start looking at them. Modifying any game calls on a wade array of talents from general creative writing to table editing, model making and the ever in demand skills of texture artists. This page is intended as a getting started and confidence builder as an in depth how to is a massive undertaking and the detailed information on how to mod FreeSpace is found within the modding section of this wiki with issue specific help and advice available on the Hard Light Productions forum.

==Before We Get Started==

===Your New Best Friends===

By arriving at and closely reading this page you have taken your first steps to making the most important friend every freespace modder has, the modding portal of the freespace wiki. Within the Wiki's pages is a gold mine of information created by the SCP team and community members who have spent a huge amount of time and effort making sure things work and that how they work is well enough documented which is also why there are a few short, sharp "go read the wiki" comments on the forums.

Your next best friends are in your FreeSpace 2\data folder and they are fs2_open.log and fred2_open.log . These two files are the logs generated by the debug builds of FreeSpace 2 and the FRED 2 mission/campaign editor. The way to tell between a regular/retail and debug build is that after the build cycle number in the file name there is a d for debug or r for regular, eg 3.6.12d. any information after this point in the file name is information that tells the support guys exactly which file version you are using. Whenever you are running a debug build of FreeSpace or FRED the program creates a constant record of the programs activity and lists any error messages where possible that occur and stores that record in the listed log files, also debug builds try to catch every error they can while r builds try to ignore them so are an invaluable tool for error checking. To open the logs simply double click on them and if prompted select any text editor, though a word processor might render the log easier to read.

===Required:===

A working and legitimate copy of Freespace 2, FreeSpace Open executables (preferably the latest Stable build or nightly) and a bit of imagination. An internet connection you can readily access helps.

==Getting Started:==

The first thing to know when modifying FreeSpace 2 is to understand how the mod structure works. Each mod needs it's own folder within the FreeSpace 2 folder, for example Wings of Dawn on my computer is C:\Games\Freespace 2\Wings of Dawn . All files that directly relate to the WoD mod are found within this folder on my PC, though a file within the folder tells FreeSpace to go and look for the Media VPs mod, yes Media VPs are a mod, but the Mod structure allows for mods to be chained together in a simple fashion but that will be covered later. Within the mod folders is another folder called data, The data folder is not present in mods relying on .[[VP]] files, which are container files which mimic the mod structure and are used to make distributing and installing mods easier, again I will talk more about .VP files later. Within data are the sub folders which the files that make the mod are stored, the sub folders are there to keep everyone sane and make everything easy to find, the majority are self explanatory but a detailed breakdown can be found in [[FS2_Data_Structure]] but below i have summarized the information important to this tutorial.

''Cache'' - here game stores ship model data that has been compiled by the game into a more readily usable form, except in cases of significant model complexity this is not needed for ship distribution and you can generally ignore the folder

''Cbanims'' - is where command and mission briefing animations are stored

''Effects'' - weapon and other 2d effects

''fonts'' - font files are kept here, unless you are aiming at a total conversion you will in all likely hood not need this folder

''force feedback'' - unused in any mod that i know

''freddocs'' - the documents that are opened when you hit help in fred so just ignore again unless you are using a custom branch of Freespace engine

''hud'' - custom hud guages and graphics

''intelanims'' - animations used in the techroom for weapons and intel sections

''interface'' - images and animations used in the menu system, note not everything you would expect to be a still is stored as a still so research carefully before changing anything. Again only larger mods and total conversions generally go into this stuff as it is very heavy going to do properly

''maps'' - Texture files for ships and other model based objects

''missions'' - where FRED2 should be storing mission files and the only place where FS2 will look for missions both single player and campaign

''models'' - .pof files go here no matter what purpose

''multidata'' - not sure about this, perhaps the guys generally dealing with multiplayer code or the guys balancing BP for

''multiplayer'' can help here, but generally you will not use this folder

''music'' - in game music files go here

''players'' - the files behind the Pilot screen on startup are stored here, not modding related except in very limited circumstances and is best just ignored unless the support guys tell you to go in there

''sounds'' - sound effects like weapons fire in here

''tables'' - last of the important ones, but the most important one, this is where the tbl and tbm files go that tells the game how to use the majority of the information in the folders listed and also controls a number of other game aspects.

''Voice'' - Voice overs for mission chatter

==Simple Modifications==

One of the simplest things to do is add a new weapon or ship created by the community and the two are often related as with new ships community members might decide they want to create a new weapon for it.

===Adding a ship===

First go to [[SC Lamia]] in [[User-made Ships]] and download it.
Next create a folder in FreeSpace 2 called New Ship and a data folder inside of that.
Then open up sc_lamia.rar if you cant there are a few small programs such as winrar that work with this format. Inside the file are 3 folders called maps, models and tables. The folders listed are identical in name to the folder names used in modifying freespace so copy them into your New Ship\data folder as they are. Congratulations you have just created your first mod. if you look in the maps folder there will be 3 .dds image files which make up the ships texture, in the models folder will contain SCLamia.pof and in tables there are two tbm files, one for the ship and one for a custom weapon for that ship. there is one more thing i want you to do though, open sclamia-shp.tbm in a text editor and find the line starting $flags: . the full line reads ''$Flags: ( "cruiser" )'' now add "in tech database" with the speech marks to the line between the brackets so it reads ''$Flags: ( "cruiser" "in tech database" )'' , save and close the file. Finally open your FreeSpace launcher and select New Ship as the mod and run the game, if you get an error message go back to the file and double check the flags line to the example I provided. When you reach the main screen go to the techroom and at the bottom should be the Shivan cruiser you just added, the ship wont appear in any missions at this time because a mission file needs creating using the ship. FreeSpace is that easy to mod, just drop the assets in the correct folders, making sure any related tables are altered to use it and off you go.

===The mod.ini===

At first glance this is a strange little file that just sits there and defies the convention that everything goes somewhere in the data folder of a mod. Instead this file goes in the main folder for the mod, eg Freespace 2\New Ship for the above example and is a very useful file which adds the final polish to a mod and performs useful tasks like linking into other mods. Like many of the files in Freespace 2 this is basically a renamed txt file and can be opened my any text editor. Let’s take a look at one.

‘# PLEASE NOTE ALL INI SETTINGS ARE *OPTIONAL*

‘# modname: Display name only, so you can have spaces instead of underscores for multi word MOD's

‘# image255x112: Location of a 255x112 bmp you wish to display in the launcher

‘# infotext: Text that will appear in the launcher

‘# website: Link to your website

‘# forum: Link to your forum

[launcher]
'modname = Mod Name

'image255x112 = mod-logo.bmp;

'infotext = Here is a short blurb for the mod

‘#website = here is where a web address goes if your mod has one

‘#forum = http://www.hard-light.net/forums

[multimod]

primarylist = ;

secondarylist = MediaVPs_3612;

This is the contents of the mod.ini for a long term project I am working on with a few amendments.

Anything following a # is a comment and is ignored by any launcher reading it.

The first section is information for the FreeSpace launcher and contains:

* modname, the mod’s name,

* image255x112, the name of a 255x112 pixel bmp to use as a mod image

* infotext, is where you can put a little bit of info about the mod and/or a tag line

* website, activates the website button in the mod selection tab of your launcher and links it to your mod’s website if you have one

* forum, as above but for a forum.

In the example shown both website and forum are commented out but if you remove the # and save they will be read by the launcher.

The next bit links the mod into other ones, the example above will call the 3.6.12 version of the media vps to enhance the visuals of anything in Freespace 2 that is not touched by your mod, for example if you turn the Ravana green, because MediaVPs_3612 is in the secondary line it will not override this but it might do if you place it in primary. Most of the time you will only use secondary list and this is the one you are recommended to use unless you know exactly what you are doing.

***note
If you copy and paste the above example you will need to remove the ‘ from in front of each line it occurs.

==On VP files==

Because of the ease in damaging data key to a mod or indeed retail IT IS STRONGLY ADVISED THAT .VP FILES ARE NOT EDITED IN ANY WAY!

The significant advantage of a VP file is ease of distribution. in simple terms a VP file is a container used to maintain the file structure between users because all that is required is that they are all placed in the Mod folder. the problem with changing them is that if you edit one and get it wrong the simple fix and in all likely hood the fix you will be told to do is to reinstall fs2/the mod as appropriate because there is no way for mod/FSO support teams to know what you have done to the VP and they have enough on their plate without having to user fix a problem that shouldn't have happened especially as the mod folders feature has been provided as a means achieving the same effect that requires no modifying of VPs.

==tbm vs tbl==

A tbl is the core table file of that type and only one can be loaded into freespace at any one time tbl files provide the structure to the engine and usually require all basic elements to be present to work.
tbm on the other hand is an additional file to the tbl, usually providing additional data to the tbl or overriding it if needed. Until you get to the stage of building mods for more than adding a few ships you will probably only use tbm if available for that table type. tbm also has the advantage that FS2 can handle multiple tbm files of any given type though avoid conflicting entries at all costs.

==Closing Words==

I cannot over state the usefulness of [[Portal:Modding]] and everything within its links, a good 90-95%of what I know about modding was learned in there and the rest was trial and error with a new newbie questions on the forum and IRC channel.

Another thing is that it is a matter of courtesy to credit people who’s resources you use, you are unlikely to get thrown out of the community for not doing so but it is always nice to have that little nod of thanks.

Remember the most important thing when modding a game, FreeSpace or any other like any hobby is to have fun. Also it can be surprising how fun trial, error and figuring things out for yourself can be.

Good luck and if you really do get stuck dont be afraid to ask questions.

[[Category:Tutorials|General Mod Creation]]

Engine limitations

2011-03-17T15:43:13Z

Headdie: added Category:Modding to help with finding this document

The maximum numbers of certain types of entities that can exist in the FS2_Open engine. Please note that 'Inferno' refers to INF builds, developed to boost engine limits. Starting with FS2_Open 3.6.10 these builds can be used in Multiplayer, older builds are not capable of joining the servers due to several incompatibilities. In addition, Inferno and regular builds are incompatible to each other in Multiplayer; someone using an Inferno build will not be able to play with someone using a regular build and vice versa. Those builds are named after the [[Inferno]] mod, but are extensively used by many other projects, like [[The Babylon Project|TBP]].
Inferno builds will become the standard, starting at FS2_Open revision 3.7, with 3.6.12 being the last version to be distributed both in normal and Inferno variants.

==Tables==
The maximum types of an entity that can exist in the table

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505;"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| [[Ships.tbl|Ship Classes]]
| 130
| 250
|- align="center"
| [[Weapons.tbl|Weapon Classes]]
| 200
| 300
|- align="center"
| Beam Shots
| colspan=2| 5
|- align="center"
| [[Objecttypes.tbl|Object Types]]
| colspan=2| 16
|- align="center"
| [[Iff_defs.tbl|IFFs]]
| colspan=2|10
|- align="center"
| [[Ai_profiles.tbl|AI Profiles]]
| colspan=2| 5
|- align="center"
| [[Cutscenes.tbl|Cutscenes]]
| colspan=2| 10
|- align="center"
| [[Hud_gauges.tbl|Hud Gauges]]
| colspan=2| 64
|- align="center"
| [[Species.tbl|Intelligence Entries]]
| colspan=2| 75
|- align="center"
| Debriefing
| colspan=2| 2,000 Characters per Stage
|}

==Objects==
The maximum number of objects that can exist in a mission at any given time (except for ships and waypoints, which apply to the whole mission).

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Objects
| 1000
|- align="center"
| Ships
| 400
|- align="center"
| Weapons
| 350
|- align="center"
| Beams
| 500
|- align="center"
| Waypoints Per Path
| 20
|- align="center"
| Waypoint Paths
| 32
|}

==Wings==
The maximum number wings or ships in a wing that can exist

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Wings
| 75
|- align="center"
| Ships per Wing
| 6
|- align="center"
| Starting Wings
| 3
|- align="center"
| Squadron Wings
| 5
|- align="center"
| TvT Teams
| 2
|- align="center"
| TvT Wings per Team
| 1
|- align="center"
| TvT Wings
| 2
|}

==Models==
The maximum number of models that can exist at one time

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| rowspan=2 style="background:#351515; width:150px"| '''Name'''
| colspan=2 style="background:#300505;"| '''Limit'''
|- align="center"
| style="background:#300505; width:75px"| '''Standard'''
| style="background:#300505; width:75px"| '''Inferno'''
|- align="center"
| Polygon Models
| 128
| 300
|}

The maximum number of a certain entity that can exist within a model

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Name'''
| style="background:#300505; width:75px"| '''Limit'''
|- align="center"
| Textures
| 64
|- align="center"
| Ship Primary Banks
| 3
|- align="center"
| Ship Secondary Banks
| 4
|}

==Sub-Weapon Types==

The maximums for the sub types of weapons.

{| border=1 cellpadding=4 style="border-collapse: collapse"
|- align="center"
| style="background:#351515; width:150px"| '''Type'''
| style="background:#300505; width:75px"| '''Max Instances'''
|- align="center"
| Corkscrew Missiles
| 64
|- align="center"
| Swarm Missiles
| 100
|}

[[Category:Source Code Project]]
[[Category:Modding]]

GTW UD-8 Kayser

2007-07-25T13:58:59Z

Headdie: /* Veteran Comments */

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

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

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

==Veteran Comments==
''If there is a gun that you want to have when dogfighting, this is that gun. Combining rapid fire with high damage, a well-aimed volley of Kayser fire can convert most fightercraft to small amounts of debris with little difficulty. The downside is high energy requirements, which somewhat reduces the advantage of the rapid firing rate. Make no mistake: if somebody comes at you spraying Kayser pulses, he's not going to do it for long, but you could well be dead before he stops.'' 
''To be perfectly honest, I really prefer the [[GTW Subach HL-7|Subach]] for its efficency and fire rate, and the [[GTW Prometheus S|Prometheus S]] for its power. I take both of them, instead of this.'' 
''Go all out when you're 90% sure of hitting your target. Otherwise fire in short bursts. With this, you have to make every shot count.'' 
''Note on the previous comment, especialy in anything that mounts more than 4 guns''

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

===Statistics - UD-D Kayser===
{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 975 m
|-
| '''Rate of Fire'''
| 3.33 / s
|-
| '''Velocity'''
| 650 mps
|-
| '''Damage'''
| 17
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Excellent
|-
| Against Subsystems
| Average
|}

===Notes===

[[Category:Weapon]]

GTW Morning Star

2007-07-25T13:52:13Z

Headdie: /* Veteran Comments */

The '''GTW ML-70 Morning Star''' is an unusual weapon, described as a long-range tactical weapon. The long-range aspect is undeniable: at 2km, it outranges ever other gun except the Maxim cannon, and even most missiles. Its high projectile speed and blistering rate of fire allow hits even at its maximum range.
 
The most interesting part of the Morning Star however, is its kinetic properties. When a target ship is hit by the weapon, it is shaken slightly; with repeated hits, the target can be driven completely off course and will tumble out of control. This can make them easy prey for a follow-up volley of [[GTM Harpoon]] or [[GTM Tornado]] missiles.
 
It also has other excelllent properties. Given its range and accuracy, as well as its rate of fire, it makes an ideal weapon to intercept bombers and their warheads. The weapon does high shield damage, but minimal hull damage, making it relatively "safe" to fire at outbound torpedoes even if your shots are being backstopped by a friendly target. It also works well as the opening weapon in a dogfight: if you start hitting your target at the weapon's maximum range, their shields should be badly drained by the time you close to range with other guns or missiles and chew up their armor.
 
Because the Morning Star does extremely minimal hull damage, it is not a good choice if your craft has only one weapon mount. Pilots should also be aware that this gun has fairly high energy requirements. If your ship has more than two firing cannons for one its mounts, the Morning Star should be mounted on the mount that has fewer firing points. Its already substantial advantages are not increased by firing more than two at once. In theory the Morning Star and Maxim gun perfectly complement eachother, but in practice the energy demand is simply too high to make this a viable tactic.

{{FS12_Weapons}}
{{shipimage|image=[[Image:Morning_Star_320x240.jpg]]|caption=The GTW ML-70 Morning Star}}

==Tech Room Data==
The GTW ML-70 Morning Star improves upon the performance of the Flail gun, which was developed during the Great War. The original Flail was too expensive to mass produce, because of its limited usage/effectiveness profile. Recent advances in high-temperature optics enable the main focusing chamber of the Morning Star to produce a much more coherent beam, increasing its range and damage levels. This comes at the expense of somewhat higher energy requirements, however.

==Veteran Comments==
''The Morning Star is a totally tactical weapon, unlike the [[GTW Flail]], which had a useful shield-damage value in addition to its knock-around capablities. Use it to push folks around, but beyond that, forget it exists.'' 
''Excellent bomb destroyer, due to the long range, high firing rate, and low energy requirements. It is also a good weapon (if you have good aim) for the mission where you have to fight off the Pegasus fighters, and is also good at knocking around bombers to prevent them from locking onto a ship.'' 

''I've never really favoured this weapon for my own use, however I sometimes find that it increases the effectiveness of AI fighter escorts in bombing missions'' 

''If you mount this thing on turrets, sentry guns, transports, cruisers and freighters, just TRY to get near them after... These things WILL juggle you, and you won't even be able to control yourself.''
 
''tut tut tut, what happened here, i had made a joyfull art form of ragdolling fighters with the flail, so when morning star came up in the campaign brief i was well happy, then i used it, hmmm, no shield damage and harder to keep your target at the end of your stream of fire, what's the point, ok you can cause bombers trouble, but thats about it, the flait was a good combat weapon that had a niche waiting for the promethus and the banshee to come along, FS2 it is just a relic of the first game.''

==Performance==
===Statistics===
{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 2000 m
|-
| '''Rate of Fire'''
| 6.67 / s
|-
| '''Velocity'''
| 1000 mps
|-
| '''Damage'''
| 9
|-
| Against Hullplating
| Poor
|-
| Against Shields
| Excellent
|-
| Against Subsystems
| Minimal
|}

===Statistics - Morning Star D===
{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 2000 m
|-
| '''Rate of Fire'''
| 5.88 / s
|-
| '''Velocity'''
| 1000 mps
|-
| '''Damage'''
| 7
|-
| Against Hullplating
| Average
|-
| Against Shields
| Excellent
|-
| Against Subsystems
| Very Poor
|}

===Notes===

[[Category:Weapon]]

GTW Flail

2007-07-25T13:45:53Z

Headdie: /* Veteran Comments */

'''GTW-32 Flail Rifle'''

{{FS12_Weapons}}
{{shipimage|image=[[Image:Flail_320x240.jpg]]|caption=The GTW-32 Flail Rifle}}

==Tech Room Data==
A rapid-fire, low energy, ceramic optic focused, krypton laser - used in tactical situations to distract or lead an enemy to their destruction at the hands of other allied fighters - this weapon, if used over an extended period of in-flight battle, can destroy an enemy fighter, but, as a destructive weapon, should only be used as a last resort. 
The fast firing rate and high mass of the Flail make it great for changing the velocity vector of an enemy fighter or bomber. It is slightly more effective than the Avenger against shields, rated at damage/second. Its low energy consumption rate makes it useful for prolonged engagements. Note, however, that once you have taken out an enemy's shields, switching to another weapon is advised.

==Veteran Comments==
''FS2 veterans playing FS1 retroactively via the Port have a surprise in store with the Flail. This weapon isn't a mere knock-around gun like the Morningstar. It boasts useful shield and subsystem damage values in addition to its ability to knock an opponent silly. The Flail's high rate of fire also makes it much more useful then most guns when installed in the offset triple-rack of an Ursa bomber. It can still be used against subsystems to good effect, and with all the shots you're putting out, it's much easier to find a way to make an enemy fighter fly through them.'' 
''Great for close-up fighting, it can be a very frustating experience to continually be hit with this cannon. It is possible to paralyze an opponent with the proper angle of fire, and render them near helpless to your missile volleys. With almost as much shield damage as the Banshee, it will peel the shields right off of the target, but it is next to useless on hull plating... so be sure to couple it with another weapon.'' 
''Best anti-lag weapon in FS1: highly recommended for multiplayer.''
 
''Great fun, your targer never gets the chance to hit you, not to mention the amusment you get from rag dolling a fighter. team it up with the Avenger, Banshee or Prometheus to beat your targets hull, found it easyer to use than the morningstar''

==Performance==
===Statistics===
{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 1200 m
|-
| '''Rate of Fire'''
| 6.67 / s
|-
| '''Velocity'''
| 1000 mps
|-
| '''Damage'''
| 12
|-
| Against Hullplating
| Minimal
|-
| Against Shields
| Excellent
|-
| Against Subsystems
| Minimal
|}

===Notes===

[[Category:Weapon]]

GTW Prometheus

2007-07-25T13:39:00Z

Headdie: /* Veteran Comments */

The '''GTW-5 Prometheus''' was a [[primary weapon]] which was developed and used during the [[Great War]]. Its combination of heavy hull damage and wide compatibility made it the weapon of choice of [[GTA]] pilots during the latter parts of the Great War.

Because of the [[Destruction of the SD Lucifer|assault on the SD ''Lucifer'']] in the [[subspace]] tunnel leading from [[Delta Serpentis]] to [[Sol]], all communication from the Terran homeworld was cut off. The substances needed to produce the Prometheus cannon veased to be available and new, retrofitted variants were made. These two cannons were the [[Prometheus R]] (Prometheus Retrofit) and the [[Prometheus S]] (Prometheus Standard).

{{FS12_Weapons}}
{{shipimage|image=[[Image:Prometheus_S_320x240.jpg]]|caption=The GTW-5 Prometheus}}

==Tech Room Data==
Named after the Titan who gave fire to humanity, the Prometheus is a laser-based weapon - an advanced radar and X-ray tracking system lock on the target and determine the target's material structure - argon laser focused via transparent ceramic optics - the laser is generated at the destructive frequency (full out-of-phase) for the target's material structure - emitted no more than .02 ms after targeting and activation by the pilot, the Prometheus stands as one of the GTA's most effective deterrents to enemy attack, an effective form of defense for GTA pilots, and as a durable, portable, and highly destructive offensive tool. 
The Prometheus works best against target hulls. Against shields, it only achieves mediocre performance. It's slow speed and high energy consumption work against it as well. However, the primary advantage of the Prometheus is that it can be equipped on almost any fighter in the GTA.

==Veteran Comments==
''The Prometheus is the best all-around weapon you will be issued in FS1, and remains quite formidible in FS2. A good gun to have, though the power requirements in FS1 can be somewhat daunting on higher difficulties.''
 
''It should be noted that there are considerable differences between the original Prometheus (known in some circles as the Prometheus O) and the Freespace 2 [[GTW Prometheus S]]. There is debate as to which "is better" but they are definitly not the same weapon.''
 
''Never liked it myself, its been a while since i played the origional but it was either the rate of fire or its power drain to damage that never worked for me, much prefered the Banshee, though if not available on the ship i was using then it was a workable alternative''

==Performance==
===Statistics===
{|
|-
| style="width:200px" | '''Range'''
| style="width:200px" | 900 m
|-
| '''Rate of Fire'''
| 3.33 / s
|-
| '''Velocity'''
| 450 mps
|-
| '''Damage'''
| 26
|-
| Against Hullplating
| Excellent
|-
| Against Shields
| Average
|-
| Against Subsystems
| Poor
|}

===Notes===

[[Category:Weapon]]

GTW Banshee

2007-07-25T13:35:09Z

Headdie: /* Veteran Comments */

'''GTW-7 Banshee'''

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

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

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

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

===Notes===

[[Category:Weapon]]