Jump to content

Damaged Starport: Difference between revisions

From Elite Dangerous Wiki
Content deleted Content added
Fixed some truly awful grammar, like seriously awful
fixing/re-adding links, consistent capitalization
 
(6 intermediate revisions by 5 users not shown)
Line 1: Line 1:
A '''Damaged Starport''' is a [[Starport]] that has previously being attacked by [[Thargoid|Thargoids]] and has became damaged. These Starports will be displayed on the [[Galaxy Map]], and these Starports can automatically updated on [[GalNet]].
A '''Damaged Starport''' is a [[Starport]] that has been damaged in a [[Thargoid]] attack. These Starports will be displayed on the [[Galaxy Map]], and their status updated on [[GalNet]].


==Overview==
==Overview==
Damaged Starports are normal space stations that can often appear outside of [[Core Systems|The Bubble]]. When [[Incursion]] is occurring, one or more damaged Starports can appear in that [[star system]] in which [[Rescue Vessel|Rescue Megaships]] will be deployed to rescue people that still in this Starport. According to [[GalNet]], The Oracle in the [[Delphi]] system began tumbling out of orbit following a Thargoid attack, and is recorded as being the first damaged Starport ever recorded on the [[Milky Way]] and was later considered stablized by independent Pilots who risked their life to save peoples in The Oracle before it crashed the moon, and repaired by Delphi's population.
Damaged Starports are normal space stations that can often appear outside of [[Core Systems|The Bubble]]. During an [[Incursion]], one or more Starports in a [[star system]] can be damaged by attacking Thargoids, and [[Rescue Vessel|Rescue Megaships]] will be deployed to nearby systems to coordinate efforts to repel the Thargoids and rescue personnel who are still trapped within those Starports. A Damaged Starport is a dangerous location, as catastrophic malfunctions and potentially the continued presence of Thargoids render attempting to dock extremely hazardous for any ships in the area; nevertheless, evacuating civilians can be a lucrative pastime for any independent pilots willing to risk their ships.

Punishment for violating the no fire zone is partially reduced: no bounty is gained when discharging weapons within the no fire zone, through a fine can still be gained from firing. Turrets will also not fire your [[Ship]] when shooting at the Starport, but instead [[System Authority Vessel|Authorities]] will assist the damaged Starport by destroy your ship instead.


==History==
==History==
{{Quote|We are immensely grateful to those courageous Commanders for helping to prevent what could have been one of the most horrific disasters in modern history.|Spokesperson for Sirius Inc after the event of The Fall of the Oracle, displayed on the GalNet}}
{{Quote|We are immensely grateful to those courageous Commanders for helping to prevent what could have been one of the most horrific disasters in modern history.|Spokesperson for Sirius Inc after the event of The Fall of the Oracle, displayed on the GalNet}}
Before December 14, 3303, attacks on this scale were apparently rare, when a number of stations in the [[Pleiades Nebula]] were devastated by the Thargoids. In 24 May, 3307, [[The Oracle]] Starport located in the [[Delphi]] system being attacked by Thargoid in [[Second Thargoid War]]. This led to a castrophic failure that shutdown Oracle's thruster systems, making The Oracle’s orbit become unstable and threatening to hit the moon below. Very fortunately, independent Pilots saved the Oracle by rescuing people that were stuck in the port and stabilizing The Oracle’s orbit. Titan's Daughter also experienced damage on a later date.
Before 14 December 3303, large-scale attacks against Starports were rare. At that time, a number of stations in the [[Pleiades Nebula]] were devastated by the Thargoids. On 24 May 3307, [[The Oracle]] Starport located in the [[Delphi]] system was attacked by Thargoids, being the first Starport on record to take such comprehensive damage. This damage led to a catastrophic failure that shut down The Oracle's thruster systems, destabilizing The Oracle’s orbit and threatening a collision with the moon below. Very fortunately, independent pilots saved The Oracle by risking their lives to rescue trapped personnel and stabilize The Oracle’s orbit. Titan's Daughter also experienced similar damage on a later date.


Locations of damaged stations have since begun to spread out, reaching the Core System as of the [[Second Thargoid War]].
Further stations throughout the Core Systems have been damaged as a result of the [[Second Thargoid War]].


==Effects==
==Effects==
[[Starport]]s under an [[Incursion]] state will first enter an "under attack" state which is marked with a red skull icon on Galaxy Map, Starports in this state will not be affected. After some weeks of failing to repel the Thargoid presence, the Starport will enter a "damaged" state which is marked with a fire icon on Galaxy Map. Starports in this state will experience multiple effects:
Starports in a system experiencing an [[Incursion]] will first enter an "under attack" state, which is marked with a red skull icon on the [[Galaxy Map]]. Starports in this state do not experience any adverse effects, but the local system will experience increased Thargoid activity. After each week in which human forces fail to repel the Thargoid incursion, one Starport in the system will enter the "damaged" state, which is marked with a fire icon on the Galaxy Map.


Starports in a damaged state will experience multiple adverse effects:
⚫
*An emergency protocol will be activated to evacuate remaining civilians on the damaged Starport
*Nearly all Starport services will be disabled
* Nearly all Starport services will be disabled, and the service interface will be glitched.
⚫
* An emergency protocol will be activated to evacuate remaining civilians on the damaged Starport; this takes the form of Evacuation Missions available from the Passenger Lounge.
*[[Docking Computer]] usage is disabled, making ships docking on this Starport forced to dock manually
* [[Docking Computer]] usage is disabled, forcing incoming ships to dock with the Starport manually.
*Upon a ship entering the Starport corridor, it will gain [[heat]] over time, even when docked
*Random explosions can occur in the Starport, making a ship experience damage and deflection
* Ships that enter the Starport corridor will gain [[heat]] over time, even when docked.
* Random explosions can occur in the Starport corridor, potentially damaging and displacing ships inside.
*Some [[Black Box]]<nowiki/>es can be salvaged in the inside of the Starport
* Some [[Black Box]]es will be available for salvage within the Starport corridor.
*The reactor core found outside of the Starport will leaking, ships near the core will experience [[HUD]] disruption
* A breach in the Starport's reactor core will leak radiation to the Starport's exterior, disrupting nearby ships' [[HUD]]s.
*The service interface will be glitched
* No-fire zone punishments are partially reduced; bounties will not be imposed (though fines may still be accrued), and the station's defense turrets will not fire at attacking vessels (however, [[System Authority Vessel]]s will still defend the Starport from attackers).
*Passenger Lounge will support evacuation missions
*Punishment of no fire zone is partially reduced


== Evacuation Missions ==
== Evacuation Missions ==
When a Starport is damaged, the [[Mission Board]] is still accessible. Passenger missions arereplaced with evacuation missions, requiring a [[Passenger Cabin]] to accept mission. In this mission, you need carry a passenger to a deployed [[Rescue Vessel]]. This mission type will reward from tens to hundreds million [[Credits]], depending on the Starport being evacuated.
When a Starport is damaged, the [[Mission Board]] is still accessible. Passenger missions are replaced with evacuation missions, which require one or more [[Passenger Cabin]]s to accept; these missions require pilots to carry passengers to a deployed [[Rescue Vessel]]. This mission type can reward anywhere from tens of thousands to tens of millions of [[Credits]], depending on the Starport being evacuated.


==Repairing==
==Repairing==
After the system entering a [[Post-Thargoid Recovery]] state, the Starport will enter a repairing phase which is marked with an orange wrench on the Galaxy Map. When this is happening, humans in this system will start to repair damaged Starports which requires a large amount of materials and taking weeks to complete repair the Starports. [[Commander|Commanders]] can deliver materials to the system to accelerate the progress. Once the repairing is conplete, the previously damaged Starport will become fully operational.
After the system enters a [[Post-Thargoid Recovery]] state, the Starport will enter a repairing phase which is marked with an orange wrench on the Galaxy Map. During this state, the system's population will begin efforts to repair damaged Starports, which requires a large amount of materials over the course of days or even weeks. [[Commander]]s cam accelerate the progress by delivering necessary materials to the system. Once the repairs are complete, the previously damaged Starport will return to full operations.


==Gallery==
==Gallery==

Latest revision as of 04:41, 28 March 2025

A Damaged Starport is a Starport that has been damaged in a Thargoid attack. These Starports will be displayed on the Galaxy Map, and their status updated on GalNet.

Overview

Damaged Starports are normal space stations that can often appear outside of The Bubble. During an Incursion, one or more Starports in a star system can be damaged by attacking Thargoids, and Rescue Megaships will be deployed to nearby systems to coordinate efforts to repel the Thargoids and rescue personnel who are still trapped within those Starports. A Damaged Starport is a dangerous location, as catastrophic malfunctions and potentially the continued presence of Thargoids render attempting to dock extremely hazardous for any ships in the area; nevertheless, evacuating civilians can be a lucrative pastime for any independent pilots willing to risk their ships.

History

We are immensely grateful to those courageous Commanders for helping to prevent what could have been one of the most horrific disasters in modern history.

— Spokesperson for Sirius Inc after the event of The Fall of the Oracle, displayed on the GalNet

Before 14 December 3303, large-scale attacks against Starports were rare. At that time, a number of stations in the Pleiades Nebula were devastated by the Thargoids. On 24 May 3307, The Oracle Starport located in the Delphi system was attacked by Thargoids, being the first Starport on record to take such comprehensive damage. This damage led to a catastrophic failure that shut down The Oracle's thruster systems, destabilizing The Oracle’s orbit and threatening a collision with the moon below. Very fortunately, independent pilots saved The Oracle by risking their lives to rescue trapped personnel and stabilize The Oracle’s orbit. Titan's Daughter also experienced similar damage on a later date.

Further stations throughout the Core Systems have been damaged as a result of the Second Thargoid War.

Effects

Starports in a system experiencing an Incursion will first enter an "under attack" state, which is marked with a red skull icon on the Galaxy Map. Starports in this state do not experience any adverse effects, but the local system will experience increased Thargoid activity. After each week in which human forces fail to repel the Thargoid incursion, one Starport in the system will enter the "damaged" state, which is marked with a fire icon on the Galaxy Map.

Starports in a damaged state will experience multiple adverse effects:

  • Nearly all Starport services will be disabled, and the service interface will be glitched.
  • An emergency protocol will be activated to evacuate remaining civilians on the damaged Starport; this takes the form of Evacuation Missions available from the Passenger Lounge.
  • Docking Computer usage is disabled, forcing incoming ships to dock with the Starport manually.
  • Ships that enter the Starport corridor will gain heat over time, even when docked.
  • Random explosions can occur in the Starport corridor, potentially damaging and displacing ships inside.
  • Some Black Boxes will be available for salvage within the Starport corridor.
  • A breach in the Starport's reactor core will leak radiation to the Starport's exterior, disrupting nearby ships' HUDs.
  • No-fire zone punishments are partially reduced; bounties will not be imposed (though fines may still be accrued), and the station's defense turrets will not fire at attacking vessels (however, System Authority Vessels will still defend the Starport from attackers).

Evacuation Missions

When a Starport is damaged, the Mission Board is still accessible. Passenger missions are replaced with evacuation missions, which require one or more Passenger Cabins to accept; these missions require pilots to carry passengers to a deployed Rescue Vessel. This mission type can reward anywhere from tens of thousands to tens of millions of Credits, depending on the Starport being evacuated.

Repairing

After the system enters a Post-Thargoid Recovery state, the Starport will enter a repairing phase which is marked with an orange wrench on the Galaxy Map. During this state, the system's population will begin efforts to repair damaged Starports, which requires a large amount of materials over the course of days or even weeks. Commanders cam accelerate the progress by delivering necessary materials to the system. Once the repairs are complete, the previously damaged Starport will return to full operations.