Containment shield
From Halopedia, the Halo wiki
Containment shields are massive hard light barriers that can be created by Sentinel forces to quarantine an area. One was projected from the Sentinel Wall around Installation 05's Library. One of the many containment measures built by the Forerunners, it helped contain and enclose the Flood inside the Quarantine Zone, and keep out anything that could sustain the Flood. It had to be lowered and deactivated in order to enter the Library and recover the Activation Index.[1] It can be also breached with heavy firepower, such as that of a Banished Scarab. A containment shield does not shut down when the defense network is disabled.
History[edit]
Installation 05[edit]
During the Battle of Installation 05, the containment shield kept UNSC and Covenant forces stationed on Delta Halo from reaching the Index. In order to gain access to the Library and retrieve the Index, the Hierarchs of the Covenant dispatched Arbiter Thel 'Vadamee to lower the shield. The Arbiter fought his way through the Sentinel defenders to the enormous chamber containing the controls for the barrier. After destroying the Sentinel Enforcer guarding the chamber, the Arbiter retracted four piston-like plug locks which unlocked the main control panel, allowing him to lower the shield. This caused the entire two-tiered control platform to move to the other side of a large chasm in the middle of the Sentinel Wall in a manner similar to an anti-gravity gondola.[1]
The deactivation of the shield allowed access to the Quarantine Zone by the Covenant and the UNSC, which also gave the Flood hundreds of new hosts. The Flood was released onto the rest of Installation 05. As a result of this, the UNSC In Amber Clad was taken over by the Flood and flown into the Covenant holy city of High Charity.[1]
Installation 00[edit]
In December 2552, three days after the Human-Covenant War ended, monitor 000 Tragic Solitude had a containment shield set up around the ruins of High Charity to contain the Flood that had survived the detonation of the city's reactors and the firing of Installation 08. As an additional security measure, Tragic Solitude had the Sentinels raze the perimeter and modify the refugia to ensure that no sentient life survived nearby, in order to deprive the Flood of any host bodies in proximity to their prison. Tragic Solitude also kept a battalion of Sentinels on patrol in the vicinity of the containment shield, not only to guard against the Flood, but to guard against future invaders who might try to breach the shield and thus release the Flood.[2]
During the Second Ark Conflict in June 2559, Atriox, the leader of the Banished, ordered Jiralhanae brothers Pavium and Voridus to salvage anything useful from the shipwrecks near High Charity, but to only scout the shell and leave it alone, well-aware of the danger posed by any surviving Flood. However, like many of the Banished, Voridus brushed off the Flood as another Covenant lie and didn't heed Atriox's warnings. Instead, Voridus deactivated the Ark's Sentinel defense network using a terminal near High Charity and burned a hole in the containment shield with a Barukaza Workshop Scarab. When Voridus' troops entered the wreckage, they were swarmed by Flood infection forms which attacked the Banished and escaped onto the Ark through the breach in the containment shield created by Voridus, unimpeded by the Ark's Sentinels due to Voridus deactivating them.[3]
Voridus eventually managed to reactivate the Sentinel defense network[4] and the Banished, with the help of the Sentinels, slew a Proto-Gravemind that the Flood formed before it could become a full-fledged Gravemind. With the Sentinel defense network reactivated, thousands of Sentinels began a cleansing operation, supported by the Banished. The Sentinels and the Banished were able to contain the Flood outbreak[5] and scour them from High Charity's ruins.[6]
Trivia[edit]
- In Halo 2, the containment shield was observed during the level Sacred Icon.
- The holographic control panel for the Containment-Shield displays what appears to be a perfectly symmetrical hand, with two thumbs. The texture, created by Bungie environment artist Paul Russel, was actually originally designed with a normal five-finger hand. However, due to texture memory constraints, the image was mirrored, creating the six-digit hand in the game. Paul Russel simply shrugged this off, thinking the Forerunners "were probably courteous enough to make their holo signage ambidextrous." Relatedly, later depictions of Forerunner hands in Halo 4 and The Forerunner Saga established most Forerunners as having six-fingered hands with two thumbs.[7][8][9]
Gallery[edit]
The shield retracting after its deactivation.
The chamber housing the controls for the containment shield.
The control panel for the shield.
Voridus' Barukaza Workshop Scarab breaks through a segment of the containment shield around High Charity in Halo Wars 2: Awakening the Nightmare.
List of appearances[edit]
- Halo 2 (First appearance)
- Halo 2: Anniversary
- Halo Wars 2
Sources[edit]
- ^ a b c Halo 2, campaign level Sacred Icon
- ^ Halo Wars 2 Phoenix Logs - Idle Hands II
- ^ Halo Wars 2: Awakening the Nightmare, campaign level What Could Go Wrong?
- ^ Halo Wars 2: Awakening the Nightmare, campaign level The Archive
- ^ Halo Wars 2: Awakening the Nightmare, campaign level Manifestation
- ^ Halo: Shadows of Reach: Sacrifice
- ^ Twitter, Paul Russel (@docabominable): "It’s a mirrored texture. I thought the accidental two thumbs would be a funny thing to see fans speculate on. But it’s just mirrored to conserve texture memory. No secrets other than dev trickery to keep texture budgets low. https://archive.is/4ml2w" (Retrieved on Dec 22, 2022) [archive]
- ^ Twitter, Paul Russel (@docabominable): "Oh, I remember thinking forerunners were probably courteous enough to make their holo signage ambidextrous. But I never told anyone that. https://archive.is/nqvUT" (Retrieved on Dec 22, 2022) [archive]
- ^ Twitter, Paul Russel (@docabominable): "It’s really both. The texture had to be mirrored, so two thumbs was inevitable. I was able to shrug it off as ambidextrous but really no one cared. Just an item checked off a list. No mystery story meaning. https://archive.is/Dm99E" (Retrieved on Dec 22, 2022) [archive]
