Editing Collapse
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 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
{{Battle infobox | {{Battle infobox | ||
|prev= | |prev= | ||
|conc= | |conc= | ||
|next=[[Warlord Conflict]] | |next=[[Warlord Conflict]] | ||
|image= [[File: | |image= [[File:Fighters.jpg|280px]] | ||
|conflict= | |conflict= | ||
|date= | |date= | ||
| Line 66: | Line 66: | ||
==Timeline of events== | ==Timeline of events== | ||
Immediately before the Collapse, an entity or group of entities were detected just beyond the edge of the Solar System, in what was termed a "TRANSIENT NEAR EXTRASOLAR EVENT"; later information suggests this was the [[Black Fleet]] entering the Sol System. The only means of determining that a transient event had even occurred was through the detection of a 0.3-second displacement of gravity waves, as well as anomalous interactions in the local Higgs field traced to sterile neutrino scattering. An AI observing the event, the Warmind Rasputin, was able to derive some information but was unable to ascertain its mechanism. Rasputin conducted an "Omnibus analysis" of the event's effects on local spacetime, measuring a wide range of data points including direction, distance, range, speed, and size as well as a comprehensive pattern analysis of the event itself. This last set of data showed, to a certainty of "9 | Immediately before the Collapse, an entity or group of entities were detected just beyond the edge of the Solar System, in what was termed a "TRANSIENT NEAR EXTRASOLAR EVENT"; later information suggests this was the [[Black Fleet]] entering the Sol System. The only means of determining that a transient event had even occurred was through the detection of a 0.3-second displacement of gravity waves, as well as anomalous interactions in the local Higgs field traced to sterile neutrino scattering. An AI observing the event, the Warmind Rasputin, was able to derive some information but was unable to ascertain its mechanism. Rasputin conducted an "Omnibus analysis" of the event's effects on local spacetime, measuring a wide range of data points including direction, distance, range, speed, and size as well as a comprehensive pattern analysis of the event itself. This last set of data showed, to a certainty of "9 Sigma", a definite and measurable pattern that had a complex, almost linguistic, structure that demonstrated both intelligence and intent. | ||
In an attempt to better understand the phenomenon by recreating all of its known variables (also known as a "bootstrap simulation"), Rasputin reran the data through a series of iterations which included a number of randomized inputs, in a process known as a Monte Carlo analysis. Despite this, it was unable to derive any definitive information about the event or its source; however, it was able to determine that whatever was behind the event was clearly a complex structure, acting with clear purpose. Rasputin concluded that the source of the event not only failed to conform to any known phenomena in the [[Wikipedia:Standard_Model|Standard Model]] of particle physics (thus labeling it "[[wikipedia:Anticausal_system|acausal]]"), it was also directed, acting with anger, and almost certain to reach the solar system in a short amount of time. As a result, the previously issued Skyshock alert was upgraded to OCP:EXTINCTION, and a number of defensive protocols were added.<ref name = "GrimoireDarkness">'''Bungie (2014/6/12)''', ''[[Destiny]]: Alpha PlayStation 4, Activision Blizzard, [[Grimoire]]: [[Grimoire:Enemies#Ghost Fragment: Darkness|Ghost Fragment: Darkness]]''</ref> In the interim, Rasputin activated TWILIGHT EXIGENT to shift his priorities towards maximizing the amount of Humans that would survive an attack by the Black Fleet; most notably, he would use this protocol to destroy information on the Fleet the [[New Pacific Arcology]] had discovered independently of his own analyses by killing those responsible. | In an attempt to better understand the phenomenon by recreating all of its known variables (also known as a "bootstrap simulation"), Rasputin reran the data through a series of iterations which included a number of randomized inputs, in a process known as a Monte Carlo analysis. Despite this, it was unable to derive any definitive information about the event or its source; however, it was able to determine that whatever was behind the event was clearly a complex structure, acting with clear purpose. Rasputin concluded that the source of the event not only failed to conform to any known phenomena in the [[Wikipedia:Standard_Model|Standard Model]] of particle physics (thus labeling it "[[wikipedia:Anticausal_system|acausal]]"), it was also directed, acting with anger, and almost certain to reach the solar system in a short amount of time. As a result, the previously issued Skyshock alert was upgraded to OCP:EXTINCTION, and a number of defensive protocols were added.<ref name = "GrimoireDarkness">'''Bungie (2014/6/12)''', ''[[Destiny]]: Alpha PlayStation 4, Activision Blizzard, [[Grimoire]]: [[Grimoire:Enemies#Ghost Fragment: Darkness|Ghost Fragment: Darkness]]''</ref> In the interim, Rasputin activated TWILIGHT EXIGENT to shift his priorities towards maximizing the amount of Humans that would survive an attack by the Black Fleet; most notably, he would use this protocol to destroy information on the Fleet the [[New Pacific Arcology]] had discovered independently of his own analyses by killing those responsible. | ||
| Line 78: | Line 78: | ||
==List of appearances== | ==List of appearances== | ||
*''[[Destiny]]'' {{Fm}} | *''[[Destiny]]'' {{Fm}} | ||
*''[[Destiny 2]]'' {{Mo}} | *''[[Destiny 2]]'' {{Mo}} | ||
* | **''[[Lightfall]]'' {{Mo}} | ||
*''[[ | |||
*''[[Entelechy]]'' {{Mo}} | *''[[Entelechy]]'' {{Mo}} | ||
| Line 90: | Line 86: | ||
[[Category:Events]] | [[Category:Events]] | ||
