NEBULOUS: Fleet Command Official Wiki - User contributions [en]

Damage Control

2024-10-22T13:06:58Z

76561198801434526: /* DC Buffing Components */ added dcx

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
Shooting weapons at hostiles is just one part of space combat, and the other part often involves taking shots. Sooner or later, your ship will catch on fire, have a leak, or have its internal components damaged beyond use.
And when that happens, your on-board damage control team will kick in and save your day.

<div style="clear: both"></div>
=== Definition of components ===
Everything on a ship is considered a component by damage control, no matter if it is a thruster, a compartment, a mount, or a module.
When a components receives damage, it will usually lose certain amounts of HP. This section explains the mechanics of component malfunction and repairs.
For detailed information on damage mechanics, see [[Component_Damage |Component Damage]].

==== Inoperable components ====
Most components have a hidden attribute called ''Functioning Threshold'', (aka Functioning Threshold). If a component's HP is reduced below this threshold, it will cease to function, and requires repairs to operate again.

=== Damage Control teams ===
Damaged components can be repaired. However, instead of repairing it back to 100%, your damage control teams can only repair a component to a certain percentage above its lowest condition percentage. This stat is known as the Max Repair stat (also colloquially known as repair cap); for most ships it starts at 10%. eg, if a component is damage down to 50% hp, repair teams on that ship will only be able to bring it back up to 60% hp

There is one an exception to this rule, a component can always be repaired to it's minimum functioning threshold hp + Max Repair, regardless of how much damage they take below the threshold. e.g. a Large Reinforced Drive (1500hp, 50hp minimum functioning) can always be repaired up to 200hp (50 from min function + 150 from 10% max repair), a Reinforced CIC (200hp, 10 minimum function threshold) can always be repaired up to 30hp (10 + 20)

Each component can only be repaired by three teams at once, one team for repairing HP and two teams for repairing debuffs. If there are no debuffs then only the one team will repair HP; and vice versa if there is no more hp to repair then only two teams will repair debuffs

Damage control teams tick once every 0.25 sec, applying the equivalent hp/sec as repair work. This is not modified by the amount of team members, a 1/5 team will repair at the same rate as a 5/5 team

Damage control teams speed in m/s is equal to <math>\text{movespeed}\times 2.5</math>. The stats on the wiki has already performed this conversion.

==== Damage Control priorities ====
Every ship has a damage control dispatcher that assigns DC teams to repair jobs and manages repair priorities.

<div style="float: right; margin-left: 20px; padding: 10px; border-style: solid; background-color:lightgray; width: 350px;">
DC dispatcher example list

Given a ship that has: 
- damaged drive (Critical prio) with atmo leak, fire, overload 
- damaged cic (high prio) 
- damaged magazine (med prio) with ammo cookoff 
- damaged DC locker (low prio) 

the lists will look something like this:

Primary: 
- Drive Overload 
- Drive Atmo leak 
- CIC hp 
- Magazine Ammo cookoff 

Secondary: 
-Drive HP 
-Magazine HP 
-DC locker HP 
</div>

The dispatcher has a primary and secondary repair job list. These lists are filled with repair jobs, which include both damaged components and debuffs (aka critical events) that need repair. Each Component adds their repair jobs to the lists according to the component's DC priority stat (normally a hidden stat), in the event of ties, components higher in the component list are prioritized and will add their debuffs to the list first.

Within each component, up to two debuffs events are added to the list. Catastrophics are prioritized first and always added to the primary list. Then, regular debuffs are added (up to the two debuff cap), starting from the top of the component's debuffs list as seen in the DC board. These debuffs are added to the primary list if the component is still alive, and added to the secondary list if destroyed (unless the component is manually prioritized). Then, the component adds its HP repair to the secondary list. If the component has no debuffs and has medium or higher DC priority, it instead adds its HP repair to the primary list

Using these lists, the DC team then assigns teams to the repair jobs in the list, satisfying all jobs in the primary list before filling secondary jobs

Damage control teams from DC lockers higher in the component list are tasked to jobs first. eg, DC teams from compartment 1's locker will be assigned to tasks before DC teams from compartment 2's locker, regardless of difference in team move speed, repair speed, or distance to damaged component. The only exception to this rule is if there is already a DC team in that component; it will be tasked to work on repairs immediately. However, this will not be performed for repair jobs in the secondary list, those jobs will summon another DC team even if there is an idle DC team in the same component.


==== Repair team casualties ====
Damage control teams themselves will only take losses if their current component is below 50% hp.
DC teams currently do not replenish, even if there is spare crew available
''see: [[Crew]]''

=== Restore ===
When a component loses all of its health, it becomes ''Destroyed''. In this state, the component can no longer be hit by any further damage (and is therefore treated as empty space by attacks), nor will it be automatically repaired by the control team. To bring it back online, you need to spend the ''Restores'' provided in DC Lockers. By Shift+LClicking a destroyed component, you can order a damage control team to preform a restore on the destroyed component. After the restore progress is completed, the component is instantly repaired to its minimum functioning HP plus its max repair. Restores require 50 "hp" worth of work to apply.

Restore usage seems to be distributed among the lockers, starting from the closest locker and working outward

== Ship Status Board ==
On the top left of the game screen, every ship has a ship status board that shows the ship's information. At the bottom right of the board, ship damage control status would be displayed.
;Fire Icon
: If there are at least one fire on board, a fire icon would light up. Hovering the mouse over the icon displays the total fire count on board.
;Active Debuffs
: If there are at least one active debuff on board, a orange number would show up on ship status board. Hovering over the number would display where and what are the debuffs on board.
;Destroyed components
: If there is at least one destroyed component, a red number will show up on ship status board. Hovering over the number would display what components are destroyed.
;Catastrophic Event
: If there is a catastrophic event on board, a red exclamation icon and a timer counting down would be displayed to the right of the corresponding ship's status board. If there is more than 1 event on board, only the shortest timer would be displayed. If the count down reaches zero, usually a big bang would take place.

== Debuffs/Catastrophic Events ==

Components can suffer various types of Critical Events (aka debuffs) in game, some would slow down the work speed of your damage control team, while others may degrade your ship's performance, or even obliterate your ship entirely.

Damage has a chance of causing debuffs on components. This chance is calculated by <math>\exp\left( -3Hp-0.5\right)\times C</math> where <math>Hp</math> is the current Hp percentage as a decimal and <math>C</math> is the critical event multiplier of the damage. This means baseline debuff chance for damage with 1x critical event multiplier starts at &sim;3% and increases to &sim;60% as the component takes damage.

This crit then has a chance of being a catastrophic based on the component's Catastrophic event probability.

The time to repair a debuff is determined by the repair speed of the DC team and the repair work required

=== Debuffs list ===
{| class="wikitable sortable"
|+ Debuffs effects list
|-
! In game name !! Internal name !! Stat Affected !! Modifier !! RepairWork
|-
| Atmosphere Leak || Atmosphere Leak || component-workspeed || -50% || 10
|-
| Fire || Fire || component-workspeed || -20% || 10
|-
| Fuel Line Fire || Fuel Line Fire || component-workspeed || -20% || 40
|-
| Magazine Cookoff || Magazine Cookoff || component-workspeed || -20% || 30
|-
| Reactor Overload || Reactor Overload || powerplant-prodefficiency || +25% || 65
|-
| Main Bus Short || Main Bus Short || powerplant-prodefficiency || -50% || 30
|-
| Cell Cookoff || Cell Launcher Cookoff || component-workspeed || -20% || 30
|-
| Container Bank Cookoff || Container Bank Cookoff || component-workspeed || -20% || 60
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || discreteweapon-reload, discreteweapon-recycle || +75%, +75% || 10
|-
| FC Waveguide Bent || FC Waveguide Bent || sensor-power || -50% || 10
|-
| Gyroscope Drift || Gyro Drift || muzzle-accuracy (spread) || +75% || 10
|-
| Heatsink Ruptured || Heatsink Ruptured || continuousweapon-cooldown, continuousweapon-overheatdamageprob|| +75%, +90% || 15
|-
| Antenna Bent || Sensor Antenna Bent || sensor-gain || -50% || 10
|-
| Antenna Bent || Sensor Oscillator Drift || sensor-maxposerror, sensor-maxvelerror || +100%, +100% || 10
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| turret-traverse, turret-elevate (rotation speed) || -80%, -80%|| 20
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| continuousweapon-directdamagemultiplier || -66% || 15
|}

* component-workspeed affects the repair speed of the DC teams inside the component; penalty cannot reduce workspeed below 33%
* There are two types of Antenna Bent, and while they have different internal names, in-game there's no way to tell which type of debuff is in effect.

{| class="wikitable sortable"
|+ Casualty class determines the voicelines that play when the debuff is incurred
|-
! In game name !! Internal name !! Affected class !! Required Condition !! Casualty class !! On-hitOnly !! Rare (catastrophic)
|-
| Atmosphere Leak || Atmosphere Leak || CrewedComponent || none || Decompression || TRUE || FALSE
|-
| Fire || Fire || HullComponent || none || Fire || FALSE || FALSE
|-
| Fuel Line Fire || Fuel Line Fire || DriveComponent || none || Fire || TRUE || TRUE
|-
| Magazine Cookoff || Magazine Cookoff || BulkMagazineComponent<ref>BulkMagazineComponents include all types of magazines, including reinforced and citadel magazines.</ref> || ContainsAnyAmmo || Fire || TRUE || TRUE
|-
| Reactor Overload || Reactor Overload || PowerplantComponent || none || Engineering || FALSE || TRUE
|-
| Main Bus Short || Main Bus Short || PowerplantComponent || none || Engineering || FALSE || FALSE
|-
| Cell Cookoff || Cell Launcher Cookoff || BaseCellLauncherComponent || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Container Bank Cookoff || Container Bank Cookoff || Container Bank<ref>Container bank cookoffs do not have an explicit affected class, but container banks have container bank cookoffs set as a unique debuff. it is unknown if container bank cookoffs can also suffer regular cell cookoffs or if it's overwritten. Magazine cookoff and cell cookoff can block eachother as they have identical keys, but container cookoff appears to have a different key. Additionally, unique debuffs are only added after the regular debuffs, which means container banks likely has a different key as otherwise the regular cell cookoff would block it.</ref> || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || DiscreteWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| FC Waveguide Bent || FC Waveguide Bent || WeaponComponent || HasIntegratedFC || CombatSystems || FALSE || FALSE
|-
| Gyroscope Drift || Gyro Drift || WeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Heatsink Ruptured || Heatsink Ruptured || ContinuousWeaponComponent || HasCooldown || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Antenna Bent || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Oscillator Drift || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| TurretedDiscreteWeaponComponent, FixedDiscreteWeaponComponent, TurretedContinuousWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| Beams<ref>Similar to container bank cookoffs. Is explicitly defined in both the spinal beam and beam turret.</ref> || none || CombatSystems || FALSE || FALSE
|}

[[File:ComponentClassInheritance.png|alt=Component Class Hierarchy|Component class hierarchy. Child classes inherit the crits of their parents.]]

==== Fire ====
Fires deal damage over time and can spread to different components
Every 30 seconds, fires deal 5% of the component's max HP as damage (ignores DR), with 10% crew vulnerability modifier
Every 45 seconds, fires have a 25% chance to spread to a component within 12.5m

A few other debuffs will also deal damage like fire, but will not spread. This includes Cookoffs and Reactor Overloads

=== Rare Debuffs/Catastrophic Events ===
There are currently 3 types of catastrophic events in game. ''Reactor Overload'', ''Fuel Line Fire'', and ''Magazine Cookoff''.

==== Reactor Overload ====
Reactor Overload is a event that would require immediate intervention of the damage control team to prevent a devastating explosion. If 65 points of repair work is not completed within 120 seconds, the reactor detonates in a gigantic explosion that completely destroys ship, and shreds a significant amount of armor off other nearby ships caught within the 1.5km explosion radius. The explosion also creates very strong radar jamming effect in all directions that is strong enough to break bullseye locks.

Reactor Overload explosions have a blast radius of 1.5km, dealing less damage against ships at the edge of the radius. The explosion shreds 200cm-20cm of armor, and if it fully shreds armor, will deal 1500 - 450 damage spread across the ship. Reactor overloads are guarenteed to hit every munition (missiles, mines, etc) in radius.

The jamming effect has a maximum range of 7.5km, 2500kw, 1dB gain, and lasts for 20 seconds.

===== Emergency reactor shutdown =====
Emergency reactor shutdowns can be initiated by the player to clear reactor overloads. They will stop all power and propulsion on the ship for 60 seconds.

30 seconds into the shutdown, all reactor overloads will be cleared, and any component that had an overload will be destroyed.

Note that shutdown is only effective on overloads, and will not stop fuel fires or cookoffs.

==== Fuel Line Fires ====
Fuel Line fires can appear on drives or reactors. If 40 points of repair work is not completed within 100 seconds, it will cause multiple small purple explosions to erupt across the ship, dealing heavy damage across the ship

it specifically causes 2 to 4 explosions per 5 meters of ship length, rounded up,<ref>More specifically, it looks at how long the ship's bounding radius is, and then multiplies that by a random float between 2-4</ref> eg a sprinter will only suffer 8-16 explosions, but a solomon will suffer 29-58 explosions.

Each explosion appears in a random position inside the hull and deals 200 damage in a 15m radius, shreds armor in a 60m radius. Explosions happen every 0.2-0.5 secs until the amount of explosions are reached.

==== Magazine/Cell Cookoff ====
Magazine/Cell Cookoffs can appear on magazines and VLS cells. If 30 points of repair work is not completed within 80 seconds, it will create a large explosion inside the ship, dealing massive damage to the area around magazine (3000 damage spread among components within 50m, shreds armor in 60m radius)
When a Magazine Cook-off is in progress, you can hear crackling sound effects in the vicinity of the ship.

Container bank cookoffs require 65pts of repair work within 120 seconds instead, and deals 15000 damage spread among components within 75m, and shreds armor within 100m.

== Damage Control Board ==
The Damage Control Board is displayed at the bottom right of the screen, whenever a ship is selected. It shows the ship's silhouette with colored boxes depicting the ships components. The color of the box indicates the component's health: bright green(high health), yellow(medium health), red(low health) and grey(destroyed).<ref>These colors are for the default color settings. Colorblindness settings will change the colors.</ref>

Aside from the ship's abstract, a couple of numbers are shown on the top of DC Board.
=== DMG ===
DMG shows how many components on ship is damaged or destroyed, individual thrusters and integrated antennas are also included.
=== TMS ===
TMS shows how many damage control teams are still operational, and how many are working. For example, for a indication of 1/2, it means 1 of the 2 teams are currently assigned with tasks.
=== RES ===
RES shows how many available restores do you have on ship. DC lockers that are destroyed with restores in them would not contribute to this number. However, it is feasible to spend 1 restore to repair a destroyed [[component:large-dc-locker|Large DC Locker]] with 2 restores in it, to get 1 additional restore back. This is often referred to as ''chain restoring''.
Restore would only be conducted if the player explicitly commanded this operation by Shift+LClicking a destroyed component, this would add a purple dotted outline over the component.

=== Prioritize ===
Player can prioritize the repair of a non-destroyed component by Shift+LClicking it, this is indicated by a blue dotted outline around the component.
=== Filtering ===
When the DC Board is expanded, there is a filter provided at the top left of the board. Player may select/deselect different categories to reduce clutter on the DC Board.

== DC Components ==
There are currently 3 types of DC-related components.

=== DC Lockers ===
Each DC lockers provide you with certain numbers of DC Teams and Restores.

{| class="wikitable"
|-
!rowspan="2"|DC Locker Type !!rowspan="2"|DC Teams !!colspan="4"|Repair Rate !!rowspan="2"|Movement Speed !!rowspan="2"|Restores
|-
! General !! Restore !! Firefighting !! Reactor Overload
|-
| [[component:small-dc-locker|Small DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:reinforced-dc-locker|Reinforced DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:damage-control-complex|Damage Control Complex]] || 3 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 2
|-
| [[component:large-dc-locker|Large DC Locker]] || 3 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 2
|-
| [[component:large-dc-storage|Large DC Storage]] || 1 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 4
|-
| [[component:rapid-dc-locker|Rapid DC Locker]] || 1 || 0.3 || 0 || 0.3 || 0.3 || 1 || 0
|}

=== DC Buffing Components ===

{| class="wikitable"
|-
! Component !! Repair Speed !! Move Speed !! Max Repair
|-
| [[component:small-workshop|Small Workshop]] || 30% || N/A || N/A
|-
| [[component:damage-control-central|Damage Control Central]] || 10% || 50% || N/A
|-
| [[component:damage-control-complex|Damage Control Complex]] || 10% || 30% || 5%
|}

=== Safety Components ===

{| class="wikitable"
|-
| [[component:fire-suppression-system|Fire Suppression System:]] || Catastrophic Event Prob. (Cell launcher): -50%

Catastrophic Event Prob. (Magazine): -50%

Firefighting Speed: +50%
|-
| [[component:redundant-reactor-failsafes| Redundant Reactor Failsafes:]] || Catastrophic Event Prob. (Reactor): -33%

Reactor Overload Repair Speed: +30%
|-
| [[component:reinforced-thruster-nozzles| Reinforced Thruster Nozzles:]] || Flank Damage Probability: -20%
|}

==Notes==
<references />

Damage Control

2024-10-22T13:05:08Z

76561198801434526: /* DC Lockers */ added large DC storage and DCX

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
Shooting weapons at hostiles is just one part of space combat, and the other part often involves taking shots. Sooner or later, your ship will catch on fire, have a leak, or have its internal components damaged beyond use.
And when that happens, your on-board damage control team will kick in and save your day.

<div style="clear: both"></div>
=== Definition of components ===
Everything on a ship is considered a component by damage control, no matter if it is a thruster, a compartment, a mount, or a module.
When a components receives damage, it will usually lose certain amounts of HP. This section explains the mechanics of component malfunction and repairs.
For detailed information on damage mechanics, see [[Component_Damage |Component Damage]].

==== Inoperable components ====
Most components have a hidden attribute called ''Functioning Threshold'', (aka Functioning Threshold). If a component's HP is reduced below this threshold, it will cease to function, and requires repairs to operate again.

=== Damage Control teams ===
Damaged components can be repaired. However, instead of repairing it back to 100%, your damage control teams can only repair a component to a certain percentage above its lowest condition percentage. This stat is known as the Max Repair stat (also colloquially known as repair cap); for most ships it starts at 10%. eg, if a component is damage down to 50% hp, repair teams on that ship will only be able to bring it back up to 60% hp

There is one an exception to this rule, a component can always be repaired to it's minimum functioning threshold hp + Max Repair, regardless of how much damage they take below the threshold. e.g. a Large Reinforced Drive (1500hp, 50hp minimum functioning) can always be repaired up to 200hp (50 from min function + 150 from 10% max repair), a Reinforced CIC (200hp, 10 minimum function threshold) can always be repaired up to 30hp (10 + 20)

Each component can only be repaired by three teams at once, one team for repairing HP and two teams for repairing debuffs. If there are no debuffs then only the one team will repair HP; and vice versa if there is no more hp to repair then only two teams will repair debuffs

Damage control teams tick once every 0.25 sec, applying the equivalent hp/sec as repair work. This is not modified by the amount of team members, a 1/5 team will repair at the same rate as a 5/5 team

Damage control teams speed in m/s is equal to <math>\text{movespeed}\times 2.5</math>. The stats on the wiki has already performed this conversion.

==== Damage Control priorities ====
Every ship has a damage control dispatcher that assigns DC teams to repair jobs and manages repair priorities.

<div style="float: right; margin-left: 20px; padding: 10px; border-style: solid; background-color:lightgray; width: 350px;">
DC dispatcher example list

Given a ship that has: 
- damaged drive (Critical prio) with atmo leak, fire, overload 
- damaged cic (high prio) 
- damaged magazine (med prio) with ammo cookoff 
- damaged DC locker (low prio) 

the lists will look something like this:

Primary: 
- Drive Overload 
- Drive Atmo leak 
- CIC hp 
- Magazine Ammo cookoff 

Secondary: 
-Drive HP 
-Magazine HP 
-DC locker HP 
</div>

The dispatcher has a primary and secondary repair job list. These lists are filled with repair jobs, which include both damaged components and debuffs (aka critical events) that need repair. Each Component adds their repair jobs to the lists according to the component's DC priority stat (normally a hidden stat), in the event of ties, components higher in the component list are prioritized and will add their debuffs to the list first.

Within each component, up to two debuffs events are added to the list. Catastrophics are prioritized first and always added to the primary list. Then, regular debuffs are added (up to the two debuff cap), starting from the top of the component's debuffs list as seen in the DC board. These debuffs are added to the primary list if the component is still alive, and added to the secondary list if destroyed (unless the component is manually prioritized). Then, the component adds its HP repair to the secondary list. If the component has no debuffs and has medium or higher DC priority, it instead adds its HP repair to the primary list

Using these lists, the DC team then assigns teams to the repair jobs in the list, satisfying all jobs in the primary list before filling secondary jobs

Damage control teams from DC lockers higher in the component list are tasked to jobs first. eg, DC teams from compartment 1's locker will be assigned to tasks before DC teams from compartment 2's locker, regardless of difference in team move speed, repair speed, or distance to damaged component. The only exception to this rule is if there is already a DC team in that component; it will be tasked to work on repairs immediately. However, this will not be performed for repair jobs in the secondary list, those jobs will summon another DC team even if there is an idle DC team in the same component.


==== Repair team casualties ====
Damage control teams themselves will only take losses if their current component is below 50% hp.
DC teams currently do not replenish, even if there is spare crew available
''see: [[Crew]]''

=== Restore ===
When a component loses all of its health, it becomes ''Destroyed''. In this state, the component can no longer be hit by any further damage (and is therefore treated as empty space by attacks), nor will it be automatically repaired by the control team. To bring it back online, you need to spend the ''Restores'' provided in DC Lockers. By Shift+LClicking a destroyed component, you can order a damage control team to preform a restore on the destroyed component. After the restore progress is completed, the component is instantly repaired to its minimum functioning HP plus its max repair. Restores require 50 "hp" worth of work to apply.

Restore usage seems to be distributed among the lockers, starting from the closest locker and working outward

== Ship Status Board ==
On the top left of the game screen, every ship has a ship status board that shows the ship's information. At the bottom right of the board, ship damage control status would be displayed.
;Fire Icon
: If there are at least one fire on board, a fire icon would light up. Hovering the mouse over the icon displays the total fire count on board.
;Active Debuffs
: If there are at least one active debuff on board, a orange number would show up on ship status board. Hovering over the number would display where and what are the debuffs on board.
;Destroyed components
: If there is at least one destroyed component, a red number will show up on ship status board. Hovering over the number would display what components are destroyed.
;Catastrophic Event
: If there is a catastrophic event on board, a red exclamation icon and a timer counting down would be displayed to the right of the corresponding ship's status board. If there is more than 1 event on board, only the shortest timer would be displayed. If the count down reaches zero, usually a big bang would take place.

== Debuffs/Catastrophic Events ==

Components can suffer various types of Critical Events (aka debuffs) in game, some would slow down the work speed of your damage control team, while others may degrade your ship's performance, or even obliterate your ship entirely.

Damage has a chance of causing debuffs on components. This chance is calculated by <math>\exp\left( -3Hp-0.5\right)\times C</math> where <math>Hp</math> is the current Hp percentage as a decimal and <math>C</math> is the critical event multiplier of the damage. This means baseline debuff chance for damage with 1x critical event multiplier starts at &sim;3% and increases to &sim;60% as the component takes damage.

This crit then has a chance of being a catastrophic based on the component's Catastrophic event probability.

The time to repair a debuff is determined by the repair speed of the DC team and the repair work required

=== Debuffs list ===
{| class="wikitable sortable"
|+ Debuffs effects list
|-
! In game name !! Internal name !! Stat Affected !! Modifier !! RepairWork
|-
| Atmosphere Leak || Atmosphere Leak || component-workspeed || -50% || 10
|-
| Fire || Fire || component-workspeed || -20% || 10
|-
| Fuel Line Fire || Fuel Line Fire || component-workspeed || -20% || 40
|-
| Magazine Cookoff || Magazine Cookoff || component-workspeed || -20% || 30
|-
| Reactor Overload || Reactor Overload || powerplant-prodefficiency || +25% || 65
|-
| Main Bus Short || Main Bus Short || powerplant-prodefficiency || -50% || 30
|-
| Cell Cookoff || Cell Launcher Cookoff || component-workspeed || -20% || 30
|-
| Container Bank Cookoff || Container Bank Cookoff || component-workspeed || -20% || 60
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || discreteweapon-reload, discreteweapon-recycle || +75%, +75% || 10
|-
| FC Waveguide Bent || FC Waveguide Bent || sensor-power || -50% || 10
|-
| Gyroscope Drift || Gyro Drift || muzzle-accuracy (spread) || +75% || 10
|-
| Heatsink Ruptured || Heatsink Ruptured || continuousweapon-cooldown, continuousweapon-overheatdamageprob|| +75%, +90% || 15
|-
| Antenna Bent || Sensor Antenna Bent || sensor-gain || -50% || 10
|-
| Antenna Bent || Sensor Oscillator Drift || sensor-maxposerror, sensor-maxvelerror || +100%, +100% || 10
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| turret-traverse, turret-elevate (rotation speed) || -80%, -80%|| 20
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| continuousweapon-directdamagemultiplier || -66% || 15
|}

* component-workspeed affects the repair speed of the DC teams inside the component; penalty cannot reduce workspeed below 33%
* There are two types of Antenna Bent, and while they have different internal names, in-game there's no way to tell which type of debuff is in effect.

{| class="wikitable sortable"
|+ Casualty class determines the voicelines that play when the debuff is incurred
|-
! In game name !! Internal name !! Affected class !! Required Condition !! Casualty class !! On-hitOnly !! Rare (catastrophic)
|-
| Atmosphere Leak || Atmosphere Leak || CrewedComponent || none || Decompression || TRUE || FALSE
|-
| Fire || Fire || HullComponent || none || Fire || FALSE || FALSE
|-
| Fuel Line Fire || Fuel Line Fire || DriveComponent || none || Fire || TRUE || TRUE
|-
| Magazine Cookoff || Magazine Cookoff || BulkMagazineComponent<ref>BulkMagazineComponents include all types of magazines, including reinforced and citadel magazines.</ref> || ContainsAnyAmmo || Fire || TRUE || TRUE
|-
| Reactor Overload || Reactor Overload || PowerplantComponent || none || Engineering || FALSE || TRUE
|-
| Main Bus Short || Main Bus Short || PowerplantComponent || none || Engineering || FALSE || FALSE
|-
| Cell Cookoff || Cell Launcher Cookoff || BaseCellLauncherComponent || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Container Bank Cookoff || Container Bank Cookoff || Container Bank<ref>Container bank cookoffs do not have an explicit affected class, but container banks have container bank cookoffs set as a unique debuff. it is unknown if container bank cookoffs can also suffer regular cell cookoffs or if it's overwritten. Magazine cookoff and cell cookoff can block eachother as they have identical keys, but container cookoff appears to have a different key. Additionally, unique debuffs are only added after the regular debuffs, which means container banks likely has a different key as otherwise the regular cell cookoff would block it.</ref> || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || DiscreteWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| FC Waveguide Bent || FC Waveguide Bent || WeaponComponent || HasIntegratedFC || CombatSystems || FALSE || FALSE
|-
| Gyroscope Drift || Gyro Drift || WeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Heatsink Ruptured || Heatsink Ruptured || ContinuousWeaponComponent || HasCooldown || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Antenna Bent || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Oscillator Drift || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| TurretedDiscreteWeaponComponent, FixedDiscreteWeaponComponent, TurretedContinuousWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| Beams<ref>Similar to container bank cookoffs. Is explicitly defined in both the spinal beam and beam turret.</ref> || none || CombatSystems || FALSE || FALSE
|}

[[File:ComponentClassInheritance.png|alt=Component Class Hierarchy|Component class hierarchy. Child classes inherit the crits of their parents.]]

==== Fire ====
Fires deal damage over time and can spread to different components
Every 30 seconds, fires deal 5% of the component's max HP as damage (ignores DR), with 10% crew vulnerability modifier
Every 45 seconds, fires have a 25% chance to spread to a component within 12.5m

A few other debuffs will also deal damage like fire, but will not spread. This includes Cookoffs and Reactor Overloads

=== Rare Debuffs/Catastrophic Events ===
There are currently 3 types of catastrophic events in game. ''Reactor Overload'', ''Fuel Line Fire'', and ''Magazine Cookoff''.

==== Reactor Overload ====
Reactor Overload is a event that would require immediate intervention of the damage control team to prevent a devastating explosion. If 65 points of repair work is not completed within 120 seconds, the reactor detonates in a gigantic explosion that completely destroys ship, and shreds a significant amount of armor off other nearby ships caught within the 1.5km explosion radius. The explosion also creates very strong radar jamming effect in all directions that is strong enough to break bullseye locks.

Reactor Overload explosions have a blast radius of 1.5km, dealing less damage against ships at the edge of the radius. The explosion shreds 200cm-20cm of armor, and if it fully shreds armor, will deal 1500 - 450 damage spread across the ship. Reactor overloads are guarenteed to hit every munition (missiles, mines, etc) in radius.

The jamming effect has a maximum range of 7.5km, 2500kw, 1dB gain, and lasts for 20 seconds.

===== Emergency reactor shutdown =====
Emergency reactor shutdowns can be initiated by the player to clear reactor overloads. They will stop all power and propulsion on the ship for 60 seconds.

30 seconds into the shutdown, all reactor overloads will be cleared, and any component that had an overload will be destroyed.

Note that shutdown is only effective on overloads, and will not stop fuel fires or cookoffs.

==== Fuel Line Fires ====
Fuel Line fires can appear on drives or reactors. If 40 points of repair work is not completed within 100 seconds, it will cause multiple small purple explosions to erupt across the ship, dealing heavy damage across the ship

it specifically causes 2 to 4 explosions per 5 meters of ship length, rounded up,<ref>More specifically, it looks at how long the ship's bounding radius is, and then multiplies that by a random float between 2-4</ref> eg a sprinter will only suffer 8-16 explosions, but a solomon will suffer 29-58 explosions.

Each explosion appears in a random position inside the hull and deals 200 damage in a 15m radius, shreds armor in a 60m radius. Explosions happen every 0.2-0.5 secs until the amount of explosions are reached.

==== Magazine/Cell Cookoff ====
Magazine/Cell Cookoffs can appear on magazines and VLS cells. If 30 points of repair work is not completed within 80 seconds, it will create a large explosion inside the ship, dealing massive damage to the area around magazine (3000 damage spread among components within 50m, shreds armor in 60m radius)
When a Magazine Cook-off is in progress, you can hear crackling sound effects in the vicinity of the ship.

Container bank cookoffs require 65pts of repair work within 120 seconds instead, and deals 15000 damage spread among components within 75m, and shreds armor within 100m.

== Damage Control Board ==
The Damage Control Board is displayed at the bottom right of the screen, whenever a ship is selected. It shows the ship's silhouette with colored boxes depicting the ships components. The color of the box indicates the component's health: bright green(high health), yellow(medium health), red(low health) and grey(destroyed).<ref>These colors are for the default color settings. Colorblindness settings will change the colors.</ref>

Aside from the ship's abstract, a couple of numbers are shown on the top of DC Board.
=== DMG ===
DMG shows how many components on ship is damaged or destroyed, individual thrusters and integrated antennas are also included.
=== TMS ===
TMS shows how many damage control teams are still operational, and how many are working. For example, for a indication of 1/2, it means 1 of the 2 teams are currently assigned with tasks.
=== RES ===
RES shows how many available restores do you have on ship. DC lockers that are destroyed with restores in them would not contribute to this number. However, it is feasible to spend 1 restore to repair a destroyed [[component:large-dc-locker|Large DC Locker]] with 2 restores in it, to get 1 additional restore back. This is often referred to as ''chain restoring''.
Restore would only be conducted if the player explicitly commanded this operation by Shift+LClicking a destroyed component, this would add a purple dotted outline over the component.

=== Prioritize ===
Player can prioritize the repair of a non-destroyed component by Shift+LClicking it, this is indicated by a blue dotted outline around the component.
=== Filtering ===
When the DC Board is expanded, there is a filter provided at the top left of the board. Player may select/deselect different categories to reduce clutter on the DC Board.

== DC Components ==
There are currently 3 types of DC-related components.

=== DC Lockers ===
Each DC lockers provide you with certain numbers of DC Teams and Restores.

{| class="wikitable"
|-
!rowspan="2"|DC Locker Type !!rowspan="2"|DC Teams !!colspan="4"|Repair Rate !!rowspan="2"|Movement Speed !!rowspan="2"|Restores
|-
! General !! Restore !! Firefighting !! Reactor Overload
|-
| [[component:small-dc-locker|Small DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:reinforced-dc-locker|Reinforced DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:damage-control-complex|Damage Control Complex]] || 3 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 2
|-
| [[component:large-dc-locker|Large DC Locker]] || 3 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 2
|-
| [[component:large-dc-storage|Large DC Storage]] || 1 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 4
|-
| [[component:rapid-dc-locker|Rapid DC Locker]] || 1 || 0.3 || 0 || 0.3 || 0.3 || 1 || 0
|}

=== DC Buffing Components ===

{| class="wikitable"
|-
! Component !! Repair Speed !! Move Speed
|-
| [[component:small-workshop|Small Workshop]] || 30% || N/A
|-
| [[component:damage-control-central|Damage Control Central]] || 10% || 50%
|}

=== Safety Components ===

{| class="wikitable"
|-
| [[component:fire-suppression-system|Fire Suppression System:]] || Catastrophic Event Prob. (Cell launcher): -50%

Catastrophic Event Prob. (Magazine): -50%

Firefighting Speed: +50%
|-
| [[component:redundant-reactor-failsafes| Redundant Reactor Failsafes:]] || Catastrophic Event Prob. (Reactor): -33%

Reactor Overload Repair Speed: +30%
|-
| [[component:reinforced-thruster-nozzles| Reinforced Thruster Nozzles:]] || Flank Damage Probability: -20%
|}

==Notes==
<references />

Crew

2024-10-22T12:57:16Z

76561198801434526: /* Mechanics */ commented-out manning components section

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
 
 
 
Crew are used to man the different components on your ships. At the moment ships are automatically filled with all the crew they need and there are no components that solely provide crew.

<div style="clear: both"></div>
== Mechanics ==

=== Crew Status ===
During battle, fighting can start to wear down the nerves of the crew. Your crew is under a certain amount of '''pressure''', rated from 0 to 3000, based on the events going on around them and the amount of damage being sustained. The amount of pressure determines what state the crew is in, which affects the voice lines you receive when commanding the ship. Currently, crew status does not impact the performance of any components. The status levels are:
{| class="wikitable"
|+ Pressure thresholds for crew status.
|-
! Pressure !! Status
|-
| <150 || Calm
|-
| <1000 || Heightened
|-
| <2500 || Rattled
|-
| ≥2500 || Panicked
|}

The following events change the pressure of your crew:
{| class="wikitable"
|+ Pressure changes due to events.
|-
! Event !! Pressure Change
|-
| Shots on armor that do not penetrate || +5
|-
| Penetrating shots || +0.5 × total damage
|-
| Component destroyed || +200
|-
| (applied per second) || -8
|}

Although pressure drops by 8 per second, it cannot fall below another variable called '''static pressure''' (SP). SP represents tension that prevents the crew from totally being at ease due to the danger of the situation. Every time a crew member is killed, a part changes its destroyed status (destroyed or repaired), or a part changes its functioning status, the SP is recalculated by this formula:

<math>\text{SP} = (1000 \times \text{fraction of components not functional}) + (25 \times \text{number of active debuffs}) - (500 \times \text{fraction of crew still alive})</math>

=== Crew Damage ===

Crew inside components can be damaged when the component is damaged.

When the component is below 50% health after being damaged, the crew has a chance to be damaged based on the hull's vulnerability stat and the attack's crew damage multiplier. e.g. a ship with 40% crew vulnerability would normally have a 40% chance, but a shell with a 0.75 or -25% crew vulnerability multiplier reduces that to 30%, reducing that shell's capability to damage crew. Conversely, a shell with 1.50 or +50% crew vulnerability multiplier increases that to 60%, boosting the shell's capability to damage crew.

If the chance succeeds, the amount of crew is reduced by <math>\frac{D}{12\times \text{MaxHp}}</math> where D is the incoming damage on that component and MaxHp is the maximum hp of the component they are in. This has a 50% chance to round up or round down.

=== Abandoning Ship ===

Ships are automatically abandoned when all CICs (including Auxiliary Steering) or all powerplants (drives, reactors), are disabled and there are no DC teams; or all CICs or powerplants are destroyed, and there are no restores. While ammunition cook-offs and fuel line fires often deal enough damage to cause an evacuation, it is not guaranteed. Evacuation can also be preformed manually, by holding the evacuation button in the DC screen for 3 seconds. Abandoning ship makes the ship uncontrollable and spawns escape pods.

Externally, escape pods can be seen embedded in the hulls under normal conditions. When evacuating, the escape pods spawn at these points and move towards the withdrawal zone at around 30 m/s. The radar marking for an escape pod appears as a circle with an x inside (&otimes;). Escape pods can be targeted and shot by anti-ship weapons, and doing so will result in the crew protesting the order.

The max amount of escape pods launched from each hull are shown below:
{| class="wikitable"
|+ Maximum escape pods for each of the hulls.
|-
!colspan="2"|ANS !!colspan="2"|OSP
|-
! Hull !! Escape Pods !! Hull !! Escape Pods
|-
| Sprinter || 2 || Ferryman || 4
|-
| Raines || 4 || Draugr || 4
|-
| Keystone || 4 || Flathead || 2
|-
| Vauxhall || 10 || Ocello || 12
|-
| Axford || 11 || Marauder || &sim;8
|-
| Solomon || 22 || Moorline || &sim;8
|}

Damage Control

2024-10-22T12:54:13Z

76561198801434526: /* Safety Components */ fixed line breaks in table

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
Shooting weapons at hostiles is just one part of space combat, and the other part often involves taking shots. Sooner or later, your ship will catch on fire, have a leak, or have its internal components damaged beyond use.
And when that happens, your on-board damage control team will kick in and save your day.

<div style="clear: both"></div>
=== Definition of components ===
Everything on a ship is considered a component by damage control, no matter if it is a thruster, a compartment, a mount, or a module.
When a components receives damage, it will usually lose certain amounts of HP. This section explains the mechanics of component malfunction and repairs.
For detailed information on damage mechanics, see [[Component_Damage |Component Damage]].

==== Inoperable components ====
Most components have a hidden attribute called ''Functioning Threshold'', (aka Functioning Threshold). If a component's HP is reduced below this threshold, it will cease to function, and requires repairs to operate again.

=== Damage Control teams ===
Damaged components can be repaired. However, instead of repairing it back to 100%, your damage control teams can only repair a component to a certain percentage above its lowest condition percentage. This stat is known as the Max Repair stat (also colloquially known as repair cap); for most ships it starts at 10%. eg, if a component is damage down to 50% hp, repair teams on that ship will only be able to bring it back up to 60% hp

There is one an exception to this rule, a component can always be repaired to it's minimum functioning threshold hp + Max Repair, regardless of how much damage they take below the threshold. e.g. a Large Reinforced Drive (1500hp, 50hp minimum functioning) can always be repaired up to 200hp (50 from min function + 150 from 10% max repair), a Reinforced CIC (200hp, 10 minimum function threshold) can always be repaired up to 30hp (10 + 20)

Each component can only be repaired by three teams at once, one team for repairing HP and two teams for repairing debuffs. If there are no debuffs then only the one team will repair HP; and vice versa if there is no more hp to repair then only two teams will repair debuffs

Damage control teams tick once every 0.25 sec, applying the equivalent hp/sec as repair work. This is not modified by the amount of team members, a 1/5 team will repair at the same rate as a 5/5 team

Damage control teams speed in m/s is equal to <math>\text{movespeed}\times 2.5</math>. The stats on the wiki has already performed this conversion.

==== Damage Control priorities ====
Every ship has a damage control dispatcher that assigns DC teams to repair jobs and manages repair priorities.

<div style="float: right; margin-left: 20px; padding: 10px; border-style: solid; background-color:lightgray; width: 350px;">
DC dispatcher example list

Given a ship that has: 
- damaged drive (Critical prio) with atmo leak, fire, overload 
- damaged cic (high prio) 
- damaged magazine (med prio) with ammo cookoff 
- damaged DC locker (low prio) 

the lists will look something like this:

Primary: 
- Drive Overload 
- Drive Atmo leak 
- CIC hp 
- Magazine Ammo cookoff 

Secondary: 
-Drive HP 
-Magazine HP 
-DC locker HP 
</div>

The dispatcher has a primary and secondary repair job list. These lists are filled with repair jobs, which include both damaged components and debuffs (aka critical events) that need repair. Each Component adds their repair jobs to the lists according to the component's DC priority stat (normally a hidden stat), in the event of ties, components higher in the component list are prioritized and will add their debuffs to the list first.

Within each component, up to two debuffs events are added to the list. Catastrophics are prioritized first and always added to the primary list. Then, regular debuffs are added (up to the two debuff cap), starting from the top of the component's debuffs list as seen in the DC board. These debuffs are added to the primary list if the component is still alive, and added to the secondary list if destroyed (unless the component is manually prioritized). Then, the component adds its HP repair to the secondary list. If the component has no debuffs and has medium or higher DC priority, it instead adds its HP repair to the primary list

Using these lists, the DC team then assigns teams to the repair jobs in the list, satisfying all jobs in the primary list before filling secondary jobs

Damage control teams from DC lockers higher in the component list are tasked to jobs first. eg, DC teams from compartment 1's locker will be assigned to tasks before DC teams from compartment 2's locker, regardless of difference in team move speed, repair speed, or distance to damaged component. The only exception to this rule is if there is already a DC team in that component; it will be tasked to work on repairs immediately. However, this will not be performed for repair jobs in the secondary list, those jobs will summon another DC team even if there is an idle DC team in the same component.


==== Repair team casualties ====
Damage control teams themselves will only take losses if their current component is below 50% hp.
DC teams currently do not replenish, even if there is spare crew available
''see: [[Crew]]''

=== Restore ===
When a component loses all of its health, it becomes ''Destroyed''. In this state, the component can no longer be hit by any further damage (and is therefore treated as empty space by attacks), nor will it be automatically repaired by the control team. To bring it back online, you need to spend the ''Restores'' provided in DC Lockers. By Shift+LClicking a destroyed component, you can order a damage control team to preform a restore on the destroyed component. After the restore progress is completed, the component is instantly repaired to its minimum functioning HP plus its max repair. Restores require 50 "hp" worth of work to apply.

Restore usage seems to be distributed among the lockers, starting from the closest locker and working outward

== Ship Status Board ==
On the top left of the game screen, every ship has a ship status board that shows the ship's information. At the bottom right of the board, ship damage control status would be displayed.
;Fire Icon
: If there are at least one fire on board, a fire icon would light up. Hovering the mouse over the icon displays the total fire count on board.
;Active Debuffs
: If there are at least one active debuff on board, a orange number would show up on ship status board. Hovering over the number would display where and what are the debuffs on board.
;Destroyed components
: If there is at least one destroyed component, a red number will show up on ship status board. Hovering over the number would display what components are destroyed.
;Catastrophic Event
: If there is a catastrophic event on board, a red exclamation icon and a timer counting down would be displayed to the right of the corresponding ship's status board. If there is more than 1 event on board, only the shortest timer would be displayed. If the count down reaches zero, usually a big bang would take place.

== Debuffs/Catastrophic Events ==

Components can suffer various types of Critical Events (aka debuffs) in game, some would slow down the work speed of your damage control team, while others may degrade your ship's performance, or even obliterate your ship entirely.

Damage has a chance of causing debuffs on components. This chance is calculated by <math>\exp\left( -3Hp-0.5\right)\times C</math> where <math>Hp</math> is the current Hp percentage as a decimal and <math>C</math> is the critical event multiplier of the damage. This means baseline debuff chance for damage with 1x critical event multiplier starts at &sim;3% and increases to &sim;60% as the component takes damage.

This crit then has a chance of being a catastrophic based on the component's Catastrophic event probability.

The time to repair a debuff is determined by the repair speed of the DC team and the repair work required

=== Debuffs list ===
{| class="wikitable sortable"
|+ Debuffs effects list
|-
! In game name !! Internal name !! Stat Affected !! Modifier !! RepairWork
|-
| Atmosphere Leak || Atmosphere Leak || component-workspeed || -50% || 10
|-
| Fire || Fire || component-workspeed || -20% || 10
|-
| Fuel Line Fire || Fuel Line Fire || component-workspeed || -20% || 40
|-
| Magazine Cookoff || Magazine Cookoff || component-workspeed || -20% || 30
|-
| Reactor Overload || Reactor Overload || powerplant-prodefficiency || +25% || 65
|-
| Main Bus Short || Main Bus Short || powerplant-prodefficiency || -50% || 30
|-
| Cell Cookoff || Cell Launcher Cookoff || component-workspeed || -20% || 30
|-
| Container Bank Cookoff || Container Bank Cookoff || component-workspeed || -20% || 60
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || discreteweapon-reload, discreteweapon-recycle || +75%, +75% || 10
|-
| FC Waveguide Bent || FC Waveguide Bent || sensor-power || -50% || 10
|-
| Gyroscope Drift || Gyro Drift || muzzle-accuracy (spread) || +75% || 10
|-
| Heatsink Ruptured || Heatsink Ruptured || continuousweapon-cooldown, continuousweapon-overheatdamageprob|| +75%, +90% || 15
|-
| Antenna Bent || Sensor Antenna Bent || sensor-gain || -50% || 10
|-
| Antenna Bent || Sensor Oscillator Drift || sensor-maxposerror, sensor-maxvelerror || +100%, +100% || 10
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| turret-traverse, turret-elevate (rotation speed) || -80%, -80%|| 20
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| continuousweapon-directdamagemultiplier || -66% || 15
|}

* component-workspeed affects the repair speed of the DC teams inside the component; penalty cannot reduce workspeed below 33%
* There are two types of Antenna Bent, and while they have different internal names, in-game there's no way to tell which type of debuff is in effect.

{| class="wikitable sortable"
|+ Casualty class determines the voicelines that play when the debuff is incurred
|-
! In game name !! Internal name !! Affected class !! Required Condition !! Casualty class !! On-hitOnly !! Rare (catastrophic)
|-
| Atmosphere Leak || Atmosphere Leak || CrewedComponent || none || Decompression || TRUE || FALSE
|-
| Fire || Fire || HullComponent || none || Fire || FALSE || FALSE
|-
| Fuel Line Fire || Fuel Line Fire || DriveComponent || none || Fire || TRUE || TRUE
|-
| Magazine Cookoff || Magazine Cookoff || BulkMagazineComponent<ref>BulkMagazineComponents include all types of magazines, including reinforced and citadel magazines.</ref> || ContainsAnyAmmo || Fire || TRUE || TRUE
|-
| Reactor Overload || Reactor Overload || PowerplantComponent || none || Engineering || FALSE || TRUE
|-
| Main Bus Short || Main Bus Short || PowerplantComponent || none || Engineering || FALSE || FALSE
|-
| Cell Cookoff || Cell Launcher Cookoff || BaseCellLauncherComponent || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Container Bank Cookoff || Container Bank Cookoff || Container Bank<ref>Container bank cookoffs do not have an explicit affected class, but container banks have container bank cookoffs set as a unique debuff. it is unknown if container bank cookoffs can also suffer regular cell cookoffs or if it's overwritten. Magazine cookoff and cell cookoff can block eachother as they have identical keys, but container cookoff appears to have a different key. Additionally, unique debuffs are only added after the regular debuffs, which means container banks likely has a different key as otherwise the regular cell cookoff would block it.</ref> || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || DiscreteWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| FC Waveguide Bent || FC Waveguide Bent || WeaponComponent || HasIntegratedFC || CombatSystems || FALSE || FALSE
|-
| Gyroscope Drift || Gyro Drift || WeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Heatsink Ruptured || Heatsink Ruptured || ContinuousWeaponComponent || HasCooldown || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Antenna Bent || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Oscillator Drift || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| TurretedDiscreteWeaponComponent, FixedDiscreteWeaponComponent, TurretedContinuousWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| Beams<ref>Similar to container bank cookoffs. Is explicitly defined in both the spinal beam and beam turret.</ref> || none || CombatSystems || FALSE || FALSE
|}

[[File:ComponentClassInheritance.png|alt=Component Class Hierarchy|Component class hierarchy. Child classes inherit the crits of their parents.]]

==== Fire ====
Fires deal damage over time and can spread to different components
Every 30 seconds, fires deal 5% of the component's max HP as damage (ignores DR), with 10% crew vulnerability modifier
Every 45 seconds, fires have a 25% chance to spread to a component within 12.5m

A few other debuffs will also deal damage like fire, but will not spread. This includes Cookoffs and Reactor Overloads

=== Rare Debuffs/Catastrophic Events ===
There are currently 3 types of catastrophic events in game. ''Reactor Overload'', ''Fuel Line Fire'', and ''Magazine Cookoff''.

==== Reactor Overload ====
Reactor Overload is a event that would require immediate intervention of the damage control team to prevent a devastating explosion. If 65 points of repair work is not completed within 120 seconds, the reactor detonates in a gigantic explosion that completely destroys ship, and shreds a significant amount of armor off other nearby ships caught within the 1.5km explosion radius. The explosion also creates very strong radar jamming effect in all directions that is strong enough to break bullseye locks.

Reactor Overload explosions have a blast radius of 1.5km, dealing less damage against ships at the edge of the radius. The explosion shreds 200cm-20cm of armor, and if it fully shreds armor, will deal 1500 - 450 damage spread across the ship. Reactor overloads are guarenteed to hit every munition (missiles, mines, etc) in radius.

The jamming effect has a maximum range of 7.5km, 2500kw, 1dB gain, and lasts for 20 seconds.

===== Emergency reactor shutdown =====
Emergency reactor shutdowns can be initiated by the player to clear reactor overloads. They will stop all power and propulsion on the ship for 60 seconds.

30 seconds into the shutdown, all reactor overloads will be cleared, and any component that had an overload will be destroyed.

Note that shutdown is only effective on overloads, and will not stop fuel fires or cookoffs.

==== Fuel Line Fires ====
Fuel Line fires can appear on drives or reactors. If 40 points of repair work is not completed within 100 seconds, it will cause multiple small purple explosions to erupt across the ship, dealing heavy damage across the ship

it specifically causes 2 to 4 explosions per 5 meters of ship length, rounded up,<ref>More specifically, it looks at how long the ship's bounding radius is, and then multiplies that by a random float between 2-4</ref> eg a sprinter will only suffer 8-16 explosions, but a solomon will suffer 29-58 explosions.

Each explosion appears in a random position inside the hull and deals 200 damage in a 15m radius, shreds armor in a 60m radius. Explosions happen every 0.2-0.5 secs until the amount of explosions are reached.

==== Magazine/Cell Cookoff ====
Magazine/Cell Cookoffs can appear on magazines and VLS cells. If 30 points of repair work is not completed within 80 seconds, it will create a large explosion inside the ship, dealing massive damage to the area around magazine (3000 damage spread among components within 50m, shreds armor in 60m radius)
When a Magazine Cook-off is in progress, you can hear crackling sound effects in the vicinity of the ship.

Container bank cookoffs require 65pts of repair work within 120 seconds instead, and deals 15000 damage spread among components within 75m, and shreds armor within 100m.

== Damage Control Board ==
The Damage Control Board is displayed at the bottom right of the screen, whenever a ship is selected. It shows the ship's silhouette with colored boxes depicting the ships components. The color of the box indicates the component's health: bright green(high health), yellow(medium health), red(low health) and grey(destroyed).<ref>These colors are for the default color settings. Colorblindness settings will change the colors.</ref>

Aside from the ship's abstract, a couple of numbers are shown on the top of DC Board.
=== DMG ===
DMG shows how many components on ship is damaged or destroyed, individual thrusters and integrated antennas are also included.
=== TMS ===
TMS shows how many damage control teams are still operational, and how many are working. For example, for a indication of 1/2, it means 1 of the 2 teams are currently assigned with tasks.
=== RES ===
RES shows how many available restores do you have on ship. DC lockers that are destroyed with restores in them would not contribute to this number. However, it is feasible to spend 1 restore to repair a destroyed [[component:large-dc-locker|Large DC Locker]] with 2 restores in it, to get 1 additional restore back. This is often referred to as ''chain restoring''.
Restore would only be conducted if the player explicitly commanded this operation by Shift+LClicking a destroyed component, this would add a purple dotted outline over the component.

=== Prioritize ===
Player can prioritize the repair of a non-destroyed component by Shift+LClicking it, this is indicated by a blue dotted outline around the component.
=== Filtering ===
When the DC Board is expanded, there is a filter provided at the top left of the board. Player may select/deselect different categories to reduce clutter on the DC Board.

== DC Components ==
There are currently 3 types of DC-related components.

=== DC Lockers ===
Each DC lockers provide you with certain numbers of DC Teams and Restores.

{| class="wikitable"
|-
!rowspan="2"|DC Locker Type !!rowspan="2"|DC Teams !!colspan="4"|Repair Rate !!rowspan="2"|Movement Speed !!rowspan="2"|Restores
|-
! General !! Restore !! Firefighting !! Reactor Overload
|-
| [[component:small-dc-locker|Small DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:reinforced-dc-locker|Reinforced DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:large-dc-locker|Large DC Locker]] || 3 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 2
|-
| [[component:rapid-dc-locker|Rapid DC Locker]] || 1 || 0.3 || 0 || 0.3 || 0.3 || 1 || 0
|}

=== DC Buffing Components ===

{| class="wikitable"
|-
! Component !! Repair Speed !! Move Speed
|-
| [[component:small-workshop|Small Workshop]] || 30% || N/A
|-
| [[component:damage-control-central|Damage Control Central]] || 10% || 50%
|}

=== Safety Components ===

{| class="wikitable"
|-
| [[component:fire-suppression-system|Fire Suppression System:]] || Catastrophic Event Prob. (Cell launcher): -50%

Catastrophic Event Prob. (Magazine): -50%

Firefighting Speed: +50%
|-
| [[component:redundant-reactor-failsafes| Redundant Reactor Failsafes:]] || Catastrophic Event Prob. (Reactor): -33%

Reactor Overload Repair Speed: +30%
|-
| [[component:reinforced-thruster-nozzles| Reinforced Thruster Nozzles:]] || Flank Damage Probability: -20%
|}

==Notes==
<references />

Damage Control

2024-10-22T12:52:30Z

76561198801434526: /* Safety Components */ updated safety components

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
Shooting weapons at hostiles is just one part of space combat, and the other part often involves taking shots. Sooner or later, your ship will catch on fire, have a leak, or have its internal components damaged beyond use.
And when that happens, your on-board damage control team will kick in and save your day.

<div style="clear: both"></div>
=== Definition of components ===
Everything on a ship is considered a component by damage control, no matter if it is a thruster, a compartment, a mount, or a module.
When a components receives damage, it will usually lose certain amounts of HP. This section explains the mechanics of component malfunction and repairs.
For detailed information on damage mechanics, see [[Component_Damage |Component Damage]].

==== Inoperable components ====
Most components have a hidden attribute called ''Functioning Threshold'', (aka Functioning Threshold). If a component's HP is reduced below this threshold, it will cease to function, and requires repairs to operate again.

=== Damage Control teams ===
Damaged components can be repaired. However, instead of repairing it back to 100%, your damage control teams can only repair a component to a certain percentage above its lowest condition percentage. This stat is known as the Max Repair stat (also colloquially known as repair cap); for most ships it starts at 10%. eg, if a component is damage down to 50% hp, repair teams on that ship will only be able to bring it back up to 60% hp

There is one an exception to this rule, a component can always be repaired to it's minimum functioning threshold hp + Max Repair, regardless of how much damage they take below the threshold. e.g. a Large Reinforced Drive (1500hp, 50hp minimum functioning) can always be repaired up to 200hp (50 from min function + 150 from 10% max repair), a Reinforced CIC (200hp, 10 minimum function threshold) can always be repaired up to 30hp (10 + 20)

Each component can only be repaired by three teams at once, one team for repairing HP and two teams for repairing debuffs. If there are no debuffs then only the one team will repair HP; and vice versa if there is no more hp to repair then only two teams will repair debuffs

Damage control teams tick once every 0.25 sec, applying the equivalent hp/sec as repair work. This is not modified by the amount of team members, a 1/5 team will repair at the same rate as a 5/5 team

Damage control teams speed in m/s is equal to <math>\text{movespeed}\times 2.5</math>. The stats on the wiki has already performed this conversion.

==== Damage Control priorities ====
Every ship has a damage control dispatcher that assigns DC teams to repair jobs and manages repair priorities.

<div style="float: right; margin-left: 20px; padding: 10px; border-style: solid; background-color:lightgray; width: 350px;">
DC dispatcher example list

Given a ship that has: 
- damaged drive (Critical prio) with atmo leak, fire, overload 
- damaged cic (high prio) 
- damaged magazine (med prio) with ammo cookoff 
- damaged DC locker (low prio) 

the lists will look something like this:

Primary: 
- Drive Overload 
- Drive Atmo leak 
- CIC hp 
- Magazine Ammo cookoff 

Secondary: 
-Drive HP 
-Magazine HP 
-DC locker HP 
</div>

The dispatcher has a primary and secondary repair job list. These lists are filled with repair jobs, which include both damaged components and debuffs (aka critical events) that need repair. Each Component adds their repair jobs to the lists according to the component's DC priority stat (normally a hidden stat), in the event of ties, components higher in the component list are prioritized and will add their debuffs to the list first.

Within each component, up to two debuffs events are added to the list. Catastrophics are prioritized first and always added to the primary list. Then, regular debuffs are added (up to the two debuff cap), starting from the top of the component's debuffs list as seen in the DC board. These debuffs are added to the primary list if the component is still alive, and added to the secondary list if destroyed (unless the component is manually prioritized). Then, the component adds its HP repair to the secondary list. If the component has no debuffs and has medium or higher DC priority, it instead adds its HP repair to the primary list

Using these lists, the DC team then assigns teams to the repair jobs in the list, satisfying all jobs in the primary list before filling secondary jobs

Damage control teams from DC lockers higher in the component list are tasked to jobs first. eg, DC teams from compartment 1's locker will be assigned to tasks before DC teams from compartment 2's locker, regardless of difference in team move speed, repair speed, or distance to damaged component. The only exception to this rule is if there is already a DC team in that component; it will be tasked to work on repairs immediately. However, this will not be performed for repair jobs in the secondary list, those jobs will summon another DC team even if there is an idle DC team in the same component.


==== Repair team casualties ====
Damage control teams themselves will only take losses if their current component is below 50% hp.
DC teams currently do not replenish, even if there is spare crew available
''see: [[Crew]]''

=== Restore ===
When a component loses all of its health, it becomes ''Destroyed''. In this state, the component can no longer be hit by any further damage (and is therefore treated as empty space by attacks), nor will it be automatically repaired by the control team. To bring it back online, you need to spend the ''Restores'' provided in DC Lockers. By Shift+LClicking a destroyed component, you can order a damage control team to preform a restore on the destroyed component. After the restore progress is completed, the component is instantly repaired to its minimum functioning HP plus its max repair. Restores require 50 "hp" worth of work to apply.

Restore usage seems to be distributed among the lockers, starting from the closest locker and working outward

== Ship Status Board ==
On the top left of the game screen, every ship has a ship status board that shows the ship's information. At the bottom right of the board, ship damage control status would be displayed.
;Fire Icon
: If there are at least one fire on board, a fire icon would light up. Hovering the mouse over the icon displays the total fire count on board.
;Active Debuffs
: If there are at least one active debuff on board, a orange number would show up on ship status board. Hovering over the number would display where and what are the debuffs on board.
;Destroyed components
: If there is at least one destroyed component, a red number will show up on ship status board. Hovering over the number would display what components are destroyed.
;Catastrophic Event
: If there is a catastrophic event on board, a red exclamation icon and a timer counting down would be displayed to the right of the corresponding ship's status board. If there is more than 1 event on board, only the shortest timer would be displayed. If the count down reaches zero, usually a big bang would take place.

== Debuffs/Catastrophic Events ==

Components can suffer various types of Critical Events (aka debuffs) in game, some would slow down the work speed of your damage control team, while others may degrade your ship's performance, or even obliterate your ship entirely.

Damage has a chance of causing debuffs on components. This chance is calculated by <math>\exp\left( -3Hp-0.5\right)\times C</math> where <math>Hp</math> is the current Hp percentage as a decimal and <math>C</math> is the critical event multiplier of the damage. This means baseline debuff chance for damage with 1x critical event multiplier starts at &sim;3% and increases to &sim;60% as the component takes damage.

This crit then has a chance of being a catastrophic based on the component's Catastrophic event probability.

The time to repair a debuff is determined by the repair speed of the DC team and the repair work required

=== Debuffs list ===
{| class="wikitable sortable"
|+ Debuffs effects list
|-
! In game name !! Internal name !! Stat Affected !! Modifier !! RepairWork
|-
| Atmosphere Leak || Atmosphere Leak || component-workspeed || -50% || 10
|-
| Fire || Fire || component-workspeed || -20% || 10
|-
| Fuel Line Fire || Fuel Line Fire || component-workspeed || -20% || 40
|-
| Magazine Cookoff || Magazine Cookoff || component-workspeed || -20% || 30
|-
| Reactor Overload || Reactor Overload || powerplant-prodefficiency || +25% || 65
|-
| Main Bus Short || Main Bus Short || powerplant-prodefficiency || -50% || 30
|-
| Cell Cookoff || Cell Launcher Cookoff || component-workspeed || -20% || 30
|-
| Container Bank Cookoff || Container Bank Cookoff || component-workspeed || -20% || 60
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || discreteweapon-reload, discreteweapon-recycle || +75%, +75% || 10
|-
| FC Waveguide Bent || FC Waveguide Bent || sensor-power || -50% || 10
|-
| Gyroscope Drift || Gyro Drift || muzzle-accuracy (spread) || +75% || 10
|-
| Heatsink Ruptured || Heatsink Ruptured || continuousweapon-cooldown, continuousweapon-overheatdamageprob|| +75%, +90% || 15
|-
| Antenna Bent || Sensor Antenna Bent || sensor-gain || -50% || 10
|-
| Antenna Bent || Sensor Oscillator Drift || sensor-maxposerror, sensor-maxvelerror || +100%, +100% || 10
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| turret-traverse, turret-elevate (rotation speed) || -80%, -80%|| 20
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| continuousweapon-directdamagemultiplier || -66% || 15
|}

* component-workspeed affects the repair speed of the DC teams inside the component; penalty cannot reduce workspeed below 33%
* There are two types of Antenna Bent, and while they have different internal names, in-game there's no way to tell which type of debuff is in effect.

{| class="wikitable sortable"
|+ Casualty class determines the voicelines that play when the debuff is incurred
|-
! In game name !! Internal name !! Affected class !! Required Condition !! Casualty class !! On-hitOnly !! Rare (catastrophic)
|-
| Atmosphere Leak || Atmosphere Leak || CrewedComponent || none || Decompression || TRUE || FALSE
|-
| Fire || Fire || HullComponent || none || Fire || FALSE || FALSE
|-
| Fuel Line Fire || Fuel Line Fire || DriveComponent || none || Fire || TRUE || TRUE
|-
| Magazine Cookoff || Magazine Cookoff || BulkMagazineComponent<ref>BulkMagazineComponents include all types of magazines, including reinforced and citadel magazines.</ref> || ContainsAnyAmmo || Fire || TRUE || TRUE
|-
| Reactor Overload || Reactor Overload || PowerplantComponent || none || Engineering || FALSE || TRUE
|-
| Main Bus Short || Main Bus Short || PowerplantComponent || none || Engineering || FALSE || FALSE
|-
| Cell Cookoff || Cell Launcher Cookoff || BaseCellLauncherComponent || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Container Bank Cookoff || Container Bank Cookoff || Container Bank<ref>Container bank cookoffs do not have an explicit affected class, but container banks have container bank cookoffs set as a unique debuff. it is unknown if container bank cookoffs can also suffer regular cell cookoffs or if it's overwritten. Magazine cookoff and cell cookoff can block eachother as they have identical keys, but container cookoff appears to have a different key. Additionally, unique debuffs are only added after the regular debuffs, which means container banks likely has a different key as otherwise the regular cell cookoff would block it.</ref> || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || DiscreteWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| FC Waveguide Bent || FC Waveguide Bent || WeaponComponent || HasIntegratedFC || CombatSystems || FALSE || FALSE
|-
| Gyroscope Drift || Gyro Drift || WeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Heatsink Ruptured || Heatsink Ruptured || ContinuousWeaponComponent || HasCooldown || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Antenna Bent || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Oscillator Drift || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| TurretedDiscreteWeaponComponent, FixedDiscreteWeaponComponent, TurretedContinuousWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| Beams<ref>Similar to container bank cookoffs. Is explicitly defined in both the spinal beam and beam turret.</ref> || none || CombatSystems || FALSE || FALSE
|}

[[File:ComponentClassInheritance.png|alt=Component Class Hierarchy|Component class hierarchy. Child classes inherit the crits of their parents.]]

==== Fire ====
Fires deal damage over time and can spread to different components
Every 30 seconds, fires deal 5% of the component's max HP as damage (ignores DR), with 10% crew vulnerability modifier
Every 45 seconds, fires have a 25% chance to spread to a component within 12.5m

A few other debuffs will also deal damage like fire, but will not spread. This includes Cookoffs and Reactor Overloads

=== Rare Debuffs/Catastrophic Events ===
There are currently 3 types of catastrophic events in game. ''Reactor Overload'', ''Fuel Line Fire'', and ''Magazine Cookoff''.

==== Reactor Overload ====
Reactor Overload is a event that would require immediate intervention of the damage control team to prevent a devastating explosion. If 65 points of repair work is not completed within 120 seconds, the reactor detonates in a gigantic explosion that completely destroys ship, and shreds a significant amount of armor off other nearby ships caught within the 1.5km explosion radius. The explosion also creates very strong radar jamming effect in all directions that is strong enough to break bullseye locks.

Reactor Overload explosions have a blast radius of 1.5km, dealing less damage against ships at the edge of the radius. The explosion shreds 200cm-20cm of armor, and if it fully shreds armor, will deal 1500 - 450 damage spread across the ship. Reactor overloads are guarenteed to hit every munition (missiles, mines, etc) in radius.

The jamming effect has a maximum range of 7.5km, 2500kw, 1dB gain, and lasts for 20 seconds.

===== Emergency reactor shutdown =====
Emergency reactor shutdowns can be initiated by the player to clear reactor overloads. They will stop all power and propulsion on the ship for 60 seconds.

30 seconds into the shutdown, all reactor overloads will be cleared, and any component that had an overload will be destroyed.

Note that shutdown is only effective on overloads, and will not stop fuel fires or cookoffs.

==== Fuel Line Fires ====
Fuel Line fires can appear on drives or reactors. If 40 points of repair work is not completed within 100 seconds, it will cause multiple small purple explosions to erupt across the ship, dealing heavy damage across the ship

it specifically causes 2 to 4 explosions per 5 meters of ship length, rounded up,<ref>More specifically, it looks at how long the ship's bounding radius is, and then multiplies that by a random float between 2-4</ref> eg a sprinter will only suffer 8-16 explosions, but a solomon will suffer 29-58 explosions.

Each explosion appears in a random position inside the hull and deals 200 damage in a 15m radius, shreds armor in a 60m radius. Explosions happen every 0.2-0.5 secs until the amount of explosions are reached.

==== Magazine/Cell Cookoff ====
Magazine/Cell Cookoffs can appear on magazines and VLS cells. If 30 points of repair work is not completed within 80 seconds, it will create a large explosion inside the ship, dealing massive damage to the area around magazine (3000 damage spread among components within 50m, shreds armor in 60m radius)
When a Magazine Cook-off is in progress, you can hear crackling sound effects in the vicinity of the ship.

Container bank cookoffs require 65pts of repair work within 120 seconds instead, and deals 15000 damage spread among components within 75m, and shreds armor within 100m.

== Damage Control Board ==
The Damage Control Board is displayed at the bottom right of the screen, whenever a ship is selected. It shows the ship's silhouette with colored boxes depicting the ships components. The color of the box indicates the component's health: bright green(high health), yellow(medium health), red(low health) and grey(destroyed).<ref>These colors are for the default color settings. Colorblindness settings will change the colors.</ref>

Aside from the ship's abstract, a couple of numbers are shown on the top of DC Board.
=== DMG ===
DMG shows how many components on ship is damaged or destroyed, individual thrusters and integrated antennas are also included.
=== TMS ===
TMS shows how many damage control teams are still operational, and how many are working. For example, for a indication of 1/2, it means 1 of the 2 teams are currently assigned with tasks.
=== RES ===
RES shows how many available restores do you have on ship. DC lockers that are destroyed with restores in them would not contribute to this number. However, it is feasible to spend 1 restore to repair a destroyed [[component:large-dc-locker|Large DC Locker]] with 2 restores in it, to get 1 additional restore back. This is often referred to as ''chain restoring''.
Restore would only be conducted if the player explicitly commanded this operation by Shift+LClicking a destroyed component, this would add a purple dotted outline over the component.

=== Prioritize ===
Player can prioritize the repair of a non-destroyed component by Shift+LClicking it, this is indicated by a blue dotted outline around the component.
=== Filtering ===
When the DC Board is expanded, there is a filter provided at the top left of the board. Player may select/deselect different categories to reduce clutter on the DC Board.

== DC Components ==
There are currently 3 types of DC-related components.

=== DC Lockers ===
Each DC lockers provide you with certain numbers of DC Teams and Restores.

{| class="wikitable"
|-
!rowspan="2"|DC Locker Type !!rowspan="2"|DC Teams !!colspan="4"|Repair Rate !!rowspan="2"|Movement Speed !!rowspan="2"|Restores
|-
! General !! Restore !! Firefighting !! Reactor Overload
|-
| [[component:small-dc-locker|Small DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:reinforced-dc-locker|Reinforced DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:large-dc-locker|Large DC Locker]] || 3 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 2
|-
| [[component:rapid-dc-locker|Rapid DC Locker]] || 1 || 0.3 || 0 || 0.3 || 0.3 || 1 || 0
|}

=== DC Buffing Components ===

{| class="wikitable"
|-
! Component !! Repair Speed !! Move Speed
|-
| [[component:small-workshop|Small Workshop]] || 30% || N/A
|-
| [[component:damage-control-central|Damage Control Central]] || 10% || 50%
|}

=== Safety Components ===

{| class="wikitable"
|-
| [[component:fire-suppression-system|Fire Suppression System:]] || Catastrophic Event Prob. (Cell launcher): -50%
Catastrophic Event Prob. (Magazine): -50%
Firefighting Speed: +50%
|-
| [[component:redundant-reactor-failsafes| Redundant Reactor Failsafes:]] || Catastrophic Event Prob. (Reactor): -33%
Reactor Overload Repair Speed: +30%
|-
| [[component:reinforced-thruster-nozzles| Reinforced Thruster Nozzles:]] || Flank Damage Probability: -20%
|}

==Notes==
<references />

Damage Control

2024-10-22T12:27:50Z

76561198801434526: /* DC Lockers */ fixed repair rate rowspan

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
Shooting weapons at hostiles is just one part of space combat, and the other part often involves taking shots. Sooner or later, your ship will catch on fire, have a leak, or have its internal components damaged beyond use.
And when that happens, your on-board damage control team will kick in and save your day.

<div style="clear: both"></div>
=== Definition of components ===
Everything on a ship is considered a component by damage control, no matter if it is a thruster, a compartment, a mount, or a module.
When a components receives damage, it will usually lose certain amounts of HP. This section explains the mechanics of component malfunction and repairs.
For detailed information on damage mechanics, see [[Component_Damage |Component Damage]].

==== Inoperable components ====
Most components have a hidden attribute called ''Functioning Threshold'', (aka Functioning Threshold). If a component's HP is reduced below this threshold, it will cease to function, and requires repairs to operate again.

=== Damage Control teams ===
Damaged components can be repaired. However, instead of repairing it back to 100%, your damage control teams can only repair a component to a certain percentage above its lowest condition percentage. This stat is known as the Max Repair stat (also colloquially known as repair cap); for most ships it starts at 10%. eg, if a component is damage down to 50% hp, repair teams on that ship will only be able to bring it back up to 60% hp

There is one an exception to this rule, a component can always be repaired to it's minimum functioning threshold hp + Max Repair, regardless of how much damage they take below the threshold. e.g. a Large Reinforced Drive (1500hp, 50hp minimum functioning) can always be repaired up to 200hp (50 from min function + 150 from 10% max repair), a Reinforced CIC (200hp, 10 minimum function threshold) can always be repaired up to 30hp (10 + 20)

Each component can only be repaired by three teams at once, one team for repairing HP and two teams for repairing debuffs. If there are no debuffs then only the one team will repair HP; and vice versa if there is no more hp to repair then only two teams will repair debuffs

Damage control teams tick once every 0.25 sec, applying the equivalent hp/sec as repair work. This is not modified by the amount of team members, a 1/5 team will repair at the same rate as a 5/5 team

Damage control teams speed in m/s is equal to <math>\text{movespeed}\times 2.5</math>. The stats on the wiki has already performed this conversion.

==== Damage Control priorities ====
Every ship has a damage control dispatcher that assigns DC teams to repair jobs and manages repair priorities.

<div style="float: right; margin-left: 20px; padding: 10px; border-style: solid; background-color:lightgray; width: 350px;">
DC dispatcher example list

Given a ship that has: 
- damaged drive (Critical prio) with atmo leak, fire, overload 
- damaged cic (high prio) 
- damaged magazine (med prio) with ammo cookoff 
- damaged DC locker (low prio) 

the lists will look something like this:

Primary: 
- Drive Overload 
- Drive Atmo leak 
- CIC hp 
- Magazine Ammo cookoff 

Secondary: 
-Drive HP 
-Magazine HP 
-DC locker HP 
</div>

The dispatcher has a primary and secondary repair job list. These lists are filled with repair jobs, which include both damaged components and debuffs (aka critical events) that need repair. Each Component adds their repair jobs to the lists according to the component's DC priority stat (normally a hidden stat), in the event of ties, components higher in the component list are prioritized and will add their debuffs to the list first.

Within each component, up to two debuffs events are added to the list. Catastrophics are prioritized first and always added to the primary list. Then, regular debuffs are added (up to the two debuff cap), starting from the top of the component's debuffs list as seen in the DC board. These debuffs are added to the primary list if the component is still alive, and added to the secondary list if destroyed (unless the component is manually prioritized). Then, the component adds its HP repair to the secondary list. If the component has no debuffs and has medium or higher DC priority, it instead adds its HP repair to the primary list

Using these lists, the DC team then assigns teams to the repair jobs in the list, satisfying all jobs in the primary list before filling secondary jobs

Damage control teams from DC lockers higher in the component list are tasked to jobs first. eg, DC teams from compartment 1's locker will be assigned to tasks before DC teams from compartment 2's locker, regardless of difference in team move speed, repair speed, or distance to damaged component. The only exception to this rule is if there is already a DC team in that component; it will be tasked to work on repairs immediately. However, this will not be performed for repair jobs in the secondary list, those jobs will summon another DC team even if there is an idle DC team in the same component.


==== Repair team casualties ====
Damage control teams themselves will only take losses if their current component is below 50% hp.
DC teams currently do not replenish, even if there is spare crew available
''see: [[Crew]]''

=== Restore ===
When a component loses all of its health, it becomes ''Destroyed''. In this state, the component can no longer be hit by any further damage (and is therefore treated as empty space by attacks), nor will it be automatically repaired by the control team. To bring it back online, you need to spend the ''Restores'' provided in DC Lockers. By Shift+LClicking a destroyed component, you can order a damage control team to preform a restore on the destroyed component. After the restore progress is completed, the component is instantly repaired to its minimum functioning HP plus its max repair. Restores require 50 "hp" worth of work to apply.

Restore usage seems to be distributed among the lockers, starting from the closest locker and working outward

== Ship Status Board ==
On the top left of the game screen, every ship has a ship status board that shows the ship's information. At the bottom right of the board, ship damage control status would be displayed.
;Fire Icon
: If there are at least one fire on board, a fire icon would light up. Hovering the mouse over the icon displays the total fire count on board.
;Active Debuffs
: If there are at least one active debuff on board, a orange number would show up on ship status board. Hovering over the number would display where and what are the debuffs on board.
;Destroyed components
: If there is at least one destroyed component, a red number will show up on ship status board. Hovering over the number would display what components are destroyed.
;Catastrophic Event
: If there is a catastrophic event on board, a red exclamation icon and a timer counting down would be displayed to the right of the corresponding ship's status board. If there is more than 1 event on board, only the shortest timer would be displayed. If the count down reaches zero, usually a big bang would take place.

== Debuffs/Catastrophic Events ==

Components can suffer various types of Critical Events (aka debuffs) in game, some would slow down the work speed of your damage control team, while others may degrade your ship's performance, or even obliterate your ship entirely.

Damage has a chance of causing debuffs on components. This chance is calculated by <math>\exp\left( -3Hp-0.5\right)\times C</math> where <math>Hp</math> is the current Hp percentage as a decimal and <math>C</math> is the critical event multiplier of the damage. This means baseline debuff chance for damage with 1x critical event multiplier starts at &sim;3% and increases to &sim;60% as the component takes damage.

This crit then has a chance of being a catastrophic based on the component's Catastrophic event probability.

The time to repair a debuff is determined by the repair speed of the DC team and the repair work required

=== Debuffs list ===
{| class="wikitable sortable"
|+ Debuffs effects list
|-
! In game name !! Internal name !! Stat Affected !! Modifier !! RepairWork
|-
| Atmosphere Leak || Atmosphere Leak || component-workspeed || -50% || 10
|-
| Fire || Fire || component-workspeed || -20% || 10
|-
| Fuel Line Fire || Fuel Line Fire || component-workspeed || -20% || 40
|-
| Magazine Cookoff || Magazine Cookoff || component-workspeed || -20% || 30
|-
| Reactor Overload || Reactor Overload || powerplant-prodefficiency || +25% || 65
|-
| Main Bus Short || Main Bus Short || powerplant-prodefficiency || -50% || 30
|-
| Cell Cookoff || Cell Launcher Cookoff || component-workspeed || -20% || 30
|-
| Container Bank Cookoff || Container Bank Cookoff || component-workspeed || -20% || 60
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || discreteweapon-reload, discreteweapon-recycle || +75%, +75% || 10
|-
| FC Waveguide Bent || FC Waveguide Bent || sensor-power || -50% || 10
|-
| Gyroscope Drift || Gyro Drift || muzzle-accuracy (spread) || +75% || 10
|-
| Heatsink Ruptured || Heatsink Ruptured || continuousweapon-cooldown, continuousweapon-overheatdamageprob|| +75%, +90% || 15
|-
| Antenna Bent || Sensor Antenna Bent || sensor-gain || -50% || 10
|-
| Antenna Bent || Sensor Oscillator Drift || sensor-maxposerror, sensor-maxvelerror || +100%, +100% || 10
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| turret-traverse, turret-elevate (rotation speed) || -80%, -80%|| 20
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| continuousweapon-directdamagemultiplier || -66% || 15
|}

* component-workspeed affects the repair speed of the DC teams inside the component; penalty cannot reduce workspeed below 33%
* There are two types of Antenna Bent, and while they have different internal names, in-game there's no way to tell which type of debuff is in effect.

{| class="wikitable sortable"
|+ Casualty class determines the voicelines that play when the debuff is incurred
|-
! In game name !! Internal name !! Affected class !! Required Condition !! Casualty class !! On-hitOnly !! Rare (catastrophic)
|-
| Atmosphere Leak || Atmosphere Leak || CrewedComponent || none || Decompression || TRUE || FALSE
|-
| Fire || Fire || HullComponent || none || Fire || FALSE || FALSE
|-
| Fuel Line Fire || Fuel Line Fire || DriveComponent || none || Fire || TRUE || TRUE
|-
| Magazine Cookoff || Magazine Cookoff || BulkMagazineComponent<ref>BulkMagazineComponents include all types of magazines, including reinforced and citadel magazines.</ref> || ContainsAnyAmmo || Fire || TRUE || TRUE
|-
| Reactor Overload || Reactor Overload || PowerplantComponent || none || Engineering || FALSE || TRUE
|-
| Main Bus Short || Main Bus Short || PowerplantComponent || none || Engineering || FALSE || FALSE
|-
| Cell Cookoff || Cell Launcher Cookoff || BaseCellLauncherComponent || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Container Bank Cookoff || Container Bank Cookoff || Container Bank<ref>Container bank cookoffs do not have an explicit affected class, but container banks have container bank cookoffs set as a unique debuff. it is unknown if container bank cookoffs can also suffer regular cell cookoffs or if it's overwritten. Magazine cookoff and cell cookoff can block eachother as they have identical keys, but container cookoff appears to have a different key. Additionally, unique debuffs are only added after the regular debuffs, which means container banks likely has a different key as otherwise the regular cell cookoff would block it.</ref> || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || DiscreteWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| FC Waveguide Bent || FC Waveguide Bent || WeaponComponent || HasIntegratedFC || CombatSystems || FALSE || FALSE
|-
| Gyroscope Drift || Gyro Drift || WeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Heatsink Ruptured || Heatsink Ruptured || ContinuousWeaponComponent || HasCooldown || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Antenna Bent || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Oscillator Drift || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| TurretedDiscreteWeaponComponent, FixedDiscreteWeaponComponent, TurretedContinuousWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| Beams<ref>Similar to container bank cookoffs. Is explicitly defined in both the spinal beam and beam turret.</ref> || none || CombatSystems || FALSE || FALSE
|}

[[File:ComponentClassInheritance.png|alt=Component Class Hierarchy|Component class hierarchy. Child classes inherit the crits of their parents.]]

==== Fire ====
Fires deal damage over time and can spread to different components
Every 30 seconds, fires deal 5% of the component's max HP as damage (ignores DR), with 10% crew vulnerability modifier
Every 45 seconds, fires have a 25% chance to spread to a component within 12.5m

A few other debuffs will also deal damage like fire, but will not spread. This includes Cookoffs and Reactor Overloads

=== Rare Debuffs/Catastrophic Events ===
There are currently 3 types of catastrophic events in game. ''Reactor Overload'', ''Fuel Line Fire'', and ''Magazine Cookoff''.

==== Reactor Overload ====
Reactor Overload is a event that would require immediate intervention of the damage control team to prevent a devastating explosion. If 65 points of repair work is not completed within 120 seconds, the reactor detonates in a gigantic explosion that completely destroys ship, and shreds a significant amount of armor off other nearby ships caught within the 1.5km explosion radius. The explosion also creates very strong radar jamming effect in all directions that is strong enough to break bullseye locks.

Reactor Overload explosions have a blast radius of 1.5km, dealing less damage against ships at the edge of the radius. The explosion shreds 200cm-20cm of armor, and if it fully shreds armor, will deal 1500 - 450 damage spread across the ship. Reactor overloads are guarenteed to hit every munition (missiles, mines, etc) in radius.

The jamming effect has a maximum range of 7.5km, 2500kw, 1dB gain, and lasts for 20 seconds.

===== Emergency reactor shutdown =====
Emergency reactor shutdowns can be initiated by the player to clear reactor overloads. They will stop all power and propulsion on the ship for 60 seconds.

30 seconds into the shutdown, all reactor overloads will be cleared, and any component that had an overload will be destroyed.

Note that shutdown is only effective on overloads, and will not stop fuel fires or cookoffs.

==== Fuel Line Fires ====
Fuel Line fires can appear on drives or reactors. If 40 points of repair work is not completed within 100 seconds, it will cause multiple small purple explosions to erupt across the ship, dealing heavy damage across the ship

it specifically causes 2 to 4 explosions per 5 meters of ship length, rounded up,<ref>More specifically, it looks at how long the ship's bounding radius is, and then multiplies that by a random float between 2-4</ref> eg a sprinter will only suffer 8-16 explosions, but a solomon will suffer 29-58 explosions.

Each explosion appears in a random position inside the hull and deals 200 damage in a 15m radius, shreds armor in a 60m radius. Explosions happen every 0.2-0.5 secs until the amount of explosions are reached.

==== Magazine/Cell Cookoff ====
Magazine/Cell Cookoffs can appear on magazines and VLS cells. If 30 points of repair work is not completed within 80 seconds, it will create a large explosion inside the ship, dealing massive damage to the area around magazine (3000 damage spread among components within 50m, shreds armor in 60m radius)
When a Magazine Cook-off is in progress, you can hear crackling sound effects in the vicinity of the ship.

Container bank cookoffs require 65pts of repair work within 120 seconds instead, and deals 15000 damage spread among components within 75m, and shreds armor within 100m.

== Damage Control Board ==
The Damage Control Board is displayed at the bottom right of the screen, whenever a ship is selected. It shows the ship's silhouette with colored boxes depicting the ships components. The color of the box indicates the component's health: bright green(high health), yellow(medium health), red(low health) and grey(destroyed).<ref>These colors are for the default color settings. Colorblindness settings will change the colors.</ref>

Aside from the ship's abstract, a couple of numbers are shown on the top of DC Board.
=== DMG ===
DMG shows how many components on ship is damaged or destroyed, individual thrusters and integrated antennas are also included.
=== TMS ===
TMS shows how many damage control teams are still operational, and how many are working. For example, for a indication of 1/2, it means 1 of the 2 teams are currently assigned with tasks.
=== RES ===
RES shows how many available restores do you have on ship. DC lockers that are destroyed with restores in them would not contribute to this number. However, it is feasible to spend 1 restore to repair a destroyed [[component:large-dc-locker|Large DC Locker]] with 2 restores in it, to get 1 additional restore back. This is often referred to as ''chain restoring''.
Restore would only be conducted if the player explicitly commanded this operation by Shift+LClicking a destroyed component, this would add a purple dotted outline over the component.

=== Prioritize ===
Player can prioritize the repair of a non-destroyed component by Shift+LClicking it, this is indicated by a blue dotted outline around the component.
=== Filtering ===
When the DC Board is expanded, there is a filter provided at the top left of the board. Player may select/deselect different categories to reduce clutter on the DC Board.

== DC Components ==
There are currently 3 types of DC-related components.

=== DC Lockers ===
Each DC lockers provide you with certain numbers of DC Teams and Restores.

{| class="wikitable"
|-
!rowspan="2"|DC Locker Type !!rowspan="2"|DC Teams !!colspan="4"|Repair Rate !!rowspan="2"|Movement Speed !!rowspan="2"|Restores
|-
! General !! Restore !! Firefighting !! Reactor Overload
|-
| [[component:small-dc-locker|Small DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:reinforced-dc-locker|Reinforced DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:large-dc-locker|Large DC Locker]] || 3 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 2
|-
| [[component:rapid-dc-locker|Rapid DC Locker]] || 1 || 0.3 || 0 || 0.3 || 0.3 || 1 || 0
|}

=== DC Buffing Components ===

{| class="wikitable"
|-
! Component !! Repair Speed !! Move Speed
|-
| [[component:small-workshop|Small Workshop]] || 30% || N/A
|-
| [[component:damage-control-central|Damage Control Central]] || 10% || 50%
|}

=== Safety Components ===

{| class="wikitable"
|-
| [[component:launcher-deluge-system|Launcher Deluge System:]] || Catastrophic Event Prob. (Cell launcher): -50%
|-
| [[component:magazine-sprinklers|Magazine Sprinklers:]] || Catastrophic Event Prob. (Magazine): -50%
|-
| [[component:redundant-reactor-failsafes| Redundant Reactor Failsafes:]] || Catastrophic Event Prob. (Reactor): -33%
|-
| [[component:reinforced-thruster-nozzles| Reinforced Thruster Nozzles:]] || Flank Damage Probability: -20%
|}

==Notes==
<references />

Damage Control

2024-10-22T12:26:57Z

76561198801434526: /* DC Lockers */ updated DC table to break apart the repair stat, reflecting the latest patch. The numbers may not be correct

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
Shooting weapons at hostiles is just one part of space combat, and the other part often involves taking shots. Sooner or later, your ship will catch on fire, have a leak, or have its internal components damaged beyond use.
And when that happens, your on-board damage control team will kick in and save your day.

<div style="clear: both"></div>
=== Definition of components ===
Everything on a ship is considered a component by damage control, no matter if it is a thruster, a compartment, a mount, or a module.
When a components receives damage, it will usually lose certain amounts of HP. This section explains the mechanics of component malfunction and repairs.
For detailed information on damage mechanics, see [[Component_Damage |Component Damage]].

==== Inoperable components ====
Most components have a hidden attribute called ''Functioning Threshold'', (aka Functioning Threshold). If a component's HP is reduced below this threshold, it will cease to function, and requires repairs to operate again.

=== Damage Control teams ===
Damaged components can be repaired. However, instead of repairing it back to 100%, your damage control teams can only repair a component to a certain percentage above its lowest condition percentage. This stat is known as the Max Repair stat (also colloquially known as repair cap); for most ships it starts at 10%. eg, if a component is damage down to 50% hp, repair teams on that ship will only be able to bring it back up to 60% hp

There is one an exception to this rule, a component can always be repaired to it's minimum functioning threshold hp + Max Repair, regardless of how much damage they take below the threshold. e.g. a Large Reinforced Drive (1500hp, 50hp minimum functioning) can always be repaired up to 200hp (50 from min function + 150 from 10% max repair), a Reinforced CIC (200hp, 10 minimum function threshold) can always be repaired up to 30hp (10 + 20)

Each component can only be repaired by three teams at once, one team for repairing HP and two teams for repairing debuffs. If there are no debuffs then only the one team will repair HP; and vice versa if there is no more hp to repair then only two teams will repair debuffs

Damage control teams tick once every 0.25 sec, applying the equivalent hp/sec as repair work. This is not modified by the amount of team members, a 1/5 team will repair at the same rate as a 5/5 team

Damage control teams speed in m/s is equal to <math>\text{movespeed}\times 2.5</math>. The stats on the wiki has already performed this conversion.

==== Damage Control priorities ====
Every ship has a damage control dispatcher that assigns DC teams to repair jobs and manages repair priorities.

<div style="float: right; margin-left: 20px; padding: 10px; border-style: solid; background-color:lightgray; width: 350px;">
DC dispatcher example list

Given a ship that has: 
- damaged drive (Critical prio) with atmo leak, fire, overload 
- damaged cic (high prio) 
- damaged magazine (med prio) with ammo cookoff 
- damaged DC locker (low prio) 

the lists will look something like this:

Primary: 
- Drive Overload 
- Drive Atmo leak 
- CIC hp 
- Magazine Ammo cookoff 

Secondary: 
-Drive HP 
-Magazine HP 
-DC locker HP 
</div>

The dispatcher has a primary and secondary repair job list. These lists are filled with repair jobs, which include both damaged components and debuffs (aka critical events) that need repair. Each Component adds their repair jobs to the lists according to the component's DC priority stat (normally a hidden stat), in the event of ties, components higher in the component list are prioritized and will add their debuffs to the list first.

Within each component, up to two debuffs events are added to the list. Catastrophics are prioritized first and always added to the primary list. Then, regular debuffs are added (up to the two debuff cap), starting from the top of the component's debuffs list as seen in the DC board. These debuffs are added to the primary list if the component is still alive, and added to the secondary list if destroyed (unless the component is manually prioritized). Then, the component adds its HP repair to the secondary list. If the component has no debuffs and has medium or higher DC priority, it instead adds its HP repair to the primary list

Using these lists, the DC team then assigns teams to the repair jobs in the list, satisfying all jobs in the primary list before filling secondary jobs

Damage control teams from DC lockers higher in the component list are tasked to jobs first. eg, DC teams from compartment 1's locker will be assigned to tasks before DC teams from compartment 2's locker, regardless of difference in team move speed, repair speed, or distance to damaged component. The only exception to this rule is if there is already a DC team in that component; it will be tasked to work on repairs immediately. However, this will not be performed for repair jobs in the secondary list, those jobs will summon another DC team even if there is an idle DC team in the same component.


==== Repair team casualties ====
Damage control teams themselves will only take losses if their current component is below 50% hp.
DC teams currently do not replenish, even if there is spare crew available
''see: [[Crew]]''

=== Restore ===
When a component loses all of its health, it becomes ''Destroyed''. In this state, the component can no longer be hit by any further damage (and is therefore treated as empty space by attacks), nor will it be automatically repaired by the control team. To bring it back online, you need to spend the ''Restores'' provided in DC Lockers. By Shift+LClicking a destroyed component, you can order a damage control team to preform a restore on the destroyed component. After the restore progress is completed, the component is instantly repaired to its minimum functioning HP plus its max repair. Restores require 50 "hp" worth of work to apply.

Restore usage seems to be distributed among the lockers, starting from the closest locker and working outward

== Ship Status Board ==
On the top left of the game screen, every ship has a ship status board that shows the ship's information. At the bottom right of the board, ship damage control status would be displayed.
;Fire Icon
: If there are at least one fire on board, a fire icon would light up. Hovering the mouse over the icon displays the total fire count on board.
;Active Debuffs
: If there are at least one active debuff on board, a orange number would show up on ship status board. Hovering over the number would display where and what are the debuffs on board.
;Destroyed components
: If there is at least one destroyed component, a red number will show up on ship status board. Hovering over the number would display what components are destroyed.
;Catastrophic Event
: If there is a catastrophic event on board, a red exclamation icon and a timer counting down would be displayed to the right of the corresponding ship's status board. If there is more than 1 event on board, only the shortest timer would be displayed. If the count down reaches zero, usually a big bang would take place.

== Debuffs/Catastrophic Events ==

Components can suffer various types of Critical Events (aka debuffs) in game, some would slow down the work speed of your damage control team, while others may degrade your ship's performance, or even obliterate your ship entirely.

Damage has a chance of causing debuffs on components. This chance is calculated by <math>\exp\left( -3Hp-0.5\right)\times C</math> where <math>Hp</math> is the current Hp percentage as a decimal and <math>C</math> is the critical event multiplier of the damage. This means baseline debuff chance for damage with 1x critical event multiplier starts at &sim;3% and increases to &sim;60% as the component takes damage.

This crit then has a chance of being a catastrophic based on the component's Catastrophic event probability.

The time to repair a debuff is determined by the repair speed of the DC team and the repair work required

=== Debuffs list ===
{| class="wikitable sortable"
|+ Debuffs effects list
|-
! In game name !! Internal name !! Stat Affected !! Modifier !! RepairWork
|-
| Atmosphere Leak || Atmosphere Leak || component-workspeed || -50% || 10
|-
| Fire || Fire || component-workspeed || -20% || 10
|-
| Fuel Line Fire || Fuel Line Fire || component-workspeed || -20% || 40
|-
| Magazine Cookoff || Magazine Cookoff || component-workspeed || -20% || 30
|-
| Reactor Overload || Reactor Overload || powerplant-prodefficiency || +25% || 65
|-
| Main Bus Short || Main Bus Short || powerplant-prodefficiency || -50% || 30
|-
| Cell Cookoff || Cell Launcher Cookoff || component-workspeed || -20% || 30
|-
| Container Bank Cookoff || Container Bank Cookoff || component-workspeed || -20% || 60
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || discreteweapon-reload, discreteweapon-recycle || +75%, +75% || 10
|-
| FC Waveguide Bent || FC Waveguide Bent || sensor-power || -50% || 10
|-
| Gyroscope Drift || Gyro Drift || muzzle-accuracy (spread) || +75% || 10
|-
| Heatsink Ruptured || Heatsink Ruptured || continuousweapon-cooldown, continuousweapon-overheatdamageprob|| +75%, +90% || 15
|-
| Antenna Bent || Sensor Antenna Bent || sensor-gain || -50% || 10
|-
| Antenna Bent || Sensor Oscillator Drift || sensor-maxposerror, sensor-maxvelerror || +100%, +100% || 10
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| turret-traverse, turret-elevate (rotation speed) || -80%, -80%|| 20
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| continuousweapon-directdamagemultiplier || -66% || 15
|}

* component-workspeed affects the repair speed of the DC teams inside the component; penalty cannot reduce workspeed below 33%
* There are two types of Antenna Bent, and while they have different internal names, in-game there's no way to tell which type of debuff is in effect.

{| class="wikitable sortable"
|+ Casualty class determines the voicelines that play when the debuff is incurred
|-
! In game name !! Internal name !! Affected class !! Required Condition !! Casualty class !! On-hitOnly !! Rare (catastrophic)
|-
| Atmosphere Leak || Atmosphere Leak || CrewedComponent || none || Decompression || TRUE || FALSE
|-
| Fire || Fire || HullComponent || none || Fire || FALSE || FALSE
|-
| Fuel Line Fire || Fuel Line Fire || DriveComponent || none || Fire || TRUE || TRUE
|-
| Magazine Cookoff || Magazine Cookoff || BulkMagazineComponent<ref>BulkMagazineComponents include all types of magazines, including reinforced and citadel magazines.</ref> || ContainsAnyAmmo || Fire || TRUE || TRUE
|-
| Reactor Overload || Reactor Overload || PowerplantComponent || none || Engineering || FALSE || TRUE
|-
| Main Bus Short || Main Bus Short || PowerplantComponent || none || Engineering || FALSE || FALSE
|-
| Cell Cookoff || Cell Launcher Cookoff || BaseCellLauncherComponent || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Container Bank Cookoff || Container Bank Cookoff || Container Bank<ref>Container bank cookoffs do not have an explicit affected class, but container banks have container bank cookoffs set as a unique debuff. it is unknown if container bank cookoffs can also suffer regular cell cookoffs or if it's overwritten. Magazine cookoff and cell cookoff can block eachother as they have identical keys, but container cookoff appears to have a different key. Additionally, unique debuffs are only added after the regular debuffs, which means container banks likely has a different key as otherwise the regular cell cookoff would block it.</ref> || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || DiscreteWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| FC Waveguide Bent || FC Waveguide Bent || WeaponComponent || HasIntegratedFC || CombatSystems || FALSE || FALSE
|-
| Gyroscope Drift || Gyro Drift || WeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Heatsink Ruptured || Heatsink Ruptured || ContinuousWeaponComponent || HasCooldown || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Antenna Bent || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Oscillator Drift || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| TurretedDiscreteWeaponComponent, FixedDiscreteWeaponComponent, TurretedContinuousWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| Beams<ref>Similar to container bank cookoffs. Is explicitly defined in both the spinal beam and beam turret.</ref> || none || CombatSystems || FALSE || FALSE
|}

[[File:ComponentClassInheritance.png|alt=Component Class Hierarchy|Component class hierarchy. Child classes inherit the crits of their parents.]]

==== Fire ====
Fires deal damage over time and can spread to different components
Every 30 seconds, fires deal 5% of the component's max HP as damage (ignores DR), with 10% crew vulnerability modifier
Every 45 seconds, fires have a 25% chance to spread to a component within 12.5m

A few other debuffs will also deal damage like fire, but will not spread. This includes Cookoffs and Reactor Overloads

=== Rare Debuffs/Catastrophic Events ===
There are currently 3 types of catastrophic events in game. ''Reactor Overload'', ''Fuel Line Fire'', and ''Magazine Cookoff''.

==== Reactor Overload ====
Reactor Overload is a event that would require immediate intervention of the damage control team to prevent a devastating explosion. If 65 points of repair work is not completed within 120 seconds, the reactor detonates in a gigantic explosion that completely destroys ship, and shreds a significant amount of armor off other nearby ships caught within the 1.5km explosion radius. The explosion also creates very strong radar jamming effect in all directions that is strong enough to break bullseye locks.

Reactor Overload explosions have a blast radius of 1.5km, dealing less damage against ships at the edge of the radius. The explosion shreds 200cm-20cm of armor, and if it fully shreds armor, will deal 1500 - 450 damage spread across the ship. Reactor overloads are guarenteed to hit every munition (missiles, mines, etc) in radius.

The jamming effect has a maximum range of 7.5km, 2500kw, 1dB gain, and lasts for 20 seconds.

===== Emergency reactor shutdown =====
Emergency reactor shutdowns can be initiated by the player to clear reactor overloads. They will stop all power and propulsion on the ship for 60 seconds.

30 seconds into the shutdown, all reactor overloads will be cleared, and any component that had an overload will be destroyed.

Note that shutdown is only effective on overloads, and will not stop fuel fires or cookoffs.

==== Fuel Line Fires ====
Fuel Line fires can appear on drives or reactors. If 40 points of repair work is not completed within 100 seconds, it will cause multiple small purple explosions to erupt across the ship, dealing heavy damage across the ship

it specifically causes 2 to 4 explosions per 5 meters of ship length, rounded up,<ref>More specifically, it looks at how long the ship's bounding radius is, and then multiplies that by a random float between 2-4</ref> eg a sprinter will only suffer 8-16 explosions, but a solomon will suffer 29-58 explosions.

Each explosion appears in a random position inside the hull and deals 200 damage in a 15m radius, shreds armor in a 60m radius. Explosions happen every 0.2-0.5 secs until the amount of explosions are reached.

==== Magazine/Cell Cookoff ====
Magazine/Cell Cookoffs can appear on magazines and VLS cells. If 30 points of repair work is not completed within 80 seconds, it will create a large explosion inside the ship, dealing massive damage to the area around magazine (3000 damage spread among components within 50m, shreds armor in 60m radius)
When a Magazine Cook-off is in progress, you can hear crackling sound effects in the vicinity of the ship.

Container bank cookoffs require 65pts of repair work within 120 seconds instead, and deals 15000 damage spread among components within 75m, and shreds armor within 100m.

== Damage Control Board ==
The Damage Control Board is displayed at the bottom right of the screen, whenever a ship is selected. It shows the ship's silhouette with colored boxes depicting the ships components. The color of the box indicates the component's health: bright green(high health), yellow(medium health), red(low health) and grey(destroyed).<ref>These colors are for the default color settings. Colorblindness settings will change the colors.</ref>

Aside from the ship's abstract, a couple of numbers are shown on the top of DC Board.
=== DMG ===
DMG shows how many components on ship is damaged or destroyed, individual thrusters and integrated antennas are also included.
=== TMS ===
TMS shows how many damage control teams are still operational, and how many are working. For example, for a indication of 1/2, it means 1 of the 2 teams are currently assigned with tasks.
=== RES ===
RES shows how many available restores do you have on ship. DC lockers that are destroyed with restores in them would not contribute to this number. However, it is feasible to spend 1 restore to repair a destroyed [[component:large-dc-locker|Large DC Locker]] with 2 restores in it, to get 1 additional restore back. This is often referred to as ''chain restoring''.
Restore would only be conducted if the player explicitly commanded this operation by Shift+LClicking a destroyed component, this would add a purple dotted outline over the component.

=== Prioritize ===
Player can prioritize the repair of a non-destroyed component by Shift+LClicking it, this is indicated by a blue dotted outline around the component.
=== Filtering ===
When the DC Board is expanded, there is a filter provided at the top left of the board. Player may select/deselect different categories to reduce clutter on the DC Board.

== DC Components ==
There are currently 3 types of DC-related components.

=== DC Lockers ===
Each DC lockers provide you with certain numbers of DC Teams and Restores.

{| class="wikitable"
|-
!rowspan="2"|DC Locker Type !!rowspan="2"|DC Teams !! Repair Rate !!rowspan="2"|Movement Speed !!rowspan="2"|Restores
|-
! General !! Restore !! Firefighting !! Reactor Overload
|-
| [[component:small-dc-locker|Small DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:reinforced-dc-locker|Reinforced DC Locker]] || 2 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 1
|-
| [[component:large-dc-locker|Large DC Locker]] || 3 || 0.2 || 0.2 || 0.2 || 0.2 || 0.5 || 2
|-
| [[component:rapid-dc-locker|Rapid DC Locker]] || 1 || 0.3 || 0 || 0.3 || 0.3 || 1 || 0
|}

=== DC Buffing Components ===

{| class="wikitable"
|-
! Component !! Repair Speed !! Move Speed
|-
| [[component:small-workshop|Small Workshop]] || 30% || N/A
|-
| [[component:damage-control-central|Damage Control Central]] || 10% || 50%
|}

=== Safety Components ===

{| class="wikitable"
|-
| [[component:launcher-deluge-system|Launcher Deluge System:]] || Catastrophic Event Prob. (Cell launcher): -50%
|-
| [[component:magazine-sprinklers|Magazine Sprinklers:]] || Catastrophic Event Prob. (Magazine): -50%
|-
| [[component:redundant-reactor-failsafes| Redundant Reactor Failsafes:]] || Catastrophic Event Prob. (Reactor): -33%
|-
| [[component:reinforced-thruster-nozzles| Reinforced Thruster Nozzles:]] || Flank Damage Probability: -20%
|}

==Notes==
<references />

Component Damage

2024-10-22T12:13:59Z

76561198801434526: /* Interior Density and Penetration Depth */ updated total armor equivalent for solomon

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
Each Component inside a ship has its own health pool. When [[Armor |armor]] has been penetrated, damage is dealt to components depending on direction of hit and the component's position in the ship.

== Damage Mechanics ==
Most attacks will cast some kind of ray or sphere colliders (aka hitboxes) through the ship (some attacks even cast multiple colliders). This collider will damage components, though the specifics vary depending on damage type

Components that are damaged below 0 HP will be destroyed (greyed out), and cannot be repaired unless a restore is used. However, there are two exceptions: Damage Threshold, and (Reinforced).

==== Damage Threshold ====

In order to destroy a component, the final "killing" hit has to deal more damage than the Damage Threshold (DT). If not, the component is brought down to 0 HP and disabled (shows as red), but is not destroyed, and therefore can be repaired without needing restores. This is checked after Damage Reduction (DR) is applied, which can make DT much more effective on ships with high DR.

==== Reinforced ====
A reinforced component can only be killed once it's at 0 HP. Any hit when the component is above 0 HP will only bring it down to 0 HP
This means that a reinforced component with a DC team repairing it ''must'' be hit twice within the 0.25 second window between repair ticks or else the DC team will bring the component above 0 HP
(Note that DC teams inside nearly destroyed modules are very vulnerable to damage and can be killed quickly)

The two hits do not have to be the same; any hit that brings the component down to 0 HP will count for the first hit, regardless of how little damage it deals or if it beats the component's DT. However, the second "greying" hit will have to beat DT as usual

Note that the reinforced tag is only "stripped" in the next frame, two hits in the same frame will both be resisted by reinforced, but if the second hit is spaced a moment afterwards, it will break through as expected.

==== Damage Reduction ====
A Hull's Damage Reduction stat reduces incoming damage by the percentage shown. For example, 40% DR will reduce 100 damage to 60 damage.

This modifier applies before damage threshold checks, and therefore massively amplifies the protective effect of Damage Threshold, especially against smaller munitions.

DR begins increasing once 20% of the component slots are filled, and maximizes when 60% of the component slots are filled. Slot size does not matter, only the number of slots filled. Damage Reduction does not change as modules are destroyed.

Damage reduction does not affect fire, bshort, or burnthrough damage. Some weapons ignore DR.

=== Interior Density and Penetration Depth ===

Just like real life ships, all ships in Nebulous also have internal structural bulkheads to provide redundancy against threats in space. In game, internal hull structure is generalized as a homogeneous interior density (Interior Armor Density Equivalent) measured in cm of armor per meter, with different hull classes having different densities. Some damage types use internal density to determine pendepth (see damage type section below). For example, if HEKP hits a Solomon and has 180cm of pen left over after penetrating armor, the Solomon's 1.2cm/m density means the penetrator can go up to 150 meters into the hull.

{| class="wikitable sortable"
|+ Interior Armor Density Equivalent of the Hulls
|-
! ANS Hull !! Interior Density (cm/m) !! Size (Length/Width/Height) !! Total Armor Equivalent (Front/Side/Top) !! Internal Armor Equivalent (F/S/T)
|-
| Sprinter || 0.5 || 80/37/28m || 56/35/30cm || 40/19/14cm
|-
| Raines || 0.5 || 96/35/40m || 78/48/50cm || 48/18/20cm
|-
| Keystone || 0.5 || 130/50/45m || 109/69/67cm || 65/25/23cm
|-
| Vauxhall || 1.00 || 215/62/60m || 275/122/120cm || 215/62/60cm
|-
| Axford || 1.20 || 195/70/75m || 314/164/170cm || 234/84/90cm
|-
| Solomon || 1.20 || 285/80/105m || 454/208/238cm || 342/96/126cm
|-
! OSP Hull !! Interior Density (cm/m) !! Size (L/W/H) !! Total Armor Equivalent (F/S/T) !! Internal Armor Equivalent (F/S/T)
|-
| Ferryman || 0.5 || 68/36/23m || 44/28/22cm || 34/18/12cm
|-
| Draugr || 0.5 || 87/53/40m || 54/37/30cm || 44/27/20cm
|-
| Flathead || 0.75 || 128/56/52m || 216/162/159cm || 96/42/39cm
|-
| Ocello || 1.2 || 210/50/75m || 312/120/150cm || 252/60/90cm
|-
| Marauder || 0.25 || 309/90/115m<ref name="lnsize">Lineships have variable dimensions due to their randomized layouts, and therefore the interior armor density stats are not accurate for all layouts.</ref> || 118/63/69cm<ref name="lnsize" /> || 78/23/29cm<ref name="lnsize" />
|-
| Moorline || 0.25 || 345/100/110m<ref name="lnsize" /> || 127/65/68cm<ref name="lnsize" /> || 87/25/28cm<ref name="lnsize" />
|}

Most damage types have a minimum pendepth of 15m. Even if the leftover penetration is 1cm, as long as it penetrates armor it will penetrate to 15m deep

Some damage types have conditions that can stop the attack early or limit penetration depth, even if it would normally penetrate deeper.

Some shells have a "Penetration Depth Override"<ref>Listed as _overrideComponentSearchDistance internally</ref>; These shells only use pendepth for calculating overpen, and if the shell does not overpen, the shell's pendepth is guarenteed to reach the override distance. This override is not usually limited by anything, and is applied after the overpen check which means the override cannot cause an overpen on its own.

=== Overpenetration ===
Shells that penetrate [[armor |armor]] and don't stop inside the hull due to fuzing, internal density, or armor at the exit point, will overpenetrate (overpen) and usually deal reduced damage against the ship (determined by the shell's overpenetration modifier). Most shell types also have reduced damage and different damage behaviors when overpenetrating.

A shell that overpenetrates can continue on and hit other targets, but some of it's armor penetration will be "used up" and the shell will have reduced penetration. e.g. a shell with 110cm pen hitting a ship with 15cm armor will use up 30cm (ignoring angling and internal density) and after overpenetrating will only have 80cm pen against the next target.

In some cases, the overpenetration vfx will play, but the shell will not exit the ship. In this case the hit is still treated as an overpenetrating hit even if the shell doesn't visibly exit.

Most other attacks besides shells don't overpenetrate. Some attack still make an overpenetration check for the purposes of vfx but this usually does not apply any explicit damage penalties and usually cannot damage further targets.

=== Structure break ===
<div style="float: right; width: 50%; padding: 20px">
[[File:PuppyNebulousStructurebreak.png|width="100%"|Structure boxes of the different hulls. Diagram by PuppyFromHell.]]

Structure boxes of the different hulls. Diagram by PuppyFromHell
</div>

All ships have a "Structure hitbox". if an attack hits this hitbox, and does not damage any components, the damage is dealt to the structure. Once enough damage has been dealt to the structure, the ship becomes structure broken, and any more damage to the structure is dealt to a random component instead. In this state, crew also take 50% more damage

<div style="clear: both"></div>
== Damage Type Overviews ==
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeShellBehavior.jpg|width="100%"|Behavior of AP and HE shells as they penetrate an Axford]]
Behavior of AP and HE shells as they penetrate an Axford. Not to scale. Diagram by smolcake.
</div>

=== HE (Shell) ===
HE shells create an explosion (sphere) inside the ship at a point along their path of travel. Any components that touch this sphere are damaged. The damage of the round is spread between all components equally. For example, a 150 damage shell will do 30 damage to 5 components or 75 damage to 2 components. If they overpen, the round does not create an explosion and the reduced damage is spread equally among all components that the round intersected with.

The explosion position is determined by the pendepth and the penetration envelope stat. Most HE shells have a penetration envelope of 0.8, which means they will detonate at some point between 80% and 100% of their pendepth.

=== AP (Shell) ===
AP shells damage the first non-destroyed component in their path; all subsequent components along it's pendepth are not damaged. If they overpen, the reduced damage is spread equally among all components that the round intersected with.

==== ''AP Sabot (Rail)'' ====
AP Sabot always spreads their damage across all components hit, dealing a certain fraction of damage to each component that falls off for each component hit, depending on the overpen multiplier. This applies even if the shot overpens.<ref>Technically, railguns are counted as always overpenetrating, which is how their damage type is changed from the standard AP shell to the unique type described.</ref>

e.g, a 300mm AP Rail Sabot with 80 damage and 50% overpen multiplier will deal 40 damage to the first component, 20 damage to the second, 10 damage to the third, etc

AP Sabot will always cause a critical event (crit) in a random component if they hit the structure hitbox, even if the ship is not structure-broken.

AP Sabot will never trigger catastrophic events (but the subsequent fires can cause catastrophics)

=== RPF (Shell) ===
RPF shells fire multiple fragmentations in a tight cone towards the nearest target (simulating the few fragments that would potentially threaten the target, out of the dozens of fragments). Each fragment acts like an AP shell, and totals up to the listed damage (eg, 250 RPF deals 16 damage per fragment, for a total of 128 damage).

Most RPF shells ignore normal penetration depth mechanics; if the fragment penetrates armor, they will always penetrate a certain depth into the hull regardless of interior density or leftover penetration.

RPF will also fuze on missiles, and has a 50% chance of damaging missiles within its blast radius (20 damage, 1.0cm pen, 50m fuze, 110m radius for 120mm RPF; 30 damage, 2.0cm pen, 60m fuze, 200m radius for 250mm RPF). This blast radius is purely antimissile and does not affect ships

RPF will trigger on terrain.

==== ''Bomb (Shell)'' ====
600mm bomb shells emit 12 fragments per target, each dealing 40 damage. The listed damage for 600mm Bomb shells assumes it hits 5 targets.

Bomb shells hit all ships within their blast radius (500m radius for 600mm bomb shells) with multiple fragments. These fragments are distributed randomly across the target's bounding radius. Or in other words, if you imagine a circle that circumscribes the ship, the 12 fragments fired at that ship will be distributed randomly inside that circle.

This can result in some fragments missing the ship, e.g. 600mm bomb shells will not always score 12 hits on every ship in its radius as ships do not fully encompass their bounding radius. In addition, these fragments can strike other targets inside the blast radius besides their intended target.

Bomb shells explode with a timed fuze. When firing on tracks, that timed fuze is stepped back by 0.5 seconds and will randomly vary ±0.33 seconds

Missiles within 300m of a bomb shell explosion have a 50% chance of being damaged for 30 damage, 2.0cm pen

=== Plasma ===

Plasma splits its damage across all components in its blast radius.

In addition to the main hit, plasma hits will also splash into 8 more splashrays upon impact, which array themselves in an approximate ring 7.5m away from the main impact location. These splashrays each have the same armor shredding and radius as the main hit, but deal no internal damage. Splashrays each shred armor separately, and can overlap in rare cases

Plasma armor shredding ignores armor angle. Both component damage and shredding falls off over distance, down to 30% at max range.

=== Beam ===
Beams deal damage five times a second, and therefore their damage per hit is 1/5 of the listed damage per second. Beams damage the first component in their path, have a fixed penetration depth of 150m (width of 6.66m), and cannot overpenetrate.

Beams deal reduced damage and armor penetration at longer ranges, reduced by 5% (x0.95) at half of max range, and reduced by 50% (x0.50) at max range.

''see also: [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/damage.html Puppy's beam damage tool]''

=== HEI (Missile) ===
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeHEKPHEIBehavior.jpg|width="100%"|Behavior of HEI and HEKP warheads on an Axford]]
Diagram of the behavior of HEI and HEKP warheads on an Axford. Not to scale. By smolcake.
</div>

HEI splits its damage into multiple fragments (aka rays), each dealing 50 dmg. The amount of fragments totals up to the listed damage value. e.g. a missile that has a listed damage of 1440 will split its damage into 28 fragments dealing 50 dmg, with one fragment left over dealing 40 dmg.

These fragments spray out in a 35 deg cone pattern from the impact location (note that the cone angles given on this page use internal values, and are therefore only half of the full angle). Each fragment splits their damage among all components in a 70m line (ignores pendepth mechanics), and do not overpenetrate. (e.g. the damage ray hitting two components will deal 25 damage to each, hitting three components will deal ~17 damage to each)

HEI warheads ignore armor angling.

For missiles, HE armor shredding radius gradually increases as warhead size increases. It starts at ~3.5m, goes to 5m at 1500 damage, 8m at 5000 damage.

Rockets function similarly, but with a slightly wider 45 deg cone and a variable ray length from 40m to 60m

==== ''HEI (Mine)'' ====
Works similarly to standard HEI, but the fragments deal 100 damage instead (times 50, for 5000 damage in total), with 100m-150m long rays, in a 50 degree cone.

<div style="clear: both"></div>

==== ''Mass driver/Fracturing block'' ====
OSP Fracturing blocks have a similar damage type compared to HEI, but instead deal only 15 damage per fragment, times 20 fragments, in a 35 deg cone. Fracturing block rays are emitted from the impact location, length of the rays is determined by penetration depth of the attack (for 500mm fracturing blocks, this is capped at 30m and has no penetration depth override). Fracturing block damage rays ignore damage reduction.

Fracturing blocks can visually overpenetrate, but this only allows the block to pass through the ship; overpenetration does not change the damage type of fracturing blocks and does not reduce the damage. Overpenetrating fracturing blocks will still deal the same damage and emit the same amount of rays on impact. As a side effect, the block itself also loses no damage after overpenning, which means if it hits a second target and penetrates, that target will also take full damage.

Unlike missile HEI, Mass drivers are affected by armor angling.

==== ''HE-SH (Shell)'' ====
600mm HE-SH works similarly to fracturing blocks. It applies 7× 60 damage rays, 50m maximum ray length, 15 deg cone. HE-SH cannot overpenetrate hulls.

=== HEKP (Missile) ===
<div style="float: right; width: 360px; padding: 20px;">
{| class="wikitable sortable"
|+ Minimum armor penetration that guarantees HEKP will hit 171.6m<ref>Not all ships are that long. Consult [[#Interior_Density_and_Penetration_Depth | the interior density and penetration depth table]]</ref> penetration depth against a given hull class, assuming their armor is at the maximum possible angle and is fresh.
|-
! ANS Hull !! Armor !! Internal Density (cm/m) !! HEKP Pen
|-
| Sprinter || 8cm || 0.50 || 106cm
|-
| Raines || 15cm || 0.50 || 124cm
|-
| Keystone || 22cm || 0.50 || 141cm
|-
| Vauxhall || 30cm || 1.00 || 247cm
|-
| Axford || 40cm || 1.20 || 306cm
|-
| Solomon || 56cm || 1.20 || 346cm
|-
! OSP Hull !! Armor !! Internal Density (cm/m) !! HEKP Pen
|-
| Ferryman || 5cm || 0.50|| 99cm
|-
| Draugr || 5cm || 0.50 || 99cm
|-
| Flathead || 48cm || 0.75 || 249cm
|-
| Ocello || 30cm || 1.20 || 281cm
|-
| Marauder || 20cm || 0.25 || 93cm
|-
| Moorline || 20cm || 0.25 || 93cm
|}
</div>

The HEKP penetrator is a spherical hitbox 10m wide and hits all components in a straight line up to 175m from the impact location. It spreads its listed damage equally among all hit components. The penetrator has a 2.0m armor shredding radius

The HEKP explosive creates a line of explosions along the path of the penetrator, and deals more overall damage as penetration depth increases, up to its listed maximum damage at 175m. HEKP does not suffer an explicit overpen penalty, but smaller hulls may not be large enough to allow the HEKP penetrator to travel 175m for maximum damage.

HEKP's explosion pattern is fixed, and broadly does not change regardless of warhead size, missile speed, or other factors. The HEKP Explosive splits its damage among 26 explosions<ref>The explosion count is not explicitly defined, rather the game derives the explosion count by dividing the maximum penetration depth by the distance between explosions. As a result, HEKP actually needs only 171.6m pendepth to reach the maximum explosion count</ref>. It tries to drop one explosion exactly every 6.6m (up to the maximum depth of 175m). If the explosive cannot drop all 26 explosions (either because the ship's hull is thinner than 175m, or the Penetrator did not travel 175m), then the damage in those explosions are lost. However, the total explosion damage will never go below 40%; The remaining explosions will have their damage scaled up to meet the 40% minimum.

Explosion count is rounded down; HEKP will create no explosions below 6.6m (but the penetrator can still damage components)

HEKP explosion radius varies throughout the explosion chain, peaking at ~25m radius at the 18th/19th explosion (~119m deep) and dropping off to ~7.5m radius near the beginning and end. Damage per explosion is the same for each explosion. Damage per explosion is distributed between components similarly to an HE shell. Armor shredding radius scales in a similar way, peaking at 6.0m (12m diameter in the best case) and dropping off to ~1.8m at the beginning and end. This is measured from the explosion point, not from the nearest surface.<ref>While in game HEKP is modeled as a line of explosions, this is intended to emulate the effect of a single large explosion moving through a confined environment at high speed, such as a supersonic missile impact: https://www.military.com/video/guided-missiles/antiship-missiles/russian-supersonic-missile-blows-away-vessel/4156566704001 </ref>

While the explosion damage and armor shredding value scales with warhead size, the shredding and damage radius are fixed regardless of warhead size
<div style="clear: both"></div>

=== Blast Frag (Missile) ===
<div style="float: right; width: 240px; padding: 20px;">
{| class="wikitable"
|+ Chance to hit based on angle of intercept.
|-
! Type !! Head-On !! Side !! Rear
|-
| BF || 50% || 20% || 80%
|-
| BF-EL || 85% || 65% || 95%
|}
</div>
Blast Frag detonates on the first enemy that comes within fuze range (regardless if it's the current target or not, as the fuze is seperate from the seeker), and has a chance of hitting against all missiles in its AoE. The fuze range is equal to the blast radius, with an upper limit of 50m. The fuze will trigger on everything, including other ships and terrain (But does not damage ships whatsoever, and will show up as a "miss" if it triggers on a ship)

Each missile within range of a blast frag detonation only has a chance of taking damage depending on the angle of intercept (based on the velocity vectors between the two missiles)<ref>This is calculated using the dot product between the normalized velocity vectors of the two missiles, which is effectively just calculating the cosine of the angle.</ref>. A blast frag missile hitting another missile head on has a moderate chance of dealing damage, a side-on hit has a low chance of damage, and a rear, or chasing hit, has the greatest chance of damage

<div style="clear: both"></div>

== External Links ==
* [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/damage.html Puppy's damage mechanics tool] - visualizes various hull damage mechanics (such as an armor penetration, beam damage falloff over distance with varying amounts of Focused Particle Accelerators)
* [https://docs.google.com/spreadsheets/d/1pB_kOSDFyLfL-RyihnDmyeRAJUCtBsbBT_H8eefH8u4/edit#gid=324047751 Puppy's All-in-one Calculator] - contains raw data on a variety of mechanics in Nebulous (Such as blast frag hit chances, flak AoE multipliers, HEKP explosion multiplers, etc)

== Notes ==
<references />

Modding/Save Keys

2024-10-22T12:11:57Z

76561198801434526: /* Compartments */ removed berthing and battle dressing station

== Save Keys ==

Save keys are strings the game uses to reference assets like ammo, hulls, and modules.
They are often used in scripts like those that copy VFX.

== Factions ==
Stock/Alliance 
Stock/Protectorate 

== Hulls ==

Stock/Sprinter Corvette 
Stock/Raines Frigate 
Stock/Keystone Destroyer 
Stock/Vauxhall Light Cruiser 
Stock/Axford Heavy Cruiser 
Stock/Solomon Battleship 
Stock/Shuttle 
Stock/Tugboat 
Stock/Bulk Feeder 
Stock/Ocello Cruiser 
Stock/Bulk Hauler 
Stock/Container Hauler 

== Common/Shared ==

=== Compartments ===
Stock/Basic CIC 
Stock/Reinforced CIC 
Stock/Citadel CIC 
Stock/Auxiliary Steering 
Stock/Small DC Locker 
Stock/Reinforced DC Locker 
Stock/Large DC Locker 
Stock/Rapid DC Locker 
Stock/Damage Control Central 
Stock/Small Workshop 
Stock/Bulk Magazine 
Stock/Reinforced Magazine 
Stock/Gun Plotting Center 
Stock/Analysis Annex 
Stock/Intelligence Center 
Stock/Plant Control Center 

=== Modules ===

Stock/Small Reactor Booster 
Stock/Adaptive Radar Receiver 
Stock/Track Correlator 
Stock/Strobe Correlator 
Stock/Mount Gyros 
Stock/Supplementary Radio Amplifiers 
Stock/Launcher Deluge System 
Stock/Magazine Sprinklers 
Stock/Redundant Reactor Failsafes 
Stock/Reinforced Thruster Nozzles 
Stock/Energy Regulator 
Stock/Small Energy Regulator 
Stock/Focused Particle Accelerator 
Stock/Ammunition Elevators 
Stock/Rapid-Cycle Cradle 
Stock/Actively Cooled Amplifiers 
Stock/Missile Programming Bus 
Stock/Missile Programming Bus Array 
Stock/Missile Parallel Interface 

=== Mounts ===
Stock/VLS-1-23 Launcher 
Stock/VLS-1-46 Launcher 
Stock/CR10 Antenna 

== Alliance ==

=== Compartments ===

Stock/Strike Planning Center 

=== Engineering Modules ===

Stock/FM200 Drive 
Stock/FM200R Drive 
Stock/FM230 'Whiplash' Drive 
Stock/FM240 'Dragonfly' Drive 
Stock/FM280 'Raider' Drive 
Stock/FM30X 'Prowler' Drive 
Stock/FM500 Drive 
Stock/FM500R Drive 
Stock/FM530 'Whiplash' Drive 
Stock/FM540 'Dragonfly' Drive 
Stock/FM580 'Raider' Drive 

Stock/FR3300 Micro Reactor 
Stock/FR4800 Reactor 

=== Sensors ===
Stock/RS35 'Frontline' Radar 
Stock/RS41 'Spyglass' Radar 
Stock/RM50 'Parallax' Radar 

=== Guns ===
Stock/Mk61 Cannon 
Stock/Mk62 Cannon 
Stock/Mk64 Cannon 
Stock/Mk65 Cannon 
Stock/Mk66 Cannon 
Stock/Mk68 Cannon 

Stock/Mk81 Railgun 
Stock/Mk550 Mass Driver 
Stock/Mk600 Beam Cannon 
Stock/Mk610 Beam Turret 

=== Missile Launchers ===
Stock/VLS-2 Launcher 
Stock/VLS-3 Launcher 
Stock/CLS-3 Launcher 

=== Point Defenses ===
Stock/Mk20 'Defender' PDT 
Stock/Mk25 'Rebound' PDT 
Stock/Mk29 'Stonewall' PDT 
Stock/Mk90 'Aurora' PDT 
Stock/Mk95 'Sarissa' PDT 

=== EWar ===
Stock/ES22 'Pinard' Electronic Support Module 
Stock/ES32 'Scryer' Missile ID System 
Stock/E55 'Spotlight' Illuminator 
Stock/E57 'Floodlight' Illuminator 
Stock/E71 'Hangup' Jammer 
Stock/E70 'Interruption' Jammer 
Stock/E90 'Blanket' Jammer 
Stock/RF101 'Bullseye' Radar 
Stock/E15 'Masquerade' Signature Booster 
Stock/Signature Scrambler 

=== Comms ===
Stock/CR70 Antenna 

== Protectorate ==
=== Engineering ===
Stock/Civilian Reactor 
Stock/Light Civilian Reactor 
Stock/Boosted Reactor 

Stock/Large DC Storage 

Stock/BW800 Drive 
Stock/BW800-R Drive 
Stock/BW1500 Drive 
Stock/BW1500-R Drive 
Stock/BW2000 Drive 
Stock/CHI-777 Yard Drive 
Stock/CHI-7700 Drive 
Stock/CHI-9100 Long Haul Drive 
Stock/Sundrive Racing Pro 

=== Sensors ===
Stock/Ithaca Bridgemaster 
Stock/Bulwark Huntress 
Stock/R550 Early Warning Radar 
Stock/R400 Radar 
Stock/RF44 'Pinpoint' Radar 

=== Turrets ===
Stock/T20 Cannon 
Stock/T30 Cannon 
Stock/T81 Plasma Cannon 

=== Fixed ===
Stock/C30 Cannon 
Stock/C53 Cannon 
Stock/C60 Cannon 
Stock/C65 Cannon 
Stock/C81 Plasma Cannon 
Stock/TE45 Mass Driver 

=== Point Defenses ===
Stock/P11 PDT 
Stock/P20 Flak PDT 
Stock/P60 Laser PDT 
=== EWar ===
Stock/L50 Laser Dazzler 
Stock/J15 Jammer 

Stock/J360 Jammer 
Stock/E20 'Lighthouse' Illuminator 

=== Missile Launchers ===
Stock/RL18 Launcher 
Stock/RL36 Launcher 
Stock/Container Bank Launcher 
Stock/Container Stack Launcher 
Stock/MLS-2 Launcher 
Stock/MLS-3 Launcher 
Stock/ML-9 Mine Launcher 

== Common Munitions ==

Stock/250mm HE Shell 
Stock/250mm AP Shell 
Stock/250mm HE-RPF Shell 
Stock/450mm HE Shell 
Stock/450mm AP Shell 
Stock/20mm Slug 
Stock/Flak Round 

== Alliance Munitions ==

=== Kinetic Ammo ===
Stock/120mm HE Shell 
Stock/120mm AP Shell 
Stock/120mm HE-RPF Shell 
Stock/15mm Sandshot 
Stock/300mm AP Rail Sabot 

=== Missiles ===
Stock/SGM-210 Squall 
Stock/SGM-225 Hurricane 
Stock/SGM-233 Gale 
Stock/SGT-350 Mace 
Stock/SDM-112 Riposte 
Stock/EA12 Chaff Decoy 
Stock/EA20 Flare Decoy 
Stock/EA99 Active Decoy 

== Protectorate Munitions ==

=== Kinetic Ammo ===
Stock/100mm HE Shell 
Stock/100mm HE-HC Shell 
Stock/100mm AP Shell 
Stock/100mm Grapeshot 
Stock/400mm Plasma Ampoule 
Stock/500mm Fracturing Block 

=== Missiles ===
Stock/S1 Rocket 
Stock/S3 Mine 
Stock/S3 Net Mine 
Stock/S3 Sprint Mine 
Stock/Mine Container 
Stock/Rocket Container 
Stock/Decoy Container (Clipper) 
Stock/Decoy Container (Line Ship) 

== Modular Missiles ==

=== Common ===
Stock/SGM-1 Body 
Stock/SGM-2 Body 
Stock/SGT-3 Body 

=== Alliance ===
Stock/SGM-H-2 Body 
Stock/SGM-H-3 Body 

=== Protectorate ===
Stock/CM-4 Body 

== Missile Components ==

=== Warheads ===
Stock/HE Impact 
Stock/HE Kinetic Penetrator 
Stock/Blast Fragmentation 
Stock/Blast Fragmentation EL 

=== Avionics ===
Stock/Direct Guidance 
Stock/Cruise Guidance 
Stock/Adv. Cruise Guidance 

=== Seekers ===
Stock/Command Receiver 
Stock/Fixed Active Radar Seeker 
Stock/Steerable Active Radar Seeker 
Stock/Steerable Extended Active Radar Seeker 
Stock/Fixed Semi-Active Radar Seeker 
Stock/Fixed Anti-Radiation Seeker 
Stock/Electro-Optical Seeker 
Stock/Wake-Homing Seeker 

=== Support ===
Stock/Cold Gas Bottle 
Stock/Decoy Launcher 
Stock/Cluster Decoy Launcher 
Stock/Fast Startup Module 
Stock/Hardened Skin 
Stock/Radar Absorbent Coating 
Stock/Self-Screening Jammer 
Stock/Boosted Self-Screening Jammer 

== Maps ==

Stock/Pillars 
Stock/The Cliff 
Stock/Nyx's Eye 
Stock/Caltrop 
Stock/Canyon 
Stock/Abyssal 
Stock/Small Testing Range 

== Manifest File ==
This is the manifest file used by the stock asset bundles.

<pre class="code">

<?xml version="1.0"?>
<BundleManifest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<BasePath>Assets/#BUNDLES/Stock</BasePath>
<Namespace>Stock</Namespace>

<ResourceFile>resources.xml</ResourceFile>

<Factions>
<Entry Name="Alliance" Address="F1/Faction Alliance.asset"/>
<Entry Name="Protectorate" Address="F2/Faction Protectorate.asset"/>
</Factions>

<Hulls>


<Entry Name="Sprinter Corvette" Address="F1/Hulls/Sprinter Corvette.prefab"/>
<Entry Name="Raines Frigate" Address="F1/Hulls/Raines Frigate.prefab"/>
<Entry Name="Keystone Destroyer" Address="F1/Hulls/Keystone Destroyer.prefab"/>
<Entry Name="Vauxhall Light Cruiser" Address="F1/Hulls/Vauxhall Light Cruiser.prefab"/>
<Entry Name="Axford Heavy Cruiser" Address="F1/Hulls/Axford Heavy Cruiser.prefab"/>
<Entry Name="Solomon Battleship" Address="F1/Hulls/Solomon Battleship.prefab"/>


<Entry Name="Shuttle" Address = "F2/Hulls/Shuttle Clipper.prefab"/>
<Entry Name="Tugboat" Address = "F2/Hulls/Tug Clipper.prefab"/>
<Entry Name="Bulk Feeder" Address = "F2/Hulls/Bulk Clipper.prefab"/>
<Entry Name="Ocello Cruiser" Address = "F2/Hulls/Ocello Cruiser.prefab"/>
<Entry Name="Bulk Hauler" Address = "F2/Hulls/Bulker Line Ship.prefab"/>
<Entry Name="Container Hauler" Address = "F2/Hulls/Container Line Ship.prefab"/>

</Hulls>

<Components>






<Entry Name="Basic CIC" Address="Common/Components/Basic CIC.prefab"/>
<Entry Name="Reinforced CIC" Address="Common/Components/Reinforced CIC.prefab"/>
<Entry Name="Citadel CIC" Address="Common/Components/Citadel CIC.prefab"/>
<Entry Name="Auxiliary Steering" Address="Common/Components/Auxiliary Steering.prefab"/>
<Entry Name="Berthing" Address="Common/Components/Berthing.prefab"/>
<Entry Name="Small DC Locker" Address="Common/Components/Small DC Locker.prefab"/>
<Entry Name="Reinforced DC Locker" Address="Common/Components/Reinforced DC Locker.prefab"/>
<Entry Name="Large DC Locker" Address="Common/Components/Large DC Locker.prefab"/>
<Entry Name="Rapid DC Locker" Address="Common/Components/Rapid DC Locker.prefab"/>
<Entry Name="Damage Control Central" Address="Common/Components/Damage Control Central.prefab"/>
<Entry Name="Small Workshop" Address="Common/Components/Small Workshop.prefab"/>
<Entry Name="Bulk Magazine" Address="Common/Components/Bulk Magazine.prefab"/>
<Entry Name="Reinforced Magazine" Address="Common/Components/Reinforced Magazine.prefab"/>
<Entry Name="Gun Plotting Center" Address="Common/Components/Gun Plotting Center.prefab"/>
<Entry Name="Battle Dressing Station" Address="Common/Components/Battle Dressing Station.prefab"/>
<Entry Name="Analysis Annex" Address="Common/Components/Analysis Annex.prefab"/>
<Entry Name="Intelligence Center" Address="Common/Components/Intelligence Center.prefab"/>
<Entry Name="Plant Control Center" Address="Common/Components/Plant Control Center.prefab"/>


<Entry Name="Small Reactor Booster" Address="Common/Components/Small Reactor Booster.prefab"/>
<Entry Name="Adaptive Radar Receiver" Address="Common/Components/Adaptive Radar Receiver.prefab"/>
<Entry Name="Track Correlator" Address="Common/Components/Track Correlator.prefab"/>
<Entry Name="Strobe Correlator" Address="Common/Components/Strobe Correlator.prefab"/>
<Entry Name="Mount Gyros" Address="Common/Components/Mount Gyros.prefab"/>
<Entry Name="Supplementary Radio Amplifiers" Address="Common/Components/Supplementary Radio Amplifiers.prefab"/>
<Entry Name="Launcher Deluge System" Address="Common/Components/Launcher Deluge System.prefab"/>
<Entry Name="Magazine Sprinklers" Address="Common/Components/Magazine Sprinklers.prefab"/>
<Entry Name="Redundant Reactor Failsafes" Address="Common/Components/Redundant Reactor Failsafes.prefab"/>
<Entry Name="Reinforced Thruster Nozzles" Address="Common/Components/Reinforced Thruster Nozzles.prefab"/>
<Entry Name="Energy Regulator" Address="Common/Components/Energy Regulator.prefab"/>
<Entry Name="Small Energy Regulator" Address="Common/Components/Small Energy Regulator.prefab"/>
<Entry Name="Focused Particle Accelerator" Address="Common/Components/Focused Particle Accelerator.prefab"/>
<Entry Name="Ammunition Elevators" Address="Common/Components/Ammunition Elevators.prefab"/>
<Entry Name="Rapid-Cycle Cradle" Address="Common/Components/Rapid-Cycle Cradle.prefab"/>
<Entry Name="Actively Cooled Amplifiers" Address="Common/Components/Actively Cooled Amplifiers.prefab"/>


<Entry Name="Missile Programming Bus" Address="Common/Components/Missile Programming Bus.prefab"/>
<Entry Name="Missile Programming Bus Array" Address="Common/Components/Missile Programming Bus Array.prefab"/>
<Entry Name="Missile Parallel Interface" Address="Common/Components/Missile Parallel Interface.prefab"/>


<Entry Name="VLS-1-23 Launcher" Address="F1/Weapons/VLS-1-23 Launcher.prefab"/>
<Entry Name="VLS-1-46 Launcher" Address="F1/Weapons/VLS-1-46 Launcher.prefab"/>


<Entry Name="CR10 Antenna" Address="Common/Components/CR10 Antenna.prefab"/>






<Entry Name="Strike Planning Center" Address="F1/Components/Strike Planning Center.prefab"/>


<Entry Name="FM200 Drive" Address="F1/Drives/FM200 Drive.prefab"/>
<Entry Name="FM200R Drive" Address="F1/Drives/FM200R Drive.prefab"/>
<Entry Name="FM230 'Whiplash' Drive" Address="F1/Drives/FM230 'Whiplash' Drive.prefab"/>
<Entry Name="FM240 'Dragonfly' Drive" Address="F1/Drives/FM240 'Dragonfly' Drive.prefab"/>
<Entry Name="FM280 'Raider' Drive" Address="F1/Drives/FM280 'Raider' Drive.prefab"/>
<Entry Name="FM30X 'Prowler' Drive" Address="F1/Drives/FM30X 'Prowler' Drive.prefab"/>
<Entry Name="FM500 Drive" Address="F1/Drives/FM500 Drive.prefab"/>
<Entry Name="FM500R Drive" Address="F1/Drives/FM500R Drive.prefab"/>
<Entry Name="FM530 'Whiplash' Drive" Address="F1/Drives/FM530 'Whiplash' Drive.prefab"/>
<Entry Name="FM540 'Dragonfly' Drive" Address="F1/Drives/FM540 'Dragonfly' Drive.prefab"/>
<Entry Name="FM580 'Raider' Drive" Address="F1/Drives/FM580 'Raider' Drive.prefab"/>

<Entry Name="FR3300 Micro Reactor" Address="F1/Components/FR3300 Micro Reactor.prefab"/>
<Entry Name="FR4800 Reactor" Address="F1/Components/FR4800 Reactor.prefab"/>


<Entry Name="RS35 'Frontline' Radar" Address="F1/Components/RS35 'Frontline' Radar.prefab"/>
<Entry Name="RS41 'Spyglass' Radar" Address="F1/Components/RS41 'Spyglass' Radar.prefab"/>
<Entry Name="RM50 'Parallax' Radar" Address="F1/Components/RM50 'Parallax' Radar.prefab"/>


<Entry Name="Mk61 Cannon" Address="F1/Weapons/Mk61 Cannon.prefab"/>
<Entry Name="Mk62 Cannon" Address="F1/Weapons/Mk62 Cannon.prefab"/>
<Entry Name="Mk64 Cannon" Address="F1/Weapons/Mk64 Cannon.prefab"/>
<Entry Name="Mk65 Cannon" Address="F1/Weapons/Mk65 Cannon.prefab"/>
<Entry Name="Mk66 Cannon" Address="F1/Weapons/Mk66 Cannon.prefab"/>
<Entry Name="Mk68 Cannon" Address="F1/Weapons/Mk68 Cannon.prefab"/>

<Entry Name="Mk81 Railgun" Address="F1/Weapons/Mk81 Railgun.prefab"/>

<Entry Name="Mk550 Mass Driver" Address="F1/Weapons/Mk550 Mass Driver.prefab"/>

<Entry Name="Mk600 Beam Cannon" Address="F1/Weapons/Mk600 Beam Cannon.prefab"/>
<Entry Name="Mk610 Beam Turret" Address="F1/Weapons/Mk610 Beam Turret.prefab"/>


<Entry Name="VLS-2 Launcher" Address="F1/Weapons/VLS-2 Launcher.prefab"/>
<Entry Name="VLS-3 Launcher" Address="F1/Weapons/VLS-3 Launcher.prefab"/>
<Entry Name="CLS-3 Launcher" Address="F1/Weapons/CLS-3 Launcher.prefab"/>


<Entry Name="Mk20 'Defender' PDT" Address="F1/Weapons/Mk20 'Defender' PDT.prefab"/>
<Entry Name="Mk25 'Rebound' PDT" Address="F1/Weapons/Mk25 'Rebound' PDT.prefab"/>
<Entry Name="Mk29 'Stonewall' PDT" Address="F1/Weapons/Mk29 'Stonewall' PDT.prefab"/>
<Entry Name="Mk90 'Aurora' PDT" Address="F1/Weapons/Mk90 'Aurora' PDT.prefab"/>
<Entry Name="Mk95 'Sarissa' PDT" Address="F1/Weapons/Mk95 'Sarissa' PDT.prefab"/>


<Entry Name="ES22 'Pinard' Electronic Support Module" Address="F1/Weapons/ES22 'Pinard' Electronic Support Module.prefab"/>
<Entry Name="ES32 'Scryer' Missile ID System" Address="F1/Components/ES32 'Scryer' Missile ID System.prefab"/>
<Entry Name="E55 'Spotlight' Illuminator" Address ="F1/Weapons/E55 'Spotlight' Illuminator.prefab"/>
<Entry Name="E57 'Floodlight' Illuminator" Address ="F1/Weapons/E57 'Floodlight' Illuminator.prefab"/>
<Entry Name="E71 'Hangup' Jammer" Address ="F1/Weapons/E71 'Hangup' Jammer.prefab"/>
<Entry Name="E70 'Interruption' Jammer" Address ="F1/Weapons/E70 'Interruption' Jammer.prefab"/>
<Entry Name="E90 'Blanket' Jammer" Address ="F1/Weapons/E90 'Blanket' Jammer.prefab"/>
<Entry Name="RF101 'Bullseye' Radar" Address ="F1/Weapons/RF101 'Bullseye' Radar.prefab"/>
<Entry Name="E15 'Masquerade' Signature Booster" Address ="F1/Weapons/E15 'Masquerade' Signature Booster.prefab"/>
<Entry Name="Signature Scrambler" Address ="F1/Components/Signature Scrambler.prefab"/>


<Entry Name="CR70 Antenna" Address="F1/Components/CR70 Antenna.prefab"/>






<Entry Name="Civilian Reactor" Address="F2/Components/Civilian Reactor.prefab"/>
<Entry Name="Light Civilian Reactor" Address="F2/Components/Light Civilian Reactor.prefab"/>
<Entry Name="Boosted Reactor" Address="F2/Components/Boosted Reactor.prefab"/>


<Entry Name="Large DC Storage" Address="F2/Components/Large DC Storage.prefab"/>

<Entry Name="BW800 Drive" Address="F2/Drives/BW800 Drive.prefab"/>
<Entry Name="BW800-R Drive" Address="F2/Drives/BW800-R Drive.prefab"/>
<Entry Name="BW1500 Drive" Address="F2/Drives/BW1500 Drive.prefab"/>
<Entry Name="BW1500-R Drive" Address="F2/Drives/BW1500-R Drive.prefab"/>
<Entry Name="BW2000 Drive" Address="F2/Drives/BW2000 Drive.prefab"/>
<Entry Name="CHI-777 Yard Drive" Address="F2/Drives/CHI-777 Yard Drive.prefab"/>
<Entry Name="CHI-7700 Drive" Address="F2/Drives/CHI-7700 Drive.prefab"/>
<Entry Name="CHI-9100 Long Haul Drive" Address="F2/Drives/CHI-9100 Long Haul Drive.prefab"/>
<Entry Name="Sundrive Racing Pro" Address="F2/Drives/Sundrive Racing Pro.prefab"/>


<Entry Name="Ithaca Bridgemaster" Address="F2/Components/Ithaca Bridgemaster.prefab"/>
<Entry Name="Bulwark Huntress" Address="F2/Components/Bulwark Huntress.prefab"/>
<Entry Name="R550 Early Warning Radar" Address="F2/Weapons/R550 Early Warning Radar.prefab"/>
<Entry Name="R400 Radar" Address="F2/Weapons/R400 'Bloodhound' LRT Radar.prefab"/>
<Entry Name="RF44 'Pinpoint' Radar" Address="F2/Weapons/RF44 'Pinpoint' Radar.prefab"/>


<Entry Name="T20 Cannon" Address="F2/Weapons/T20 Cannon.prefab"/>
<Entry Name="T30 Cannon" Address="F2/Weapons/T30 Cannon.prefab"/>
<Entry Name="T81 Plasma Cannon" Address="F2/Weapons/T81 Plasma Cannon.prefab"/>


<Entry Name="C30 Cannon" Address="F2/Weapons/C30 Cannon.prefab"/>
<Entry Name="C53 Cannon" Address="F2/Weapons/C53 Cannon.prefab"/>
<Entry Name="C60 Cannon" Address="F2/Weapons/C60 Cannon.prefab"/>
<Entry Name="C65 Cannon" Address="F2/Weapons/C65 Cannon.prefab"/>
<Entry Name="C81 Plasma Cannon" Address="F2/Weapons/C81 Plasma Cannon.prefab"/>
<Entry Name="TE45 Mass Driver" Address="F2/Weapons/TE45 Mass Driver.prefab"/>


<Entry Name="P11 PDT" Address="F2/Weapons/P11 'Pavise' PDT.prefab"/>
<Entry Name="P20 Flak PDT" Address="F2/Weapons/P20 'Bastion' PDT.prefab"/>
<Entry Name="P60 Laser PDT" Address="F2/Weapons/P60 'Grazer' PDT.prefab"/>


<Entry Name="L50 Laser Dazzler" Address="F2/Weapons/L50 'Blackjack' Laser Dazzler.prefab"/>
<Entry Name="J15 Jammer" Address="F2/Weapons/J15 'Bellbird' Jammer.prefab"/>

<Entry Name="J360 Jammer" Address="F2/Weapons/J360 'Lyrebird' Jammer.prefab"/>
<Entry Name="E20 'Lighthouse' Illuminator" Address="F2/Weapons/E20 'Lighthouse' Illuminator.prefab"/>



<Entry Name="RL18 Launcher" Address="F2/Weapons/RL18 Launcher.prefab"/>
<Entry Name="RL36 Launcher" Address="F2/Weapons/RL36 Launcher.prefab"/>
<Entry Name="Container Bank Launcher" Address="F2/Weapons/Container Bank Launcher.prefab"/>
<Entry Name="Container Stack Launcher" Address="F2/Weapons/Container Stack Launcher.prefab"/>
<Entry Name="MLS-2 Launcher" Address="F2/Weapons/MLS-2 Launcher.prefab"/>
<Entry Name="MLS-3 Launcher" Address="F2/Weapons/MLS-3 Launcher.prefab"/>
<Entry Name="ML-9 Mine Launcher" Address="F2/Weapons/ML-9 Mine Launcher.prefab"/>



</Components>

<Munitions>




<Entry Name="250mm HE Shell" Address="F1/Munitions/250mm HE Shell.asset"/>
<Entry Name="250mm AP Shell" Address="F1/Munitions/250mm AP Shell.asset"/>
<Entry Name="250mm HE-RPF Shell" Address="F1/Munitions/250mm HE-RPF Shell.asset"/>
<Entry Name="450mm HE Shell" Address="F1/Munitions/450mm HE Shell.asset"/>
<Entry Name="450mm AP Shell" Address="F1/Munitions/450mm AP Shell.asset"/>
<Entry Name="20mm Slug" Address="F1/Munitions/20mm Slug.asset"/>
<Entry Name="Flak Round" Address="F1/Munitions/Flak Round.asset"/>






<Entry Name="120mm HE Shell" Address="F1/Munitions/120mm HE Shell.asset"/>
<Entry Name="120mm AP Shell" Address="F1/Munitions/120mm AP Shell.asset"/>
<Entry Name="120mm HE-RPF Shell" Address="F1/Munitions/120mm HE-RPF Shell.asset"/>
<Entry Name="15mm Sandshot" Address="F1/Munitions/15mm Sandshot.asset"/>
<Entry Name="300mm AP Rail Sabot" Address="F1/Munitions/300mm AP Rail Sabot.asset"/>



<Entry Name="EA12 Chaff Decoy" Address="F1/Munitions/EA12 Chaff Decoy.prefab"/>
<Entry Name="EA20 Flare Decoy" Address="F1/Munitions/EA20 Flare Decoy.prefab"/>
<Entry Name="EA99 Active Decoy" Address="F1/Munitions/EA99 Active Decoy.prefab"/>








<Entry Name="100mm HE Shell" Address="F2/Munitions/100mm HE Shell.asset"/>
<Entry Name="100mm HE-HC Shell" Address="F2/Munitions/100mm HE-HC Shell.asset"/>
<Entry Name="100mm AP Shell" Address="F2/Munitions/100mm AP Shell.asset"/>
<Entry Name="100mm Grapeshot" Address="F2/Munitions/100mm Grape.asset"/>

<Entry Name="400mm Plasma Ampoule" Address="F2/Munitions/400mm Plasma Ampoule.asset"/>
<Entry Name="500mm Fracturing Block" Address="F2/Munitions/500mm Fracturing Block.asset"/>


<Entry Name="S1 Rocket" Address="F2/Munitions/R-2 'Piranha' Rocket.prefab"/>
<Entry Name="S3 Mine" Address="F2/Munitions/M-30 'Mattock' Mine.prefab"/>
<Entry Name="S3 Net Mine" Address="F2/Munitions/M-30-N 'Mattock' Cooperative Mine.prefab"/>
<Entry Name="S3 Sprint Mine" Address="F2/Munitions/M-50 'Auger' Sprint Mine.prefab"/>
<Entry Name="Mine Container" Address="F2/Munitions/CM-4M Mine Container.prefab"/>
<Entry Name="Rocket Container" Address="F2/Munitions/CM-4R Rocket Container.prefab"/>
<Entry Name="Decoy Container (Clipper)" Address="F2/Munitions/CM-4D1 Decoy Container (Clipper).prefab"/>
<Entry Name="Decoy Container (Line Ship)" Address="F2/Munitions/CM-4D2 Decoy Container (Line Ship).prefab"/>

</Munitions>

<MissileBodies>

<Entry Name="SGM-1 Body" Address="Common/Munitions/SGM-1/SGM-1 Body.prefab"/>
<Entry Name="SGM-2 Body" Address="Common/Munitions/SGM-2/SGM-2 Body.prefab"/>
<Entry Name="SGT-3 Body" Address="Common/Munitions/SGT-3/SGT-3 Body.prefab"/>


<Entry Name="SGM-H-2 Body" Address="F1/Munitions/SGM-H-2/SGM-H-2 Body.prefab"/>
<Entry Name="SGM-H-3 Body" Address="F1/Munitions/SGM-H-3/SGM-H-3 Body.prefab"/>


<Entry Name="CM-4 Body" Address="F2/Munitions/CM-4/CM-4 Body.prefab"/>
</MissileBodies>

<MissileComponents>


<Entry Name="HE Impact" Address="Common/Munitions/Missile Components/HE Impact.asset"/>
<Entry Name="HE Kinetic Penetrator" Address="Common/Munitions/Missile Components/HE Kinetic Penetrator.asset"/>
<Entry Name="Blast Fragmentation" Address="Common/Munitions/Missile Components/Blast Fragmentation.asset"/>
<Entry Name="Blast Fragmentation EL" Address="Common/Munitions/Missile Components/Blast Fragmentation EL.asset"/>


<Entry Name="Direct Guidance" Address="Common/Munitions/Missile Components/Direct Guidance.asset"/>
<Entry Name="Cruise Guidance" Address="Common/Munitions/Missile Components/Cruise Guidance.asset"/>



<Entry Name="Command Receiver" Address="Common/Munitions/Missile Components/Command Receiver.asset"/>
<Entry Name="Fixed Active Radar Seeker" Address="Common/Munitions/Missile Components/Fixed Active Radar Seeker.asset"/>
<Entry Name="Steerable Active Radar Seeker" Address="Common/Munitions/Missile Components/Steerable Active Radar Seeker.asset"/>
<Entry Name="Steerable Extended Active Radar Seeker" Address="Common/Munitions/Missile Components/Steerable Extended Active Radar Seeker.asset"/>
<Entry Name="Fixed Semi-Active Radar Seeker" Address="Common/Munitions/Missile Components/Fixed Semi-Active Radar Seeker.asset"/>
<Entry Name="Fixed Anti-Radiation Seeker" Address="Common/Munitions/Missile Components/Fixed Anti-Radiation Seeker.asset"/>
<Entry Name="Electro-Optical Seeker" Address="Common/Munitions/Missile Components/Electro-Optical Seeker.asset"/>
<Entry Name="Wake-Homing Seeker" Address="Common/Munitions/Missile Components/Wake-Homing Seeker.asset"/>


<Entry Name="Cold Gas Bottle" Address="Common/Munitions/Missile Components/Cold Gas Bottle.asset"/>
<Entry Name="Decoy Launcher" Address="Common/Munitions/Missile Components/Decoy Launcher.asset"/>
<Entry Name="Cluster Decoy Launcher" Address="Common/Munitions/Missile Components/Cluster Decoy Launcher.asset"/>
<Entry Name="Fast Startup Module" Address="Common/Munitions/Missile Components/Fast Startup Module.asset"/>
<Entry Name="Hardened Skin" Address="Common/Munitions/Missile Components/Hardened Skin.asset"/>
<Entry Name="Radar Absorbent Coating" Address="Common/Munitions/Missile Components/Radar Absorbent Coating.asset"/>
<Entry Name="Self-Screening Jammer" Address="Common/Munitions/Missile Components/Self-Screening Jammer.asset"/>
<Entry Name="Boosted Self-Screening Jammer" Address="Common/Munitions/Missile Components/Boosted Self-Screening Jammer.asset"/>

</MissileComponents>

<Maps>

<Entry Name="Pillars" Address="Maps/Pillars.prefab"/>

<Entry Name="The Cliff" Address="Maps/Cliff.prefab"/>
<Entry Name="Nyx's Eye" Address="Maps/Eye.prefab"/>
<Entry Name="Caltrop" Address = "Maps/Caltrop.prefab"/>
<Entry Name="Canyon" Address="Maps/Canyon.prefab"/>


<Entry Name="Abyssal" Address="Maps/Abyssal.prefab"/>
<Entry Name="Small Testing Range" Address="Maps/Shooting Gallery.prefab"/>


</Maps>

<Debuffs>

<Entry Address="Debuffs/Atmosphere Leak.asset"/>
<Entry Address="Debuffs/Fire.asset"/>

<Entry Address="Debuffs/Main Bus Short.asset"/>

<Entry Address="Debuffs/Sensor Antenna Bent.asset"/>
<Entry Address="Debuffs/Sensor Oscillator Drift.asset"/>


<Entry Address="Debuffs/Ammunition Loader Jammed.asset"/>
<Entry Address="Debuffs/Gyro Drift.asset"/>
<Entry Address="Debuffs/FC Waveguide Bent.asset"/>
<Entry Address="Debuffs/Heatsink Ruptured.asset"/>
<Entry Address="Debuffs/Turret Bearing Surface Bent.asset"/>


<Entry Address="Debuffs/Magazine Cookoff.asset"/>
<Entry Address="Debuffs/Cell Launcher Cookoff.asset"/>
<Entry Address="Debuffs/Reactor Overload.asset"/>
<Entry Address="Debuffs/Fuel Line Fire.asset"/>
<Entry Address="Debuffs/Container Bank Cookoff.asset"/>

</Debuffs>

<Voices>

<Entry Address="Voices/Marshall Voice.asset"/>
<Entry Address="Voices/Meccanismo Voice.asset"/>
<Entry Address="Voices/Jane Voice.asset"/>
<Entry Address="Voices/Griff Voice.asset"/>
<Entry Address="Voices/Delly Voice.asset"/>
<Entry Address="Voices/Solestine Voice.asset"/>
<Entry Address="Voices/Lauren Voice.asset"/>

</Voices>



<Scenarios>
<Entry Address="Scenarios/Control.asset"/>
<Entry Address="Scenarios/Deathmatch.asset"/>
<Entry Address="Scenarios/Station Capture.asset"/>
<Entry Address="Scenarios/Tug Of War.asset"/>
<Entry Address="Scenarios/Two Flags.asset"/>
<Entry Address="Scenarios/Center Flag.asset"/>
</Scenarios>

<TipLists>
<Entry Address="tips.txt"/>
</TipLists>

</BundleManifest>

</pre>

Component Damage

2024-10-22T12:09:15Z

76561198801434526: /* HEKP (Missile) */ updated BB armour and HEKP pendepth in the table

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
Each Component inside a ship has its own health pool. When [[Armor |armor]] has been penetrated, damage is dealt to components depending on direction of hit and the component's position in the ship.

== Damage Mechanics ==
Most attacks will cast some kind of ray or sphere colliders (aka hitboxes) through the ship (some attacks even cast multiple colliders). This collider will damage components, though the specifics vary depending on damage type

Components that are damaged below 0 HP will be destroyed (greyed out), and cannot be repaired unless a restore is used. However, there are two exceptions: Damage Threshold, and (Reinforced).

==== Damage Threshold ====

In order to destroy a component, the final "killing" hit has to deal more damage than the Damage Threshold (DT). If not, the component is brought down to 0 HP and disabled (shows as red), but is not destroyed, and therefore can be repaired without needing restores. This is checked after Damage Reduction (DR) is applied, which can make DT much more effective on ships with high DR.

==== Reinforced ====
A reinforced component can only be killed once it's at 0 HP. Any hit when the component is above 0 HP will only bring it down to 0 HP
This means that a reinforced component with a DC team repairing it ''must'' be hit twice within the 0.25 second window between repair ticks or else the DC team will bring the component above 0 HP
(Note that DC teams inside nearly destroyed modules are very vulnerable to damage and can be killed quickly)

The two hits do not have to be the same; any hit that brings the component down to 0 HP will count for the first hit, regardless of how little damage it deals or if it beats the component's DT. However, the second "greying" hit will have to beat DT as usual

Note that the reinforced tag is only "stripped" in the next frame, two hits in the same frame will both be resisted by reinforced, but if the second hit is spaced a moment afterwards, it will break through as expected.

==== Damage Reduction ====
A Hull's Damage Reduction stat reduces incoming damage by the percentage shown. For example, 40% DR will reduce 100 damage to 60 damage.

This modifier applies before damage threshold checks, and therefore massively amplifies the protective effect of Damage Threshold, especially against smaller munitions.

DR begins increasing once 20% of the component slots are filled, and maximizes when 60% of the component slots are filled. Slot size does not matter, only the number of slots filled. Damage Reduction does not change as modules are destroyed.

Damage reduction does not affect fire, bshort, or burnthrough damage. Some weapons ignore DR.

=== Interior Density and Penetration Depth ===

Just like real life ships, all ships in Nebulous also have internal structural bulkheads to provide redundancy against threats in space. In game, internal hull structure is generalized as a homogeneous interior density (Interior Armor Density Equivalent) measured in cm of armor per meter, with different hull classes having different densities. Some damage types use internal density to determine pendepth (see damage type section below). For example, if HEKP hits a Solomon and has 180cm of pen left over after penetrating armor, the Solomon's 1.2cm/m density means the penetrator can go up to 150 meters into the hull.

{| class="wikitable sortable"
|+ Interior Armor Density Equivalent of the Hulls
|-
! ANS Hull !! Interior Density (cm/m) !! Size (Length/Width/Height) !! Total Armor Equivalent (Front/Side/Top) !! Internal Armor Equivalent (F/S/T)
|-
| Sprinter || 0.5 || 80/37/28m || 56/35/30cm || 40/19/14cm
|-
| Raines || 0.5 || 96/35/40m || 78/48/50cm || 48/18/20cm
|-
| Keystone || 0.5 || 130/50/45m || 109/69/67cm || 65/25/23cm
|-
| Vauxhall || 1.00 || 215/62/60m || 275/122/120cm || 215/62/60cm
|-
| Axford || 1.20 || 195/70/75m || 314/164/170cm || 234/84/90cm
|-
| Solomon || 1.20 || 285/80/105m || 458/212/242cm || 342/96/126cm
|-
! OSP Hull !! Interior Density (cm/m) !! Size (L/W/H) !! Total Armor Equivalent (F/S/T) !! Internal Armor Equivalent (F/S/T)
|-
| Ferryman || 0.5 || 68/36/23m || 44/28/22cm || 34/18/12cm
|-
| Draugr || 0.5 || 87/53/40m || 54/37/30cm || 44/27/20cm
|-
| Flathead || 0.75 || 128/56/52m || 216/162/159cm || 96/42/39cm
|-
| Ocello || 1.2 || 210/50/75m || 312/120/150cm || 252/60/90cm
|-
| Marauder || 0.25 || 309/90/115m<ref name="lnsize">Lineships have variable dimensions due to their randomized layouts, and therefore the interior armor density stats are not accurate for all layouts.</ref> || 118/63/69cm<ref name="lnsize" /> || 78/23/29cm<ref name="lnsize" />
|-
| Moorline || 0.25 || 345/100/110m<ref name="lnsize" /> || 127/65/68cm<ref name="lnsize" /> || 87/25/28cm<ref name="lnsize" />
|}

Most damage types have a minimum pendepth of 15m. Even if the leftover penetration is 1cm, as long as it penetrates armor it will penetrate to 15m deep

Some damage types have conditions that can stop the attack early or limit penetration depth, even if it would normally penetrate deeper.

Some shells have a "Penetration Depth Override"<ref>Listed as _overrideComponentSearchDistance internally</ref>; These shells only use pendepth for calculating overpen, and if the shell does not overpen, the shell's pendepth is guarenteed to reach the override distance. This override is not usually limited by anything, and is applied after the overpen check which means the override cannot cause an overpen on its own.

=== Overpenetration ===
Shells that penetrate [[armor |armor]] and don't stop inside the hull due to fuzing, internal density, or armor at the exit point, will overpenetrate (overpen) and usually deal reduced damage against the ship (determined by the shell's overpenetration modifier). Most shell types also have reduced damage and different damage behaviors when overpenetrating.

A shell that overpenetrates can continue on and hit other targets, but some of it's armor penetration will be "used up" and the shell will have reduced penetration. e.g. a shell with 110cm pen hitting a ship with 15cm armor will use up 30cm (ignoring angling and internal density) and after overpenetrating will only have 80cm pen against the next target.

In some cases, the overpenetration vfx will play, but the shell will not exit the ship. In this case the hit is still treated as an overpenetrating hit even if the shell doesn't visibly exit.

Most other attacks besides shells don't overpenetrate. Some attack still make an overpenetration check for the purposes of vfx but this usually does not apply any explicit damage penalties and usually cannot damage further targets.

=== Structure break ===
<div style="float: right; width: 50%; padding: 20px">
[[File:PuppyNebulousStructurebreak.png|width="100%"|Structure boxes of the different hulls. Diagram by PuppyFromHell.]]

Structure boxes of the different hulls. Diagram by PuppyFromHell
</div>

All ships have a "Structure hitbox". if an attack hits this hitbox, and does not damage any components, the damage is dealt to the structure. Once enough damage has been dealt to the structure, the ship becomes structure broken, and any more damage to the structure is dealt to a random component instead. In this state, crew also take 50% more damage

<div style="clear: both"></div>
== Damage Type Overviews ==
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeShellBehavior.jpg|width="100%"|Behavior of AP and HE shells as they penetrate an Axford]]
Behavior of AP and HE shells as they penetrate an Axford. Not to scale. Diagram by smolcake.
</div>

=== HE (Shell) ===
HE shells create an explosion (sphere) inside the ship at a point along their path of travel. Any components that touch this sphere are damaged. The damage of the round is spread between all components equally. For example, a 150 damage shell will do 30 damage to 5 components or 75 damage to 2 components. If they overpen, the round does not create an explosion and the reduced damage is spread equally among all components that the round intersected with.

The explosion position is determined by the pendepth and the penetration envelope stat. Most HE shells have a penetration envelope of 0.8, which means they will detonate at some point between 80% and 100% of their pendepth.

=== AP (Shell) ===
AP shells damage the first non-destroyed component in their path; all subsequent components along it's pendepth are not damaged. If they overpen, the reduced damage is spread equally among all components that the round intersected with.

==== ''AP Sabot (Rail)'' ====
AP Sabot always spreads their damage across all components hit, dealing a certain fraction of damage to each component that falls off for each component hit, depending on the overpen multiplier. This applies even if the shot overpens.<ref>Technically, railguns are counted as always overpenetrating, which is how their damage type is changed from the standard AP shell to the unique type described.</ref>

e.g, a 300mm AP Rail Sabot with 80 damage and 50% overpen multiplier will deal 40 damage to the first component, 20 damage to the second, 10 damage to the third, etc

AP Sabot will always cause a critical event (crit) in a random component if they hit the structure hitbox, even if the ship is not structure-broken.

AP Sabot will never trigger catastrophic events (but the subsequent fires can cause catastrophics)

=== RPF (Shell) ===
RPF shells fire multiple fragmentations in a tight cone towards the nearest target (simulating the few fragments that would potentially threaten the target, out of the dozens of fragments). Each fragment acts like an AP shell, and totals up to the listed damage (eg, 250 RPF deals 16 damage per fragment, for a total of 128 damage).

Most RPF shells ignore normal penetration depth mechanics; if the fragment penetrates armor, they will always penetrate a certain depth into the hull regardless of interior density or leftover penetration.

RPF will also fuze on missiles, and has a 50% chance of damaging missiles within its blast radius (20 damage, 1.0cm pen, 50m fuze, 110m radius for 120mm RPF; 30 damage, 2.0cm pen, 60m fuze, 200m radius for 250mm RPF). This blast radius is purely antimissile and does not affect ships

RPF will trigger on terrain.

==== ''Bomb (Shell)'' ====
600mm bomb shells emit 12 fragments per target, each dealing 40 damage. The listed damage for 600mm Bomb shells assumes it hits 5 targets.

Bomb shells hit all ships within their blast radius (500m radius for 600mm bomb shells) with multiple fragments. These fragments are distributed randomly across the target's bounding radius. Or in other words, if you imagine a circle that circumscribes the ship, the 12 fragments fired at that ship will be distributed randomly inside that circle.

This can result in some fragments missing the ship, e.g. 600mm bomb shells will not always score 12 hits on every ship in its radius as ships do not fully encompass their bounding radius. In addition, these fragments can strike other targets inside the blast radius besides their intended target.

Bomb shells explode with a timed fuze. When firing on tracks, that timed fuze is stepped back by 0.5 seconds and will randomly vary ±0.33 seconds

Missiles within 300m of a bomb shell explosion have a 50% chance of being damaged for 30 damage, 2.0cm pen

=== Plasma ===

Plasma splits its damage across all components in its blast radius.

In addition to the main hit, plasma hits will also splash into 8 more splashrays upon impact, which array themselves in an approximate ring 7.5m away from the main impact location. These splashrays each have the same armor shredding and radius as the main hit, but deal no internal damage. Splashrays each shred armor separately, and can overlap in rare cases

Plasma armor shredding ignores armor angle. Both component damage and shredding falls off over distance, down to 30% at max range.

=== Beam ===
Beams deal damage five times a second, and therefore their damage per hit is 1/5 of the listed damage per second. Beams damage the first component in their path, have a fixed penetration depth of 150m (width of 6.66m), and cannot overpenetrate.

Beams deal reduced damage and armor penetration at longer ranges, reduced by 5% (x0.95) at half of max range, and reduced by 50% (x0.50) at max range.

''see also: [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/damage.html Puppy's beam damage tool]''

=== HEI (Missile) ===
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeHEKPHEIBehavior.jpg|width="100%"|Behavior of HEI and HEKP warheads on an Axford]]
Diagram of the behavior of HEI and HEKP warheads on an Axford. Not to scale. By smolcake.
</div>

HEI splits its damage into multiple fragments (aka rays), each dealing 50 dmg. The amount of fragments totals up to the listed damage value. e.g. a missile that has a listed damage of 1440 will split its damage into 28 fragments dealing 50 dmg, with one fragment left over dealing 40 dmg.

These fragments spray out in a 35 deg cone pattern from the impact location (note that the cone angles given on this page use internal values, and are therefore only half of the full angle). Each fragment splits their damage among all components in a 70m line (ignores pendepth mechanics), and do not overpenetrate. (e.g. the damage ray hitting two components will deal 25 damage to each, hitting three components will deal ~17 damage to each)

HEI warheads ignore armor angling.

For missiles, HE armor shredding radius gradually increases as warhead size increases. It starts at ~3.5m, goes to 5m at 1500 damage, 8m at 5000 damage.

Rockets function similarly, but with a slightly wider 45 deg cone and a variable ray length from 40m to 60m

==== ''HEI (Mine)'' ====
Works similarly to standard HEI, but the fragments deal 100 damage instead (times 50, for 5000 damage in total), with 100m-150m long rays, in a 50 degree cone.

<div style="clear: both"></div>

==== ''Mass driver/Fracturing block'' ====
OSP Fracturing blocks have a similar damage type compared to HEI, but instead deal only 15 damage per fragment, times 20 fragments, in a 35 deg cone. Fracturing block rays are emitted from the impact location, length of the rays is determined by penetration depth of the attack (for 500mm fracturing blocks, this is capped at 30m and has no penetration depth override). Fracturing block damage rays ignore damage reduction.

Fracturing blocks can visually overpenetrate, but this only allows the block to pass through the ship; overpenetration does not change the damage type of fracturing blocks and does not reduce the damage. Overpenetrating fracturing blocks will still deal the same damage and emit the same amount of rays on impact. As a side effect, the block itself also loses no damage after overpenning, which means if it hits a second target and penetrates, that target will also take full damage.

Unlike missile HEI, Mass drivers are affected by armor angling.

==== ''HE-SH (Shell)'' ====
600mm HE-SH works similarly to fracturing blocks. It applies 7× 60 damage rays, 50m maximum ray length, 15 deg cone. HE-SH cannot overpenetrate hulls.

=== HEKP (Missile) ===
<div style="float: right; width: 360px; padding: 20px;">
{| class="wikitable sortable"
|+ Minimum armor penetration that guarantees HEKP will hit 171.6m<ref>Not all ships are that long. Consult [[#Interior_Density_and_Penetration_Depth | the interior density and penetration depth table]]</ref> penetration depth against a given hull class, assuming their armor is at the maximum possible angle and is fresh.
|-
! ANS Hull !! Armor !! Internal Density (cm/m) !! HEKP Pen
|-
| Sprinter || 8cm || 0.50 || 106cm
|-
| Raines || 15cm || 0.50 || 124cm
|-
| Keystone || 22cm || 0.50 || 141cm
|-
| Vauxhall || 30cm || 1.00 || 247cm
|-
| Axford || 40cm || 1.20 || 306cm
|-
| Solomon || 56cm || 1.20 || 346cm
|-
! OSP Hull !! Armor !! Internal Density (cm/m) !! HEKP Pen
|-
| Ferryman || 5cm || 0.50|| 99cm
|-
| Draugr || 5cm || 0.50 || 99cm
|-
| Flathead || 48cm || 0.75 || 249cm
|-
| Ocello || 30cm || 1.20 || 281cm
|-
| Marauder || 20cm || 0.25 || 93cm
|-
| Moorline || 20cm || 0.25 || 93cm
|}
</div>

The HEKP penetrator is a spherical hitbox 10m wide and hits all components in a straight line up to 175m from the impact location. It spreads its listed damage equally among all hit components. The penetrator has a 2.0m armor shredding radius

The HEKP explosive creates a line of explosions along the path of the penetrator, and deals more overall damage as penetration depth increases, up to its listed maximum damage at 175m. HEKP does not suffer an explicit overpen penalty, but smaller hulls may not be large enough to allow the HEKP penetrator to travel 175m for maximum damage.

HEKP's explosion pattern is fixed, and broadly does not change regardless of warhead size, missile speed, or other factors. The HEKP Explosive splits its damage among 26 explosions<ref>The explosion count is not explicitly defined, rather the game derives the explosion count by dividing the maximum penetration depth by the distance between explosions. As a result, HEKP actually needs only 171.6m pendepth to reach the maximum explosion count</ref>. It tries to drop one explosion exactly every 6.6m (up to the maximum depth of 175m). If the explosive cannot drop all 26 explosions (either because the ship's hull is thinner than 175m, or the Penetrator did not travel 175m), then the damage in those explosions are lost. However, the total explosion damage will never go below 40%; The remaining explosions will have their damage scaled up to meet the 40% minimum.

Explosion count is rounded down; HEKP will create no explosions below 6.6m (but the penetrator can still damage components)

HEKP explosion radius varies throughout the explosion chain, peaking at ~25m radius at the 18th/19th explosion (~119m deep) and dropping off to ~7.5m radius near the beginning and end. Damage per explosion is the same for each explosion. Damage per explosion is distributed between components similarly to an HE shell. Armor shredding radius scales in a similar way, peaking at 6.0m (12m diameter in the best case) and dropping off to ~1.8m at the beginning and end. This is measured from the explosion point, not from the nearest surface.<ref>While in game HEKP is modeled as a line of explosions, this is intended to emulate the effect of a single large explosion moving through a confined environment at high speed, such as a supersonic missile impact: https://www.military.com/video/guided-missiles/antiship-missiles/russian-supersonic-missile-blows-away-vessel/4156566704001 </ref>

While the explosion damage and armor shredding value scales with warhead size, the shredding and damage radius are fixed regardless of warhead size
<div style="clear: both"></div>

=== Blast Frag (Missile) ===
<div style="float: right; width: 240px; padding: 20px;">
{| class="wikitable"
|+ Chance to hit based on angle of intercept.
|-
! Type !! Head-On !! Side !! Rear
|-
| BF || 50% || 20% || 80%
|-
| BF-EL || 85% || 65% || 95%
|}
</div>
Blast Frag detonates on the first enemy that comes within fuze range (regardless if it's the current target or not, as the fuze is seperate from the seeker), and has a chance of hitting against all missiles in its AoE. The fuze range is equal to the blast radius, with an upper limit of 50m. The fuze will trigger on everything, including other ships and terrain (But does not damage ships whatsoever, and will show up as a "miss" if it triggers on a ship)

Each missile within range of a blast frag detonation only has a chance of taking damage depending on the angle of intercept (based on the velocity vectors between the two missiles)<ref>This is calculated using the dot product between the normalized velocity vectors of the two missiles, which is effectively just calculating the cosine of the angle.</ref>. A blast frag missile hitting another missile head on has a moderate chance of dealing damage, a side-on hit has a low chance of damage, and a rear, or chasing hit, has the greatest chance of damage

<div style="clear: both"></div>

== External Links ==
* [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/damage.html Puppy's damage mechanics tool] - visualizes various hull damage mechanics (such as an armor penetration, beam damage falloff over distance with varying amounts of Focused Particle Accelerators)
* [https://docs.google.com/spreadsheets/d/1pB_kOSDFyLfL-RyihnDmyeRAJUCtBsbBT_H8eefH8u4/edit#gid=324047751 Puppy's All-in-one Calculator] - contains raw data on a variety of mechanics in Nebulous (Such as blast frag hit chances, flak AoE multipliers, HEKP explosion multiplers, etc)

== Notes ==
<references />

Damage Control

2024-08-25T00:19:24Z

76561198801434526: Made some of the debuff table sortable

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
Shooting weapons at hostiles is just one part of space combat, and the other part often involves taking shots. Sooner or later, your ship will catch on fire, have a leak, or have its internal components damaged beyond use.
And when that happens, your on-board damage control team will kick in and save your day.

<div style="clear: both"></div>
=== Definition of components ===
Everything on a ship is considered a component by damage control, no matter if it is a thruster, a compartment, a mount, or a module.
When a components receives damage, it will usually lose certain amounts of HP. This section explains the mechanics of component malfunction and repairs.
For detailed information on damage mechanics, see [[Component_Damage |Component Damage]].

==== Inoperable components ====
Most components have a hidden attribute called ''Functioning Threshold'', (aka Functioning Threshold). If a component's HP is reduced below this threshold, it will cease to function, and requires repairs to operate again.

=== Damage Control teams ===
Damaged components can be repaired. However, instead of repairing it back to 100%, your damage control teams can only repair a component to a certain percentage above its lowest condition percentage. This stat is known as the Max Repair stat (also colloquially known as repair cap); for most ships it starts at 10%. eg, if a component is damage down to 50% hp, repair teams on that ship will only be able to bring it back up to 60% hp

There is one an exception to this rule, a component can always be repaired to it's minimum functioning threshold hp + Max Repair, regardless of how much damage they take below the threshold. e.g. a Large Reinforced Drive (1500hp, 50hp minimum functioning) can always be repaired up to 200hp (50 from min function + 150 from 10% max repair), a Reinforced CIC (200hp, 10 minimum function threshold) can always be repaired up to 30hp (10 + 20)

Each component can only be repaired by three teams at once, one team for repairing HP and two teams for repairing debuffs. If there are no debuffs then only the one team will repair HP; and vice versa if there is no more hp to repair then only two teams will repair debuffs

Damage control teams tick once every 0.25 sec, applying the equivalent hp/sec as repair work. This is not modified by the amount of team members, a 1/5 team will repair at the same rate as a 5/5 team

Damage control teams speed in m/s is equal to <math>\text{movespeed}\times 2.5</math>. The stats on the wiki has already performed this conversion.

==== Damage Control priorities ====
Every ship has a damage control dispatcher that assigns DC teams to repair jobs and manages repair priorities.

<div style="float: right; margin-left: 20px; padding: 10px; border-style: solid; background-color:lightgray; width: 350px;">
DC dispatcher example list

Given a ship that has: 
- damaged drive (Critical prio) with atmo leak, fire, overload 
- damaged cic (high prio) 
- damaged magazine (med prio) with ammo cookoff 
- damaged DC locker (low prio) 

the lists will look something like this:

Primary: 
- Drive Overload 
- Drive Atmo leak 
- CIC hp 
- Magazine Ammo cookoff 

Secondary: 
-Drive HP 
-Magazine HP 
-DC locker HP 
</div>

The dispatcher has a primary and secondary repair job list. These lists are filled with repair jobs, which include both damaged components and debuffs (aka critical events) that need repair. Each Component adds their repair jobs to the lists according to the component's DC priority stat (normally a hidden stat), in the event of ties, components higher in the component list are prioritized and will add their debuffs to the list first.

Within each component, up to two debuffs events are added to the list. Catastrophics are prioritized first and always added to the primary list. Then, regular debuffs are added (up to the two debuff cap), starting from the top of the component's debuffs list as seen in the DC board. These debuffs are added to the primary list if the component is still alive, and added to the secondary list if destroyed (unless the component is manually prioritized). Then, the component adds its HP repair to the secondary list. If the component has no debuffs and has medium or higher DC priority, it instead adds its HP repair to the primary list

Using these lists, the DC team then assigns teams to the repair jobs in the list, satisfying all jobs in the primary list before filling secondary jobs

Damage control teams from DC lockers higher in the component list are tasked to jobs first. eg, DC teams from compartment 1's locker will be assigned to tasks before DC teams from compartment 2's locker, regardless of difference in team move speed, repair speed, or distance to damaged component. The only exception to this rule is if there is already a DC team in that component; it will be tasked to work on repairs immediately. However, this will not be performed for repair jobs in the secondary list, those jobs will summon another DC team even if there is an idle DC team in the same component.


==== Repair team casualties ====
Damage control teams themselves will only take losses if their current component is below 50% hp.
DC teams currently do not replenish, even if there is spare crew available
''see: [[Crew]]''

=== Restore ===
When a component loses all of its health, it becomes ''Destroyed''. In this state, the component can no longer be hit by any further damage (and is therefore treated as empty space by attacks), nor will it be automatically repaired by the control team. To bring it back online, you need to spend the ''Restores'' provided in DC Lockers. By Shift+LClicking a destroyed component, you can order a damage control team to preform a restore on the destroyed component. After the restore progress is completed, the component is instantly repaired to its minimum functioning HP plus its max repair. Restores require 50 "hp" worth of work to apply.

Restore usage seems to be distributed among the lockers, starting from the closest locker and working outward

== Ship Status Board ==
On the top left of the game screen, every ship has a ship status board that shows the ship's information. At the bottom right of the board, ship damage control status would be displayed.
;Fire Icon
: If there are at least one fire on board, a fire icon would light up. Hovering the mouse over the icon displays the total fire count on board.
;Active Debuffs
: If there are at least one active debuff on board, a orange number would show up on ship status board. Hovering over the number would display where and what are the debuffs on board.
;Destroyed components
: If there is at least one destroyed component, a red number will show up on ship status board. Hovering over the number would display what components are destroyed.
;Catastrophic Event
: If there is a catastrophic event on board, a red exclamation icon and a timer counting down would be displayed to the right of the corresponding ship's status board. If there is more than 1 event on board, only the shortest timer would be displayed. If the count down reaches zero, usually a big bang would take place.

== Debuffs/Catastrophic Events ==

Components can suffer various types of Critical Events (aka debuffs) in game, some would slow down the work speed of your damage control team, while others may degrade your ship's performance, or even obliterate your ship entirely.

Damage has a chance of causing debuffs on components. This chance is calculated by <math>\exp\left( -3Hp-0.5\right)\times C</math> where <math>Hp</math> is the current Hp percentage as a decimal and <math>C</math> is the critical event multiplier of the damage. This means baseline debuff chance for damage with 1x critical event multiplier starts at &sim;3% and increases to &sim;60% as the component takes damage.

This crit then has a chance of being a catastrophic based on the component's Catastrophic event probability.

The time to repair a debuff is determined by the repair speed of the DC team and the repair work required

=== Debuffs list ===
{| class="wikitable sortable"
|+ Debuffs effects list
|-
! In game name !! Internal name !! Stat Affected !! Modifier !! RepairWork
|-
| Atmosphere Leak || Atmosphere Leak || component-workspeed || -50% || 10
|-
| Fire || Fire || component-workspeed || -20% || 10
|-
| Fuel Line Fire || Fuel Line Fire || component-workspeed || -20% || 25
|-
| Magazine Cookoff || Magazine Cookoff || component-workspeed || -20% || 18
|-
| Reactor Overload || Reactor Overload || powerplant-prodefficiency || +25% || 65
|-
| Main Bus Short || Main Bus Short || powerplant-prodefficiency || -50% || 30
|-
| Cell Cookoff || Cell Launcher Cookoff || component-workspeed || -20% || 18
|-
| Container Bank Cookoff || Container Bank Cookoff || component-workspeed || -20% || 60
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || discreteweapon-reload, discreteweapon-recycle || +75%, +75% || 10
|-
| FC Waveguide Bent || FC Waveguide Bent || sensor-power || -50% || 10
|-
| Gyroscope Drift || Gyro Drift || muzzle-accuracy (spread) || +75% || 10
|-
| Heatsink Ruptured || Heatsink Ruptured || continuousweapon-cooldown, continuousweapon-overheatdamageprob|| +75%, +90% || 15
|-
| Antenna Bent || Sensor Antenna Bent || sensor-gain || -50% || 10
|-
| Antenna Bent || Sensor Oscillator Drift || sensor-maxposerror, sensor-maxvelerror || +100%, +100% || 10
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| turret-traverse, turret-elevate (rotation speed) || -80%, -80%|| 20
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| continuousweapon-directdamagemultiplier || -66% || 15
|}

* component-workspeed affects the repair speed of the DC teams inside the component; penalty cannot reduce workspeed below 33%
* There are two types of Antenna Bent, and while they have different internal names, in-game there's no way to tell which type of debuff is in effect.

{| class="wikitable sortable"
|+ Casualty class determines the voicelines that play when the debuff is incurred
|-
! In game name !! Internal name !! Affected class !! Required Condition !! Casualty class !! On-hitOnly !! Rare (catastrophic)
|-
| Atmosphere Leak || Atmosphere Leak || CrewedComponent || none || Decompression || TRUE || FALSE
|-
| Fire || Fire || HullComponent || none || Fire || FALSE || FALSE
|-
| Fuel Line Fire || Fuel Line Fire || DriveComponent || none || Fire || TRUE || TRUE
|-
| Magazine Cookoff || Magazine Cookoff || BulkMagazineComponent<ref>BulkMagazineComponents include all types of magazines, including reinforced and citadel magazines.</ref> || ContainsAnyAmmo || Fire || TRUE || TRUE
|-
| Reactor Overload || Reactor Overload || PowerplantComponent || none || Engineering || FALSE || TRUE
|-
| Main Bus Short || Main Bus Short || PowerplantComponent || none || Engineering || FALSE || FALSE
|-
| Cell Cookoff || Cell Launcher Cookoff || BaseCellLauncherComponent || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Container Bank Cookoff || Container Bank Cookoff || Container Bank<ref>Container bank cookoffs do not have an explicit affected class, but container banks have container bank cookoffs set as a unique debuff. it is unknown if container bank cookoffs can also suffer regular cell cookoffs or if it's overwritten. Magazine cookoff and cell cookoff can block eachother as they have identical keys, but container cookoff appears to have a different key. Additionally, unique debuffs are only added after the regular debuffs, which means container banks likely has a different key as otherwise the regular cell cookoff would block it.</ref> || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
|-
| Ammunition Loader Jammed || Ammunition Loader Jammed || DiscreteWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| FC Waveguide Bent || FC Waveguide Bent || WeaponComponent || HasIntegratedFC || CombatSystems || FALSE || FALSE
|-
| Gyroscope Drift || Gyro Drift || WeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Heatsink Ruptured || Heatsink Ruptured || ContinuousWeaponComponent || HasCooldown || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Antenna Bent || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Antenna Bent || Sensor Oscillator Drift || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
| Bearing Surface Bent || Turret Bearing Surface Bent|| TurretedDiscreteWeaponComponent, FixedDiscreteWeaponComponent, TurretedContinuousWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
| Focusing Element Misaligned|| Focusing Element Misaligned|| Beams<ref>Similar to container bank cookoffs. Is explicitly defined in both the spinal beam and beam turret.</ref> || none || CombatSystems || FALSE || FALSE
|}

[[File:ComponentClassInheritance.png|alt=Component Class Hierarchy|Component class hierarchy. Child classes inherit the crits of their parents.]]

==== Fire ====
Fires deal damage over time and can spread to different components
Every 30 seconds, fires deal 5% of the component's max HP as damage (ignores DR), with 10% crew vulnerability modifier
Every 45 seconds, fires have a 25% chance to spread to a component within 12.5m

A few other debuffs will also deal damage like fire, but will not spread. This includes Cookoffs and Reactor Overloads

=== Rare Debuffs/Catastrophic Events ===
There are currently 3 types of catastrophic events in game. ''Reactor Overload'', ''Fuel Line Fire'', and ''Magazine Cookoff''.

==== Reactor Overload ====
Reactor Overload is a event that would require immediate intervention of the damage control team to prevent a devastating explosion. If 65 points of repair work is not completed within 120 seconds, the reactor detonates in a gigantic explosion that completely destroys ship, and shreds a significant amount of armor off other nearby ships caught within the 1.5km explosion radius. The explosion also creates very strong radar jamming effect in all directions that is strong enough to break bullseye locks.

Reactor Overload explosions have a blast radius of 1.5km, dealing less damage against ships at the edge of the radius. The explosion shreds 200cm-20cm of armor, and if it fully shreds armor, will deal 1500 - 450 damage spread across the ship. Reactor overloads are guarenteed to hit every munition (missiles, mines, etc) in radius.

The jamming effect has a maximum range of 7.5km, 2500kw, 1dB gain, and lasts for 20 seconds.

===== Emergency reactor shutdown =====
Emergency reactor shutdowns can be initiated by the player to clear reactor overloads. They will stop all power and propulsion on the ship for 60 seconds.

30 seconds into the shutdown, all reactor overloads will be cleared, and any component that had an overload will be destroyed.

Note that shutdown is only effective on overloads, and will not stop fuel fires or cookoffs.

==== Fuel Line Fires ====
Fuel Line fires can appear on drives or reactors. If 25 points of repair work is not completed within 80 seconds, it will cause multiple small purple explosions to erupt across the ship, dealing heavy damage across the ship

it specifically causes 2 to 4 explosions per 5 meters of ship length, rounded up,<ref>More specifically, it looks at how long the ship's bounding radius is, and then multiplies that by a random float between 2-4</ref> eg a sprinter will only suffer 8-16 explosions, but a solomon will suffer 29-58 explosions.

Each explosion appears in a random position inside the hull and deals 200 damage in a 15m radius, shreds armor in a 60m radius. Explosions happen every 0.2-0.5 secs until the amount of explosions are reached.

==== Magazine/Cell Cookoff ====
Magazine/Cell Cookoffs can appear on magazines and VLS cells. If 18 points of repair work is not completed within 60 seconds, it will create a large explosion inside the ship, dealing massive damage to the area around magazine (3000 damage spread among components within 50m, shreds armor in 60m radius)
When a Magazine Cook-off is in progress, you can hear crackling sound effects in the vicinity of the ship.

Container bank cookoffs require 65pts of repair work within 120 seconds instead, and deals 15000 damage spread among components within 75m, and shreds armor within 100m.

== Damage Control Board ==
The Damage Control Board is displayed at the bottom right of the screen, whenever a ship is selected. It shows the ship's silhouette with colored boxes depicting the ships components. The color of the box indicates the component's health: bright green(high health), yellow(medium health), red(low health) and grey(destroyed).<ref>These colors are for the default color settings. Colorblindness settings will change the colors.</ref>

Aside from the ship's abstract, a couple of numbers are shown on the top of DC Board.
=== DMG ===
DMG shows how many components on ship is damaged or destroyed, individual thrusters and integrated antennas are also included.
=== TMS ===
TMS shows how many damage control teams are still operational, and how many are working. For example, for a indication of 1/2, it means 1 of the 2 teams are currently assigned with tasks.
=== RES ===
RES shows how many available restores do you have on ship. DC lockers that are destroyed with restores in them would not contribute to this number. However, it is feasible to spend 1 restore to repair a destroyed [[component:large-dc-locker|Large DC Locker]] with 2 restores in it, to get 1 additional restore back. This is often referred to as ''chain restoring''.
Restore would only be conducted if the player explicitly commanded this operation by Shift+LClicking a destroyed component, this would add a purple dotted outline over the component.

=== Prioritize ===
Player can prioritize the repair of a non-destroyed component by Shift+LClicking it, this is indicated by a blue dotted outline around the component.
=== Filtering ===
When the DC Board is expanded, there is a filter provided at the top left of the board. Player may select/deselect different categories to reduce clutter on the DC Board.

== DC Components ==
There are currently 3 types of DC-related components.

=== DC Lockers ===
Each DC lockers provide you with certain numbers of DC Teams and Restores.

{| class="wikitable"
|-
! DC Locker Type !! DC Teams !! Repair Rare !! Movement Speed !! Restores
|-
| [[component:small-dc-locker|Small DC Locker]] || 2 || 0.2 || 0.5 || 1
|-
| [[component:reinforced-dc-locker|Reinforced DC Locker]] || 2 || 0.2 || 0.5 || 1
|-
| [[component:large-dc-locker|Large DC Locker]] || 3 || 0.2 || 0.5 || 2
|-
| [[component:rapid-dc-locker|Rapid DC Locker]] || 1 || 0.3 || 1 || 0
|}

=== DC Buffing Components ===

{| class="wikitable"
|-
! Component !! Repair Speed !! Move Speed
|-
| [[component:small-workshop|Small Workshop]] || 30% || N/A
|-
| [[component:damage-control-central|Damage Control Central]] || 10% || 50%
|}

=== Safety Components ===

{| class="wikitable"
|-
| [[component:launcher-deluge-system|Launcher Deluge System:]] || Catastrophic Event Prob. (Cell launcher): -50%
|-
| [[component:magazine-sprinklers|Magazine Sprinklers:]] || Catastrophic Event Prob. (Magazine): -50%
|-
| [[component:redundant-reactor-failsafes| Redundant Reactor Failsafes:]] || Catastrophic Event Prob. (Reactor): -33%
|-
| [[component:reinforced-thruster-nozzles| Reinforced Thruster Nozzles:]] || Flank Damage Probability: -20%
|}

==Notes==
<references />

Ranks and XP

2024-06-23T15:14:26Z

76561198801434526: gramatical fix

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
As players play multiplayer matches in Nebulous, they gain experience (XP) which translates to certain ranks shown in game. These ranks have no influence on gameplay except as a rough indicator of multiplayer playtime.

<div style="clear: both"></div>
== XP ==
XP is gained via multiplayer games. Wins award 30 XP, losses and draws award 10 XP. XP is only awarded at the end of a match, so leaving early will deny any XP award.

There is currently no way to lose XP<ref>There is a function in game to deduct -50 or -60 XP if the player disconnects early, but it was dummied out as the dev couldn't find a satisfactory way to differentiate from a legitimate crash, or an intentional ALT+F4</ref>, any XP gained is permanent.

== Ranks ==
There are 11 ranks in Nebulous:
* Midshipman (MID) - 0 XP
* Ensign (ENS) - 100 XP
* Lieutenant Junior Grade (LTJG) - 500 XP
* Lieutenant (LT) - 1,200 XP
* Lieutenant Commander (LCDR) - 3,000 XP
* Commander (CMDR) - 6,500 XP
* Captain (CAPT) - 10,000 XP
* Commodore (CDRE) - 18,000 XP
* Rear Admiral (RADM) - 30,000 XP
* Vice Admiral (VADM) - 60,000 XP
* Grand Admiral (GADM) -120,000 XP

== Notes ==
<references />

Ranks and XP

2024-06-23T15:14:04Z

76561198801434526: created page

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
As players play multiplayer matches in Nebulous, they gain XP which translates to certain ranks shown in game. These ranks have no influence on gameplay except as a rough indicator of multiplayer playtime.

<div style="clear: both"></div>
== XP ==
XP is gained via multiplayer games. Wins award 30 XP, losses and draws award 10 XP. XP is only awarded at the end of a match, so leaving early will deny any XP award.

There is currently no way to lose XP<ref>There is a function in game to deduct -50 or -60 XP if the player disconnects early, but it was dummied out as the dev couldn't find a satisfactory way to differentiate from a legitimate crash, or an intentional ALT+F4</ref>, any XP gained is permanent.

== Ranks ==
There are 11 ranks in Nebulous:
* Midshipman (MID) - 0 XP
* Ensign (ENS) - 100 XP
* Lieutenant Junior Grade (LTJG) - 500 XP
* Lieutenant (LT) - 1,200 XP
* Lieutenant Commander (LCDR) - 3,000 XP
* Commander (CMDR) - 6,500 XP
* Captain (CAPT) - 10,000 XP
* Commodore (CDRE) - 18,000 XP
* Rear Admiral (RADM) - 30,000 XP
* Vice Admiral (VADM) - 60,000 XP
* Grand Admiral (GADM) -120,000 XP

== Notes ==
<references />

List of Maps

2024-06-23T15:09:02Z

76561198801434526: created page

<div style="float: left; padding-right: 20px;">
__TOC__
</div>

<div style="clear: both"></div>

== List of maps ==
{| class="wikitable"
|+ Vanilla Maps
|-
! Name !! Max Players
|-
| Caltrop || 8
|-
| Canyon || 10
|-
| Pillars || 8
|-
| Nyx's Eye || 10
|-
| Tumbleweed || 8
|-
| Cliff || 4
|-
| Abyssal || 8<ref Name="variable_players">Map is listed as a 4P map, but will allow 8 player games.</ref>
|-
| Small Testing Range<ref>Initial Formations are disabled for Small Testing Range.</ref> || 8<ref Name="variable_players">Map is listed as a 4P map, but will allow 8 player games.</ref>
|}

Note that although more than the above numbers of people can join a lobby, the host will be unable to start the game unless the map supports that number of people.

== Game modes ==
* Annihilation: Teams fight until all ships on a side are destroyed, or the timer runs out.
* Control: Teams must capture zones to win. Each friendly zone gives the team score points over time. The match ends when all ships on a side are destroyed, one team reaches the required number of points, or the timer runs out. Points only come from captured zones. Capture zones are 2km across and each zone gives 2pts every 10 seconds to the team that controls it
* Tug-of-War: Control, but when a team gains points, the enemy team loses the same number.
* Capture the Flag: Flags spawn on the enemy team's end. Ships must go to the other side of the map, take the flag, then make it back to the friendly zone. A ship that is destroyed with the flag "drops" it, allowing it to be picked up by another ship and moved again. Flags can be manually dropped by clicking on the flag icon. A team wins when they get the required number of flags.
* Centerflag: Capture the Flag, but the flags are in the center of the map.
* Station Capture: There is one zone around a station on the Red team's side. The Attackers must capture this zone to win. The game ends when the station is captured, all ships on a side are destroyed, or the timer runs out.

Capture points for Control and Tug of War take 60 seconds to capture.
In Control, control points confer 2 points every 10 seconds.
In Tug of War, the score shifts by <math>2\times \left|\Delta p\right|</math> (where <math>\Delta p</math> is the difference in points controlled by the two teams) every 10 seconds in favor of the team holding more points.

== Notes ==
<references />

Movement

2024-06-23T14:52:41Z

76561198801434526: /* Formation */ fixed formatting of rel/true/loose

<div style="float: left; padding-right: 20px;">
__TOC__
</div>

Ships don't move like real-spaceships, they move more like submarines/ships, with max speeds as well as space applying friction to ships slowing and stopping them if they lose engine power.

<div style="clear: both"></div>
== Mechanics ==
* Thrust: Fraction of engine power used. Options are: 1/3, 2/3, Full, and Flank.
* Acceleration: This mostly is affected by the drives, however the mass of the ship based on installed components slightly affects acceleration.
* Flank Speed: Boosts top speed by 50% (does not affect turn speed or turn acceleration). When flanking, every active thruster checks for flank damage once per second, and takes 5 damage if the check fails. Forward acceleration is additionally increased by 50%
* Heading/Roll: Holds the ship pointing in a certain direction or oriented "up" a certain way
* Drives as main modifier
* Dodging & Evasive: EVADE setting makes your ships move randomly to dodge shots, but makes them take longer to get to their destination. Skilled players can manually set up complex waypoints or use the orbit command to dodge shots, which is often more effective than the standard EVADE setting.

When a target is lost and there are no remaining roll drivers, the ship will issue itself a temporary ROL order to prevent re-masking weapons.

{| class="wikitable"
|+ Thrust multipliers for linear thrust in non-forward directions
|-
! ANS Ships !! Lateral !! Reverse !! OSP Ships !! Lateral !! Reverse
|-
| Sprinter || 90% || 95% || Ferryman || 75% || 80%
|-
| Raines || 80% || 90% || Draugr || 75% || 80%
|-
| Keystone || 80% || 90% || Flathead || 75% || 80%
|-
| Vauxhall || 80% || 95% || Ocello || 80% || 80%
|-
| Axford || 75% || 85% || Marauder || 30% || 80%
|-
| Solomon || 75% || 85% || Moorline || 30% || 80%
|}

Ships have their thrust power scaled to a certain amount for lateral and reverse movement, with lateral thrust (side to side / up down) usually being the worst. Main forward thrusters are always at 1.00 scale

Tracks are annotated by two lines: one fixed length line that indicates the heading of the track (if the track is a warship), and one variable length line with a circle on the end that indicates the track's velocity. The velocity line represents the track's predicted location after 10 seconds.

=== Linear Acceleration ===

Ships have to accelerate to max speed, and having higher thrust makes that happen faster. [todo: enter similar equation as below with drag]

=== Turning ===

Ships have an angular thrust for turning and rolling. It is possible to calculate the time to turn a ship's nose 180°.

<div style="float: right; width: 300px;">
{| class="wikitable"
|-
! Hull !! Inertia Factor <math>F_y</math>
|-
| Sprinter|| 1.59
|-
| Raines || 2.16
|-
| Keystone || 4.09
|-
| Vauxhall || 8.32
|-
| Axford || 8.72
|-
| Solomon || 17.2
|}
</div>

* <math>P \equiv \text{Angular Thrust (as seen in-game)}</math>
* <math>M \equiv \text{Ship Mass (as seen in-game)}</math>
* <math>F \equiv \text{Ship Inertia Factor (see chart)}</math>

Because of damping, ships will accelerate only to a certain maximum speed given by (in radians per second), <math>\omega_\text{max} = \frac{1000P}{MF}</math>

The time in seconds, <math>t</math>, to turn 180° is: <math>\large{{t \approx \frac{\pi}{\omega_\text{max}} + 10}}</math>

(<math>\omega_\text{max}</math> is usually smaller than the listed max turn rate, <math>R</math>, except for buffed light ships and possibly when rolling. To compare the two, take <math>R</math>, multiply by <math>\pi</math>, and divide by 180. If the result is <math>< \omega_\text{max}</math>, then replace <math>\omega_\text{max}</math> in the equation above by the result.)

<div style="clear: both"></div>

== Controls ==

{| class="wikitable"
|-
! Abbreviation !! Name !! Default Keybind !! Description
|-
| ORB || Orbit Position || O || Orbit around a point
|-
| POS || Move to Position || M || Move to a point
|-
| CRS || Drive Course || SHIFT + M || Move continuously in one direction
|-
| HDG || Hold Heading || H || Point towards a direction
|-
| CHD || Clear Hold Heading || Not Bound || Clears heading command
|-
| ROL || Roll Ship || Shift + H || Roll to a specific rotation
|-
| CRL || Clear Roll Ship || Not Bound || Clears roll command
|-
| CLR || Clear HDG/ROL || Not Bound || Clears both heading and roll commands
|-
| FRM || Form With Ship || Shift + F || Join formation with another ship
|-
| ALD || Assume Lead || Ctrl + F || Become leader of current formation
|-
| ALL STOP || Hold Position || Shift + Space || Clears move command
|}

== Formation ==
Formations allow for ships to be grouped together and commanded as one unit. Ships in a formation will attempt to maintain a certain position relative to the guide/lead ship, and will match speed and heading with the lead ship. If the formation becomes too separated while manoeuvring, ships will slow down to allow other ships to catch up.

Formations have 3 modes:
* '''Rel''': Maintains relative positions around the lead ship according to its heading, allowing the formation to rotate with the lead ship.
* '''Tru''': Maintains a fixed position around the lead ship, and does not adjust the formation if the lead rotates. Ships will still rotate to match the lead's heading
* '''Loose''': Similar to Tru, but the formation will not slow down for the slower ships and will be allowed to outrun each-other.

Holding shift and giving orders issues the order to the entire formation. This includes changing settings on the status panel. If you select a ship in the formation that is not the lead ship, and give it a movement order, the ship will exit the formation to complete its order.

Movement

2024-06-23T14:52:03Z

76561198801434526: /* Controls */ removed table caption

<div style="float: left; padding-right: 20px;">
__TOC__
</div>

Ships don't move like real-spaceships, they move more like submarines/ships, with max speeds as well as space applying friction to ships slowing and stopping them if they lose engine power.

<div style="clear: both"></div>
== Mechanics ==
* Thrust: Fraction of engine power used. Options are: 1/3, 2/3, Full, and Flank.
* Acceleration: This mostly is affected by the drives, however the mass of the ship based on installed components slightly affects acceleration.
* Flank Speed: Boosts top speed by 50% (does not affect turn speed or turn acceleration). When flanking, every active thruster checks for flank damage once per second, and takes 5 damage if the check fails. Forward acceleration is additionally increased by 50%
* Heading/Roll: Holds the ship pointing in a certain direction or oriented "up" a certain way
* Drives as main modifier
* Dodging & Evasive: EVADE setting makes your ships move randomly to dodge shots, but makes them take longer to get to their destination. Skilled players can manually set up complex waypoints or use the orbit command to dodge shots, which is often more effective than the standard EVADE setting.

When a target is lost and there are no remaining roll drivers, the ship will issue itself a temporary ROL order to prevent re-masking weapons.

{| class="wikitable"
|+ Thrust multipliers for linear thrust in non-forward directions
|-
! ANS Ships !! Lateral !! Reverse !! OSP Ships !! Lateral !! Reverse
|-
| Sprinter || 90% || 95% || Ferryman || 75% || 80%
|-
| Raines || 80% || 90% || Draugr || 75% || 80%
|-
| Keystone || 80% || 90% || Flathead || 75% || 80%
|-
| Vauxhall || 80% || 95% || Ocello || 80% || 80%
|-
| Axford || 75% || 85% || Marauder || 30% || 80%
|-
| Solomon || 75% || 85% || Moorline || 30% || 80%
|}

Ships have their thrust power scaled to a certain amount for lateral and reverse movement, with lateral thrust (side to side / up down) usually being the worst. Main forward thrusters are always at 1.00 scale

Tracks are annotated by two lines: one fixed length line that indicates the heading of the track (if the track is a warship), and one variable length line with a circle on the end that indicates the track's velocity. The velocity line represents the track's predicted location after 10 seconds.

=== Linear Acceleration ===

Ships have to accelerate to max speed, and having higher thrust makes that happen faster. [todo: enter similar equation as below with drag]

=== Turning ===

Ships have an angular thrust for turning and rolling. It is possible to calculate the time to turn a ship's nose 180°.

<div style="float: right; width: 300px;">
{| class="wikitable"
|-
! Hull !! Inertia Factor <math>F_y</math>
|-
| Sprinter|| 1.59
|-
| Raines || 2.16
|-
| Keystone || 4.09
|-
| Vauxhall || 8.32
|-
| Axford || 8.72
|-
| Solomon || 17.2
|}
</div>

* <math>P \equiv \text{Angular Thrust (as seen in-game)}</math>
* <math>M \equiv \text{Ship Mass (as seen in-game)}</math>
* <math>F \equiv \text{Ship Inertia Factor (see chart)}</math>

Because of damping, ships will accelerate only to a certain maximum speed given by (in radians per second), <math>\omega_\text{max} = \frac{1000P}{MF}</math>

The time in seconds, <math>t</math>, to turn 180° is: <math>\large{{t \approx \frac{\pi}{\omega_\text{max}} + 10}}</math>

(<math>\omega_\text{max}</math> is usually smaller than the listed max turn rate, <math>R</math>, except for buffed light ships and possibly when rolling. To compare the two, take <math>R</math>, multiply by <math>\pi</math>, and divide by 180. If the result is <math>< \omega_\text{max}</math>, then replace <math>\omega_\text{max}</math> in the equation above by the result.)

<div style="clear: both"></div>

== Controls ==

{| class="wikitable"
|-
! Abbreviation !! Name !! Default Keybind !! Description
|-
| ORB || Orbit Position || O || Orbit around a point
|-
| POS || Move to Position || M || Move to a point
|-
| CRS || Drive Course || SHIFT + M || Move continuously in one direction
|-
| HDG || Hold Heading || H || Point towards a direction
|-
| CHD || Clear Hold Heading || Not Bound || Clears heading command
|-
| ROL || Roll Ship || Shift + H || Roll to a specific rotation
|-
| CRL || Clear Roll Ship || Not Bound || Clears roll command
|-
| CLR || Clear HDG/ROL || Not Bound || Clears both heading and roll commands
|-
| FRM || Form With Ship || Shift + F || Join formation with another ship
|-
| ALD || Assume Lead || Ctrl + F || Become leader of current formation
|-
| ALL STOP || Hold Position || Shift + Space || Clears move command
|}

== Formation ==
Formations allow for ships to be grouped together and commanded as one unit. Ships in a formation will attempt to maintain a certain position relative to the guide/lead ship, and will match speed and heading with the lead ship. If the formation becomes too separated while manoeuvring, ships will slow down to allow other ships to catch up.

Formations have 3 modes:
* ''Rel'': Maintains relative positions around the lead ship according to its heading, allowing the formation to rotate with the lead ship.
* ''Tru'': Maintains a fixed position around the lead ship, and does not adjust the formation if the lead rotates. Ships will still rotate to match the lead's heading
* ''Loose'': Similar to Tru, but the formation will not slow down for the slower ships and will be allowed to outrun each-other.

Holding shift and giving orders issues the order to the entire formation. This includes changing settings on the status panel. If you select a ship in the formation that is not the lead ship, and give it a movement order, the ship will exit the formation to complete its order.

Movement

2024-06-23T14:51:13Z

76561198801434526: /* Turning */ fixed table

<div style="float: left; padding-right: 20px;">
__TOC__
</div>

Ships don't move like real-spaceships, they move more like submarines/ships, with max speeds as well as space applying friction to ships slowing and stopping them if they lose engine power.

<div style="clear: both"></div>
== Mechanics ==
* Thrust: Fraction of engine power used. Options are: 1/3, 2/3, Full, and Flank.
* Acceleration: This mostly is affected by the drives, however the mass of the ship based on installed components slightly affects acceleration.
* Flank Speed: Boosts top speed by 50% (does not affect turn speed or turn acceleration). When flanking, every active thruster checks for flank damage once per second, and takes 5 damage if the check fails. Forward acceleration is additionally increased by 50%
* Heading/Roll: Holds the ship pointing in a certain direction or oriented "up" a certain way
* Drives as main modifier
* Dodging & Evasive: EVADE setting makes your ships move randomly to dodge shots, but makes them take longer to get to their destination. Skilled players can manually set up complex waypoints or use the orbit command to dodge shots, which is often more effective than the standard EVADE setting.

When a target is lost and there are no remaining roll drivers, the ship will issue itself a temporary ROL order to prevent re-masking weapons.

{| class="wikitable"
|+ Thrust multipliers for linear thrust in non-forward directions
|-
! ANS Ships !! Lateral !! Reverse !! OSP Ships !! Lateral !! Reverse
|-
| Sprinter || 90% || 95% || Ferryman || 75% || 80%
|-
| Raines || 80% || 90% || Draugr || 75% || 80%
|-
| Keystone || 80% || 90% || Flathead || 75% || 80%
|-
| Vauxhall || 80% || 95% || Ocello || 80% || 80%
|-
| Axford || 75% || 85% || Marauder || 30% || 80%
|-
| Solomon || 75% || 85% || Moorline || 30% || 80%
|}

Ships have their thrust power scaled to a certain amount for lateral and reverse movement, with lateral thrust (side to side / up down) usually being the worst. Main forward thrusters are always at 1.00 scale

Tracks are annotated by two lines: one fixed length line that indicates the heading of the track (if the track is a warship), and one variable length line with a circle on the end that indicates the track's velocity. The velocity line represents the track's predicted location after 10 seconds.

=== Linear Acceleration ===

Ships have to accelerate to max speed, and having higher thrust makes that happen faster. [todo: enter similar equation as below with drag]

=== Turning ===

Ships have an angular thrust for turning and rolling. It is possible to calculate the time to turn a ship's nose 180°.

<div style="float: right; width: 300px;">
{| class="wikitable"
|-
! Hull !! Inertia Factor <math>F_y</math>
|-
| Sprinter|| 1.59
|-
| Raines || 2.16
|-
| Keystone || 4.09
|-
| Vauxhall || 8.32
|-
| Axford || 8.72
|-
| Solomon || 17.2
|}
</div>

* <math>P \equiv \text{Angular Thrust (as seen in-game)}</math>
* <math>M \equiv \text{Ship Mass (as seen in-game)}</math>
* <math>F \equiv \text{Ship Inertia Factor (see chart)}</math>

Because of damping, ships will accelerate only to a certain maximum speed given by (in radians per second), <math>\omega_\text{max} = \frac{1000P}{MF}</math>

The time in seconds, <math>t</math>, to turn 180° is: <math>\large{{t \approx \frac{\pi}{\omega_\text{max}} + 10}}</math>

(<math>\omega_\text{max}</math> is usually smaller than the listed max turn rate, <math>R</math>, except for buffed light ships and possibly when rolling. To compare the two, take <math>R</math>, multiply by <math>\pi</math>, and divide by 180. If the result is <math>< \omega_\text{max}</math>, then replace <math>\omega_\text{max}</math> in the equation above by the result.)

<div style="clear: both"></div>

== Controls ==

{| class="wikitable"
|+ Thrust multipliers for linear thrust in non-forward directions
|-
! Abbreviation !! Name !! Default Keybind !! Description
|-
| ORB || Orbit Position || O || Orbit around a point
|-
| POS || Move to Position || M || Move to a point
|-
| CRS || Drive Course || SHIFT + M || Move continuously in one direction
|-
| HDG || Hold Heading || H || Point towards a direction
|-
| CHD || Clear Hold Heading || Not Bound || Clears heading command
|-
| ROL || Roll Ship || Shift + H || Roll to a specific rotation
|-
| CRL || Clear Roll Ship || Not Bound || Clears roll command
|-
| CLR || Clear HDG/ROL || Not Bound || Clears both heading and roll commands
|-
| FRM || Form With Ship || Shift + F || Join formation with another ship
|-
| ALD || Assume Lead || Ctrl + F || Become leader of current formation
|-
| ALL STOP || Hold Position || Shift + Space || Clears move command
|}

== Formation ==
Formations allow for ships to be grouped together and commanded as one unit. Ships in a formation will attempt to maintain a certain position relative to the guide/lead ship, and will match speed and heading with the lead ship. If the formation becomes too separated while manoeuvring, ships will slow down to allow other ships to catch up.

Formations have 3 modes:
* ''Rel'': Maintains relative positions around the lead ship according to its heading, allowing the formation to rotate with the lead ship.
* ''Tru'': Maintains a fixed position around the lead ship, and does not adjust the formation if the lead rotates. Ships will still rotate to match the lead's heading
* ''Loose'': Similar to Tru, but the formation will not slow down for the slower ships and will be allowed to outrun each-other.

Holding shift and giving orders issues the order to the entire formation. This includes changing settings on the status panel. If you select a ship in the formation that is not the lead ship, and give it a movement order, the ship will exit the formation to complete its order.

Movement

2024-06-23T14:50:46Z

76561198801434526: Added movement page

<div style="float: left; padding-right: 20px;">
__TOC__
</div>

Ships don't move like real-spaceships, they move more like submarines/ships, with max speeds as well as space applying friction to ships slowing and stopping them if they lose engine power.

<div style="clear: both"></div>
== Mechanics ==
* Thrust: Fraction of engine power used. Options are: 1/3, 2/3, Full, and Flank.
* Acceleration: This mostly is affected by the drives, however the mass of the ship based on installed components slightly affects acceleration.
* Flank Speed: Boosts top speed by 50% (does not affect turn speed or turn acceleration). When flanking, every active thruster checks for flank damage once per second, and takes 5 damage if the check fails. Forward acceleration is additionally increased by 50%
* Heading/Roll: Holds the ship pointing in a certain direction or oriented "up" a certain way
* Drives as main modifier
* Dodging & Evasive: EVADE setting makes your ships move randomly to dodge shots, but makes them take longer to get to their destination. Skilled players can manually set up complex waypoints or use the orbit command to dodge shots, which is often more effective than the standard EVADE setting.

When a target is lost and there are no remaining roll drivers, the ship will issue itself a temporary ROL order to prevent re-masking weapons.

{| class="wikitable"
|+ Thrust multipliers for linear thrust in non-forward directions
|-
! ANS Ships !! Lateral !! Reverse !! OSP Ships !! Lateral !! Reverse
|-
| Sprinter || 90% || 95% || Ferryman || 75% || 80%
|-
| Raines || 80% || 90% || Draugr || 75% || 80%
|-
| Keystone || 80% || 90% || Flathead || 75% || 80%
|-
| Vauxhall || 80% || 95% || Ocello || 80% || 80%
|-
| Axford || 75% || 85% || Marauder || 30% || 80%
|-
| Solomon || 75% || 85% || Moorline || 30% || 80%
|}

Ships have their thrust power scaled to a certain amount for lateral and reverse movement, with lateral thrust (side to side / up down) usually being the worst. Main forward thrusters are always at 1.00 scale

Tracks are annotated by two lines: one fixed length line that indicates the heading of the track (if the track is a warship), and one variable length line with a circle on the end that indicates the track's velocity. The velocity line represents the track's predicted location after 10 seconds.

=== Linear Acceleration ===

Ships have to accelerate to max speed, and having higher thrust makes that happen faster. [todo: enter similar equation as below with drag]

=== Turning ===

Ships have an angular thrust for turning and rolling. It is possible to calculate the time to turn a ship's nose 180°.

<div style="float: right; width: 300px;">
{| class="wikitable"
|-
! Hull !! Inertia Factor <math>F_y</math>
| Sprinter|| 1.59
|-
| Raines || 2.16
|-
| Keystone || 4.09
|-
| Vauxhall || 8.32
|-
| Axford || 8.72
|-
| Solomon || 17.2
|}
</div>

* <math>P \equiv \text{Angular Thrust (as seen in-game)}</math>
* <math>M \equiv \text{Ship Mass (as seen in-game)}</math>
* <math>F \equiv \text{Ship Inertia Factor (see chart)}</math>

Because of damping, ships will accelerate only to a certain maximum speed given by (in radians per second), <math>\omega_\text{max} = \frac{1000P}{MF}</math>

The time in seconds, <math>t</math>, to turn 180° is: <math>\large{{t \approx \frac{\pi}{\omega_\text{max}} + 10}}</math>

(<math>\omega_\text{max}</math> is usually smaller than the listed max turn rate, <math>R</math>, except for buffed light ships and possibly when rolling. To compare the two, take <math>R</math>, multiply by <math>\pi</math>, and divide by 180. If the result is <math>< \omega_\text{max}</math>, then replace <math>\omega_\text{max}</math> in the equation above by the result.)

<div style="clear: both"></div>
== Controls ==

{| class="wikitable"
|+ Thrust multipliers for linear thrust in non-forward directions
|-
! Abbreviation !! Name !! Default Keybind !! Description
|-
| ORB || Orbit Position || O || Orbit around a point
|-
| POS || Move to Position || M || Move to a point
|-
| CRS || Drive Course || SHIFT + M || Move continuously in one direction
|-
| HDG || Hold Heading || H || Point towards a direction
|-
| CHD || Clear Hold Heading || Not Bound || Clears heading command
|-
| ROL || Roll Ship || Shift + H || Roll to a specific rotation
|-
| CRL || Clear Roll Ship || Not Bound || Clears roll command
|-
| CLR || Clear HDG/ROL || Not Bound || Clears both heading and roll commands
|-
| FRM || Form With Ship || Shift + F || Join formation with another ship
|-
| ALD || Assume Lead || Ctrl + F || Become leader of current formation
|-
| ALL STOP || Hold Position || Shift + Space || Clears move command
|}

== Formation ==
Formations allow for ships to be grouped together and commanded as one unit. Ships in a formation will attempt to maintain a certain position relative to the guide/lead ship, and will match speed and heading with the lead ship. If the formation becomes too separated while manoeuvring, ships will slow down to allow other ships to catch up.

Formations have 3 modes:
* ''Rel'': Maintains relative positions around the lead ship according to its heading, allowing the formation to rotate with the lead ship.
* ''Tru'': Maintains a fixed position around the lead ship, and does not adjust the formation if the lead rotates. Ships will still rotate to match the lead's heading
* ''Loose'': Similar to Tru, but the formation will not slow down for the slower ships and will be allowed to outrun each-other.

Holding shift and giving orders issues the order to the entire formation. This includes changing settings on the status panel. If you select a ship in the formation that is not the lead ship, and give it a movement order, the ship will exit the formation to complete its order.

Intelligence

2024-06-23T13:58:18Z

76561198801434526: /* Intel Packets */ reduced horizontal real-estate of heading image

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
When a radar track is picked up, intelligence on this track will start being gathered by related components. As intelligence accumulates, more info will be provided on this track, such as ship internal condition, point defense condition, and CIC/weapons/thrusters condition.

<div style="clear: both"></div>
== Intel Effort ==
When a track is detected, ''intel effort'' will be used to identify the track. Only the ''intel effort'' statistic from the component with the highest ''intel effort'' is used.
For example, if a ship is being tracked by a Sprinter corvette with basic CIC(1pt/s), and the team has 2 Solomon battleship in communication range, with one fitting an intelligence center(15pt/s), and the other one also fitted with a analysis annex (15×(1+30%)=19.5pt/s), only the last Solomon's 19.5pt/s effort would be used.

Intel progress can be made on radar and visual tracks.<ref>Note that visual tracks are not transmitted over the network, which means remote intel like intel center will not work on them.</ref> Intel cannot be gathered on burn tracks or ELINT (but those tracks will show any previous intel gathered)

== Intel Packets ==
All ships initially have a identification difficulty of 200; this is the baseline size of intel packets.
If a ship has higher identification difficulty, packets sizes are scaled accordingly.
Track info is split into a couple of packets, with default identification difficulty of 200:
* Packet 1 is of size 200.
* Packet 2 is of size 250, reaching the end of packet 2 would require a total ''intel effort'' of 450 points.
* Update Packets are of size 400 per update, reaching the end of update packet 1 would require a total ''intel effort'' of 850 points.
The track info update would progress as follows:
{| class="wikitable"
|-
! Packet Type !! Track Information !! Effort Cost !! Cumulative Time For Basic CIC(1/s) !! Cumulative Time For Citadel CIC(4/s) !! Cumulative Time For Intelligence Center(15/s)
|-
| - || Track <nowiki>####</nowiki>-Unknown || 0 || 0s || 0s || 0s
|-
| Packet 1 || Warship || 200 || 200s || 50s || 13.3s
|-
| Packet 1 || Warship (Class) || 200 || 400s || 100s || 26.7s
|-
| Packet 1 || Class (Hull) || 200 || 600s || 150s || 40s
|-
| Packet 1 || Ship Name (Hull) || 200 || 800s || 200s || 53.3s
|-
| Packet 2 || Ship Name (Hull), Ship Status || 250 || 1050s || 262.5s || 70s
|-
| Packet 2 || Ship Name (Hull), Ship Status,% || 250 || 1300s || 325s || 86.7s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 1700s || 425s || 113.3s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 2100s || 525s || 140s
|-
| ... || ... || ... || ... || ... || ...
|}

<div style="float: right; width: 30%; padding: 20px">
[[File:Heading.png|alt=Image of a track with the heading and velocity vectors labelled. |Image of a track with the heading and velocity vectors labelled. ]]

Image of a track with the heading and velocity vectors labelled.
</div>

The intel gathered is shared to the entire team, and if the component providing intel is lost, other intel sources can continue where it left off assuming they can see the track.<ref>It seems like all ships on the team can receive intel even if their comms are destroyed.</ref>

Missile intel is similar, but has packet sizes of 20, the first packet identifies that it's a missile and the second packet reveals specific name and seeker combo. The second packet will also incur a 0.1x multiplier on any intel work on it that isn't from a dedicated missile identifier (eg, intel center is reduced to 1.5 work/s, taking ~13 sec to get detailed report, but scryer still gets its full 10/s taking only 2 sec to get detailed report).

Once identified as a warship, the track's heading will be displayed as a line pointing out of the track in the tactical view.

== Ship Status ==
A ship track can have one of the following status displayed:
* '''EVACUATED''': Ship has been evacuated
* '''NOT UNDER COMMAND''': CIC is disabled or destroyed.
* '''IMMOBILISED''': Drives no longer operational.
* '''HARMLESS''': no offensive weapon available (EW included), either all are destroyed or the ship has no ammunition to fire.
Statuses higher on this list have priority and will be displayed over lower statuses.

However, please do note that ship status are only updated at each update packet. It is completely normal to see a ship under way with the status of '''IMMOBLISED''' or '''NOT UNDER COMMAND''' for some period due to how this mechanic works.

=== Intel Accuracy and Details ===

COND% is determined by the percentage of functioning components (''i.e'', any component that's above its functioning threshold), and adds or subtracts up to the intel accuracy<ref>As a result, intel accuracy is often better described as intel ''inaccuracy'', as a lower number is better</ref> to it (eg, a ship with two green components, and one red component will have COND: 66%, if the Intel source has 20% inaccuracy that number can vary from 46% to 86%)

Debuff count is just the amount of debuffs, plus minus multiplied by the inaccuracy (''e.g.'' a ship with 10 debuffs and a Intel accuracy of 20% will show anywhere from 8 to 12 debuffs)

PD% condition is similar to COND%, but only looks at PD systems. Each PDT, decoy type, and PD missile type are counted as a component(''e.g.'', if a ship has 5 PDTs, chaff, flares, active decoys, and two types of PD missiles, every PDT getting knocked out but all decoys and PDMs functional will result in PD: 50%)

== Working on remote tracks ==

Most sources of intel can only work locally, which means that the intel source can only work on tracks that the ship itself sees. However, certain components such as intelligence centers can work on remote tracks, allowing them to work on all tracks that is shared to the ship by the team.

Note that the intel doesn't just work for the player bringing the intel center, it works for all players on the same team.

If an intel ship cannot recieve tracks (due to ships being comms jammed/comms off/comms destroyed), then it will not be able to work on that track.

Ships can still recieve intel if comms jammed or comms destroyed, as intel is a teamwide thing, with the information independent of the communication network''[possibly a bug]''

== EO Seeker Special Capability ==
If a ship class and/or hull type is identified, a EO seeker missile is capable of locking only onto such type of target if fired in TRK(track) mode.

== Re-Acquisition of a Lost Track ==
After a track is broken, if it is re-acquired more than 2.5km from its last known position, then it will be assigned with a new track number with no intel. This would force the track to go through all the intel packets again before detailed information is regained.
Likewise, if the track is re-established within 2.5km from the last known position, all information is preserved.

== Decoy Container ==
Decoy containers can mimic ship signatures of Ferrymans and Marauders. These decoy containers cannot be revealed by intel alone, and will require visual spotting to distinguish from a real target. Decoy containers will typically have their heading pointing in the direction in which they are moving, which is not necessarily typical behaviour for Marauders.

== Visual ==
<div style="float: right; width: 50%; padding: 20px">
[[File:MagicSmoke.png|alt=Smoke released by a dead shuttle in the testing range. |Smoke released by a dead shuttle in the testing range. ]]

Smoke (right) released by a dead shuttle in the testing range.
</div>
Ships within visual range will have their model revealed, which reveals their loadout and current state.
The ship's bridge lights switch to blue to amber when the ship has no more power (eg, all reactors disabled or destroyed)
External modules show black smoke and sparks when destroyed.

== Sound ==
'''[WIP]'''
Sounds can be used to learn information about the ship. You can hear sound effects near the location of your camera, regardless of how far any friendly ships may be from the location.

=== Alarms ===
Upon being destroyed, a ship typically sounds an evacuation alarm which will occur several seconds before lifepods get released.

=== Damage ===
Visible ships will play a certain sound effect when some of its components are damaged (hits on structure before structurebreak will not play this sound). The sound effect is not guaranteed to play every time the components are damaged''needs confirmation'', but is more likely to play when hit by high damage attacks.

The sound effect can only play once every 2.5 seconds, and will only play if the model is visible.

If a ship gets structurebroken, a damage sound effect is played immediately, ignoring the above restrictions.

=== Weapon Sounds ===
Most weapon types have unique sound effects when in use. Turrets have a distinctive sound when rotating, and missile tubes have distinctive sounds when launching missiles

=== Intercom Chatter ===
Intercom chatter can give clues to the status of a ship.

If the ship's model is visible and the player's viewpoint is close enough, radio chatter can be heard from the ship.

[transcript WIP]

Fire will have a smouldering, crackling sound, and either a visible external yellow/orange fire or white sparks (electrical fire). The two different vfx are only a visual difference, the fire behaves the same.

Atmosphere leak will have a hissing, air leak sort of sound and a bright white cloud appearance

== Notes ==
<references />

Intelligence

2024-06-23T13:57:29Z

76561198801434526: added linebreak between images and caption text

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
When a radar track is picked up, intelligence on this track will start being gathered by related components. As intelligence accumulates, more info will be provided on this track, such as ship internal condition, point defense condition, and CIC/weapons/thrusters condition.

<div style="clear: both"></div>
== Intel Effort ==
When a track is detected, ''intel effort'' will be used to identify the track. Only the ''intel effort'' statistic from the component with the highest ''intel effort'' is used.
For example, if a ship is being tracked by a Sprinter corvette with basic CIC(1pt/s), and the team has 2 Solomon battleship in communication range, with one fitting an intelligence center(15pt/s), and the other one also fitted with a analysis annex (15×(1+30%)=19.5pt/s), only the last Solomon's 19.5pt/s effort would be used.

Intel progress can be made on radar and visual tracks.<ref>Note that visual tracks are not transmitted over the network, which means remote intel like intel center will not work on them.</ref> Intel cannot be gathered on burn tracks or ELINT (but those tracks will show any previous intel gathered)

== Intel Packets ==
All ships initially have a identification difficulty of 200; this is the baseline size of intel packets.
If a ship has higher identification difficulty, packets sizes are scaled accordingly.
Track info is split into a couple of packets, with default identification difficulty of 200:
* Packet 1 is of size 200.
* Packet 2 is of size 250, reaching the end of packet 2 would require a total ''intel effort'' of 450 points.
* Update Packets are of size 400 per update, reaching the end of update packet 1 would require a total ''intel effort'' of 850 points.
The track info update would progress as follows:
{| class="wikitable"
|-
! Packet Type !! Track Information !! Effort Cost !! Cumulative Time For Basic CIC(1/s) !! Cumulative Time For Citadel CIC(4/s) !! Cumulative Time For Intelligence Center(15/s)
|-
| - || Track <nowiki>####</nowiki>-Unknown || 0 || 0s || 0s || 0s
|-
| Packet 1 || Warship || 200 || 200s || 50s || 13.3s
|-
| Packet 1 || Warship (Class) || 200 || 400s || 100s || 26.7s
|-
| Packet 1 || Class (Hull) || 200 || 600s || 150s || 40s
|-
| Packet 1 || Ship Name (Hull) || 200 || 800s || 200s || 53.3s
|-
| Packet 2 || Ship Name (Hull), Ship Status || 250 || 1050s || 262.5s || 70s
|-
| Packet 2 || Ship Name (Hull), Ship Status,% || 250 || 1300s || 325s || 86.7s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 1700s || 425s || 113.3s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 2100s || 525s || 140s
|-
| ... || ... || ... || ... || ... || ...
|}

<div style="float: right; width: 50%; padding: 20px">
[[File:Heading.png|alt=Image of a track with the heading and velocity vectors labelled. |Image of a track with the heading and velocity vectors labelled. ]]

Image of a track with the heading and velocity vectors labelled.
</div>

The intel gathered is shared to the entire team, and if the component providing intel is lost, other intel sources can continue where it left off assuming they can see the track.<ref>It seems like all ships on the team can receive intel even if their comms are destroyed.</ref>

Missile intel is similar, but has packet sizes of 20, the first packet identifies that it's a missile and the second packet reveals specific name and seeker combo. The second packet will also incur a 0.1x multiplier on any intel work on it that isn't from a dedicated missile identifier (eg, intel center is reduced to 1.5 work/s, taking ~13 sec to get detailed report, but scryer still gets its full 10/s taking only 2 sec to get detailed report).

Once identified as a warship, the track's heading will be displayed as a line pointing out of the track in the tactical view.

== Ship Status ==
A ship track can have one of the following status displayed:
* '''EVACUATED''': Ship has been evacuated
* '''NOT UNDER COMMAND''': CIC is disabled or destroyed.
* '''IMMOBILISED''': Drives no longer operational.
* '''HARMLESS''': no offensive weapon available (EW included), either all are destroyed or the ship has no ammunition to fire.
Statuses higher on this list have priority and will be displayed over lower statuses.

However, please do note that ship status are only updated at each update packet. It is completely normal to see a ship under way with the status of '''IMMOBLISED''' or '''NOT UNDER COMMAND''' for some period due to how this mechanic works.

=== Intel Accuracy and Details ===

COND% is determined by the percentage of functioning components (''i.e'', any component that's above its functioning threshold), and adds or subtracts up to the intel accuracy<ref>As a result, intel accuracy is often better described as intel ''inaccuracy'', as a lower number is better</ref> to it (eg, a ship with two green components, and one red component will have COND: 66%, if the Intel source has 20% inaccuracy that number can vary from 46% to 86%)

Debuff count is just the amount of debuffs, plus minus multiplied by the inaccuracy (''e.g.'' a ship with 10 debuffs and a Intel accuracy of 20% will show anywhere from 8 to 12 debuffs)

PD% condition is similar to COND%, but only looks at PD systems. Each PDT, decoy type, and PD missile type are counted as a component(''e.g.'', if a ship has 5 PDTs, chaff, flares, active decoys, and two types of PD missiles, every PDT getting knocked out but all decoys and PDMs functional will result in PD: 50%)

== Working on remote tracks ==

Most sources of intel can only work locally, which means that the intel source can only work on tracks that the ship itself sees. However, certain components such as intelligence centers can work on remote tracks, allowing them to work on all tracks that is shared to the ship by the team.

Note that the intel doesn't just work for the player bringing the intel center, it works for all players on the same team.

If an intel ship cannot recieve tracks (due to ships being comms jammed/comms off/comms destroyed), then it will not be able to work on that track.

Ships can still recieve intel if comms jammed or comms destroyed, as intel is a teamwide thing, with the information independent of the communication network''[possibly a bug]''

== EO Seeker Special Capability ==
If a ship class and/or hull type is identified, a EO seeker missile is capable of locking only onto such type of target if fired in TRK(track) mode.

== Re-Acquisition of a Lost Track ==
After a track is broken, if it is re-acquired more than 2.5km from its last known position, then it will be assigned with a new track number with no intel. This would force the track to go through all the intel packets again before detailed information is regained.
Likewise, if the track is re-established within 2.5km from the last known position, all information is preserved.

== Decoy Container ==
Decoy containers can mimic ship signatures of Ferrymans and Marauders. These decoy containers cannot be revealed by intel alone, and will require visual spotting to distinguish from a real target. Decoy containers will typically have their heading pointing in the direction in which they are moving, which is not necessarily typical behaviour for Marauders.

== Visual ==
<div style="float: right; width: 50%; padding: 20px">
[[File:MagicSmoke.png|alt=Smoke released by a dead shuttle in the testing range. |Smoke released by a dead shuttle in the testing range. ]]

Smoke (right) released by a dead shuttle in the testing range.
</div>
Ships within visual range will have their model revealed, which reveals their loadout and current state.
The ship's bridge lights switch to blue to amber when the ship has no more power (eg, all reactors disabled or destroyed)
External modules show black smoke and sparks when destroyed.

== Sound ==
'''[WIP]'''
Sounds can be used to learn information about the ship. You can hear sound effects near the location of your camera, regardless of how far any friendly ships may be from the location.

=== Alarms ===
Upon being destroyed, a ship typically sounds an evacuation alarm which will occur several seconds before lifepods get released.

=== Damage ===
Visible ships will play a certain sound effect when some of its components are damaged (hits on structure before structurebreak will not play this sound). The sound effect is not guaranteed to play every time the components are damaged''needs confirmation'', but is more likely to play when hit by high damage attacks.

The sound effect can only play once every 2.5 seconds, and will only play if the model is visible.

If a ship gets structurebroken, a damage sound effect is played immediately, ignoring the above restrictions.

=== Weapon Sounds ===
Most weapon types have unique sound effects when in use. Turrets have a distinctive sound when rotating, and missile tubes have distinctive sounds when launching missiles

=== Intercom Chatter ===
Intercom chatter can give clues to the status of a ship.

If the ship's model is visible and the player's viewpoint is close enough, radio chatter can be heard from the ship.

[transcript WIP]

Fire will have a smouldering, crackling sound, and either a visible external yellow/orange fire or white sparks (electrical fire). The two different vfx are only a visual difference, the fire behaves the same.

Atmosphere leak will have a hissing, air leak sort of sound and a bright white cloud appearance

== Notes ==
<references />

Intelligence

2024-06-23T13:56:41Z

76561198801434526: Added image showing track heading

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
When a radar track is picked up, intelligence on this track will start being gathered by related components. As intelligence accumulates, more info will be provided on this track, such as ship internal condition, point defense condition, and CIC/weapons/thrusters condition.

<div style="clear: both"></div>
== Intel Effort ==
When a track is detected, ''intel effort'' will be used to identify the track. Only the ''intel effort'' statistic from the component with the highest ''intel effort'' is used.
For example, if a ship is being tracked by a Sprinter corvette with basic CIC(1pt/s), and the team has 2 Solomon battleship in communication range, with one fitting an intelligence center(15pt/s), and the other one also fitted with a analysis annex (15×(1+30%)=19.5pt/s), only the last Solomon's 19.5pt/s effort would be used.

Intel progress can be made on radar and visual tracks.<ref>Note that visual tracks are not transmitted over the network, which means remote intel like intel center will not work on them.</ref> Intel cannot be gathered on burn tracks or ELINT (but those tracks will show any previous intel gathered)

== Intel Packets ==
All ships initially have a identification difficulty of 200; this is the baseline size of intel packets.
If a ship has higher identification difficulty, packets sizes are scaled accordingly.
Track info is split into a couple of packets, with default identification difficulty of 200:
* Packet 1 is of size 200.
* Packet 2 is of size 250, reaching the end of packet 2 would require a total ''intel effort'' of 450 points.
* Update Packets are of size 400 per update, reaching the end of update packet 1 would require a total ''intel effort'' of 850 points.
The track info update would progress as follows:
{| class="wikitable"
|-
! Packet Type !! Track Information !! Effort Cost !! Cumulative Time For Basic CIC(1/s) !! Cumulative Time For Citadel CIC(4/s) !! Cumulative Time For Intelligence Center(15/s)
|-
| - || Track <nowiki>####</nowiki>-Unknown || 0 || 0s || 0s || 0s
|-
| Packet 1 || Warship || 200 || 200s || 50s || 13.3s
|-
| Packet 1 || Warship (Class) || 200 || 400s || 100s || 26.7s
|-
| Packet 1 || Class (Hull) || 200 || 600s || 150s || 40s
|-
| Packet 1 || Ship Name (Hull) || 200 || 800s || 200s || 53.3s
|-
| Packet 2 || Ship Name (Hull), Ship Status || 250 || 1050s || 262.5s || 70s
|-
| Packet 2 || Ship Name (Hull), Ship Status,% || 250 || 1300s || 325s || 86.7s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 1700s || 425s || 113.3s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 2100s || 525s || 140s
|-
| ... || ... || ... || ... || ... || ...
|}

<div style="float: right; width: 50%; padding: 20px">
[[File:Heading.png|alt=Image of a track with the heading and velocity vectors labelled. |Image of a track with the heading and velocity vectors labelled. ]]
Image of a track with the heading and velocity vectors labelled.
</div>

The intel gathered is shared to the entire team, and if the component providing intel is lost, other intel sources can continue where it left off assuming they can see the track.<ref>It seems like all ships on the team can receive intel even if their comms are destroyed.</ref>

Missile intel is similar, but has packet sizes of 20, the first packet identifies that it's a missile and the second packet reveals specific name and seeker combo. The second packet will also incur a 0.1x multiplier on any intel work on it that isn't from a dedicated missile identifier (eg, intel center is reduced to 1.5 work/s, taking ~13 sec to get detailed report, but scryer still gets its full 10/s taking only 2 sec to get detailed report).

Once identified as a warship, the track's heading will be displayed as a line pointing out of the track in the tactical view.

== Ship Status ==
A ship track can have one of the following status displayed:
* '''EVACUATED''': Ship has been evacuated
* '''NOT UNDER COMMAND''': CIC is disabled or destroyed.
* '''IMMOBILISED''': Drives no longer operational.
* '''HARMLESS''': no offensive weapon available (EW included), either all are destroyed or the ship has no ammunition to fire.
Statuses higher on this list have priority and will be displayed over lower statuses.

However, please do note that ship status are only updated at each update packet. It is completely normal to see a ship under way with the status of '''IMMOBLISED''' or '''NOT UNDER COMMAND''' for some period due to how this mechanic works.

=== Intel Accuracy and Details ===

COND% is determined by the percentage of functioning components (''i.e'', any component that's above its functioning threshold), and adds or subtracts up to the intel accuracy<ref>As a result, intel accuracy is often better described as intel ''inaccuracy'', as a lower number is better</ref> to it (eg, a ship with two green components, and one red component will have COND: 66%, if the Intel source has 20% inaccuracy that number can vary from 46% to 86%)

Debuff count is just the amount of debuffs, plus minus multiplied by the inaccuracy (''e.g.'' a ship with 10 debuffs and a Intel accuracy of 20% will show anywhere from 8 to 12 debuffs)

PD% condition is similar to COND%, but only looks at PD systems. Each PDT, decoy type, and PD missile type are counted as a component(''e.g.'', if a ship has 5 PDTs, chaff, flares, active decoys, and two types of PD missiles, every PDT getting knocked out but all decoys and PDMs functional will result in PD: 50%)

== Working on remote tracks ==

Most sources of intel can only work locally, which means that the intel source can only work on tracks that the ship itself sees. However, certain components such as intelligence centers can work on remote tracks, allowing them to work on all tracks that is shared to the ship by the team.

Note that the intel doesn't just work for the player bringing the intel center, it works for all players on the same team.

If an intel ship cannot recieve tracks (due to ships being comms jammed/comms off/comms destroyed), then it will not be able to work on that track.

Ships can still recieve intel if comms jammed or comms destroyed, as intel is a teamwide thing, with the information independent of the communication network''[possibly a bug]''

== EO Seeker Special Capability ==
If a ship class and/or hull type is identified, a EO seeker missile is capable of locking only onto such type of target if fired in TRK(track) mode.

== Re-Acquisition of a Lost Track ==
After a track is broken, if it is re-acquired more than 2.5km from its last known position, then it will be assigned with a new track number with no intel. This would force the track to go through all the intel packets again before detailed information is regained.
Likewise, if the track is re-established within 2.5km from the last known position, all information is preserved.

== Decoy Container ==
Decoy containers can mimic ship signatures of Ferrymans and Marauders. These decoy containers cannot be revealed by intel alone, and will require visual spotting to distinguish from a real target. Decoy containers will typically have their heading pointing in the direction in which they are moving, which is not necessarily typical behaviour for Marauders.

== Visual ==
<div style="float: right; width: 50%; padding: 20px">
[[File:MagicSmoke.png|alt=Smoke released by a dead shuttle in the testing range. |Smoke released by a dead shuttle in the testing range. ]]
Smoke (right) released by a dead shuttle in the testing range.
</div>
Ships within visual range will have their model revealed, which reveals their loadout and current state.
The ship's bridge lights switch to blue to amber when the ship has no more power (eg, all reactors disabled or destroyed)
External modules show black smoke and sparks when destroyed.

== Sound ==
'''[WIP]'''
Sounds can be used to learn information about the ship. You can hear sound effects near the location of your camera, regardless of how far any friendly ships may be from the location.

=== Alarms ===
Upon being destroyed, a ship typically sounds an evacuation alarm which will occur several seconds before lifepods get released.

=== Damage ===
Visible ships will play a certain sound effect when some of its components are damaged (hits on structure before structurebreak will not play this sound). The sound effect is not guaranteed to play every time the components are damaged''needs confirmation'', but is more likely to play when hit by high damage attacks.

The sound effect can only play once every 2.5 seconds, and will only play if the model is visible.

If a ship gets structurebroken, a damage sound effect is played immediately, ignoring the above restrictions.

=== Weapon Sounds ===
Most weapon types have unique sound effects when in use. Turrets have a distinctive sound when rotating, and missile tubes have distinctive sounds when launching missiles

=== Intercom Chatter ===
Intercom chatter can give clues to the status of a ship.

If the ship's model is visible and the player's viewpoint is close enough, radio chatter can be heard from the ship.

[transcript WIP]

Fire will have a smouldering, crackling sound, and either a visible external yellow/orange fire or white sparks (electrical fire). The two different vfx are only a visual difference, the fire behaves the same.

Atmosphere leak will have a hissing, air leak sort of sound and a bright white cloud appearance

== Notes ==
<references />

File:Heading.png

2024-06-23T13:55:47Z

76561198801434526: Image of a track with the heading and velocity vectors labelled.

== Summary ==
Image of a track with the heading and velocity vectors labelled.

Intelligence

2024-06-23T13:54:19Z

76561198801434526: /* Visual */ clarification of image caption

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
When a radar track is picked up, intelligence on this track will start being gathered by related components. As intelligence accumulates, more info will be provided on this track, such as ship internal condition, point defense condition, and CIC/weapons/thrusters condition.

<div style="clear: both"></div>
== Intel Effort ==
When a track is detected, ''intel effort'' will be used to identify the track. Only the ''intel effort'' statistic from the component with the highest ''intel effort'' is used.
For example, if a ship is being tracked by a Sprinter corvette with basic CIC(1pt/s), and the team has 2 Solomon battleship in communication range, with one fitting an intelligence center(15pt/s), and the other one also fitted with a analysis annex (15×(1+30%)=19.5pt/s), only the last Solomon's 19.5pt/s effort would be used.

Intel progress can be made on radar and visual tracks.<ref>Note that visual tracks are not transmitted over the network, which means remote intel like intel center will not work on them.</ref> Intel cannot be gathered on burn tracks or ELINT (but those tracks will show any previous intel gathered)

== Intel Packets ==
All ships initially have a identification difficulty of 200; this is the baseline size of intel packets.
If a ship has higher identification difficulty, packets sizes are scaled accordingly.
Track info is split into a couple of packets, with default identification difficulty of 200:
* Packet 1 is of size 200.
* Packet 2 is of size 250, reaching the end of packet 2 would require a total ''intel effort'' of 450 points.
* Update Packets are of size 400 per update, reaching the end of update packet 1 would require a total ''intel effort'' of 850 points.
The track info update would progress as follows:
{| class="wikitable"
|-
! Packet Type !! Track Information !! Effort Cost !! Cumulative Time For Basic CIC(1/s) !! Cumulative Time For Citadel CIC(4/s) !! Cumulative Time For Intelligence Center(15/s)
|-
| - || Track <nowiki>####</nowiki>-Unknown || 0 || 0s || 0s || 0s
|-
| Packet 1 || Warship || 200 || 200s || 50s || 13.3s
|-
| Packet 1 || Warship (Class) || 200 || 400s || 100s || 26.7s
|-
| Packet 1 || Class (Hull) || 200 || 600s || 150s || 40s
|-
| Packet 1 || Ship Name (Hull) || 200 || 800s || 200s || 53.3s
|-
| Packet 2 || Ship Name (Hull), Ship Status || 250 || 1050s || 262.5s || 70s
|-
| Packet 2 || Ship Name (Hull), Ship Status,% || 250 || 1300s || 325s || 86.7s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 1700s || 425s || 113.3s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 2100s || 525s || 140s
|-
| ... || ... || ... || ... || ... || ...
|}

The intel gathered is shared to the entire team, and if the component providing intel is lost, other intel sources can continue where it left off assuming they can see the track.<ref>It seems like all ships on the team can receive intel even if their comms are destroyed.</ref>

Missile intel is similar, but has packet sizes of 20, the first packet identifies that it's a missile and the second packet reveals specific name and seeker combo. The second packet will also incur a 0.1x multiplier on any intel work on it that isn't from a dedicated missile identifier (eg, intel center is reduced to 1.5 work/s, taking ~13 sec to get detailed report, but scryer still gets its full 10/s taking only 2 sec to get detailed report).

Once identified as a warship, the track's heading will be displayed as a line pointing out of the track in the tactical view.

== Ship Status ==
A ship track can have one of the following status displayed:
* '''EVACUATED''': Ship has been evacuated
* '''NOT UNDER COMMAND''': CIC is disabled or destroyed.
* '''IMMOBILISED''': Drives no longer operational.
* '''HARMLESS''': no offensive weapon available (EW included), either all are destroyed or the ship has no ammunition to fire.
Statuses higher on this list have priority and will be displayed over lower statuses.

However, please do note that ship status are only updated at each update packet. It is completely normal to see a ship under way with the status of '''IMMOBLISED''' or '''NOT UNDER COMMAND''' for some period due to how this mechanic works.

=== Intel Accuracy and Details ===

COND% is determined by the percentage of functioning components (''i.e'', any component that's above its functioning threshold), and adds or subtracts up to the intel accuracy<ref>As a result, intel accuracy is often better described as intel ''inaccuracy'', as a lower number is better</ref> to it (eg, a ship with two green components, and one red component will have COND: 66%, if the Intel source has 20% inaccuracy that number can vary from 46% to 86%)

Debuff count is just the amount of debuffs, plus minus multiplied by the inaccuracy (''e.g.'' a ship with 10 debuffs and a Intel accuracy of 20% will show anywhere from 8 to 12 debuffs)

PD% condition is similar to COND%, but only looks at PD systems. Each PDT, decoy type, and PD missile type are counted as a component(''e.g.'', if a ship has 5 PDTs, chaff, flares, active decoys, and two types of PD missiles, every PDT getting knocked out but all decoys and PDMs functional will result in PD: 50%)

== Working on remote tracks ==

Most sources of intel can only work locally, which means that the intel source can only work on tracks that the ship itself sees. However, certain components such as intelligence centers can work on remote tracks, allowing them to work on all tracks that is shared to the ship by the team.

Note that the intel doesn't just work for the player bringing the intel center, it works for all players on the same team.

If an intel ship cannot recieve tracks (due to ships being comms jammed/comms off/comms destroyed), then it will not be able to work on that track.

Ships can still recieve intel if comms jammed or comms destroyed, as intel is a teamwide thing, with the information independent of the communication network''[possibly a bug]''

== EO Seeker Special Capability ==
If a ship class and/or hull type is identified, a EO seeker missile is capable of locking only onto such type of target if fired in TRK(track) mode.

== Re-Acquisition of a Lost Track ==
After a track is broken, if it is re-acquired more than 2.5km from its last known position, then it will be assigned with a new track number with no intel. This would force the track to go through all the intel packets again before detailed information is regained.
Likewise, if the track is re-established within 2.5km from the last known position, all information is preserved.

== Decoy Container ==
Decoy containers can mimic ship signatures of Ferrymans and Marauders. These decoy containers cannot be revealed by intel alone, and will require visual spotting to distinguish from a real target. Decoy containers will typically have their heading pointing in the direction in which they are moving, which is not necessarily typical behaviour for Marauders.

== Visual ==
<div style="float: right; width: 50%; padding: 20px">
[[File:MagicSmoke.png|alt=Smoke released by a dead shuttle in the testing range. |Smoke released by a dead shuttle in the testing range. ]]
Smoke (right) released by a dead shuttle in the testing range.
</div>
Ships within visual range will have their model revealed, which reveals their loadout and current state.
The ship's bridge lights switch to blue to amber when the ship has no more power (eg, all reactors disabled or destroyed)
External modules show black smoke and sparks when destroyed.

== Sound ==
'''[WIP]'''
Sounds can be used to learn information about the ship. You can hear sound effects near the location of your camera, regardless of how far any friendly ships may be from the location.

=== Alarms ===
Upon being destroyed, a ship typically sounds an evacuation alarm which will occur several seconds before lifepods get released.

=== Damage ===
Visible ships will play a certain sound effect when some of its components are damaged (hits on structure before structurebreak will not play this sound). The sound effect is not guaranteed to play every time the components are damaged''needs confirmation'', but is more likely to play when hit by high damage attacks.

The sound effect can only play once every 2.5 seconds, and will only play if the model is visible.

If a ship gets structurebroken, a damage sound effect is played immediately, ignoring the above restrictions.

=== Weapon Sounds ===
Most weapon types have unique sound effects when in use. Turrets have a distinctive sound when rotating, and missile tubes have distinctive sounds when launching missiles

=== Intercom Chatter ===
Intercom chatter can give clues to the status of a ship.

If the ship's model is visible and the player's viewpoint is close enough, radio chatter can be heard from the ship.

[transcript WIP]

Fire will have a smouldering, crackling sound, and either a visible external yellow/orange fire or white sparks (electrical fire). The two different vfx are only a visual difference, the fire behaves the same.

Atmosphere leak will have a hissing, air leak sort of sound and a bright white cloud appearance

== Notes ==
<references />

Intelligence

2024-06-23T13:53:34Z

76561198801434526: /* Visual */ added image of death smoke

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
When a radar track is picked up, intelligence on this track will start being gathered by related components. As intelligence accumulates, more info will be provided on this track, such as ship internal condition, point defense condition, and CIC/weapons/thrusters condition.

<div style="clear: both"></div>
== Intel Effort ==
When a track is detected, ''intel effort'' will be used to identify the track. Only the ''intel effort'' statistic from the component with the highest ''intel effort'' is used.
For example, if a ship is being tracked by a Sprinter corvette with basic CIC(1pt/s), and the team has 2 Solomon battleship in communication range, with one fitting an intelligence center(15pt/s), and the other one also fitted with a analysis annex (15×(1+30%)=19.5pt/s), only the last Solomon's 19.5pt/s effort would be used.

Intel progress can be made on radar and visual tracks.<ref>Note that visual tracks are not transmitted over the network, which means remote intel like intel center will not work on them.</ref> Intel cannot be gathered on burn tracks or ELINT (but those tracks will show any previous intel gathered)

== Intel Packets ==
All ships initially have a identification difficulty of 200; this is the baseline size of intel packets.
If a ship has higher identification difficulty, packets sizes are scaled accordingly.
Track info is split into a couple of packets, with default identification difficulty of 200:
* Packet 1 is of size 200.
* Packet 2 is of size 250, reaching the end of packet 2 would require a total ''intel effort'' of 450 points.
* Update Packets are of size 400 per update, reaching the end of update packet 1 would require a total ''intel effort'' of 850 points.
The track info update would progress as follows:
{| class="wikitable"
|-
! Packet Type !! Track Information !! Effort Cost !! Cumulative Time For Basic CIC(1/s) !! Cumulative Time For Citadel CIC(4/s) !! Cumulative Time For Intelligence Center(15/s)
|-
| - || Track <nowiki>####</nowiki>-Unknown || 0 || 0s || 0s || 0s
|-
| Packet 1 || Warship || 200 || 200s || 50s || 13.3s
|-
| Packet 1 || Warship (Class) || 200 || 400s || 100s || 26.7s
|-
| Packet 1 || Class (Hull) || 200 || 600s || 150s || 40s
|-
| Packet 1 || Ship Name (Hull) || 200 || 800s || 200s || 53.3s
|-
| Packet 2 || Ship Name (Hull), Ship Status || 250 || 1050s || 262.5s || 70s
|-
| Packet 2 || Ship Name (Hull), Ship Status,% || 250 || 1300s || 325s || 86.7s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 1700s || 425s || 113.3s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 2100s || 525s || 140s
|-
| ... || ... || ... || ... || ... || ...
|}

The intel gathered is shared to the entire team, and if the component providing intel is lost, other intel sources can continue where it left off assuming they can see the track.<ref>It seems like all ships on the team can receive intel even if their comms are destroyed.</ref>

Missile intel is similar, but has packet sizes of 20, the first packet identifies that it's a missile and the second packet reveals specific name and seeker combo. The second packet will also incur a 0.1x multiplier on any intel work on it that isn't from a dedicated missile identifier (eg, intel center is reduced to 1.5 work/s, taking ~13 sec to get detailed report, but scryer still gets its full 10/s taking only 2 sec to get detailed report).

Once identified as a warship, the track's heading will be displayed as a line pointing out of the track in the tactical view.

== Ship Status ==
A ship track can have one of the following status displayed:
* '''EVACUATED''': Ship has been evacuated
* '''NOT UNDER COMMAND''': CIC is disabled or destroyed.
* '''IMMOBILISED''': Drives no longer operational.
* '''HARMLESS''': no offensive weapon available (EW included), either all are destroyed or the ship has no ammunition to fire.
Statuses higher on this list have priority and will be displayed over lower statuses.

However, please do note that ship status are only updated at each update packet. It is completely normal to see a ship under way with the status of '''IMMOBLISED''' or '''NOT UNDER COMMAND''' for some period due to how this mechanic works.

=== Intel Accuracy and Details ===

COND% is determined by the percentage of functioning components (''i.e'', any component that's above its functioning threshold), and adds or subtracts up to the intel accuracy<ref>As a result, intel accuracy is often better described as intel ''inaccuracy'', as a lower number is better</ref> to it (eg, a ship with two green components, and one red component will have COND: 66%, if the Intel source has 20% inaccuracy that number can vary from 46% to 86%)

Debuff count is just the amount of debuffs, plus minus multiplied by the inaccuracy (''e.g.'' a ship with 10 debuffs and a Intel accuracy of 20% will show anywhere from 8 to 12 debuffs)

PD% condition is similar to COND%, but only looks at PD systems. Each PDT, decoy type, and PD missile type are counted as a component(''e.g.'', if a ship has 5 PDTs, chaff, flares, active decoys, and two types of PD missiles, every PDT getting knocked out but all decoys and PDMs functional will result in PD: 50%)

== Working on remote tracks ==

Most sources of intel can only work locally, which means that the intel source can only work on tracks that the ship itself sees. However, certain components such as intelligence centers can work on remote tracks, allowing them to work on all tracks that is shared to the ship by the team.

Note that the intel doesn't just work for the player bringing the intel center, it works for all players on the same team.

If an intel ship cannot recieve tracks (due to ships being comms jammed/comms off/comms destroyed), then it will not be able to work on that track.

Ships can still recieve intel if comms jammed or comms destroyed, as intel is a teamwide thing, with the information independent of the communication network''[possibly a bug]''

== EO Seeker Special Capability ==
If a ship class and/or hull type is identified, a EO seeker missile is capable of locking only onto such type of target if fired in TRK(track) mode.

== Re-Acquisition of a Lost Track ==
After a track is broken, if it is re-acquired more than 2.5km from its last known position, then it will be assigned with a new track number with no intel. This would force the track to go through all the intel packets again before detailed information is regained.
Likewise, if the track is re-established within 2.5km from the last known position, all information is preserved.

== Decoy Container ==
Decoy containers can mimic ship signatures of Ferrymans and Marauders. These decoy containers cannot be revealed by intel alone, and will require visual spotting to distinguish from a real target. Decoy containers will typically have their heading pointing in the direction in which they are moving, which is not necessarily typical behaviour for Marauders.

== Visual ==
<div style="float: right; width: 50%; padding: 20px">
[[File:MagicSmoke.png|alt=Smoke released by a dead shuttle in the testing range. |Smoke released by a dead shuttle in the testing range. ]]
Smoke released by a dead shuttle in the testing range.
</div>
Ships within visual range will have their model revealed, which reveals their loadout and current state.
The ship's bridge lights switch to blue to amber when the ship has no more power (eg, all reactors disabled or destroyed)
External modules show black smoke and sparks when destroyed.

== Sound ==
'''[WIP]'''
Sounds can be used to learn information about the ship. You can hear sound effects near the location of your camera, regardless of how far any friendly ships may be from the location.

=== Alarms ===
Upon being destroyed, a ship typically sounds an evacuation alarm which will occur several seconds before lifepods get released.

=== Damage ===
Visible ships will play a certain sound effect when some of its components are damaged (hits on structure before structurebreak will not play this sound). The sound effect is not guaranteed to play every time the components are damaged''needs confirmation'', but is more likely to play when hit by high damage attacks.

The sound effect can only play once every 2.5 seconds, and will only play if the model is visible.

If a ship gets structurebroken, a damage sound effect is played immediately, ignoring the above restrictions.

=== Weapon Sounds ===
Most weapon types have unique sound effects when in use. Turrets have a distinctive sound when rotating, and missile tubes have distinctive sounds when launching missiles

=== Intercom Chatter ===
Intercom chatter can give clues to the status of a ship.

If the ship's model is visible and the player's viewpoint is close enough, radio chatter can be heard from the ship.

[transcript WIP]

Fire will have a smouldering, crackling sound, and either a visible external yellow/orange fire or white sparks (electrical fire). The two different vfx are only a visual difference, the fire behaves the same.

Atmosphere leak will have a hissing, air leak sort of sound and a bright white cloud appearance

== Notes ==
<references />

File:MagicSmoke.png

2024-06-23T13:50:56Z

76561198801434526: Smoke released by a dead shuttle in the testing range.

== Summary ==
Smoke released by a dead shuttle in the testing range.

Intelligence

2024-06-23T13:25:03Z

76561198801434526: Added notes section

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
When a radar track is picked up, intelligence on this track will start being gathered by related components. As intelligence accumulates, more info will be provided on this track, such as ship internal condition, point defense condition, and CIC/weapons/thrusters condition.

<div style="clear: both"></div>
== Intel Effort ==
When a track is detected, ''intel effort'' will be used to identify the track. Only the ''intel effort'' statistic from the component with the highest ''intel effort'' is used.
For example, if a ship is being tracked by a Sprinter corvette with basic CIC(1pt/s), and the team has 2 Solomon battleship in communication range, with one fitting an intelligence center(15pt/s), and the other one also fitted with a analysis annex (15×(1+30%)=19.5pt/s), only the last Solomon's 19.5pt/s effort would be used.

Intel progress can be made on radar and visual tracks.<ref>Note that visual tracks are not transmitted over the network, which means remote intel like intel center will not work on them.</ref> Intel cannot be gathered on burn tracks or ELINT (but those tracks will show any previous intel gathered)

== Intel Packets ==
All ships initially have a identification difficulty of 200; this is the baseline size of intel packets.
If a ship has higher identification difficulty, packets sizes are scaled accordingly.
Track info is split into a couple of packets, with default identification difficulty of 200:
* Packet 1 is of size 200.
* Packet 2 is of size 250, reaching the end of packet 2 would require a total ''intel effort'' of 450 points.
* Update Packets are of size 400 per update, reaching the end of update packet 1 would require a total ''intel effort'' of 850 points.
The track info update would progress as follows:
{| class="wikitable"
|-
! Packet Type !! Track Information !! Effort Cost !! Cumulative Time For Basic CIC(1/s) !! Cumulative Time For Citadel CIC(4/s) !! Cumulative Time For Intelligence Center(15/s)
|-
| - || Track <nowiki>####</nowiki>-Unknown || 0 || 0s || 0s || 0s
|-
| Packet 1 || Warship || 200 || 200s || 50s || 13.3s
|-
| Packet 1 || Warship (Class) || 200 || 400s || 100s || 26.7s
|-
| Packet 1 || Class (Hull) || 200 || 600s || 150s || 40s
|-
| Packet 1 || Ship Name (Hull) || 200 || 800s || 200s || 53.3s
|-
| Packet 2 || Ship Name (Hull), Ship Status || 250 || 1050s || 262.5s || 70s
|-
| Packet 2 || Ship Name (Hull), Ship Status,% || 250 || 1300s || 325s || 86.7s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 1700s || 425s || 113.3s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 2100s || 525s || 140s
|-
| ... || ... || ... || ... || ... || ...
|}

The intel gathered is shared to the entire team, and if the component providing intel is lost, other intel sources can continue where it left off assuming they can see the track.<ref>It seems like all ships on the team can receive intel even if their comms are destroyed.</ref>

Missile intel is similar, but has packet sizes of 20, the first packet identifies that it's a missile and the second packet reveals specific name and seeker combo. The second packet will also incur a 0.1x multiplier on any intel work on it that isn't from a dedicated missile identifier (eg, intel center is reduced to 1.5 work/s, taking ~13 sec to get detailed report, but scryer still gets its full 10/s taking only 2 sec to get detailed report).

Once identified as a warship, the track's heading will be displayed as a line pointing out of the track in the tactical view.

== Ship Status ==
A ship track can have one of the following status displayed:
* '''EVACUATED''': Ship has been evacuated
* '''NOT UNDER COMMAND''': CIC is disabled or destroyed.
* '''IMMOBILISED''': Drives no longer operational.
* '''HARMLESS''': no offensive weapon available (EW included), either all are destroyed or the ship has no ammunition to fire.
Statuses higher on this list have priority and will be displayed over lower statuses.

However, please do note that ship status are only updated at each update packet. It is completely normal to see a ship under way with the status of '''IMMOBLISED''' or '''NOT UNDER COMMAND''' for some period due to how this mechanic works.

=== Intel Accuracy and Details ===

COND% is determined by the percentage of functioning components (''i.e'', any component that's above its functioning threshold), and adds or subtracts up to the intel accuracy<ref>As a result, intel accuracy is often better described as intel ''inaccuracy'', as a lower number is better</ref> to it (eg, a ship with two green components, and one red component will have COND: 66%, if the Intel source has 20% inaccuracy that number can vary from 46% to 86%)

Debuff count is just the amount of debuffs, plus minus multiplied by the inaccuracy (''e.g.'' a ship with 10 debuffs and a Intel accuracy of 20% will show anywhere from 8 to 12 debuffs)

PD% condition is similar to COND%, but only looks at PD systems. Each PDT, decoy type, and PD missile type are counted as a component(''e.g.'', if a ship has 5 PDTs, chaff, flares, active decoys, and two types of PD missiles, every PDT getting knocked out but all decoys and PDMs functional will result in PD: 50%)

== Working on remote tracks ==

Most sources of intel can only work locally, which means that the intel source can only work on tracks that the ship itself sees. However, certain components such as intelligence centers can work on remote tracks, allowing them to work on all tracks that is shared to the ship by the team.

Note that the intel doesn't just work for the player bringing the intel center, it works for all players on the same team.

If an intel ship cannot recieve tracks (due to ships being comms jammed/comms off/comms destroyed), then it will not be able to work on that track.

Ships can still recieve intel if comms jammed or comms destroyed, as intel is a teamwide thing, with the information independent of the communication network''[possibly a bug]''

== EO Seeker Special Capability ==
If a ship class and/or hull type is identified, a EO seeker missile is capable of locking only onto such type of target if fired in TRK(track) mode.

== Re-Acquisition of a Lost Track ==
After a track is broken, if it is re-acquired more than 2.5km from its last known position, then it will be assigned with a new track number with no intel. This would force the track to go through all the intel packets again before detailed information is regained.
Likewise, if the track is re-established within 2.5km from the last known position, all information is preserved.

== Decoy Container ==
Decoy containers can mimic ship signatures of Ferrymans and Marauders. These decoy containers cannot be revealed by intel alone, and will require visual spotting to distinguish from a real target. Decoy containers will typically have their heading pointing in the direction in which they are moving, which is not necessarily typical behaviour for Marauders.

== Visual ==
Ships within visual range will have their model revealed, which reveals their loadout and current state.
The ship's bridge lights switch to blue to amber when the ship has no more power (eg, all reactors disabled or destroyed)
External modules show black smoke and sparks when destroyed.

== Sound ==
'''[WIP]'''
Sounds can be used to learn information about the ship. You can hear sound effects near the location of your camera, regardless of how far any friendly ships may be from the location.

=== Alarms ===
Upon being destroyed, a ship typically sounds an evacuation alarm which will occur several seconds before lifepods get released.

=== Damage ===
Visible ships will play a certain sound effect when some of its components are damaged (hits on structure before structurebreak will not play this sound). The sound effect is not guaranteed to play every time the components are damaged''needs confirmation'', but is more likely to play when hit by high damage attacks.

The sound effect can only play once every 2.5 seconds, and will only play if the model is visible.

If a ship gets structurebroken, a damage sound effect is played immediately, ignoring the above restrictions.

=== Weapon Sounds ===
Most weapon types have unique sound effects when in use. Turrets have a distinctive sound when rotating, and missile tubes have distinctive sounds when launching missiles

=== Intercom Chatter ===
Intercom chatter can give clues to the status of a ship.

If the ship's model is visible and the player's viewpoint is close enough, radio chatter can be heard from the ship.

[transcript WIP]

Fire will have a smouldering, crackling sound, and either a visible external yellow/orange fire or white sparks (electrical fire). The two different vfx are only a visual difference, the fire behaves the same.

Atmosphere leak will have a hissing, air leak sort of sound and a bright white cloud appearance

== Notes ==
<references />

Intelligence

2024-06-23T13:24:24Z

76561198801434526: /* Sound */ formatting fix

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
When a radar track is picked up, intelligence on this track will start being gathered by related components. As intelligence accumulates, more info will be provided on this track, such as ship internal condition, point defense condition, and CIC/weapons/thrusters condition.

<div style="clear: both"></div>
== Intel Effort ==
When a track is detected, ''intel effort'' will be used to identify the track. Only the ''intel effort'' statistic from the component with the highest ''intel effort'' is used.
For example, if a ship is being tracked by a Sprinter corvette with basic CIC(1pt/s), and the team has 2 Solomon battleship in communication range, with one fitting an intelligence center(15pt/s), and the other one also fitted with a analysis annex (15×(1+30%)=19.5pt/s), only the last Solomon's 19.5pt/s effort would be used.

Intel progress can be made on radar and visual tracks.<ref>Note that visual tracks are not transmitted over the network, which means remote intel like intel center will not work on them.</ref> Intel cannot be gathered on burn tracks or ELINT (but those tracks will show any previous intel gathered)

== Intel Packets ==
All ships initially have a identification difficulty of 200; this is the baseline size of intel packets.
If a ship has higher identification difficulty, packets sizes are scaled accordingly.
Track info is split into a couple of packets, with default identification difficulty of 200:
* Packet 1 is of size 200.
* Packet 2 is of size 250, reaching the end of packet 2 would require a total ''intel effort'' of 450 points.
* Update Packets are of size 400 per update, reaching the end of update packet 1 would require a total ''intel effort'' of 850 points.
The track info update would progress as follows:
{| class="wikitable"
|-
! Packet Type !! Track Information !! Effort Cost !! Cumulative Time For Basic CIC(1/s) !! Cumulative Time For Citadel CIC(4/s) !! Cumulative Time For Intelligence Center(15/s)
|-
| - || Track <nowiki>####</nowiki>-Unknown || 0 || 0s || 0s || 0s
|-
| Packet 1 || Warship || 200 || 200s || 50s || 13.3s
|-
| Packet 1 || Warship (Class) || 200 || 400s || 100s || 26.7s
|-
| Packet 1 || Class (Hull) || 200 || 600s || 150s || 40s
|-
| Packet 1 || Ship Name (Hull) || 200 || 800s || 200s || 53.3s
|-
| Packet 2 || Ship Name (Hull), Ship Status || 250 || 1050s || 262.5s || 70s
|-
| Packet 2 || Ship Name (Hull), Ship Status,% || 250 || 1300s || 325s || 86.7s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 1700s || 425s || 113.3s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 2100s || 525s || 140s
|-
| ... || ... || ... || ... || ... || ...
|}

The intel gathered is shared to the entire team, and if the component providing intel is lost, other intel sources can continue where it left off assuming they can see the track.<ref>It seems like all ships on the team can receive intel even if their comms are destroyed.</ref>

Missile intel is similar, but has packet sizes of 20, the first packet identifies that it's a missile and the second packet reveals specific name and seeker combo. The second packet will also incur a 0.1x multiplier on any intel work on it that isn't from a dedicated missile identifier (eg, intel center is reduced to 1.5 work/s, taking ~13 sec to get detailed report, but scryer still gets its full 10/s taking only 2 sec to get detailed report).

Once identified as a warship, the track's heading will be displayed as a line pointing out of the track in the tactical view.

== Ship Status ==
A ship track can have one of the following status displayed:
* '''EVACUATED''': Ship has been evacuated
* '''NOT UNDER COMMAND''': CIC is disabled or destroyed.
* '''IMMOBILISED''': Drives no longer operational.
* '''HARMLESS''': no offensive weapon available (EW included), either all are destroyed or the ship has no ammunition to fire.
Statuses higher on this list have priority and will be displayed over lower statuses.

However, please do note that ship status are only updated at each update packet. It is completely normal to see a ship under way with the status of '''IMMOBLISED''' or '''NOT UNDER COMMAND''' for some period due to how this mechanic works.

=== Intel Accuracy and Details ===

COND% is determined by the percentage of functioning components (''i.e'', any component that's above its functioning threshold), and adds or subtracts up to the intel accuracy<ref>As a result, intel accuracy is often better described as intel ''inaccuracy'', as a lower number is better</ref> to it (eg, a ship with two green components, and one red component will have COND: 66%, if the Intel source has 20% inaccuracy that number can vary from 46% to 86%)

Debuff count is just the amount of debuffs, plus minus multiplied by the inaccuracy (''e.g.'' a ship with 10 debuffs and a Intel accuracy of 20% will show anywhere from 8 to 12 debuffs)

PD% condition is similar to COND%, but only looks at PD systems. Each PDT, decoy type, and PD missile type are counted as a component(''e.g.'', if a ship has 5 PDTs, chaff, flares, active decoys, and two types of PD missiles, every PDT getting knocked out but all decoys and PDMs functional will result in PD: 50%)

== Working on remote tracks ==

Most sources of intel can only work locally, which means that the intel source can only work on tracks that the ship itself sees. However, certain components such as intelligence centers can work on remote tracks, allowing them to work on all tracks that is shared to the ship by the team.

Note that the intel doesn't just work for the player bringing the intel center, it works for all players on the same team.

If an intel ship cannot recieve tracks (due to ships being comms jammed/comms off/comms destroyed), then it will not be able to work on that track.

Ships can still recieve intel if comms jammed or comms destroyed, as intel is a teamwide thing, with the information independent of the communication network''[possibly a bug]''

== EO Seeker Special Capability ==
If a ship class and/or hull type is identified, a EO seeker missile is capable of locking only onto such type of target if fired in TRK(track) mode.

== Re-Acquisition of a Lost Track ==
After a track is broken, if it is re-acquired more than 2.5km from its last known position, then it will be assigned with a new track number with no intel. This would force the track to go through all the intel packets again before detailed information is regained.
Likewise, if the track is re-established within 2.5km from the last known position, all information is preserved.

== Decoy Container ==
Decoy containers can mimic ship signatures of Ferrymans and Marauders. These decoy containers cannot be revealed by intel alone, and will require visual spotting to distinguish from a real target. Decoy containers will typically have their heading pointing in the direction in which they are moving, which is not necessarily typical behaviour for Marauders.

== Visual ==
Ships within visual range will have their model revealed, which reveals their loadout and current state.
The ship's bridge lights switch to blue to amber when the ship has no more power (eg, all reactors disabled or destroyed)
External modules show black smoke and sparks when destroyed.

== Sound ==
'''[WIP]'''
Sounds can be used to learn information about the ship. You can hear sound effects near the location of your camera, regardless of how far any friendly ships may be from the location.

=== Alarms ===
Upon being destroyed, a ship typically sounds an evacuation alarm which will occur several seconds before lifepods get released.

=== Damage ===
Visible ships will play a certain sound effect when some of its components are damaged (hits on structure before structurebreak will not play this sound). The sound effect is not guaranteed to play every time the components are damaged''needs confirmation'', but is more likely to play when hit by high damage attacks.

The sound effect can only play once every 2.5 seconds, and will only play if the model is visible.

If a ship gets structurebroken, a damage sound effect is played immediately, ignoring the above restrictions.

=== Weapon Sounds ===
Most weapon types have unique sound effects when in use. Turrets have a distinctive sound when rotating, and missile tubes have distinctive sounds when launching missiles

=== Intercom Chatter ===
Intercom chatter can give clues to the status of a ship.

If the ship's model is visible and the player's viewpoint is close enough, radio chatter can be heard from the ship.

[transcript WIP]

Fire will have a smouldering, crackling sound, and either a visible external yellow/orange fire or white sparks (electrical fire). The two different vfx are only a visual difference, the fire behaves the same.

Atmosphere leak will have a hissing, air leak sort of sound and a bright white cloud appearance

Intelligence

2024-06-23T13:22:56Z

76561198801434526: created intel page

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
When a radar track is picked up, intelligence on this track will start being gathered by related components. As intelligence accumulates, more info will be provided on this track, such as ship internal condition, point defense condition, and CIC/weapons/thrusters condition.

<div style="clear: both"></div>
== Intel Effort ==
When a track is detected, ''intel effort'' will be used to identify the track. Only the ''intel effort'' statistic from the component with the highest ''intel effort'' is used.
For example, if a ship is being tracked by a Sprinter corvette with basic CIC(1pt/s), and the team has 2 Solomon battleship in communication range, with one fitting an intelligence center(15pt/s), and the other one also fitted with a analysis annex (15×(1+30%)=19.5pt/s), only the last Solomon's 19.5pt/s effort would be used.

Intel progress can be made on radar and visual tracks.<ref>Note that visual tracks are not transmitted over the network, which means remote intel like intel center will not work on them.</ref> Intel cannot be gathered on burn tracks or ELINT (but those tracks will show any previous intel gathered)

== Intel Packets ==
All ships initially have a identification difficulty of 200; this is the baseline size of intel packets.
If a ship has higher identification difficulty, packets sizes are scaled accordingly.
Track info is split into a couple of packets, with default identification difficulty of 200:
* Packet 1 is of size 200.
* Packet 2 is of size 250, reaching the end of packet 2 would require a total ''intel effort'' of 450 points.
* Update Packets are of size 400 per update, reaching the end of update packet 1 would require a total ''intel effort'' of 850 points.
The track info update would progress as follows:
{| class="wikitable"
|-
! Packet Type !! Track Information !! Effort Cost !! Cumulative Time For Basic CIC(1/s) !! Cumulative Time For Citadel CIC(4/s) !! Cumulative Time For Intelligence Center(15/s)
|-
| - || Track <nowiki>####</nowiki>-Unknown || 0 || 0s || 0s || 0s
|-
| Packet 1 || Warship || 200 || 200s || 50s || 13.3s
|-
| Packet 1 || Warship (Class) || 200 || 400s || 100s || 26.7s
|-
| Packet 1 || Class (Hull) || 200 || 600s || 150s || 40s
|-
| Packet 1 || Ship Name (Hull) || 200 || 800s || 200s || 53.3s
|-
| Packet 2 || Ship Name (Hull), Ship Status || 250 || 1050s || 262.5s || 70s
|-
| Packet 2 || Ship Name (Hull), Ship Status,% || 250 || 1300s || 325s || 86.7s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 1700s || 425s || 113.3s
|-
| Update Packet || Ship Name (Hull), Ship Status,% || 400 || 2100s || 525s || 140s
|-
| ... || ... || ... || ... || ... || ...
|}

The intel gathered is shared to the entire team, and if the component providing intel is lost, other intel sources can continue where it left off assuming they can see the track.<ref>It seems like all ships on the team can receive intel even if their comms are destroyed.</ref>

Missile intel is similar, but has packet sizes of 20, the first packet identifies that it's a missile and the second packet reveals specific name and seeker combo. The second packet will also incur a 0.1x multiplier on any intel work on it that isn't from a dedicated missile identifier (eg, intel center is reduced to 1.5 work/s, taking ~13 sec to get detailed report, but scryer still gets its full 10/s taking only 2 sec to get detailed report).

Once identified as a warship, the track's heading will be displayed as a line pointing out of the track in the tactical view.

== Ship Status ==
A ship track can have one of the following status displayed:
* '''EVACUATED''': Ship has been evacuated
* '''NOT UNDER COMMAND''': CIC is disabled or destroyed.
* '''IMMOBILISED''': Drives no longer operational.
* '''HARMLESS''': no offensive weapon available (EW included), either all are destroyed or the ship has no ammunition to fire.
Statuses higher on this list have priority and will be displayed over lower statuses.

However, please do note that ship status are only updated at each update packet. It is completely normal to see a ship under way with the status of '''IMMOBLISED''' or '''NOT UNDER COMMAND''' for some period due to how this mechanic works.

=== Intel Accuracy and Details ===

COND% is determined by the percentage of functioning components (''i.e'', any component that's above its functioning threshold), and adds or subtracts up to the intel accuracy<ref>As a result, intel accuracy is often better described as intel ''inaccuracy'', as a lower number is better</ref> to it (eg, a ship with two green components, and one red component will have COND: 66%, if the Intel source has 20% inaccuracy that number can vary from 46% to 86%)

Debuff count is just the amount of debuffs, plus minus multiplied by the inaccuracy (''e.g.'' a ship with 10 debuffs and a Intel accuracy of 20% will show anywhere from 8 to 12 debuffs)

PD% condition is similar to COND%, but only looks at PD systems. Each PDT, decoy type, and PD missile type are counted as a component(''e.g.'', if a ship has 5 PDTs, chaff, flares, active decoys, and two types of PD missiles, every PDT getting knocked out but all decoys and PDMs functional will result in PD: 50%)

== Working on remote tracks ==

Most sources of intel can only work locally, which means that the intel source can only work on tracks that the ship itself sees. However, certain components such as intelligence centers can work on remote tracks, allowing them to work on all tracks that is shared to the ship by the team.

Note that the intel doesn't just work for the player bringing the intel center, it works for all players on the same team.

If an intel ship cannot recieve tracks (due to ships being comms jammed/comms off/comms destroyed), then it will not be able to work on that track.

Ships can still recieve intel if comms jammed or comms destroyed, as intel is a teamwide thing, with the information independent of the communication network''[possibly a bug]''

== EO Seeker Special Capability ==
If a ship class and/or hull type is identified, a EO seeker missile is capable of locking only onto such type of target if fired in TRK(track) mode.

== Re-Acquisition of a Lost Track ==
After a track is broken, if it is re-acquired more than 2.5km from its last known position, then it will be assigned with a new track number with no intel. This would force the track to go through all the intel packets again before detailed information is regained.
Likewise, if the track is re-established within 2.5km from the last known position, all information is preserved.

== Decoy Container ==
Decoy containers can mimic ship signatures of Ferrymans and Marauders. These decoy containers cannot be revealed by intel alone, and will require visual spotting to distinguish from a real target. Decoy containers will typically have their heading pointing in the direction in which they are moving, which is not necessarily typical behaviour for Marauders.

== Visual ==
Ships within visual range will have their model revealed, which reveals their loadout and current state.
The ship's bridge lights switch to blue to amber when the ship has no more power (eg, all reactors disabled or destroyed)
External modules show black smoke and sparks when destroyed.

== Sound ==
**[WIP]**
Sounds can be used to learn information about the ship. You can hear sound effects near the location of your camera, regardless of how far any friendly ships may be from the location.

=== Alarms ===
Upon being destroyed, a ship typically sounds an evacuation alarm which will occur several seconds before lifepods get released.

=== Damage ===
Visible ships will play a certain sound effect when some of its components are damaged (hits on structure before structurebreak will not play this sound). The sound effect is not guaranteed to play every time the components are damaged''needs confirmation'', but is more likely to play when hit by high damage attacks.

The sound effect can only play once every 2.5 seconds, and will only play if the model is visible.

If a ship gets structurebroken, a damage sound effect is played immediately, ignoring the above restrictions.

=== Weapon Sounds ===
Most weapon types have unique sound effects when in use. Turrets have a distinctive sound when rotating, and missile tubes have distinctive sounds when launching missiles

=== Intercom Chatter ===
Intercom chatter can give clues to the status of a ship.

If the ship's model is visible and the player's viewpoint is close enough, radio chatter can be heard from the ship.

[transcript WIP]

Fire will have a smouldering, crackling sound, and either a visible external yellow/orange fire or white sparks (electrical fire). The two different vfx are only a visual difference, the fire behaves the same.

Atmosphere leak will have a hissing, air leak sort of sound and a bright white cloud appearance

Console Commands

2024-06-22T20:25:29Z

76561198801434526: /* Using the Console */ fixed formatting

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
 
 
 

There are many console commands that you can use to aid testing in single player mode.

<div style="clear: both"></div>
== Using the Console ==
To use any of the console commands, first press F2 to open the console. Here you can use a list of commands to alter game mechanics and make testing more convenient.
Be advised that you can use TAB for auto-complete, but you cannot click or select prompted command. Some commands require a argument to function.
Pressing the up/down arrow key would allow you to select formerly used commands, this command history function preserves throughout game session. i.e. Game will not purge history unless you restart the game.
After you are done with the console, click bottom right close button to close the console.

== Available Commands ==
All commands are case sensitive. Default options are encapsulated with [], all options are reset after each combat.
For Example:
<nowiki>exampleCommand notDefaultOption/[defaultOption]</nowiki>

* <nowiki>dbgBotPause True/[False]</nowiki>
** Stops AI from issuing new commands to AI ships, may cause AI to drift around.
* dbgBotIdleAllUnits
** Order all AI ships to abandon all orders and idle, used in combo with dbgBotPause.
* <nowiki>dbgEnableEnemyControl True/[False]</nowiki>
** Allow you to control hostile AI ships, with some limitations:
*** You cannot fire on track from hostile AI ships, only fire on position is available.
*** You cannot see its damage control panel.
* <nowiki>dbgSuspendVisibility True/[False]</nowiki>
** Make all ship hulls always visible, useful for evaluating missile/gun performance.
* time-scale INTEGER
** Make time flows INTEGER times faster, useful for speedup maneuvering and others. It is not advised to speed this past 20.
** Using active pause would reset time scale.
* dbgForceDebuff
** Forces the next penetrating hit (counts for any hit in the game) to cause a debuff
* dbgForceRareDebuff
** Similar to above, but forces a rare debuff instead (aka, a catastrophic event)
* Commands
** Will give you a list of all available commands in games.

[TODO]list more useful console commands

== Getting Help ==
If you need help using a command. Type 'man COMMAND'. For example, if you need help for the 'man' command, type 'man man'.
For getting deeper into console mastering, try 'help'.

Console Commands

2024-06-22T20:24:54Z

76561198801434526: created page

<div style="float: left; padding-right: 20px;">
__TOC__
</div>
 
 
 

There are many console commands that you can use to aid testing in single player mode.

<div style="clear: both"></div>
== Using the Console ==
To use any of the console commands, first press F2 to open the console. Here you can use a list of commands to alter game mechanics and make testing more convenient.
Be advised that you **CAN** use Tab for auto-complete, but you cannot click or select prompted command. Some commands require a argument to function.
Pressing the up/down arrow key would allow you to select formerly used commands, this command history function preserves throughout game session. i.e. Game will not purge history unless you restart the game.
After you are done with the console, click bottom right close button to close the console.

== Available Commands ==
All commands are case sensitive. Default options are encapsulated with [], all options are reset after each combat.
For Example:
<nowiki>exampleCommand notDefaultOption/[defaultOption]</nowiki>

* <nowiki>dbgBotPause True/[False]</nowiki>
** Stops AI from issuing new commands to AI ships, may cause AI to drift around.
* dbgBotIdleAllUnits
** Order all AI ships to abandon all orders and idle, used in combo with dbgBotPause.
* <nowiki>dbgEnableEnemyControl True/[False]</nowiki>
** Allow you to control hostile AI ships, with some limitations:
*** You cannot fire on track from hostile AI ships, only fire on position is available.
*** You cannot see its damage control panel.
* <nowiki>dbgSuspendVisibility True/[False]</nowiki>
** Make all ship hulls always visible, useful for evaluating missile/gun performance.
* time-scale INTEGER
** Make time flows INTEGER times faster, useful for speedup maneuvering and others. It is not advised to speed this past 20.
** Using active pause would reset time scale.
* dbgForceDebuff
** Forces the next penetrating hit (counts for any hit in the game) to cause a debuff
* dbgForceRareDebuff
** Similar to above, but forces a rare debuff instead (aka, a catastrophic event)
* Commands
** Will give you a list of all available commands in games.

[TODO]list more useful console commands

== Getting Help ==
If you need help using a command. Type 'man COMMAND'. For example, if you need help for the 'man' command, type 'man man'.
For getting deeper into console mastering, try 'help'.

Munitions & Missiles

2024-06-22T20:00:05Z

76561198801434526: /* Missile Construction */ fixed capitalization

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [[#Point_Defense_Missile_Setting | Point Defense Missile Setting]] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID). The threat types of some special missiles are listed below.
* Containers: Size 3 conventional
* R-2 Rockets: Size 1 conventional
* Mines: Size 3 conventional

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! Wall Thickness
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.5 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 0.5 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 2.5 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.5 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 0.5 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 2.0 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [[munition:m-30-mattock-mine | M-30 Mattock Mine]]
* [[munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]]
* [[munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [[munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]]
* [[munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [[Electronic_Warfare#Soft_Kill_Decoys | Soft Kill Decoys]].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:59:36Z

76561198801434526: /* Missile Construction */ Added wall thickness to missile table

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [[#Point_Defense_Missile_Setting | Point Defense Missile Setting]] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID). The threat types of some special missiles are listed below.
* Containers: Size 3 conventional
* R-2 Rockets: Size 1 conventional
* Mines: Size 3 conventional

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! Wall thickness
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.5 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 0.5 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 2.5 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.5 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 0.5 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 2.0 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [[munition:m-30-mattock-mine | M-30 Mattock Mine]]
* [[munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]]
* [[munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [[munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]]
* [[munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [[Electronic_Warfare#Soft_Kill_Decoys | Soft Kill Decoys]].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:54:14Z

76561198801434526: /* Threat Size */ added special missile sizes

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [[#Point_Defense_Missile_Setting | Point Defense Missile Setting]] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID). The threat types of some special missiles are listed below.
* Containers: Size 3 conventional
* R-2 Rockets: Size 1 conventional
* Mines: Size 3 conventional

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [[munition:m-30-mattock-mine | M-30 Mattock Mine]]
* [[munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]]
* [[munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [[munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]]
* [[munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [[Electronic_Warfare#Soft_Kill_Decoys | Soft Kill Decoys]].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:25:56Z

76561198801434526: /* Decoy Containers */ fixed link alias

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [[#Point_Defense_Missile_Setting | Point Defense Missile Setting]] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID).

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [[munition:m-30-mattock-mine | M-30 Mattock Mine]]
* [[munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]]
* [[munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [[munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]]
* [[munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [[Electronic_Warfare#Soft_Kill_Decoys | Soft Kill Decoys]].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:25:06Z

76561198801434526: /* External Links */ fixed link 3

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [[#Point_Defense_Missile_Setting | Point Defense Missile Setting]] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID).

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [[munition:m-30-mattock-mine | M-30 Mattock Mine]]
* [[munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]]
* [[munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [[munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]]
* [[munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [[Electronic_Warfare#Soft_Kill_Decoys]].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:24:48Z

76561198801434526: /* External Links */ fixed link 2

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [[#Point_Defense_Missile_Setting | Point Defense Missile Setting]] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID).

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [[munition:m-30-mattock-mine | M-30 Mattock Mine]]
* [[munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]]
* [[munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [[munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]]
* [[munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [[Electronic_Warfare#Soft_Kill_Decoys]].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html | Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:24:21Z

76561198801434526: /* External Links */ fixed link

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [[#Point_Defense_Missile_Setting | Point Defense Missile Setting]] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID).

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [[munition:m-30-mattock-mine | M-30 Mattock Mine]]
* [[munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]]
* [[munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [[munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]]
* [[munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [[Electronic_Warfare#Soft_Kill_Decoys]].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [[https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:23:54Z

76561198801434526: /* Special Missiles */ fixed links

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [[#Point_Defense_Missile_Setting | Point Defense Missile Setting]] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID).

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [[munition:m-30-mattock-mine | M-30 Mattock Mine]]
* [[munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]]
* [[munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [[munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]]
* [[munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [[Electronic_Warfare#Soft_Kill_Decoys]].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [*https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:23:08Z

76561198801434526: /* Defensive Missiles */ fixed link 2

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [[#Point_Defense_Missile_Setting | Point Defense Missile Setting]] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID).

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [munition:m-30-mattock-mine | M-30 Mattock Mine]
* [munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]
* [munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]
* [munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [Electronic_Warfare#Soft_Kill_Decoys].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [*https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:21:31Z

76561198801434526: /* Defensive Targeting Doctrine */ fixed link

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [#Point_Defense_Missile_Setting | Point Defense Missile Setting] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID).

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [munition:m-30-mattock-mine | M-30 Mattock Mine]
* [munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]
* [munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]
* [munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [Electronic_Warfare#Soft_Kill_Decoys].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [*https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T19:19:05Z

76561198801434526: /* Defensive Missiles */ fleshed-out defensive missiles section

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the [Missiles#Point_Defense_Missile_Setting | Point Defense Missile Setting] if Fire Mode is switched away from DCTRN/D.

===== Threat Size =====
Threat size controls which missile threats the AMM will automatically launch against. Size 1, 2, and/or 3 can be toggled on or off. There is an additional switch which allows the missile to target all missiles (ALL), conventional missiles only (CONV) and hybrid missiles only (HYBRID).

===== Size Ordering =====
The size ordering setting has three modes.
* '''DESCEND''': The missile will be fired at the largest valid threat size first before firing against smaller threats.
* '''ASCEND''': The missile will be fired at the smallest valid threat size first before firing against larger threats.
* '''EQUAL''': The missile launch sequence will be unaffected by threat size so long as it is the correct size.

===== Salvo Size =====
The salvo size setting controls whether 1, 2 or 3 AMMs will be fired at a threat.

===== Distance Priority =====
* '''NEAR-TO-FAR''': The missile will be fired at the closest threats first before firing against further threats.
* '''FAR-TO-NEAR''': The missile will be fired at the furthest threats first before firing against closer threats.

==== Point Defense Missile Setting ====
The Point Defense Missile Settings (PDMSL) are settings which control the behaviour of ships' and formations' AMMs and can override the AMMs' defensive targeting doctrines. The default values for these settings can be changed in the Settings screen off the Main Menu. These settings are abbreviated when displayed in the ship's control console (''e.g.'' Fire Mode DCTRN / Fire Policy 1 Salvo / Salvo Size 1 / Last Salvo Yes will be displayed as D 1 1 Y).

===== Firing Mode =====
The fire mode controls the logic that governs automatic launching of AMMs.
* '''DCTRN (D)''': The AMMs will launch automatically according to their defensive targeting doctrine.
* '''ALL (A)''': The AMMs will be indiscriminately launched against all nearby threats.
* '''MAN (M)''': AMMs will only launch against prioritized threats (ones the player has 'Z'+clicked on).

===== Fire Policy =====
The fire policy controls the number of salvoes launched against a threat (not including last salvo).
* '''1 Salvo (1)''': One salvo will be launched.
* '''2 Salvo (2)''': Two salvoes will be launched.
* '''MAX DOF (M)''': Follow-up salvoes will be launched after the previous salvo's India time (time to intercept) has elapsed until the threat is destroyed.

===== Salvo Size =====
Salvo size controls the number of AMMs launched in a single salvo against a threat.
* '''1 (1)''': One AMM will be fired pre salvo.
* '''2 (2)''': Two AMMs will be fired per salvo.
* '''3 (3)''': Three AMMs will be fired per salvo.
* '''DCTRN (D)''': The AMMs' salvo size setting will be followed.

===== Last Salvo =====
Last salvo controls whether or not a final salvo of missiles will be fired at the last possible moment regardless of fire policy or if other AMMs are in flight.
* '''YES (Y)''': A last salvo will be fired.
* '''NO (N)''': A last salvo will not be fired.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [munition:m-30-mattock-mine | M-30 Mattock Mine]
* [munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]
* [munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]
* [munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [Electronic_Warfare#Soft_Kill_Decoys].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [*https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T18:34:13Z

76561198801434526: /* Defensive Missiles */ Fleshing-out defensive missiles

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Defensive Targeting Doctrine (Missile) ====
Doctrine decides how defensive missiles are fired against incoming missiles. These settings can be overridden by the  if Fire Mode is switched away from DCTRN/D.

==== Point Defense Missile Setting (Setting) ====

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [munition:m-30-mattock-mine | M-30 Mattock Mine]
* [munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]
* [munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]
* [munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [Electronic_Warfare#Soft_Kill_Decoys].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [*https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T18:15:27Z

76561198801434526: Added special missiles

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

== Special Missiles ==
There are certain types of ammunition that could be loaded into launchers and operate just like missiles, but cannot be modified.

=== Mines ===
Mines are loitering traps that can be deployed to destroy passing ships and delay enemy movement

Upon deployment, mines will move up to 500m away. They take 90 seconds to arm, and are triggered by a magnetic detector. A non-friendly ship that comes within 2km will trigger the mine. Notably, the mine identifies friendly ships via Comms signal. If the comms signal is disrupted (''e.g.'' manually turning off comms, antenna destroyed from battle damage, mine jammed by comms jammer<ref>Mine comms are simillar to CMD and do not check for same jammer cone</ref>) the mine will not be able to identify the friendly ship and will trigger on it.

Unlike other missiles, the seeker on mines will not differentiate between friendly or hostile shops, even with comms on. A mine tripped by an enemy ship that then misses can then seek onto a friendly ship and hit it. In this case, friendly PD will not fire on the incoming mine.

Mines use an HEI payload, but with 100 damage fragments rather than 50 damage fragments

Mines have 40 hp, 2.0cm wall thickness

There are currently 3 types of mines in game, they are:
* [munition:m-30-mattock-mine | M-30 Mattock Mine]
* [munition:m-30-n-mattock-cooperative-mine | M-30-N Mattock Cooperative Mine]
* [munition:m-50-auger-sprint-mine | M-50 Auger Sprint Mine]

Mines can be deployed from a mine container; this container behaves similarly to a cruise missile but instead releases its payload at the end of the cruise path, distributing mines within a 2km sphere. The mine container itself has 50 and does not drop mines if it is prematurely destroyed.

=== Rockets ===
Rockets are unguided missiles. They are not perfectly accurate and will slightly drift off course over time

R-2 rockets have 8 health and 1.5cm wall thickness

=== Decoy Containers ===
* [munition:cm-4d1-decoy-container-clipper | CM-4D1 Decoy Container Clipper]
* [munition:cm-4d2-decoy-container-line-ship | CM-4D2 Decoy Container Line Ship]

Decoy containers are destroyed in exactly three hits, regardless of if the damage source is RPF or torpedo hits. These missiles are given a randomly generated name and take fleet prefixes friendly ships when being identified by enemy intelligence. For ship launched decoys designed to fool seekers, please refer to [Electronic_Warfare#Soft_Kill_Decoys].

== Trivia ==
* Missile number codes do not need to be filled out, a tempest can have the code SGM-21 or SGM-2 and the game will allow it. The game will also allow multiple missiles to have the same number (though same name missiles will overwrite templates)

== External Links ==
* [*https://rocketpuppy.github.io/Nebulous-Fleet-Command-Minmax-Tool/missile-engine-tuner.html Puppy's online missile engine tuner]

== Notes ==
<references />

Munitions & Missiles

2024-06-22T17:41:26Z

76561198801434526: updated heading levels for missile mechanics added wall thickness section

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

==== Mixed Salvos ====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

==== MLS Launcher ====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

=== Defensive Missiles ===
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

==== Doctrine ====
Doctrine decides how defensive missiles are fired against incoming missiles.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

==== Wall Thickness ====
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system.
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

Munitions & Missiles

2024-06-22T17:38:51Z

76561198801434526: /* Missile Mechanics */ added launching section

[[File:Missile Designer.png|thumb|400px|The missile designer]]
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.

== Missile Mechanics ==
=== Targeting ===
==== Target Selection Cycle ====
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".

* Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
** ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
** For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
* If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
** If the missile has multiple validators, every validator will check each target.<ref> It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.</ref>
** If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
** If the seeker is set to reject unvalidated, invalid targets are always ignored.
* The scores of the targets are then modified based on a few factors
** If the missile has a current target, and that target appears in the list again, then:
*** If the current target is closer than the seeker's ''Lock Current Target Distance'' stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
*** Otherwise, if the current target is not a decoy, its score is multiplied by the ''Target Affinity'' stat of the seeker (10x for most seekers, 3x for WAKE).
** If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
* Select a random target weighted by the scores of the targets remaining in the list.

CMD seekers do not undergo this process as their only target is the track they were fired on.

If the seeker is under jamming, the target's [[Radar#Return_Power_Density |return power]] has to exceed the [[Electronic_Warfare |combined jamming power]] felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.

If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.

==== Validation ====
<div style="float: right; width: 50%; padding: 20px">
[[File:SmolcakeBackupVsValidator.jpg|Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.]]
''Comparison of dual-seeker and seeker-validator behavior. Diagram by smolcake.''
</div>
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does '''''NOT''''' provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.

The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.

Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).

Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.

Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.

==== Backup Seeker ====
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.

Backups will also utilize any existing validators, regardless of position.
<div style="clear: both"></div>

=== Launching Missiles ===

Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile

==== Track mode (TRK) ====
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.

Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.

Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.

==== Position mode (POS) ====
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.

* Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
* Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.

If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.

==== Programming ====
Missile launches out of VLS tubes are affected by ''Programming Time'' and ''Programming Channels''.

Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.

Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.

===== Mixed Salvos =====
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.

===== MLS Launcher =====
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.

MLS will not fire defensive missiles automatically.

===== Defensive Missiles =====
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.

When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.

Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets

====== Doctrine ======
Doctrine decides how defensive missiles are fired against incoming missiles.

== Missile Construction ==
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.

Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.

{| class="wikitable"
! Missile Body
! Size
! Integrity
! width=1% | Socket Weight
! width=1% | Programming Time (s)
! Components
! Main Speed (m/s)
! Thruster Speed (m/s)
! Range (m)
! Acceleration (G)
! Top Speed (s)
! Turn Rate (G)
! Radar Cross Section (Front / Side)
! width=1% | Cost (pts)
! width=1% | Faction
|-
| [[File:SGM-1 Icon.png|25px]] SGM-100 Balestra Missile || 1 || 10 || 0.33x || 6 || 3 || 250-400 || 40-50 || 1458-5911 || 35.7-76.5 || 0.3-1.1 || 3.9-13.3 || 156m2 / 400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-2 Icon.png|25px]] SGM-200 Tempest Missile || 2 || 30 || 1x || 8 || 4 || 150-350 || 30-40 || 2962-14920 || 14.3-30.6 || 0.5-2.5 || 1.5-5.3 || 625m2 / 950m2 || 2 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGT-3 Icon.png|25px]] SGT-300 Pilum Torpedo || 3 || 110 || 3x || 6 || 4 || 125-200 || 20-35 || 2573-14797 || 10.2-15.3 || 0.8-2.0 || 0.8-3.6 || 900m2 / 2400m2 || 1 || [[File:Alliance Roundel.png|25px]][[File:OSP Roundel.png|25px]]
|-
| [[File:SGM-H-2 Icon.png|25px]] SGM-H-200 Cyclone Hybrid Missile || 2 || 25 || 0.8x || 10 || 4 || 150-350 Cruise 500-1000 Sprint || 30-40 Cruise 500-1000 Sprint || 5930-19359 Cruise 1438-4875 Sprint || 8.2-16.3 Cruise 120.0-204.1 Sprint || 0.9-4.4 Cruise 0.3-1.0 Sprint || 0.7-2.8 Cruise 14.8-31.9 Sprint || 625m2 / 950m2 || 8 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:SGM-H-3 Icon.png|25px]] SGM-H-300 Atlatl Hybrid Missile || 3 || 60 || 1.8x || 16 || 5 || 100-200 Cruise 550-1000 Sprint || 20-40 Cruise 550-1000 Sprint || 7944-24917 Cruise 2216-7361 Sprint || 6.1-9.2 Cruise 76.5-127.6 Sprint || 1.1-3-3 Cruise 0.4-1.3 Sprint || 0.5-2.5 Cruise 16.9-40.8 Sprint || 1600m2 / 3600m2 || 11 || [[File:Alliance Roundel.png|25px]]
|-
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m2 / 40002 || 1 || [[File:OSP Roundel.png|25px]]
|}

=== Payload ===
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
{| class="wikitable"
! Payload
! Fuze
! Area Damage Type
! Base Cost (pts)
! Notes
|-
| [[File:Warhead shaped.png|25px]] HE Impact || Contact || Shaped Angle 70 deg || 0.25 ||
|-
| [[File:Warhead hekp.png|25px]] HE Kinetic Penetrator || Delayed Contact || None || 2 || Penetration depth depends on the missile's top speed
|-
| [[File:Warhead frag.png|25px]] Blast Fragmentation || Proximity || Blast Fragmentation Radius || 0.25 || Larger missiles increase the area damage radius as well
|-
| [[File:Warhead frag el.png|25px]] Blast Fragmentation EL || Proximity || Blast Fragmentation Radius || 3.5 || Larger missiles increase the area damage radius as well
|}

=== Avionics Package ===
The avionics package determines how the missile is controlled. It has the following configuration options:
* '''Weapon Role''' sets how the missile may be launched:
** DEFENSIVE: Missiles can be launched manually and by the point defense system.
** OFFENSIVE: Missiles can be launched manually.
* '''Launch Type''' sets the behavior immediately after launching:
** HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
** COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
* '''Target Lost Behavior''' sets what the missile will do if it loses the target:
** RESUME SEARCH: The missile will search for a new target.
** SELF DESTRUCT: The missile will self destruct.
* '''Terminal Maneuvers''' sets what evasive maneuvers the missile will perform on its terminal approach to the target:
** NONE: No evasive maneuvers.
** WEAVE: Missile will weave from side to side.
** CORKSCREW: Missile will spiral towards the target.
* '''Trajectory Preference''' sets the approach angle the guidance system will try to maintain.
** FREE APPRAOCH: Missile will fly directly towards the target.
** MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
{| class="wikitable"
! Avionics Package
! Description
! Base Cost (pts)
|-
| [[File:Avionics basic.png|25px]] Direct Guidance || The simplest form of missile guidance system. This avionics package guides the missile in a straight line towards the target that has been acquired by the missile's seeker. || 0
|-
| [[File:Avionics cruise.png|25px]] Cruise guidance || A more advanced form of missile guidance that is capable of following a complex waypoint path to the target, enabling blind strikes around asteroids and more. || 2
|}

=== Seeker ===
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
* TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
* VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
{| class="wikitable"
! Seeker
! Type
! Range (M)
! FOV (deg)
! Validator Reliability (%)
! Steerable
! Position Trageting
! Support TRPs
! Measures Position
! Measures Velocity
! Base Cost / Validator Cost
|-
| [[File:Seeker command.png|25px]] Command Receiver || COMMS || Fleet || Fleet || Fleet || '''Fleet''' || '''No''' || '''No''' || '''Yes''' || '''Yes''' || 3.5 / 3
|-
| [[File:Seeker active fixed.png|25px]] Fixed Active Radar Seeker || RADAR || 2000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1 / 0.25
|-
| [[File:Seeker active steerable.png|25px]] Steerable Active Radar Seeker || RADAR || 2000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 1.5 / 0.5
|-
| [[File:Seeker active steerable.png|25px]] Steerable Extended Active Radar Seeker || RADAR || 5000 || 40 || 95 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || 3 / 1
|-
| [[File:Seeker semiactive fixed.png|25px]] Fixed Semi-Active Radar Seeker || RADAR || 4000 || 50 || 95 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''Yes''' || 0.5 / 0.5
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker || PSV RADAR || 3000 || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 2 / 2
|-
| [[File:Seeker arh fixed.png|25px]] Fixed Anti-Radiation Seeker (Home On Jam) || PSV JAM || ∞ || 50 || 93 || '''No''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.5 / 0.5
|-
| [[File:Seeker eo.png|25px]] Electro-Optical Seeker || EO || 3000 || 60 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Yes''' || '''No''' || 8 / 5
|-
| [[File:Seeker wake.png|25px]] Wake-Homing Seeker || WAKE || 1500 || 120 || 100 || '''Yes''' || '''Yes''' || '''Yes''' || '''Direction Only''' || '''No''' || 0.25 / 0.5
|}

=== Auxiliary ===
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
{| class="wikitable"
! Auxiliary
! Modifiers
! Base Cost (pts)
|-
| [[File:Support coldgas.png|25px]] Cold Gas Bottle || '''+150%''' Boost-Phase Strafe '''+100%''' Boost-Phase Turn Rate || 1
|-
| [[File:Support decoys.png|25px]] Decoy Launcher || '''+3''' Decoys Fired || 12
|-
| [[File:Support decoys cluster.png|25px]] Cluster Decoy Launcher || '''+6''' Decoys Fired || 30
|-
| [[File:Support fastboot.png|25px]] Fast Startup Module || '''-66%''' Programming Time '''_20%''' Failure Rate || 3
|-
| [[File:Support armor.png|25px]] Hardened Skin || '''+20''' Body Integrity || 5
|-
| [[File:Support stealth.png|25px]] Radar Absorbent Coating || '''-40%''' Radar Signature Bonus || 4
|-
| [[File:Support jammer.png|25px]] Self-Screening Jammer || '''RADAR''' - range: 1000 m; radiated power: 0.5 kW; gain: 2 dB || 5
|-
| [[File:Support jammer.png|25px]] Boosted Self-Screening Jammer || '''RADAR''' - range: 4000 m; radiated power: 0.5 kW; gain: 4 dB; beam width: 10 deg || 10
|}

Munitions & Missiles

2024-06-22T17:20:34Z

76561198801434526: /* Missile Construction */ added RCS to table

Munitions & Missiles

2024-06-22T17:14:46Z

76561198801434526: /* Seeker */ fixed capitilization

Munitions & Missiles

2024-06-22T17:14:06Z

76561198801434526: /* Seeker */ added validator cost to table

Munitions & Missiles

2024-06-22T17:10:24Z

76561198801434526: /* Seeker */

Munitions & Missiles

2024-06-22T17:05:56Z

76561198801434526: /* Seeker */ added HOJ to table