Installation 00: Difference between revisions

Line 51: Line 51:
In [[2553|March 2553]], the [[Office of Naval Intelligence]] deployed an automated probe-carrying spacecraft to the damaged Ark using advanced slipspace technology. The ship arrived in November and dispersed its probes, although all communications with the devices were cut off after initial transmissions confirming the Ark's survival. In response, the {{UNSCShip|Rubicon}} was sent from [[Luna]] in December 2553 to conduct a more thorough investigation of the installation's ravaged surface.<ref name="hitd c2">'''[[Halo: Hunters in the Dark]]''', ''Chapter 2''</ref> Due to the damage dealt to the Ark's life support systems and its artificial sun, heavily inclement weather became the norm.<ref name="EH">'''[[Eleventh Hour reports]]''', ''part 4''</ref>
In [[2553|March 2553]], the [[Office of Naval Intelligence]] deployed an automated probe-carrying spacecraft to the damaged Ark using advanced slipspace technology. The ship arrived in November and dispersed its probes, although all communications with the devices were cut off after initial transmissions confirming the Ark's survival. In response, the {{UNSCShip|Rubicon}} was sent from [[Luna]] in December 2553 to conduct a more thorough investigation of the installation's ravaged surface.<ref name="hitd c2">'''[[Halo: Hunters in the Dark]]''', ''Chapter 2''</ref> Due to the damage dealt to the Ark's life support systems and its artificial sun, heavily inclement weather became the norm.<ref name="EH">'''[[Eleventh Hour reports]]''', ''part 4''</ref>


The [[''Rubicon'']] carried several [[remote contact team]]s, who landed on the damaged Ark and attempted to find the source of the mysterious signal. After about eight days, contact with all teams was lost; only one team, [[RCT-06]], returned, having sustained heavy casualties and carrying with them a device of unknown nature. The armature's origin was subjected to debate, but it was believed by the team to be the source of the beacon picked up by the initial investigative group.<ref name="EH"/> The device, actually a broken, barely active [[monitor]], began to relate its past life as a human: [[Chakas]]. Though the ship's ONI attaché initially doubted the veracity of the monitor's account, the science team leader pointed out that it was consistent with the "[[Halo: Cryptum|Bornstellar Relation]]" found on [[Onyx]].
The [[Rubicon]] carried several [[remote contact team]]s, who landed on the damaged Ark and attempted to find the source of the mysterious signal. After about eight days, contact with all teams was lost; only one team, [[RCT-06]], returned, having sustained heavy casualties and carrying with them a device of unknown nature. The armature's origin was subjected to debate, but it was believed by the team to be the source of the beacon picked up by the initial investigative group.<ref name="EH"/> The device, actually a broken, barely active [[monitor]], began to relate its past life as a human: [[Chakas]]. Though the ship's ONI attaché initially doubted the veracity of the monitor's account, the science team leader pointed out that it was consistent with the "[[Halo: Cryptum|Bornstellar Relation]]" found on [[Onyx]].


Eventually, the monitor revealed that it was none other than [[343 Guilty Spark]] himself. Claiming that he knew the location of the [[Librarian]], whom he believed to be alive, Spark subsumed the ship's AI, knocked out the crew via the life support systems, and hijacked the ship.<ref>'''[[Halo: Primordium]]''', ''pages 377-379''</ref> Communications with the ''Rubicon'' halted within 48 hours of its last report. Search and rescue teams were then deployed to the site, but reported no findings.<ref name="EH"/>
Eventually, the monitor revealed that it was none other than [[343 Guilty Spark]] himself. Claiming that he knew the location of the [[Librarian]], whom he believed to be alive, Spark subsumed the ship's AI, knocked out the crew via the life support systems, and hijacked the ship.<ref>'''[[Halo: Primordium]]''', ''pages 377-379''</ref> Communications with the ''Rubicon'' halted within 48 hours of its last report. Search and rescue teams were then deployed to the site, but reported no findings.<ref name="EH"/>
Anonymous user