Not sure exactly where to put this, so I think I'll post it here.

And yes, I know, of all the things to say about this Lockbox and balance...

But seriously, I find the Elachi Torpedo rather lacking. In terms of a torpedo which is designed to be disabling, I think it's outperformed by tricobalts, and that shouldn't be the case.

Comparing the two, the Elachi Torp has a 10.5s cooldown, and a 10% chance for a base 2s disable. Tricobalts, on the other hand, have a 30.5s cooldown, and a 100% chance for a base 1.7s disable.

Now consider the following scenarios where you continuously fire either torp at a target for, say, 1281s (a little over 20 mins). Say the target is a transwarp gate, so it does not resist your attacks, and your torps always hit.

After 1281s, the tricobalt fired 42 times, the Elachi fired 122 times.

The trico procs a 1.7s disable on every hit, so the gateway is disabled for a total of 42 * 1.7 = 71.4 seconds (a little over a minute, and about 5% of the total combat time).

The Elachi, on the other hand, only procs 10% of the time, so on average it procced 12 times. Thus it disables the gateway for a total of 12 * 2 = 24 seconds (half a minute, a tiny 2% of the total combat time).

So far I've ignored the case where the torps are upgraded by TS or HY. I haven't completely looked at the TS case, but reading off of my tooltips (not the base numbers mind you), I get this: an Elachi HY gives 20K damage and a guaranteed 3s disable. A tricobalt HY gives about 29k damage and a guaranteed disable anywhere between 3s - 9s (average 6s, twice what the Elachi does).

Looking at these numbers, the stock tricobalt seems to be outperforming the Elachi torp a great deal. Given the cost of investment of the Elachi torp, the opposite should be true; the Elachi should be the superior disabling torpedo.

What I was considering was something like this: for the base Elachi torpedo, increase the proc chance to 33% (this is in line with the stock Chroniton proc chance) and the base disable up to 2.3s. So in the above scenario, the torpedo would have procced about 40 times, disabling the target for a total of 40 * 2.3 = 92s (compared to the tricobalt's 71.4s).

For the Torpedo Spread variant, I'm guessing it should be a guaranteed disable, but only for a reduced time, about 1.5s (similar to how a Chroniton behaves). For HY torps, perhaps the disable should be an average 7ish seconds, + or - 7ish seconds (so varying randomly between 1s and 15s).

Of couse, in the name of balance, I'd say (if it's not true already) that the Elachi disable should be resisted by Subsyst. Repair, cleansed by Engineering team, etc. Also, it probably also shouldn't be upgraded by the Nadeon Detonator console (as of now it does, and the disables stack).

Feel free to dispute me if my numbers are off or you disagree. Yes I know, I ignored PW doffs, and that a true torp boat could churn out more Elachi torps. But the same is true of tricobalts, AND you could do double disable duty with 1 fore 1 back, etc.