3,186
edits
Rasputin: Difference between revisions
→Biography
| Line 23: | Line 23: | ||
Rasputin was the one to first discover the coming of the Darkness.<ref>'''Bungie (2014-9-9)''', ''Destiny PlayStation 4, Activision Blizzard, [[Grimoire]]: [[Grimoire/Enemies#Ghost_Fragment:_Darkness|Ghost Fragment: Darkness]]''</ref> At that time, Rasputin's original core programming was to protect humanity. However, every action he had taken to that point had either failed or was statistically predicted to have a 100% probability of failure. Once it became clear that no conceivable action could be taken to fulfill his core programming, he implemented a protocol known as MIDNIGHT EXIGENT and reconfigured his core programming to that of long term survival, abandoning his previous function and going dark, while simultaneously ordering all remaining forces at his disposal to do the same.<ref>'''Bungie (2014-9-9)''', ''Destiny PlayStation 4, Activision Blizzard, [[Grimoire]]: [[Grimoire/Allies#Ghost_Fragment:_Rasputin_3|Ghost Fragment: Rasputin 3]]''</ref> | Rasputin was the one to first discover the coming of the Darkness.<ref>'''Bungie (2014-9-9)''', ''Destiny PlayStation 4, Activision Blizzard, [[Grimoire]]: [[Grimoire/Enemies#Ghost_Fragment:_Darkness|Ghost Fragment: Darkness]]''</ref> At that time, Rasputin's original core programming was to protect humanity. However, every action he had taken to that point had either failed or was statistically predicted to have a 100% probability of failure. Once it became clear that no conceivable action could be taken to fulfill his core programming, he implemented a protocol known as MIDNIGHT EXIGENT and reconfigured his core programming to that of long term survival, abandoning his previous function and going dark, while simultaneously ordering all remaining forces at his disposal to do the same.<ref>'''Bungie (2014-9-9)''', ''Destiny PlayStation 4, Activision Blizzard, [[Grimoire]]: [[Grimoire/Allies#Ghost_Fragment:_Rasputin_3|Ghost Fragment: Rasputin 3]]''</ref> | ||
In recent times, the [[Fallen]] and [[Guardian]]s discovered Rasputin was still alive, and protecting something valuable in the Cosmodrome. After a communications array at the [[Terrestrial Complex]] was reactivated by the Guardians, Rasputin was able to reconnect with the old interplanetary defense network, resuming control of [[Warsat]]s and [[Skyshock|ground installations]] across the system and launching a series of orbital strikes against the [[Vex]] and [[Cabal]] on [[Mars]].<ref>'''Bungie (2014-9-9)''', ''Destiny PlayStation 4, Activision Blizzard, [[Grimoire]]: [[Grimoire/Allies#Ghost_Fragment:_Rasputin_2|Ghost Fragment: Rasputin 2]]''</ref> Rasputin is later encountered within the [[Dust Palace]], attempting to protect a broken AI (who had been connected to the Warmind of Mars) from the invading Cabal, but ultimately loses it to the [[Psion Flayer]]s.<ref name = "IGNBeta">[https://www.youtube.com/watch?v=vR0XkVzPpmA '''Youtube''': ''IGN Live Presents: Destiny Beta'']</ref> The [[Hive]] attempted to locate and attack Rasputin, either to kill him or corrupt him for their own purposes.<ref>'''Bungie (2014-12-9)''', ''Destiny: The Dark Below, PlayStation 4, Activision Blizzard.</ref> Later, the [[Fallen]] attempted to hijack Rasputins systems, using the modified [[shank]] [[S.A.B.E.R.-2]] to bypass his protocols and take direct control of the warsats. Once again, Rasputin called for help. | However, unknown to the other warminds, Rasputin had made his own preparations, known as the "ABHORRENT IMPERATIVE." If it looked as if humanity was about to go extinct, and that the Traveler would attempt to leave, Rasputin would launch a series of Caedometric weapons at the Traveler to immobilize it and coerce it into a "pseudoaltrusitic" defensive action. It would do so through its many proxies, so as to hide Rasputin's culpability in such an attack. Even before the collapse, Rasputin had been discretely stockpiling such weapons in the Cosmodrome, though some human operators suspected Rasputin's involvement. | ||
In recent times, the [[Fallen]] and [[Guardian]]s discovered Rasputin was still alive, and protecting something valuable in the Cosmodrome. After a communications array at the [[Terrestrial Complex]] was reactivated by the Guardians, Rasputin was able to reconnect with the old interplanetary defense network, resuming control of [[Warsat]]s and [[Skyshock|ground installations]] across the system and launching a series of orbital strikes against the [[Vex]] and [[Cabal]] on [[Mars]].<ref>'''Bungie (2014-9-9)''', ''Destiny PlayStation 4, Activision Blizzard, [[Grimoire]]: [[Grimoire/Allies#Ghost_Fragment:_Rasputin_2|Ghost Fragment: Rasputin 2]]''</ref> Rasputin resisted any attempts by the [[City]] to parley, even going so far as to dismember a scouting team sent by the [[Vanguard]]. Rasputin is later encountered within the [[Dust Palace]], attempting to protect a broken AI (who had been connected to the Warmind of Mars) from the invading Cabal, but ultimately loses it to the [[Psion Flayer]]s.<ref name = "IGNBeta">[https://www.youtube.com/watch?v=vR0XkVzPpmA '''Youtube''': ''IGN Live Presents: Destiny Beta'']</ref> The [[Hive]] attempted to locate and attack Rasputin, either to kill him or corrupt him for their own purposes.<ref>'''Bungie (2014-12-9)''', ''Destiny: The Dark Below, PlayStation 4, Activision Blizzard.</ref> Later, the [[Fallen]] attempted to hijack Rasputins systems, using the modified [[shank]] [[S.A.B.E.R.-2]] to bypass his protocols and take direct control of the warsats. Once again, Rasputin called for help. | |||
==Quotes== | ==Quotes== | ||