Despair-class fighter: Difference between revisions
From Halopedia, the Halo wiki
mNo edit summary |
Lejellysoup (talk | contribs) mNo edit summary |
||
| Line 25: | Line 25: | ||
Despair-class hunter-killers were present at the [[Battle of Janjur Qom]].<ref name="cryptum"/> At the close of the [[Forerunner-Flood war]], multiple ''Despair''-class fighters were stationed at [[Requiem]] in defense of the [[shield world]].<ref>'''Halo: Silentium''', ''String 34''</ref> Several ''Despair''-class fighters saw action against the rogue {{Class|Contender|artificial intelligence}} [[Mendicant Bias]]. After the [[Great Purification|firing]] of the [[Halo Array]], some of the ''Despair''-class fighters were moved to [[Shield Worlds]] and Halo installations. At least one ''Despair''-class hunter-killer was moved to [[Installation 00]] by the [[Librarian]].<ref>'''[[Halo Wars 2]]''' - ''[[Phoenix Logs]]: [[Phoenix Logs#Forerunner Ship|Forerunner Ship]]''</ref> | Despair-class hunter-killers were present at the [[Battle of Janjur Qom]].<ref name="cryptum"/> At the close of the [[Forerunner-Flood war]], multiple ''Despair''-class fighters were stationed at [[Requiem]] in defense of the [[shield world]].<ref>'''Halo: Silentium''', ''String 34''</ref> Several ''Despair''-class fighters saw action against the rogue {{Class|Contender|artificial intelligence}} [[Mendicant Bias]]. After the [[Great Purification|firing]] of the [[Halo Array]], some of the ''Despair''-class fighters were moved to [[Shield Worlds]] and Halo installations. At least one ''Despair''-class hunter-killer was moved to [[Installation 00]] by the [[Librarian]].<ref>'''[[Halo Wars 2]]''' - ''[[Phoenix Logs]]: [[Phoenix Logs#Forerunner Ship|Forerunner Ship]]''</ref> | ||
On [[2559|May 2559]], a ''Despair''-class fighter's [[design seed]] was found and reactivated by [[Colony]]'s [[Huragok]],<ref>'''[[Halo Wars 2]]''' - ''Operation: STORMBREAKER: [[Gatecrashers]]''</ref> with the [[Banished]] planning to use the fighter to destroy the {{UNSCShip|Spirit of Fire}}, but their efforts were halted when [[ODST]] squad [[Sunray 1-1]] managed to halt the fighter's | On [[2559|May 2559]], a ''Despair''-class fighter's [[design seed]] was found and reactivated by [[Colony]]'s [[Huragok]],<ref>'''[[Halo Wars 2]]''' - ''Operation: STORMBREAKER: [[Gatecrashers]]''</ref> with the [[Banished]] planning to use the fighter to destroy the {{UNSCShip|Spirit of Fire}}, but their efforts were halted when [[ODST]] squad [[Sunray 1-1]] managed to halt the fighter's launch and destroy it.<ref>'''[[Halo Wars 2]]''' - ''Operation: STORMBREAKER: [[Not on My Watch]]''</ref> | ||
==List of appearances== | ==List of appearances== | ||
Revision as of 11:41, July 27, 2017
Template:Ship Class Infobox The Despair-class fighter, also known as the Despair-class hunter-killer,[1] was a classification of Forerunner fighter craft. They were described as curved and sleek in design.[1]
History
Despair-class hunter-killers were present at the Battle of Janjur Qom.[1] At the close of the Forerunner-Flood war, multiple Despair-class fighters were stationed at Requiem in defense of the shield world.[2] Several Despair-class fighters saw action against the rogue Contender-class artificial intelligence Mendicant Bias. After the firing of the Halo Array, some of the Despair-class fighters were moved to Shield Worlds and Halo installations. At least one Despair-class hunter-killer was moved to Installation 00 by the Librarian.[3]
On May 2559, a Despair-class fighter's design seed was found and reactivated by Colony's Huragok,[4] with the Banished planning to use the fighter to destroy the UNSC Spirit of Fire, but their efforts were halted when ODST squad Sunray 1-1 managed to halt the fighter's launch and destroy it.[5]
List of appearances
- Halo: Cryptum (First appearance)
- Halo: Silentium
- Halo Wars 2
Sources
- ^ a b c Halo: Cryptum, page 195
- ^ Halo: Silentium, String 34
- ^ Halo Wars 2 - Phoenix Logs: Forerunner Ship
- ^ Halo Wars 2 - Operation: STORMBREAKER: Gatecrashers
- ^ Halo Wars 2 - Operation: STORMBREAKER: Not on My Watch
| |||||||||||||||||||||||||||||
