Damage Control: Difference between revisions

From NEBULOUS: Fleet Command Official Wiki
 
(14 intermediate revisions by 2 users not shown)
Line 6: Line 6:


<div style="clear: both"></div>
<div style="clear: both"></div>
== Definition of components ==
=== 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.
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.
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]].
For detailed information on damage mechanics, see [[Component_Damage |Component Damage]].


=== Inoperable components ===
==== 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.
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.


=== Repair teams ===
=== 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
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)
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)


Only 1 team can repair a component's HP, but multiple DC teams can simultaneously work in the same component if there are also debuffs (fires, atmo leaks, etc) that need fixing.
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 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 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.


==== Repair team priorities ====
==== Damage Control priorities ====
Damage control teams are assigned based on their order in the component list. 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.
Every ship has a damage control dispatcher that assigns DC teams to repair jobs and manages repair priorities.
<!-- TODO, find out component priority mechanics from damagecontroldispatcher.UserCode_RpcTaskTeam-->
 
<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:<br />
- damaged drive (Critical prio) with atmo leak, fire, overload<br />
- damaged cic (high prio)<br />
- damaged magazine (med prio) with ammo cookoff<br />
- damaged DC locker (low prio)<br />
 
the lists will look something like this:
 
Primary:<br />
- Drive Overload<br />
- Drive Atmo leak<br />
- CIC hp<br />
- Magazine Ammo cookoff<br />
 
Secondary:<br />
-Drive HP<br />
-Magazine HP<br />
-DC locker HP<br />
</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.
<!-- Not complete, there were some details that I didn't understand esp with restores and prio, refer to DamageControlDispatcher.SortAndAssignJobs(), HullComponent.GetAvailableDCJobs() -d0d0 -->


==== Repair team casualties ====
==== Repair team casualties ====
Line 33: Line 66:


=== Restore ===
=== Restore ===
When a component has lost all of its health, it would be considered to be in the ''Destroyed'' state. In this state, the component no longer responds to any further damage, 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.
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
Restore usage seems to be distributed among the lockers, starting from the closest locker and working outward
Line 59: Line 92:


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


Line 100: Line 133:
* 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.
* 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"
{| class="wikitable sortable"
|+ Casualty class determines the voicelines that play when the debuff is incurred
|+ 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)
! In game name !! Internal name !! Affected class !! Required Condition !! Casualty class !! On-hitOnly !! Rare (catastrophic)
|-
|-
| Atmosphere Leak || Atmosphere Leak || CrewedComponent || none || Decompression || TRUE || FALSE
| Atmosphere Leak || Atmosphere Leak || CrewedComponent || none || Decompression || TRUE || FALSE
|-
|-
| Fire || Fire || HullComponent || none || Fire || FALSE || FALSE
| Fire || Fire || HullComponent || none || Fire || FALSE || FALSE
|-
|-
| Fuel Line Fire || Fuel Line Fire || DriveComponent || none || Fire || TRUE || TRUE
| 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
| 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 || Example
| Reactor Overload || Reactor Overload || PowerplantComponent || none || Engineering || FALSE || TRUE
|-
|-
| Main Bus Short || Main Bus Short || PowerplantComponent || none || Engineering || FALSE || FALSE
| Main Bus Short || Main Bus Short || PowerplantComponent || none || Engineering || FALSE || FALSE
|-
|-
| Cell Cookoff || Cell Launcher Cookoff || BaseCellLauncherComponent || ContainsAnyAmmo || CombatSystems || TRUE || TRUE
| 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 setting container banks to the same key as cell cookoffs will prevent the container cookoff from being added to the debuff table.</ref> || 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
| Ammunition Loader Jammed || Ammunition Loader Jammed || DiscreteWeaponComponent || none || CombatSystems || FALSE || FALSE
|-
|-
| FC Waveguide Bent || FC Waveguide Bent || WeaponComponent || HasIntegratedFC || CombatSystems || FALSE || FALSE
| FC Waveguide Bent || FC Waveguide Bent || WeaponComponent || HasIntegratedFC || CombatSystems || FALSE || FALSE
|-
|-
| Gyroscope Drift || Gyro Drift || WeaponComponent || none || CombatSystems || FALSE || FALSE
| Gyroscope Drift || Gyro Drift || WeaponComponent || none || CombatSystems || FALSE || FALSE
|-
|-
| Heatsink Ruptured || Heatsink Ruptured || ContinuousWeaponComponent || HasCooldown || 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 Antenna Bent || BaseActiveSensorComponent, PassiveSensorComponent || none || CombatSystems || FALSE || FALSE
|-
|-
| Antenna Bent || Sensor Oscillator Drift || 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</ref>, TurretedContinuousWeaponComponent || 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
| 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
|}
|}


Line 151: Line 184:


==== Reactor Overload ====
==== 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 two minutes, 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 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.
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.
Line 165: Line 198:


==== Fuel Line Fires ====
==== Fuel Line Fires ====
Fuel Line fires can appear on drives or reactors. If 25 points of repair work is not completed within 1 minute, it will cause multiple small purple explosions to erupt across the ship, dealing heavy damage across the ship
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.
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.
Line 172: Line 205:


==== Magazine/Cell Cookoff ====
==== Magazine/Cell Cookoff ====
Magazine/Cell Cookoffs can appear on magazines and VLS cells. If 18 points of repair work is not completed within 1 minute, it will create a large explosion, dealing massive damage to the area around magazine inside the ship (3000 damage spread among components within 50m, shreds armor in 60m radius)
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.
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
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 ==
== Damage Control Board ==
Line 202: Line 235:
{| class="wikitable"
{| class="wikitable"
|-
|-
! DC Locker Type !! DC Teams !! Repair Rare !! Movement Speed !! Restores
!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:small-dc-locker|Small DC Locker]] || 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:reinforced-dc-locker|Reinforced DC Locker]] || 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:large-dc-locker|Large DC Locker]] || 3 || 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 || 1 || 0
| [[component:rapid-dc-locker|Rapid DC Locker]] || 1 || 0.3 || 0 || 0.3 || 0.3 || 1 || 0
|}
|}


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


Line 228: Line 269:
{| class="wikitable"
{| class="wikitable"
|-
|-
| [[component:launcher-deluge-system|Launcher Deluge System:]] || Catastrophic Event Prob. (Cell launcher): -50%
| [[component:fire-suppression-system|Fire Suppression System:]] || Catastrophic Event Prob. (Cell launcher): -50%
|-
 
| [[component:magazine-sprinklers|Magazine Sprinklers:]] || Catastrophic Event Prob. (Magazine): -50%
Catastrophic Event Prob. (Magazine): -50%
 
Firefighting Speed: +50%
|-
|-
| [[component:redundant-reactor-failsafes| Redundant Reactor Failsafes:]] || Catastrophic Event Prob. (Reactor): -33%
| [[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%
| [[component:reinforced-thruster-nozzles| Reinforced Thruster Nozzles:]] || Flank Damage Probability: -20%

Latest revision as of 13:06, 22 October 2024

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.

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.

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]\displaystyle{ \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.

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

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]\displaystyle{ \exp\left( -3Hp-0.5\right)\times C }[/math] where [math]\displaystyle{ Hp }[/math] is the current Hp percentage as a decimal and [math]\displaystyle{ C }[/math] is the critical event multiplier of the damage. This means baseline debuff chance for damage with 1x critical event multiplier starts at ∼3% and increases to ∼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

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.
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[1] 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[2] 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[3] none CombatSystems FALSE FALSE

Component Class Hierarchy

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,[4] 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).[5]

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

DC Locker Type DC Teams Repair Rate Movement Speed Restores
General Restore Firefighting Reactor Overload
Small DC Locker 2 0.2 0.2 0.2 0.2 0.5 1
Reinforced DC Locker 2 0.2 0.2 0.2 0.2 0.5 1
Damage Control Complex 3 0.2 0.2 0.2 0.2 0.5 2
Large DC Locker 3 0.2 0.2 0.2 0.2 0.5 2
Large DC Storage 1 0.2 0.2 0.2 0.2 0.5 4
Rapid DC Locker 1 0.3 0 0.3 0.3 1 0

DC Buffing Components

Component Repair Speed Move Speed Max Repair
Small Workshop 30% N/A N/A
Damage Control Central 10% 50% N/A
Damage Control Complex 10% 30% 5%

Safety Components

Fire Suppression System: Catastrophic Event Prob. (Cell launcher): -50%

Catastrophic Event Prob. (Magazine): -50%

Firefighting Speed: +50%

Redundant Reactor Failsafes: Catastrophic Event Prob. (Reactor): -33%

Reactor Overload Repair Speed: +30%

Reinforced Thruster Nozzles: Flank Damage Probability: -20%

Notes

  1. ↑ BulkMagazineComponents include all types of magazines, including reinforced and citadel magazines.
  2. ↑ 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.
  3. ↑ Similar to container bank cookoffs. Is explicitly defined in both the spinal beam and beam turret.
  4. ↑ More specifically, it looks at how long the ship's bounding radius is, and then multiplies that by a random float between 2-4
  5. ↑ These colors are for the default color settings. Colorblindness settings will change the colors.
Retrieved from "https://hoodedhorse.com/wiki/NEBULOUS_Fleet_Command/index.php?title=Damage_Control&oldid=546"