About: Juggernaut Mk. I   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

After analyzing field reports that showed grievous losses, the GDI Board of Directors met to address the issue of the lack of long-range mobile artillery support. The Juggernaut Mk. I combined GDI naval and walker technology by fitting three large-caliber naval guns to a modified Titan Mk. I chassis. 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 Juggernaut Mk. III, used by regular GDI regiments.

AttributesValues
rdfs:label
  • Juggernaut Mk. I
rdfs:comment
  • After analyzing field reports that showed grievous losses, the GDI Board of Directors met to address the issue of the lack of long-range mobile artillery support. The Juggernaut Mk. I combined GDI naval and walker technology by fitting three large-caliber naval guns to a modified Titan Mk. I chassis. 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 Juggernaut Mk. III, used by regular GDI regiments.
dcterms:subject
landspeed
  • 5(xsd:integer)
imgdesc
  • Mobile and deployed Juggernauts
armortype
  • Light
groundattack
  • 75(xsd:integer)
techlvl
  • 6(xsd:integer)
req
useguns
  • 120(xsd:integer)
Cooldown
  • 150(xsd:integer)
dbkwik:cnc/property/wikiPageUsesTemplate
Range
  • 18(xsd:integer)
Faction
Produced
Role
  • Self-propelled artillery walker
Name
  • Juggernaut Mk. I
ImgSize
  • 250(xsd:integer)
Cost
  • 950(xsd:integer)
Notes
  • Must deploy to fire
Sight
  • 9(xsd:integer)
HP
  • *350 *400
eliteability
  • Sensors
abstract
  • After analyzing field reports that showed grievous losses, the GDI Board of Directors met to address the issue of the lack of long-range mobile artillery support. The Juggernaut Mk. I combined GDI naval and walker technology by fitting three large-caliber naval guns to a modified Titan Mk. I chassis. 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. However, while other walkers were withdrawn from service, the Juggernaut and its descendants remained essential parts of the arsenal. 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 Juggernaut Mk. III, used by regular GDI regiments.
is wikipage disambiguates of
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software