Fandom

Arkham City Wiki

Cloudburst

847pages on
this wiki
Add New Page
Talk0 Share

BATMAN™ ARKHAM KNIGHT 20150625113607

In Batman: Arkham Knight, the Cloudburst was a weapon that was designed by Simon Stagg under the influence of Scarecrow that launched and amplified the effects of Scarecrow's Fear Toxin. The Cloudburst initially was an invention that was meant to quickly spread cures to diseases in heavily infected areas via inhalation. The Cloudburst ran on Stagg Enterprises' Nimbus Generators, which amplified the Fear Toxin and disabled any vehicles that lacked a Nimbus Cell.

On Halloween, the Arkham Knight's Militia took control of Stagg's Airships over Founders' Island. As the Militia began powering up the Cloudburst with Nimbus Cells, their preparations were interrupted by Batman, who infiltrated the airships in search of Scarecrow and Oracle. The Arkham Knight had a chopper rip the Cloudburst from the front of the airship that it was attached to with Scarecrow hanging on, and was forced to finish the power-up offsite. The Cloudburst was then mounted onto the Arkham Knight's personal tank which was well armored and armed. The Cloudburst did succeed in launching the Fear Toxin in Gotham City, and engulfed the entire city to the point that Batman could only fly from building top to building top. It was eventually destroyed by the Batmobile after a long and intense battle with 5 Cobra Tanks and the Cloudburst Tank itself. An enhanced version of the boss fight consisting of 6 Cobra Tanks along side the Arkham Knight's Tank was found in the New Game Plus version of the game.

Trivia

  • "Cloudburst" possibly referred to the natural phenomenon of the same name which is described as "a sudden violent rainstorm".

It also could reference a character named Cloudburst in DC comics that is a member of the new Extremists

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.