Editing Failsafe
From Destinypedia, the Destiny wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 59: | Line 59: | ||
Failsafe was relieved when the Guardian arrived to investigate the crashed object. [[Saint-14]] asked for information on the object, and Failsafe explained that the local Vex had begun to display abnormal behaviour, but was unable to provide more help do to her being disconnected from her external array. Saint told her that [[Osiris]] had a suprise for her after they finished tracking down the object, and Failsafe became properly motivated. She asked the Guardian to destroy the Vex in proximity to the Exodus Black so she could be released from her confinement. The Guardian reached the impact site of the object, and Failsafe declared that it was "super weird", as the object crashed straight through the crust of the planetoid without leaving a crater. The Guardian rebooted Failsafe's data array, but the Vex quickly set up a firewall requiring a Vex signature. Failsafe told the Guardian to retrieve a severed Vex head. After reconnecting, Failsafe was hit by significant critical errors, but reassured the Guardian that it was a good sign. Failsafe told Saint that she would share him the data, after he told her what the suprise was. Saint explained that Osiris was building a relay aboard the [[H.E.L.M.]], causing Failsafe to reroute energy so she could experience joy again. She quickly disconnected from the comms so she could connect to the H.E.L.M..<ref>'''Bungie (2024/12/4)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Mission: Meteoric]]''</ref> | Failsafe was relieved when the Guardian arrived to investigate the crashed object. [[Saint-14]] asked for information on the object, and Failsafe explained that the local Vex had begun to display abnormal behaviour, but was unable to provide more help do to her being disconnected from her external array. Saint told her that [[Osiris]] had a suprise for her after they finished tracking down the object, and Failsafe became properly motivated. She asked the Guardian to destroy the Vex in proximity to the Exodus Black so she could be released from her confinement. The Guardian reached the impact site of the object, and Failsafe declared that it was "super weird", as the object crashed straight through the crust of the planetoid without leaving a crater. The Guardian rebooted Failsafe's data array, but the Vex quickly set up a firewall requiring a Vex signature. Failsafe told the Guardian to retrieve a severed Vex head. After reconnecting, Failsafe was hit by significant critical errors, but reassured the Guardian that it was a good sign. Failsafe told Saint that she would share him the data, after he told her what the suprise was. Saint explained that Osiris was building a relay aboard the [[H.E.L.M.]], causing Failsafe to reroute energy so she could experience joy again. She quickly disconnected from the comms so she could connect to the H.E.L.M..<ref>'''Bungie (2024/12/4)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Mission: Meteoric]]''</ref> | ||
In the H.E.L.M., Osiris initialized the remote connection to the Exodus Black. Failsafe recalibrated, and thanked the team for allowing her access off of the Exodus Black, but Osiris went straight to the point and asked for Failsafe's data. Failsafe explained that a new signal was coming from the Vex, likely an alternate tessellation of the radiolarial substrate. Osiris questioned if it was a cascading failure in the Vex system, but Failsafe believed it was actually emergent behavior.<ref | In the H.E.L.M., Osiris initialized the remote connection to the Exodus Black. Failsafe recalibrated, and thanked the team for allowing her access off of the Exodus Black, but Osiris went straight to the point and asked for Failsafe's data. Failsafe explained that a new signal was coming from the Vex, likely an alternate tessellation of the radiolarial substrate. Osiris questioned if it was a cascading failure in the Vex system, but Failsafe believed it was actually emergent behavior.<ref>'''Bungie (2024/12/4)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[Echoes Act I: A Familiar Voice]]''</ref> | ||
After returning with new data, Failsafe gave the Guardian a Standard [[Radiolite]] Sampler and tasked them with investigating strange silica formations with the [[Well of Flame]]. As the Guardian extracted samples, a minor quake occured revealing a unique object. The Guardian returned it to Failsafe's research bay in the H.E.L.M. for analysis. Failsafe was able to use the data from the specimen to design new fireteam equipment. Examining the Guardian's data from earlier, Failsafe determined that the Vex's behavior was unusual, and suspected something else was behind them.<ref name="Rising Chorus">'''Bungie (2024/12/4)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[A Rising Chorus: Act I]]''</ref> | After returning with new data, Failsafe gave the Guardian a Standard [[Radiolite]] Sampler and tasked them with investigating strange silica formations with the [[Well of Flame]]. As the Guardian extracted samples, a minor quake occured revealing a unique object. The Guardian returned it to Failsafe's research bay in the H.E.L.M. for analysis. Failsafe was able to use the data from the specimen to design new fireteam equipment. Examining the Guardian's data from earlier, Failsafe determined that the Vex's behavior was unusual, and suspected something else was behind them.<ref name="Rising Chorus">'''Bungie (2024/12/4)''', ''[[Destiny 2]]: [[Episode: Echoes]] - [[A Rising Chorus: Act I]]''</ref> |