Despair-class fighter: Difference between revisions
From Halopedia, the Halo wiki
No edit summary Tag: Mobile edit |
Tag: Mobile edit |
||
| Line 34: | Line 34: | ||
''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 name="sil"/> 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 name="pl ship"/> | ''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 name="sil"/> 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 name="pl ship"/> | ||
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}}, | 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}}. However, their efforts were halted when the [[Orbital Drop Shock Trooper]] squad [[Sunray 1-1]] managed to [[Operation: SPEARBREAKER|halt]] the fighter's launch and destroy it.<ref>'''Halo Wars 2''', ''Operation: STORMBREAKER: [[Not on My Watch]]''</ref> | ||
==Gallery== | ==Gallery== | ||
Revision as of 08:15, December 7, 2019
| Despair-class fighter | |
|---|---|
| |
| Production information | |
|
Class: |
|
|
Role: |
Hunter-killer fighter[1] |
| Chronological and affiliation | |
|
Era: |
|
|
Affiliation: |
|
The Despair-class fighter, also known as the Despair-class hunter-killer, was a classification of Forerunner fighter craft. They were described as curved and sleek in design.[1]
Operational 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.[3] 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.[2]
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. However, their efforts were halted when the Orbital Drop Shock Trooper squad Sunray 1-1 managed to halt the fighter's launch and destroy it.[5]
Gallery
- Despair.jpg
- Despair2.jpg
- Despair3.jpg
A Despair-class fighter in its dock on Installation 00.
List of appearances
- Halo: Cryptum (First appearance)
- Halo: Silentium
- Halo Wars 2
Sources
- ^ a b c d e Halo: Cryptum, page 195
- ^ a b Halo Wars 2, Phoenix Logs: Forerunner Ship
- ^ a b Halo: Silentium, String 34
- ^ Halo Wars 2, Operation: STORMBREAKER: Gatecrashers
- ^ Halo Wars 2, Operation: STORMBREAKER: Not on My Watch
| |||||||||||||||||||||||||||||
