Juggernaut (Firestorm)

The first-generation Juggernaut was a GDI artillery walker that entered service during the Firestorm Conflict.
==Background==
After analyzing battle data from the Second Tiberium War, GDI came to the conclusion that its forces lack a long-range fire support unit. To address this issue, technicians combined a modified Titan delivery system with ship-based artillery technology. The result was the Juggernaut.
Like contemporary Nod self-propelled artillery, the Juggernaut had to deploy stabilizers out of its rear and become stationary prior to firing. Each of the walker's guns was smaller than the single gun carried by its Nod counterpart, but the larger number of guns allowed the Juggernaut to better saturate a target area. When deployed, the turret can traverse 360 degrees, ensuring all around security. The Juggernaut is notably faster in mobile mode, compared to Nod's artillery.
Like all walkers of the period, the Juggernaut emerged from the conflict with mixed reviews. GDI found the all-terrain mobility conferred by walkers to be offset by the expense of construction and deployment.Verdu, Michael. 2006-09-29. Technology in 2047. Crysis News. 2009-05-30. However, while other walkers were withdrawn from service, the Juggernaut and its descendants remained essential parts of the arsenal.Electronic Arts Los Angeles, Command & Conquer 3: Kane's Wrath. Nod Weaponry, "GDI Behemoth". As indirect combat vehicles GDI decided the all-terrain mobility outweighed the costs.
After the Firestorm Crisis, the Steel Talons division designed the second iteration of the Juggernaut, called the Behemoth. By the Third Tiberium War, this iteration was adapted to the newer Juggernaut, used by regular GDI regiments.
==Game unit==
The Juggernaut serves as a mobile artillery gun, possessing great range and power that make it perfect for siege warfare. Despite its imposing appearance, however, the Juggernaut is surprisingly vulnerable to most forms of attack, especially anti-armor weaponry. On top of this, it is fairly slow moving. These two vulnerabilities combined bestow the Juggernaut with the necessity to be protected either by friendly units or a healthy amount of distance from its targets.
The Juggernaut cannot fire while mobile; in order to use its powerful artillery guns, it needs to plant itself in the ground first, a process which takes around two seconds to complete. Once implanted, it can and will fire at any target inside its attack radius; in order for it to attack anything outside that radius, it must rise back up, move to another spot, and then plant itself again.
Their attack is weaker than that of their Nod Artillery counterpart, but has a wider dispersal, and is best used against crowds of enemy infantry. While it is useful against infantry or even light armor, it is not very effective against heavily armored units or buildings. However, it has a significantly greater attack radius than Nod Artillery: considering that Nod Artillery has eggshell-thin armor, this means that artillery battles in Firestorm now become very lopsided. It is now extremely difficult for Nod Artillery to attack GDI bases defended by Juggernauts. Further, Nod bases which were once securely defended by entrenched artillery can now have them destroyed from a distance by Juggernauts. While Juggernauts are not useful against heavily armored units, Nod technology doesn't focus on heavy armor: only Tick-tanks can withstand a barrage long enough to try to rush their positions. However, the Tick-tank is infamously outclassed by the GDI Titan walker. It is now extremely difficult for Nod to counter a GDI assault force composed of Juggernaut and Titans. They are still weak against air units, and here there is something of an advantage because Nod's basic infantry have anti-air capability that GDI's Disc Throwers do not. However, while a bit more expensive, Jump Jet infantry or Hover MLRS can still cover the advance. For that matter, air strikes in Tiberian Sun are not particularly effective against large numbers of units, so a sufficient number of well protected Juggernauts can eventually grind down a Nod base from outside their firing range.
== AI behavior ==
Juggernauts controlled by the AI will not undeploy again once they are deployed, unless their target is within their minimum range.
Juggernauts controlled by the AI have the following behavior:
===Easy ===
*1x targeting production structures, base defenses, power plants, Construction yards, Tiberium refineries, Missile Silo or Upgrade Center
**This task force may be accompanied by 1 additional Juggernaut
**This task force will only be ordered to attack power plants if enemy base is at low power mode
**This task force will only be ordered to attack Tiberium Refineries if the enemy owns 4 or more of these
*1x deploying near friendly base
**This task force may be accompanied by 1 additional Juggernaut
===Medium/Hard===
* 3x targeting production structures, base defenses, power plants, Construction yards, Tiberium refineries, Missile Silo or Upgrade Center
** This task force will only be ordered to attack power plants if enemy base is at low power mode
** This task force will only be ordered to attack Tiberium Refineries if the enemy owns a certain number of these (3 in Medium, 2 in Hard)
** This task force may be accompanied by 3 additional Juggernauts (Hard only)
*3x deploying near friendly base
**This task force may be accompanied by 3 additional Juggernauts (Hard only)
==Gallery==
CNCFS_Juggernaut_Concept_Art.jpg|Concept art
FS_Juggernaut_Manual_Render.jpg|Manual render
FS_Juggernaut_Render.gif|Render of mobile Juggernauts
Juggernaut_2030_01.jpg|Render of Juggernauts attacking a Nod base in deployed mode
Juggernaut_deploy_animation.gif|Deploy animation
==Videos==
==See also==
* Artillery, Nod counterpart
==References==
Category:Firestorm vehicles