Damaged Starport: Difference between revisions
Add repairing |
Fixed some truly awful grammar, like seriously awful |
||
| Line 2: | Line 2: | ||
==Overview== | ==Overview== | ||
Damaged Starports are normal space | 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. | ||
Punishment | 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 | 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. | ||
Locations of damaged stations have since begun to spread out, reaching the Core System as of the [[Second Thargoid War]]. | |||
==Effects== | ==Effects== | ||
[[Starport]]s under an [[Incursion]] state will first enter an "under attack" state which marked with a red skull icon on Galaxy Map, Starports | [[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: | ||
*An emergency protocol will be activated to | *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 | ||
*[[Docking Computer]] usage is disabled, making ships docking on this Starport | *[[Docking Computer]] usage is disabled, making ships docking on this Starport forced to dock manually | ||
* | *Upon a ship entering the Starport corridor, it will gain [[heat]] over time, even when docked | ||
*Random | *Random explosions can occur in the Starport, making a ship experience damage and deflection | ||
*Some [[Black Box]] can be salvaged in the inside of the Starport | *Some [[Black Box]]<nowiki/>es can be salvaged in the inside of the Starport | ||
* | *The reactor core found outside of the Starport will leaking, ships near the core will experience [[HUD]] disruption | ||
*The service interface will be glitched | *The service interface will be glitched | ||
*Passenger Lounge will support evacuation missions | *Passenger Lounge will support evacuation missions | ||
* | *Punishment of no fire zone is partially reduced | ||
== Evacuation Missions == | == Evacuation Missions == | ||
When a Starport is damaged, [[Mission Board]] | 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. | ||
==Repairing== | ==Repairing== | ||
After the system entering a [[Post-Thargoid Recovery]] state, the Starport will enter a 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. | ||
==Gallery== | ==Gallery== | ||
Revision as of 21:47, 19 September 2024
A Damaged Starport is a Starport that has previously being attacked by Thargoids and has became damaged. These Starports will be displayed on the Galaxy Map, and these Starports can automatically updated on GalNet.
Overview
Damaged Starports are normal space stations that can often appear outside of The Bubble. When Incursion is occurring, one or more damaged Starports can appear in that star system in which 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.
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 Authorities will assist the damaged Starport by destroy your ship instead.
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 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.
Locations of damaged stations have since begun to spread out, reaching the Core System as of the Second Thargoid War.
Effects
Starports 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:
- An emergency protocol will be activated to evacuate remaining civilians on the damaged Starport
- Nearly all Starport services will be disabled
- Docking Computer usage is disabled, making ships docking on this Starport forced to dock 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
- Some Black Boxes can be salvaged in the inside of the Starport
- The reactor core found outside of the Starport will leaking, ships near the core will experience HUD disruption
- The service interface will be glitched
- Passenger Lounge will support evacuation missions
- Punishment of no fire zone is partially reduced
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.
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. Commanders can deliver materials to the system to accelerate the progress. Once the repairing is conplete, the previously damaged Starport will become fully operational.