Reaper-class Torpedo

From Starsector Wiki
Jump to navigation Jump to search
Reaper-class Torpedo
Reaper.png
HighExplosiveDamageIcon.png
General Information
Mount Small, Missile
Primary Role Torpedo
Ordnance points 2
DPS 4,000
Damage type High Explosive
Range 1,200
Flux/sec 0
Speed Fast (400)
Tracking None
Shots/min 12
Damage 4,000
Ammo 1
Projectile health 500


A single unguided torpedo of devasting yield with a powerful on-board engine.

The quintessential strike weapon, a single Reaper torpedo is a large self-propelled, armored, unguided delivery system for an enriched AM-catalyzed nuclear warhead. The science behind the surprisingly compact detonator is poorly understood in the Sector though widely speculated to be based on physics classified as secret by Domain authority. What is known is that three or four of these slipping through PD arcs are enough to destroy even the largest capital ship.

–In-Game Description


Notes

The Reaper-class Torpedo is a single-shot, unguided strike weapon with the highest per-shot damage of any weapon in the game. It also comes in medium and large launcher variants. The Reaper has high HP (500) and can withstand light point defense fire.

The Reaper inherits the velocity of the launching ship. Consequently lateral movement will impart a "drift" to the torpedo and launching while flying forward will reduce the time the torpedo needs to reach top speed. Some players find it useful to decelerate while flying directly towards the target (C + W) in order to nullify any relatively sideways movement. Reaper torpedoes have a 0.5 second arming time so firing at point blank will cause them to bounce, unpredictably.

It is also deployed by the Cobra bomber.

A Shade misjudging the minimum arming time & is potentially about to be hit by it's own Reaper ricochet


Animation

Single Reaper.gif


Change History

0.8a

Expanded Missile Racks:

  • One-shot Reaper torpedo launcher now has a 5 second cooldown
Icon cross.png
At least two versions out of date. Last verified for version 0.8a-RC19. Please refer to Version History and update this page.