Gigacannon

From Starsector Wiki
Jump to navigation Jump to search
Gigacannon
Gigacannon.png
EnergyDamageIcon.png
General Information
Mount Large, Energy
Primary Role Strike
Ordnance points 25
DPS 200
Damage type Energy
Range 700
Flux/sec 150
Accuracy Perfect
Turn rate Very slow
Shots/min 6
Damage 2000


"High-ranking naval officers on Ultradyne Askonia Combine board of directors rammed through large-scale AM projector weapon development despite objection of engineering lead. Project allegedly initiated at personal behest of so-called Executor [traitor Andrada]. HEGINT assets report test firing displays dramatic power output but weapon system integration projected to reduce enemy warfighting capability in fleet action due to doctrinal inefficacy. Recommend no sabotage operation." - classified report to the High Hegemon

–In-Game Description


The Gigacannon is effectively a large scale version of the Antimatter Blaster, with longer range and greater damage per shot, lack of dependency on ammunition, as well as drastically increased damage/flux efficiency.

Though the description talks about inefficiency, it specifically refers to the Executor not being suited to using the Gigacannon to its full effectiveness, not the weapon itself being ineffective. The main drawback of the weapon, on the other hand, is its extremely low rate of fire, with as much as 10 seconds needed between each shot, it's vital for the player to time each shot carefully, even more so compared to other strike weapons like the Tachyon Lance. Further contributing to the problem is how the Gigacannon requires large energy weapon mounts instead of the more easily available small mounts, meaning that the player cannot compensate for the weapon's poor DPS by mounting more of them easily. While the Gigacannon certainly has its uses, a weapon with greater DPS would be a more practical choice under most circumstances.


Icon check temp.png
Only up to date for version 0.96a. It is likely still broadly correct but not verified for the most up to date data yet. Please double check the Version History.